Documente Academic
Documente Profesional
Documente Cultură
1
Installation Guide
For SAP
September 2007
Introscope Installation for SAP
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
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.
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:
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
• 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
Installation User
You should run the installer with the same user account that will be used later on for
running the Enterprise Manager. In particular, on Unix operating systems do not use the
root account to launch the installer. A common best practice is to use the sidadm user of
the Solution Manager installation to install and run the Enterprise Manager.
i5/OS introscope7.1.P9os400SAPEndUser.jar
* 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.
The operating system independent installer is contained in the file SAPISEM71.SAR of the
folder #OS independent on the Service Marketplace.
After installation, you can check the results in the installer logs.
When launching the installer, make sure the installer.properties file is in the same
directory as the .exe / .bin / .jar file!
If you want to change this directory, e.g., because your SAP installation is located on a
different Windows drive, use one of the following alternatives.
Note: Use slash (/) as path separator for all platforms, including Windows!
Note: The instructions in this guide will use examples relative to the default
installation directory.
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)
Installation: Successful.
166 SUCCESSES
0 WARNINGS
0 NONFATAL ERRORS
0 FATAL ERRORS
Note: The number of successes may be different than what is shown in this example.
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
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 i5/OS, set the Java heap size properties to -Xms64m –Xmx2048m
Example:
cd /usr/sap/ccms/wilyintroscope
SAPCAR –xvf SAPISMM71_xx.SAR
As a result you will find one or more .jar files in the subdirectory config/modules,
some .js files in the subdirectory scripts, and some other files distributed over the
Enterprise Manager installation.
The newly installed management modules only become active after the Enterprise
Manager is (re-)started. For Windows installations the Enterprise Manager is typically
automatically launched as Windows Service. This means you will have to restart the
Windows Service for the Enterprise Manager.
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
Introscope_Enterprise_Manager does not work correctly with nohup. The effect is
that the Enterprise Manager does not fully launch. In this case, please adapt the shell script
runem.nohup.sh to your needs and use this to launch the EM:
nohup ./runem.nohup.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.
To activate the Wily Enterprise Manager at system startup, you should add an Autostart
Job Entry to the subsystem QUSRWRK. To achieve this, run the following commands:
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
chown –R <Your User> /usr/sap/ccms/wilyintroscope
in QSHELL.
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:
cd /usr/sap/ccms/wilyintroscope
nohup runem.sh &
Alternatively you can submit the Enterprise Manager to Batch via:
SBMJOB CMD(QSH CMD('cd /usr/sap/ccms/wilyintroscope &&
/usr/sap/ccms/wilyintroscope/runem.sh')) JOB(WILYEM) CPYENVVAR(*YES)
ALWMLTTHD(*YES)
On Other Platforms
On other platforms, switch to the <Introscope home> directory, then launch the
Enterprise Manager with the command:
./Introscope_Enterprise_Manager
3. Check the TCP port that Introscope Enterprise Manager is using for agent connections.
Look for lines similar to the following in the logfile:
In this case, the Enterprise Manager agent port is 6001 (default value).
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.
SAP provides several agent profiles for different applications running on the SAP J2EE
Engine. All profiles adhere to the name pattern sap_IntroscopeAgent*.profile. You will
have to choose one of the profiles from the table below. Currently the following profiles are
available:
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.
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.
By default, the Introscope agents write log files to the subdirectory logs (e.g.
/usr/sap/ccms/wily/logs). On Unix systems, make sure that the monitored systems
(user sidadm) have write access to this directory (write permission for group sapsys). As
an alternative, you can change the properties introscope.autoprobe.logfile and
log4j.appender.logfile.File to some other directories where the monitored systems
have write access.
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.
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:
Example:
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
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.
The procedure to add JVM options depends on the startup method for the J2EE nodes.
Check SAP Note 697162 for instructions to set JVM options for your specific startup
method. The following procedure is an example in case you use SAP J2EE startup
framework for J2EE 6.20:
1. Open the file:
<drive>:\usr\sap\<J2EE_ENGINE_ID>\j2ee\j2ee_<INSTANCE>\configtool\servi
ce.ini
-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>
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>
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>
7. To verify that Config tool changes were made, open the file:
<drive>:\usr\sap\<SID>\<instance>\j2ee\cluster\instance.properties
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>
<drive>:\usr\sap\<SID>\<instance>\j2ee\cluster\instance.properties
The procedure to add JVM options for the IPC to enable Introscope is described in SAP Note
886600. Note that Introscope does not support IPC running in the VM container (VMC) as
it is delivered for SAP CRM 5.0.
You have to modify the .bat file that launches the servlet engine. A typical location for the
file is C:\servletExec AS\se-LHCMS\StartServletExec.bat . Add the following
Java VM parameters:
-Xbootclasspath/p:<drive>:/usr/sap/ccms/wily/connectors/connector.j
ar;<drive>:/usr/sap/ccms/wily/Agent.jar
-Dcom.wily.introscope.agentProfile=<drive>:/usr/sap/ccms/wily/sap_I
ntroscopeAgent.profile
-Dcom.wily.introscope.agent.agentName=<AgentName>
Further information on integrating xMII into Solution Manager Diagnostics can be found in
SAP Note 903825.
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
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.
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.
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
b. by directly starting the file Introscope Workstation.exe in the installation directory.
6 Introscope-Enabling Duet
ASP.NET Applications
This chapter describes installing and configuring the Introscope .NET Agent with Duet. The
following steps are required:
• Installing the Intoscope .NET Agent
• Set up user permissions for Agent Directory
• Configure Introscope .NET Agent settings
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.
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.
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:
\install
\UninstallerData
\wily
sap_default-full.pbl
sap_IntroscopeAgent_Duet.profile
sap_IntroscopeAgent_custom.profile
Into the \wily subdirectory of the AgentHome directory, usually:
<drive>:\usr\sap\ccms\wilydotnet\wily
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.
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.
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.
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
Enter either the host name or IP address of the machine where Enterprise Manager
resides.
The value should be the port on which the Enterprise Manager listens for Agent
connections.
Default setting is 6001.
4. Save changes to the IntroscopeAgent.profile.
Restart IIS
To restart the IIS open a command prompt window and execute the following command:
iisreset /restart
7 Environment Performance
Agent Installation
Note: The recommended procedure to install and customize the EPAgent 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 below.
The plugin is calling saposcol with the path you specify above to retrieve monitoring data,
so the user running the EPAgent needs permission to execute saposcol.
For SAP J2EE 6.40 and 7.00, monitoring of the files std_servern.out is recommended and
supported. For each monitored file, one line must be added to the
SapGcScanner.properties file in the following format:
file.P40_server1=C:/usr/sap/P40/JC00/work/std_server1.out
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).
SAP_WMI_IIS IIS
If you do not have a java.exe (at least java 1.4) in your PATH, edit the property
wrapper.java.command in config/EPAService.conf.
You may have to adapt the path to a java 1.4 VM in the shell script before.
This chapter describes installing and deploying WebView on the Java stack of SAP
NetWeaver. Information is provided in the following sections:
• System and Version Requirements
• Reviewing Installation and Configuration Process
• Installing and Configuring WebView with SAP NetWeaver
NetWeaver Version
WebView can be deployed on the Java stack of NetWeaver 04 or 2004s (SAP J2EE version
6.40 or 7.00).
-Djava.awt.headless=true
Solaris
-Dswing.volatileImageBufferEnabled=false
-Djava.awt.headless=true
Linux
-Dswing.volatileImageBufferEnabled=false
-Djava.awt.headless=true
HP UX
-Dswing.volatileImageBufferEnabled=false
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.
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.
2. Launch WebView via Solution Manager Diagnostics (Menu Entry J2EE Server Analysis)
or directly via URL http://host:5xx00/webview. You should get a login screen from the
WebView application and a message below the login frame similar to the following:
This WebView instance is connected to the Enterprise Manager on localhost.
There are 3 agent(s) reporting..
3. Log in to WebView with one of the user accounts listed in Chapter 1 and open the
Console. Click to open some so-called dashboards and check if some charts are
displayed.
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.
4. Delete the directory <some path>/wily (or wherever you put the agent files).
Step 2b: copy all management modules from config/modules to each subdirectory.
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" />
Note: If you do not have a full license for Introscope, you cannot use permission=”full”
here!
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.