Now, oc4j-ra.xml is runtime connection configuration file which binds connections details to JNDI names. Suppose while designing the BPEL Process, if you choose a connection to your apps database - For example:
Say, atgtest1.idc.oracle.com-1528-AIA is the connection, the JNDI name which would be created will be 'eis/Apps/atgtest1' - This can be changed at anytime.
At runtime this JNDI name would be looked up in oc4j-ra.xml to find out which database connection it points.
oc4j-ra.xml is present at $ORACLE_HOME\j2ee\home\application-deployments\default\AppsAdapter, where ORACLE_HOME is directory where 1013 SOA Suite is installed.
Sample entry in oc4j-ra.xml would be like this (click on enlarge):
Replace APPS_USER,APPS_PASSWORD,MACHINE,PORT_NUMBER and SID with those of Database you intend to use apps adapter on.
Restart BPEL Server after modifying oc4j-ra.xml to reflect the changes. Inorder to restart server :
a. Open command shell
b. cd $ORACLE_HOME/opmn/bin
c. $ opmnctl stopall
d. $ opmnctl startall
No comments:
Post a Comment