Troubleshooting
Problem
Enabling Agent & Integration Servers to work with Global Security
Symptom
How does one get our agents and Integration Servers to work with Global security?What parameters/modifications etc.required?
Cause
Resolving The Problem
1. In the Agents classpath ensure that the appropriate properties folder is
included
%WAS_HOME%\AppServer\properties
or
%WAS_HOME%\AppServer\profiles\<PROFILE_NAME>\properties. (in 6.0 if a
profile is specified)
or
%WAS_CLIENT_HOME%\AppServer\properties (if
using a AppClient and not a full AppServer installed on the
boxes)
.
2. Modify the SAS properties (sas.client.props) file from
the WebSphere installation to contain the username and
password to be used
for authentication to the WebSphere (corbaloc based) JNDI. The file is located
in the
%WAS_HOME%\AppServer\properties ( In
%WAS_HOME%\AppServer\profiles\<PROFILE_NAME>\properties in 6.0)
The
relevant parameters that are to be modified are -
com.ibm.CORBA.loginSource=properties (default is prompt which means you
have to key in the passwd each time you startup an
agent)
com.ibm.CORBA.securityEnabled=true
com.ibm.CORBA.loginUserid=<jndis
ecurityuser>
com.ibm.CORBA.loginPassword=<jndisecuritypasswd>
3.
Specify the following java parameter to the agent startup command to leverage
this
file
-Dcom.ibm.CORBA.ConfigURL=%WAS_HOME%/AppServer/properties/sas.client.pro
ps.
Now, agents should work correctly and startup without errors and
register on the WAS JNDI.
The following is not used/required by Yantra
agents on WAS but recommended (primarily for WLS)
4. If using the App
Client,
a. additionally source the following setyup files in
.
${WAS_CLIENT_HOME}/bin/setupClient.sh
.
${WAS_CLIENT_HOME}/bin/setupCmdLine.sh
b. set the CLIENT_OPT variable
as
export
CLIENT_OPT=-Djava.ext.dirs=${WAS_EXT_DIRS}:${WAS_CLIENT_HOME}/plugins:${WAS_CLIE
NT_HOME}/java/jre/lib/ext:${WAS_CLIENT_HOME}/java/jre/lib
c. Pass that
to the startup java command line as
${JAVA_HOME}/bin/java ${CLIENT_OPT}
-D....
5. In the agents' management.propeties, uncomment and set the
following
-
yfsjndi.jmx.java.naming.security.principal=<jndisecurityuser>
yfsjndi.jm
x.java.naming.security.credentials=<jndisecuritypasswd>
Historical Number
PRI49752
Product Synonym
[<p><b>]Fact[</b><p>];
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21527552