Could you please tell me the Difference between Tibco MQ series Adapter and Tibco BW MQ plugin.
Is there any advantages of using MQ adapters over MQ plugins.
Primary difference being the ease of use and deployment. Tibco MQ series Adapter works by using the MQ binding file and also it is invoked inside BW by using the adapter palette activities. MQ adapters are deployed as a separate entity as aar.
Where as ActiveMatrix MQ plugins enables developers to directly interact with MQ destinations and there is no additional deployment of adapter service required.
Related
Can Solace integrate with IBM Websphere Application Server 8.5.5.0? We are thinking to eliminate the existing IBM MQ7.0 from our IBM WAS 8.5.5.0 integration components.
I have found one article/document on the Solace portal for IBM WAS 7/8.0, but not for 8.5.5.0? But we need to know the capability of Solace and whether it will integrate with IBM WAS 8.5.5.0 or not?
Solace can absolutely integrate with IBM Websphere Application Server 8.5.5.0. The current Websphere Integration Guide that is available on the Solace dev portal is applicable to Websphere Application Servers 7.x and 8.x. It is available here: http://dev.solace.com/integration-guides/websphere-application-server/
The Solace JMS Resource Adapter is designed to be generic. It is generally able to integrate with any Jave EE Application Server.
If you have a support contract with Solace and you encounter any specific issues integrating Solace with any version of the IBM Websphere Application Server, you can contact support by emailing support#solace.com with a description of your issue.
In our project we have websphere liberty server and IBM MQ as message server. We are moving in cloud. We want to replace IBM MQ with AWS SQS. In server.xml we have following entries to get IBM MQ connection factory using jndi.
<jmsQueueConnectionFactory connectionManagerRef="ABCConnMgr" jndiName="jms/ABC_QCF">
<properties.wmqJms channel="CH.ABC.SVRCONN" hostName="abc-mq1-st4.ebiz.abc.com" port="21414" queueManager="ABC401" transportType="CLIENT"/>
</jmsQueueConnectionFactory>
<connectionManager agedTimeout="-1s" connectionTimeout="180s" id="ABCConnMgr" maxIdleTime="1800s" maxPoolSize="50" minPoolSize="0" purgePolicy="EntirePool" purgeagedTimeout="-1s" reapTime="180s"/>
<jmsQueue id="ABC.ORDERMGT.INPUT.QA" jndiName="jms/ABC_ORDERMGT_INPUT">
<properties.wmqJms baseQueueName="ABC.ORDERMGT.INPUT.QA"/>
</jmsQueue>
Similarly I am looking jndi configuration for Amazon SQS connection factory and sqs queue. I think IBM need to develop resource adapter for SQS and provide this configuration.
You are correct, you will need a resource adapter for Amazon SQS. It could be provided by any third-party vendor, does not need to be IBM for it to work because JCA is a standard.
Once you have a resource adapter, here are some helpful Knowledge Center links to get it configured in Liberty,
Overview of JCA/JMS config
Configuring Resource Adapters
Configuring JMS Connection Factories
Configuring JMS Destinations
I am new to powershell. I need to connect to IBM WebSphere MQ Explorer via powershell script. I have already installed IBM library to support MQ Explorer connection. But I am not getting any connection commands to connect to the QueManagers in MQ Explorer. Please guide me.
I need to push a message to MQ from ruby code. The only gem I see is WMQ and I don't think that works on OSX systems (mine is a remote MQ)
What are options I have? I can't find any details on this online
It would be far easier to use Java on Mac OS X rather than Ruby. But if you want to stick with Ruby then your only option is to use MQ Light to communicate with an MQ Server via AMQP protocol.
Note: AMQP protocol was introduced in MQ v8.0.0.4.
I am working with WebSphere MQ FTE. While reading a document I came across a sentence that the bridge agent connects to local queue manager through binding mode. What is meant by binding mode in WebSphere MQ?
WebSphere MQ was originally created to be a local communication stack that resided on the same server as the applications that used it. In this mode, applications talk to it using Inter Process Communication (IPC). This is where two processes on the same server intercommunicate using shared memory, semaphores and other local communication.
Eventually the MQ client was created and allowed applications to communicate with WebSphere MQ over the network. This meant that there were now two modes of communication with the queue manager. The term Client Mode naturally arose to refer to communications using the MQ client. The term Bindings Mode arose to differentiate client mode from native WMQ IPC connections.
So when you read that an FTE agent uses bindings mode connections, that means that it runs on the same server as a queue manager and that it communicates with the queue manager using shared memory instead of over the network.
Note that with WebSphere MQ File Transfer Edition the licensing refers to "Client" and "Server" bundles of the products. The Client package is the FTE agents without a copy of WebSphere MQ Server included. The Server package is the same FTE components bundled with a copy of WebSphere MQ Server and with the ability to connect in bindings mode.