In the WebLogic Server/Portal 10 Administration Console, expand the Servers node.
Select the node for the server you want to manage with Node Manager.
Configure the agent classpath in Node Manager:
In the Administration Console, select the Configuration tab.
Select the Server Start tab.
Locate the agent classpath for the specific Managed Server as found in setAgentEnv_sever-instance.sh.
Add the agent classpath to the following classpath text field:
${CLASSPATH}:PolicyAgent-base/lib/agent.jar:PolicyAgent-base/ lib/openssoclientsdk.jar:PolicyAgent-base/locale:PolicyAgent-base/ AgentInstance/config
where AgentInstance represents the agent instance directory, such as Agent_001.
To avoid typing errors, copy and paste the agent classpath entries from the setAgentEnv_managed-sever-instance.sh file.
managed-server-instance is the name of the Managed Server instance. For example, server1.
To the same classpath text field referred to in the previous step, prepend the following classpath entries:
DeployContainer-base/BEA-Java-Home/lib/tools.jar: DeployContainer-base/wlserver_10.0/server/lib/weblogic.jar
DeployContainer-base is the directory in whichWebLogic Server/Portal 10 was installed.
BEA-Java-Home is the directory that contains the JDK for theWebLogic Server/Portal 10 instance.
Click Save.
Click Activate Changes.
Configure the agent Java options in Server Start.
In the WebLogic Server/Portal 10 Administration Console, select the Configuration tab.
Select the Server Start tab.
Locate the Java options as found in setAgentEnv_sever-instance .sh for the specific Managed Server.
Add the Java options to the Arguments text field as follows:
-Djava.util.logging.config.file=PolicyAgent-base/config/ OpenSSOAgentLogConfig.properties -DLOG_COMPATMODE=Off
To avoid typing errors, copy and paste the agent Java option entries from the setAgentEnv_managed-sever-instance.sh file.
Click Save.
Click Activate Changes.