Changing the SOA Suite database Username etc in 10g

Changing the SOA Suite database Username etc in 10g

SOA 10g by default installs to orabpel and oraesb user. In a testing environment you may want to create more then one SOA 10g instance in one db. This procedure explains how to do that

1. First run the irca to create the necessary schemas.

./irca.sh all "xxxx.xxx.oracle.com 1521 xxx.xxx.oracle.com" welcome1 -overwrite ORABPEL welcome1  ORAESB welcome1 ORAWSM welcome1

Then run irca gaian with a different username's for example ORABPEL_OracleAS_3 , ORAESB_OracleAS_3 and ORAWSM_OracleAS_3.

./irca.sh all "xxx.xxx.oracle.com 1521 xxx.xxx.oracle.com" welcome1 -overwrite ORABPEL_OracleAS_3 welcome1  ORAESB_OracleAS_3 welcome1 ORAWSM_OracleAS_3 welcome1

2. Install the SOA Suite normally. SOA Suite 10g by default install in the orabpel and oraesb schema's only.

3. Now open the ${SOA_HOME}\j2ee\home\config\data-sources.xml file ,

and change the username and password etc for the data-sources. You can also use the EM Application Server control
for this purpose.

4.  From the ${SOA_HOME}\bpel\install\extensions directory, copy the following files to ${SOA_HOME}\bpel\domains\default\deploy:

    bpel_TaskActionHandler_1.0.jar
    bpel_TaskManager_1.0.jar

5. Connect to the oraesb schema  and run the following sql script ,

SQL> spool params.sql
SQL> SELECT 'INSERT INTO esb_parameter VALUES (''' || param_name || ''', ''' || param_value || ''');' FROM esb_parameter;
SQL> spool off
SQL> quit

Take the params.sql file and run it against the schema ORAESB_OracleAS_3.

6. Now apply the latest SOA 10g patch set ,
and run the schema upgrade scripts on the new schemans i.e ORABPEL_OracleAS_3 , ORAESB_OracleAS_3

If your SOA Suite is 10.1.3.3 or later, you will have to also run an additional script that updates the BPEL schema. This is documented in the install guides for each version, but in summary, the script is:

    ${SOA_HOME}\bpel\system\database\scripts\upgrade_10131_10135_oracle.sql

7. For OWSM open the file ,
${SOA_HOME}\owsm\bin\install_properties

Scroll down to the section that contains the install.db.* properties. After backing up the existing settings, modify them for your environment:

    install.db.type=oracle
    install.db.driver.type=thin
    install.db.host=localhost
    install.db.port=1521
    install.db.name=xe
    install.db.userid=oraowsm_OracleAS_1
    install.db.password=oraowsm

8. Run the command ,

${SOA_HOME}\owsm\bin\wsmadmin.bat install

9. Restart all the oc4j containers and check whether every thing is working fine or not.