This page described the initial configuration of the plugin. You will probably need to go through this list before getting the plugin running the first time.

1. Place check_was, check_was-<version>.jar and check_was.profiles in the same directory (e.g. /opt/plugins/custom). This can be on any computer with TCP access to the server running WAS, or on the WAS server itself.
2. Make sure check_was is executable by your Nagios user.
3. Update check_was by setting the environment variables at the start of the script to the appropriate values for your server. JAVA_HOME must point to an IBM JRE/JDK. WAS_HOME needs to point to a directory that contains a directory named "runtimes" containing the following WAS libraries: com.ibm.ws.admin.client_<version>.jar and com.ibm.ws.webservices.thinclient_<version>.jar. If you run the plugin on the same server as WAS, WAS_HOME should point to the WAS install directory.
4. Edit check_was.servers. This file should contain the configuration to connect to your WAS server. For each server, the following properties should be provided:
5. <server alias>.hostname=<the hostname or IP of the WAS server>
6. <server alias>.port=<the port of the SOAP connector on the server, e.g. 8880>
7. <server alias>.username=<the admin user name>
8. <server alias>.password=<the admin password>
9. <server alias>.securityenabled=<true if security is enabled, false otherwise>
10. <server alias>.truststore=<the path to the keystore containing the certificated to be used for SSL. If you are running the plugin on your WAS server and use the default WAS keystores, this should point to etc/trust.p12 in your profile>
11. <server alias>.truststorepassword=<the password for the trust store>
12. <server alias>.keystore=<the path to the keystore containing the private key to be used for SSL. If you are running the plugin on your WAS server and use the default WAS keystores, this should point to etc/key.p12 in your profile>
13. <server alias>.keystorepassword=<the password for the key store>
14. You're done.