• Changing the Agent port from 6001 to other values
• Uninstalling Introscope
• Setting up domains
• User Management
• Activating Leak Hunter
• Running WebView and Enterprise Manager on Different Hosts
Change the Agent Port
The Enterprise Manager by default listens on TCP port 6001 for agent connections. You can change this value to any desired port:
1. Open the file,config/IntroscopeEnterpriseManager.properties.
2. Change the value of propertyintroscope.enterprisemanager.port.channel1
to the desired port.
3. Save changes and close the file.
4. Remember to change the property in thesap_IntroscopeAgent.profile to the
same port.
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.
4. Delete the directory <some path>/wily (or wherever you put the agent files).
Uninstalling Environment Performance Agents
1. On Windows only: Call the script DeregisterEPAService.bat to stop and unregister the Windows service.
2. On other platforms: Stop the Java VM containing the EPAgent. 3. Delete the complete directory containing the EPAgent installation.
Uninstalling the Enterprise Manager
1. Windows only: Call the batch file DeRegisterEMservice.bat to remove the Windows Service
2. Windows only: Call the wizard to uninstall Introscope: Start Control Panel Add or Remove Programs; Select Introscope and click change/remove to launch the Wizard. Click Next to continue the uninstall.
3. Remove any remaining files from /usr/sap/ccms/wilyintroscope.
Uninstalling WebView on Netweawer
1. Use SDM to undeploy the applicationcom.wilytech.webview if you still have a copy
of WebView deployed on NetWeaver.
Setting up Introscope Domains
Introscope agents can be organized into so-called domains. You can use this feature to group agents which are correlated, e.g. belonging to the same domain.
Domains are defined in the Enterprise Manager by the configuration file
config/domains.xml. By default, there is only one domain, the SuperDomain, which contains all agents. SAP recommends defining one domain for each system or for each main instance (in Solution Manager Diagnostics terms). You can pick agents for a domain based on the host name and on the agent name.
Example: Assume you want to create two domains EPP and EPQ for the productive and the QA Enterprise Portal. Your agent names contain the System id (also EPQ, EPP).
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" />
Note: If you do not have a full license for Introscope, you cannot use permission=”full” here!
Activating Leak Hunter
Leak Hunter is an additional Introscope feature for detecting memory leaks that is by default disabled. Leakhunter may have substantial impact on the Java memory footprint and on the response time for any Java VM where you activate
Leakhunter: Only activate Leakhunter when needed, e.g., if you discover permanently increasing memory consumption in spite of several full garbage collections. It may furthermore be advisable to increase the Java heap before activating Leakhunter to compensate additional memory requirements of Leakhunter. To activate Leakhunter proceed as follows:
1. Set introscope.agent.leakhunter.enable=true in the agent profile used for the JVM with potential leak.
2. Set the introscope.agent.leakhunter.timeoutInMinutes property to the number of minutes that you want LeakHunter to look for new leaks. During this period, the Introscope agent will use more memory, the amount depending on how many Java Collection classes the NetWeaver JVM uses. Set to the shortest period that is long enough to insure that all application funcationality gets invoked within the active leak hunting window. For instance, if you restart the JVM at 5pm but don’t expect to have significant load on the JVM until 9am the next day, then you would set it to 1140 minutes (19 hours) so that LeakHunter searches for leaks until 12pm the next day giving 3 hours of leak hunting during active use. If you knew you were going to run significant load through the JVM right after restarting, you could set the timeout to 120 or 240 minutes.
3. Leave introscope.agent.leakhunter.collectAllocationStackTraces set to false since setting it to true requires more memory. If your JVM has spare memory available after running LeakHunter with this set to false, you could try setting to true if you feel you need to see the stacktraces to understand the source of your leak.
4. Add sap_leakhunter.jar to the introscope.autoprobe.directivesFile property in the agent profile, separating it from other JARs or PBDs with a comma.
5. Restart the JVM with the suspect memory leak.
6. Look for a new LeakHunter node under agent in the Investigator window of the Introscope Workstation.
Running WebView and EM on Different Hosts (WebView
on NetWeaver only)
When running WebView on a different host than the Enterprise Manager, you must configure WebView to connect to the Enterprise Manager on the remote host. Use the Visual Adminstrator of SAP J2EE:
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: