JMS adapter webspehere mq, network failure - stop

Hello,
After a network failure the JMS sender adapter (JMS --> XI) goes red, and doesn't automatically recover after a network failure. It is necessary to manually stop and start the adapter. This is bad design from SAP. You would like it to behave like the ftp adapter which automatically continues to poll for files after a network outage.
What can be done to overcome this bad design?
I'm on XI SP 18.
My Idea is to use the new AAM described in
SAP Note 766332
1. com.sap.aii.af.service.administration.cpa: Channel-related interfaces and APIs
2. com.sap.aii.af.service.administration.monitoring: Monitoring interfaces and APIs
3. com.sap.aii.af.service.administration.i18n: Localization interfaces and APIs
I would like to write a standard j2se application to connect using jndi to list the status of the channels, and then stop and start depending on status.
Which jar files should be included?
Example code?

Hello,
I have now built a workaround solution based on the AAM API.
It is implemented as a J2EE stateless session bean and a J2EE client. The client reads config with information about which channels to restart and calls the bean which checks status on the channels and restarts the ones with errors or in a stopped state. We schedult the program to run every 5 minutes and check the status.
Check the channelstatus.jsp for hints on how to use the api.
It's a pity SAP hasn't got this functionality builtin, it's clearly a design error.
/Otto
Edited by: Otto Frost on Dec 18, 2007 4:32 PM

Similar Messages

MDB,MDB container or JMS adapter stops processing messages from JMS queue

Hi guys,
we have created a component using Enterprise Java Beans, let's say a product catalog, deployed it on a Glassfish v2 instance, and connected it to a legacy system using JMS and Sun MQ v4.1 as messaging system. The catalog component thus starts one MDB that listens on a JMS queue, let's say a queue named catalog_business_events_in, and waits for incoming messages, i.e. in our case update events. The problem is, that in general this approach works well, but sometimes the MDBs/JMS adapter stops for some reason fetching and processing messages from the JMS queue. We don't know why - no exceptions, etc.. Seems to be a Glassfish EJB container, JMS adapter or Sun MQ configuration issue. It seems to be that our component is not the problem.
The messages are compressed/uncompressed by Sun MQ automatically. We actually have 2 Sun MQ instances in clustered mode running to have some kind of failover - no HA cluster, yet. Sun MQ instances are accessed from Glassfish instances running in different Glassfish clusters - so we have a dedicated Sun MQ cluster not a Sun MQ instance per Glassfish instance. Each Glassfish instance is configured such that it knows both Sun MQ instances to allow automatic failover.
Has someone an idea, why the MDBs/ MDB container/ JMS adapter - stops processing messages? We are kind of puzzled as it happens more often now and apparently when traffic is (very) low not high!
Thanks for your help.
Cheers,
Martin
Edited by: east1979 on Jan 13, 2009 8:06 AM

Hi Manoj,
I have a very similar if not identical issue,
Error while running realtime jobs that read from JMS tables via JMS MQ adapter:
15/11/12 09:10:08 JMS GET OPERATION ERROR : TIMEOUT.UNABLE TO RECEIVE RESPONSE FROM THE INVOKED DATA SERVICES SERVICE.ADAPTER OPERA
TION TO CONTINUE.
15/11/12 09:10:15 Communication Error. See real time job log for details.
Dump available:
https://sapmats.wdf.sap.corp/download/download.cgi?id=5C0KZAHA3RSXBJW3ABLMUUT2P5UUKWO2TM3EJDM5W2HGDZUDID
Version of DS:14.0.3.273
Any comments?
Thansk and kind Regards,
Kenneth

PI 7.1: Weblogic (JMS adapter) - Connectivity & MONITORING!!

Hi ALL
WE have a requirement to integrate PI with Weblogic server using JMS adapter.
However, we would like to host the JMS queues in PI, so that we have end to end monitoring capability.
We do not want Weblogic Server to host these queue, instead want PI 7.1 to maintain these quese ... so that we can monitor these interfaces end -to- end.
Please, let us know if anybody has done this Weblogic integration with JMS queue monitoring within PI 7.1.
So, the main GOAL is to have JMS Queue monitoring in PI, where we have visibility to how many queues are running and the no.of messages in sent in each queue and failures if any.
Also, is there any Queue monitoring under /nwa adminstration; where we can see the queue created in PI
So, if anyone has implemented this in PI 7.1, please let us know.
Your help is greatly appreicated!!
Thank you,
Patrick.
Edited by: Patrick Jones on Sep 25, 2009 6:24 PM
Edited by: Patrick Jones on Sep 25, 2009 8:58 PM
Edited by: Patrick Jones on Sep 26, 2009 12:09 AM
Edited by: Patrick Jones on Sep 26, 2009 10:04 PM
Edited by: Patrick Jones on Sep 28, 2009 2:28 AM

Hi Patrick,
We've done something similar but with PI 7.0 & Weblogic hosting the queue so I'm not sure how useful this will be to you...
Firstly, great move to have the queue/s hosted in PI (in my opinion), for several reasons:
- You won't have to keep investigating whether or not Weblogic actually put the message on the queue/s or not.
- It makes monitoring a bit easier.
- For some reason on PI 7.0, when Weblogic or stops the queue services then PI stops polling for messages although we have green lights in RWB communication channel monitoring. If we stop & start the comm channel/s then the JMS Adapter starts picking up messages off the queue. A couple of SAP notes point to a known Weblogic issue with the way Weblogic works with initial contexts. Hosting the queues in PI would take care of this problem.
Currently we are using HermesJMS to monitor all JMS queue/s with number of messages & possible message backlog in the queues. We are also working on setting up Business Processing Monitoring that can do full end-to-end monitoring of a business process across the landscape not just in within PI. I'm also curious to see what's available in PI 7.1 for JMS queue monitoring.
Regards, Trevor

Invoking Jms Adapter from BPEL with enque stoped

Hi guys, I have an issue.
In my BPEL flowI have an invoke activity which has a jms adapter as a partner link.
The thing is that if you stop the enque in the DB, your flow in BPEL continues like nothing happened. It just passes the payload to the jms adapter. From it's point of view is asynchronous , but I want to make sure that the payload is in the queue before I continue the flow.
Any ideas?

Hi Oracler,
I don't understand what you mean by XML schema inline? Where do you define that in a JMS adapter ? Can you be more specfic when you say Try including both the elements(TEXT_LOB , TEXT_VC ) in the schema? I don't have those elements in my schema at all. I have tried the opaque option I still get the same Translator NULL error.
Please anyone help....

Sending Msg From HTTP client to XI through JMS Adapter using WebSphereMQ

Hello
I am trying to send some msg from Http client
I configured JMS adapter as receiver
Transport Protocol :WEBsphereMQ JMS provider
Message protocol :JMS1.x
I have given the Ip address of my machine where I installed WEB Sphere MQ
Server Port :1416
Transport Protocol :WebSphere MQ
JMS compliant: JMS-compliant
In SXMB_MONI
Http client sends message without any error.
But while tracing I got message
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
Can anybody tell me the solution..
Thnaks

Hi,
I have not directly faced this but i may suggest ,
1. What do you see in sxmb_moni, do you have a queue problem?
2. see this File-to-File Scenario Stopped Working the reply from Shravan and the last message.
<i>The XBTO que was the problem. I deleted all LUWs in it and now new transactions are working again</i>
3. You may also use this /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Regards,
Anirban.

MessageTransformBean in sender JMS Adapter flat file to xml conversion

Hi All,
The scenario is MQ (Flat File ) --->PI -
>Idoc
The flat file structure is
112233
AABBCC
The expected XML Structure after using MessageTransformBean in the sender JMS adapter is
<Record>
<Row>
<f1>11</f1>
<f2>22</f2>
<f3>33</f3>
</Row>
<Row>
<f1>AA</f1>
<f2>BB</f2>
<f3>CC</f3>
</Row>
</Record>
But I am getting 2 SEPARATE xml messages each with only one Row in it like the following
1st XML:
<Record>
<Row>
<f1>11</f1>
<f2>22</f2>
<f3>33</f3>
</Row>
</Record>
2nd XML:
<Record>
<Row>
<f1>AA</f1>
<f2>BB</f2>
<f3>CC</f3>
</Row>
</Record>
I would like to have one xml message with all rows in it.It seems the MessageTransformBean is not recognizing the end of line in the flat file.Do i need to use endSeparator explicitly.
I followed the "How to use Content Conversion in JMS Adapter " and configured the adapter,still no luck..
Any Help greatly Appreciated
Thanks,
C

Hi Chirag,
The parameter name sequence changes alphabetically by itself when I save and activate it eventhough I enter as it is in the document.How to stop changing this sequence or put it the order as required in the Module Processor.
Currently my sequence is
Transform.Class
Transform.ContentType
xml.conversionType
xml.documentName
xml.documentNamespace
xml.fieldFixedLengths
xml.fieldNames
xml.processFieldNames
xml.structureTitle
Let me know how to change the sequence ,if that is the issue.
Thanks,
C

Sender JMS Adapter - NOT Working

Hello Everybody - We are on SP13, also installed JMS Driver files on the system. We are running, Central Adapter Engine.
We configured the Sender JMS Adapter for WBI MQ->XI->SAP scenario. We need to JMS Adapter to be configured to connect to WBI from XI. Everything looks great in configuration but in the Adpater Monitoring, JMS Adapter is with Error Status and Message says "Sender channel. Details: (No detail information set.)".
Does anybody has any idea about this error ?
I checked SAP Help link as well on this. Based on this link http://help.sap.com/saphelp_nw04/helpdata/en/ca/e7673c86d19b35e10000000a11402f/frameset.htm. Do we need to configure this JMS Adapter somewhere on teh server as well ? If yes, then where ? Pls respond if you have any clue about it.
Thanks in anticipation...

Hello Stefan - Thanks for response.
Here are the Parameters.......
Adapter Type: JMS
Sender Type Clicked
Transport protocol:WebSphereMQ (non-JMS)
Message protocol:JMS 1.x
Adapter Engine:Integration Server
Queue ConnectionFactory Java Class:com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class:com.ibm.mq.jms.MQQueue
IP Address or Server Name:10.9.48.154
Server Port:1414
Queue Manager Name:WBIDEV
Channel Name:WBI.XI.SVRCONN
JMS Queue:XI_REQUEST
Transport/Network Protocol:TCP/IP
JMS-Compliant:JMS-Compliant
Transactional JMS Session:Check box Set
JMS Queue User:XIUSER
JMS Queue Password:********
Set XI message ID(MessageID) to:GUID(recommended value)
Set XI cenversation ID(conversationID) to:No value
Mapping of Message:Message Payload=JMS Payload
Quality of Service:Exactly Once
Time Period for duplicate check for EO(IO)(secs):86400
Wait After Message Error(msecs):1000
Wait before Reconnect(msecs):1000
Status:Active
The Error Message I see in the Adapter Monitor is "Sender Channel. Details: (No detail information set.)
Pls advice If I am missing anything ?
Thanks....
Amrish.

Sender JMS adapter configuration for IBM MQSeries

Dear All,
i am doing a IBM MQSeries 5.2.x Message ->sender JMS adapter -> XI server -> receiver RFC adapter -> R/3.
i have deployed the JMS adapter with the required jar files of IBM MQSeries 5.2.x in XI server.
in Sender JMS adapter configuration for IBM MQSeries 5.2.x, i have put following data:
1. Transport Protocol: Websphere MQ - is it okay?
in JMS provider settings:
2. in channel name - what should be there?
3. Transport Network protocol should be TCP/IP or WebsphereMQ - how to decide this thing.
4. JMS Complaint - whether WebsphereMQ or JMS API.
in JMS Settings:
5. JMS Queue user - is this IBM MQSeries 5.2.x Queue User or someother user?
6. JMS Message Selector - what data to take here.
So if anybody has connected IBM MQSeries 5.2.x to XI via JMS adapter, please answer my above queries.
Regards,
Rajeev Gupta

Hi Swaroop,
you can send me those documents at my gmail-id : [email protected]
Hi All,
one more question - to connect XI server to IBM MQSeries via JMS adapter in ID, do we need to have a MQSeries Client installed on XI server - or - just by configuring JMS adapter, we can send messages from IBM MQSeries to XI server without any MQSeries client on XI server?
Why Channel name is required in JMS configuration data?
Thanks,
Rajeev Gupta

Correlation issue in JMS adapter - SYNC/ASYNC scenario without BPM

Hi,
I am working on a SYNC/ASYNC scenario with JMS adapter without using BPM. My scenario is SOAP<>PI>JMS. I configured the interface as below:
1. SOAP Sender channel
2. JMS Receiver Channel writing to Queue A.
     Module used:      a. RequestOneWayBean
               b. WaitResponseBean
     Correlation Settings:
               a. Set JMS Correlation ID to "XI Message ID"
               b. Store JMS CorrelationID of request (Checked)
               c. Set JMS Property to "JMS Correlation Id"
               d. Value = "XI MEssage ID"
3. JMS Sender channel reading from queue B ( I am exporting the message from queue A and importing into queue B)
     Module used:      a. NotifyResponseBean
     Correlation Settings:
               a. Set XI MEssage Id to "GUID"
               b. Set XI Conversation ID to "Stored JMS COrrelationID of Request"
I can see the cid in the message from queue A. But I observed thhat the header format of the message in Queue A is "MQSTR".
ISSUE:
1. While writing the message to queue A, below adapter log details(part b) concerned me:
     a. Message '8747a7c2-2b06-11df-8055-005056a70ed6' successfully processed by channel
     b. Could not create acknowledgements for message '8747a7c2-2b06-11df-8055-005056a70ed6'
I am not sure why I am receiving the message that " could not create acknowledgements"
2. While reading the message from the sender channel,I consistently get the error message as below:
     a. XI message ID corresponding to JMS message with ID 'ID:414d51205341504449442e514d202020c67b954b20005602'
          will be created as a new GUID with value '21bca916-424f-41f6-3347-c71090392b58'
     b. Error while processing message '21bca916-424f-41f6-3347-c71090392b58'; detailed error description:
          com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: found no correlation ID: RecoverableException:
          found no correlation ID at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:105) ...
Below are the blogs which I have already gone through:
1. JMS Synchronous Scenario without BPM - Correlation Settings and Transactional JMS Session
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b028f6f6-7da5-2a10-19bd-cf322cf5ae7b
2. Note: 1086303
3. Sync / Async Bridge without BPM
In the note, they mentioned something about header being "MQRFH2". BUt in our case, the header is "MSSTR". Not sure whether it makes any difference.
Please help.
Edited by: GP on Mar 9, 2010 4:24 AM

Hi,
detailed error description:
com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: found no correlation ID: RecoverableException:
found no correlation ID at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:105) ...
This error would generally arose when there are multiple messages, got stuck in the outbound queue. Try to stop both the sender and receiver JMS comunication channels and clear both the inbound and outbound queues.
Once all the messages in the queue are cleraed, try posting the message again.
Regards,
Swetha.

Error in JMS Adapter Configuration.

Hi,
Its regarding JMS receiver adapter for MQ Series.
We have MQ 6.0 installed on PI server. While trying to connect thorough JMS receiver adapter we are getting a connection failure error at communication channel level.
The MQ administrator is of the opinion that as MQ is local to the PI server a channel is not required.
In the MQ server, the administrator has created a Manager and Queue which we are using in the JMS receiver channel.
We have provided the queue connection factory as the default one used for MQ 5.3
class also as the default. (All the extra jar files required for MQ 6.0 is deployed).
The error description says:
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '10.23.86.134:XBEIG_QMGR1'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:586)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2110)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused.
Any inputs would be very helpful...
Many Thanks,
Rosine.

you can check the SAP Note 856346 - FAQ on JMS adapter it might have some info

Missing message in JMS adapter sender

Hi,
we have a synchronous interface with a JMS adapter. The scenario is:
ECC 5.0 -> XI -> MQSeries -> XI -> ECC 5.0
We put the message in the queue MQ correctly and we get the response message. I can see this in the adapter monitoring in RuntimeWorkbench. But from this moment the message is missing. I can't see anything in the bpm monitoring (SXMB_MONI_BPE). The bpm stops in workitem receive but doesn't return any error.
I don't know how to see where we lose the message and why.
Thanks for advance.
Paloma

Hi,
Can you see your message in SXMB_MONI? Is your BPM is in running state in sxmb_moni?
You can double click on "PE" in sxmb_moni. It will take you to the Workflow display. Then click on button Technical details,which will show you all steps and if you expand all branches..you should be able to see your error / exception message in case if any.
Please check n let us know the result.
Nilesh

SOA Suite 11g - dynamic JNDI destination JMS adapter

hi there soa suite users,
im currently using oracle soa suite 11g,
my use case having a bpel process processing something
and then route the result to several queue.
like this:
jms/adminduk/queue/mks1
jms/adminduk/queue/pdg1,
etc...
so the destination name can be build dynamically in the bpel,
and i stored in a string variable "destName".
(im using WLS 10.3 jms)
now i need to invoke a jms adapter service with produce operation,
but the queue destination needs to be using the variable "destName".
i already tried using assigning to property "jca.jms.JMSDestinationName"
in the invoke activity.
<invoke ...>
<bpelx:inputProperty name="jca.jms.JMSDestinationName"
variable="destName"/>
</invoke>
but it seems not working, and im getting this error:
Caused by: com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
parts: {{
summary=<summary>Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation
'SendSinkBioWniFromDaerahResponse' failed du
e to: ERRJMS_ERR_CR_QUEUE_PROD.
ERRJMS_ERR_CR_QUEUE_PROD.
Unable to create Queue producer due to JMSException.
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
</summary>
,detail=<detail>[JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer
requested. The linked
exception may contain more information about the reason for failure.</detail>
,code=<code>null</code>
this is a basic use case of jms interoperability,
anyone have answers to this ??
thank you :)

Hi,
If someone is looking to dynamically set the JMSqueue name here is the solution.
in the Invoke activity set "jca.jms.JMSDestinationName"
value to "JMSHeaderVariable"
set the type to "input"
in the JMSHeaderVariable set the queue name dynamically.
and in the JMSadapter give any valid queue name, still the message will be routed to the queue which you have set in the invoke adapter.

JMS adapter could not receive message from Tibco EMS topic

I'm trying to consume message from tibco EMS topic using Oracle SOA JMS adapter. Can anyone please let me know the steps to do this. Appreciate your help.
Thanks,
SB

Increase Log level for cube.activation to debug and check the logs by stopping & starting the activation agent(I mean Retire and activate the process) .. It should give a clue on what's happening..

JMS adapter transaction. Rollback message to queue.

Hi all !
A have question about jms adapter transaction. My composite application has 3 steps : JMS adapter (listener), mediator, WS adapter. JMS adapter listen queue push message to mediator, mediator invoke web service. If ws not available (server down), mediator try recovery 5 times. After 5 times, reject message from queue. I wont rollback message to queue. I saw examples with JMS + BPEL, but it not help me. Anybody can help me.

Hi,
You don’t need to catch a mediator fault – you can let it rollback to the JMS Queue and let the Queue do the retries.
To get the retries working, log in to the weblogic console and navigate to JMS Modules -> Your Module -> Your Queue -> Configuration -> Delivery Failure
Here you will find options for Redelivery Limit. Set this to the number of retries you need.
Then navigate to the connection factory you want and set the redelivery delay.
This should get your desired behaviour, but once the message has failed it will be discarded. If you prefer to put it on an error queue you can create an error queue, and in the original queue’s, goto Delivery Failure, change the expireation policy and set the Error Destination to be your error queue.
Hope that helps!
Robert

JMS Adapter Supports below message

Hi Frnds,
I am working on one scenario i have to read and write RFH2 Message from MQ,we decided to use jms adapter.
JMS Adapter supports below Message to put in MQ,
<Data>
     <MQRFH2>
          <usr>
               <TransactionType>GL_Update</TransactionType>
               <Environment>LIVE</Environment>
               <SourceScheme>EANCM</SourceScheme>
               <SourceApplicationId>5051150003606</SourceApplicationId>
               <DestScheme>EANCM</DestScheme>
               <DestinationRouting>5051150003330</DestinationRouting>
               <OriginalRouting/>
               <MessageRecordCount>1</MessageRecordCount>
               <BusinessTransactionId>20090405193001</BusinessTransactionId>
               <ParentBusTID/>
               <ParentBusId/>
               <EECode>Y</EECode>
          </usr>
          <mcd>
               <Msd>xml</Msd>
          </mcd>
     </MQRFH2>
     <Message>
          <GL_Update>
               <header>
                    <SourceEAN>5051150003606</SourceEAN>
                    <DestinationEAN>5051150003330</DestinationEAN>
               </header>
               <detail>
                    <AuthorisedUser/>
                    <HeaderText/>
                    <HeaderReference/>
                    <PostingItem>
                         <ProfitCentre>7027101000</ProfitCentre>
                         <CostCentre/>
                         <AccountCode>0001413150</AccountCode>
                         <GlobalBusinessIdentifier>AU10</GlobalBusinessIdentifier>
                         <MonetaryAmount>0000000100.00</MonetaryAmount>
                         <GlobalCurrencyCode>AUD</GlobalCurrencyCode>
                         <RunDate>20080725</RunDate>
                         <Description>IV006270M000000000000000000001</Description>
                         <WorkBreakdownStructureElement/>
                         <BudgetRequest/>
                         <TransactionType/>
                         <TransactionNumber/>
                         <PostingKey>50</PostingKey>
                         <SalesTax>
                              <SalesTaxCode/>
                              <SalesTaxAmount/>
                         </SalesTax>
                         <PersonnelNumber/>
                         <Assignment/>
                         <CalculateTaxBase/>
                         <BaselineDate/>
                         <PaymentTerms/>
                         <MedicalReference/>
                    </PostingItem>
                    <PostingItem>
                         <ProfitCentre/>
                         <CostCentre/>
                         <SalesTax>
                              <SalesTaxCode>P3</SalesTaxCode>
                         </SalesTax>
                    </PostingItem>
                    <PostingItem>
                         <ProfitCentre>7022001001</ProfitCentre>
                         <CostCentre/>
                         <AccountCode>0001701001</AccountCode>
                    </PostingItem>
               </detail>
               <trailer>
                    <thisDocumentGenerationDateTime>20090405T072928Z</thisDocumentGenerationDateTime>
                    <thisDocumentIdentifier>20090405T072928Z</thisDocumentIdentifier>
               </trailer>
          </GL_Update>
     </Message>
</Data>
please help me on this
it possible to achieve using JMS adapter or not?? what is the alternative solution ??
Regards,
raj

Hi RSR,
JMS is the better way to connect sonic MQ.below iam attaching you few points while using JMS.
1.for the JMS adapter an external driver is needed (java archive)
2.this archive is provided by the respective provider of the queuing system
3.the driver has to be deployed via SDM , see XI configuration guide for details
4.Routing rules and sender has to be specified as for any other channel in the directory
    object model
5.the message header information is determined from the appropriate sender
   agreement for the communication channel
6.the communication channel defined must be used in exactly one sender agreement
7.at least the interface name and the sender service must be qualified in the
    sender agreement ,other fields are optional
Depending on the transport protocol selected, specify the following :
8.For Sonic MQ JMS Provider :
·        Java class QueueConnectionFactory
·        Java class queue
·        IP address or server name
·        Server port
·        JMS queue
9.JNDI JMS Provider Lookup
·        JNDI name of QueueConnectionFactory
·        JNDI name of JMS queue
·        Name of JNDI Initial Context Factory
·        Address of JNDI server
·        JNDI users
·        JNDI password with confirmation
10.
For WebSphereMQ (MQ Series) JMS Provider
·        Java class QueueConnectionFactory
·        Java class queue
·        IP address or server name
·        Queue manager name
·        Channel name
·        JMS queue
·        Character set for non-ASCll names
·        Transport/network protocol
·        Target client
11.
JMS Provider Administered Objects via File
   File name of serialized object QueueConnectionFactory
   File name of serialized object Queue
With Rgds,
MF.Haq

JMS adapter webspehere mq, network failure - stop

Similar Messages

Maybe you are looking for