JGroups Log Configuration

Even though you set "org.collaxa.thirdparty.jgroups” logging level from BPELConsole to minimum, still you will find that jgroup messages are logged in file. To have full control on JGroups logging, please perform the following steps:

• Stop the OC4J process using opmnctl

• Open the $ORACLE_HOME/j2ee/<oc4j_name>/config/j2ee-logging.xml file and add the following log handler for jgroups. You can change the path to any other directory. I have set it to $ORACLE_HOME/bpel/system/logs/jgroups folder where a log.xml will be created. This file will contain the jgroups log messages:

<log_handler name="jgroups-handler" class="oracle.core.ojdl.logging.ODLHandlerFactory">
<property name="path" value="%ORACLE_HOME%/bpel/system/logs/jgroups"/>
<property name="maxFileSize" value="10485760"/>
<property name="maxLogSize" value="104857600"/>
<property name="encoding" value="UTF-8"/>
<property name="supplementalAttributes" value="J2EE_APP.name,J2EE_MODULE.name"/>
</log_handler>


Add the following logger, immediately below the org.quartz logger:

<logger name="org.collaxa.thirdparty.jgroups" level="SEVERE" useParentHandlers="false">
<handler name="jgroups-handler"/>
</logger>

• Start the BPEL OC4J process using opmnctl and confirm the jgroups trace level messages in the $ORACLE_HOME/bpel/system/logs/jgroups/log.xml file.

• You can use the EM console to change the level for "org.collaxa.thirdparty.jgroups" to the desired level, or directly edit this file and change the level.

oc4jadmin password change in SOA Suite

The administrator password for each OC4J instance in the Cluster must be the same as the administrator password for the OC4J instance on which Application Server Control is running. So if you have something like home which is your admin instance and than you  have oc4j_soa, oc4j_wsm, oc4j_gtwy and you have to change password of oc4jadmin then you have to perform following steps.

1. Change oc4jadmin password for admin oc4j in cluster. 
   • Simply log in using the oc4jadmin user name and password, and then click Setup.
2. On each node and oc4j edit ORACLE_HOME/j2ee/oc4j_instance_name/config/system-jazn-data.xml to update oc4jadmin password

<user>
     <name>oc4jadmin</name>
     <display-name>OC4J Administrator</display-name>
     <guid>41A2E560C96711DABFD08D3BF8B780C4</guid>
     <description>OC4J Administrator</description>
     <credentials>{903}4nlfYYDwaqMJipVbGXuS2ce8egfwBPqp</credentials>
</user>

Modify credentials to say password123. Please remember to put ! as the exclamation point (!) ensures that the password will be encrypted in the configuration file.

<credentials>!password123</credentials>

Node:There is another approach of modifying with EM console where you go to Cluster Topology > <remote_oc4j> > Administration > Security Providers > Instance Level Security > Realms > click the number in the Users column. Click oc4jadmin and modify password. Return to the Cluster Topology page and restart the remote OC4J instance.

SOA Suite Log File Rotation

In <ORACLE_HOME>/opmn/conf/opmn.xml, apply the following changes for each OC4J you want to modify log file settings

• Add -Dstdstream.filesize=FILE_SIZE_IN_MB -Dstdstream.filenumber=TOTAL_NO_OF_FILES parameters in the <java-options>. For example, if you want to limit log file size to 10MB and total number of files to be created to 10 than add

-Dstdstream.filesize=10 -Dstdstream.filenumber=10

• Add -out and -err parameters to the <oc4j-options> to specify standard output and standard error log files.

-out $ORACLE_HOME/opmn/logs/soa_log.out -err $ORACLE_HOME/opmn/logs/soa_log.err

Apply the changes and restart OC4J. If you are just restarting OC4J make sure to reload opmn before restarting.

After restart you should be able to see log files soa_log_YYYY_MM_DD_HH_MI_SS.out and  soa_log_YYYY_MM_DD_HH_MI_SS.err created under $ORACLE_HOME/opmn/logs/<oc4j_name>_<group_name>_<jvm_id> folder.

Resetting ESB Metadata repository

Sometimes ESB repository does not behaves as expected especially after a rigorous DEV cycles or for some other reasons. In order to bring it back to clean, at $ORACLE_HOME/integration/esb/bin directory a script called ‘reset.bat/sh’ is available. This script will cleanup the ESB repository. Simply execute the command as shown below and follow the output.

./reset.sh -DDB_URL=jdbc:oracle:thin:@//db_host:db_port/sid -DDB_USER=oraesb -DDB_PASSWORD=oraesb123

Once you are able to execute it successfully, its very important to restart your ESB instance before using it.