Professional Documents
Culture Documents
Introscope Version 8 Installation Guide
Introscope Version 8 Installation Guide
March 2010
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
Page 2
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 (PBDs), 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.
Page 3
Page 4
Introscope Installation for SAP and, if the Enterprise Manager was updated, a new version is downloaded automatically. 2. Introscope WebView: Browser-based user interface, uses the Microsoft Silverlight browser plugin. In some details limited functionality. WebView is available by default on the Enterprise Manager (no installation necessary), default URL: http://emhost:8081/webview. In general using the Workstation should be preferred to WebView since it is more powerful. The most convenient option is to use 1b (Launch Workstation via Java Webstart). The binaries are then only downloaded once and after that cached on the client PC. You may also decide to install the workstation explicitly on your client PC (1a).
Introscope Access
After installation, you can use the following default credentials to access Introscope:
Furthermore, you can add live_agent_control and historical_agent_control permissions to the Admin user if you want. Please refer to the User Management section in Chapter 7 for details.
Page 5
Save the files in the same directory as the Introscope installer executable. The installer will then automatically locate this file during the installation process. Note: The installer does not validate whether you have downloaded the correct archive for your platform. Be sure you download and specify the correct archive for your platform.
Installation Tools
Details on the used installation tools (sapcar and SDM) can be found in the Support Package Stack Guide: http://service.sap.com/instguidesNW04 -> Operations
Page 6
Page 7
Introscope Installation for SAP Move the remaining files from the old installation to a different location, e.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. Make sure you also extract the new management modules files (SAPISMM*.SAR) as described in the next section. Shut down the newly installed Enterprise Manager in case it was launched after the installation. Remove the subdirectories /data and /traces from the new installation if they exist. They will only be created if the Enterprise Manager is started. Copy or move the old subdirectories /data and /traces to the new location. Be aware that the traces database will be migrated to a new format when the Enterprise Manager is launched. As an alternative, you may also decide to drop the /traces directory completely instead of migrating it. Manually transfer any custom management modules (located in /config/modules) from the old to the new location. But do not overwrite newly installed standard SAP modules with older versions. Manually transfer any customization (Java VM parameter in file Introscope Enterprise Manager.lax or EMService.conf or runem.nohup.sh, other properties in file config/IntroscopeEnterpriseManager.properties). Do not replace the new configuration files with the old copies since you may then loose any newly introduced properties. Instead, copy and paste any customization from your old files.
Agent Upgrade
All agent installations and upgrades can (and should) be done centrally by the administration tools of Solution Manager. The only manual steps are to restart the managed systems after any configuration change and to undeploy the JmxService J2EE application (com.wilytech.jmxservice), which is no longer needed. In case you want to do a manual upgrade, to get rid of any obsolete files we recommend performing a fresh installation, e.g. by moving the old agent installation to a different directory. Since some agent files are locked while the monitored system is running, the monitored system must be down for the agent upgrade. Also for the manual upgrade, the JmxService J2EE application is no longer needed starting with release 7.1p9 of the Introscope agent. Please undeploy the old version with SDM.
WebView Upgrade
Starting with Introscope 7.1 the Enterprise Manager already contains an embedded WebView that is run as part of the Enterprise Manager Java process. It is no longer necessary to deploy it on NetWeaver, and support for deploying WebView on Netweaver is stopped as of Introscope release 7.2. You should undeploy the old version of WebView on NetWeaver (com.wilytech.webview). WebView running in the Enterprise Manager is by
Page 8
Introscope Installation for SAP default reached via the URL http://emhost:8081/webview. The former URL http://smdhost:5xx00/webview is no longer valid for this operating mode.
Page 9
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
Page 10
Solaris on SPARC 32bit Solaris on SPARC 64bit* Windows IA32 Windows x86_64 64bit Windows on IA64
introscope8.2.2.0solarisSAP.bin
* For Solaris SPARC and HPUX on PA RISC only 32-bit installers are available. If you want to run the Enterprise Manager on a 64 Java VM, you can exchange the Java VM after the installation. See below for details. Note, 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.
Operating System
Linux on IA 64bit
Java 5 VM Download Link http://commerce.bea.com/products/weblogicjrockit/jro ckit_prod_fam-bea.jsp Click on JRockit 5.0, Agree to terms, Download JRockit 5.0 R27 JDK Linux (Intel Itanium - 64-bit) http://www.ibm.com/developerworks/java/jdk/linux/do wnload.html, select 64-bit iSeries/pSeries in column J2SE 5.0
Page 11
http://www.ibm.com/developerworks/java/jdk/linux/do wnload.html, select 64-bit zSeries (S/390) in column J2SE 5.0 http://java.sun.com/javase/downloads/index_jdk5.jsp, select Solaris x86 Platform and Solaris x64 Platform - J2SE(TM) Development Kit 5.0 latest Update, accept license
2. Add the option DUSER_INSTALL_DIR=<installation directory> to the invocation of the installer (see below), .e.g.,
Page 12
introscope8.2.2.0windows.SAP.exe DUSER_INSTALL_DIR=d:/usr/sap/ccms/wilyintroscope.
Note: The instructions in this guide will use examples relative to the default
installation directory.
Introscope8.2.2.0windows.SAP.exe
For any other platform-dependent installer, use the command in the following example. You may have to set the right permission before you can launch the installation:
./introscope8.2.2.0solaris.SAP.bin
For the IBM i installer you first need to determine the JDK that you will be using. Wily introscope requires a JDK 5. Depending on the operating system version you are using you should prefer IBM IT4J (J9) over the IBM Classic JVM. Here is a list of
Page 13
Introscope Installation for SAP the JAVA_HOME directories and the according IBM I product options that need to be installed: IBM i 6.1: /QOpenSys/QIBM/ProdData/JavaVM/jdk50/64bit/jre (5761JV1 Opt. 9) i5/OS V5R4: /QOpenSys/QIBM/ProdData/JavaVM/jdk50/32bit/jre (5722JV1 Opt. 8) i5/OS V5R3: /QIBM/ProdData/Java400/jdk15 (5722JV1 Opt. 7) Then, run the following command in QSH: <JAVA_HOME>/bin/java Djava.version=1.5 classpath introscope8.2.2.0os400SAP.jar install For the platform independent installer that does not contain a bundled Java VM use the following command. /some/path/java refers to the Java 5 VM that you installed as described above: /some/path/java classpath introscope8.2.2.0otherUnixSAP.jar install Note: In any case, the configuration file installer.properties must be located in the current directory where you launch the installer. You can avoid copying the installation file itself by using the complete path to the executable. 2. Verify installation using instructions in the following section, Verifying Installation.
Verifying Installation
The installer does not give confirmation of successful installation on the console. To confirm installation was successful: 1. Verify that the Introscope directory exists at: <drive>:\usr\sap\ccms\wilyintroscope (Windows) /usr/sap/ccms/wilyintroscope (Unix, IBM i) OR the location you specified. 2. Open the file,
/usr/sap/ccms/wilyintroscope/install/Introscope_<version>_InstallL og.log.
Note: The number of successes may be different than what is shown in this example.
Introscope Version 8 Installation Guide for SAP (5/3/2010) Page 14
EMService.conf: Used when Enterprise Manager is running as Windows Service on Windows platforms. The property wrapper.java.command defines the Java VM to use. Increase the value of adapt wrapper.java.maxmemory to increase the Java
heap (corresponds to Xmx).
Introscope_Enterprise_Manager.lax: Enterprise Manager launched with script Introscope_Enterprise_Manager (typically only on Unix). Adapt lax.nl.current.vm to the full path of the VM to use (if you want to change the default) and use lax.nl.java.option.additional to modify Java VM
parameters.
runem.sh: Used when Enterprise Manager is launched on IBM i. Adapt the JVM_ARGS
environment variable. 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. Enter the absolute path to a Java 5 VM if you want to use a Java VM that is not bundled with the installer. In particular, 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.
Set the Java VM parameter Djava.awt.headless=true for all platforms. Otherwise, the Enterprise Manager will need an X server, i.e., the DISPLAY environment variable must point to a valid X Windows server. Set the Java VM parameter Dswing.volatileImageBufferEnabled=false for all platforms based on the Sun VM in case you see display problems with WebView. On IBM i, set the Java heap size properties based on the JVM o o IT4J (J9): -Xms512m -Xmx512m IBM Classic: -Xms64m -Xmx2048m
Page 15
./EMCtrl.sh start
The shell script launches the Enterprise Manager in background mode (via nohup). It is not necessary to explicitly use nohup for EMCtrl.sh. Consider launching the Enterprise Manager automatically at system startup. Typically, you will have to hook it into one of the operating system specific init scripts.
Page 16
Introscope Installation for SAP To set this up, you have to run a set of commands. This should be done ideally as the user that the Wily Introscope Enterprise Manager will run under. If this user is not authorized for some commands, do run the commands as user that is authorized (e.g. QSECOFR) and change the ownership of the created objects afterwards.
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.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, 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, for example the <SID>ADM of your Solution Manager system. This user needs to have access to the files in /usr/sap/ccms/wilyintroscope. You can ensure this by running
Page 17
Introscope Installation for SAP For controlling (starting/stopping) the Wily Enterprise Manager you can use the EMCtrl.sh script as in Unix. However, be aware that the Wily Enterprise Manager job will run in your current subsystem if you start it from a shell with EMCtrl.sh start.
home>/logs/IntroscopeEnterpriseManager.log.
2. Check that the Enterprise Manager has started. Look for the following line in the logfile:
[INFO] [Manager.PostOfficeHub] Server listening for incoming default socket connections on port 6001
In this case, the Enterprise Manager agent port is 6001 (default value).
Page 18
Note: The recommended procedure to install and customize the Introscope Agent is to use the setup wizard provided in Solution Manager Diagnostics. If you do not have Solution Manager Diagnostics available follow the manual procedure described in the second section of this chapter below.
Page 19
5. 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. 6. In the pane Introscope Agent Setttings, select the system that you want to instrument with the agent. Check select all and click Retrieve Current Settings. This will display the current status of the agent setup. 7. To initially setup or update the agents, click Setup Introscope Agent . This will open the setup dialog as shown below. Select the desired agent version (by default only one available) and choose the profile. Next, check the desired instrumentation areas, and, in the case of AIX, review the AIX settings to match your environment (J9 or classic mode). 8. Finally, hit Apply to perform the necessary changes in the agent configuration. Agent config files will be adapted, an Autoprobe connector will be created if necessary, and the Java VM parameters will be set as required for the managed system.
Page 20
Introscope Installation for SAP 9. For Netweaver 7.1: You may see a dialog asking to manually set the JVM parameters via the ConfigTool. Use the Configtool to set the parameters as described. For Netweaver 7.11, this dialog should not show up. 10. If the setup was successful, restart the managed system at your convenience, e.g. in the next maintenance window. After the restart, the agent will be active and should show up in the Introscope UIs.
Page 21
Introscope Installation for SAP section, could not be applied. The following instructions are valid for SAP J2EE versions 6.20, 6.40, 7.00, and 7.10 and higher. The instructions in the following section work on both Windows and Unix systems, but the examples show Windows convention (backslashes in the paths).
Note: Always use forward slashes (/) as path separators for Introscope config files and for
JVM parameters on all platforms including Windows. This avoids the need to escape the Windows path separator backslash (\) by doubling it.
The following steps are required to install and configure the Introscope Agent to report information to the Enterprise Manager: 1. Extract the Introscope Agent files 2. Create the Introscope Agent autoprobe connector (not for IBM i Classic VM and Java 5) 3. Introscope-enable the application code by setting Java VM parameters
Page 22
Applications Covered SAP Netweaver (Java stack) SAP IPC (IPC 4.0 only, not VMC)
Note: For Introscope-enabling SAP IPC, please also check SAP Note 886600.
You will need to configure the host name or IP address and port of the machine where the Enterprise Manager resides. To configure the Introscope Agent: 1. Open the agent profile, e.g. file <drive>:\usr\sap\ccms\wily\IntroscopeAgent.profile. 2. Locate the property, introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT. Enter either the host name or IP address of the machine where Enterprise Manager resides. 3. Locate the property, introscope.agent.enterprisemanager.transport.tcp.port.DEFAULT. The value should be the port on which the Enterprise Manager listens for Agent connections. Default setting is 6001. 4. Save changes to the agent profile.
Page 23
Introscope Installation for SAP sap_ep_iviews_rolename.jar Re-activate metrics for each iView/rolename combination. Activate only one of these 2: sap_ep_iviews.jar or sap_ep_iviews_rolename.jar! SAP Duet specific instrumentation Solution Manager self-monitoring Instrumentation for SAP partner and acquisition products - GRC Redwood CPS
Important Note: You should re-create the AutoProbe connector every time you update the JVM that is used for the SAP J2EE nodes, even if you just change the patch level, e.g., from 1.4.2_04 to 1.4.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.
The following section details how to configure JVM AutoProbe. For AIX with the IBM J9 Hybrid VM please see SAP Note 1015184there are special parameters to pass when creating the autoprobe connector and when launching the VM. For Linux with the IBM J9 Hybrid VM please see SAP Note 1149214.
Introscope Installation for SAP use the JVM that is running the tool pass the JVM directory on the command line to the tool 1. Change the working directory to wily\connectors. 2. 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.jar -jvm <java_home> -output connector.jar Example: java -jar CreateAutoProbeConnector.jar -jvm C:/soft/jdk14 -output connector.jar 3. The output is the file connector.jar in the same directory.
Agent Name
You should assign a unique name to each SAP J2EE node that is Introscope-enabled. This so-called agent name is assigned by an additional Java VM option (referred to as <AgentName> below). SAP suggests the following naming convention for the agent name. 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:
Page 25
Note: It is not necessary to integrate the host name into the agent name, since the host name is assigned automatically to the agent. Using a unique naming convention for all agent installations helps to group agents that belong to the same installation together.
Set Java VM Parameters for NetWeaver 04 / SAP J2EE 6.40 and Netweaver2004s / SAP J2EE 7.00
1. Run the SAP J2EE Configtool. 2. Select the server to modify.
Page 26
Introscope Installation for SAP 3. In the Java Parameters field, add the following new java parameters (Windows example): -Xbootclasspath/p:<drive>:/usr/sap/ccms/wily/connectors/connector.jar;< drive>:/usr/sap/ccms/wily/Agent.jar -Dcom.wily.introscope.agentProfile=<drive>:/usr/sap/ccms/wily/Introscop eAgent.profile -Dcom.wily.introscope.agent.agentName=<AgentName>
Note: Note that for NetWeaver 6.40 on Windows, the slashes for these java
parameters must go forwards. Unix example: -Xbootclasspath/p:/usr/sap/ccms/wily/connectors/connector.jar: /usr/sap/ccms/wily/Agent.jar -Dcom.wily.introscope.agentProfile=/usr/sap/ccms/wily/IntroscopeAgent.p rofile -Dcom.wily.introscope.agent.agentName=<AgentName> IBM i Classic VM example: -Xbootclasspath/p:/QIBM/ProdData/Java400/jdk14/lib/instrumentation.jar: /usr/sap/ccms/wily/Agent.jar -agentlib:QJVAIAGENT=/usr/sap/ccms/wily/Agent.jar -Dos400.jvmti.force.jitc -Dcom.wily.introscope.agentProfile=/usr/sap/ccms/wily/IntroscopeAgent.p rofile -Dcom.wily.introscope.agent.agentName=<AgentName>
4. Click the disk button to save. 5. Repeat steps 2 - 4 for each server node. 6. Restart the SAP instance. 7. To verify that Config tool changes were made, open the file: <drive>:\usr\sap\<SID>\<instance>\j2ee\cluster\instance.properties 8. Check for a line beginning with ID<server_id>.JavaParameters, and see if it contains the lines you entered in the step above.
Set Java VM Parameters for NetWeaver versions based on the Java 5 VM (Netweaver 7.10 and up, Netweaver CE)
For Netweaver 7.1 and up there are no node-specific Java VM parameters. For this reason, the nodename part of the agent name must be calculated dynamically by using the variable
Page 27
Introscope Installation for SAP $[elem/Name]. At run time, this will be filled in with the node name. In the example below, variables are also used for the SID and the instance name. They will be replaced automatically if you use the string exactly as written below. Example: Enter ${SYSTEM_NAME}_${INSTANCE_NAME}_$[elem/Name] in the Configtool. For the first node, it will be replaced with PP1_JC00_server0.
1. Run the SAP J2EE Configtool. 2. Navigate to Instance/VM Parameters/System and enter the following new parameters (Windows example): Name
com.wily.introscope.agent.agentName com.wily.introscope.agentProfile
Value
${SYSTEM_NAME}_${INSTANCE_NAME}_$[elem/Name]
<drive>:/usr/sap/ccms/wily
/IntroscopeAgent.profile
3. Navigate to Instance/VM Parameters/Additional and enter the following new java parameter (Windows example): -javaagent:<drive>:/usr/sap/ccms/wily/Agent.jar Note that for NetWeaver on Windows, the slashes for these java parameters must go forwards. Unix example:
Instance/VM Parameters/System: Name com.wily.introscope.agent.agentName com.wily.introscope.agentProfile Value ${SYSTEM_NAME}_${INSTANCE_NAME}_$[elem/Name] /usr/sap/ccms/wily/IntroscopeAgent.profile
4. Click the disk button to save. 5. Repeat steps 2 - 4 for each instance. 6. Restart the SAP instance. 7. To verify that Config tool changes were made, open the file: <drive>:\usr\sap\<SID>\<instance>\j2ee\cluster\instance.properties 8. Check for a line beginning with ID<server_id>.JavaParameters, and see if it contains the lines you entered in the step above.
Page 28
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.IsengardServerConnectionManager] Connected Agent to the Introscope Enterprise Manager at localhost:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory. Host = "emhost", Process = "SAP Netweaver", Agent Name = "xxx_server0".
Page 29
Introscope Installation for SAP You should get a login prompt as shown below. Use login credentials from the table in Chapter 1 to authenticate. As an alternative, you can also launch a Workstation that you explicitly installed or WebView (http://emhost:8081/webview).
Open the Investigator (Workstation menu New Investigator) to display a tree of all connected hosts and agents. Click the plus signs to open subtrees. For each connected agent, you should find a subtree host SAP Netweaver AgentName in the Investigator that looks similar to the screenshot below. Depending on the type of the managed system, some tree nodes may be missing. Please check the following: If your managed system is running SAP J2EE, you should at least have SAP J2EE. CPU is only available on some Windows, Solaris, and Linux platforms, so this may indeed be missing. Some nodes will only appear after first use. For example, Servlets will only appear after the first servlet has been executed.
Page 30
Page 31
5 Workstation Installation
If you decide to explicitly install the Introscope Workstation on Client PCs, proceed as described in this section. Note that the workstation can always be downloaded on demand from the Enterprise Manager using Java WebStart, as described in Chapter 1. Installers are available for the following platforms: Windows 32bit Windows x86_64 Linux IA32 Linux x86_64 The installation is described here for Windows. If you want to install it on Linux, remember to set the DISPLAY before launching the installer. 1. Extract the downloaded Workstation installer: sapcar xvf SAPISWS*.SAR 2. Copy the two files that you downloaded from CA Wilys FTP server to the directory which contains the installer (see Chapter 1, Download Third-Party External Component Package from CA Wily). These are the same files that were used for the Enterprise Manager installation. The following files should be copied: a. eula.txt b. The osgiPackages archive appropriate for your system: i. osgiPackages.v1.2.windows.zip, for a Windows system ii. osgiPackages.v1.2.unix.tar, for a UNIX system 3. Launch the installer. If you keep the file installer.properties in the directory where you launch the installer, the installation will proceed silently. Alternatively, remove the file installer.properties. Then you will be guided through the installation by a wizard. a. (Silent installation) By default, the installation will be placed in the folder c:\Introscope82. If desired, pass a different target directory as a command line parameter: IntroscopeWorkstation8.2.2.0windowsSAP.exe DUSER_INSTALL_DIR=d:/usr/sap/some/dir b. (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. Finally, click Install to launch the installation.
Page 32
Introscope Installation for SAP 4. Launch the Workstation: a. via the Start Menu: CA Wily Introscope 8.2.2.0 Introscope Workstation
Page 33
Page 34
Uninstalling Introscope
Uninstalling Introscope Agents
5. Remove the Java VM options for Introscope from the J2EE nodes that you instrumented before. The following options should be removed: a. -Xbootclasspath/p: <some path>/wily/connectors/connector.jar: <some path>/wily/Agent.jar (Java 1.3, 1.4 only) b. -Dcom.wily.introscope.agentProfile=<some path>/wily/IntroscopeAgent.profile c. -Dcom.wily.introscope.agent.agentName=<AgentName> d. -javaagent:<some path>/wily/Agent.jar (Java 5 only) 6. Use SDM to undeploy the JmxService helper application (com.wilytech.jmxservice) in case it is still present from previous Introscope versions.
Introscope Version 8 Installation Guide for SAP (5/3/2010) Page 35
Introscope Installation for SAP 7. Restart the affected J2EE instances for the changes to become effective. 8. Delete the directory <some path>/wily (or wherever you put the agent files).
Page 36
Step 2: Replicate the management modules: Step 2a: In the directory config/modules, create one subdirectory for each domain. The folder name must be the domain name (in the example, folders EPP, EPQ). Step 2b: copy all management modules from config/modules to each subdirectory. Step 3: Restart the Enterprise Manager to activate the changes. 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. Note that the SuperDomain must always be the last entry in the domains file. Note that currently the Introscope Host Agent and the Netweaver agent for some system must always be in the same domain. If the Host Agent remains in the SuperDomain and Netweaver agents are moved to some custom domain, the SAP GC metrics will be missing in the Netweaver agent.
User Management
User accounts must be maintained in the file users.xml, located in the subdirectory config/ of the Enterprise Manager. Permissions are controlled by the file domains.xml in the same directory. To create a new user X with password Y, proceed as follows: 1. Generate the MD5-encoded password by the script MD5Encoder: MD5Encoder Y Y:57cec4137b614c87cb4e24a3d03a3e0
Page 37
Introscope Installation for SAP 2. Add a new line to users.xml before the final </users> line, using the generated password string (the part after :) as password: <user name="X" password="57cec4137b614c87cb4e24a3d03a3e0" /> <grant <grant <grant <grant 3. Add permissions for the user to the Superdomain in the domains.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, you cannot use permission=full or write here!
3. Choose TicketKeystore in the Views menu. 4. Choose the export button. Please choose the cert format.
Page 38
Introscope Installation for SAP additional EM acts as Manager of Managers (MoM). Only the MoM accepts Workstation and Solution Manager connections, whereas the other EMs in the cluster act as Collectors. Only collectors accept agent connections. To configure an EM cluster, proceed as follows: 1. Make sure the prerequisites are met: a. Strict clock synchronization between all involved hosts (e.g. via NTP). b. Fast LAN connection between all EMs 2. Configure the collector EMs. In config/IntroscopeEnterpriseManager.properties, set introscope.enterprisemanager.clustering.collector.enable=true 3. Configure the MoM. In config/IntroscopeEnterpriseManager.properties, set introscope.enterprisemanager.clustering.manager.enable=true List connection data for all collector Ems, e.g. introscope.enterprisemanager.clustering.login.em1.host=myhost1 introscope.enterprisemanager.clustering.login.em1.port=6001 introscope.enterprisemanager.clustering.login.em1.publickey=internal/server /EM.public introscope.enterprisemanager.clustering.login.em2.host=myhost2 introscope.enterprisemanager.clustering.login.em2.port=6001 introscope.enterprisemanager.clustering.login.em2.publickey=internal/server /EM.public
Page 39