com/ibm/ws/sib/utils/ras/SibTr not found   

Hi,

The problem is the fact that the SIB Performance tool is really expecting a full WAS install rather than a cut down WID version.

The sibperf setup script expects to call WAS_HOME\bin\setupCmdLine.bat, which sets up the path correctly. This does not exist in the wid version and therefore your path is not setup. This results in a class not found exception.

Solutions?
1) The best option is to run with a full WAS server installation.
You can use a full WAS installed version to start the SIB Performance Tool and then use this to monitor the WAS (wid) server of interest. Note you should use a WAS602 server install to view WAS602 servers. Similarly, use a WAS61 server install to view WAS61 servers.

2) The other option would be to set the path for the WID server by hand (I have not tried this but it should work). The sibperf.bat scripts could be edited as follows:

In addtion to what you already have, add to the java execution line:

-Dcom.ibm.CORBA.ConfigURL=file:T:\wid_6.0.1\runtimes\base_v6_stub\profiles\default\properties\sas.client.props

-Dcom.ibm.SSL.ConfigURL=file:T:\wid_6.0.1\runtimes\base_v6_stub\profiles\default\properties\ssl.client.props

-Dcom.ibm.SOAP.ConfigURL=file:T:\wid_6.0.1\runtimes\base_v6_stub\profiles\default\properties\soap.client.props

Also, in the "set extdirs" of sibperf.bat add the following to those already defined:

T:\wid601\runtimes\base_v6_stub\java\lib;
T:\wid601\runtimes\base_v6_stub\lib;
T:\wid601\runtimes\base_v6_stub\installedChannels;
T:\wid601\runtimes\base_v6_stub\lib\ext;

That should ensure the correct classes are on the path. This would replicate the work done by the "setupCmdLine.bat" script (which is not present in wid).

If that does not work, then the best option is to use a full server install to start the SIB Performance Tool....that will work.

Thierry,

I notice that you are running WAS runtime within WID. The tool was written for a
full installation product rather than the WID install version. It may work but it
is not something I have tried (or really intended). Running against a full installation
product will fix the problem.

Alternatively, you can connect to a external server from WID - in which case you should
set the WAS_HOME to be the external server and it should work.

Finally, if you do wish to try with the WID internal version of WAS, it may just require
some minor changes to the path. You need to ensure that you set WAS_HOME correctly - the
path should contain the WAS plugins directories and bin directories. Specifically your error
demonstrates that you are missing com.ibm.ws.sib.utils_2.0.0.jar. This should be picked up
from WAS_HOME but you can add it by hand by editing the sibperf file and adding (to the
"set extdirs=" line) something similar to the following (depending upon the exact location):
T:\wid601\runtimes\bi_v6\plugins;
(this adds all the jars from that directory)

Hope that helps - if you do take the last option and it works could you possibly let the forum
know the outcome? Thanks.

David