websphere discovery help

ebailey · ‎10-24-2006

Hello,

We are evaluating hyperic for our many servers and so far we are happy except for one notable issue. We cannot get hyperic to auto-discover any of our websphere servers nor can we manually add websphere.

PMI is turned on. In Websphere 6 their is no standard level of monitoring, just basic and extended. I used the basic level

I set the install path in agent.proproties to /opt/IBM/WebSphere and restarted the agent

After restarting the agent I had the server run auto-discover and I entered the path to websphere in the path field. Nothing appeared once auto-discover was done.

I tried to manually add websphere by creating a server then editing the configuration to auto-discover pools and such. Each time I get the following error in the web interface and the agent log file.

2006-10-24 15:48:25,266 ERROR [MeasurementCommandsServer] Error getting real time measurement: Plugin error: Plugin class not found: com/ibm/websphere/management/exception/ConnectorException (invalid classpath or corrupt plugin jar)

Any idea what I need to do to get this working?

Thanks

Ed

ebailey · ‎10-24-2006

another error I found in the hyperic server log

2006-10-24 16:21:08,017 ERROR [org.hyperic.hq.ui.action.resource.common.inventory.EditConfigPropertiesAction] invalid config org.hyperic.hq.appdef.shared.InvalidConfigException: Invalid configuration: Plugin error: Plugin class not found: com/ibm/websphere/management/exception/ConnectorException (invalid classpath or corrupt plugin jar)
[1]-NESTED-EXCEPTION:
org.hyperic.hq.measurement.monitor.LiveMeasurementException: Plugin error: Plugin class not found: com/ibm/websphere/management/exception/ConnectorException (invalid classpath or corrupt plugin jar)

dougm_hyperic · ‎10-24-2006

What version of HQ are you using and on what OS?
Are you using WebSphere 6.0 or 6.1?

On Oct 24, 2006, at 1:10 PM, Ed Bailey wrote:

> Hello,
>
> We are evaluating hyperic for our many servers and so far we are
> happy except for one notable issue. We cannot get hyperic to auto-
> discover any of our websphere servers nor can we manually add
> websphere.
>
> PMI is turned on. In Websphere 6 their is no standard level of
> monitoring, just basic and extended. I used the basic level
>
> I set the install path in agent.proproties to /opt/IBM/WebSphere
> and restarted the agent
>
> After restarting the agent I had the server run auto-discover and I
> entered the path to websphere in the path field. Nothing appeared
> once auto-discover was done.
>
> I tried to manually add websphere by creating a server then editing
> the configuration to auto-discover pools and such. Each time I get
> the following error in the web interface and the agent log file.
>
> 2006-10-24 15:48:25,266 ERROR [MeasurementCommandsServer] Error
> getting real time measurement: Plugin error: Plugin class not
> found: com/ibm/websphere/management/exception/ConnectorException
> (invalid classpath or corrupt plugin jar)
>
> Any idea what I need to do to get this working?
>
> Thanks
>
> Ed

ebailey · ‎10-24-2006

Hi,

I am using websphere 6.0 and the latest release of hyperic 2.7.5

Thanks

Ed

redhat es 4.0 is the OS

Message was edited by: ebailey

dougm_hyperic · ‎10-25-2006

What OS are you running on? You shouldn't actually need to change
the agent.properties, but if you do, make sure lib/management.jar
exists relative to that path. You might just need to change to:
websphere.installpath=/opt/IBM/WebSphere/AppServer

Which is the default 6.0 installpath.

On Oct 24, 2006, at 9:27 PM, Ed Bailey wrote:

> Hi,
>
> I am using websphere 6.0 and the latest release of hyperic 2.7.5.
>
> Thanks
>
> Ed

ebailey · ‎10-26-2006

I am running websphere on RedHat Linux ES 3.0

I had already set the path in agent.properties and then restarted the agent but still no luck. Also I checked and management.jar is where it is supposed to be.

I installed the enterprise trial and it could not find websphere either. I tried to manually add the server and saw the following error

2006-10-26 09:36:54,234 ERROR [MeasurementCommandsServer] Error getting real time measurement: Plugin error: Plugin class not found: com/ibm/websphere/pmi/client/PmiClient (invalid classpath or corrupt plugin jar)

Any ideas?

Is their a way to get some sort of debug information from the agent log during auto discovery?

Thanks

Ed

dougm_hyperic · ‎10-26-2006

You shouldn't have to modify the websphere.installpath in
agent.properties on Linux, it should be auto-discovered if WebSphere
is running when the agent is started.
The exception is Solaris, where currently the user must be root or
the same user as WAS to read the process arguments.
You can enable debug logging, see: http://support.hyperic.com/
confluence/display/DOCSHQ27/HQ+Agent
+Configuration#HQAgentConfiguration-agentdebuglog
In log/agent.log, you'll see messages along the lines of:

DEBUG [WebsphereProductPlugin] websphere.installpath found in process
table
DEBUG [WebsphereProductPlugin] Using profile: default
DEBUG [WebsphereProductPlugin] Using soap properties: /opt/WebSphere6/
AppServer/profiles/default/properties/soap.client.props
DEBUG [ProductPluginManager] adding to websphere classpath:
DEBUG [ProductPluginManager] + /opt/WebSphere6/AppServer/java/jre/
lib/core.jar
DEBUG [ProductPluginManager] - /opt/WebSphere6/AppServer/java/jre/
lib/ext/log.jar
DEBUG [ProductPluginManager] + /opt/WebSphere6/AppServer/lib/
bootstrap.jar
DEBUG [ProductPluginManager] + /opt/WebSphere6/AppServer/lib/
wssec.jar
DEBUG [ProductPluginManager] + /opt/WebSphere6/AppServer/lib/
pmiclient.jar
DEBUG [ProductPluginManager] + /opt/WebSphere6/AppServer/lib/
wasjmx.jar

The PmiClient client class lives in lib/pmiclient.jar

+ == File exists and is readable
~ == File exists but is not readable
- == File does not exist (ok if there are a few, since the classpath
includes 5.x jars too)

To make sure we're looking at the same version here, please post this
from your websphere.installpath:
% cat properties/version/wasproduct.component

On Oct 26, 2006, at 6:53 AM, Ed Bailey wrote:

> I am running websphere on RedHat Linux ES 3.0
>
> I had already set the path in agent.properties and then restarted
> the agent but still no luck. Also I checked and management.jar is
> where it is supposed to be.
>
> I installed the enterprise trial and it could not find websphere
> either. I tried to manually add the server and saw the following error
>
> 2006-10-26 09:36:54,234 ERROR [MeasurementCommandsServer] Error
> getting real time measurement: Plugin error: Plugin class not
> found: com/ibm/websphere/pmi/client/PmiClient (invalid classpath or
> corrupt plugin jar)
>
> Any ideas?
>
> Is their a way to get some sort of debug information from the agent
> log during auto discovery?
>
> Thanks
>
> Ed

ebailey · ‎10-31-2006

Thanks - I will give your idea a try and let you know what happened.

Ed

dougm_hyperic · ‎11-07-2006

Any luck with this Ed?

On Oct 31, 2006, at 2:16 PM, Ed Bailey wrote:

> Thanks - I will give your idea a try and let you know what happened.
>
> Ed

ebailey · ‎11-08-2006

Sorry it took so long to get back to you - I can now see the issue. A corporate guy did the install and nothing is where it should be. Anyway to work around this? Would using symlinks work?

Thanks

Ed

Agent logs are below -

2006-11-08 10:50:37,420 DEBUG [AutoScan] Running AutoServerDetector for: WebSphere Admin 5.0
2006-11-08 10:50:37,421 DEBUG [WebsphereDetector] WebSphere Admin 5.0 '/opt/IBM/WebSphere/AppSrv/lib/jmxc.jar'. exists()=false
2006-11-08 10:50:37,421 DEBUG [WebsphereDetector] WebSphere Admin 5.0 '/opt/IBM/WebSphere/Dmgr/lib/jmxc.jar'.ex ists()=false
2006-11-08 10:50:37,422 DEBUG [WebsphereDetector] WebSphere Admin 5.0 '/opt/IBM/WebSphere/AppSrv/lib/jmxc.jar'. exists()=false
2006-11-08 10:50:37,422 DEBUG [AutoScan] Running AutoServerDetector for: WebSphere Admin 6.0
2006-11-08 10:50:37,422 DEBUG [WebsphereDetector] WebSphere Admin 6.0 '/opt/IBM/WebSphere/AppSrv/../../properti es/version/WAS.product'.exists()=false
2006-11-08 10:50:37,422 DEBUG [WebsphereDetector] WebSphere Admin 6.0 '/opt/IBM/WebSphere/Dmgr/../../properties /version/WAS.product'.exists()=false
2006-11-08 10:50:37,422 DEBUG [WebsphereDetector] WebSphere Admin 6.0 '/opt/IBM/WebSphere/AppSrv/../../properti es/version/WAS.product'.exists()=false
2006-11-08 10:50:37,422 DEBUG [AutoScan] Running AutoServerDetector for: WebSphere Admin 6.1
2006-11-08 10:50:37,422 DEBUG [WebsphereDetector] WebSphere Admin 6.1 '/opt/IBM/WebSphere/AppSrv/../../properti es/version/WAS.product'.exists()=false
2006-11-08 10:50:37,422 DEBUG [WebsphereDetector] WebSphere Admin 6.1 '/opt/IBM/WebSphere/Dmgr/../../properties /version/WAS.product'.exists()=false
2006-11-08 10:50:37,422 DEBUG [WebsphereDetector] WebSphere Admin 6.1 '/opt/IBM/WebSphere/AppSrv/../../properti es/version/WAS.product'.exists()=false

ebailey · ‎11-08-2006

I forgot to add this -

The install root is /opt/IBM/WebSphere/AppServer

[ebailey@****** version]$ cat wasproduct.component
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE component PUBLIC "componentId" "component.dtd">
<component build-date="6/7/06" build-version="cf110623.10" name="wasproduct" spec-version="6.0.0.0"/>

dougm_hyperic · ‎11-09-2006

I see, so the deployment manager (Dmgr) and node (AppSrv) are
deployed under /opt/IBM/WebSphere rather than /opt/IBM/WebSphere/
AppServer?

The symlink option may work, looks the plugin would just need to find:
/opt/IBM/WebSphere/properties/version/WAS.product

Assuming in your environment that file lives at:
/opt/IBM/WebSphere/AppServer/properties/version/WAS.product?

On Nov 8, 2006, at 12:40 PM, Ed Bailey wrote:

> Sorry it took so long to get back to you - I can now see the issue.
> A corporate guy did the install and nothing is where it should be.
> Anyway to work around this? Would using symlinks work?
>
> Thanks
>
> Ed
>
> Agent logs are below -
>
> 2006-11-08 10:50:37,420 DEBUG [AutoScan] Running AutoServerDetector
> for: WebSphere Admin 5.0
> 2006-11-08 10:50:37,421 DEBUG [WebsphereDetector] WebSphere Admin
> 5.0 '/opt/IBM/WebSphere/AppSrv/lib/jmxc.jar'.
> exists()=false
> 2006-11-08 10:50:37,421 DEBUG [WebsphereDetector] WebSphere Admin
> 5.0 '/opt/IBM/WebSphere/Dmgr/lib/jmxc.jar'.ex
> ists()=false
> 2006-11-08 10:50:37,422 DEBUG [WebsphereDetector] WebSphere Admin
> 5.0 '/opt/IBM/WebSphere/AppSrv/lib/jmxc.jar'.
> exists()=false
> 2006-11-08 10:50:37,422 DEBUG [AutoScan] Running AutoServerDetector
> for: WebSphere Admin 6.0
> 2006-11-08 10:50:37,422 DEBUG [WebsphereDetector] WebSphere Admin
> 6.0 '/opt/IBM/WebSphere/AppSrv/../../properti
> es/version/WAS.product'.exists()=false
> 2006-11-08 10:50:37,422 DEBUG [WebsphereDetector] WebSphere Admin
> 6.0 '/opt/IBM/WebSphere/Dmgr/../../properties /
> version/WAS.product'.exists()=false
> 2006-11-08 10:50:37,422 DEBUG [WebsphereDetector] WebSphere Admin
> 6.0 '/opt/IBM/WebSphere/AppSrv/../../properti
> es/version/WAS.product'.exists()=false
> 2006-11-08 10:50:37,422 DEBUG [AutoScan] Running AutoServerDetector
> for: WebSphere Admin 6.1
> 2006-11-08 10:50:37,422 DEBUG [WebsphereDetector] WebSphere Admin
> 6.1 '/opt/IBM/WebSphere/AppSrv/../../properti
> es/version/WAS.product'.exists()=false
> 2006-11-08 10:50:37,422 DEBUG [WebsphereDetector] WebSphere Admin
> 6.1 '/opt/IBM/WebSphere/Dmgr/../../properties /
> version/WAS.product'.exists()=false
> 2006-11-08 10:50:37,422 DEBUG [WebsphereDetector] WebSphere Admin
> 6.1 '/opt/IBM/WebSphere/AppSrv/../../properti
> es/version/WAS.product'.exists()=false

dougm_hyperic · ‎11-09-2006

Ed, can you also post the output of the following, run from the agent
directory:

./jre/bin/java -jar pdk/lib/sigar.jar pargs
State.Name.eq=java,Args.*.eq=com.ibm.ws.bootstrap.WSLauncher

sharan_hyperic · ‎11-10-2006

any one reply me for websphere app server 6

ebailey · ‎11-10-2006

Hello

Below is the requested output. I was able to get things moving forward a little bit by using symlinks to put the lib directory and WAS.product file in the right path. Now I can see a websphere instance loaded in the Hyperic web GUI, but now I need to configure it.

I am testing hyperic on one of our dev websphere boxes so securituy is not enabled so I should be able to login with no user name and password. Also, global security is not enabled. I am not real sure what the server is using for its soap port. The WAS console says it is 8881 but I know the default port is 8880 and I have seen some docs that suggest ports 8878 and 8879. So I tried them all and I get the following error

"The configuration has not been set for this resource due to : Invalid configuration: Error contacting resource: ADMC0016E: The system cannot create a SOAP connector to connect to host tucwad151.vsi.com at port 8881."

I was able to find error ADMC0016E in the IBM website and it seems their is an issue with the ssl cert? Does this error make sense?

Any ideas?

Thanks for much for everyones help.

Ed

This is the requested info

pid=17399
exe=/opt/IBM/WebSphere/AppServer/java/jre/bin/java
cwd=/opt/IBM/WebSphere/AppSrv
0=>/opt/IBM/WebSphere/AppServer/java/bin/java<=
1=>-Xbootclasspath/p:/opt/IBM/WebSphere/AppServer/java/jre/lib/ext/ibmorb.jar:/opt/IBM/WebSphere/AppServer/java/jre/lib/ext/ibmext.jar<=
2=>-Dwas.status.socket=45657<=
3=>-classpath<=
4=>/opt/IBM/WebSphere/AppSrv/properties:/opt/IBM/WebSphere/AppServer/properties:/opt/IBM/WebSphere/AppServer/lib/bootstrap.jar:/opt/IBM/WebSphere/AppServer/lib/j2ee.jar:/opt/IBM/WebSphere/AppServer/lib/lmproxy.jar:/opt/IBM/WebSphere/AppServer/lib/urlprotocols.jar<=
5=>-Xms50m<=
6=>-Xmx256m<=
7=>-Dws.ext.dirs=/opt/IBM/WebSphere/AppServer/java/lib:/opt/IBM/WebSphere/AppSrv/classes:/opt/IBM/WebSphere/AppServer/classes:/opt/IBM/WebSphere/AppServer/lib:/opt/IBM/WebSphere/AppServer/installedChannels:/opt/IBM/WebSphere/AppServer/lib/ext:/opt/IBM/WebSphere/AppServer/web/help:/opt/IBM/WebSphere/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime<=
8=>-Dderby.system.home=/opt/IBM/WebSphere/AppServer/derby<=
9=>-Dcom.ibm.itp.location=/opt/IBM/WebSphere/AppServer/bin<=
10=>-Djava.util.logging.configureByServer=true<=
11=>-Dibm.websphere.preload.classes=true<=
12=>-Duser.install.root=/opt/IBM/WebSphere/AppSrv<=
13=>-Dwas.install.root=/opt/IBM/WebSphere/AppServer<=
14=>-Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager<=
15=>-Ddb2j.system.home=/opt/IBM/WebSphere/AppServer/cloudscape<=
16=>-Dserver.root=/opt/IBM/WebSphere/AppSrv<=
17=>-Djava.awt.headless=true<=
18=>-Djava.security.auth.login.config=/opt/IBM/WebSphere/AppSrv/properties/wsjaas.conf<=
19=>-Djava.security.policy=/opt/IBM/WebSphere/AppSrv/properties/server.policy<=
20=>com.ibm.ws.bootstrap.WSLauncher<=
21=>com.ibm.ws.runtime.WsServer<=
22=>/opt/IBM/WebSphere/AppSrv/config<=
23=>tucwad151Cell<=
24=>tucwad151Node<=
25=>nodeagent<=
26=><=

------------------------

pid=17735
exe=/opt/IBM/WebSphere/AppServer/java/jre/bin/java
cwd=/opt/IBM/WebSphere/Dmgr
0=>/opt/IBM/WebSphere/AppServer/java/bin/java<=
1=>-Xbootclasspath/p:/opt/IBM/WebSphere/AppServer/java/jre/lib/ext/ibmorb.jar:/opt/IBM/WebSphere/AppServer/java/jre/lib/ext/ibmext.jar<=
2=>-Dwas.status.socket=45676<=
3=>-classpath<=
4=>/opt/IBM/WebSphere/Dmgr/properties:/opt/IBM/WebSphere/AppServer/properties:/opt/IBM/WebSphere/AppServer/lib/bootstrap.jar:/opt/IBM/WebSphere/AppServer/lib/j2ee.jar:/opt/IBM/WebSphere/AppServer/lib/lmproxy.jar:/opt/IBM/WebSphere/AppServer/lib/urlprotocols.jar<=
5=>-Xms50m<=
6=>-Xmx256m<=
7=>-Dws.ext.dirs=/opt/IBM/WebSphere/AppServer/java/lib:/opt/IBM/WebSphere/Dmgr/classes:/opt/IBM/WebSphere/AppServer/classes:/opt/IBM/WebSphere/AppServer/lib:/opt/IBM/WebSphere/AppServer/installedChannels:/opt/IBM/WebSphere/AppServer/lib/ext:/opt/IBM/WebSphere/AppServer/web/help:/opt/IBM/WebSphere/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime<=
8=>-Dderby.system.home=/opt/IBM/WebSphere/AppServer/derby<=
9=>-Dcom.ibm.itp.location=/opt/IBM/WebSphere/AppServer/bin<=
10=>-Djava.util.logging.configureByServer=true<=
11=>-Dibm.websphere.preload.classes=true<=
12=>-Duser.install.root=/opt/IBM/WebSphere/Dmgr<=
13=>-Dwas.install.root=/opt/IBM/WebSphere/AppServer<=
14=>-Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager<=
15=>-Ddb2j.system.home=/opt/IBM/WebSphere/AppServer/cloudscape<=
16=>-Dserver.root=/opt/IBM/WebSphere/Dmgr<=
17=>-Djava.awt.headless=true<=
18=>-Djava.security.auth.login.config=/opt/IBM/WebSphere/Dmgr/properties/wsjaas.conf<=
19=>-Djava.security.policy=/opt/IBM/WebSphere/Dmgr/properties/server.policy<=
20=>com.ibm.ws.bootstrap.WSLauncher<=
21=>com.ibm.ws.runtime.WsServer<=
22=>/opt/IBM/WebSphere/Dmgr/config<=
23=>tucwad151Cell<=
24=>tucwad151CellManager<=
25=>dmgr<=

------------------------

pid=10717
exe=/opt/IBM/WebSphere/AppServer/java/jre/bin/java
cwd=/opt/IBM/WebSphere/AppSrv
0=>/opt/IBM/WebSphere/AppServer/java/bin/java<=
1=>-Xbootclasspath/p:/opt/IBM/WebSphere/AppServer/java/jre/lib/ext/ibmorb.jar:/opt/IBM/WebSphere/AppServer/java/jre/lib/ext/ibmext.jar<=
2=>-Dwas.status.socket=39348<=
3=>-classpath<=
4=>/opt/IBM/WebSphere/AppSrv/properties:/opt/IBM/WebSphere/AppServer/properties:/opt/IBM/WebSphere/AppServer/lib/bootstrap.jar:/opt/IBM/WebSphere/AppServer/lib/j2ee.jar:/opt/IBM/WebSphere/AppServer/lib/lmproxy.jar:/opt/IBM/WebSphere/AppServer/lib/urlprotocols.jar<=
5=>-Xms50m<=
6=>-Xmx512m<=
7=>-Dws.ext.dirs=/opt/IBM/WebSphere/AppServer/java/lib:/opt/IBM/WebSphere/AppSrv/classes:/opt/IBM/WebSphere/AppServer/classes:/opt/IBM/WebSphere/AppServer/lib:/opt/IBM/WebSphere/AppServer/installedChannels:/opt/IBM/WebSphere/AppServer/lib/ext:/opt/IBM/WebSphere/AppServer/web/help:/opt/IBM/WebSphere/AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime<=
8=>-Dderby.system.home=/opt/IBM/WebSphere/AppServer/derby<=
9=>-Dcom.ibm.itp.location=/opt/IBM/WebSphere/AppServer/bin<=
10=>-Djava.util.logging.configureByServer=true<=
11=>-Dibm.websphere.preload.classes=true<=
12=>-Duser.install.root=/opt/IBM/WebSphere/AppSrv<=
13=>-Dwas.install.root=/opt/IBM/WebSphere/AppServer<=
14=>-Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager<=
15=>-Ddb2j.system.home=/opt/IBM/WebSphere/AppServer/cloudscape<=
16=>-Dserver.root=/opt/IBM/WebSphere/AppSrv<=
17=>-Djava.security.auth.login.config=/opt/IBM/WebSphere/AppSrv/properties/wsjaas.conf<=
18=>-Djava.security.policy=/opt/IBM/WebSphere/AppSrv/properties/server.policy<=
19=>com.ibm.ws.bootstrap.WSLauncher<=
20=>com.ibm.ws.runtime.WsServer<=
21=>/opt/IBM/WebSphere/AppSrv/config<=
22=>tucwad151Cell<=
23=>tucwad151Node<=
24=>logic<=

------------------------

Message was edited by: ebailey

dougm_hyperic · ‎11-10-2006

Good to hear you got a bit further Ed. Thanks for the sigar output,
looks like we can enhance the plugin to use some of the command line
properties to auto-discover this setup without having to setup the
symlinks.
You can check the agent's log/agent.log for more details on the
error. This error can happen if there's something listening on the
port, but it isn't the soap connector. You can also verify the port
the checking serverindex.xml for SOAP_CONNECTOR_PORT, for example in
one of our 6.0 setups:

profiles/default/config/cells/demoNode01Cell/nodes/demoNode01/
serverindex.xml:

<specialEndpoints xmi:id="NamedEndPoint_1138921219768"
endPointName="SOAP_CONNECTOR_ADDRESS">
<endPoint xmi:id="EndPoint_1138921219768"
host="demo.intranet.hyperic.net" port="8880"/>
</specialEndpoints>

You'll want to use the deployment manager's port, which I believe in
your environment would be listed in this file:
/opt/IBM/WebSphere/Dmgr/config/cells/tucwad151Cell/nodes/
tucwad151CellManager/serverindex.xml

On Nov 10, 2006, at 6:37 AM, Ed Bailey wrote:

> Hello
>
> Below is the requested output. I was able to get things moving
> forward a little bit by using symlinks to put the lib directory and
> WAS.product file in the right path. Now I can see a websphere
> instance loaded in the Hyperic web GUI, but now I need to configure
> it.
>
> I am testing hyperic on one of our dev websphere boxes so securituy
> is not enabled so I should be able to login with no user name and
> password. Also, global security is not enabled. I am not real sure
> what the server is using for its soap port. The WAS console says it
> is 8881 but I know the default port is 8880 and I have seen some
> docs that suggest ports 8878 and 8879. So I tried them all and I
> get the following error
>
> "The configuration has not been set for this resource due to :
> Invalid configuration: Error contacting resource: ADMC0016E: The
> system cannot create a SOAP connector to connect to host
> tucwad151.vsi.com at port 8881."
>
> I was able to find error ADMC0016E in the IBM website and it seems
> their is an issue with the ssl cert? Does this error make sense?
>
> Any ideas?
>
> Thanks for much for everyones help.
>
> Ed

ebailey · ‎11-15-2006

Hi,

I am not having much luck using other ports. I get the following with every port I use -

2006-11-15 14:35:53,646 ERROR [org.hyperic.hq.ui.action.resource.common.inventory.EditConfigPropertiesAction] invalid config org.hyperic.hq.appdef.shared.InvalidConfigException: Invalid configuration: Error contacting resource: ADMC0016E: The system cannot create a SOAP connector to connect to host localhost at port 8880.
[1]-NESTED-EXCEPTION:
org.hyperic.hq.measurement.monitor.LiveMeasurementException: Error contacting resource: ADMC0016E: The system cannot create a SOAP connector to connect to host localhost at port 8880.
2006-11-15 14:21:31,394 ERROR [org.hyperic.hq.ui.action.resource.common.inventory.EditConfigPropertiesAction] invalid config org.hyperic.hq.appdef.shared.InvalidConfigException: Invalid configuration: Error contacting resource: ADMC0016E: The system cannot create a SOAP connector to connect to host localhost at port 8879.
[1]-NESTED-EXCEPTION:
org.hyperic.hq.measurement.monitor.LiveMeasurementException: Error contacting resource: ADMC0016E: The system cannot create a SOAP connector to connect to host localhost at port 8879.

I went to /opt/IBM/WebSphere/Dmgr/config/cells/tucwad151Cell/nodes/tucwad151CellManager

and did not see a port labeled deployment manager

I did see the following

serverindex.xmi" xmlns:appdeployment="http://www.ibm.com/websphere/appserver/schemas/5.0/appdeployment.xmi" xmlns:ipc="http://www.ib
m.com/websphere/appserver/schemas/5.0/ipc.xmi">
<xmi:Documentation>
<contact>WebSphere Application Server v5.0 Default Configuration Files v1.25.1.7 9/13/04</contact>
</xmi:Documentation>
<serverindex:ServerIndex xmi:id="ServerIndex_1" endPointRefs="NamedEndPoint_1 NamedEndPoint_2" hostName="tucwad151">
<serverEntries xmi:id="ServerEntry_1" serverDisplayName="dmgr" serverName="dmgr" serverType="DEPLOYMENT_MANAGER">
<specialEndpoints xmi:id="NamedEndPoint_1" endPointName="CELL_DISCOVERY_ADDRESS">
<endPoint xmi:id="EndPoint_1" host="tucwad151" port="7277"/>
</specialEndpoints>
<specialEndpoints xmi:id="NamedEndPoint_2" endPointName="BOOTSTRAP_ADDRESS">
<endPoint xmi:id="EndPoint_2" host="tucwad151" port="9809"/>
</specialEndpoints>
<specialEndpoints xmi:id="NamedEndPoint_4" endPointName="SOAP_CONNECTOR_ADDRESS">
<endPoint xmi:id="EndPoint_4" host="tucwad151" port="8879"/>
</specialEndpoints>
<specialEndpoints xmi:id="NamedEndPoint_5" endPointName="ORB_LISTENER_ADDRESS">
<endPoint xmi:id="EndPoint_5" host="tucwad151" port="9101"/>
</specialEndpoints>
<specialEndpoints xmi:id="NamedEndPoint_6" endPointName="SAS_SSL_SERVERAUTH_LISTENER_ADDRESS">
<endPoint xmi:id="EndPoint_6" host="tucwad151" port="9404"/>
</specialEndpoints>
<specialEndpoints xmi:id="NamedEndPoint_7" endPointName="CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS">
<endPoint xmi:id="EndPoint_7" host="tucwad151" port="9405"/>
</specialEndpoints>
<specialEndpoints xmi:id="NamedEndPoint_8" endPointName="CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS">
<endPoint xmi:id="EndPoint_8" host="tucwad151" port="9406"/>
</specialEndpoints>
<specialEndpoints xmi:id="NamedEndPoint_9" endPointName="WC_adminhost">
<endPoint xmi:id="EndPoint_9" host="*" port="9060"/>
</specialEndpoints>
<specialEndpoints xmi:id="NamedEndPoint_10" endPointName="DCS_UNICAST_ADDRESS">
<endPoint xmi:id="EndPoint_10" host="tucwad151" port="9352"/>
</specialEndpoints>
<specialEndpoints xmi:id="NamedEndPoint_11" endPointName="WC_adminhost_secure">
<endPoint xmi:id="EndPoint_11" host="*" port="9043"/>
</specialEndpoints>
</serverEntries>
</serverindex:ServerIndex>
</xmi:XMI>

I tried all of the ports and had the same error.

Any ideas?

Thanks

Ed

JoeHayes · ‎02-20-2007

The port you want is 8879, the SOAP connection port.

All

websphere discovery help