I have a need to connect with IBM WAS JMX using SOAP protocol specifically, locally as well as remotely. I am looking for ways to get JMX data of IBM WAS with SOAP protocol on jconsole.
Tried with URL like service:jmx:soap://<host>:<port>/jndi/JMXConnector but it did not. What configuration needs to be done on IBM WAS side so as to connect with JConsole using SOAP protocol?
Even referred IBM WAS docs but could not find anything relevant - https://www.ibm.com/support/knowledgecenter/SSEQTP_8.5.5/com.ibm.websphere.base.doc/ae/ragt_rconnector_customp.html
Here are the few references that I referred for connecting IBMWAS JMX with JConsole using SOAP Protocol:
https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/cjmx_overview.html
https://www.ibm.com/support/knowledgecenter/SSEQTP_9.0.5/com.ibm.websphere.base.doc/ae/container_admservice_tasks.html
https://www.ibm.com/support/knowledgecenter/SSEQTP_9.0.5/com.ibm.websphere.base.doc/ae/uagt_rconnector.html
https://www.ibm.com/support/knowledgecenter/SSEQTP_9.0.5/com.ibm.websphere.base.doc/ae/ragt_rconnector_customp.html
After doing the necessary configuration on IBM WAS server side as recommended there and also listing down here :
Server side Conf. steps, from UI :
Security -> Global Security -> RMI/IIOP security -> CSIV2 inbound communication -> Under Csiv2 transport layer
Change transport from SSL-supported to SSL-required.
Security -> Global Security -> RMI/IIOP security -> CSIV2 outbound communication -> Under Csiv2 transport layer
Change transport from SSL-supported to SSL-required.
Set Servers >> ServerTypes >> Application servers >> server1 >> Administration services >> Configuration : Set Remote Connector & Local Connector as SOAP Connector under General Properties
Set Servers >> ServerTypes >> Application servers >> server1 >> Administration services >> JMX Connectors : Set SOAPConnector Enabled = Yes
Set Servers >> ServerTypes >> Application servers > server1 > Ports > SOAP_CONNECTOR_ADDRESS : Set Host = * under General Settings
Application servers > server1 > Ports > BOOTSTRAP_ADDRESS : Set Host = * under General Settings
Restart IBM server
Getting following error while trying to connect -
REST Error [400]: Bad Request -- Invalid parameter found in connection URL. Verify the provided connection configurations.
Related
I was getting this error below:
"Connecting to remote server TESTSERVER01 failed with the following error message : The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM."
I've following the hundreds of fixes online for this. Nothing works, ideas?
The fix which worked on all my Windows 2012 servers was....
Enabled Powershell Remoting.
Enabled Credentials Negotiating on both servers.
Set trusted hosts to *.mydomain.
Crucial: GPEDIT.MSC -> Computer Configuration -> Administrative Templates -> Windows Components -> Windows Remote Management -> WinRM Service. Key = Allow remote server management through WinRm be set to '*' not empty!
I'm new to Websphere and trying to create a cluster Websphere 8.5 with IBM Http Server as the webserver. My topology is different from all the examples provided by IBM :
I have 2 physical machines : machine A and machine B.
On machine A : deployment manager + app server A + HTTP Server + HTTP administration server + webserver plugin
On machine B : app server B + webserver plugin
I have a cluster who contains appsv A and appsv B, and now I want to create a webserver on machine Afor the cluster.
I've used the "Webserver Configuration Tool" to create a remote webserver : websv for machine B. But I don't know how to do with app server A...
Am I doing wrong? Should I configure the plug-in separately on the machines but giving the same name for the webserver so that I can migrate the cfg files to one then put it on machine A?
How should I do with the "configwebsv.bat"?
Thanks a lot for your responses.
Allen
There's no reason to do anything with a webserver or webserver plug-in on machine B. The dmgr is aware of any clusters you have and allows you to map them to your webserver no matter where it lives.
I have verified that it is possible to connect to a jboss node through jmx in jvisualvm using remote connection with a portnumber and user name and password. However wanting to add this jboss node as external monitor in LR controller there is no place to add i.e. username and password when setting up a remote UNIX monitor in loadrunner. When adding a UNIX resource and external measurement all I am asked is the name of the machine to add (in the wizard).
Is it possible to add a jboss node as UNIX resource monitor in LR controller without sitescope?
JMX requires Sitecope as the monitoring foundation for LoadRunner. Or, you can find some sort of JMX to SNMP bridge and then use the native SNMP monitor in LoadRunner. Howeverm, even then the SNMP monitor in SiteScope is more mature.
I have a swing client which connects to my ejb2 application deployed in JBoss 5.1. There is a particular requirement from Customer to make it available on internet.
The deployment architecture is as follows,
swing_client --> extranet_ip |firewall | --> iis7_machine --> jboss5.1_machine.
jndi properties in client is as follows
Context.PROVIDER_URL=http://extranet_ip:9180/invoker/JNDIFactory
Context.INITIAL_CONTEXT_FACTORY=org.jboss.naming.HttpNamingContextFactory
This configuration works fine when the client is inside intranet. But it does not work in internet (extranet).
When I tried initially I got the error 'Connection refused'
After seeing some posts in various forums, I changed the file server\deploy\http-invoker.sar\META-INF\jboss-service.xml, to reflect the extranet_ip in invokerURL.
Aftet this I am getting the following error.
org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://10.200.1.193:4546/?dataType=invocation&enableTcpNoDelay=true&marshaller=org.jboss.invocation.unified.marshall.InvocationMarshaller&unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshaller]
Where 10.200.1.193 is the intranet IP address of JBoss Server machine.
I tried changing the trasport parameter in remoting-jboss-beans.xml to http, but at that time client is not working in both intranet and extranet.
Please anybody suggest a way forward for this issue. Or is there any other way to implement RMI over Http in JBoss?
Update: As a solution, I had to change my deployment architecture as follows.
swing_client --> extranet_ip |firewall | --> jboss5.1_machine
where the JBoss Application Server will be directly exposed through firewall. Then update clientConnectAddress in the remoting-jboss-beans.xml to the extranet IP. Also open the ports 8080 & 4446 in the firewall for this address.
This way the swing client is working if I use the jnid properties as follows.
Context.PROVIDER_URL : http://extranet_ip:8080/invoker/JNDIFactory
Context.INITIAL_CONTEXT_FACTORY : org.jboss.naming.HttpNamingContextFactory
But still looking for a solution where there is no need to open any non-standard ports and no need to expose the Application Server directly.
After a long struggle I found a solution for my issue. The solution was to change EJB container's invoker type to http in standardjboss.xml. When the invoker is http, it will use the settings in http-invoker.sar for remote binding.
I try to connect to CVS through eclipse. After entering (host, repository path, user, password) and by clicking finish, it gives me the following error :
Error validating location : "Could not connect to :pserver:username#host:/CVS/Myproject:I/O exception occured: ProxyHTTP: java.IOEXCEPTION: proxy error (the specified socket layer (SSL) port is not allowed.ISA Server is not configured to allow SSL REQUEST FROM THIS PORT. most web browser use port 443for SSL request .)"
What could I do ?
If you need to access the Web via a proxy server, but use an internal CVS server that shouldn't be accessed via the proxy, you can add the CVS server to Eclipse's proxy bypass list.
To do this, go to Windows→Preferences→General→Network Connections and click 'Add Host'. You'll likely want to use wildcards to specify all internal servers, e.g. *.mycompany.com.au or 163.189.*.
Obviously a problem with your proxy server. Try disabling proxy settings in Eclipse or ask your system administrator to fix the proxy server configuration.
In my particular case, i solved this issue going to: windows -> preferences -> network connections and set Active Provider = Direct
As soon as i modified this i was able to check out the code.