Managed Server Monitoring tools for WLS 8.1 on linux

Question

Our organization uses a set of locally written shell scripts to monitor the status of the managed servers in a WLS 8.1 domain installed on RedHat Linux 4, update4.
The main monitoring script uses the output of the "ps" and "netstat" commands to determine the process-id, server name, and tcp ports used by each managed server.
It is able to determine the name of the managed server by parsing the value of the "-Dweblogic.Name" parameter from the command line of the java command that launches the jvm that represents the managed server.
When a managed server is started, the command line resembles the following:
java \
-DLotsofVariables \
-classpath LotsofCpElements \
-Djava.security.policy==PolicyFile \
-Dweblogic.Name=NameOfMgdServer
The maximum number of characters displayed by the "ps" command with the wide (-w) option is 4096.
A recent addition to the class path has increased the length of the command line, resulting in the "NameOfMgdServer" being truncated.
It now appears similar to the following:
java \
-DLotsofVariables \
-classpath LotsofCpElements \
-Djava.security.policy==PolicyFile \
-Dweblogic.Name=NameO
This breaks our monitoring script because it is looking for a managed server named "NameOfMgdServer", not "NameO".
Each managed server is monitored by the WLS administration server and the local node manager.
Is there a way to restructure or rewrite the command line used to launch the managed server java jvm such that the "-Dweblogic.Name=NameOfMgdServer" appears before the specification of the classpath?
I can find no mention of the "-Dweblogic.Name" parameter on the "Remote Start" tab corresponding to each managed server, so it appears that WLS is building the java command line internally based on the contents of the config.xml file, before launching the managed server process.
I've considered adding an additional parameter to the java command line preceding the specification of the classpath, simply to identify the identity of the managed server, but I don't like this type of hack.
Perhaps someone else has developed a similar monitoring tool, and could provide some advice?
Any feedback is appreciated

Answer 1

Our organization uses a set of locally written shell scripts to monitor the status of the managed servers in a WLS 8.1 domain installed on RedHat Linux 4, update4.
The main monitoring script uses the output of the "ps" and "netstat" commands to determine the process-id, server name, and tcp ports used by each managed server.
It is able to determine the name of the managed server by parsing the value of the "-Dweblogic.Name" parameter from the command line of the java command that launches the jvm that represents the managed server.
When a managed server is started, the command line resembles the following:
java \
-DLotsofVariables \
-classpath LotsofCpElements \
-Djava.security.policy==PolicyFile \
-Dweblogic.Name=NameOfMgdServer
The maximum number of characters displayed by the "ps" command with the wide (-w) option is 4096.
A recent addition to the class path has increased the length of the command line, resulting in the "NameOfMgdServer" being truncated.
It now appears similar to the following:
java \
-DLotsofVariables \
-classpath LotsofCpElements \
-Djava.security.policy==PolicyFile \
-Dweblogic.Name=NameO
This breaks our monitoring script because it is looking for a managed server named "NameOfMgdServer", not "NameO".
Each managed server is monitored by the WLS administration server and the local node manager.
Is there a way to restructure or rewrite the command line used to launch the managed server java jvm such that the "-Dweblogic.Name=NameOfMgdServer" appears before the specification of the classpath?
I can find no mention of the "-Dweblogic.Name" parameter on the "Remote Start" tab corresponding to each managed server, so it appears that WLS is building the java command line internally based on the contents of the config.xml file, before launching the managed server process.
I've considered adding an additional parameter to the java command line preceding the specification of the classpath, simply to identify the identity of the managed server, but I don't like this type of hack.
Perhaps someone else has developed a similar monitoring tool, and could provide some advice?
Any feedback is appreciated