Tibco Ems Windows

0726

'
Hi,

We have a portal application which send messages to the TIBCO queue whenever the user browses the portal website. To send message to the TIBCO queue we are using javax.jms api and some thread mechanism. We have 10 machines in production and this works fine only in few machines and in other machines we are getting the following error message.(Note: All the machines are connected to the same TIBCO EMS server and queue )

The TIBCO EMS plug-in is included in TIBCO Administrator installation. Once the TIBCO EMS plug-in is installed, it can be accessed from TIBCO Administrator GUI by clicking Application Management > All Services Instances > machine-name – EMS port. Users and groups defined for the TIBCO EMS Server can be synchronized.

SystemErr R javax.jms.JMSException: Failed to connect to the server at tcp://zzzzzz:12523
at com.tibco.tibjms.TibjmsxLinkTcp._createSocket(TibjmsxLinkTcp.java:791)
at com.tibco.tibjms.TibjmsxLinkTcp.connect(TibjmsxLinkTcp.java:886)
at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:671)
at com.tibco.tibjms.TibjmsConnection. (TibjmsConnection.java:1932)
at com.tibco.tibjms.TibjmsQueueConnection.

(TibjmsQueueConnection.java:37)
at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:148)
at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:201)
at com.tibco.tibjms.TibjmsQueueConnectionFactory.createQueueConnection(TibjmsQueueConnectionFactory.java:79)

I would appreciate if anyone can help me to resolve this.

Regards, Tibco Ems Windows
Subbu'

Tibco Ems Client Download Windows

I have two different applications that need to share data between them. By data, I mean only some pieces of data and not the entire data across the systems.

The databases of the applications are owned by us but the applications are third party.

The two applications use database as an integration mechanism where they have a transaction table into which the data to be integrated is written to. A third party application then picks the data from there.

We are evaluating how to utilize TIBCO for performing the integration - (Trying to go away from the third party integration pieces). Such that, we expect Tibco to pick the data from the transaction table, apply any business logic and sync up the other systems as result of the integration.

I have in the past wrote a windows service that polls a similar transaction table and write (the data to be synced/integrated) to the TIBCO queue and have the windows service read from the queue, apply the business logic and do the integration or data sync in the other system's database.

I was using TIBCO EMS module to work with the message queues. But if there are other options within and outside of TIBCO, please provide some pointers.

We are particular on TIBCO because the org moves in a direction to make TIBCO a standard means of integration between systems.

TIA

windows-servicestibcotibco-emstibco-business-workssystem-integration
user6520593user6520593

2 Answers

TIBCO BusinessWorks Product is the right option for you here in this where it allows you to connect to the database / ems, I believe. This allows to integrate systems and define your process and orchestrate the logic you might wanted to do.

It has the connection palette to connect to database, fetches the required data using query and allows to process that data for further processing.

Ems

May be you can find more details in documentation

RaoRao

In addition to Tibco Businessworks, TIBCO ADB adapter can also be used which plugs into database tables and picks up new changes and publish to Queue, then have Businessworks process to perform the logic and then update to a target application data base. The database adapters from Tibco are suited well for high volume data integration otherwise you can achieve the same using Businessworks

ImrankhanImrankhan

Not the answer you're looking for? Browse other questions tagged windows-servicestibcotibco-emstibco-business-workssystem-integration or ask your own question.

This entry was posted on 26.07.2019.