Smart Plug-in for WebLogic Server Release Notes

PRINTED DOCUMENTATION
The following manuals offer information that you need to install, configure, and use the WebLogic Server
SPI.
! HP OpenView SMART Plug-Ins for WebLogic Server: User's Guide
Part Number: B9145-90000
! HP OpenView SMART Plug-In for WebLogic Server: Reference
Part Number: B9145-90001
Chapter 2: Known Problems and Workarounds
! Problem: On Windows NT 4.0 managed nodes, WebLogic Server SPI programs fail to execute
successfully when the TEMP environment variable is not set in the OVO agent’s environment.
Workaround:
1 At the NT 4.0 managed node open the Control Panel→
→→
→System→
→→
→Environment tabbed dialog.
2 Add the TEMP environment variable to the System Variable list (this environment variable is usually set as a
User Variable, but is not set as a System Variable).
!
Problem: WebLogic Server SPI cannot locate and therefore is unable to monitor the WebLogic log
file.
The location and name of the WebLogic Server log file is specified in the WebLogic Administration
Console in the "Logging" tab on the server configuration page. If this log file is specified with a
relative path, this path is relative to the directory in which the WebLogic Server is started. The default
is the WebLogic home (WL_HOME) directory specified when the WebLogic SPI is configured. This
startup directory is specified in the startup scripts installed by BEA.
No means currently exists for querying the server for its startup directory. So, if the WebLogic Server
is started up in a directory other than WL_HOME and the log file is specified as a relative path, the
WLSSPI may not be able to locate and monitor the WebLogic Server log file.
Workaround: Ensure that WebLogic Server is started from the WL_HOME directory, which is the
default if you use the startup scripts provided by BEA. Also, note that the WLSSPI will not recognize a
fully qualified path name for the log file. You must use a relative path for the WebLogic Server log file
in order for it to be located and monitored by the WLSSPI.
! Problem: The Web browser cannot be launched from an operator action after you have correctly
configured the WLS-SPI as instructed in the WLS-SPI User's Guide, Chapter 2 “Configure the
Management Server to Launch your Web Browser.”
Workaround:
1 Stop and restart the agent from a user other than root by entering the following commands on the managed
node:
opcagt –kill