Introscope BOLight setup is no longer supported
The setup described in this wiki is no longer functional due to changes in the Diagnostic Agent.
Please refer to the following kbase for the alternative information for setting up Introscope monitoring.
On this page, we will configure each managed BI and Web Application Server host using the ACTool 2.x. These steps should be repeated on every host in your landscape where you have installed a Diagnostic Agent or are running a Web Application Server hosting BI web applications.
Prepare the ACTool for Managed Host configuration
- Confirm you have copied ACTool zip file to the host that you are configuring
- Extract the ACTool zip file to a folder
Browse into the <actool>\conf directory. Delete the file products.xml and rename the file products_bolight.xml to products.xml (we are replacing the original products.xml). Then, edit the file boe.properties with a text editor. Edit the following properties then save the changes.
- Save the changes to boe.properties.
Execute the ACTool for Managed Host configuration
The ACTool allows you to select which configurations to make depending on what components are installed on a particular host. In this section, we will configure our hosts for monitoring using the ACTool.
- In the folder where you extracted ACTool, right click on run_actool.bat and choose Run As administrator.
- Type 2 then press Enter to select SAP BI PLATFORM 4.x then type 1 and press Enter for the option to Execute
Next, you should determine the required configuration options depending on what components are on the host that you are currently configuring. Refer to the table below for options then proceed with the setup:
Components on the host being configured ACTool config options to enter Default BI 4.x install (including Apache Tomcat) Press Enter to select all configuration options BI installation only (No Apache Tomcat) Type 2,3,4,8,9,19 and press Enter Only Apache Tomcat (with Diagnostic Agent) Type 4,12,14,15 and press Enter Only Apache Tomcat (without Diagnostic Agent) Type 12,14,15 and press Enter
- When the script is completed, review the list of executed scripts and check for SUCCESS. If there are any FAILURE steps, you can troubleshoot this specific step and then re-run only this step again to complete the configuration (see below Troubleshooting section). You can close ACTool by typing quit and press Enter.
- Finally, restart the SAPDAA_98, SAPHostExec, Apache Tomcat, and Server Intelligence Agent services
- If the steps were successful, you can continue to the next page: 6. Validate the implementation
Troubleshooting ACTool and further documentation
This section provides some tips for troubleshooting the ACTool configuration process.
ACTool User Guide
For further information about ACTool, browse to the directory where you extracted ACTool and check the /doc directory for the file ACTool User Guide.pdf.
You can identify issues with ACTool configuration by analyzing the ACTool tracelog. Browse to the location where you extracted ACTool and check the /logs directory for the log file ac*trace.log.
ACTool provides a Check option to validate your configuration. The steps to run a Check are the same as when you ran the Execute option, however in this mode the ACTool simply checks your configurations and displays SUCCESS or FAILURE for each previously configured script step.
Troubleshooting a failed ACTool configuration step
In the ACTool output, each configuration script or step is displayed along with the source of this configuration (either a KBase or Wiki page). If you encounter a FAILURE message for a particular step, you can review the specific changes this script is making on the system. The majority of steps are documented in SAP Note 1653689
Apache Tomcat does not start!
The ACTool configures Java Options for Tomcat to tell Tomcat to load the Introscope Java Bytecode Agent. Common problems include:
- The user running Apache Tomcat service does not have read permissions on the wily folder. (by default C:\usr\sap\ccms\wily). To fix the problem, grant the Tomcat service user read permissions on the /wily folder.
- The user running Apache Tomcat service does not have write permissions on the wily/logs folder (by default C:\usr\sap\ccms\wily\logs). To fix the problem, grant the Tomcat service user write permissions on the /wily/logs folder.
- If you need to restore the Apache Tomcat service immediately and troubleshoot at a later time, you can go to Apache Tomcat Configuration in your Windows start menu, click on the Java tab, and remove the -javaagent property from Java Options. You will of course need to re-add this property later to restore monitoring.