Wily Introscope Agent for xMII 11.5

[Former Member]

Hi guys -

I was wondering if someone has already implemented Wily Introscope monitoring for xMII 11.5 servers. I currently have Introscope 8.0 Enterprise Manager setup already and I have managed to hook up agents on EP 7.0 server.

I tried to download a couple of agents for our 32 bit xMII app servers but while creating the java connector it throws up error complaining about incorrect version major.minor

ISEM - SAPISEM02_1-10007433.SAR

ISMM - SAPISMM02_1-10007429.SAR

ISAGENT - ISAGENTSTD02_3-10007435.SAR (I did not use SMD for setup)

Any help in this regard is much appreciated!

Kind Regards,

RazaMahdi Rivi.

[Former Member · Accepted solution]

Hello RazaMahdi,

Did you download the compatible wily agent version for 32bit OS. Once you have installed Wily agent on xMII systems follow the below steps to connect the agent to enterprise manager.

You have to create a AutoProbe connector that fits for the Java VM that you use:

Use the CreateAutoProbeConnector.jar tool to create a connector specific to the JVM used to run the application server. There are two ways to specify the JVM:

u2022 use the JVM that is running the tool

u2022 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:

u2022 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 /usr/java14 -output ConnectorXMII.jar

3. The output is the file: <drive>:\usr\sap\ccms\wily\connectors\ConnectorXMII.jar

After creating the autoprobe connector, you have to manually set java parameters in StartServletExec.bat file to activate the wily agent. StartServletExec.bat file is located in <>\ServletExec AS\se-xMII

-Xbootclasspath/p:C:/usr/sap/ccms/wily/connectors/ConnectorXMII.jar;C:/usr/sap/ccms/wily/Agent.jar

-Dcom.wily.introscope.agentProfile=C:/usr/sap/ccms/wily/IntroscopeAgent.profile

-Dcom.wily.introscope.agent.agentName=XMIIAgent

Delete, install and start ServletExec service.

Delete Service

******************

C:\ServletExec AS\bin>DeleteNTService.exe -n ServletExec-xMII <Enter>

Install NT Service

*********************

C:\ServletExec AS\bin>InstallNTService.exe -n "ServletExec-xMII" -start "C:\ServletExec AS\se-xMII\StartServletExec.bat" -stop "C:\ServletExec AS\se-xMII\StopServletExec.bat" <Enter>

Wily agent on MII system should now start reporting metrics to enterprise manager.

[Former Member · Accepted solution]

Hello Aravind -

Many thanks for your quick reply ... I am still not able to find the 32 bit version for the agent. Here is what I did earlier too..

I downloaded the Agent for 32 bit (ours is x86)however SWDC only has 32 for Win IA32:

SAP Technology Components" --> SAP SOLUTION MANAGER" --> SAP SOLUTION MANAGER 7.0 EHP 1" --> Entry by Component" --> Agents for managed systems -->

WILY INTROSCOPE AGENT 8

1. OS independent

SAR ISAGENT801_01-10007435.SAR Patch for WILY INTROSCOPE AGENT 8 SP01

SAR ISAGENT8SP01_00-10007435.SAR SP01 for WILY INTROSCOPE AGENT 8

DIAGNOSTICS AGENT 7.11

AIX 64bit

HP-UX on IA64 64bit

HP-UX on PA-RISC 64bit

Linux on IA32 32bit

Linux on IA64 64bit

Linux on Power 64bit

Linux on x86_64 64bit

Solaris on SPARC 64bit

Solaris on x64_64 64bit

Windows Server on IA32 32bit

Windows Server on IA64 64bit

Windows Server on x64 64bit

I have used ISAGENT8SP01_00-10007435.SAR for my Agent, however the output is

"C:\usr\sap\ccms\wily\connectors>java -jar CreateAutoProbeConnector.jar -jvm C:\j

2sdk1.4.2_07 -output connector.jar

Exception in thread "main" java.lang.UnsupportedClassVersionError: com/wily/intr

oscope/api/CreateAutoProbeConnector (Unsupported major.minor version 48.0)

at java.lang.ClassLoader.defineClass0(Native Method)

at java.lang.ClassLoader.defineClass(Unknown Source)

at java.security.SecureClassLoader.defineClass(Unknown Source)

at java.net.URLClassLoader.defineClass(Unknown Source)

at java.net.URLClassLoader.access$100(Unknown Source)

at java.net.URLClassLoader$1.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

at java.lang.ClassLoader.loadClassInternal(Unknown Source)

"

Thanks & Regards,

RazaMahdi.

Edited by: RazaMahdi Rizvi on Apr 2, 2011 4:08 AM

[Former Member · Accepted solution]

I am getting the following error on xMII (11.5) 32 bit Windows server:

C:\usr\sap\ccms\wily\connectors>java -jar CreateAutoProbeConnector.jar -jvm C:\j

2sdk1.4.2_07 -output connector.jar

Exception in thread "main" java.lang.UnsupportedClassVersionError: com/wily/intr

oscope/api/CreateAutoProbeConnector (Unsupported major.minor version 48.0)

at java.lang.ClassLoader.defineClass0(Native Method)

at java.lang.ClassLoader.defineClass(Unknown Source)

at java.security.SecureClassLoader.defineClass(Unknown Source)

at java.net.URLClassLoader.defineClass(Unknown Source)

at java.net.URLClassLoader.access$100(Unknown Source)

at java.net.URLClassLoader$1.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

at java.lang.ClassLoader.loadClassInternal(Unknown Source)

C:\usr\sap\ccms\wily\connectors>set path

Path=E:\oracle\ora92\bin;E:\Oracle\RIVET\920\bin;C:\Program Files\Oracle\jre\1.3

.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\Program Files\HP\NCU;C:\WINDOWS\

system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Windows Imaging\;C

:\j2sdk1.4.2_07

C:\usr\sap\ccms\wily\connectors>set JAVA_HOME

JAVA_HOME=C:\j2sdk1.4.2_07

Can someone please suggest what is wrong...

Thanks,

RazaMahdi.