sap netweaver application server java_SAP NetWeaver Application Server Java

Run Outside Discovery on the HostManual Operations

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 versionManual 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.

Check if an SLDR is neededManual Operations

As prerequisites, you need to choose, according to your landscape, if an SLDR is requiredsee page Preparing System Landscape Data Router.

Implement SAP Note for the Licence Management InformationManual Operations

Implement SAP Note 983424- Extension of AS JAVA SLD Data Supplier, so that the Licence 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)

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 OperationsRun 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 the adm 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.

Create SDAGENTJ User

User to authenticate local HTTP and P4 calls by the simple Diagnostics Agent for data collectionManual 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 JavaCheck theBCIA 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.

Configure the BCI Adapter for each InstanceManual 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).

Set 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 toadm: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 using the config tool: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

Check the current VM Parameter:Select Your choise: 14  (Get the VM System Parameters info)

Read the "Custom Properties" section and check:com.wily.introscope.agent.agentName=${SYSTEM_NAME}_${INSTANCE_NAME}_$[elem/Name]

com.wily.introscope.agentProfile/usr/sap/${SYSTEM_NAME}/${INSTANCE_NAME}/ByteCodeAgent/core/config/IntroscopeAgent.profile

introscope.agent.hostName = ${INSTANCE_HOST}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.

After parameter update, select your choice: 3 (Apply Changes).

Get VM Additional ParametersSelect Your choise: 18  (Get VM Additionnal System Parameters info)

Read the "Custom Properties" section and check the the following:

"-javaagent:/usr/sap/${SYSTEM_NAME}_${INSTANCE_NAME}/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).

Any parameter change, require a Java stack Restart

Check if the BCI Agent Java Startup Parameters are set correctly: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

Check LMDBManual 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.

CTC config store servlet must be installedManual 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