SAP NetWeaver Application Server Java

Preparations in the Managed System

Task	Actions
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 Java	Install the latest SAP NetWeaver version from support.sap.com/swdc
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 needed	As 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 Information	Implement 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: SAP Setup Guide for Introscope 10.7 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
J2EE Job Scheduler configuration to collect J2EE jobs	The J2EE Scheduler Jobs extractor requires an additional (manual) preparation step: the configuration of an external scheduler in the managed SAP Java system. The external scheduler is a read-only interface. No jobs will be modified. Prerequisites The FRUN Java user used by the SDA agent to connect to the SAP Java system (e.g. SDAGENTJ_<FRUN> ) has the SAP_JAVA_WSNAVIGATOR role. Activities Log on to SAP NetWeaver Administrator of the managed system with an administrator user. Open the Java Scheduler administration page, for example, Operation Management → Jobs → Java Scheduler. Choose the tab to display external schedulers. Add a new scheduler entry. In the dialog box, enter a name and a description (for example, "SolManReadInterface" and "External interface for reading scheduler states"). Assign the FRUN agent user (e.g. SDAGENTJ_<FRUN>), no password is required. Confirm. In the external schedulers table, there will now a new entry created with an automatically generated scheduler ID, the name you have entered, the description and user.
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 installed	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
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)