Please ensure that the jdk version of the J2EE Engine VM is version 1.5 and above (Tested JVM vendors are oracle and SAP). JVM version of the instance can be checked using the system information application as shown in the system information screenshots below.
Two ways to do this :
I. Through the 'System Information' web application using a browser (preferred)
II. Using config tool
Using System Information
1.) Open the default Netweaver AS JAVA landing page as shown below. Please click on the System Information link (highlighted below)
|
|
|
|
Please login to the system information application using administrator or j2ee_admin credentials
Select the Netweaver AS JAVA instance a.k.a J2EE Engine Instance to be monitored as show. Please verify that the version is atleast 1.5 and above. Click on 'VM System Parameters' link to display/modify VM system parameters for this instance.
2.)
Please check the 3 JMX related system VM parameters to be enabled shown above. The full name of the first parameter is com.sun.management.jmxremote.authenticate as shown in the tool tip. All these 3 parameters should be in enabled state as shown in the 'enabled' column. Please set an appropriate and available port value for the JMX remote port by selecting the parameter and clicking the modify button as shown.
3.)
The javax.management.builder.initial VM parameter should be selected and disabled as shown.
4.) The J2EE Engine should be restarted for these changes to take effect
Using ConfigTool
Open a command prompt. To start Config tool :
WINDOWS
- go to <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory.
- Type configtool.bat
UNIX / LINUX
- go to <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory.
- Type ./configtool.sh
1. Add the following VM options in the corresponding Instance (as shown in the screen shots)
com.sun.management.jmxremote.port=<<JMX_PORT>>
com.sun.management.jmxremote.ssl=false
com.sun.management.jmxremote.authenticate=false
2. Disable the following VM options , if exists
Javax.management.builder.initial=com.sap.pj.jmx.server.interceptor.InterceptorChainBuilder
3. Save the changes and close the ConfigTool
4. Start the SAP Server
Please check with Jconsole, to test JMX Connection is enabled or not. Default values for the service url to be specified in Jconsole remote monitoring is as shown below. Please also provide the administrator or j2ee_admin credentials
service:jmx:rmi:///jndi/rmi://IP or hostname of the engine:jmx remote port configured/jmxrmi
Jar files needed to monitor the J2EE Engine:
For later netweaver versions (7.3 and above), here are the 4 jar files needed :
1.) sap.com~tc~bl~pj_jmx~Impl.jar
This could be found in: <SID>\<instance name>\j2ee\cluster\bin\ext\tc~jmx\lib\private\.
For example C:\usr\sap\SP1\J01\j2ee\cluster\bin\ext\tc~jmx\lib\private\sap.com~tc~bl~pj_jmx~Impl.jar
Please rename this as com_sap_pj_jmx.jar and copy this to the agent's egurkha\lib folder.
The remaining 3 jar files mentioned below can be found in: <SID>\<instance ID>\j2ee\j2eeclient\.For example: C:\SAP\JP1\JC00\j2ee\j2eeclient.
sap.com~tc~je~clientlib~impl.jar
Please rename this to sapj2eeclient.jar and copy this to the agent's egurkha\lib folder
sap.com~tc~exception~impl.jar
Please rename this to exception.jar and copy this to the agent's egurkha\lib folder
sap.com~tc~logging~java~impl.jar
Please rename this to logging.jar and copy this to the agent's egurkha\lib folder
Older versions of the J2EE Engine also use 4 jar files but the jar files already have the names that we expect. Please copy these as is to the agent's egurkha\lib directory
com_sap_pj_jmx.jar should be in \usr\sap\<instance name>\<instance>\j2ee\admin\lib
sapj2eeclient.jar should be in \usr\sap\<instance name>\<instance>\j2ee\j2eeclient
exception.jar should also be in \usr\sap\<instance name>\<instance>\j2ee\j2eeclient
logging.jar should also be in \usr\sap\<instance name>\<instance>\j2ee\j2eeclient