OraNA :: Oracle News Aggregator

When doing configuration management on your SOA application to various environments; development, test, acceptance and production. You would use you on mechanism for deployment.

• CruiseControl
• Maven
• Oracle SOA Build System

What I found out during some SOA projects, that your build system is too fast for the de Oracle SOA Suite server. When deploying a lot of BPEL processes and ESB services, you sometimes get strange errors. This is related that WSDL files cannot be found or strange errors when registering ESB services. The solution is very simple.

Introduce a wait time between each deployment. Choose this delay between 4 and 10 seconds.

After deployment, the system needs to take care that everything is in place. This will take some time. Therefore a new deployment directly after the previous one, could result in errors.

Marc

After a out of the box installation and configuration of the Oracle Application Server, most of the log files of the AS are configured to be rotated. This means that after a period or when they reach a particular size, the log file is copied and a new log files is created.
This gives the AS administrators flexibility to maintain these files; backup etc..

There is one log file, the so called standard output / standard err, also known as print output to console, that is not configured to be rotated. But this files is growing and growing, it could easily grow into hundreds of giga bytes.

The name of this files is:

$ORACLE_HOME/opmn/logs/default_group~OC4J_INSTANCE_NAME~default_group~1/log

It is possible to make this file rotatable.

Add the following parameters in the configuration of your OC4J instance,

In java-options:

-Dstdstream.filesize=8

Note: 8 means, rotate after 8 MB in size.

In oc4j-options:

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

Seperate standard outout and error messages.


See also the Oracle docs on this.