|
Problem |
Many of our scripts like XMLConfig and wscp use
sas.client.props by default and sas.client.props has security enabled by
default. This results in some exception messages when these scripts are
used with security disabled on the server. In WebSphere® Application
Server V3.5, wscp did not use sas.client.props by default. |
|
Cause |
Many scripts shipped with WebSphere Application Server,
such as XMLConfig and wscp, use sas.client.props by default and
sas.client.props has security enabled by default. This results in
some exception messages when these scripts are used with security disabled
on the server. In V3.5, wscp did not use sas.client.props by default. |
|
Solution |
The following message is displayed when running scripts
based on XMLConfig and wscp. Sometimes, the scripts may even hang.
1> [2002-04-03 15:14:21.312], [ServerID: -1],
[SecurityTaggedComponentAssistorImpl.register]:
JSAS0026E: Exception connecting object to the
ORB. Check
the sas.server.props file to ensure that the SSL keyStore and
trustStore properties are set properly. If the problem
persists, contact support for assistance.
Solution
The easiest solution is to disable security in sas.client.props by
replacing:
com.ibm.CORBA.securityEnabled=true
with
com.ibm.CORBA.securityEnabled=false
To selectively disable security for some scripts:
- Create a copy of the setupCmdLine.sh or
setupCmdLine.bat script as backup
- Modify references to CLIENTSAS, WSCPCLIENTSAS and other defined
variables in setupCmdLine.sh or setupCmdLine.bat
- Verify the updated script calls setupCmdLine.sh or
setupCmdLine.bat
|
|
|
|
|
|
|