IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Table for WebLogic/WebLogic Portal server startup script locations - J2EE Agent


WebLogic/WebLogic Portal Server startup scripts locations

Server Type \ Startup Method start from command line start as a Windows service
Standalone / Admin WebLogic Server WebLogic 8 <wl_domain>/startWebLogic.cmd(sh) <wl_domain> /installService.cmd
WebLogic Portal Server 8
WebLogic 9 <wl_domain>/bin/startWebLogic.cmd(sh) Not Applicable
Managed WebLogic Server WebLogic 8 <wl_domain>/startManagedWebLogic.cmd(sh) <wl_domain>/installService.cmd
WebLogic Portal Server 8
WebLogic 9 <wl_domain>/bin/startWebLogic.cmd(sh) Not Applicable

For Managed WebLogic/WebLogic Portal Server started from the Node Manager, those files were changed after configuration. To update the PATH/LD_LIBRARY_PATH/LIBPATH/SHLIB_PATH environment variable, use one of the following commands:

<WL_HOME>/server/bin/startNodeManager.cmd(sh)
<WL_HOME>/server/bin/installNodeMgrSvc.cmd(sh)
<WL_HOME>/common/bin/commEnv.cmd(sh)

The server specific startup arguments and the classpath are saved in the config.xml file on the domain admin server.

For users that start Node Manager from command line, restart the Node Manager before start the managed server.

For users that start Node Manager as windows service, reinstall the Node Manager Windows service by running uninstallNodeMgrSvc.cmd and installNodeMgrSvc.cmd.

For WebLogic 9 users that start Node Manager from WebLogic Script Tool, first stop Node Manager and exit the WebLogic Script Tool, then re-run setWLSEnv.cmd(sh) for the changed environment to work. Then, start Node Manager from the WebLogic Script Tool again.

<wl_domain> is the directory where you have the domain admin server of WebLogic/WebLogic Portal Server installed.

For users who start the WebLogic/WebLogic Portal Server as a Windows service, remember to re-install Windows service.


Parent topic:

Configure the J2EE data collector for WebLogic/WebLogic Portal Server