cancel
Showing results for 
Search instead for 
Did you mean: 

How to connect SAP XI engine with TIBCO EMS

Former Member
0 Kudos

Hi,

how can I connect SAP XI 3.0 with TIBCO EMS?

If i'm going to use XI provider, Do I need to deply any jar files into XI?

Thanks in advance.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

but Tibco administrator has especified that they are using TIBCO with no JNDI ¿

Former Member
0 Kudos

Hi,

Any particular reason why he doesn't want to use this?...its normally availabe per Default in TIBCO EMS.

I saw you want to use https, are you shure that connection is working? As far as i know EMS uses ssl as secure transport mechanism, so the url should be ssl://host:port

Also you should have added the "tibcrypt.jar" to your deployed libraries for JMS Adapter

With best regards

Sebastian

Edited by: Sebastian Simon on Sep 9, 2010 11:36 AM

Former Member
0 Kudos

Hi Sebastian,

I don't know why thw client doesn't want to use TIBCO.

These are the jar I've deployed:

jms.jar

tibcrypt.jar

tbemsd_sec.jar

tibjmaapps.jar

tibjms.jar

tibjmsadmin.jar

tibjmsufo.jar

tibrvjms.jar

slf4j-api-1.4.2.jar

slf4j-simple-1.4.2.jar

and yes, we are usings SSL://host:port and the error persist.

BR,

Former Member
0 Kudos

Hello Loupor,

Did you take a look into your default Trace (NWA), i guess there' ll be more details about the error,

sounds like something can't start.

About the jars, the jms jar doesn't need to be packaged along,as the jms api is already present in the JMS Adapter,

Try to remove it.

Best wishes

Sebastian

Former Member
0 Kudos

Hello,

We have already deployed the new libraries (.jar). They were deployed successfully.

So now, we set up JMS Adapter again and the following error is displayed:

Error establishing JMS connection; error message: Failed to connect to the server at tcp://localhost:7222 Connection refused (error:239);error code: null

What does it mean 'localhost' in this case? Xi Server or Tibco EMS Server? Tibco server isn't localhost.

What could be the reason for this error???

If I am not using the string 'localhost:7222' in any parameter of the configuration, where does the adapter take this value from????

Have I to define another parameter in the JMS adapter?

Is this string hardcode in any .class?

Thanks.

Former Member
0 Kudos

Hi Loupor,

Your Adapter obviously uses the default host/port of an EMS installation.

Consult your TIBCO Admins about documentation how to set the parameters.

Additionally read this SAP note to the exact topic (XI JMS Adapter and TIBCO EMS Faq) :

https://service.sap.com/sap/support/notes/1099720

There's a chapter about generic configuration options:

Name : JMS.QueueConnectionFactoryImpl.classname

Value: com.tibco.tibjms.TibjmsQueueConnectionFactory

Name : JMS.QueueConnectionFactoryImpl.constructor

Value: java.lang.String localhost:7222 -


> here: your host + port!

Name : JMS.QueueImpl.classname

Value: com.tibco.tibjms.TibjmsQueue

Name : JMS.QueueImpl.constructor

Value: java.lang.String YourQueueName

With best regards

Sebastian

Former Member
0 Kudos

This message was moderated.

Former Member
0 Kudos

HI,

At this moment I've deployed the TIBCO libraries into my XI and I've created an XI adapter in order to connect with TIBCO system as folows:

Transport protocol Access JMS Provider Generically

JMS.queue ConnectionFactoryImpl.classname com.tibco.tibjms.tibjmsQueueConnectionFactory

JMS.QueueConnectionFactoryImpl.constructor java.lang.String https://hostname:port

JMS.QueueImpl.classname com.tibco.tibjms.tibjmsQueue

JMS.QueueImpl.constructor java.lang.string TibcoQueueName

SecuritySSLOn True

SecurityKeyName Name

JMS Settings

JMS Queue User User

JMS Queue Password UserPassword

I don't know where is the problem, but all the times I've obtained the same error:

MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: STARTING, on event: process_commence for DFA: JMS_TIBCO_ADAPTER

Thanks in advance.

Former Member
0 Kudos

Hello loupor,

I would prefer to EMS with the JNDI option instead of general JMS Provider (as described in the note).

I build many integrations to EMS and it works perfectly (even with the EMS advanced Failover balancing options using more then one host name).

Choose Transport protocol "Acces JMS Provider with JNDI" and configure the channel as described in the note

in chapter "JMS channel connection parameter configuration to connect to TIBCO EMS using the JNDI mode"

With best regards

Sebastian

henrique_pinto
Active Contributor
0 Kudos

EMS is a "custom" type of JMS.

You can basically use JMS adapter with some little tweaks.

Check this note: https://service.sap.com/sap/support/notes/1099720

BR,

Henrique.