GW Agent for Weblogic

This page reviews the GroundWork JDMA for Weblogic.

Deploying GroundWork Agent for Weblogic

JDMA Software - All of the JDMA and associated files needed for installation are included with GroundWork Monitor 6.2 and later. They are stored in /usr/local/groundwork/apache2/htdocs/java-agents/, and may be downloaded via HTTP.

Prerequisites

The following should be installed and running:

Configuration Steps for Weblogic

1. Set up encryption [Optional]: GroundWork servers are set to receive NSCA messages unencrypted with XOR obfuscation by default. If you want to change this default, you can do so with the following procedure. Triple-DES is currently the only encryption method supported by the Java agent.

   Any other process that sends NSCA messages to this GroundWork server, such as GDMA or a child server, will be affected, and may also need to have its configuration adjusted.

   • On the GroundWork server, edit the file:

     /usr/local/groundwork/config/bronx.cfg

     Change the line:

     #listener_encryption_method=1

     to

     listener_encryption_method=3

   • Restart the Nagios process:

     /etc/init.d/groundwork restart nagios

2. Download the file gwos-wls-monitoringAgent.war located on the GroundWork server in the folder:

   /usr/local/groundwork/apache2/htdocs/java-agents/

3. Deploy the war file to the folder:

   <WEBLOGIC_INSTALL_DIRECTORY>/wlserver_10.3/samples/domains/wl_server/autodeploy/

Exporting Profiles to the GroundWork Server

To monitor components for your environment you need to generate environment based custom configuration files. To generate the custom files;

1. Visit http://<weblogic server>: 7001/gwos-wls-monitoringAgent/index.html, and select Start New Configuration.
2. Enter the Weblogic connection settings:
   • Make sure the nagios_encryption setting matches the listener_encryption_method and nagios_password setting matches the listener_password that you set in the bronx.cfg file.

     Only XOR and Triple-DES encryption are supported.

     Also, no encryption is supported.

3. Select the mbean attributes from the list. Provide an alias, warning and critical values. The agent communicates to the GroundWork server with an alias only. Define a value that is understandable and unique if the default alias is too long. Click Next.
4. Fill out the GroundWork server name and login details:
   • Specify the classpath to copy the new properties file:

     <WEBLOGIC_INSTALL_DIRECTORY>/wlserver_10.3/samples/server/examples/build/serverclasses

   • Click Export.
   • Enter the GroundWork server name, username and password and select Export. The old gwos_properties file is backed up with the name gwos_weblogic.xml_old.backup. This exports the profiles to the GroundWork server.
5. On your GroundWork server login as an administrator and go to Configuration and import the file service-profile-weblogic.xml.
   • If you have exported multiple weblogic profiles, you would see multiple profile names like service-profile-weblogic_1.xml, service-profile-weblogic_2.xml. The higher suffix is the latest export.
   • Next, create or assign these services to a host and Commit.
6. On your weblogic server, touch the following file using the touch command:

   <WEBLOGIC_INSTALL_DIRECTORY>/wlserver_10.3/samples/domains/wl_server/autodeploy/gwos-wls-monitoringAgent.war

   • This will reload and restart the application.
   • You should see the GWOS MBean Collector started successfully message in the gwosCollector.log file. Also you will see the passive check results in the nagios.log file on your GroundWork server.