A complete guide to setup CA APM Introscope 9 for monitoring SAP BI Platform 4.1 on Windows [PART 2/2]

Continued from:  A complete guide to setup CA APM Introscope 9 for monitoring SAP BI Platform 4.1 on Windows [PART 1/2]

Step 4: Configure each BI node and application server node

In this step, we need to enable monitoring on each Apache Tomcat and BI Platform node. In this example, Apache Tomcat is installed by the SAP BI Platform installer. If you have a stand-alone install of Apache Tomcat or another Java application server you can copy the wily folder from the BI node to the Java application server node and complete the configuration as shown below.

1. On the BI / Java application server node, browse to <INSTALL_ROOT>:\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wily\webapp then edit the file IntroscopeAgent_tomcat.profile with a text editor
2. Search for $IntroscopeAgentEnterpriseManagerHost and replace this with the hostname of your Introscope Enterprise Manager
3. Search for $IntroscopeAgentEnterpriseManagerPort and replace this with the agent communication port number of your Introscope Enterprise Manager
   
   
4. Save the changes to IntroscopeAgent_tomcat.profile
5. Launch the Apache Tomcat configuration editor (START-->Programs-->Tomcat-->Tomcat Configuration) then click on the Java tab
6. Add the following Java properties under Java Options
   
   -Dintroscope.agent.name=TOMCAT_<PORT>
   -javaagent:<Path_To_Agent.jar>
   -Dcom.wily.introscope.agentProfile=<Path_To_IntroscopeAgent_tomcat.profile>
   
   Example:
   
   -Dintroscope.agent.name=TOMCAT_8080
   -javaagent:C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wily\Agent.jar
   -Dcom.wily.introscope.agentProfile=C:\Program Files(x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\wily\webapp\IntroscopeAgent_tomcat.profile
   
   
   
7. Click the Apply button, then click on the General tab and restart Apache Tomcat. If the Apache Tomcat service fails to start, check that you entered the Java properties correctly in the previous step and that the files exist in the specified locations
   
   
8. Next, launch the Central Management Console, logon as Administrator, choose Servers. Under nodes, right click on an SIA node and click Placeholders
   
   
9. Edit the following Placeholder values:
   
   

   Placeholder	Value	Description
   %IntroscopeAgentEnableInstrumentation%	true	Enables or disables Introscope instrumentation on BOE Java based servers (APS, AJS, etc)
   %IntroscopeAgentEnterpriseManagerHost%	IEMHOSTNAME	Hostname of your Introscope Enterprise Manager
   %IntroscopeAgentEnterpriseManagerPort%	6001	Agent listening port of your Introscope Enterprise Manager
   %NCSInstrumentLevelThreshold%	10	Set the instrumentation level to 10
   %SMDAgentHost%	localhost	This property should always be set to localhost
   %SMDAgentPort%	59818	This port should match the port set in SapAgentConfig.xml

   
   
10. Restart the Server Intelligence Agent and repeat steps 8 and 9 for each additional SIA node

Step 5: Validate the installation/configuration is working

In this step, we will make sure that the metrics are working correctly. Before you start this step, go ahead and refresh some Web Intelligence documents, Crystal Reports, Dashboards, etc to generate some performance data in the Introscope Enterprise Manager

1. Go to start, programs, CA APM, then click on Introscope Workstation Webstart or browse to http://iemhost:8081/workstation
2. Logon to Introscope using user Admin and password Admin89
3. Click Workstation,New Investigator
4. Expand SuperDomain, then locate and expand your BI / Java application server node
5. Verify that you see the following:
   
   
6. Next, click Workstation, New Console and validate that the Apache Tomcat and BOE 4.0 dashboards are returning data according to the products you are using in your BI landscape
   
   

Congratulations, your BI landscape is now being monitored by CA APM Introscope.  Should you face a roadblock in the configuration, you can request help from SAP by submitting an incident to component BI-BIP-DEP.  Stay tuned to this space for forthcoming BI Introscope diagnostics and monitoring blogs coming soon!

Please don't forget to rate this blog if you found this tutorial helpful.