Professional Documents
Culture Documents
Introscope Version 7.1
Introscope Version 7.1
Contents
Contents........................................................................................................................................... 2 1 Installation Overview ............................................................................................................... 3 2 Upgrading from Previous Versions to Introscope 7.1................................................................ 7 3 Installing the Introscope Enterprise Manager .......................................................................... 10 4 Introscope-Enabling SAP J2EE Systems ................................................................................ 19 5 Workstation Installation ......................................................................................................... 28 6 Introscope-Enabling Duet ASP.NET Applications.................................................................. 29 7 Environment Performance Agent Installation ......................................................................... 37 8 Installing and Configuring WebView with SAP NetWeaver ................................................... 41 9 Additional Installation Options ............................................................................................... 44
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 7.1 Installing Introscope Enterprise Manager Introscope-enabling SAP J2EE Systems (Agent Installation) Optional: Installing Introscope Workstation Optional: Installing Introscope WebView on NetWeaver Environment Performance Agent installation Optional Configuration Steps
Introscope Overview
Introscope is a system management application created to manage Java Application performance. Unlike development tools, Introscope is designed to scale with minimal performance impact. This allows you to monitor and manage your application performance in live production environments. You are installing Introscope as part of SAP Solution Manager to give SAP support better visibility into technical issues you may experience. You will also get access to Introscope so that you can analyze performance problems on your own.
Page 3
Page 4
Introscope Installation for SAP a. Use the WebView that is available by default on the Enterprise Manager (no installation necessary), default URL: http://emhost:8081/webview. b. Deploy WebView on top of SAP Netweaver (see Chapter 6). 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). If you decide using WebView 2a) is recommended. Deploying WebView on NetWeaver (2b) is normally not needed.
Introscope Access
After installation, you can use the following default credentials to access Introscope:
Page 5
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
Note that 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. You may want to simply undeploy the old version of WebView on NetWeaver (com.wilytech.webview). As a consequence, WebView running in the Enterprise Manager is by default reached via the URL
Page 8
Introscope Installation for SAP http://emhost:8081/webview. The former URL http://smdhost:5xx00/webview is no longer valid for this operating mode. If you want to run WebView on NetWeaver anyway, deploy the new version in the same way as the old version. However, before you deploy the new version you need to undeploy the old version and restart the J2EE server. See also the FAQ.
Page 9
Operating System
AIX5 64bit i5/OS HP-UX 11 on PA-RISC 32bit HP-UX 11 on PA-RISC 64bit* HP-UX 11 on IA64 Linux on IA32 32bit Linux on x86_64 64bit
Page 10
Solaris on SPARC 32bit Solaris on SPARC 64bit* Windows IA32 Windows x86_64 64bit* Windows on IA64
introscope7.1solarisSAPEndUser.bin
introscope7.1windowsSAPEndUser.exe
introscope7.1windowsitanium64SAPEndUser.exe
* For Solaris SPARC, HPUX on PA RISC, and Windows on x86_64 only 32-bit installers are available. If you want to run the Enterprise Manager on a 64 Java VM, you can exchange the Java VM after the installation. See below for details.
Operating System
Linux on IA 64bit
Java 5 VM Download Link http://commerce.bea.com/products/weblogicjrockit/jro ckit_prod_fam.jsp Click on JRockit 5.0, Agree to terms, Download JRockit 5.0 R26 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 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,
Page 11
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.,
introscope7.1windows.SAPEndUser.exe DUSER_INSTALL_DIR=d:/usr/sap/ccms/wilyintroscope.
Page 12
Introscope Installation for SAP 2. Locate the USER_INSTALL_DIR property. To change the install directory location, enter the desired location in the USER_INSTALL_DIR property.
Note: The instructions in this guide will use examples relative to the default
installation directory.
Introscope7.1windows.SAPEndUser.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:
./introscope7.1solaris.SAPEndUser.bin
For the i5/OS installer run the following command in QSH: /QIBM/ProdData/Java400/jdk15/bin/java classpath introscope7.1.P4os400SAPEndUser.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 introscope7.1otherUnixSAPEndUser.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, i5/OS) OR the location you specified. 2. Open the file,
/usr/sap/ccms/wilyintroscope/install/Introscope_InstallLog.log .
3. Verify that the following lines appear at the top of the file:
Page 13
Note: The number of successes may be different than what is shown in this example.
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.nohup.sh: Used when Enterprise Manager is launched with nohup ./runem.nohup.sh& on Unix platforms where the primary script Introscope_Enterprise_Manager does not work. Adapt the IHOME, JAVAPATH, and JVMARGS environment variables. runem.sh: Used when Enterprise Manager is launched on i5/OS. 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 Windows on x86_64
Page 14
Introscope Installation for SAP 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 i5/OS, set the Java heap size properties to -Xms64m Xmx2048m
Page 15
lax.stdin.redirect=
2. In the IntroscopeEnterpriseManager.properties file, ensure that the property introscope.enterprisemanager.disableInteractiveMode is set to true, as in:
introscope.enterprisemanager.disableInteractiveMode=true
3. Start the Enterprise Manager with the following command:
nohup ./Introscope_Enterprise_Manager&
It is critical that both of the Introscope Enterprise Manager properties are set exactly as described above. If you attempt to run the Enterprise Manager in nohup mode without changing these properties as described, or set them incorrectly, the Enterprise Manager may not start, or CPU utilization may become excessive.
Note: For some platforms, we discovered that the automatically generated script
CRTJOBD JOBD(<Your Library>/WILYEM) JOBQ(QUSRNOMAX) TEXT('Jobdescription for Wily EM') RQSDTA('QSH CMD(''cd /usr/sap/ccms/wilyintroscope && /usr/sap/ccms/wilyintroscope/runem.sh'')') USER(<Your User>) GRTOBJAUT OBJ(<Your Library>/WILYEM) OBJTYPE(*JOBD) USER(<Your User>) AUT(*USE) ADDAJE SBSD(QUSRWRK) JOB(WILYEM) JOBD(<Your Library>/WILYEM)
<Your Library> can be any library, for example R3400. <Your User> can be any user, for example the <SID>ADM of your Solution Manager system. However, this user needs to have access to the files in /usr/sap/ccms/wilyintroscope. You can ensure this by running
Page 16
Note: Make sure the Enterprise Manager has both read access and write access to the
complete /usr/sap/ccms/wilyintroscope directory, so that configuration changes will be properly saved.
On Windows
Start the Enterprise Manager using one of the following methods: from the Start menu, Introscope > Administration > Introscope Enterprise Manager. OR run Introscope Enterprise Manager.exe (located in the <Introscope home> directory, by default c:/usr/sap/ccms/wilyintroscope).
On i5/OS
Note: The Enterprise Manager can be run in QSH shell but not in QP2TERM (Pase environment). To launch the Enterprise Manager directly on i5/OS, open a QSHELL and do the following:
On Other Platforms
On other platforms, switch to the <Introscope home> directory, then launch the Enterprise Manager with the command:
./Introscope_Enterprise_Manager
home>/logs/IntroscopeEnterpriseManager.log.
2. Check that the Enterprise Manager has started. Look for the following line in the logfile:
Page 17
[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: 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.
Page 19
Applications Covered SAP J2EE, Enterprise Portal XI 3.0 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\sap_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 20
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.
Page 21
Introscope Installation for SAP Make sure to specify exactly the JVM that is used for launching the J2EE node by passing the JVM directory <java_home> on the command line: java -jar CreateAutoProbeConnector.jar -jvm <java_home> -output connector.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: <AgentName>=SID_Product_Nodename Where the placeholder mean the following:
Explanation SystemID Identifier for product usage J2EE node name / directory
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.
Page 22
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. 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/sap_Intro scopeAgent.profile -Dcom.wily.introscope.agent.agentName=<AgentName>
Page 23
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/sap_IntroscopeAge nt.profile -Dcom.wily.introscope.agent.agentName=<AgentName> i5/OS 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/sap_IntroscopeAge nt.profile -Dcom.wily.introscope.agent.agentName=<AgentName>
4. Click the disk button to save. 5. Repeat steps 2 - 4 for each server. 6. Restart SAP server. 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 24
Note: Note that for NetWeaver on Windows, the slashes for these java parameters
must go forwards. Unix example: -javaagent:/usr/sap/ccms/wily/Agent.jar -Dcom.wily.introscope.agentProfile=/usr/sap/ccms/wily/sap_IntroscopeAge nt.profile -Dcom.wily.introscope.agent.agentName=<AgentName>
4. Click the disk button to save. 5. Repeat steps 2 - 4 for each server. 6. Restart SAP server. 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 25
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".
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
Page 26
Introscope Installation for SAP 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 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 27
5 Workstation Installation
If you decide to explicitly install the Introscope Workstation on Client PCs, proceed as described in this section. 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 SAPISWS71.SAR 2. 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:\Introscope71. If desired, pass a different target directory as a command line parameter: IntroscopeWorkstation7.1windowsSAPExpertCenter.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. 3. Launch the Workstation: a. via the Start Menu: Introscope 7.1 Introscope Workstation
Page 28
6 Introscope-Enabling Duet
ASP.NET Applications
Installing the Intoscope .NET Agent Set up user permissions for Agent Directory Configure Introscope .NET Agent settings This chapter describes installing and configuring the Introscope .NET Agent with Duet. The following steps are required:
Requirements
Before starting the installation of the Introscope .NET Agent the Microsoft Duet Server Components have to be installed and configured. Check if they are installed by having a look to the Microsoft IIS Manager. You have to see there the following three application pools: AzManSvcWebAppPool IBFWebAppPool RequestHandlerAppPool
Previous Agents
If a previous version of the .NET Agent has been installed on a machine in your environment, Wily recommends the previous version of the Agent be uninstalled before you install the new version of the .NET Agent.
Note: If you wish to use an older version of the .NET Agent rather than the current version, you
must uninstall the current version of the Agent first before installing the older version.
Page 29
2. Click Next. The Choose Install Folder page is displayed. The installation directory is referred to through this guide as the AgentHome directory. Install the .NET agent into a wilydotnet subdirectory of the NetWeaver CCMS directory, usually:
<drive>:\usr\sap\ccms\wilydotnet
Note: If there is no SAP component installed on this server you will not find the
NetWeaver CCMS directory (<drive>:\usr\sap\ccms). The directory will be created by the installation.
Page 30
3. Click Install. The .NET Agent is installed and the Installation Complete Page is displayed. 4. Confirm the .NET agent was installed correctly by checking for the existence of the following directories in the AgentHome directory:
<drive>:\usr\sap\ccms\wilydotnet\wily
Page 31
3. Verify that the Administrator and Create Owner user names have Special Permissions. 4. Click the Add button. The Selected Users or Groups dialogue box is displayed.
Page 32
5. Enter the name NETWORK SERVICE in the Enter the object names to select field. 6. Click the Check Names button to validate the user. Click the OK button after the user name is validated and underlined. The Permission Entry dialogue box is displayed.
7. Verify that the user has the following permissions: Full Control Modify
Page 33
Introscope Installation for SAP Read & Execute List Folder Contents Read Write 8. Click the Advanced button. The Advanced Security Settings for Wily dialogue box is displayed.
9. Click the Replace permission entries on all child objects with entries shown here that apply to child objects check box to propagate permissions to the child directories, and click OK.
Page 34
Replace IntroscopeAgent.profile
The sap_IntroscopeAgent_Duet.profile you copied to the \wily subdirectory of the AgentHome directory is configured for the use with Duet and restricts the monitoring to only Duet related .NET processes and application pools. You need to replace the existing IntroscopeAgent.profile by the sap_IntroscopeAgent_Duet.profile: 1. Rename the exitsing IntroscopeAgent.profile to original_IntroscopeAgent.profile 2. Rename the sap_IntroscopeAgent_Duet.profile to IntroscopeAgent.profile
Page 35
Restart IIS
To restart the IIS open a command prompt window and execute the following command:
iisreset /restart
<drive>:\usr\sap\ccms\wilydotnet\wily The files will be named IntroscopeAgent.DefaultDomain.log and IntroscopeAgent.<Duet application name>.log
Open the files and check if the .NET connected successfully to the Introscope Enterprise Manager.
Page 36
Page 37
Page 38
Introscope Installation for SAP Windows: Copy python_epa.bat to C:/usr/sap/SID/TRXxx/python_epa.bat; adapt the paths in this file. Copy serviceLoad.py to C:/usr/sap/SID/TRXxx/exe/python_support and C:/usr/sap/SID/SYS/exe/nuc/NTI386/python_support (backup the old files before). After copying the files, adapt the path to the python_epa.bat script in the agent config file: introscope.epagent.stateless.SAP_TREX.command=C:/usr/sap/SID/TRXxx/python_e pa.bat Unix: Copy python_epa.sh to /usr/sap/SID/TRXxx/python_epa.sh; adapt the paths in this file. Copy serviceLoad.py to /usr/sap/SID/TRXxx/exe/python_support and /usr/sap/SID/SYS/exe/nuc/NTI386/python_support (backup the old files before). After copying the files, adapt the path to the python_epa.sh script in the agent config file: introscope.epagent.stateless.SAP_TREX.command=/usr/sap/SID/TRXxx/python_epa .sh Note that this plugin is not active by default. You have to add it to the stateless plugin list (see above).
Page 39
Page 40
NetWeaver Version
WebView can be deployed on the Java stack of NetWeaver 04 or 2004s (SAP J2EE version 6.40 or 7.00).
Page 41
Required Options -Dsun.java2d.noddraw=true Make sure that -Djava.awt.headless=true is not set! -Djava.awt.headless=true -Dswing.volatileImageBufferEnabled=false -Djava.awt.headless=true -Dswing.volatileImageBufferEnabled=false -Djava.awt.headless=true -Dswing.volatileImageBufferEnabled=false Please check FAQ!
To configure SAP NetWeaver for WebView deployment: 1. Open the SAP J2EE config tool. 2. Select the server to modify. 3. In the Java Parameters field, add the parameters from the table above for your operating system. 4. Click the disk icon to save.
Start SDM
1. Start SDM via the command /usr/sap/<SID>/JC00/SDM/program/RemoteGui. 2. Connect to the running SDM server.
Page 42
Introscope Installation for SAP 6. From the Introscope CD, add the file WebView7.1netweaver.ear for deployment. The file is located in the folder webview. The SDM screen should look similar to the screenshot below.
7. Start deployment.
Note: These instructions assume you are installing WebView on the same machine as
the Introscope Enterprise Manager.
Page 43
Uninstalling Introscope
Uninstalling Introscope Agents
1. 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/sap_IntroscopeAgent.profile c. -Dcom.wily.introscope.agent.agentName=<AgentName> d. -javaagent:<some path>/wily/Agent.jar (Java 5 only) 2. Use SDM to undeploy the JmxService helper application (com.wilytech.jmxservice) in case it is still present from previous Introscope versions. 3. Restart the affected J2EE instances for the changes to become effective.
Page 44
Introscope Installation for SAP 4. Delete the directory <some path>/wily (or wherever you put the agent files).
Page 45
Step 2: Replicate the management modules: Step 2a: In the directory config/modules, create one subdirectory for each domain. 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.
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 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" /> 3. Add permissions for the user to the Superdomain in the domains.xml file: <grant user="X" permission="read" /> <grant user="X" permission="run_tracer" />
Introscope Version 7.1 Installation Guide for SAP (10/2/2007) Page 46
Introscope Installation for SAP Note: If you do not have a full license for Introscope, you cannot use permission=full here!
Page 47
Introscope Installation for SAP 6. Launch the Visual Administrator and connect to the SAP J2EE installation running WebView 7. Navigate to Server Services Web Container
8. Search for the application wilytech.com/com.wilytech.webview, open the tree by clicking on the + and select the first subentry.
9. Click View on the right hand side to get a popup. 10. Select the tab Context Parameters. 11. You will find the parameter introscope.webview.enterprisemanager.tcp.host. Change the value of this property from localhost to the IP address or host name of the remote host running the Enterprise Manager:
Page 48