SAP NetWeaver Application Server Java
As prerequisites, you shall install the SAP Host Agent and run Outside Discovery as described in page Preparing Outside Discovery.
Install SAP NetWeaver Java
Focused Run for SAP Solution Manager supports the latest SAP NetWeaver version
Manual Operations
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.
Manual Operation ( can be automated by OS scripts)
Add the following line to profile DEFAULT.PFL: service/admin_users = sapadm
Multiple users (e.g. daaadm, dazadm) must be separated by space.
Manual Operations
As prerequisites, you need to choose, according to your landscape, if an SLDR is required see page Preparing System Landscape Data Router.
Manual Operations
Implement SAP Note 983424 — Extension of AS JAVA SLD Data Supplier, so that the Licence Management information are reported into LMDB
Use Netweaver Admin for Netweaver 71 and higher Use Visual Administrator for Netweaver 7.0.x)
Check the Data Supplier Configuration documentation:
For Netweaver 7.1 and above
For Netweaver 7.0
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.
Manual Operations
- Run as adm /usr/sap//SCS/exe/sldreg -configure /usr/sap//SYS/global/slddest.cfg -usekeyfile As well execute the following on all ABAP Instances: /usr/sap//J*/exe/sldreg -configure /usr/sap//SYS/global/slddest.cfg -usekeyfile
- Specify the HTTP connect information: [User, Password, Host, Port, HTTP/HTTPS] Of the Focused Run SLDR or Solution Manager SLD
Note: When specifying an HTTPS port, make sure that the OS environment variable SECUDIR is defined for theadm OS user. - Restart the sapstartsrv sapcontrol -nr -function RestartService
- Check logs and XML /usr/sap//SCS/work/ and /usr/sap//J*/work/ if the dev_sldregk, dev_sldregs, dev_krnlreg and sapstartsrv_sld.xml are correctly generated
- Check HTTP response: Success. HTTP status code: 200.
User to authenticate local HTTP and P4 calls by the simple Diagnostics Agent for data collection
Manual Operations
Create SDAGENTJ user with required roles as described in the Focused Run Security Guide.
Install BCI Adapter to collect performance metrics and trace data of the NW Java
Check the BCIA compatibility version here: How to Proceed — Read Me First
Install the CA APM Byte Code Injection Agent (CA APM BCIA), as described in the CA APM release relevant SAP Setup Guides available here: RCA_Introscope_Home, 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.
Manual Operations
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).
S et the parameter for the startup of the BCI Adapter in the java startup profile:
- Check Authorizations on the ByteCodeAgent Directory: /usr/sap//J/ByteCodeAgent:
- the folder must belongs to adm:sapsys. If not, execute the command: chown -R adm:sapsys ByteCodeAgent
- the folder must have read/write/exe authorizations ( drxrwxr-w), sapsys must have write authorizations.
- Logon as adm and cd to /usr/sap//J/j2ee/configtool
- Start consoleconfig.sh
- Select Your choice: 7 (Instance where you want to set the Java Parameters).
- Select Your choice: 11 (VM Parameters) and Confirm that you want to use Vendor and Platform by default
- Select Your choise: 14 (Get the VM System Parameters info)
- Read the «Custom Properties» section and check:
-
- com.wily.introscope.agent.agentName=$_$_$[elem/Name]
- com.wily.introscope.agentProfile/usr/sap/$/$/ByteCodeAgent/core/config/IntroscopeAgent.profile
- introscope.agent.hostName = $
- In case, one of the parameter above is missing or different, select Your choice:
- 15 (Edit the VM System Parameters info)
- or 16 (Add the VM System Parameters info). Note «Enter Description» is optional.
- Select Your choise: 18 (Get VM Additionnal System Parameters info)
- Read the «Custom Properties» section and check the the following:
«-javaagent:/usr/sap/$_$/ByteCodeAgent/Agent.jar = » («Enter Value» field is Empty) - If the Additional Prameter was not set properly, please use «D» for deletion, apply, then 19 (Add VM Sys Param info).
- After parameter update, select your choice: 3 (Apply Changes).
- Log on to the Java Netweaver Administration in the Configuration / Infrastructure / Java System Properties section
In «System VM Parameters» Tab and «Additional VM Parameters» Tab and check parameters correctness. - At OS level, check /usr/sap//J/j2ee/cluster/instance.properties
- At CA APM level, check the results at http://:8081/webview
Manual Operations
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.
Manual Operations
Needed 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
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
As prerequisites, you shall install the SAP Host Agent and run Outside Discovery as described
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
Configure JAVA Data Supplier (J2EESystem)
Use NetWeaver Admin for NetWeaver 71 and higher Use Visual Administrator for NetWeaver 7.0.x)
Check the Data Supplier Configuration documentation:
Note: Make sure you use an URL like http://:/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 adm /usr/sap//SCS/exe/sldreg -configure /usr/sap//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 -function RestartService
Note: The Service needs to be restarted for all instances of the system.
Check logs and XML /usr/sap///work/ and /usr/sap//J*/work/ if the dev_sldregk, dev_sldregs, dev_krnlreg and sapstartsrv_sld.xml are correctly generated
Check HTTP response: Success. HTTP status code: 200.
User to authenticate local HTTP and P4 calls by the simple Diagnostics Agent for data collection
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.
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:
-the folder must belongs to adm:sapsys. If not, execute the command: chown -R 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
- -Dcom.wily.introscope.agent.agentName= $_$_$[elem/Name]
- -Dcom.wily.introscope.agentProfile= /usr/sap/$/$ /ByteCodeAgent/core/config/IntroscopeAgent.profile
- -Dintroscope.agent.hostName=$
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.Please replace / 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://:8081/webview
- At OS level, check /usr/sap//J/work/dev_serverX the active parameter
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.
- 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)
Sap netweaver application server java
A pure Java system provides a Java™ 2 Enterprise Edition (Java EE) 1.6 compliant-environment for developing and running Java EE programs. With this installation you can run Java EE applications but not ABAP programs.
The design of SAP NetWeaver Application Server is aimed at providing an exceptionally high level of robustness and supportability for the applications running on it. The architecture of SAP NetWeaver Application Server Java and basic terminology are explained below. For details, you should refer to the component-specific documentation.
Instances of SAP NetWeaver Application Server Java
An SAP NetWeaver Application Server Java system has various instances. An instance is an administrative unit containing various components of an SAP system. The components of an instance are parameterized in a shared instance profile. Each instance is identified by a system ID and an instance number.
A distinction is made between application server instances and system central services instances (SCS instances).
There can be any number of application server instances in an SAP NetWeaver Java. The instances process incoming user requests. A Java application server instance contains one Internet Communication Manager, one SAP start service, and any number of Java server processes.
As well as multiple application server instances, there is one special instance that contains the message server, the enqueue server, and a separate start service — The SCS instance (system central services instance). The SCS instance cannot process any dialog requests — it is used to manage locks, exchange messages, and balance workload in the SAP system.
Components of SAP NetWeaver Application Server Java
- Java server processes
- Startup framework
- Internet Communication Manager
- Enqueue Server
- Message Server
- SAP Start Service
The following figure shows the components of a Java-only system. For a better overview, series lines have not been used. Incoming requests are accepted by the Internet Communication Manager and distributed to the Java server processes. There is one database for each Java system.
More Information