Tuesday, June 28, 2011

Printing Soap messages in TIBCO Business works (BW)

If you want to print the Soap messages (in and out) from SoapRequestReply Activity in business works designer specify -p (e.g. soap_properties.cfg) in advance while running tester for any bw process.

and in the configuration file (soap_properties.cfg) define.
java.property.com.tibco.plugin.soap.trace.inbound=true
java.property.com.tibco.plugin.soap.trace.outbound=true
java.property.com.tibco.plugin.soap.trace.filename=c:/soap.txt
java.property.com.tibco.plugin.soap.trace.pretty=true
Trace.Task.*=true
Trace.Debug.*=true

This is helpful in doing junit testing for any webservice integration from designer

Thursday, June 16, 2011

Hot deployments in weblogic

Pretty useful link for the developers. Saves sometimes while development.

http://download.oracle.com/docs/cd/E13222_01/wls/docs81/webapp/deployment.html#158848

Printing log4j loggers during junits

Simple but useful. While running jUnit during development people see warning log4j appenders could not be found and it doesn't print the log4j statments like log.debug or log.info.
Developer generally put the sysout statements or using debug mode to see the values and the flows.

One of the way is to create a basic template for log4j property or xml file and load it in the setup method.
The other easiest way to add a single line in the setup method. Log4j libs should be there in the classpath.

/* This will initialize the basic log4j configurations */
BasicCongfigurator.configure();