Tech Mastery: Deep Dives into AEM, Cloud Technologies, AI Innovations, and Advanced Marketing Strate

Installing the patches to weblogic server using Oracle Smart Update:

• Download the patch through metalink using the patch id or bug no.
• Uncompress patch zip file to $MWHOME/utills/bsu/cache_dir (If the cache_dir folder is not available then create the same)

•  Launch the Oracle Smart Update Tool (bsu.cmd) from $MWHOME\utils\bsu, this will list all the applied patchs and all those patches that are ready for installation.

CodeCache is full. Compiler has been disabled - Oracle SOA Suite 11g:

Frequently we used to see the below message in our log file.

Java HotSpot(TM) 64-Bit Server VM warning: CodeCache is full. Compiler has been disabled.
Java HotSpot(TM) 64-Bit Server VM warning: Try increasing the code cache size using -XX:ReservedCodeCacheSize=

The code cache is a memory area separate from the JVM heap that is used for compilation and storage of native code.This is where the JIT compiled methods are kept.

The JIT compilier will be disabled when the code cache is full. Once the JIT compiler is switched off due to the Code Cache being full, it does not switch back on.

This will affect the performance of the server in high extend.

We can try to increase the default code cache size to resolve this issue.

Steps to increase the code cache size(we have increased to 64m)

• Login into Admin Server node
• Open $DOMAIN_HOME/bin/setSOADomainEnv.sh file 
• Edit the "DEFAULT_MEM_ARGS" to add the following parameters at the end of line before double quotes: -XX:InitialCodeCacheSize=64m -XX:ReservedCodeCacheSize=64m
• Login into admin console and go to all the servers server start up properties tab and edit the section to add the following parameters at the end of the line  -XX:InitialCodeCacheSize=64m -XX:ReservedCodeCacheSize=64m

• Restart all servers (Admin and Managed)

Import/Publish the services from Oracle Service Bus to Service Registry:

• Login to OSB console
• Select System Administration and click on UDDI Registries and click Add Registry

•  Enter the Oracle Service Registry details as shown below and click on save

Storing the Cross reference data to a custom table - Oracle SOA Suite:

• Right-click the project and select New.

• Select SOA Tier from the Categories section, and then select Transformations.

• Select Cross Reference (XREF) from the Items section.

• Click OK.

• In the File Name field, specify the name of the cross reference file.

• In the End System fields, enter the end system names.

• Click OK.

How to identify the weblogic server version installed

1. cd %DOMAIN_HOME%/bin
2. Execute setDomainEnv.cmd
3.Execute java weblogic.version -verbose



The weblogic server version is 10.3.5.0

Difference between BPEL 1.1 and BPEL 2.0 – Oracle SOA Suite 11g:

• <forEach> activity to repeat the set of activities . Replace the FlowN activity in BPEL 1.1 version.
• <repeatUntil> - Use this activity if the body of an activity must be performed at least once. The XPath expression condition in the repeatUntil activity is evaluated after the body of the activity completes.
•  <if>-<elseif>-<else> - Replaces the switch activity in BPEL 2.0 - This activity enables you to define conditional behavior for specific activities to decide between two or more branches. Only one activity is selected for execution from a set of branches.
• Changed <terminate> to <exit>
• <compensateScope>  - to compensate the specified child scope
• A <rethrow> activity has been added to fault handlers this activity enables you to rethrow a fault originally captured by the immediately enclosing fault handler.