Optimize 10.3.0 | webMethods Optimize Documentation | Administering webMethods Optimize | For System Administrators | Discovering Assets and Monitoring Components | Discovering Assets | The Discovery Page | Adding MashZone NextGen Server Assets for Discovery
 
Adding MashZone NextGen Server Assets for Discovery
In order to monitor MashZone NextGen TomEE server component types, prior to discovering the MashZone NextGen assets, update the Software AG_directory \MashZone NextGen\apache-tomee-jaxrs\bin\startup.bat/sh script with the following:
*Add Catalina variables to enable JMX:On Windows, before the call "%EXECUTABLE%" start %CMD_LINE_ARGS% command:
Dcom.sun.management.jmxremote=true�
set CATALINA _OPTS=%CATALINA_OPTS% -Dcom.sun.management.jmxremote.port=8088�
set CATALINA_OPTS=%CATALINA_OPTS% -Dcom.sun.management.jmxremote.ssl=false�
set CATALINA_OPTS=%CATALINA_OPTS%
-Dcom.sun.management.jmxremote.authenticate=false�
rem ### Use actual ip if below doesn't work
set CATALINA_OPTS=%CATALINA_OPTS% -Djava.rmi.server.hostname=host
or IP
set CATALINA_OPTS=%CATALINA_OPTS% -Djava.rmi.server.useLocalHostname=true
And on UNIX before the exec "$PRGDIR"/"$EXECUTABLE" start "$@" command:
export CATALINA_OPTS="${CATALINA_OPTS}
-Dcom.sun.management.jmxremote=true"
export CATALINA_OPTS="${CATALINA_OPTS}
-Dcom.sun.management.jmxremote.port=8088"
export CATALINA_OPTS="${CATALINA_OPTS}
-Dcom.sun.management.jmxremote.ssl=false"
export CATALINA_OPTS="${CATALINA_OPTS}
-Dcom.sun.management.jmxremote.authenticate=false"
### Use actual ip if below doesn't work
export CATALINA_OPTS="${CATALINA_OPTS}
-Djava.rmi.server.hostname=host or IP"export
CATALINA_OPTS="${CATALINA_OPTS}
-Djava.rmi.server.useLocalHostname=true"
*Add JMX variables:
-Dcom.sun.management.jmxremote=true
-Dcom.sun.management.jmxremote.rmi.port=port
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Djava.rmi.server.hostname=host_name
-Djava.rmi.server.useLocalHostname=true
Important:
If you are monitoring MashZone NextGen Universal Messaging server component types, and they are missing after the discovery of MashZone NextGen assets, check the Infrastructure Data Collector error.log file available at Software AG_directory \profiles\InfraDC\logs for an error message, telling you that the MashZone NextGen Universal Messaging realm lacks the proper privileges. Add the required privileges, and rediscover the MashZone NextGen Universal Messaging component type assets.
*To add MashZone NextGen server assets for discovery
1. In My webMethods: Navigate > Applications > Administration > Analytics > Infrastructure Components > Discovery
2. Click Add Asset.
The Add Asset Discovery dialog is displayed.
3. Populate the fields (required fields are identified with *).
The following table describes the fields in the Add Asset Discovery dialog.
Field
Description
*Asset Type
Select the type of asset (MashZone NextGen) to discover.
*Data Collector
Select the Infrastructure Data Collector to use for the discovery.
*Host
Enter the host name or IP address for the MashZone NextGen Server. The name must be unique.
*Port
Enter the port number for the applicable MashZone NextGen Server.
*Username
User ID needed to log in to the asset.
*Password
Password needed to log in to the asset.
4. Click OK to add the specified asset, or click Cancel if you want to cancel the procedure without adding the asset discovery.