WASWLM: WSCP quits working due to changing the bootstrap port.

Technote (FAQ)
Problem
How to configure WSCP to use a bootstrap port number other than 900.
Solution
The default WSCP utilizes port 900. If the port number is changed the bootstrapPort in admin.config file using the following line:

com.ibm.ejs.sm.adminServer.bootstrapPort=


WSCP will not automatically recognize the change in port number.

Resulting in following error:

com.ibm.ejs.sm.client.RepositoryOpException: Failed to create InitialContext : null at
com.ibm.ejs.sm.client.RepositoryOpException.<init>(RepositoryOpException .java:47)
at
com.ibm.ejs.sm.ejscp.ClientRepository.<init>(ClientRepository.java:150)
at
com.ibm.ejs.sm.ejscp.EjscpExtension.init(EjscpExtension.java:113)
at tcl.lang.JavaLoadCmd.cmdProc(JavaLoadCmd.java:129)

How to reconfigure WSCP to use the new bootstrap port number:

1. Create a new file .wscprc (please note there is a DOT in front) in user home directory.

Where is user home?

Assume my user name is "admin"


On a NT4.0 box c:\WINNT\Profiles\admin
On a Windows 2000 box c:\Documents and Settings\admin
On an AIX box The location you run as "root" which is usually /


2.Edit the .wscprc file to include

wscp.hostPort=<newport>

For more information on the .wscprc file, please check the following InfoCenter Document:

For 3.5.x:
http://www-4.ibm.com/software/webservers/appserv/doc/v35/ae/infocenter/was/atswcpus.html

For 4.0.x:
http://www-4.ibm.com/software/webservers/appserv/doc/v40/ae/infocenter/index.html
Section 6.6.0.2.2 WebSphere Control Program (wscp)

How to use -p option(Starting WSCP when using a port other than default port 900)

Please search DCF with following key words

wscp websphere port non-root was

How to Trace WSCP Client
Infocenter for 3.5 X Chapter 6.6.0.2.2.3.7: Tracing the administrative server, application servers, and the wscp client

1.Edit the .wsprc to include

wscp.traceString=com.ibm.ejs.sm.ejscp.*=all=enabled
wscp.traceString=com.ibm.ejs.sm.ejscp.commands.*=all=enabledwscp.traceString=com.ibm.ejs.sm.client.*=all=enabled

2.Start WSCP and send the errors to trace file

<was _root>\bin>wscp.bat >wscp.trace

<was _root>\bin>wscp -f <file name.tcl>>wscp.trace












Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Administrative Console (all non-scripting)
Operating system(s): Multi-Platform
Software version: 3.5, 4.0
Software edition: Advanced
Reference #: 1052547
IBM Group: Software Group
Modified date: 2002-05-21