• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

SSL connectivity issue with tibco

 
Vanitha Anandan
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We are trying to establish SSL connection from Application A to application server B.
Previously the connectivity was using tcp with port number 7022. We are trying to change the configuration for SSL connectivity with 9022.

The following configuration details we got from the Application B team for establishing SSL connection :

URL: ssl://hostname:9022
Connection factory: ApplicationA
JNDI Name for Request Queue : JNDI.Request
JNDI Name for Reply Queue : JNDI.Reply

The following are the Configuration details on Websphere Console
Application Servers > ApplicationA > Message Listener Service > Listener Ports > XYZ.RequestPort

Generic JMS Providers > tibcoclient
Classpath : /opt/WebSphere51/AppServer/cycle0server/tibjms.jar
/opt/WebSphere51/AppServer/cycle0server/jcert.jar
/opt/WebSphere51/AppServer/cycle0server/jnet.jar
/opt/WebSphere51/AppServer/cycle0server/jsse.jar
/opt/WebSphere51/AppServer/cycle0server/tibcrypt.jar

External Provider URL : ssl://hostname:9022

Generic JMS Destinations


Name : JNDI.Request
JNDI Name : jms/ems/XYZ.REQ
External JNDI Name : JNDI.Request

JMS Connection Factories

Name : ApplicationA
JNDI Name : ApplicationA
External JNDI Name : ApplicationA
Type : Queue

With the above configurational changes when we start the server we are facing following issue:

1. The connectivity still remains with tcp with the port 9022 instead of SSL
tcp://hostname:9022

Caused by: javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to the server at tcp://hostname:9022 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://hostname:9022]

at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:692)
at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:516)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory$1.run(IndirectJndiLookupObjectFactory.java:375)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:111)
at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstanceExt(IndirectJndiLookupObjectFactory.java:221)
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:889)
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:701)
at com.ibm.ws.naming.jndicos.CNContextImpl.cacheLookup(CNContextImpl.java:3050)

please suggest where ssl config changes we are missing

 
Vanitha Anandan
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Created jndi.properties file as a result ssl issue has gone
Now the issue is

Original exception: javax.resource.spi.ResourceAdapterInternalException: createQueueConnection failed

javax.jms.JMSSecurityException: Error occured while reading identity data: Invalid or not supported identity data
at com.tibco.tibjms.TibjmsSSL._identityFromStore(TibjmsSSL.java:2772)
at com.tibco.tibjms.TibjmsSSL.createIdentity(TibjmsSSL.java:2677)
at com.tibco.tibjms.TibjmsxLinkSSL._initSSL(TibjmsxLinkSSL.java:319)
at com.tibco.tibjms.TibjmsxLinkSSL.connect(TibjmsxLinkSSL.java:392)
at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:688)
at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:1955)

Any help?
 
Vanitha Anandan
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We have already imported tibco ems .pem file in our keystore
 
Bhagat Singh Rawat
Ranch Hand
Posts: 93
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Vanitha Anandan wrote:We have already imported tibco ems .pem file in our keystore



Hi VAnitha,

Post your problem at TIBCO Developer Forum. Might be you get the help from there.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic