Introscope Version 8 Installation Guide For SAP

March 2010

Introscope Installation for SAP

Contents
Contents ........................................................................................................................................... 2 1 Installation Overview ............................................................................................................... 3 2 Upgrading from Previous Versions to Introscope 8 ................................................................... 7 3 Installing the Introscope Enterprise Manager .......................................................................... 10 4 Introscope-Enabling SAP J2EE Systems ................................................................................ 19 5 Workstation Installation ......................................................................................................... 32 6 Environment Performance Agent (De)Installation .................................................................. 34 7 Additional Installation Options ............................................................................................... 35

Introscope® Version 8 Installation Guide for SAP (5/3/2010)

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 8 • Installing Introscope Enterprise Manager • Introscope-enabling SAP J2EE Systems (Agent Installation) • Optional: Installing Introscope Workstation • Environment Performance Agent (De)installation • Optional Configuration Steps

Introscope Overview
Introscope is an application management solution 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. The Right to View (RTV) version of CA-Wily Introscope is a restricted, read-only form of the full product and is bundled with SAP Solution Manager. With the RTV version, support is limited to products that are licensed and supported by SAP. The instrumentation, dashboards, Probe Builder Directives (PBD’s), management modules, and Smartstor data contained within the RTV version of CA-Wily Introscope as provided by SAP is the intellectual property of SAP. Use of these functions is restricted by SAP and may only be used in an unrestricted manner by licensing SAP Extended Diagnostics by CA-Wily from SAP.

Introscope® Version 8 Installation Guide for SAP (5/3/2010)

Page 3

you can install the Introscope Workstation on the Enterprise Manager host or any client PC. b. It runs as part of the SMDAgent in the SMDAgent process to collect data on operating system level. The EPAgent is not supported any more. Requires Java 5 to be installed. For this reason. GC logs. • Host-Level Introscope Agent (on the managed systems) The so-called Introscope Host Agent is installed once per host. The Host Agent generates less load on the Enterprise Manager than a normal agent. Deciding About the UI for Introscope There are three different options to access Introscope: 1. from saposcol. More details on Enterprise Manager Sizing and self-monitoring can be found in the FAQ attached to SAP Note 797147. No explicit installation of the Workstation is necessary. See the next section for recommendations about the UI for Introscope. Only in exceptional cases manual installation is necessary. and TREX. Typically. you can install the Enterprise Manager on a separate host. as described below.g. Introscope Workstation: Swing-based client user interface. Use Java WebStart to download the Workstation on demand from the Enterprise Manager. Alternatively. • Optionally. the default configuration using 512MB Java heap (about 1GB main memory) will suffice.. for up to ten agents. the agent runs within the Java process of the monitored system. ABAP instances. Explicit installation on the client PC on which you want to use it (see Chapter 5). 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. For about twenty additional agents. add 512MB of Java heap to a total of 1024MB (allow 2GB main memory). For every new start of the Workstation the cached version is checked against the Enterprise Manager Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 4 .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. • Introscope Java Agent (on the managed systems) The setup of the Java agent is typically done centrally via a setup UI in Solution Manager Diagnostics. The workstation will be downloaded only once and is then cached on the client PC. In previous releases. The EPAgent is now replaced by the host-level agent. default URL: http://emhost:8081/workstation. it should not be included in the memory sizing calculation above. e. the Introscope Environment Performance Agent (EPAgent) took the role of the host-level agent. full functionality a. After activation by restarting the Java VM. The Host agent is configured automatically by the SMD setup wizard for managed systems.

you can add live_agent_control and historical_agent_control permissions to the Admin user if you want. Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 5 . 2. Install the Introscope Enterprise Manager on the central monitoring system and add the management modules. 3. In some details limited functionality. you can use the following default credentials to access Introscope: User Admin Guest Password Admin89 guest12 Access Rights read. Download installation files from SAP Service Marketplace. 5. Please refer to the User Management section in Chapter 7 for details. Obtain the Latest File Versions SAP Note 797147 SAP Note 797147 is the central entry point for up to date information regarding the installation of Wily Introscope. Review the latest version of this note before you start the installation. A list of frequently asked questions for troubleshooting the installation is also attached to this note. You may also decide to install the workstation explicitly on your client PC (1a). In general using the Workstation should be preferred to WebView since it is more powerful. run_tracer read Furthermore. a new version is downloaded automatically.Introscope Installation for SAP and. WebView is available by default on the Enterprise Manager (no installation necessary). 2. Install the Introscope Java Agents and Host Agents on managed systems. Optional: Install the Introscope Workstation. default URL: http://emhost:8081/webview. Introscope WebView: Browser-based user interface. 4. Check SAP Note 797147 for latest updates to the installation procedure and to this document. if the Enterprise Manager was updated. The binaries are then only downloaded once and after that cached on the client PC. Introscope Access After installation. The most convenient option is to use 1b (Launch Workstation via Java Webstart). uses the Microsoft Silverlight browser plugin. The Installation Process The Introscope installation process consists of the following steps: 1. You also find a list of frequently asked questions attached to the note.

for a UNIX system (including IBM i) Save the files in the same directory as the Introscope installer executable. To download the third-party external component package files: 1.2. Go to http://opensrcd. you must download these files to your network.com/ips/osgi/ 2.2.2.windows. The installer will then automatically locate this file during the installation process. Before starting an installation or upgrade.tar.unix.sap. for a Windows system osgiPackages.2.ca. Download the Latest Updates from the Service Marketplace Download all files listed in SAP Note 797147 from the SAP Service Marketplace.v1.txt The osgiPackages archive appropriate for your system: o o osgiPackages.Introscope Installation for SAP Download Third-Party External Component Package from CA Wily The Introscope 8. Note: The installer does not validate whether you have downloaded the correct archive for your platform. 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.com/instguidesNW04 -> Operations Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 6 . Be sure you download and specify the correct archive for your platform.v1.zip. Download the following files from the subdirectory for current release (introscope 8.2 installer requires third-party external component package files.2): eula.

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

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

Introscope Installation for SAP default reached via the URL http://emhost:8081/webview. Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 9 . The former URL http://smdhost:5xx00/webview is no longer valid for this operating mode.

download the file SAPISEM*.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.2.0aix64SAP.0linuxAmd64SAP. you will run the installer file and add some SAP customization (management modules.SAR from the corresponding folder on the Service Marketplace (see Note 797147 for the exact location). The first table below lists the platforms for which a platform specific installer with a bundled Java VM is available.2.0hpuxIA64SAP.2.bin introscope8.2.bin introscope8.2. Choose the Enterprise Manager Installer File Depending on the operating system on which you want to install the Enterprise Manager. Operating System AIX5 64bit IBM i 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 introscope8. scripts.2. To install the Introscope Enterprise Manager.2. different installation files must be chosen.2. If you find your operating system listed here. The file names listed below may vary slightly for patch updates to the Enterprise Manager.2. on Unix operating systems do not use the root account to launch the installer. In particular. etc.0hpuxSAP.0os400SAP.2.0linuxSAP.2.).2. A common best practice is to use the sidadm user of the Solution Manager installation to install and run the Enterprise Manager.jar Introscope8.bin Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 10 .bin introscope8.bin introscope8.

com/developerworks/java/jdk/linux/do wnload.0windowsSAP.jsp Click on JRockit 5.0 Linux on Power 64bit Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 11 .0solarisSAP. Note.2. If you want to run the Enterprise Manager on a 64 Java VM. Operating System Linux on IA 64bit Java 5 VM Download Link http://commerce. you can use the generic installer for the operating systems listed below.exe introscope8.com/products/weblogicjrockit/jro ckit_prod_fam-bea. select 64-bit iSeries/pSeries in column J2SE 5.ibm.0windowsitanium64SAP. Launch the OS-independent installer The operating system independent installer is contained in the file SAPISEM*.SAR of the folder #OS independent on the Service Marketplace.0windowsAMD64SAP.2. Platform Independent Introscope Installer If you do not find your operating system in the table above.2.2.2.html.2. however. that you will not see any benefit from switching to a 64-bit VM unless you have to extend the Java heap (-Xmx) to a value that is not possible with a 32-bit VM – just the opposite: When switching to a 64 bit VM the same EM configuration will have less capacity than before due to the 64-bit intrinsic overhead. Agree to terms. Installation includes one additional step then: 1. Download JRockit 5.2.Introscope Installation for SAP Solaris on SPARC 32bit Solaris on SPARC 64bit* Windows IA32 Windows x86_64 64bit Windows on IA64 introscope8. you can exchange the Java VM after the installation.bin introscope8.2.64-bit) http://www.exe introscope8.0 R27 JDK Linux (Intel Itanium .bea. See below for details.0.exe * For Solaris SPARC and HPUX on PA RISC only 32-bit installers are available. Install a Java 5 VM 2.

Introscope Installation for SAP Linux on zSeries 64bit http://www. you will get an graphical installation wizard. because your SAP installation is located on a different Windows drive.com/developerworks/java/jdk/linux/do wnload.properties file is in the same directory as the . select Solaris x86 Platform and Solaris x64 Platform .properties. The installer runs in the background as it installs Introscope components. When launching the installer. and doesn’t provide any feedback.bin / .jsp. 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 / IBM i: /usr/sap/ccms/wilyintroscope If you want to change this directory.0 http://java.J2SE(TM) Development Kit 5.jar file! If the installer.properties are located. including Windows! Alternative 1: Set the Installation Directory via Command Line Option 1.g.SAR As a result you will find two files: The file installer..exe / . e. select 64-bit zSeries (S/390) in column J2SE 5. The Introscope installer is invoked from the command line and runs “silently”. Open a command prompt and go to the directory where the installer file and the file installer.properties file does not exist.e.g. Add the option –DUSER_INSTALL_DIR=<installation directory> to the invocation of the installer (see below). getting its input from the response file installer. depending on your platform. . Note: Use slash (/) as path separator for all platforms. Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 12 . accept license Solaris on x86_64 64bit Extract the Introscope Installer Extract the SAR file with the following command: SAPCAR –xvf SAPISEM*. you can check the results in the installer logs. make sure the installer.sun. use one of the following alternatives.html.. After installation.com/javase/downloads/index_jdk5. The Introscope installer will perform an automated install of Introscope components.ibm.properties which configures the installation procedure and one of the installer files mentioned above. 2.0 latest Update.

v1.2. Start the Installer 1.0windows. read the license. Add the External Component Package Copy the External Component Package Copy the two files that you downloaded from CA Wily’s FTP server to the directory which contains the installer (see Chapter 1. for a UNIX system (including IBM i) Accept the License Open the file eula.txt The osgiPackages archive appropriate for your system: o o osgiPackages. double-click on the introscope8.0windows./introscope8.2. enter the desired location in the USER_INSTALL_DIR property.SAP.windows.tar. If the license is not accepted installation will fail.SAP.properties 1. for a Windows system osgiPackages. Locate the USER_INSTALL_DIR property.bin • For the IBM i installer you first need to determine the JDK that you will be using. Here is a list of Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 13 . and modify the last line to read LGPL=accept.2.exe –DUSER_INSTALL_DIR=d:/usr/sap/ccms/wilyintroscope. Depending on the operating system version you are using you should prefer IBM IT4J (J9) over the IBM Classic JVM. Note: The instructions in this guide will use examples relative to the default installation directory.zip.2. Wily introscope requires a JDK 5.2.0solaris.exe • For any other platform-dependent installer. The following files should be copied: eula.properties in a text editor. You may have to set the right permission before you can launch the installation: .2.0windows. Launch the installer for your platform using the appropriate command: • For Windows.2. Open the file installer. Download Third-Party External Component Package from CA Wily). 2. To change the install directory location.2.SAP. Alternative 2: Edit installer. or launch from command-line with the following command: Introscope8.txt in a text editor.v1. use the command in the following example.unix.SAP.exe.Introscope Installation for SAP introscope8.

log. 3.Introscope Installation for SAP the JAVA_HOME directories and the according IBM I product options that need to be installed: IBM i 6.0os400SAP. IBM i) OR the location you specified.2. 7) Then.properties must be located in the current directory where you launch the installer. 2. 384 Successes 0 Warnings 0 NonFatalErrors 0 FatalErrors Note: The number of successes may be different than what is shown in this example.5 –classpath introscope8.1: /QOpenSys/QIBM/ProdData/JavaVM/jdk50/64bit/jre (5761JV1 Opt. Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 14 .jar install Note: In any case. 8) i5/OS V5R3: /QIBM/ProdData/Java400/jdk15 (5722JV1 Opt. Verify that the Introscope directory exists at: • <drive>:\usr\sap\ccms\wilyintroscope (Windows) • /usr/sap/ccms/wilyintroscope (Unix.0otherUnixSAP.jar install • For the platform independent installer that does not contain a bundled Java VM use the following command. To confirm installation was successful: 1. /some/path/java refers to the Java 5 VM that you installed as described above: /some/path/java –classpath introscope8. You can avoid copying the installation file itself by using the complete path to the executable. Verifying Installation. Verify that the following lines appear in the file: Summary ------Installation: Successful. 9) i5/OS V5R4: /QOpenSys/QIBM/ProdData/JavaVM/jdk50/32bit/jre (5722JV1 Opt.2. Open the file.2. /usr/sap/ccms/wilyintroscope/install/Introscope_<version>_InstallL og.2. Verify installation using instructions in the following section. 2. run the following command in QSH: <JAVA_HOME>/bin/java –Djava. the configuration file installer. Verifying Installation The installer does not give confirmation of successful installation on the console.version=1.

java.option.java.conf: Used when Enterprise Manager is running as Windows Service on Windows platforms. i. The property wrapper.additional to modify Java VM parameters.e.sh: Used when Enterprise Manager is launched on IBM i.current. Set the Java VM parameter –Djava. In particular. set the Java heap size properties based on the JVM o o IT4J (J9): -Xms512m -Xmx512m IBM Classic: -Xms64m -Xmx2048m Add the following parameters: -verbose:gc -Djava. Otherwise. runem. Increase the value of adapt wrapper. Adapt the JVM_ARGS environment variable. 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 o Enter the path of a separately installed Java 5 VM for platforms where you used the platform independent installer.Introscope Installation for SAP 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: EMService.awt. On IBM i.volatileImageBufferEnabled=false for all platforms based on the Sun VM in case you see display problems with WebView.headless=true for all platforms. Adapt lax.lax: Enterprise Manager launched with script Introscope_Enterprise_Manager (typically only on Unix).nl.5 Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 15 .java. Introscope_Enterprise_Manager.vm to the full path of the VM to use (if you want to change the default) and use lax.. the DISPLAY environment variable must point to a valid X Windows server.nl.maxmemory to increase the Java heap (corresponds to –Xmx). the Enterprise Manager will need an X server.version=1. Enter the absolute path to a Java 5 VM if you want to use a Java VM that is not bundled with the installer. Set the Java VM parameter –Dswing.command defines the Java VM to use. 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.

2. Running the Enterprise Manager on UNIX On Unix platforms a shell script is provided to start and stop the Introscope Enterprise Manager. Consider launching the Enterprise Manager automatically at system startup. The newly installed management modules only become active after the Enterprise Manager is (re-)started.. Typically.SAR As a result you will find one or more . To check. e. This means you will have to restart the Windows Service for the Enterprise Manager.sh. Go to the subdirectory /bin of the Enterprise Manager installation and issue the following command to launch the Enterprise Manager. and some other files distributed over the Enterprise Manager installation. It is not necessary to explicitly use nohup for EMCtrl.Introscope Installation for SAP Install the SAP Management Modules Extract the file SAPISMM*. Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 16 . Example: cd /usr/sap/ccms/wilyintroscope SAPCAR –xvf SAPISMM*. /usr/sap/ccms/wilyintroscope.jar files in the subdirectory config/modules. some . Running the Enterprise Manager on IBM i It is recommended to create an own subsystem for running the Wily Introscope Enterprise Manager on IBM i. For Windows installations the Enterprise Manager is typically automatically launched as Windows Service. it is registered as Windows service (On Unix you should run it as background process).sh start The shell script launches the Enterprise Manager in background mode (via nohup). you will have to hook it into one of the operating system specific init scripts. Make sure to use the correct user account when launching the EM: . Start the service if it is not yet running. perform the following: 1. Launch Enterprise Manager as Windows Service To launch the Enterprise Manager automatically at system restart.g.SAR in the home directory of the Enterprise Manager installation. 1./EMCtrl.js files in the subdirectory scripts. Open the Services Control Panel (Start Menu Control Panel Administrative Tools Services) and check that the service “Introscope Enterprise Manager” has been created.

g. you have to change ownerships by executing the following commands: CHGOBJOWN OBJ(WILYEM) OBJTYPE(*LIB) NEWOWN(<Your User>) CHGOBJOWN OBJ(WILYEM/WILYJOBQ) OBJTYPE(*JOBQ) NEWOWN(<Your User>) CHGOBJOWN OBJ(WILYEM/WILYJOBD) OBJTYPE(*JOBD) NEWOWN(<Your User>) CHGOBJOWN OBJ(WILYEM/WILYCLS) OBJTYPE(*CLS) NEWOWN(<Your User>) CHGOBJOWN OBJ(WILYEM/WILYSBS) OBJTYPE(*SBSD) NEWOWN(<Your User>) <Your User> can be any user.sh start'')') CRTCLS CLS(WILYEM/WILYCLS) TEXT('Wily EM job class') CRTSBSD SBSD(WILYEM/WILYSBS) POOLS((1 *BASE)) TEXT('Wily EM subsystem') ADDRTGE SBSD(WILYEM/WILYSBS) SEQNBR(1) CMPVAL(*ANY) PGM(QSYS/QCMD) POOLID(1) CLS(WILYEM/WILYCLS) ADDJOBQE SBSD(WILYEM/WILYSBS) JOBQ(WILYEM/WILYJOBQ) MAXACT(*NOMAX) ADDAJE SBSD(WILYEM/WILYSBS) JOB(WILYEM) JOBD(WILYEM/WILYJOBD) If you can not run the commands as the Wily EM user. If this user is not authorized for some commands. QSECOFR) and change the ownership of the created objects afterwards./EMCtrl. To activate the Wily Enterprise Manager at system startup. This is what needs to be done: CRTLIB LIB(WILYEM) TEXT('Wily EM library') CRTJOBQ JOBQ(WILYEM/WILYJOBQ) TEXT('Wily EM job queue') CRTJOBD JOBD(WILYEM/WILYJOBD) JOBQ(WILYEM/WILYJOBQ) TEXT('Wily EM job description') USER(<Your User>) RQSDTA('QSH CMD(''cd /usr/sap/ccms/wilyintroscope/bin && . Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 17 . This should be done ideally as the user that the Wily Introscope Enterprise Manager will run under. you have to run a set of commands. you need to add the start of subsystem WILYEM/WILYSBS to your startup program (QSTRUP). do run the commands as user that is authorized (e. for example the <SID>ADM of your Solution Manager system. You can ensure this by running chown –R <Your User> /usr/sap/ccms/wilyintroscope in QSHELL or QP2TERM. This user needs to have access to the files in /usr/sap/ccms/wilyintroscope.Introscope Installation for SAP To set this up.

the Enterprise Manager agent port is 6001 (default value).Introscope Installation for SAP For controlling (starting/stopping) the Wily Enterprise Manager you can use the EMCtrl. 1.PostOfficeHub] Server listening for incoming default socket connections on port 6001 In this case. Check the TCP port that Introscope Enterprise Manager is using for agent connections. Check that the Enterprise Manager has started.sh script as in Unix. Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 18 .sh start”. 3. check that it is running properly. However. be aware that the Wily Enterprise Manager job will run in your current subsystem if you start it from a shell with “EMCtrl. 2. Locate the Enterprise Manager log at <Introscope home>/logs/IntroscopeEnterpriseManager. Look for lines similar to the following in the logfile: [INFO] [Manager.log. Check That Introscope Is Running Properly After you have launched the Enterprise Manager. Look for the following line in the logfile: 03/28/10 10:54:36 AM CET [INFO] [Manager] Introscope Enterprise Manager started.

Launch the Introscope Setup application: Diagnostics Setup Managed Systems Introscope Agent.SCA using SDM. Deploy ISAGENTSMD*.Introscope Installation for SAP 4 Introscope-Enabling SAP J2EE Systems After you have installed the Enterprise Manager. Automated Installation of the Introscope Agent via SMD The Solution Manager Diagnostics provides an application that performs the setup of the Introscope bytecode agent for Java automatically. Enable Maintenance Mode on SMD. 1. If you do not have Solution Manager Diagnostics available follow the manual procedure described in the second section of this chapter below. 2. the setup wizard for the managed system must have been executed. Before you can run the Introscope agent setup. Your screen will look similar to the image below: Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 19 . 3. you are ready to install and configure the Introscope Agent and Introscope-enable your Java Applications. Note: The recommended procedure to install and customize the Introscope Agent is to use the setup wizard provided in Solution Manager Diagnostics. Disable Maintenance Mode on SMD. This section explains the steps to run the setup. 4.

Finally. select the system that you want to instrument with the agent. This will display the current status of the agent setup. Select the desired agent version (by default only one available) and choose the profile.Introscope Installation for SAP 5. To initially setup or update the agents. review the AIX settings to match your environment (J9 or classic mode). Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 20 . Check the Enterprise Manager Settings at the top of the screen. These are the connection parameters that will be used by the agent to connect to the Enterprise Manager. click Setup Introscope Agent …. 8. In the pane Introscope Agent Setttings. and. 6. and the Java VM parameters will be set as required for the managed system. check the desired instrumentation areas. Next. an Autoprobe connector will be created if necessary. 7. This will open the setup dialog as shown below. Agent config files will be adapted. in the case of AIX. Check “select all” and click “Retrieve Current Settings”. hit Apply to perform the necessary changes in the agent configuration.

Use the Configtool to set the parameters as described.g. After the restart. e. For Netweaver 7. 10. For Netweaver 7. If the setup was successful.1: You may see a dialog asking to manually set the JVM parameters via the ConfigTool.Introscope Installation for SAP 9. described in the previous Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 21 .11. These steps are only required if the automated installation. in the next maintenance window. the agent will be active and should show up in the Introscope UIs. Manual Installation of the Introscope Agent This section describes the manual configuration of Introscope bytecode agent for Java. restart the managed system at your convenience. this dialog should not show up.

7.2.10 and higher. All profiles adhere to the name pattern IntroscopeAgent*. Note that the profile names have changed starting with the 7.profile is intended for SAP IPC 4.profile.SAR 2. The instructions in the following section work on both Windows and Unix systems. Configuring Introscope Agent Settings The following section details how to configure the Introscope Agent. Confirm the Agent was installed correctly by checking for the existence of the /wily directory in the <drive>:\usr\sap\ccms directory. depending on the monitored solution you need to choose different profiles: Choose the Right Agent Profile SAP provides two agent profiles for different use cases. The following instructions are valid for SAP J2EE versions 6. and 7. Create the Introscope Agent autoprobe connector (not for IBM i Classic VM and Java 5) 3. This guide will refer to the IntroscopeAgent. For all applications running on the SAP J2EE Engine use IntroscopeAgent. The following steps are required to install and configure the Introscope Agent to report information to the Enterprise Manager: 1.0. Note that this file contains SAP-specific customization. The Agent configuration settings are found by default in the file /usr/sap/ccms/wily/IntroscopeAgent. This avoids the need to escape the Windows path separator backslash (\) by doubling it. Extract the Introscope Agent files 2. Extract the agent installer file into the NetWeaver CCMS directory.Introscope Installation for SAP section.profile. 6.2. Introscope-enable the application code by setting Java VM parameters Extract the Introscope Agent To install the Introscope Agent: 1. SAPCAR –xvf ISAGENTSTD*.40. Note: Always use forward slashes (/) as path separators for Introscope config files and for JVM parameters on all platforms including Windows. The second profile IntroscopeAgent_ipc.20.profile file as the Agent profile.0 (72_02) release: Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 22 .profile.00. could not be applied. Furthermore. usually: <drive>:\usr\sap\ccms. but the examples show Windows convention (backslashes in the paths).

sap_ep. Locate the property.jar. By default. not VMC) Note: For Introscope-enabling SAP IPC. Enter either the host name or IP address of the machine where Enterprise Manager resides.DEFAULT.tcp.jar This instrumentation covers standard SAP J2EE (e. To configure the Introscope Agent: 1. file <drive>:\usr\sap\ccms\wily\IntroscopeAgent.sap_xi_typic al. The value should be the port on which the Enterprise Manager listens for Agent connections.profile.directivesFile.autoprobe.0 only.g.tcp.transport.enterprisemanager.autoprobe. 2. introscope.profile IntroscopeAgent_ipc.transport. You can add entries to the property. introscope.jar SAP J2EE 7. web services.jar. Save changes to the agent profile.sap_ep_iviews.host.agent.g.profile Applications Covered SAP Netweaver (Java stack) SAP IPC (IPC 4.agent. Default setting is 6001. please also check SAP Note 886600. and XI functionality. You will need to configure the host name or IP address and port of the machine where the Enterprise Manager resides.jar.4! Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 23 . Choose the Right Instrumentation Packages The instrumentation is split into several JAR packages.Introscope Installation for SAP File Name IntroscopeAgent. Portal. Do not activate for Java 1. memory allocation.10 and JDK5 specific instrumentation.directivesFile=sap_typical. the following packages are active: introscope. 3.g. e. Open the agent profile. Servlets.DEFAULT. 4. e. There are additional instrumentation sections which are not active by default.enterprisemanager. separated by comma: sap_sapvm. database/JDBC. user management. You can customize the list of packages by modifying the property introscope. etc.port.). JCO/RFC. Locate the property.

GRC Redwood CPS … sap_duet.appender. The following section details how to configure JVM AutoProbe. Activate only one of these 2: sap_ep_iviews. This step is not required for Java 5 VMs and not for an IBM Classic Java VM running on IBM i Instead.jar sap_smd.logfile. the Introscope agents write log files to the subdirectory logs of the agent installation (e.4.jar Re-activate metrics for each iView/rolename combination.jar! SAP Duet specific instrumentation Solution Manager self-monitoring Instrumentation for SAP partner and acquisition products . As an alternative.jar Check the Agent Log File Location By default. from 1. Configuring JVM AutoProbe You have to create a so-called AutoProbe connector that fits for the Java VM that you use. /usr/sap/ccms/wily/logs).File to some other directories where the monitored systems have write access. There are two ways to specify the JVM: Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 24 .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.g. e.jar or sap_ep_iviews_rolename. make sure that the monitored systems (user sidadm) have read and write access to this directory (write permission for group sapsys).Introscope Installation for SAP sap_ep_iviews_rolename. even if you just change the patch level. you can change the properties introscope. For Linux with the IBM J9 Hybrid VM please see SAP Note 1149214. 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.logfile and log4j.jar tool to create a connector specific to the JVM used to run the application server.4.autoprobe. different VM parameters are used for these platforms. Important Note: You should re-create the AutoProbe connector every time you update the JVM that is used for the SAP J2EE nodes.2_04 to 1.. On Unix systems. Creating an AutoProbe Connector Use the CreateAutoProbeConnector.jar sap_partner.g.

on Windows. note the difference between Unix and Windows in the class path: The entries are separated by . SAP suggests the following naming convention for the agent name. you can use forward slashes (/) on all platforms.jar -jvm C:/soft/jdk14 -output connector. EPQ. Activating the Agent: Set Java VM Parameters After you have created the AutoProbe Connector. Furthermore. For SAP J2EE 6.jar 3. even on Windows. J01. you will only want to activate the agent on the SAP J2EE server nodes.Introscope Installation for SAP • use the JVM that is running the tool • pass the JVM directory on the command line to the tool 1.jar Example: java -jar CreateAutoProbeConnector. This is also generated by the automated setup via Solution Manager Diagnostics starting with SP14: <AgentName>=SID_Instance_Nodename Where the placeholder mean the following: Placeholder SID Instance Nodename Explanation SystemID Name of the instance J2EE node name / directory Example EPP. Typically.40. The output is the file connector. 2.jar -jvm <java_home> -output connector. not on dispatchers and state controllers. but by : on Unix.jar in the same directory. Note that for class path and directory paths. DVEBMGS00 server0 Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 25 . Change the working directory to wily\connectors. This so-called agent name is assigned by an additional Java VM option (referred to as <AgentName> below). Agent Name You should assign a unique name to each SAP J2EE node that is Introscope-enabled. you even cannot use backslash (\) on Windows. you must add three Java VM options. EPD JC00. Run the Create AutoProbe Connector tool using the following command: • 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.

profile -Dcom.agent.agentName=<AgentName> 3.20 The procedure to add JVM options depends on the startup method for the J2EE nodes.introscope.agentProfile=/usr/sap/ccms/wily/IntroscopeAgent.agentProfile=<drive>:/usr/sap/ccms/wily/Introscop eAgent.jar. Using a unique naming convention for all agent installations helps to group agents that belong to the same installation together.agentName=<AgentName> Unix example: -Xbootclasspath/p:/usr/sap/ccms/wily/connectors/connector. Run the SAP J2EE Configtool. Open the file: <drive>:\usr\sap\<J2EE_ENGINE_ID>\j2ee\j2ee_<INSTANCE>\configtool\servi ce.introscope.p rofile -Dcom. 2.introscope. The following procedure is an example in case you use SAP J2EE startup framework for J2EE 6.jar:/usr/sap/ ccms/wily/Agent.20: 1.introscope. Restart SAP server. Select the server to modify.wily. Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 26 . Append the following commands to JavaParameters (Windows example): -Xbootclasspath/p:<drive>:/usr/sap/ccms/wily/connectors/connector.ini 2. Set Java VM Parameters for NetWeaver 04 / SAP J2EE 6.agent. Check SAP Note 697062 for instructions to set JVM options for your specific startup method.Introscope Installation for SAP Note: It is not necessary to integrate the host name into the agent name.jar -Dcom. since the host name is assigned automatically to the agent.wily. Set Java VM Parameters for SAP J2EE 6.40 and Netweaver2004s / SAP J2EE 7.00 1.wily.wily.jar -Dcom.< drive>:/usr/sap/ccms/wily/Agent.

agent.jar: /usr/sap/ccms/wily/Agent.agentName=<AgentName> Note: Note that for NetWeaver 6.wily.introscope.jar -Dcom.jar: /usr/sap/ccms/wily/Agent.10 and up. 6.agent.agentProfile=/usr/sap/ccms/wily/IntroscopeAgent.introscope.< drive>:/usr/sap/ccms/wily/Agent.profile -Dcom.introscope. the slashes for these java parameters must go forwards. For this reason.jitc -Dcom.wily. Unix example: -Xbootclasspath/p:/usr/sap/ccms/wily/connectors/connector.agent.JavaParameters. 7. 5. Click the disk button to save.jar.force. open the file: <drive>:\usr\sap\<SID>\<instance>\j2ee\cluster\instance.jar -Dos400.agentName=<AgentName> IBM i Classic VM example: -Xbootclasspath/p:/QIBM/ProdData/Java400/jdk14/lib/instrumentation.4 for each server node.introscope.properties 8.Introscope Installation for SAP 3. the nodename part of the agent name must be calculated dynamically by using the variable Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 27 .agentProfile=<drive>:/usr/sap/ccms/wily/Introscop eAgent. Set Java VM Parameters for NetWeaver versions based on the Java 5 VM (Netweaver 7.wily. Repeat steps 2 .wily.p rofile -Dcom.jar -agentlib:QJVAIAGENT=/usr/sap/ccms/wily/Agent. add the following new java parameters (Windows example): -Xbootclasspath/p:<drive>:/usr/sap/ccms/wily/connectors/connector. Restart the SAP instance.introscope.wily. and see if it contains the lines you entered in the step above.jar -Dcom.jvmti. Netweaver CE) For Netweaver 7.agentName=<AgentName> 4.wily.introscope.p rofile -Dcom. To verify that Config tool changes were made. Check for a line beginning with ID<server_id>.40 on Windows. In the Java Parameters field.1 and up there are no node-specific Java VM parameters.agentProfile=/usr/sap/ccms/wily/IntroscopeAgent.

wily. Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 28 . this will be filled in with the node name. Repeat steps 2 . Unix example: Instance/VM Parameters/System: Name com. Run the SAP J2EE Configtool. 6. Navigate to Instance/VM Parameters/System and enter the following new parameters (Windows example): Name com. 7. For the first node.agentName com. To verify that Config tool changes were made. Check for a line beginning with ID<server_id>.wily.wily.agent. Restart the SAP instance.wily.introscope.4 for each instance. In the example below. open the file: <drive>:\usr\sap\<SID>\<instance>\j2ee\cluster\instance. They will be replaced automatically if you use the string exactly as written below. variables are also used for the SID and the instance name. 2. Example: Enter ${SYSTEM_NAME}_${INSTANCE_NAME}_$[elem/Name] in the Configtool.agentProfile Value ${SYSTEM_NAME}_${INSTANCE_NAME}_$[elem/Name] /usr/sap/ccms/wily/IntroscopeAgent.introscope. 5.introscope.properties 8. Navigate to Instance/VM Parameters/Additional and enter the following new java parameter (Windows example): -javaagent:<drive>:/usr/sap/ccms/wily/Agent. the slashes for these java parameters must go forwards. 1. it will be replaced with PP1_JC00_server0.jar Note that for NetWeaver on Windows.introscope.Introscope Installation for SAP $[elem/Name]. Click the disk button to save.agentProfile Value ${SYSTEM_NAME}_${INSTANCE_NAME}_$[elem/Name] <drive>:/usr/sap/ccms/wily /IntroscopeAgent.profile 3.profile Instance/VM Parameters/Additional: Name -javaagent:/usr/sap/ccms/wily/Agent.jar 4. At run time.agentName com. and see if it contains the lines you entered in the step above.JavaParameters.agent.

Check that the Agent is Running Launch the Introscope Workstation to check if the data provided by the agent arrives at the Enterprise Manager. where <AgentName> is the name that you assigned via the JVM parameter above. e.isengard. in the directory /usr/sap/ccms/wily/logs. For this purpose.g. Agent Name = "xxx_server0". 2.. Set Java VM Parameters for IBM WebSphere Application Server The procedure to add JVM options for IBM WebSphere Application Server to enable Introscope is described in SAP Note 1418638. You will probably find warnings that the connection to the Enterprise Manager failed – since you have not yet started the Enterprise Manager. Set Java VM Parameters for Tomcat The procedure to add JVM options for Tomcat Server to enable Introscope is described in SAP Note 1438005.DefaultSocketFactory.postofficehub.link. Check that the SAP J2EE nodes start up correctly after the restart and that the J2EE applications are available as before.log. Checking that the Agent is Running 1. Process = "SAP Netweaver".Introscope Installation for SAP 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.net.com. EXAMPLE The last few lines of the agent log file should similar to the following: 12/06/06 01:41:46 PM PST [INFO] [IntroscopeAgent.<AgentName>. launch the Workstation in a browser: http://emhost:8081/workstation Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 29 . Note that Introscope does not support IPC running in the VM container (VMC) as it is delivered for SAP CRM 5.0.IsengardServerConnectionManager] Connected Agent to the Introscope Enterprise Manager at localhost:6001. The file will be named IntroscopeAgent.wily. Search for an Agent log file in the logs subdirectory of the Introscope agent directory. Open the text file with a text editor and check the last lines. Host = "emhost".

Servlets will only appear after the first servlet has been executed. For each connected agent. Please check the following: If your managed system is running SAP J2EE. Depending on the type of the managed system. you should at least have SAP J2EE. some tree nodes may be missing. Some nodes will only appear after first use. Open the Investigator (Workstation menu New Investigator) to display a tree of all connected hosts and agents.Introscope Installation for SAP You should get a login prompt as shown below. For example. and Linux platforms. Use login credentials from the table in Chapter 1 to authenticate. you can also launch a Workstation that you explicitly installed or WebView (http://emhost:8081/webview). Solaris. you should find a subtree host SAP Netweaver AgentName in the Investigator that looks similar to the screenshot below. As an alternative. so this may indeed be missing. Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 30 . CPU is only available on some Windows. Click the plus signs to open subtrees.

Introscope Installation for SAP Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 31 .

osgiPackages.v1.v1.0windowsSAP. Keep No for Configure VM Settings and enter the host name of the Enterprise Manager in the field Workstation Default Host. the installation will be placed in the folder c:\Introscope82.2. (Silent installation) By default.2. remember to set the DISPLAY before launching the installer. Note that the workstation can always be downloaded on demand from the Enterprise Manager using Java WebStart.tar. Installers are available for the following platforms: Windows 32bit Windows x86_64 Linux IA32 Linux x86_64 The installation is described here for Windows. as described in Chapter 1. for a Windows system ii.windows. Extract the downloaded Workstation installer: sapcar –xvf SAPISWS*. Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 32 . Finally. Then you will be guided through the installation by a wizard.txt b.zip. eula. remove the file installer. a. 1.properties. Launch the installer. osgiPackages. The osgiPackages archive appropriate for your system: i. The following files should be copied: a. the installation will proceed silently.properties in the directory where you launch the installer. Alternatively.Introscope Installation for SAP 5 Workstation Installation If you decide to explicitly install the Introscope Workstation on Client PCs.2. (installation with wizard) Select a target installation directory of your choice. Download Third-Party External Component Package from CA Wily). If you keep the file installer.SAR 2. click Install to launch the installation. pass a different target directory as a command line parameter: IntroscopeWorkstation8. These are the same files that were used for the Enterprise Manager installation. proceed as described in this section. Copy the two files that you downloaded from CA Wily’s FTP server to the directory which contains the installer (see Chapter 1.exe –DUSER_INSTALL_DIR=d:/usr/sap/some/dir b.unix. for a UNIX system 3.2. If you want to install it on Linux. If desired.

by directly starting the file Introscope Workstation. Launch the Workstation: a.2. via the Start Menu: ´CA Wily Introscope 8.2.0 Introscope Workstation b.exe in the installation directory. Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 33 .Introscope Installation for SAP 4.

Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 34 .bat which is located in the installation directory of the EPAgent. 2. Please remove any existing manual EPAgent installations from the monitored systems. Activate the HostAgent 4.Introscope Installation for SAP 6 Environment Performance Agent (De)Installation Note: Starting with SP13 of Solution Manager Diagnostics (LMSERVICE13_0). including the configuration of appropriate plugins to monitor the managed system. This will enable and configure the host agent. This will stop the Windows service and remove the service. the Introscope HostAgent takes over the role of the former EPAgent. The HostAgent is part of the SMDAgent process and centrally administered via the SMD. Windows only: If the EPAgent was set up to run as Windows Service. Unix only: Search for the Java process hosting the EPAgent and kill the process. call the batch file DeregisterEPAService. Remove the complete installation directory of the EPAgent. After upgrading Solution Manager Diagnostics to SP13. 3. Remove the EPAgent 1. run the managed systems setup wizard for all managed systems.

-Dcom. Open the file. Change the value of property introscope. -Xbootclasspath/p: <some path>/wily/connectors/connector. -Dcom.Introscope Installation for SAP 7 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 • Enable Single Sign On from Solution Manager • Enterprise Manager Cluster Setup Change the Agent Port The Enterprise Manager by default listens on TCP port 6001 for agent connections.properties.jmxservice) in case it is still present from previous Introscope versions. Uninstalling Introscope Uninstalling Introscope Agents 5. 3. Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 35 . 1. -javaagent:<some path>/wily/Agent. Remember to change the property in the IntroscopeAgent.agent.wily. config/IntroscopeEnterpriseManager.4 only) b. The following options should be removed: a.profile c. Remove the Java VM options for Introscope from the J2EE nodes that you instrumented before.jar (Java 5 only) 6. 4.jar: <some path>/wily/Agent.wilytech.agentName=<AgentName> d.port.profile to the same port.introscope. You can change this value to any desired port: 1. Use SDM to undeploy the JmxService helper application (com.3.jar (Java 1.wily.introscope. Save changes and close the file.agentProfile=<some path>/wily/IntroscopeAgent.channel1 to the desired port.enterprisemanager. 2.

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

User Management User accounts must be maintained in the file users. create one subdirectory for each domain. located in the subdirectory config/ of the Enterprise Manager. the SAP GC metrics will be missing in the Netweaver agent. Note that currently the Introscope Host Agent and the Netweaver agent for some system must always be in the same domain. 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. folders EPP.xml. proceed as follows: 1.xml in the same directory. EPQ). To create a new user X with password Y. Step 2b: copy all management modules from config/modules to each subdirectory. Permissions are controlled by the file domains. Generate the MD5-encoded password by the script MD5Encoder: MD5Encoder Y Y:57cec4137b614c87cb4e24a3d03a3e0 Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 37 . Note that the SuperDomain must always be the last entry in the domains file. The folder name must be the domain name (in the example. If the Host Agent remains in the SuperDomain and Netweaver agents are moved to some custom domain. Step 3: Restart the Enterprise Manager to activate the changes.Introscope Installation for SAP Step 2: Replicate the management modules: Step 2a: In the directory config/modules.

you have to set up additional EMs. 4. Enterprise Manager Cluster Setup If the scalability limit of a single Enterprise Manager is reached. Add permissions for the user to the Superdomain in the domains. 3. you cannot use permission=”full” or “write“ here! Enable Single Sign On from Solution Manager Starting with Introscope Enterprise Manager release 7. Choose the export button. Add a new line to users. or connect multiple EMs to a cluster. Open the Visual Administrator 2. Currently. Please choose the cert format.2.xml before the final </users> line. Copy the Certificate from the ABAP Stack 1.Introscope Installation for SAP 2. an Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 38 . All authenticated users will be mapped to the Introscope user Admin. To enable this feature. Navigate to Server Services Key storage 3.xml file: user="X" permission="read" /> user="X" permission="run_tracer" /> user="X" permission="historical_agent_control" /> user="X" permission="live_agent_control" /> Note: If you do not have a full license for Introscope. only the Java certificate must be exported. appearing virtually as one EM. Double click the “Own Certificate” in the System PSE part of the screen such that it appears in the Certificate pane. the certificates from the ABAP / Java stack of the Solution Manager system must be copied to the directory sap/TrustedCerts in the Enterprise Manager. the Enterprise Manager web server can accept single sign on tickets from Solution Manager systems. Call transaction STRUST 2. Click export to save the certificate as <hostname>. You can either keep each EM isolated and connect it to Solution Manager.2 (SAP release 72_02). For jump-in from Solution Manager Diagnostics. no automated procedure is available to perform these steps. In this cluster. using the generated password string (the part after :) as password: <user name="X" password="57cec4137b614c87cb4e24a3d03a3e0" /> <grant <grant <grant <grant 3. No restart is required. Add the Certificates to the Enterprise Manager Copy the exported certificates to the Enterprise Manager directory sap/TrustedCerts. Copy the Certificate from the Java Stack 1. Choose TicketKeystore in the Views menu.der.

Make sure the prerequisites are met: a.em2.clustering.enterprisemanager.publickey=internal/server /EM.em1.g.clustering.em2.em1.collector.clustering. To configure an EM cluster.enterprisemanager.enterprisemanager.properties.manager.login.host=myhost2 introscope.publickey=internal/server /EM.enterprisemanager.host=myhost1 introscope.login. In config/IntroscopeEnterpriseManager. Fast LAN connection between all EMs 2. b. set introscope. whereas the other EMs in the cluster act as “Collectors”.clustering.login. Only collectors accept agent connections.login.login.enterprisemanager.port=6001 introscope. via NTP). In config/IntroscopeEnterpriseManager.clustering.login.clustering.g. set introscope.public introscope.em2.public Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 39 .Introscope Installation for SAP additional EM acts as “Manager of Managers” (MoM).enterprisemanager. proceed as follows: 1. Configure the collector EMs. Only the MoM accepts Workstation and Solution Manager connections. Configure the MoM. e. introscope.em1.enterprisemanager. Strict clock synchronization between all involved hosts (e.enable=true List connection data for all collector Ems.port=6001 introscope.clustering.properties.enable=true 3.clustering.enterprisemanager.

Sign up to vote on this title
UsefulNot useful