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.
Friday, June 13, 2008
Sunday, June 01, 2008
Oracle SOA Build System: Web Enabled
The Oracle SOA Build System is based on a (L)unix script. The script will validate the input parameters and then call the Ant build tool. To deploy and or compile the SOA code to the application server.
Using this script, you need access to the server on which the script is available and configured. You also need some basic (L)unix commands to execute the task of the build system. Sometime administrators are not willing to give access to those systems, even if the access privileges are low.
Access to the Oracle SOA Build System via a WEB interface makes it more user friendly and less failures in the usage of the tool.
I have looked on the Net to integrate the build tool in other tools that are used in continuous integration. Tool such as CruiseControl are very useful. But most of these tools are working around a single environment; development. We I was looking for was a web interface in which I can use the full functionality of the build tool.
I did a project were we integrate the tool in CruiseControl, but it did not give me the flexibility of the tool itself.
Now a few new files have been created to enable the obbuild system to be executed from the browser. This result that the interface is very simple and everyone can use it. The next screens shows you some examples. The interface is simple but effective.
Deploy the SalesOrderEBS to the ESB server.
Using this script, you need access to the server on which the script is available and configured. You also need some basic (L)unix commands to execute the task of the build system. Sometime administrators are not willing to give access to those systems, even if the access privileges are low.
Access to the Oracle SOA Build System via a WEB interface makes it more user friendly and less failures in the usage of the tool.
I have looked on the Net to integrate the build tool in other tools that are used in continuous integration. Tool such as CruiseControl are very useful. But most of these tools are working around a single environment; development. We I was looking for was a web interface in which I can use the full functionality of the build tool.
I did a project were we integrate the tool in CruiseControl, but it did not give me the flexibility of the tool itself.
Now a few new files have been created to enable the obbuild system to be executed from the browser. This result that the interface is very simple and everyone can use it. The next screens shows you some examples. The interface is simple but effective.
Download the latest version from your source control system.
Deploy the SalesOrderEBS to the ESB server.
Subscribe to:
Posts (Atom)