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
Daniel Super Contributor.
Super Contributor.
332 views

Unable to create websphere 8.5 monitor

Jump to solution

I'm trying to create a websphere 8.5 monitor on sitescope 11.33. I have been following this instructions (http://sitescope-help.saas.hpe.com/en/11.33/Online/Content/Refer/MR_WebSphere_AS_Mon.htm)

The websphere is on the same network, no firewalls in between

I have imported the following jks and jar files:
    com.ibm.ws.admin.client_8.5.0.jar
    com.ibm.ws.runtime.jar
    DummyClientKeyFile.jks
    DummyClientTrustFile.jks
    ibmorb.jar

I have also changed the websphere.props on the SiteScope\templates.application\websphere.props with the following:
I'm not sure if the information for WAS 8.5 was correct.
    was85x_classpath=com.ibm.ws.admin.client_8.5.0.jar;com.ibm.ws.runtime.jar;

Also, I have tested the configuration. I got all the step successful but the step 6 to test the connection against the websphere.
I notice that on the step 6 says that "Some of the jars were missed from WebSphere client folder", but I have imported all the necessary files.

Step 1: Check jars from WAS client directory to use as additional classpath: 
Next jars will be added to classpath: 
D:\was_monitors\<<server_name>>\com.ibm.ws.admin.client_8.5.0.jar 
D:\was_monitors\<<server_name>>\com.ibm.ws.runtime.jar 
D:\was_monitors\<<server_name>>\ibmorb.jar  

Step 2: Check secure jar from WAS (skip this step if SSL is not used): 
Check com.ibm.ws.security.crypto*: 
..\java\lib\ext\com.ibm.ws.security.crypto.jar - exists.  

Step 3: Check JVM security option in the java.security file (skip this step if SSL is not used): 
Next lines were found: 
ssl.ServerSocketFactory.provider=sun.security.ssl.SSLServerSocketFactoryImpl 
ssl.SocketFactory.provider=sun.security.ssl.SSLSocketFactoryImpl  

Step 4: Check that the certificate was imported into the java key store (skip this step if SSL is not used): 
All certificates were imported into SiteScope key store  

Step 5: Check Trust and Key Store files: 
D:\was_monitors\<<server_name>>\DummyClientTrustFile.jks - exists. 
D:\was_monitors\<<server_name>>\DummyClientKeyFile.jks - exists.  

Step 6: Result of test connection: 
ADMC0016E: The system cannot create a SOAP connector to connect to host <<server_name>> at port 8880.; nested exception is: com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host <<server_name>> at port 8880. 
Some of the jars were missed from WebSphere client folder

This is the error I got from the logs:

2018-04-09 17:51:35,671 [WebSphereBaseUpdater] (WebSphereAbstractUpdater.java:91) ERROR - Could not connect to WebSphere Application Server. A connector to WebSphere Application Server could not be created due to an exception. WebSphere Application Server connector was expected to be non-null, but was null: webSphereServerConnector=null
2018-04-09 17:51:35,671 [http-bio-443-exec-3] (WebSphereMonitor.java:707) ERROR - Could not make a connection to WebSphere Application Server. Please check the connection properties, verify that the application server is running and try again (See the logs for details)
com.mercury.sitescope.monitors.j2ee.websphere.internaljvm.exceptions.WebSphereServerConnectorException: Exception occurred while instantiating com.mercury.sitescope.monitors.j2ee.websphere.WebSphereMonitorJMX
	at com.mercury.sitescope.monitors.j2ee.websphere.internaljvm.connector.WebSphereServerConnector.initMonitorImplInstance(WebSphereServerConnector.java:51)
	at com.mercury.sitescope.monitors.j2ee.websphere.internaljvm.connector.WebSphereServerConnector.<init>(WebSphereServerConnector.java:37)
	at com.mercury.sitescope.monitors.j2ee.websphere.internaljvm.WebSphereAbstractUpdater.initWebSphereServerConnector(WebSphereAbstractUpdater.java:156)
	at com.mercury.sitescope.monitors.j2ee.websphere.internaljvm.WebSphereAbstractUpdater.execute(WebSphereAbstractUpdater.java:82)
	at com.mercury.sitescope.monitors.j2ee.websphere.internaljvm.WebSphereAbstractUpdater.run(WebSphereAbstractUpdater.java:62)
	at java.lang.Thread.run(Thread.java:745)
Caused by: com.mercury.sitescope.monitors.j2ee.rmiprocess.ConnectionException: ADMC0016E: The system cannot create a SOAP connector to connect to host <<server_name>> at port 8880.; nested exception is: 
	com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host <<server_name>> at port 8880.
	at com.mercury.sitescope.monitors.j2ee.websphere.WebSphereMonitorJMX.connect(WebSphereMonitorJMX.java:155)
	at com.mercury.sitescope.monitors.j2ee.websphere.WebSphereMonitorJMX.<init>(WebSphereMonitorJMX.java:88)
	at sun.reflect.GeneratedConstructorAccessor414.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at com.mercury.sitescope.monitors.j2ee.websphere.internaljvm.connector.WebSphereServerConnector.initMonitorImplInstance(WebSphereServerConnector.java:47)
	... 5 more
Caused by: com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host <<server_name>> at port 8880.
	at com.ibm.websphere.management.AdminClientFactory.createAdminClientPrivileged(AdminClientFactory.java:635)
	at com.ibm.websphere.management.AdminClientFactory.access$000(AdminClientFactory.java:127)
	at com.ibm.websphere.management.AdminClientFactory$1.run(AdminClientFactory.java:210)
	at java.security.AccessController.doPrivileged(Native Method)
	at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:65)
	at com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:206)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at com.mercury.sitescope.monitors.j2ee.websphere.WebSphereMonitorJMX.connect(WebSphereMonitorJMX.java:140)
	... 10 more
Caused by: java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at com.ibm.websphere.management.AdminClientFactory.createAdminClientPrivileged(AdminClientFactory.java:457)
	... 20 more
Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.ibm.ws.management.connector.soap.AdminServiceSMR
	at com.ibm.ws.management.connector.soap.SOAPConnectorClient.<init>(SOAPConnectorClient.java:147)
	... 25 more
2018-04-09 17:51:40,351 [WebSphereBaseUpdater] (WebSphereAbstractUpdater.java:91) ERROR - Could not connect to WebSphere Application Server. A connector to WebSphere Application Server could not be created due to an exception. WebSphere Application Server connector was expected to be non-null, but was null: webSphereServerConnector=null
2018-04-09 17:51:40,351 [http-bio-443-exec-3] (WebSphereMonitor.java:707) ERROR - Could not make a connection to WebSphere Application Server. Please check the connection properties, verify that the application server is running and try again (See the logs for details)
com.mercury.sitescope.monitors.j2ee.websphere.internaljvm.exceptions.WebSphereServerConnectorException: Exception occurred while instantiating com.mercury.sitescope.monitors.j2ee.websphere.WebSphereMonitorJMX
	at com.mercury.sitescope.monitors.j2ee.websphere.internaljvm.connector.WebSphereServerConnector.initMonitorImplInstance(WebSphereServerConnector.java:51)
	at com.mercury.sitescope.monitors.j2ee.websphere.internaljvm.connector.WebSphereServerConnector.<init>(WebSphereServerConnector.java:37)
	at com.mercury.sitescope.monitors.j2ee.websphere.internaljvm.WebSphereAbstractUpdater.initWebSphereServerConnector(WebSphereAbstractUpdater.java:156)
	at com.mercury.sitescope.monitors.j2ee.websphere.internaljvm.WebSphereAbstractUpdater.execute(WebSphereAbstractUpdater.java:82)
	at com.mercury.sitescope.monitors.j2ee.websphere.internaljvm.WebSphereAbstractUpdater.run(WebSphereAbstractUpdater.java:62)
	at java.lang.Thread.run(Thread.java:745)
Caused by: com.mercury.sitescope.monitors.j2ee.rmiprocess.ConnectionException: ADMC0016E: The system cannot create a SOAP connector to connect to host <<server_name>> at port 8880.; nested exception is: 
	com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host <<server_name>> at port 8880.
	at com.mercury.sitescope.monitors.j2ee.websphere.WebSphereMonitorJMX.connect(WebSphereMonitorJMX.java:155)
	at com.mercury.sitescope.monitors.j2ee.websphere.WebSphereMonitorJMX.<init>(WebSphereMonitorJMX.java:88)
	at sun.reflect.GeneratedConstructorAccessor414.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at com.mercury.sitescope.monitors.j2ee.websphere.internaljvm.connector.WebSphereServerConnector.initMonitorImplInstance(WebSphereServerConnector.java:47)
	... 5 more
Caused by: com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host <<server_name>> at port 8880.
	at com.ibm.websphere.management.AdminClientFactory.createAdminClientPrivileged(AdminClientFactory.java:635)
	at com.ibm.websphere.management.AdminClientFactory.access$000(AdminClientFactory.java:127)
	at com.ibm.websphere.management.AdminClientFactory$1.run(AdminClientFactory.java:210)
	at java.security.AccessController.doPrivileged(Native Method)
	at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:65)
	at com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:206)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at com.mercury.sitescope.monitors.j2ee.websphere.WebSphereMonitorJMX.connect(WebSphereMonitorJMX.java:140)
	... 10 more
Caused by: java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at com.ibm.websphere.management.AdminClientFactory.createAdminClientPrivileged(AdminClientFactory.java:457)
	... 20 more
Caused by: java.lang.NoClassDefFoundError: Could not initialize class com.ibm.ws.management.connector.soap.AdminServiceSMR
	at com.ibm.ws.management.connector.soap.SOAPConnectorClient.<init>(SOAPConnectorClient.java:147)
	... 25 more

Any idea about this problem?

0 Likes
1 Solution

Accepted Solutions
Micro Focus Expert
Micro Focus Expert

Re: Unable to create websphere 8.5 monitor

Jump to solution

Hello Daniel,

Please find below a link with another forum with the answer:

https://community.softwaregrp.com/t5/SiteScope-Practitioners-Forum/WebSphere-8-5-monitor-error/m-p/1641018/highlight/false#M7917

Hope this can help you,

Regards,

 

Miguel Torres
Micro Focus SW Support

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.

[Opinions expressed in my postings are mine alone, and do not reflect the opinions of my employer.No warranties express or implied for any solution/suggestion posted.]
0 Likes
1 Reply
Micro Focus Expert
Micro Focus Expert

Re: Unable to create websphere 8.5 monitor

Jump to solution

Hello Daniel,

Please find below a link with another forum with the answer:

https://community.softwaregrp.com/t5/SiteScope-Practitioners-Forum/WebSphere-8-5-monitor-error/m-p/1641018/highlight/false#M7917

Hope this can help you,

Regards,

 

Miguel Torres
Micro Focus SW Support

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.

[Opinions expressed in my postings are mine alone, and do not reflect the opinions of my employer.No warranties express or implied for any solution/suggestion posted.]
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.