Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
Highlighted
Honored Contributor.. Tom Meier Honored Contributor..
Honored Contributor..
357 views

SiteScope 11.33 to OMW 9.0 integration with monitors deployed to OMW Service-tree

Jump to solution

Hi all,

I’m using SiteScope 11.24 with OMW 9.0 and OA 11.14 in our Produktion.
In OMW services I got a sitescope service with all monitors and groups.

Now I want to upgrade to SiteScope 11.33.

So I built a test environment with a new SiteScope 11.33 Server and installed manually OA 12.01.
The integration to our OMW 9.0 test server was successful and I receive sitescope events on OMW console.
I also installed and deployed SiteScope Discovery Policy to the new SiteScope server.

But I didn’t get the SiteScope service tree and found in OA system.txt this failure:

0: ERR: Tue Jan 17 02:00:20 2017: agtrep (3808/5624): (agtrep-132) Error in executing discovery action(s): Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/axis/client/Service
 at java.lang.ClassLoader.defineClass1(Native Method)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
 at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
 at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
 at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
 at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
 at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
 at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:264)
 at com.mercury.sitescope.api.configuration.SiteScopeExternalAPIConnector.getSiteScopeExternalAPI(SiteScopeExternalAPIConnector.java:56)
 at com.mercury.sitescope.api.configuration.SiteScopeExternalAPIConnector.getAPIConfiguration(SiteScopeExternalAPIConnector.java:31)
 at com.mercury.sitescope.integrations.om.topology.common.APIExecuterUsingIntegrationViewer.execute(APIExecuterUsingIntegrationViewer.java:59)
 at com.mercury.sitescope.integrations.om.topology.monitors.OmDiscoveryXmlGeneratorVisitor.main(OmDiscoveryXmlGeneratorVisitor.java:26)
Caused by: java.lang.ClassNotFoundException: org.apache.axis.client.Service
 at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
 at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
 ... 18 more

0: ERR: Tue Jan 17 02:00:20 2017: agtrep (3808/5624): (agtrep-133) No output received from discovery policy action

Any idea what I did wrong?

Many thanks in advanced

Tom

Labels (1)
0 Likes
1 Solution

Accepted Solutions
Honored Contributor.. Tom Meier Honored Contributor..
Honored Contributor..

Re: SiteScope 11.33 to OMW 9.0 integration with monitors deployed to OMW Service-tree

Jump to solution

Hi all,

there is a failure in SiteScope OM integration jar filenames or in OM integration batch file.

In directory %sitescope_home%\integrations\om\lib you can find 15 jar files.

One jar file name has changed.

New file name: axis-SiteScope.jar

Old file name: axis.jar

All other 14 jar files has the same name as in 11.24.

But the class_path was not changed !

SiteScope Discovery police will also start:

%sitescope_home%\integrations\om\bin\run_api_call_om.bat

In the batch the set CLASS_PATH ..\lib\axis.jar …must be changed to ..\lib\axis-SiteScope,jar

After this change also monitors and groups will be transferred to OMW services.

 

best regards

Tom

0 Likes
3 Replies
Outstanding Contributor.. Allan_D_SIS Outstanding Contributor..
Outstanding Contributor..

Re: SiteScope 11.33 to OMW 9.0 integration with monitors deployed to OMW Service-tree

Jump to solution

Hello

In order to investigate further what is happening, please attach the following files:

1. Policy you mentioned (SiteScope Discovery Policy)...if possible.

2. system.txt (%ovdatadir%log)

3. agtrep.xml (%ovdatadir%datafiles)

Regards,

Allan D.

Allan Delgado Calderon
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
0 Likes
Honored Contributor.. Tom Meier Honored Contributor..
Honored Contributor..

Re: SiteScope 11.33 to OMW 9.0 integration with monitors deployed to OMW Service-tree

Jump to solution

Hi Allan,

thanks for helping me.

The policy I used comes with SiteScope in the directory:

%SiteScope_home%\tools\OMIntegration\SiteScopeMonitorDiscoveryPolicy\SiS_Discovery_policy_3.0\ForServer

and I followed SiteScopeMonitorDiscoveryPolicy_readme.docx

Here the contents from agtrep.xml file:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?><configuration>

I think in agtrep.xml should be more info.

Sorry, I could only updload pictures so I attached the policy in OMW console.

many thanks

Tom

0 Likes
Honored Contributor.. Tom Meier Honored Contributor..
Honored Contributor..

Re: SiteScope 11.33 to OMW 9.0 integration with monitors deployed to OMW Service-tree

Jump to solution

Hi all,

there is a failure in SiteScope OM integration jar filenames or in OM integration batch file.

In directory %sitescope_home%\integrations\om\lib you can find 15 jar files.

One jar file name has changed.

New file name: axis-SiteScope.jar

Old file name: axis.jar

All other 14 jar files has the same name as in 11.24.

But the class_path was not changed !

SiteScope Discovery police will also start:

%sitescope_home%\integrations\om\bin\run_api_call_om.bat

In the batch the set CLASS_PATH ..\lib\axis.jar …must be changed to ..\lib\axis-SiteScope,jar

After this change also monitors and groups will be transferred to OMW services.

 

best regards

Tom

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.