P. 1
Wily Intro Scope 8 Installation Guide

Wily Intro Scope 8 Installation Guide

|Views: 15,145|Likes:
Published by jgb6275

More info:

Published by: jgb6275 on Aug 31, 2010
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





Introscope Version 8 Installation Guide For SAP

March 2010

Introscope Installation for SAP

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

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

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

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

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

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

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.

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

0.0windowsSAP. Operating System Linux on IA 64bit Java 5 VM Download Link http://commerce.0 Linux on Power 64bit Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 11 .64-bit) http://www.SAR of the folder #OS independent on the Service Marketplace. Installation includes one additional step then: 1.html. Launch the OS-independent installer The operating system independent installer is contained in the file SAPISEM*.bin introscope8.com/products/weblogicjrockit/jro ckit_prod_fam-bea. you can exchange the Java VM after the installation.exe introscope8.2. Platform Independent Introscope Installer If you do not find your operating system in the table above. If you want to run the Enterprise Manager on a 64 Java VM.2.ibm.2.0windowsitanium64SAP. Agree to terms.0windowsAMD64SAP.com/developerworks/java/jdk/linux/do wnload. Download JRockit 5.Introscope Installation for SAP Solaris on SPARC 32bit Solaris on SPARC 64bit* Windows IA32 Windows x86_64 64bit Windows on IA64 introscope8. however. you can use the generic installer for the operating systems listed below.2. Install a Java 5 VM 2.2. select 64-bit iSeries/pSeries in column J2SE 5.0 R27 JDK Linux (Intel Itanium .bea.2. Note.0solarisSAP. See below for details.exe * For Solaris SPARC and HPUX on PA RISC only 32-bit installers are available.2.2. 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.jsp Click on JRockit 5.exe introscope8.

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

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

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

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

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

If this user is not authorized for some commands.g. you have to run a set of commands. QSECOFR) and change the ownership of the created objects afterwards.Introscope Installation for SAP To set this up. This should be done ideally as the user that the Wily Introscope Enterprise Manager will run under. do run the commands as user that is authorized (e. you need to add the start of subsystem WILYEM/WILYSBS to your startup program (QSTRUP). This user needs to have access to the files in /usr/sap/ccms/wilyintroscope. You can ensure this by running chown –R <Your User> /usr/sap/ccms/wilyintroscope in QSHELL or QP2TERM. 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 && ./EMCtrl. for example the <SID>ADM of your Solution Manager system. To activate the Wily Enterprise Manager at system startup. 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. Introscope® Version 8 Installation Guide for SAP (5/3/2010) Page 17 .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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->