Changing Metadata Repository

In my earlier post I wrote about and how to create metadata repository. In this I am writing how to change the metadata repository. By changing metadata repository means pointing the BPM to store the BPEL processes and instances information on a new server.

There are two ways of doing the same :

1. First is through EM (Enterprise Manager) console and
2. The second is directly editing the data-sources.xml file.

So, lets do it through first method.

Through Enterprise Manager or EM Console

1. Login to EM Console.
2. Click the instance for which data repository has to be changed. In this case oc4j_soa.
3. 
   Click on administration tab.
4. 
   Click on the arrow against the JDBC Resources.
5. 
   Click on the connection pool for which data repository has to be changed.
6. 
   Enter the URL and credentials of new database.
7. 
   Click Apply.
8. Repeat from step 5 for other connection pools.
9. Restart the SOA Suite.
10. You are done.

The other way to do the same is to directly edit the data-sources.xml file.

Here are the steps:

1. Find data-sources.xml in [Oracle Home\j2ee\oc4j_soa\config]
2. Open it in any text editor.
3. You'll find the sections as below:
   
4. Replace the values of host port service_name with that of new database.
5. Restart the SOA Suite.
   

Creating Metadata Repository

BPEL Metadata Repository is a place where all the information about a deployed BPEL processes and all its instances(running, errored or stale) is stored. Metadata Repository resides on a database specified during the advance installation of SOA Suite or on ORALITE database provided by oracle with SOA Suite for basic installation.

Creating Metadata Repository:

To create Metadata repository an IRCA script must be executed on the database. The script creates three schemas on the database viz. orabpel, oraesb and orawsm. IRCA stands for 'Integration Repository Creation Assistant'. To run the IRCA script follow the steps as below:

1. Set ORACLE_HOME in your for using SQLPLUS.

2. Connect to the database.

3. Set JAVA_HOME.

4. Execute the irca.sh (UNIX/Linux)/irca.bat(Windows) command located in the soa_schemas\irca folder of the SOA Suite Installaion to load the schema into the target database.

   IRCA provides two execution modes: silent and interactive.

   In the silent mode, you provide all the execution parameters in a single string, using the syntax:

irca[.sh] all ["server port servicename"] [database password] -overwrite [schema name] [schema password]...

Breakup of command:

all : for all schema

server: database location

port: port on which service is running

servicename: name of the service(for eg: xe in case of xe database)

database password: password of the database

overwrite: overwrites the existing definition of schemas

schema name: name of the schema(orabpel oraesb or orawsm)

schema password: any password you provide

for eg:

irca[.sh] all "localhost 1521 orcl" welcome -overwrite orabpel orabpel oraesb oraesb orawsm

In the interactive mode, you invoke the command by specifying only the schema to be loaded:

irca[.sh] orabpel

The utility prompts you for the database details and the passwords.

NOTE: If basic installation is done then IRCA script is not required.