Contact Us
How you can contact us:

SAP NetWeaver Application Server Java

This page explains how to prepare a SAP NetWeaver Application Server Java managed system for the execution of the Simple System Integration

Currently the following monitoring application are supported for SAP NetWeaver Application Server Java systems:

Preparations in the Managed System

Preparation Tool (optional)In order to automate certain tasks, you can use the Preparation Tool
Run Outside Discovery on the Host

As prerequisites, you shall install the SAP Host Agent and run Outside Discovery as described

in Preparing Outside Discovery page.

Install SAP NetWeaver JavaInstall the latest SAP NetWeaver version from

Change the Default Profile

The Default profile needs to be updated with sapadm user to allow the communication between the Simple Diagnostics Agent and the Managed System.

Add the following line to profile DEFAULT.PFL:  service/admin_users = sapadm

Multiple users (e.g. daaadm, dazadm) must be separated by space.

Note: Can be automated by OS scripts

Check if an SLDR is neededAs prerequisites, you need to choose, according to your landscape, if an SLDR is required
see Preparing System Landscape Data Router page.
Implement SAP Note for the License Management InformationImplement SAP Note 1983424 - Extension of AS JAVA SLD Data Supplier, so that the License Management information are reported into LMDB

Configure JAVA Data Supplier (J2EESystem)

Use NetWeaver Admin for NetWeaver 71 and higher Use Visual Administrator for NetWeaver 7.0.x)

Manual Operations

Check the Data Supplier Configuration documentation: 

  • For NetWeaver 7.1 and above
  • For NetWeaver 7.0

Note: Make sure you use an URL like http://<host>:<HTTP port>/sld/ds as target of the data supplier.

Automation can be achieved Here.

Configure SAP Start Service Data Supplier

Configure this service to send the payload of all instances:

  • BCControllInstance: SAP Start Service Instance for each instances.
  • CentralserviceInstanceKernel: SAP Central Technical Instance: SAP Central Technical Instance
  • J2EEInstanceKernel Payload: SAP Netweaver Java Technical Instances for each instances.

Run as <sid>adm /usr/sap/<SID>/SCS<InstNbr>/exe/sldreg -configure /usr/sap/<SID>/SYS/global/slddest.cfg -usekeyfile

Specify the HTTP connect information: [User, Password, Host, Port, HTTP/HTTPS] Of the SAP Focused Run SLDR or SAP Solution Manager SLD

Note: SECUDIR must point to directory containing client PSE and credentials (for more information check the respective SAP Help).

Restart the sapstartsrv sapcontrol -nr <Instance Number> -function RestartService 

Note: The Service needs to be restarted for all instances of the system.

Check logs and XML /usr/sap/<SID>/<Instance>/work/ and /usr/sap/<SID>/J*<Instance Number>/work/  if the dev_sldregk, dev_sldregs, dev_krnlreg and sapstartsrv_sld.xml are correctly generated

Check HTTP response: Success. HTTP status code: 200.

Create SDAGENTJ User

User to authenticate local HTTP and P4 calls by the simple Diagnostics Agent for data collection

Create SDAGENTJ user with required roles as described in Security Guide.
Install BCI Adapter to collect performance metrics and trace data of the NW Java

Check the BCIA compatibility version on the Managed Systems Preparation and Maintenance Guide page.

Install the CA APM Byte Code Injection Agent (CA APM BCIA), as described in the CA APM release relevant SAP Setup Guides available here: CA APM Introscope Page, following the chapter entitled: Manual Installation of the Introscope Agent. 

Automation of the distribution of the BCI Adapter software can be achieved with OS scripts (copy the BCI SW in central DIR_EXE), which adapts the instance profile with an additional command for sapcpe.

Configure the BCI Adapter for each Instance

The following example can be used to configure the BCI Adapter for each Instance. The full Process is described here:

Note: since Netweaver 7.10 the Java startup parameters have to be set for each instance (and not for each server node). 

Set the parameter for the startup of the BCI Adapter in the java startup profile:

  • Check Authorizations on the ByteCodeAgent Directory: /usr/sap/<SID>/J<Inst>/ByteCodeAgent:

-the folder must belongs to <SID>adm:sapsys. If not, execute the command: chown -R <SID>adm:sapsys ByteCodeAgent
-the folder must have read/write/exe authorizations (drxrwxr-w), sapsys must have write authorizations.

  • Execute the Configuration with
    • NetWeaver Administration (nwa) or
    • configtool or
    • console config
  • Set System VM Parameter
    Examples show Unix notation for parameters having path values - adapt for Windows accordingly.
    When copying the below parameters, make sure to remove superfluous spaces.

    • -Dcom.wily.introscope.agent.agentName= ${SYSTEM_NAME}_${INSTANCE_NAME}_$[elem/Name]
    • -Dcom.wily.introscope.agentProfile= /usr/sap/${SYSTEM_NAME}/${INSTANCE_NAME} /ByteCodeAgent/core/config/IntroscopeAgent.profile
    • -Dintroscope.agent.hostName=${INSTANCE_HOST}

You can set this parameter as above and the SAP J2EE engine will replace the variables.

  • Set VM Additional Parameters
    Examples show Unix notation for parameters having path values - adapt for Windows accordingly.

    • -javaagent:/usr/sap/<SID>/<INSTANCE_NAME>/ByteCodeAgent/Agent.jar   (Value is Empty)

Please replace <SID>/<INSTANCE_NAME>  with your real values the SAP J2EE engine does not replace variables set in parameter names

  • The parameter change, require a Java stack Restart
  • Check if the BCI Agent Java Startup Parameters are set correctly:
    • At CA APM level, check the results at http://<host>:8081/webview
    • At OS level, check /usr/sap/<SID>/J<Inst>/work/dev_serverX  the active parameter
Check LMDB

From the LMDB (Technical System view), check the last data changes from the data supplier.

Check the Software / Product Instance and Software Component Version sections, to see what has been reported by the Data Supplier.

CTC config store servlet must be installedNeeded for checking EnableInvokerServletGlobally = false and UME setting (Configuration and Security Analytics). In certain NW Java versions, this CTC servlet was not part of the default delivery. In this case, it also needs to be deployed. Find details in SAP Note 635099 - CCDB CTC Extractor – Prerequisites
Edit Configuration in Simple System Integration

FRUN 2.0 <= FP03, enter values for the following parameters:

  • Monitoring User (the above mentioned SDAGENTJ or a comparable user)
  • Monitoring Password

FRUN 3.0 >= SP00, enter values for the following parameters:

  • Monitoring User (the above mentioned SDAGENTJ or a comparable user)
  • Monitoring Password
  • Communication Mode (set the required combination of HTTP(S)/P4(S) protocols)
  • HTTP(S) Port (used for all hosts)
  • P4(S) Port (used for all hosts)
  • Configuration per Host (to use different port numbers for different hosts)