Introscope Version 7.

1 Installation Guide For SAP
September 2007

Introscope Installation for SAP

Contents........................................................................................................................................... 2 1 Installation Overview ............................................................................................................... 3 2 Upgrading from Previous Versions to Introscope 7.1................................................................ 7 3 Installing the Introscope Enterprise Manager .......................................................................... 10 4 Introscope-Enabling SAP J2EE Systems ................................................................................ 19 5 Workstation Installation ......................................................................................................... 28 6 Introscope-Enabling Duet ASP.NET Applications.................................................................. 29 7 Environment Performance Agent Installation ......................................................................... 37 8 Installing and Configuring WebView with SAP NetWeaver ................................................... 41 9 Additional Installation Options ............................................................................................... 44

Introscope® Version 7.1 Installation Guide for SAP (10/2/2007)

Page 2

Introscope Installation for SAP

1 Installation Overview
This document covers the installation and configuration of Introscope in the following chapters: • Installation Overview • Upgrading previous versions to Introscope 7.1 • Installing Introscope Enterprise Manager • Introscope-enabling SAP J2EE Systems (Agent Installation) • Optional: Installing Introscope Workstation • Optional: Installing Introscope WebView on NetWeaver • Environment Performance Agent installation • Optional Configuration Steps

Introscope Overview
Introscope is a system management application created to manage Java Application performance. Unlike development tools, Introscope is designed to scale with minimal performance impact. This allows you to monitor and manage your application performance in live production environments. You are installing Introscope as part of SAP Solution Manager to give SAP support better visibility into technical issues you may experience. You will also get access to Introscope so that you can analyze performance problems on your own.

Introscope® Version 7.1 Installation Guide for SAP (10/2/2007)

Page 3

Introscope Installation for SAP

Reviewing the Installation and Configuration Process
You will be installing the following Introscope components: • Introscope Enterprise Manager (server component) The Enterprise Manager is typically installed on the Solution Manager host. Alternatively, you can install the Enterprise Manager on a separate host. The memory and CPU requirements for the Enterprise Manager depend on the number of Introscope Agents that you connect and on the complexity of the monitored systems. Typically, for up to ten agents, the default configuration using 512MB Java heap (about 600MB main memory) will suffice. For about twenty additional agents, add 512MB of Java heap to a total of 1024MB (allow 1500MB main memory). More details on Enterprise Manager Sizing and self-monitoring can be found in the FAQ attached to SAP Note 797147. • Introscope Java Agent (on the managed systems) The installation files have to be copied to each monitored host once. For each Java server node you set Java VM parameters to activate the agent. After activation by restarting the Java VM, the agent runs within the Java process of the monitored system. • Introscope Environment Performance Agent (on the managed systems) The Environment Performance Agent is installed once per host. It runs in a separate Java process to collect data on operating system level, e.g., from saposcol and TREX. The EPAgent generates less load on the Enterprise Manager than a normal agent. For this reason, it should not be included in the memory sizing calculation above. • Optionally, you can install the Introscope Workstation on the Enterprise Manager host or any client PC and/or deploy Introscope WebView on the SAP NetWeaver Web Application Server). See the next section for recommendations about the UI for Introscope.

Deciding About the UI for Introscope
There are four different options to access Introscope: 1. Introscope Workstation: Swing-based client user interface, full functionality a. Explicit installation on the client PC on which you want to use it (see Chapter 5). b. Use Java WebStart to download it on demand from the Enterprise Manager. Requires Java 5 (no installation necessary), default URL: http://emhost:8081/workstation. The workstation will be downloaded only once and is then cached on the client PC. For every new start of the Workstation the cached version is checked against the Enterprise Manager and, if the Enterprise Manager was updated, a new version is downloaded automatically. 2. Introscope WebView: Browser-based user interface, uses Adobe SVG plugin. In some details limited functionality.

Introscope® Version 7.1 Installation Guide for SAP (10/2/2007)

Page 4

Download installation files from SAP Service Marketplace. The current version can only be downloaded from the Service Marketplace. 4.Introscope Installation for SAP a. Use the WebView that is available by default on the Enterprise Manager (no installation necessary). Install the Introscope Java Agents and Environment Performance Agents on managed systems. Optional: Install the Introscope Workstation. Introscope Access After installation. Obtain the Latest File Versions Installation CD Note: The Introscope version 5. A list of frequently asked questions for troubleshooting the installation is also attached to this note. Introscope® Version 7.3 originally shipped with NW 04 SR 1 is outdated. You may also decide to install the workstation explicitly on your client PC (1a). Deploying WebView on NetWeaver (2b) is normally not needed. Check SAP Note 797147 for latest updates to the installation procedure and to this document. 3. If you decide using WebView 2a) is recommended. you can use the following default credentials to access Introscope: User Admin Guest Password Admin89 guest12 Access Rights read. 2. run_tracer read The Installation Process The Introscope installation process consists of the following steps: 1. 5. The most convenient option is to use 1b (Launch Workstation via Java Webstart).1 Installation Guide for SAP (10/2/2007) Page 5 . Install the Introscope Enterprise Manager on the central monitoring system. In general using the Workstation should be preferred to WebView since it is more powerful. b. The binaries are then only downloaded once and after that cached on the client PC. Deploy WebView on top of SAP Netweaver (see Chapter 6). See SAP Note 797147 for download links. default URL: http://emhost:8081/webview.

Download the Latest Updates from the Service Marketplace Download all files listed in SAP Note 797147 from the SAP Service Marketplace. Review the latest version of this note before you start the installation.1 Installation Guide for SAP (10/2/2007) Page 6 -> Operations Introscope® Version 7.Introscope Installation for SAP SAP Note 797147 SAP Note 797147 is the central entry point for up to date information regarding the installation of Wily Introscope. You also find a list of frequently asked questions attached to the note. The note explains the exact locations of the files. Installation Tools Details on the used installation tools (sapcar and SDM) can be found in the “Support Package Stack Guide”: http://service.

1 at the same time. /usr/sap/ccms/wilyintroscope. Upgrade Enterprise Manager. version 5. Introscope 7. Upgrading the agents will require a restart of the monitored systems. If you are performing a fresh installation.1 Version Compatibility and Upgrade Sequence The Introscope Enterprise Manager 7.g.1 supports Introscope Agents of older releases. 2.g. This can be done without impact on any monitored systems. This chapter explains the options to upgrade an Introscope installation to Introscope 7. If you want to keep the historical performance data. In other words. which is discouraged. some charts on the Console may remain empty because the SAP customizing assumes that Agents and Enterprise Manager have the same version.1 Installation Guide for SAP (10/2/2007) Page 7 .g. move the directories /data and /traces to a new location in the filesystem.1. e.1 agent to an older Enterprise Manager does not work. Workstation. Since WebView is running as part of the Enterprise Manager an explicit upgrade of WebView is not needed – unless you deploy WebView on NetWeaver. and 7) to Enterprise Manager Version 7. you can connect with agents of different versions (e. and Enterprise Manager must always have the same version and patch level. the following procedure is recommended: • Shut down the Enterprise Manager via the Windows Services Control Panel or kill on Unix. If you want to keep the performance database (SmartStor) of the previous version or any other configuration settings and if you want to keep the old location. When using older agents with a newer Enterprise Manager. Enterprise Manager Upgrade There is no tool support for an in-place upgrade of the Enterprise Manager. WebView. 6. Workstation. Then upgrade the Introscope agents in the monitored systems at your convenience.1 Uninstall Introscope Introscope® Version 7. Due to this version dependency we recommend to upgrade sequence: 1. and WebView first. • Windows only: Launch the uninstaller via the Windows Start Menu. Connecting a new version 7. • Back up your Enterprise Manager directory. please proceed to the next chapter.Introscope Installation for SAP 2 Upgrading from Previous Versions to Introscope 7. e. Connecting WebView and Enterprise Manager of different versions does not work.

jmxservice). • Manually transfer any custom management modules (located in /config/modules) from the old to the new location.g. Since some agent files are locked while the monitored system is running. e. In case you want to do a manual upgrade. you may also decide to drop the /traces directory completely instead of migrating it. Do not replace the new configuration files with the old copies since you may then loose any newly introduced properties.wilytech. Please undeploy the old version with SDM. by moving the old agent installation to a different directory. • Manually transfer any customization (Java VM parameter in file Introscope Enterprise Manager. copy and paste any customization from your old files.webview). Agent Upgrade All agent installations and upgrades can (and should) be done centrally by the administration tools of Solution Manager. which is no longer needed. • Shut down the newly installed Enterprise Manager in case it was launched after the installation. The only manual steps are to restart the managed systems after any configuration change and to undeploy the JmxService J2EE application (com. Instead. • Copy or move the old subdirectories /data and /traces to the new location.g. from /usr/sap/ccms/wilyintroscope to /usr/sap/ccms/wilyintroscope.Introscope Installation for SAP • Move the remaining files from the old installation to a different of the Introscope agent.1 Installation Guide for SAP (10/2/2007) Page 8 .old • Perform the new installation to the same directory (/usr/sap/ccms/wilyintroscope) again using the procedure described in the next section. • Remove the subdirectories /data and /traces from the new installation if they exist. the monitored system must be down for the agent upgrade. You may want to simply undeploy the old version of WebView on NetWeaver (com. WebView Upgrade Note that starting with Introscope 7. e.conf or runem.1 the Enterprise Manager already contains an embedded WebView that is run as part of the Enterprise Manager Java process.SAR) as described in the next section. WebView running in the Enterprise Manager is by default reached via the URL Introscope® Version or EMService. As a consequence.wilytech. As an alternative. the JmxService J2EE application is no longer needed starting with release 7. But do not overwrite newly installed standard SAP modules with older versions. It is no longer necessary to deploy it on NetWeaver. to get rid of any obsolete files we recommend performing a fresh installation. Make sure you also extract the new management modules files (SAPISMM*. Be aware that the traces database will be migrated to a new format when the Enterprise Manager is launched. Also for the manual upgrade. They will only be created if the Enterprise Manager is started.nohup. other properties in file config/IntroscopeEnterpriseManager.

However. Introscope® Version 7. If you want to run WebView on NetWeaver anyway.Introscope Installation for SAP http://emhost:8081/webview. deploy the new version in the same way as the old version. before you deploy the new version you need to undeploy the old version and restart the J2EE server. See also the FAQ.1 Installation Guide for SAP (10/2/2007) Page 9 . The former URL http://smdhost:5xx00/webview is no longer valid for this operating mode.

bin introscope7. Choose the Enterprise Manager Installer File Depending on the operating system on which you want to install the Enterprise Manager.jar introscope7.bin introscope7. The file names listed below may vary slightly for patch updates to the Enterprise Manager.1 Installation Guide for SAP (10/2/2007) Page 10 .1. different installation files must be chosen. scripts.1hpuxIA64SAPEndUser.1linuxSAPEndUser.bin Introscope® Version 7. In particular.). If you find your operating system listed here. The first table below lists the platforms for which a platform specific installer with a bundled Java VM is available.bin introscope7. download the file SAPISEM*. you will run the installer file and add some SAP customization (management modules. Operating System AIX5 64bit i5/OS HP-UX 11 on PA-RISC 32bit HP-UX 11 on PA-RISC 64bit* HP-UX 11 on IA64 Linux on IA32 32bit Linux on x86_64 64bit Installer Filename introscope7.bin introscope7.Introscope Installation for SAP 3 Installing the Introscope Enterprise Manager Installation User You should run the installer with the same user account that will be used later on for running the Enterprise Manager.1hpuxSAPEndUser. on Unix operating systems do not use the root account to launch the installer.1aix64SAPEndUser. etc.P9os400SAPEndUser.SAR from the corresponding folder on the Service Marketplace (see Note 797147 for the exact location). A common best practice is to use the sidadm user of the Solution Manager installation to install and run the Enterprise Manager. To install the Introscope Enterprise Manager.1linuxAmd64SAPEndUser.

ibm.jsp Click on JRockit 5.Introscope Installation for SAP Solaris on SPARC 32bit Solaris on SPARC 64bit* Windows IA32 Windows x86_64 64bit* Windows on IA64 introscope7.1solarisSAPEndUser. Installation includes one additional step then: ckit_prod_fam.0 http://java.bea.0 R26 JDK Linux (Intel Itanium .com/developerworks/java/jdk/linux/do wnload.1windowsSAPEndUser.1windowsitanium64SAPEndUser.64-bit) http://www.SAR of the folder #OS independent on the Service Marketplace. See below for details. Platform Independent Introscope Installer If you do not find your operating system in the table above. Download JRockit 5.0 wnload. Install a Java 5 VM 2. Operating System Linux on IA 64bit Java 5 VM Download Link http://commerce. and Windows on x86_64 only 32-bit installers are available. If you want to run the Enterprise Manager on a 64 Java VM. you can exchange the Java VM after the installation. select 64-bit iSeries/pSeries in column J2SE 5.sun.jsp.0. Agree to terms.html. HPUX on PA Linux on Power 64bit Linux on zSeries 64bit Solaris on x86_64 64bit Introscope® Version 7.1 Installation Guide for SAP (10/2/2007) Page 11 . you can use the generic installer for the operating systems listed below.exe introscope7. Launch the OS-independent installer The operating system independent installer is contained in the file select 64-bit zSeries (S/390) in column J2SE 5.bin introscope7.exe * For Solaris SPARC.

because your SAP installation is located on a different Windows drive. getting its input from the response file file is in the same directory as the . Open the file installer. After installation.1 Installation Guide for SAP (10/2/2007) Page 12 .e.exe / . .properties in a text editor. you can check the results in the installer logs. accept license Extract and Run the Introscope Installer Extract the SAR file with the following command: SAPCAR –xvf SAPISEM* 1. Note: Use slash (/) as path separator for all are located. introscope7.J2SE(TM) Development Kit 5. use one of the following alternatives. Introscope® Version 7. Add the option –DUSER_INSTALL_DIR=<installation directory> to the invocation of the installer (see below). The installer runs in the background as it installs Introscope components. Alternative 2: Edit installer. depending on your platform. 2. When launching the installer... and doesn’t provide any feedback. The Introscope installer is invoked from the command line and runs “silently”. e. including Windows! Alternative 1: Set the Installation Directory via Command Line Option 1. Open a command prompt and go to the directory where the installer file and the file installer. make sure the which configures the installation procedure and one of the installer files mentioned above.jar file! Optional: Configuring the Installation Directory The installation of the Enterprise Manager by default goes to the following directories: • Windows: C:\usr\sap\ccms\wilyintroscope • Unix / i5/OS: /usr/sap/ccms/wilyintroscope If you want to change this directory.exe –DUSER_INSTALL_DIR=d:/usr/sap/ccms/wilyintroscope. The Introscope installer will perform an automated install of Introscope components.SAPEndUser.SAR As a result you will find two files: The file installer.0 latest Update.bin / .g.Introscope Installation for SAP select Solaris x86 Platform and Solaris x64 Platform .1windows.

/some/path/java refers to the Java 5 VM that you installed as described above: /some/path/java –classpath introscope7.SAPEndUser. /usr/sap/ccms/wilyintroscope/install/Introscope_InstallLog. Start the Installer 1. You can avoid copying the installation file itself by using the complete path to the executable.exe. Verifying Installation. 2. double-click on the introscope7. Launch the installer for your platform using the appropriate command: • For Windows. To change the install directory location. the configuration file installer. To confirm installation was successful: 1.exe • For any other platform-dependent installer. Open the file.jar install • For the platform independent installer that does not contain a bundled Java VM use the following command. use the command in the following example.SAPEndUser. Verify that the Introscope directory exists at: • <drive>:\usr\sap\ccms\wilyintroscope (Windows) • /usr/sap/ccms/wilyintroscope (Unix.P4os400SAPEndUser.1windows.1otherUnixSAPEndUser.bin • For the i5/OS installer run the following command in QSH: /QIBM/ProdData/Java400/jdk15/bin/java –classpath introscope7. Note: The instructions in this guide will use examples relative to the default installation directory. 2.Introscope Installation for SAP 2. Verifying Installation The installer does not give confirmation of successful installation on the console. Verify that the following lines appear at the top of the file: Introscope® Version 7./introscope7. i5/OS) OR the location you specified. 3.log .SAPEndUser. Verify installation using instructions in the following section. Locate the USER_INSTALL_DIR property. or launch from command-line with the following command: Introscope7. enter the desired location in the USER_INSTALL_DIR property. You may have to set the right permission before you can launch the installation: .jar install Note: In any must be located in the current directory where you launch the installer.1 Installation Guide for SAP (10/2/2007) Page 13 .1windows.1.

sh: Used when Enterprise Manager is launched with nohup .java. The property wrapper. JAVAPATH.option.additional to modify Java VM parameters. Adapt Java VM and Java VM Parameters Depending on the startup mode the Java VM and the Java VM parameters are adapted in different locations: on Unix platforms where the primary script Introscope_Enterprise_Manager does not work.command defines the Java VM to use. Introscope_Enterprise_Manager. and JVMARGS environment variables.vm to the full path of the VM to use (if you want to change the default) and use lax. you have to do this in two cases: o Enter the path of a separately installed 64 bit Java 5 VM for platforms on which by default only a 32 bit VM is provided: Solaris on SPARC HPUX on PA RISC Windows on x86_64 Introscope® Version Used when Enterprise Manager is launched on i5/OS. The following Java VM parameter changes should be considered: Increase the heap size (–Xmx) of the Enterprise Manager if you have more than ~10 agents. Adapt lax.conf: Used when Enterprise Manager is running as Windows Service on Windows to increase the Java heap (corresponds to –Xmx).Introscope Installation for SAP Installation: Successful. Enter the absolute path to a Java 5 VM if you want to use a Java VM that is not bundled with the installer.current.nohup. Increase the value of adapt wrapper. Adapt the JVM_ARGS environment variable. Adapt the 166 SUCCESSES 0 WARNINGS 0 NONFATAL ERRORS 0 FATAL ERRORS Note: The number of successes may be different than what is shown in this example.lax: Enterprise Manager launched with script Introscope_Enterprise_Manager (typically only on Unix).1 Installation Guide for SAP (10/2/2007) Page 14 . runem. In particular./runem.nohup.

volatileImageBufferEnabled=false for all platforms based on the Sun VM in case you see display problems with WebView. Launch Enterprise Manager as Windows Service To launch the Enterprise Manager automatically at system restart.g.Introscope Installation for SAP Enter the path of a separately installed Java 5 VM for platforms where you used the platform independent installer. 1. i.. In the Introscope Enterprise Manager. as in: Introscope® Version 7. e. Running Enterprise Manager in nohup Mode on UNIX The Introscope Enterprise Manager should be configured to launch automatically on Unix.SAR As a result you will find one or more .. This means you will have to restart the Windows Service for the Enterprise Manager. but several properties must first be set in the Introscope properties files.awt.redirect. Start the service if it is not yet running. make sure there is no value for the property lax.e.lax file. To check. For this purpose it can be run in nohup mode on UNIX. set the Java heap size properties to -Xms64m –Xmx2048m Install the SAP Management Modules Extract the file SAPISMM71_xx.js files in the subdirectory scripts. perform the following: 1. For Windows installations the Enterprise Manager is typically automatically launched as Windows Service.jar files in the subdirectory config/modules. Otherwise.stdin. /usr/sap/ccms/wilyintroscope. Set the Java VM parameter –Dswing. the Enterprise Manager will need an X server. it is registered as Windows service (On Unix you should run it as background process). and some other files distributed over the Enterprise Manager installation.1 Installation Guide for SAP (10/2/2007) Page 15 .headless=true for all platforms. the DISPLAY environment variable must point to a valid X Windows server. some . On i5/OS. Example: cd /usr/sap/ccms/wilyintroscope SAPCAR –xvf SAPISMM71_xx. The newly installed management modules only become active after the Enterprise Manager is (re-)started. 2. o Set the Java VM parameter –Djava.SAR in the home directory of the Enterprise Manager installation. Open the Services Control Panel (Start Menu Control Panel Administrative Tools Services) and check that the service “Introscope Enterprise Manager” has been created.

The effect is that the Enterprise Manager does not fully to your needs and use this to launch the EM: Note: For some platforms.nohup. please adapt the shell script runem. for example the <SID>ADM of your Solution Manager system. Introscope® Version & Consider launching the Enterprise Manager automatically at system startup. as in: introscope.stdin. we discovered that the automatically generated script nohup .disableInteractiveMode=true 3. <Your User> can be any user. the Enterprise Manager may not start. Running Enterprise Manager on i5/OS Note: The Enterprise Manager can be run in QSH shell but not in QP2TERM (Pase environment).Introscope Installation for SAP file. this user needs to have access to the files in /usr/sap/ccms/wilyintroscope. or set them incorrectly. In the IntroscopeEnterpriseManager. In this case. If you attempt to run the Enterprise Manager in nohup mode without changing these properties as described./Introscope_Enterprise_Manager& It is critical that both of the Introscope Enterprise Manager properties are set exactly as described above.redirect= 2.nohup.1 Installation Guide for SAP (10/2/2007) Page 16 . ensure that the property introscope. You can ensure this by running chown –R <Your User> /usr/sap/ccms/wilyintroscope in QSHELL. However. you should add an Autostart Job Entry to the subsystem QUSRWRK. you will have to hook it into one of the operating system specific init scripts. or CPU utilization may become'')') USER(<Your User>) GRTOBJAUT OBJ(<Your Library>/WILYEM) OBJTYPE(*JOBD) USER(<Your User>) AUT(*USE) ADDAJE SBSD(QUSRWRK) JOB(WILYEM) JOBD(<Your Library>/WILYEM) <Your Library> can be any library. Start the Enterprise Manager with the following command: nohup .enterprisemanager. To activate the Wily Enterprise Manager at system startup. Introscope_Enterprise_Manager does not work correctly with nohup. run the following commands: CRTJOBD JOBD(<Your Library>/WILYEM) JOBQ(QUSRNOMAX) TEXT('Jobdescription for Wily EM') RQSDTA('QSH CMD(''cd /usr/sap/ccms/wilyintroscope && /usr/sap/ccms/wilyintroscope/runem. for example R3400./runem. Typically.disableInteractiveMode is set to true. To achieve this.

1. OR • run Introscope Enterprise Manager.1 Installation Guide for SAP (10/2/2007) Page 17 & Alternatively you can submit the Enterprise Manager to Batch via: SBMJOB CMD(QSH CMD('cd /usr/sap/ccms/wilyintroscope && /usr/sap/ccms/wilyintroscope/runem. open a QSHELL and do the following: cd /usr/sap/ccms/wilyintroscope nohup runem. then launch the Enterprise Manager with the command: .exe (located in the <Introscope home> directory. 2. Check that the Enterprise Manager has started. To launch the Enterprise Manager directly on i5/OS. Locate the Enterprise Manager log at <Introscope home>/logs/IntroscopeEnterpriseManager. On Windows Start the Enterprise Manager using one of the following methods: • from the Start menu. On i5/OS Note: The Enterprise Manager can be run in QSH shell but not in QP2TERM (Pase environment).Introscope Installation for SAP Manually Starting Enterprise Manager If you have not set up automatic start of the Enterprise Manager. check that it is running properly. Look for the following line in the logfile: Introscope® Version 7. Note: Make sure the Enterprise Manager has both read access and write access to the complete /usr/sap/ccms/wilyintroscope directory. switch to the <Introscope home> directory. by default c:/usr/sap/ccms/wilyintroscope). Introscope > Administration > Introscope Enterprise Manager. so that configuration changes will be properly saved./Introscope_Enterprise_Manager Checking That Introscope Is Running Properly After you have launched the Enterprise Manager. you have to start the Enterprise Manager')) JOB(WILYEM) CPYENVVAR(*YES) ALWMLTTHD(*YES) On Other Platforms On other platforms.

1 Installation Guide for SAP (10/2/2007) Page 18 .PostOfficeHub] Server listening for incoming default socket connections on port 6001 In this case. 3. Introscope® Version 7. Check the TCP port that Introscope Enterprise Manager is using for agent connections.Introscope Installation for SAP 11/28/06 10:54:36 AM CET [INFO] [Manager] Introscope Enterprise Manager started. the Enterprise Manager agent port is 6001 (default value). Look for lines similar to the following in the logfile: [INFO] [Manager.

and 7. Extract the Introscope Agent files 2.20.SAR 2. For SAP J2EE versions after 7. Confirm the Agent was installed correctly by checking for the existence of the /wily directory in the <drive>:\usr\sap\ccms directory.00. Note: Always use forward slashes (/) as path separators for Introscope config files and for JVM parameters on all platforms including Windows. Introscope® Version 7.00. but the examples show Windows convention (backslashes in the paths). This avoids the need to escape the Windows path separator backslash (\) by doubling it. Create the Introscope Agent autoprobe connector (not for i5/OS and Java 5) 3. you are ready to install and configure the Introscope Agent and Introscope-enable your Java Applications. usually: <drive>:\usr\sap\ccms. SAPCAR –xvf ISAGENT71*. Installing the Introscope Agent with SAP NetWeaver After you have installed the Enterprise Manager. Configuring Introscope with SAP NetWeaver Application Servers Overview The following steps are required to install and configure the Introscope Agent to report information to the Enterprise Manager: 1. please check SAP Note 943031 (Note is not yet available for customers). 6.40. The following instructions are valid for SAP J2EE versions 6. Extract the agent installer file into the NetWeaver CCMS directory.Introscope Installation for SAP 4 Introscope-Enabling SAP J2EE Systems Note: The recommended procedure to install and customize the Introscope Agent is to use the setup wizard provided in Solution Manager Diagnostics.1 Installation Guide for SAP (10/2/2007) Page 19 . The instructions in the following section work on both Windows and Unix systems. If you do not have Solution Manager Diagnostics available follow the manual procedure described below. Introscope-enable the application code by setting Java VM parameters Extract the Introscope Agent To install the Introscope Agent: 1.

Default setting is 6001. 3.profile sap_IntroscopeAgent_xi. You will have to choose one of the profiles from the table below.tcp. Locate the property.Introscope Installation for SAP Configuring Introscope Agent Settings The following section details how to configure the Introscope Agent. depending on the monitored solution you need to choose different profiles: Choose the Right Agent Profile SAP provides several agent profiles for different applications running on the SAP J2EE Engine. 4. Introscope® Version 7.enterprisemanager.DEFAULT.1 Installation Guide for SAP (10/2/2007) Page 20 .profile.0 SAP IPC (IPC 4. Enterprise Portal XI 3. not VMC) Note: For Introscope-enabling SAP IPC.profile file as the Agent profile.profile sap_IntroscopeAgent_ipc. introscope. Note that this file contains SAP-specific customization. e.transport. please also check SAP Note 886600.transport.g.DEFAULT.profile Applications Covered SAP J2EE. To configure the Introscope Agent: 1.agent. All profiles adhere to the name pattern sap_IntroscopeAgent*. Enter either the host name or IP address of the machine where Enterprise Manager resides. Locate the property. You will need to configure the host name or IP address and port of the machine where the Enterprise Manager resides. The value should be the port on which the Enterprise Manager listens for Agent connections. file <drive>:\usr\sap\ccms\wily\sap_IntroscopeAgent.0 2.agent. Furthermore. introscope.profile.enterprisemanager. Open the agent profile. This guide will refer to the sap_IntroscopeAgent. Save changes to the agent profile.profile. The Agent configuration settings are found by default in the file /usr/sap/ccms/wily/sap_IntroscopeAgent.port. Currently the following profiles are available: File Name sap_IntroscopeAgent.

2_05! For this reason it is also important that you specify exactly the same JVM that is actually used by the SAP J2EE nodes.2_04 to 1. different VM parameters are used for these platforms. Instead.4. There are two ways to specify the JVM: • use the JVM that is running the tool • pass the JVM directory on the command line to the tool 1.4.1 Installation Guide for SAP (10/2/2007) Page 21 .File to some other directories where the monitored systems have write access. Creating an AutoProbe Connector Use the CreateAutoProbeConnector. As an alternative.logfile and log4j. and the Agent reports that information to the Enterprise Manager. Run the Create AutoProbe Connector tool using the following command: Introscope® Version 7.appender. will install probes dynamically into application code as it is loaded.g. make sure that the monitored systems (user sidadm) have write access to this directory (write permission for group sapsys).logfile. 2.. from 1.Introscope Installation for SAP Check the Agent Log File Location By default. Important Note: You should re-create the AutoProbe connector every time you update the JVM that is used for the SAP J2EE nodes. For AIX with the IBM J9 Hybrid VM please see SAP Note 1015184—there are special parameters to pass when creating the autoprobe connector and when launching the VM. JVM AutoProbe. This step is not required for Java 5 VMs and not for any Java VM running on i5/OS. e. The Probes then report information to the Introscope Agent. Change the working directory to wily\connectors. Configuring JVM AutoProbe You have to create a so-called AutoProbe connector that fits for the Java VM that you use.jar tool to create a connector specific to the JVM used to run the application server.autoprobe. Introscope-enabling SAP NetWeaver A Java application is monitored by adding Probes to the bytecode (called “Introscope-enabling” your application).g. even if you just change the patch level. The following section details how to configure JVM AutoProbe. the Introscope agents write log files to the subdirectory logs (e. The method you will be configuring. /usr/sap/ccms/wily/logs). you can change the properties introscope. On Unix systems.

note the difference between Unix and Windows in the class path: The entries are separated by . Typically. Note that for class path and directory paths. The output is the file connector. IPC server0 Note: It is not necessary to integrate the host name into the agent name. you must add three Java VM options. Agent Name You should assign a unique name to each SAP J2EE node that is Introscope-enabled. EPD EP. you will only want to activate the agent on the SAP J2EE server nodes. since the host name is assigned automatically to the agent.jar 3. you even cannot use backslash (\) on Windows.jar Example: java -jar CreateAutoProbeConnector. but by : on Unix. For SAP J2EE 6. Using a unique naming convention for all agent installations helps to group agents that belong to the same installation together. not on dispatchers and state controllers. This so-called agent name is assigned by an additional Java VM option (referred to as <AgentName> below).1 Installation Guide for SAP (10/2/2007) Page 22 . Activating the Agent: Set Java VM Parameters After you have created the AutoProbe Connector. XI.40.jar in the same directory. Furthermore. EPQ.Introscope Installation for SAP • Make sure to specify exactly the JVM that is used for launching the J2EE node by passing the JVM directory <java_home> on the command line: java -jar CreateAutoProbeConnector.jar -jvm <java_home> -output connector. on Windows.jar -jvm C:/soft/jdk14 -output connector. even on Windows. SAP suggests the following naming convention for the agent name: <AgentName>=SID_Product_Nodename Where the placeholder mean the following: Placeholder SID Product Nodename Explanation SystemID Identifier for product usage J2EE node name / directory Example EPP. you can use forward slashes (/) on all platforms. Introscope® Version 7.

profile -Dcom.profile -Dcom.00 1.agentProfile=/usr/sap/ccms/wily/sap_IntroscopeAge nt. add the following new java parameters (Windows example): -Xbootclasspath/p:<drive>:/usr/sap/ccms/wily/connectors/connector.profile -Dcom.introscope. Restart SAP server. Select the server to modify.jar:/usr/sap/ ccms/wily/Agent.20 The procedure to add JVM options depends on the startup method for the J2EE nodes.agentName=<AgentName> 3.jar. In the Java Parameters field.agentName=<AgentName> Unix example: -Xbootclasspath/p:/usr/sap/ccms/wily/connectors/connector. Open the file: <drive>:\usr\sap\<J2EE_ENGINE_ID>\j2ee\j2ee_<INSTANCE>\configtool\servi ce.introscope.introscope.agent.jar -Dcom. Check SAP Note 697162 for instructions to set JVM options for your specific startup method.Introscope Installation for SAP Set Java VM Parameters for SAP J2EE 6.jar -Dcom.agentProfile=<drive>:/usr/sap/ccms/wily/sap_Intro scopeAgent.wily.wily.jar -Dcom. 3. Run the SAP J2EE Configtool.wily.wily.wily. 2.jar.20: 1.ini 2. The following procedure is an example in case you use SAP J2EE startup framework for J2EE 6.agentName=<AgentName> Introscope® Version 7.agentProfile=<drive>:/usr/sap/ccms/wily/sap_Intro scopeAgent.1 Installation Guide for SAP (10/2/2007) Page 23 .40 and Netweaver2004s / SAP J2EE 7. Set Java VM Parameters for NetWeaver 04 / SAP J2EE 6.introscope.< drive>:/usr/sap/ccms/wily/Agent.introscope.agent.wily.agent.introscope.< drive>:/usr/sap/ccms/wily/Agent. Append the following commands to JavaParameters (Windows example): -Xbootclasspath/p:<drive>:/usr/sap/ccms/wily/connectors/connector.

jar -agentlib:QJVAIAGENT=/usr/sap/ccms/wily/Agent.profile -Dcom.agentProfile=/usr/sap/ccms/wily/sap_IntroscopeAge nt. 3.agent. Select the server to modify. and see if it contains the lines you entered in the step above.wily. add the following new java parameters (Windows example): -javaagent:<drive>:/usr/sap/ccms/wily/Agent.jar -Dcom. To verify that Config tool changes were made. Set Java VM Parameters for NetWeaver versions based on Java 5 VM 1.wily.introscope. Click the disk button to save.jar -Dos400.profile -Dcom.introscope.introscope.jar: /usr/sap/ccms/wily/Agent.wily. Run the SAP J2EE Configtool.introscope.agentProfile=/usr/sap/ccms/wily/sap_IntroscopeAge nt.agentName=<AgentName> Introscope® Version 7.force. Unix example: -Xbootclasspath/p:/usr/sap/ccms/wily/connectors/ 8.agent. Check for a line beginning with ID<server_id>. open the file: <drive>:\usr\sap\<SID>\<instance>\j2ee\cluster\instance.agentName=<AgentName> 4.jar: /usr/sap/ccms/wily/Agent.JavaParameters.introscope.40 on Windows.1 Installation Guide for SAP (10/2/2007) Page 24 .Introscope Installation for SAP Note: Note that for NetWeaver 6. 7. the slashes for these java parameters must go forwards.wily.wily.profile -Dcom.jitc -Dcom. 5.introscope.agentName=<AgentName> i5/OS example: -Xbootclasspath/p:/QIBM/ProdData/Java400/jdk14/lib/instrumentation. In the Java Parameters field.wily. Repeat steps 2 .agent.jar -Dcom. 6. 2. Restart SAP server.agentProfile=<drive>:/usr/sap/ccms/wily/sap_Intro scopeAgent.jvmti.4 for each server.

Set Java VM Parameters for SAP IPC The procedure to add JVM options for the IPC to enable Introscope is described in SAP Note 886600.jar -Dcom.agentName=<AgentName> 4. Restart SAP server.bat file that launches the servlet engine. A typical location for the file is C:\servletExec AS\se-LHCMS\StartServletExec.agentProfile=<drive>:/usr/sap/ccms/wily/sap_I ntroscopeAgent. Unix example: -javaagent:/usr/sap/ccms/wily/ 8.5 You have to modify the .JavaParameters. Add the following Java VM parameters: -Xbootclasspath/p:<drive>:/usr/sap/ccms/wily/connectors/connector. 6.introscope.wily.1 Installation Guide for SAP (10/2/2007) Page 25 .agent. Click the disk button to save.<drive>:/usr/sap/ccms/wily/Agent.agentProfile=/usr/sap/ccms/wily/sap_IntroscopeAge nt. Check for a line beginning with ID<server_id>.j ar. 5.introscope. open the file: <drive>:\usr\sap\<SID>\<instance>\j2ee\cluster\instance. To verify that Config tool changes were made. Repeat steps 2 .wily. 7.introscope. the slashes for these java parameters must go forwards. Set Java VM Parameters for SAP xMII 11.bat .profile -Dcom.agentName=<AgentName> Further information on integrating xMII into Solution Manager Diagnostics can be found in SAP Note 903825.jar -Dcom. Note that Introscope does not support IPC running in the VM container (VMC) as it is delivered for SAP CRM 5.agent.wily.profile -Dcom.wily.introscope.Introscope Installation for SAP Note: Note that for NetWeaver on Windows.4 for each server. Introscope® Version 7. and see if it contains the lines you entered in the step above.

g. Process = "SAP Netweaver". For this purpose. in the directory /usr/sap/ccms/wily/logs.Introscope Installation for SAP Checking that the Agent is Running 1. Check that the SAP J2EE nodes start up correctly after the restart and that the J2EE applications are available as before.IsengardServerConnectionManager] Connected Agent to the Introscope Enterprise Manager at localhost:6001. You will probably find warnings that the connection to the Enterprise Manager failed – since you have not yet started the Enterprise Manager. launch the Workstation in a browser: http://emhost:8081/workstation You should get a login prompt as shown below. Agent Name = "xxx_server0". Click the plus signs to open subtrees..log. As an alternative. EXAMPLE The last few lines of the agent log file should similar to the following: 12/06/06 01:41:46 PM PST [INFO] [ The file will be named IntroscopeAgent.isengard. Check that the Agent is Running Launch the Introscope Workstation to check if the data provided by the agent arrives at the Enterprise Manager. For each connected agent.1 Installation Guide for SAP (10/2/2007) Page 26 . Search for an Agent log file in the logs subdirectory of the Introscope agent directory.postofficehub. Open the Investigator (Workstation menu New Investigator) to display a tree of all connected hosts and agents.<AgentName>. Open the text file with a text editor and check the last lines. 2. you should find a subtree host SAP Netweaver AgentName in the Introscope® Version 7.DefaultSocketFactory. Use login credentials from the table in Chapter 1 to where <AgentName> is the name that you assigned via the JVM parameter above. Host = "emhost". you can also launch a Workstation that you explicitly installed or WebView (http://emhost:8081/webview).

Please check the following: If your managed system is running SAP J2EE. Some nodes will only appear after first use.1 Installation Guide for SAP (10/2/2007) Page 27 . Depending on the type of the managed system. Introscope® Version 7.Introscope Installation for SAP Investigator that looks similar to the screenshot below. so this may indeed be missing. For example. some tree nodes may be missing. you should at least have SAP J2EE. CPU is only available on some Windows and Linux platforms. Servlets will only appear after the first servlet has been executed.

Then you will be guided through the installation by a wizard. Keep No for Configure VM Settings and enter the host name of the Enterprise Manager in the field Workstation Default Host.SAR 2. remove the file installer. Introscope® Version 7. click Install to launch the installation. If you want to install it on Linux.exe in the installation in the directory where you launch the installer.Introscope Installation for SAP 5 Workstation Installation If you decide to explicitly install the Introscope Workstation on Client PCs. Alternatively. Launch the Workstation: a.1 Introscope Workstation b. a. (installation with wizard) Select a target installation directory of your choice.1 Installation Guide for SAP (10/2/2007) Page 28 . the installation will be placed in the folder c:\Introscope71. (Silent installation) By default. proceed as described in this section. 1. If desired. Extract the downloaded Workstation installer: sapcar –xvf SAPISWS71. 3.1windowsSAPExpertCenter. via the Start Menu: Introscope 7. by directly starting the file Introscope Workstation. Installers are available for the following platforms: Windows 32bit Windows x86_64 Linux IA32 Linux x86_64 The installation is described here for –DUSER_INSTALL_DIR=d:/usr/sap/some/dir b. Finally. remember to set the DISPLAY before launching the installer. pass a different target directory as a command line parameter: IntroscopeWorkstation7. If you keep the file installer. the installation will proceed silently. Launch the installer.

Installing the Introscope .pbl sap_IntroscopeAgent_Duet.NET Applications • Installing the Intoscope .NET Agent rather than the current version.1 Installation Guide for SAP (10/2/2007) Page 29 .profile sap_IntroscopeAgent_custom.NET Agent with Duet.NET Agent has been installed on a machine in your environment.profile Introscope® Version 7.NET Agent • Set up user permissions for Agent Directory • Configure Introscope .NET Agent.SAR to a temporary directory.exe webdav. Check if they are installed by having a look to the Microsoft IIS Manager. You have to see there the following three application pools: • AzManSvcWebAppPool • IBFWebAppPool • RequestHandlerAppPool Previous Agents If a previous version of the . There are five files in the archive: introscopeDotNetAgentInstall7.P1.Introscope Installation for SAP 6 Introscope-Enabling Duet ASP. Wily recommends the previous version of the Agent be uninstalled before you install the new version of the .0.NET Agent Extract the Installer Archive Extract the installer archive ISDOTNET70_01. The following steps are required: Requirements Before starting the installation of the Introscope . Note: If you wish to use an older version of the .pbd sap_default-full. you must uninstall the current version of the Agent first before installing the older version.NET Agent the Microsoft Duet Server Components have to be installed and configured.NET Agent settings This chapter describes installing and configuring the Introscope .

Introscope® Version 7.0. usually: <drive>:\usr\sap\ccms\wilydotnet Note: If there is no SAP component installed on this server you will not find the NetWeaver CCMS directory (<drive>:\usr\sap\ccms).net agent perform the following steps: 1. The installation directory is referred to through this guide as the AgentHome directory. Click Next.P1.exe file.NET agent into a wilydotnet subdirectory of the NetWeaver CCMS directory. Double-click the introscopeDotNetAgentInstall7. The Choose Install Folder page is displayed. The Introduction page is displayed.1 Installation Guide for SAP (10/2/2007) Page 30 .Introscope Installation for SAP Run the Installer To install the . The directory will be created by the installation. 2. Install the .

usually: <drive>:\usr\sap\ccms\wilydotnet\wily Introscope® Version 7. The .NET Agent is installed and the Installation Complete Page is displayed. Confirm the .profile sap_IntroscopeAgent_custom.NET agent was installed correctly by checking for the existence of the following directories in the AgentHome directory: \install \UninstallerData \wily Manual Copy of Files Copy the following four files which are included in the Installer Archive: webdav. Click Install.profile Into the \wily subdirectory of the AgentHome directory.pbd sap_default-full.Introscope Installation for SAP 3.pbl sap_IntroscopeAgent_Duet. 4.1 Installation Guide for SAP (10/2/2007) Page 31 .

The Properties window for the folder is displayed. Introscope® Version 7. Verify that the Administrator and Create Owner user names have Special Permissions. are running with the user “NETWORK SERVICE”. For the Agent and AutoProbe to run. which run the ASP. 2. By default the w3wp. In Windows Explorer.1 Installation Guide for SAP (10/2/2007) Page 32 . 3.NET Duet applications. and the bin and ext subdirectories. right-click on the <AgentHome>\wily folder and select Properties.exe processes. 4. The Selected Users or Groups dialogue box is displayed. the user authorization token executing the worker process must have permissions for the <AgentHome>\wily directory. Click on the Security tab of the Properties window. Verify Minimum User Permissions To verify the minimum user permissions: 1. the installation directory <AgentHome>\wily is created with permissions in accordance with the machine policy. A dialogue box similar to this is displayed. Click the Add button.Introscope Installation for SAP Set Up User Permissions for Agent Directory When you install the Agent.

6. Verify that the user has the following permissions: Full Control Modify Introscope® Version 7.1 Installation Guide for SAP (10/2/2007) Page 33 . 7. Enter the name “NETWORK SERVICE” in the “Enter the object names to select” field. Click the Check Names button to validate the user. The Permission Entry dialogue box is displayed.Introscope Installation for SAP 5. Click the OK button after the user name is validated and underlined.

9.Introscope Installation for SAP Read & Execute List Folder Contents Read Write 8. and click OK. Introscope® Version 7. Click the Advanced button.1 Installation Guide for SAP (10/2/2007) Page 34 . The Advanced Security Settings for Wily dialogue box is displayed. Click the “Replace permission entries on all child objects with entries shown here that apply to child objects” check box to propagate permissions to the child directories.

DEFAULT Enter either the host name or IP address of the machine where Enterprise Manager resides.enterprisemanager. Default setting is 6001.transport. You will need to configure the host name or IP address and port of the machine where the Enterprise Manager resides: 1.tcp. introscope. You need to replace the existing IntroscopeAgent.profile to IntroscopeAgent. Rename the sap_IntroscopeAgent_Duet.profile.DEFAULT The value should be the port on which the Enterprise Manager listens for Agent connections.enterprisemanager. Locate the property. Replace IntroscopeAgent.profile. introscope. 2.profile file. 3.transport.profile 2.NET Agent Settings The following section details how to configure the Introscope .profile you copied to the \wily subdirectory of the AgentHome directory is configured for the use with Duet and restricts the monitoring to only Duet related .profile Configure Agent to Enterprise Manager Connection Properties The connection configuration to the Enterprise Manager you need to configure in the IntroscopeAgent.profile: 1.profile The sap_IntroscopeAgent_Duet.NET processes and application pools. Open the <drive>:\usr\sap\ccms\wilydotnet\wily\IntroscopeAgent. Introscope® Version 7. Save changes to the IntroscopeAgent.NET Agent in a Duet Scenario.Introscope Installation for SAP Configure Introscope .port. Rename the exitsing by the sap_IntroscopeAgent_Duet. Locate the property.tcp.1 Installation Guide for SAP (10/2/2007) Page 35 .profile to original_IntroscopeAgent.agent. 4.

NET connected successfully to the Introscope Enterprise Manager.NET Agent is running To verify the minimum user permissions: In Windows Explorer. Check that the IIS start up correctly after the restart.DefaultDomain.log and IntroscopeAgent. Search for the Agent log files.<Duet application name>. usually: <drive>:\usr\sap\ccms\wilydotnet\wily The files will be named IntroscopeAgent.1 Installation Guide for SAP (10/2/2007) Page 36 . 2. Some post setup tasks are necessary. Restart IIS To restart the IIS open a command prompt window and execute the following command: iisreset /restart Check that the .Introscope Installation for SAP Post Setup Tasks After the installation and configuration of the Introscope .NET Agent it is not running. They will be located in the \wily subdirectory of the AgentHome directory. Introscope® Version 7.log Open the files and check if the . right-click 1.

and to collect TREX performance data. All of the configuration steps in this section apply to this file.DEFAULT=6001 Introscope® Version 7.enterprisemanager.tcp.Introscope Installation for SAP 7 Environment Performance Agent Installation Note: The recommended procedure to install and customize the EPAgent is to use the setup wizard provided in Solution Manager Diagnostics.SAR with the command below.4 VM. in the subdirectory config.1 Installation Guide for SAP (10/2/2007) Page 37 .agent. The setup procedure includes the following steps: • Customize the EPAgent connection parameters • Select plugins that should be activated • Customize the individual plugins • Launch the agent and check proper operation Extract the Files Extract the files from the archive ISEPA71. sapcar –xvf ISEPA71. If you do not have Solution Manager Diagnostics available follow the manual procedure described below.agent.SAR Configure the EPAgent Configuration of the Epagent is done via the configuration file IntroscopeEPAgent. The “Environment Performance Agent” (EPAgent) is used to collect performance metrics from different sources that do not require bytecode instrumentation. The agent runs as a stand-alone Java process which requires at least a Java 1. All extracted files will go to a subdirectory epagent. monitor GC data in detail. SAP currently provides plugins to monitor the operating system based on saposcol.tcp. The recommended location for extracting the files is the directory /usr/sap/ccms. set the two connection properties for the Enterprise Manager connection to the same values that you used for the “normal” agents in Chapter such that all files will go to directory /usr/sap/ccms/epagent.transport.DEFAULT=emhost introscope. Customize Connection Properties At the bottom of the configuration file. unless stated otherwise.

names=SAPOSCOL. introscope. The data will appear in two locations then: hostname|SAP EPAgent|SAP GC|agentname and hostname|SAP Netweaver|agentname|SAP GC.names= Customize the Plugin SAPOSCOL The SAPOSCOL plugin periodically polls performance data from the saposcol process.Introscope Installation for SAP Select Plugins to Run Plugins are activated by listing their names in one of the two properties below.epagent.out Customize the Plugin SAP_TREX The SAP_TREX plugin can retrieve performance counters from TREX -> System Monitoring and Alert Management -> Media Library -> Documentation -> SAPOSCOL: file in the following format: file. Customize the Plugin SAP_GC The SAP_GC plugin monitors log files from J2EE nodes and periodically reports data about garbage collection activity. as below. introscope. Additional info on saposcol can be found on the Service Marketplace: http://service.epagent. Installation.sup. so the user running the EPAgent needs permission to execute For SAP J2EE 6. one line must be added to the SapGcScanner. or include saposcol in the PATH for the user that runs the EPAgent.out file.stateful.oscol.40 and ControllerXml /usr/sap/SID/SYS/exe/run/saposcol The plugin is calling saposcol with the path you specify above to retrieve monitoring data. located in the subdirectory epaplugins/sap.1 Installation Guide for SAP (10/2/2007) Page 38 . The plugin is controlled via a separate configuration file SapGcScanner.P40_server0=C:/usr/sap/P40/JC00/work/std_server0.plugins.00. Example: file. Either pass it as parameter to the plugin class. the plugin needs the path to saposcol.SAP_GC introscope.stateful. By default.class=com. It needs two support files to be copied from epaplugins/sap to the TREX installation: Introscope® Version 7. monitoring of the files std_servern. SAPOSCOL and SAP_GC are active. Agentname should be the name of the Introscope agent that monitors the J2EE node whose log file you want to monitor.out is recommended and supported.<agentname>=<full path to file>.P40_server1=C:/usr/sap/P40/JC00/work/std_server1. To allow communication to saposcol. and Operation.SAPOSCOL. Make sure you list the plugins in the correct category (stateful or stateless). For each monitored file.

adapt the paths in this file. Introscope® Version 7.bat Unix: Copy python_epa.bat to C:/usr/sap/SID/TRXxx/python_epa. You have to add it to the stateless plugin list (see above).stateless.epagent. adapt the path to the python_epa. start the script RegisterEPAService. Copy serviceLoad. To create the service.SAP_TREX.bat.command=/usr/sap/SID/TRXxx/python_epa . edit the property wrapper. If you do not have a java.4) in your PATH. After copying the files. After creation.conf.epagent. Customize the Plugins for Windows Performance Counters There are currently three plugins to collect Windows performance counters with Introscope: Plugin Name SAP_WMI_MSS SAP_WMI_DOTNET SAP_WMI_IIS Monitored Component MS SQL Server Dot Net IIS Activate the plugins by listing them in the stateless to /usr/sap/SID/TRXxx/ script in the agent config file: to /usr/sap/SID/TRXxx/exe/python_support and /usr/sap/SID/SYS/exe/nuc/NTI386/python_support (backup the old files before).SAP_TREX. Copy serviceLoad.Introscope Installation for SAP Windows: Copy After copying the files.exe (at least java 1.command in config/ Note that this plugin is not active by default. Run the EPAgent Running the EPAgent on Windows On Windows the EPAgent should be run as service. adapt the path to the to C:/usr/sap/SID/TRXxx/exe/python_support and C:/usr/sap/SID/SYS/exe/nuc/NTI386/python_support (backup the old files before).java.stateless. adapt the paths in this file. start the service via the services MMC plugin.1 Installation Guide for SAP (10/2/2007) Page 39 .command=C:/usr/sap/SID/TRXxx/python_e pa.bat script in the agent config file: introscope.

Introscope® Version 7. the Investigator view of the Workstation should look similar to the screenshot below. Check Proper Operation If your setup was successful.1 Installation Guide for SAP (10/2/2007) Page 40 .4 VM in the shell script before.Introscope Installation for SAP Running the EPAgent on Unix Use the supplied shell script epagent./ & You may have to adapt the path to a java to launch the agent in nohup mode: nohup .

Modify JVM options of J2EE server nodes for WebView.Introscope Installation for SAP 8 Installing and Configuring WebView with SAP NetWeaver Remember that in most cases there is no need to run WebView on NetWeaver since the Enterprise Manager already hosts a WebView instance. This chapter describes installing and deploying WebView on the Java stack of SAP NetWeaver. you’re ready to start installing and configuring WebView. Undeploy old version of WebView.EAR file in the SAP NetWeaver application server through which you will be running WebView. 2.00). 3. Deploy the WebView . Introscope® Version 7. Review Chapter 1 to make sure you want to deploy WebView on NetWeaver.40 or 7. This process consists of the following steps: 1.1 Installation Guide for SAP (10/2/2007) Page 41 . Information is provided in the following sections: • System and Version Requirements • Reviewing Installation and Configuration Process • Installing and Configuring WebView with SAP NetWeaver System and Version Requirements Introscope Version Introscope Enterprise Manager and Introscope WebView must have the same version! NetWeaver Version WebView can be deployed on the Java stack of NetWeaver 04 or 2004s (SAP J2EE version 6. Reviewing Installation and Configuration Process After you’ve checked the system requirements and collected the appropriate access and configuration information for your deployment.

1 Installation Guide for SAP (10/2/2007) Page 42 . Undeploying Previous Versions of WebView 3. 4. Introscope® Version 7.awt. 3.awt. Start SDM 1.volatileImageBufferEnabled=false -Djava.wilytech. In the Java Parameters field. Click the disk icon to save.headless=true -Dswing. Platform and JVM Windows Solaris Linux HP UX AIX Required Options -Dsun. Start SDM via the command /usr/sap/<SID>/JC00/SDM/program/RemoteGui.noddraw=true Make sure that -Djava.webview. Select the deployment tab.java2d. Connect to the running SDM server.headless=true is not set! -Djava. Important: Restart the J2EE Server before continuing with deployment.headless=true -Dswing.headless=true -Dswing. Deploying the WebView Package 5.awt. Open the SAP J2EE config tool.Introscope Installation for SAP Installing and Configuring WebView with SAP NetWeaver Configuring SAP NetWeaver for WebView Deployment Depending on the platform you have to add special JVM options for running WebView. 4.volatileImageBufferEnabled=false -Djava. add the parameters from the table above for your operating system.awt. Select the undeployment tab and undeploy com. Select the server to modify. Use the table below to choose the right options and revisit SAP Note 797147 to check for latest updates. 2.volatileImageBufferEnabled=false Please check FAQ! To configure SAP NetWeaver for WebView deployment: 1. 2.

From the Introscope CD. 2. add the file WebView7.. 7.ear for deployment.1netweaver. Launch WebView via Solution Manager Diagnostics (Menu Entry J2EE Server Analysis) or directly via URL http://host:5xx00/webview. Verifying Successful WebView Deployment After deploying WebView.1 Installation Guide for SAP (10/2/2007) Page 43 .Introscope Installation for SAP 6. verify that WebView is starting and has connected to the Enterprise Manager. Make sure that the Enterprise Manager is running (see the section. Checking That Introscope Is Running Properly). Click to open some so-called dashboards and check if some charts are displayed. Introscope® Version 7. You should get a login screen from the WebView application and a message below the login frame similar to the following: This WebView instance is connected to the Enterprise Manager on localhost. Note: These instructions assume you are installing WebView on the same machine as the Introscope Enterprise Manager. 3. The SDM screen should look similar to the screenshot below. Start deployment. The file is located in the folder webview. Log in to WebView with one of the user accounts listed in Chapter 1 and open the Console. 1. There are 3 agent(s) reporting.

enterprisemanager. 2. -Dcom. Open the file. -Xbootclasspath/p: <some path>/wily/connectors/connector.jar (Java 5 only) 2. You can change this value to any desired port: 1.jmxservice) in case it is still present from previous Introscope versions. -javaagent:<some path>/wily/Agent. config/IntroscopeEnterpriseManager. Use SDM to undeploy the JmxService helper application (com.3.agent. Introscope® Version 7. Restart the affected J2EE instances for the changes to become effective. 1. -Dcom. Change the value of property introscope.profile c.jar: <some path>/wily/Agent. 4.Introscope Installation for SAP 9 Additional Installation Options This chapter covers additional customizing steps of the Introscope Installation: • Changing the Agent port from 6001 to other values • Uninstalling Introscope • Setting up domains • User Management • Activating Leak Hunter • Running WebView and Enterprise Manager on Different Hosts Change the Agent Port The Enterprise Manager by default listens on TCP port 6001 for agent connections.port. Remove the Java VM options for Introscope from the J2EE nodes that you instrumented before. Remember to change the property in the sap_IntroscopeAgent. The following options should be removed: a. Uninstalling Introscope Uninstalling Introscope Agents 1.4 only) b.wily.agentProfile=<some path>/wily/sap_IntroscopeAgent. 3.channel1 to the desired port.1 Installation Guide for SAP (10/2/2007) Page 44 . 3.introscope.wily.agentName=<AgentName> Save changes and close the file.profile to the same port.jar (Java 1.

the SuperDomain. SAP recommends defining one domain for each system or for each main instance (in Solution Manager Diagnostics terms). belonging to the same domain.xml. Uninstalling WebView on Netweawer 1. 2. 3. On Windows only: Call the script DeregisterEPAService. You can pick agents for a domain based on the host name and on the agent name. Select Introscope and click change/remove to launch the Wizard.wilytech. 3. Uninstalling the Enterprise Manager 1. Remove any remaining files from /usr/sap/ccms/wilyintroscope.webview if you still have a copy of WebView deployed on NetWeaver. Uninstalling Environment Performance Agents 1. there is only one domain. EPP).Introscope Installation for SAP 4. On other platforms: Stop the Java VM containing the EPAgent. Delete the complete directory containing the EPAgent installation. Use SDM to undeploy the application com. Delete the directory <some path>/wily (or wherever you put the agent files).1 Installation Guide for SAP (10/2/2007) Page 45 . By default.bat to stop and unregister the Windows service. which contains all agents. Step 1: Adapt the domains. Windows only: Call the wizard to uninstall Introscope: Start Control Panel Add or Remove Programs. e. Example: Assume you want to create two domains EPP and EPQ for the productive and the QA Enterprise Portal. Windows only: Call the batch file DeRegisterEMservice. Setting up Introscope Domains Introscope agents can be organized into so-called domains. Your agent names contain the System id (also EPQ.g.bat to remove the Windows Service 2. Click Next to continue the uninstall. You can use this feature to group agents which are correlated.xml file on the Enterprise Manager: Introscope® Version 7. Domains are defined in the Enterprise Manager by the configuration file config/domains.

Generate the MD5-encoded password by the script MD5Encoder: MD5Encoder Y Y:57cec4137b614c87cb4e24a3d03a3e0 2. located in the subdirectory config/ of the Enterprise Manager.xml in the same directory. Add permissions for the user to the Superdomain in the domains.xml before the final </users> line. Step 3: Restart the Enterprise Manager to activate the changes. create one subdirectory for each domain. Permissions are controlled by the file domains.Introscope Installation for SAP Step 2: Replicate the management modules: Step 2a: In the directory config/modules. Step 2b: copy all management modules from config/modules to each subdirectory. using the generated password string (the part after :) as password: <user name="X" password="57cec4137b614c87cb4e24a3d03a3e0" /> 3. To create a new user X with password Y. Step 4: Check the Explorer in Workstation or WebView to see if the domains appear and if the agents are assigned to the right domain.xml file: <grant user="X" permission="read" /> <grant user="X" permission="run_tracer" /> Introscope® Version 7.xml. proceed as follows: 1. Add a new line to users.1 Installation Guide for SAP (10/2/2007) Page 46 . User Management User accounts must be maintained in the file users. Note that the SuperDomain must always be the last entry in the domains file.

During this period.autoprobe.Introscope Installation for SAP Note: If you do not have a full license for Introscope.directivesFile property in the agent profile. For instance. the amount depending on how many Java Collection classes the NetWeaver JVM uses. the Introscope agent will use more memory. Look for a new LeakHunter node under agent in the Investigator window of the Introscope Workstation.leakhunter. 3.leakhunter. If your JVM has spare memory available after running LeakHunter with this set to false. separating it from other JARs or PBDs with a comma.enable=true in the agent profile used for the JVM with potential leak.. you cannot use permission=”full” here! Activating Leak Hunter Leak Hunter is an additional Introscope feature for detecting memory leaks that is by default disabled.leakhunter. Leakhunter may have substantial impact on the Java memory footprint and on the response time for any Java VM where you activate Leakhunter: Only activate Leakhunter when needed. Add sap_leakhunter. Set introscope. To activate Leakhunter proceed as follows: 1.jar to the introscope. It may furthermore be advisable to increase the Java heap before activating Leakhunter to compensate additional memory requirements of Leakhunter.collectAllocationStackTraces set to false since setting it to true requires more memory. e. if you restart the JVM at 5pm but don’t expect to have significant load on the JVM until 9am the next day. If you knew you were going to run significant load through the JVM right after restarting. 4.agent. you could set the timeout to 120 or 240 minutes. you must configure WebView to connect to the Enterprise Manager on the remote host. Set the introscope. 6. 5. then you would set it to 1140 minutes (19 hours) so that LeakHunter searches for leaks until 12pm the next day giving 3 hours of leak hunting during active use. Use the Visual Adminstrator of SAP J2EE: Introscope® Version 7.1 Installation Guide for SAP (10/2/2007) Page 47 . 2.timeoutInMinutes property to the number of minutes that you want LeakHunter to look for new leaks.g.agent. if you discover permanently increasing memory consumption in spite of several full garbage collections.agent. Set to the shortest period that is long enough to insure that all application funcationality gets invoked within the active leak hunting window. Leave introscope. Restart the JVM with the suspect memory leak. Running WebView and EM on Different Hosts (WebView on NetWeaver only) When running WebView on a different host than the Enterprise Manager. you could try setting to true if you feel you need to see the stacktraces to understand the source of your leak.

10.wilytech. Launch the Visual Administrator and connect to the SAP J2EE installation running WebView click the x to close the Window Introscope® Version 7. open the tree by clicking on the + and select the first subentry. Change the value of this property from localhost to the IP address or host name of the remote host running the Enterprise Manager: Select the tab “Context Parameters”. Search for the application wilytech.Introscope Installation for SAP 6. Click View on the right hand side to get a popup. 9. You will find the parameter introscope. Navigate to Server Services Web Container 8.1 Installation Guide for SAP (10/2/2007) Page 48 .webview.webview.tcp. 11.

Sign up to vote on this title
UsefulNot useful