Websphere SSL - invalid certificate, key identifier is missing from authority key identifier extension

when you tried to access to secured WebService from your Websphere application , and get such error ":org.apache.axis2.AxisFault: 
javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.g:PKIX path building failed: java.security.cert.CertPathBuilderException: invalid certificate, key identifier is missing from authority key identifier extension"

you probably need to install the certificate in your web sphere

To establish trusted server-to-server communication for IBM Connections, import signer certificates from IBM HTTP Server into the WebSphere Application Server default trust store.

There are different types of certificates that you can use. This procedure describes how to import a self-signed certificate. You can also import a certificate that you purchased from a third-party Certificate Authority. To help decide a key file strategy for your environment, go the IBM HTTP Server knowledge center.

To import a public certificate from IBM HTTP Server to the default trust store in IBM WebSphere Application Server, complete the following steps:

Procedure

1. Log into the IBM WebSphere Application Server Integrated Solutions Console and select Security > SSL Certificate and key management > Key stores and certificates.
2. Click CellDefaultTrustStore.
3. Click Signer Certificates.
4. Click Retrieve from port.
5. Enter the Host name, SSL Port, and Alias of the web server. The Alias is typically an arbitrary string that will become the name of the credentials.
6. Click Retrieve Signer Information and then click OK. The root certificate is added to the list of signer certificates.
7. If using Tivoli® Access Manager or other proxies, also repeat steps 4-6 for your Tivoli Access Manager or other proxy servers.
8. restart server.

the above is from Adding certificates to the WebSphere trust store

there is another way :

Procedure

export the certificate :

navigate to the url via browser , in the browser click on the certificate , and export it in DER format or base64 format.

save it in accessible path.

1. Log into the IBM WebSphere Application Server Integrated Solutions Console and select Security > SSL Certificate and key management > Key stores and certificates.
2. Click NodeDefaultTrustStore.
3. Click Signer Certificates.
4. Click Add.
5. Enter the Alias of the web server. The Alias is typically an arbitrary string that will become the name of the credentials, and the exported certificate location- described above, choose the right dataType  (DER format or Base64).
6. Then click OK. The root certificate is added to the list of signer certificates.
7. restart server.

TRACE HTTP communication on WebSphere

Problem determination: Debugging HTTP communication using Tracing, HTTP error, and NCSA access log settings | WebSphere .



good article

WebSphere PMI – Performance monitor

WebSphere PMI – Performance monitor

General settings

Make sure PMI is enabled

In the above screen you can control which level of logs the PMI would monitor , basic-extended-all or custom were you can choose your own statistics set.

Basic overhead up to 2%

_ Extended overhead up to 3%

_ All overhead of up to 6%

_ Custom will depend on the counters enabled but it is reasonable to expect

somewhere between 2%-6%

Runtime monitor

Open the current activity

Choose the statiscs you want to see

Click on the view modules – to see the graph .

Note:

You can log to file all the results to see it after

If you want to log to file – you can control on the log files

To see the logs

Browse to the tpv file – and click on the ViewLog button .

Extra details – and links could be found here:

Case study: Tuning WebSphere Application Server V7 and V8 for performance

WebSphere Application Server V7: Monitoring the Runtime

Tuning performance

 

WebSphere Application Server Performance Tuning Toolkit

enjoy 

Yaniv Tzanany

 

Tuning WebSphere Application Server V7 and V8 for performance

Case study: Tuning WebSphere Application Server V7 and V8 for performance:

The WebSphere® Application Server Performance Tuning Toolkit is an Eclipse-based intelligent tool designed to help users tune the performance of WebSphere Application Server using data collection, data analysis, and statistical inference technology. It is designed to help users locate bottlenecks and tune their applications appropriately.

Solving memory problems in WebSphere applications

Learn how to identify root causes for and solve memory problems in WebSphere® Commerce during system test.
Solving memory problems in WebSphere applications

Websphere Max memory allocation for JVM

When you set the max memory size on websphere  7 installed on 32 bit machine – you will get the next warning:

 You have set the Maximum heap size field to a value greater than 2 gigabytes. This is only valid on a 64 bit server. You can ignore this warning if the server will run in 64 bit mode; otherwise, the maximum value is 2048.

The server failed to startup on 32 bit machine when I set  the max memory to 2200 (M).
in the startServer.log - you can find such logging:

ADMU7704E: Failed while trying to start the Windows Service associated with server: server1;
probable error executing WASService.exe: Starting Service: YANIVTNode01
Service failed to start.  startServer return code = -1



I test it on 64bit server , I set the max memory to 2500 , and the server startup successfully.
Summary:
If we want more than 2G RAM allocation for websphere on windows  , you must used 64Bit server.

enjoy 

Yaniv Tzanany

Websphere - RSA premaster secret error , Illegal key size or default parameter

When i used signer with strong RSA key greater than 2048 bits on my Websphere 6.1 ( i did not test it on newer version) ,  i get the next exception  - see below.


its looks like websphere 6.1 could not handle stronger cryptography greater than 2048bits, and you need to expand/enhance websphere to allow for it to work with RSA keys greather than 2048.


to fix such behavior,  install the unrestricted policy files following the next steps:
 - Make a backup of the current policy files: local_policy.jar and      
US_export_policy.jar located at "jre\lib\security". The files should be
backed up outside of classpath.                                        
- Remove the current policy files from "jre\lib\security" completely.  
Renaming is not enough.                                                
- Download the unrestricted policy files from                          
https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=jcesdk
- Copy the new policy files to "jre\lib\security"                      
- Restart WAS/APP/JVM and verify the results                            


good luck 
Yaniv Tzanany



this is the exception when you used the default setting and try to work with RSA grater than 2048 under webspehere:


javax.net.ssl.SSLKeyException: RSA premaster secret error
   at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
   at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:83)
   at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java:84)
   at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:499)
   at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2114)
   at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096)
   at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
   at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)


Caused by: com.ctc.wstx.exc.WstxIOException: Connection has been shutdown: javax.net.ssl.SSLKeyException: RSA premaster secret error
   at com.ctc.wstx.sw.BaseStreamWriter.finishDocument(BaseStreamWriter.java:1692)
   at com.ctc.wstx.sw.BaseStreamWriter.close(BaseStreamWriter.java:288)
   at org.apache.axiom.util.stax.wrapper.XMLStreamWriterWrapper.close(XMLStreamWriterWrapper.java:46)
   at org.apache.axiom.om.impl.MTOMXMLStreamWriter.close(MTOMXMLStreamWriter.java:174)
   at org.apache.axiom.om.impl.llom.OMSerializableImpl.serializeAndConsume(OMSerializableImpl.java:197)
   at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:79)
   ... 79 more
Caused by: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLKeyException: RSA premaster secret error
   at com.ibm.jsse2.jc.i(jc.java:211)
   at com.ibm.jsse2.jc.j(jc.java:399)
   at com.ibm.jsse2.j.write(j.java:19)
   at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:88)
   at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:146)
   at org.apache.commons.httpclient.ChunkedOutputStream.flush(ChunkedOutputStream.java:191)
   at com.ctc.wstx.io.UTF8Writer.flush(UTF8Writer.java:99)
   at com.ctc.wstx.sw.BufferingXmlWriter.flush(BufferingXmlWriter.java:214)
   at com.ctc.wstx.sw.BufferingXmlWriter.close(BufferingXmlWriter.java:194)
   at com.ctc.wstx.sw.BaseStreamWriter.finishDocument(BaseStreamWriter.java:1690)
   ... 84 more
Caused by: javax.net.ssl.SSLKeyException: RSA premaster secret error
   at com.ibm.jsse2.cb.(cb.java:57)
   at com.ibm.jsse2.eb.a(eb.java:192)
   at com.ibm.jsse2.eb.a(eb.java:114)
   at com.ibm.jsse2.db.m(db.java:208)
   at com.ibm.jsse2.db.a(db.java:259)
   at com.ibm.jsse2.jc.a(jc.java:271)
   at com.ibm.jsse2.jc.g(jc.java:403)
   at com.ibm.jsse2.jc.a(jc.java:401)
   at com.ibm.jsse2.j.write(j.java:10)
   at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:88)
   at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:146)
   at org.apache.commons.httpclient.ChunkedOutputStream.flush(ChunkedOutputStream.java:191)
   at com.ctc.wstx.io.UTF8Writer.flush(UTF8Writer.java:99)
   at com.ctc.wstx.sw.BufferingXmlWriter.flush(BufferingXmlWriter.java:214)
   at com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:311)
   at org.apache.axiom.util.stax.wrapper.XMLStreamWriterWrapper.flush(XMLStreamWriterWrapper.java:50)
   at org.apache.axiom.om.impl.MTOMXMLStreamWriter.flush(MTOMXMLStreamWriter.java:184)
   at org.apache.axis2.databinding.utils.writer.MTOMAwareXMLSerializer.flush(MTOMAwareXMLSerializer.java:79)
   at org.apache.axis2.databinding.ADBDataSource.serialize(ADBDataSource.java:94)
   at org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMSourcedElementImpl.java:691)
   at org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:965)
   at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally(SOAPEnvelopeImpl.java:283)
   at org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:245)
   at org.apache.axiom.om.impl.llom.OMSerializableImpl.serializeAndConsume(OMSerializableImpl.java:193)
   ... 80 more
Caused by: java.security.InvalidKeyException: Illegal key size or default parameters
   at javax.crypto.Cipher.a(Unknown Source)
   at javax.crypto.Cipher.a(Unknown Source)
   at javax.crypto.Cipher.a(Unknown Source)
   at javax.crypto.Cipher.init(Unknown Source)   at com.ibm.jsse2.cb.(cb.java:8)                                                    

WebSphere "IBM End user tried to act as a CA"

When i tried to access a secured web services i get the next error:

org.apache.axis2.AxisFault: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.h: End user tried to act as a CA

at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)

at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:83)

at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java:84)

at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:499)

the CA in this case is Entrust company.

after some hours , i found the next article that helped me to solved it out , and this way i understood i am not alone here.

the fix is described here:

IBM End user tried to act as a CA - United States.

summery:

update the java.security file , set the

ssl.TrustManagerFactory.algorithm to use IbmPKIX insteaf of IbmX509 .

this article gave me the clue that its somthing with entrust CA as well

http://academicwritingtips.org/component/k2/item/899-entrust.html

and restart your server.

enjoy

Yaniv Tzanany

IBM Recommended values for Web server plug-in config

Recently i solved a problem when making a call to a Websphere that took about 70 seconds to response.

The client get web service invocation error after 60 seconds.

we try to find out where such parameter is set , because its obvious that someone is dropping our client connection ( its very long time but at least get the client be happy its worked), i found such parameter in the server http plug -in config file , the parameter is :

ServerIOTimeout means "how long should the plug-in wait for a response from the application". and its was set to 60 seconds , i increase it to 120 seconds.

now i need to find out why its take 70 seconds...................

the next link is the recommended values for such plug in with explanation.

IBM Recommended values for Web server plug-in config - United States

enjoy

Yaniv Tzanany

SSO - WebSphere with a side of SPNEGO

This document is intended to provide instructions to configure SPNEGO for WebSphere Application Server in standalone and clustered configurations using Microsoft Active Directory as the Kerberos security server. It is meant to be a ‘quick-start’ guide, providing the minimum steps and default options required to get up and running quickly in both WAS 6.1 and WAS 7.0 environments

IBM Techdocs White Paper: WebSphere with a side of SPNEGO

Working with WebSphere MQ JMS Under WebSphere app server

i struggled allot to make this JMS  sample working .
follow the next instruction to use JMS under web sphere.

1. get into admin console
2. get into JMS->connection factories  -> new
    choose web sphere MQ , click OK .
give it a logic name , and a jndi name such as jms/myMqFactory, and set the correct parameters during the wizard.
click finish and save.

3. goto Resources -> JMS ->queues
4. click new , and choose websphere MQ message provider
set the name and jndi name such as jms/mqRequestQ
and set the queue name
5. click apply and save.

some resources i used :
Developing a JMS client

IBM WebSphere Developer Technical Journal: Building an Enterprise Service Bus with WebSphere Application Server V6 -- Part 3
A java.lang.ClassCastException error occurs during a JNDI lookup of a queue connection factory

How to extract Queue Manager Name from CF / QCF in your J2EE JMS application

here is the code snippets, i used tp send message to mqRequestQ and get result from mqResponseQ , and pick the message with the same msg id:

private void testJMS(String qIn,String qOut )
{

    String  outString                 = "I am a string from JMS";
    String  qcfName                   = "jms/myMqFactory";
    String  qnameIn                   = "jms/mqRequestQ";
    String  qnameOut                  = "jms/mqResponseQ";
    boolean verbose                   = false;

    Session           session    = null;


    Connection        connection = null;
    ConnectionFactory   qcf  = null;

    Queue                  inQueue    = null;
    Queue                  outQueue   = null;
    InitialContext context = null;
    try {
context = new InitialContext();
qcf = (ConnectionFactory)context.lookup( qcfName );
inQueue = (Queue)context.lookup( qnameIn );
outQueue = (Queue)context.lookup( qnameOut );

   if(qcf != null)
   {
connection = qcf.createConnection();  
connection.start();
boolean transacted = false;
session = connection.createSession( transacted,
Session.AUTO_ACKNOWLEDGE);
((MQQueue)inQueue).setTargetClient(JMSC.MQJMS_CLIENT_NONJMS_MQ); //its 1
MessageProducer  queueSender = session.createProducer(inQueue);
queueSender.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
queueSender.setTimeToLive(60000); // in milli seconds 0 - unlimited
TextMessage outMessage = session.createTextMessage(outString);
outMessage.setJMSCorrelationID("Alis0000");
queueSender.send(outMessage);
queueSender.close();

String msgID  = outMessage.getJMSMessageID();
String selector1 = "JMSMessageID='"+msgID+"'";
MessageConsumer queueReciever =  session.createConsumer(outQueue, selector1);
javax.jms.Message inMessage =  queueReciever.receive(2000);
if ( inMessage instanceof TextMessage )
{
String replyString = ((TextMessage) inMessage).getText();
}
queueReciever.close();

session.close();
session = null;
connection.close();
connection = null;
   }

} catch (NamingException e) {
// there is no such DSN lets report it and will try to work without the DataSource name

} catch (JMSException je) {
      System.out.println("JMS failed with "+je);
      Exception le = je.getLinkedException();
      if (le != null)
      {
  System.out.println("linked exception "+le);
      }
}
}

enjoy
Yaniv Tzanany

Work manager in WebSphere

The Work Manager API offers a solution for performing parallel processing directly within a managed environment. You can leverage this new offering to implement parallel processing within a J2EE container.
here are some interesting links to this issue:

The wise work manager for context-based scoping - Improve thread performance with the Work Manager API

The Work Manager API: Parallel Processing Within a J2EE Container

Notes about the Work class you might implement under websphere , when:
if  isDaemon  return  true, this Work is expected to run a long time and will not use a pooled thread.

enjoy
Yaniv T

MQ Queue Manager connection pooling (MQQueueManager)

WebSphere MQ classes for Java Version 5.2 provides additional support for applications that deal with multiple connections to WebSphere MQ queue managers.
When a connection is no longer required, instead of destroying it, it can be pooled, and later reused.
This can provide a substantial performance enhancement for applications and middleware that connect serially to arbitrary queue managers.

read this complete article , with sample how to achieve connection pooling in your software.

regards
Yaniv Tzanany

Eclipse Memory Analyzer with phd files - IBM dump format

If you try to open phd file with the MAT software (Eclipse Memory Analyzer Tool) , you will get some error,"Not a HPROF heap dump (java.io.IOException)".

the solution is to install IBM Diagnostic Tool Framework for Java Version 1.4 to the MAT.

Help -> software update -> find and install ,Click next  -> new archive site -> dtfj-updatesite.zip

The Installation instructions could be found here as well  http://www.ibm.com/developerworks/java/jdk/tools/dtfj.html

after restart your MAT , you can open the phd file, and find your memory leaks.

more info:
Using the IBM DTFJ with the Eclipse Memory Analyzer Tool

enjoy
Yaniv Tzanany

How to generate and analyze websphere heap dump ?

If you need to generate and analyze websphere heap dump , here is the complete action you need to take.

1. There are many ways to generate heap dump , the next way looks like the easiest ( for me ) to generate manually the heap dump

• Start the wsadmin scripting client 
•  follow the procedure in this article "Generating heap dumps manually"

i used the next two commands in the wsadmin:
set objectName [$AdminControl queryNames WebSphere:type=JVM,process=server1,node=MYXXXNode01,*]

$AdminControl invoke $objectName generateHeapDump

2. To analyze the output - download two useful tools - to analyze heap dump :

• HeapRoots 
• HeapAnalyzer
• Eclipse Memory Analyzer Tool --> THE BEST --> you can read all about it in my post here Eclipse Memory Analyzer with phd files - IBM dump format 

to run heaproot i used:
java -jar HR207.jar "C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\heapdump.20100905.152441.6336.0001.phd"

command sample:
ts -100 ->Tabulating all objects (100), sorted by total-size
os -100 -> Showing all objects(100), sorted by size.
up -> move up with the results
down -> move down with the results (next chunk)
os -100 > tt.txt  -> redirect results to file tt.txt

to run heapanalyzer i used ( its failed to open large heap dump):
java -Xmx1000m -jar ha406.jar "C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\heapdump.20100905.152441.6336.0001.phd"

all commands tested on windows with websphere 7.0 , should be ok on linux platform.

reference:
Generating heap dumps manually
Solving memory problems in WebSphere applications
Webcast replay: Using IBM HeapAnalyzer to diagnose Java heap issues

enjoy
Yaniv T

WebSphere network deployment - cluster

although i didn't created such topology yet, but i am about to do it in the near future . in the mean while i looked for stuff regards this issue.
and i found many many many stuff.

here some useful links i found that its a good starting point(i might add some later - i am sure there are more)
Setting up a multinode environment
step by step -> Using WebSphere Application Server V5 for load balancing and failover.

session Management in cluster is very important here is a useful link.
IBM WebSphere Session Management



Yaniv T

WebSphere filter in version 6.1.0.0 Vs 6.1.0.17

The problem :
In Version 6.1.0.0 (before I set the path 17) , my web xml contains the next filter declaration
<filter>
<filter-name>WSConfigFilter</filter-name>
<filter-class>com.fis.infra.presentation.web.services.weblogic.filter.WSConfigFilter</filter-class>
<init-param>
<param-name>LoginWebService</param-name>
<param-value>GUIWebServices/services/LoginFacade?WSDL</param-value>
</init-param>
<init-param>
<param-name>PresentationWebService</param-name>
<param-value>GUIWebServices/services/PresentationFacade?WSDL</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>WSConfigFilter</filter-name>
<url-pattern>/Infrastructure/RTInfra/WS_Client/WSConfig.xml</url-pattern>
</filter-mapping>
We access to this file WSConfig.xml in the login ( maybe the first page/data from server) ,I would like to generate this file in the server.
On version 6.1.0.0 this filter get invoked as you ask this file , after I installed the patch (6.1.0.17) this filter is not invoked only after he found this page ( I create it manually ).

The Solution:
After digging in the web i came up with this problem from IBM PK33090; 6.1: A filter that serves a file does not popup an alert message
So you can follow the instruction how to add Webcontainer custom property , and add the relvant property to solved this issue:

1. In the administrative console, click "Servers" and under Servers click "Application Servers"
2. Click on the server to which the custom property is to be applied
3. Under "Configuration" and "Container settings" click "Web Container Settings" and under Web Container Settings click "Web Container"
4. Under "Configuration" and "Additional Properties" click "Custom Properties"
5. In the Custom Properties page, click "New"
6. “Name" = com.ibm.ws.webcontainer.invokefilterscompatibility “Value”= true .
7. Click "Apply" or "OK"
8. Click "Save" in the "Messages" box which appears
9. Restart the server for the custom property to take effect

and than i saw my filter get invoked as usual.

WebSphere tips

1. make sure you are using the latest java ibm version in your websphere application , its affect your application performance, you can find your ibm java version like this [websphereroot]/java/jre/java -fullversion

2. If you go to Application servers > server1 > Process Definition > Java Virtual Machine and checked the "Verbose garbage collection " check box , after restarting the server you can see all GC activities in server log directory under file native_stderr.log , to analyse this file you can download an IBM tool from here ->IBM Pattern Modeling and Analysis Tool for Java Garbage Collector

3. In the post i wrote before this one i mention how to get a full trace from your web sphere application , to analyse this trace you can use the next tool from IBM ->IBM Trace and Request Analyzer for WebSphere Application Server

4. To debug your deployed application on websphere follow the next steps:
in the admin console - Application servers > server1 > Process Definition > Java Virtual Machine checked the "Debug Mode " , by doing so the parameters that in the "Debug arguments" text box will be added to the server when restarting , usually the parameters looks like this "-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket, server=y,suspend=n,address=7777" , so after restarting your server open your Eclipse (in this case) and you just need to attach to a "remote java application" and put in the server name (where the websphere server is running ) and the port number you set/have from the address (i.e. 7777), and pray :)


5. very good article about java performance on AIX you can find here Maximizing Java performance on AIX

6. here are some WebSphere Tuning links
WebSphere Tuning Tips

WebSphere tuning for the impatient: How to get 80% of the performance improvement with 20% of the effort

Tuning performance

Java virtual machine settings

DB2 tuning parameters

Solving memory problems in WebSphere applications

Trace configuration for Web Sphere

Here are some instruction i get from IBM , to make a full trace to my application .
1) Trace the application flow from application server startup (for this you will require to setup the application and also WebSphere to use datasources).

Please use the following trace String:
*=info:com.ibm.ws.webservices.*=all:WAS.j2c=all:RRA=all:WAS.database=all:Messaging=all:JMSApi=all:Transaction=all

See instructions below for tracing setup:
1. In the Application Server Administrative Console, expand Troubleshooting and select Logs and Trace.

2. In the Logging and Tracing page, select your server and then Diagnostic Trace.

3. Ensure that Enable Log is selected.

4. Under Trace Output, select File, and accept the defaults.

5. Click OK and save your configuration.

6. Again, expand Troubleshooting and select Logs and Trace.

7. In the Logging and Tracing page, select your server and then Change Log Detail Levels.

8. Enter the following trace string:
*=info:com.ibm.ws.webservices.*=all:WAS.j2c=all:RRA=all:WAS.database=all:Messaging=all:JMSApi=all:Transaction=all

NOTE: Please ensure you have setup at least 10 historical files of at least 50 MB each to ensure the whole test is captured from startup.
..
you can see the trace.log file under your your log directory .

WebSphere usefull links for tips

Some useful links to a very common questions , while starting with IBM WebSphere Application server , that i get from IBM stuff

1. Web Sphere profiles / Servers
a. What is a profile , how to manage/create/control servers

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tpro_profiles.html

b. Control servers via Command line

You can explor the commands
under \installDir\Profiles\myProfileName\bin

For example, to start server1
through the command line I'm running the startserver server1 from the next
directory
C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\bin

c. Servers logs
\installDir\Profiles\myProfileName\logs\AppServerName

For example, the full path for
the log files under my profile is
C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\server1

d. Administration console.
To access the admin console:
Start->Programs->IBM WebSphere->Application
Server V6.1->profiles->profileName->Administrative Console

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/welcadminconsole.html

e. Is there a node manager.

The WebSphere ND (Network Deployment)
product enables you to manage nodes
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tagt_svr_conf_nodes.html

f. 1-N servers
in one profile and how to control each one .
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tpro_profiles.html

2. WEB Sphere File
architecture, main configuration file names.
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tcfg_data.html

3. Control the start-up
parameters (-DXXXX=YYYY ) , adding custom parameters.
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/trun_app_startup.html

4. Adding application
specific parameter (environment variable )
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tcws_variable.html

5. Supported JVM version – how to change the JVM version if needed.

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/urun_rconfproc_jvm.html

6. Eclipse and Web
sphere - how to debug deployed application

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/ttrb_debugwsa.html

7. Create Data source name (connection pooling)

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tdat_tccrtprovds.html

8. Performance tips and tricks

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/welc6toptuning.html

9. Deployment issues,
export web services via Web sphere .

10. Deploy software on
web sphere
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/trun_appl.html

11. Apache web With Web sphere integration.
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/twsv_plugin.html

I hope I wrote all the necessary things .