IBM®
Skip to main content
    United States change      Terms of use
 
 
Select a scope:    
     Home      Products      Services & industry solutions      Support & downloads      My account     
alphaWorks  >  Java technology  >  

Class Finder Toolkit for Websphere Application Server

Two command line tools for determining all the run-time JARs, zip files, and directories for a given class inside WebSphere Application Server.


Date Posted: May 6, 2004
Overview Requirements DownloadFAQsForum Reviews

1. Why can't you make Class Finder Toolkit independent of the WAS installation?
2. What are the common SOAP ports used by WAS?
3. For dcl, what if WAS Security is enabled?


1. Why can't you make Class Finder Toolkit independent of the WAS installation?

Class Finder Toolkit relies on WAS features that are internal to WAS. Dependencies such as JARs, WAS security configuration, etc., make it hard to upgrade in the future.
Back to top Back to top

2. What are the common SOAP ports used by WAS?

8879 for ND, 8880 for Base. You can look it up from WAS admin console. For ND, it can be found under System Administration/Deployment Manger/End Points/SOAP_CONNECTOR_ADDRESS.
Back to top Back to top

3. For dcl, what if WAS Security is enabled?

In order for dcl to work when WAS Security is enabled, the local WAS version has to be on the same or above fix pack level as that of the remote WAS. For instance, if you have a 5.0.2.3 installed on the remote WAS, then you need to install 5.0.2.3 or above.

Under $WAS_HOME/properties/soap.client.props, update the following lines:

    com.ibm.SOAP.securityEnabled=true
    com.ibm.SOAP.loginUserid="id goes here"
    com.ibm.SOAP.loginPassword="pwd goes here"
Back to top Back to top
Download now Download now

Related technologies

For platform(s):
Windows, Java, UNIX

For topics:
MBean, Websphere Application Server


Related resources

WebSphere Application Server zone

developerWorks Java technology zone

IBM Systems Journal

 

    About IBM Privacy Contact