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 install the Diagnostic Agent on all BI hosts and Web Application Server hosts in the landscape. If you have a dedicated Web Application Server host, installing the Diagnostic Agent is optional but still recommended as it provides metrics on host performance. If you have a host with both the BI install and WAS install (a default BIP install for example), it is only required to install the Diagnostic Agent once.
The Diagnostic Agent must be installed while logged on as a user with local administrator privileges
User Accounts for Diagnostic Agent
There are three user accounts which are used to run the Diagnostic Agent services. By default, the SWPM installer will create these users as local accounts, assign them to the correct local groups, and assign the required user rights permissions for these accounts. Using local accounts is the recommended approach. If you plan to use local accounts, skip to the section Install The Diagnostics Agent.
Using Domain Accounts instead of default Local Accounts
If your organization requires you to use domain accounts only, you need to create the required domain accounts and domain groups ahead of installing the Diagnostic Agent. Request your domain admin to create the following users and groups on the domain and configure the group membership as shown below.
Domain Users to create
Domain Groups to create
User Group Membership
|User||Assign to Group|
Once the users and groups are created on the domain, go to the host where you will be installing the Diagnostic Agent and assign the following user rights. You can also set this as a domain policy as long as the required user rights are pushed to the host where you are installing the Diagnostic Agent.
Access this computer from the network
Adjust memory quotas for a process
Replace a process level token
Log on as a Service
Restore files and directories
Deny Logon Locally
Deny log on through Remote Desktop Services
Install the Diagnostic Agent
- Verify the "Hosts File" format on the host has correctly been define following the Mandatory Standard. See https://wiki.scn.sap.com/wiki/x/i4IjIQ
- Confirm that you have copied the required files to the BI or WAS host.
Open a command prompt and browse to your temporary media directory and use SAPCAR to extract the SWPM*.SAR to a folder called swpm.
Run the command:
SAPCAR_816-80000938.EXE -xvf SWPM10SP20_1-20009707.SAR -R swpm
Next, browse to the swpm directory and execute sapinst.exe using the parameter SMD_INSTALLATION_SCENARIO=ishub
Run the following command:
- The installer will launch a browser and will prompt you for a user name and password. (Note: If warned about a certificate, click continue to this website). Enter the user account and password that you are using to install the Diagnostic Agent (must have local administrator access) then press OK.
- After the Software Provisioning Manager starts, scroll down to the bottom of available options, expand Generic Options, Diagnostics in SAP Solution Manager, then choose Install – Diagnostics Agent and click Next
- When prompted to log off, click OK. Then, log back on the host and the install will continue.
- Next, under Search Location, for Package Path, click the Browse button and browse to your temporary media location and select SAPEXE.SAR then click OK. Then click Next.
- The Package Name location for SAPEXE.SAR will be populated in the list..
- Next, under Search Location, for Package Path, click the Browse button and browse to your temporary media location and select SAPHOSTAGENT.SAR then click OK. Then click Next again. Repeat this step for SAPJVM6.SAR and SAPDIAGNOSTICAGENT.SAR until all Packages are populated in under Archive Locations then click Next.
- On the Diagnostics Agent Host screen, confirm the Host name is correct and click Next.
- On the General System Parameters for the Diagnostic Agent screen, you can choose the installation drive and choose a custom Diagnostics Agent System ID, or just click Next to choose the defaults.
- On the Windows Domain for the Diagnostics Agent screen, you can choose to allow the Diagnostics Agent installer create local user accounts by selecting Local Domain. If you need to use domain accounts that you have already created (see User Accounts for Diagnostics Agent section), choose Different Domain and enter the domain name of the accounts you will be using under the Windows Domain field. Click Next.
- If you are using a pre-created domain account, enter the password for domain users daaadm and SAPServiceDAA. Otherwise, specify a strong password that you would like to use for the local accounts daaadm and SAPServiceDAA.
- You may receive some warnings. Click Next to continue and if you are ok with the warnings then click No on the following message box to acknowledge the pre-requisites warning and to not repeat checks.
- If you are using a pre-created domain account for user sapadm, enter the password you defined for this account on the domain. Otherwise, specify a strong password for the new local sapadm account. This account is responsible for running the which runs the SAPHostControl service. Enter the desired password and click Next.
- When prompted to add SAPServiceDAA to the trusted users list, click Yes.
- On the Diagnostic Agent Instance screen, click Next to choose the default instance number of 98. If you have an instance already on 98, choose a unique instance number and click Next.
- On the SLD Destination for the Diagnostic Agent screen, choose the default of No SLD destination and click Next.
- On the Connection of the Diagnostics Agent to SAP Solution Manager screen, choose Do not configure connection and click Next.
- On the Parameter Summary screen, click Next to begin the installation.
- You will be updated when the installation has succeeded.
- Once you have completed the Diagnostic Agent installations on each managed host in the BI landscape, you can continue to the next page: 5. Configure managed hosts using ACTool