« December 2008 | Main

September 2009 Archives

September 7, 2009

Increasing the logging to Weblogic Message Bridge

Steps to increase the logging on Weblogic 10.3.1 Message Bridge.

It would be great if Weblogic too has a logging feature enablement for all the individual components in a single page as in OC4J. There is one Logging tab for the Domain but it doesnt help any. I have an issue in JMS Message Bridge but couldnt find any tab/page where I could increase/enable the logging for the Bridge.

After digging few Weblogic document, I found that this has to be done via the flags while WL is being started.

The easiest place is in the startWeblogic.cmd (startWeblogic.sh for Linux flavours). Search for the comment "START WEBLOGIC" and then include the debug flags in the Weblogic startup line as follows:

Original line:
echo JAVA_HOME\bin\java JAVA_VM MEM_ARGS -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy JAVA_OPTIONS PROXY_SETTINGS SERVER_CLASS
JAVA_HOME\bin\java JAVA_VM MEM_ARGS -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy JAVA_OPTIONS PROXY_SETTINGS SERVER_CLASS
)

Included line:
echo JAVA_HOME\bin\java JAVA_VM MEM_ARGS -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy JAVA_OPTIONS PROXY_SETTINGS SERVER_CLASS
JAVA_HOME\bin\java JAVA_VM MEM_ARGS -Dweblogic.Name=%SERVER_NAME% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy -Dweblogic.Debug.DebugMessagingBridgeStartup=true -Dweblogic.Debug.DebugMessagingBridgeRuntime=true JAVA_OPTIONS PROXY_SETTINGS SERVER_CLASS
)

There is an IF statement in starting Weblogic script that checks for redirection of the log file. Its in the same location as above statement. So, include the flags in the both the places.

Restart Weblogic and check the AdminServer.log for more information on Bridging.

September 17, 2009

Benefits of upgrading to Weblogic Server

There has been a mail thread on this topic in the FMW Forum and I liked the White paper on this. Couple of points from the people who replied to this:

In addition to being the strategic runtime for Oracle Fusion Middleware, the new product lines acquired from BEA, the Oracle Applications portfolio and the forthcoming Fusion Applications, Oracle WebLogic Server offers significant additional capabilities to the Oracle Application Server customer base beyond that which was available within Oracle Application Server including:

1. Runtime: Within the area of the core container, beyond the fully certified Java EE 5.0 compatibility, WebLogic Server extends the runtime in numerous areas including the Java Message Service (message ordering with unit of order, unit of work, scale out with distributed destinations and store and forward infrastructure, C and .NET JMS clients), Web services (conversational Web services, buffered Web services, asynchronous Web services, SOAP over JMS), built-in Tuxedo integration and runtime tuning (self tuning work managers) amongst others.

2. Development: Within the area of development capabilities above that in basic servers, WebLogic includes Java class FastSwap capabilities for fast test/debug cycles without server restarts, split development for tightly integrated IDE development, HTTP Publish/Subscribe Server for AJAX applications, filtering class loader to handle multiple versions of class libraries, Ant tasks for development, deployment and configuration automation and deep Eclipse and JDeveloper integration amongst others.

3. Operations and Administration: Within the area of operations and administration, WebLogic Server extends basic server capabilities in numerous areas including transactional and batch configuration, zero-downtime re-deployment, domain template builder and configuration wizard for simplified cloning, consistent scripting and command line tooling for all server configuration with WebLogic Scripting Tool, sophisticated lifecycle control over applications and the container, built in diagnostics framework amongst others.

4. High Availability: Within the area of high availability WebLogic Server extends basic core availability capabilities in a number of areas including clustered JNDI, whole server migration, service migration, high availability for singleton services

The white paper can be downloaded here.

September 29, 2009

Move AIA Home from one location to another

More often, w face this issue when preparing the DEV/TEST instances. What if we install AIA in one of the directories and what we our mount point is out of space and we want to move this directory to another location?

1. The solution is very simple. The configuration for AIA home is referred only in one location i.e., opmn.xml file. This file is located in $ORACLE_HOME/opmn/conf directory, where ORACLE_HOME is the directory location where the SOA Suite is installed.

For the oc4j_soa container, the AIA home is mentioned in the module-data element as follows:

-Daia.home=/slot/ems1054/oracle/product/AIAHOME

So, if the AIA Home needs to be moved to a different location, this is one of the config files to be changed.

2. Then, in the $AIA_HOME/bin, change the locations of the directories in aiaenv.sh (aiaenv.cmd for Windows).

3. For some of the PIPs like Revenue Accounting, the AIA location is specified in the $AIA_HOME/config/AIAConfigurationProperties.xml file. So, change the locations in this file as well.

Thats it !!! Restart the SOA and everything is fine to go with new AIA Home.

Deploy using the deploy tool utility in AIA

One of the good utilities that can be used to deploy the BPEL/ESB is AIA deploy tool. In the BPEL and ESB projects that we create, we use the partner link locations, WSDLs and XSDs for a particular server. If we need to deploy these projects to a different server, then we need to change the locations of the WSDLs and XSDs everytime.

Instead of doing it manually, we can use AIA Deploy tool. This utility has a tokenizer which will tokenize and change the URLs accordingly in the entire project and generates the build.xml (incase of BPEL) and deploymentplan.xml (incase of ESB). We can then run the 'ant' tool to deploy our processes to the server.

The DeployTool is located in $AIA_HOME/util. Here are the steps to use it.

1. There is a file called Tokenizer.properties which we need to populate the process directory (directory of the BPEL/ESB project). Ensure the process directory has the read/write permissions. Update the Tokenizer.properties with the following properties:

a) home.dir1 -> enter the directory of the process to be deployed.
eg: home.dir1=/product/example/JMSAdapterServices/MySample

b) ESB_COPY_FOLDER =/product/AIA_HOME/util/DeployTool/EsbCopy

c) BPEL_COPY_PATH=product/AIA_HOME/util/DeployTool/BpelCopy

2. Run the command to deploy:
$ ant runesb -DTokenizerPropsFilePath=/product/AIA_HOME/util/DeployTool/Tokenizer.properties

$ ant runbpel -DTokenizerPropsFilePath=/product/AIA_HOME/util/DeployTool/Tokenizer.properties

Note: Deploy tool will only create the deployment plan for ESB. It does NOT deploy the process. Once the deployment plan is generated, goto the ESB directory and run the ant tool to deploy the process.

4. Goto $AIA_HOME/bin and source the AIA environment file - aiaenv.sh. This will source all the environment variables. Then run "ant" to deploy the process.

About September 2009

This page contains all entries posted to Learn with Pavan in September 2009. They are listed from oldest to newest.

December 2008 is the previous archive.

Many more can be found on the main index page or by looking through the archives.

Creative Commons License
This weblog is licensed under a Creative Commons License.
Powered by
Movable Type and Oracle