Platforms supported by JMS adapter

Hi ,
Can anybody tell which platform/OS the JMS adapter supports ?
Regards,
Tarang

Tarang,
There is nothing to do compatibility support for JMS adapter. The one and only thing is the JMS provider like MQ-Series , Sonic MQ etc.. needs to be anlayzed for Platform/OS compatibility.
Best regards,
raj.

Similar Messages

Language support in JMS adapter with Oracle JDev 10.1.3.1

Hi,
I' using JDeveloper 10.1.3.1 with Oracle SOA Suite - ESB 10.1.3.1 in the following scenario:
1) Use Database adapter with "on insert" condition to read Student record with Chinese name (Unicode format) - ESB process
2) Use JMS adapter to push this data into "DemoTopic" as string - ESB process
3) Use Message Driven Bean's (EJB 3.0) "onMessage" method to fetch the data from JMS topic - J2EE app
4) Use JDBC executeUpdate to update this Chinese name into another database table - J2EE app
5) Finally, verify the updated Chinese name in ADF application - J2EE app
Prerequisites
1) The database charset on both sides of the flow is UTF8
2) The ADF application JSF page encoding is UTF8
3) The SOA Suite is installed on DB repository (UTF8 charset)
Result
1) The flow from Step 1-5 works.
2) But, the println of the JMS message (holding the Chinese name) gives "????" when checked with Wordpad (Unicode readable word processor)
3) Junk characters are inserted into the database
Please let me know where I'm going wrong. Also, let me know if I need to configure/set the character encoding in OC4J, or the JMS adapter and how.

Hi all,
This is been resolved by using the AL32UTF8 character set in the database. JMS adapter by default supports UTF-8. No setting/configuration needs to be done.

Calling Foreign JMS in SOA Suite 11g JMS Adapter

Hi,
Just want to get some guidance in the implementation of Foreign JMS in WebLogic 10.3.
I followed the creation of the Foreign JMS Server using this document:
http://download.oracle.com/docs/cd/E12839_01/apirefs.1111/e13952/taskhelp/jms_modules/foreign_servers/CreateForeignServers.html
I am trying to connect to a remote Weblogic 10.3 JMS queue but cannot get pass the JDev wizard stage.
I need to call the foreign JMS via the Fusion 11g JMS Adapter but cannot lookup the destination from the JDev wizard. My composite will produce a message that will end up in the remote queue.
Has anybody got this to work? Is this supported in JMS Adapter? I've read quite a few using MDB to call the Foreign JMS but not JMS Adapter.
Regards,
Robert

Please refer to the following document that shows how to access remote wls jms queues and topics. This is the preferred way when accessing remote wls destinations.
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10231/adptr_jms.htm#BABJACJA
Thanks
Aman

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

Support for Topics in XI JMS Adapter

Hello Everyone,
I am trying to configure Topics instead of queues for JMS Adapter and I am not able to exchange messages with Topics. However, when I change Topics with Queues in JMS configuration file on XI 2.0, the scenario works okay.
Can anyone let me know if JMS adapter for XI 2.0 or XI 3.0 supports topics. If yes, then what changes should I make in order to exchange messages with Topics via JMS adapter.
Thanks,

Hi Lalit,
No support for JMS topics in SAP XI 2.0 nor XI 3.0.
I don't know why it isn't supported. Maybe SAP wants to avoid the hassle of configuring durable subscribers. And customers forgetting to remove durable subscriptions whereby message pile up until the JMS broker runs out of disk space.
Kind regards, Guy Crets

How to covert EBCDIC format to ASCII in JMS Adapter??????????

Hi All,
I am developing one JMS to File scenario, in which JMS adapter will pick file which is in EBCDIC format from WebSphere MQ and send it to receiver file system by receiver file adapter. when i am trying this, i am getting file in EBCDIC format in receiver file system, but the file system is expecting data in ASCII format.
Is there any options to encode the EBCDIC format to ASCII in Sender JMS Adapter or Receiver File Adapter.
Thanks,
Madhusudhan.

Hi,
It was Basis / Database / OS staff that configured this aspect of the connection, and I am afraid I do not have any more details.
A Google search gave me the following from IBM Documentation on MQ Series:
<a href="http://publib.boulder.ibm.com/infocenter/wsphelp/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/ucli_pqcfm.html">http://publib.boulder.ibm.com/infocenter/wsphelp/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/ucli_pqcfm.html</a>
MQSeries queue connection factory settings for application clients
CCSID
The coded character set identifier for use with the WebSphere MQ queue manager.
This coded character set identifier (CCSID) must be one of the CCSIDs supported by WebSphere MQ.
Data type String
For more information about supported CCSIDs, and about converting between message data from one coded character set to another, see the WebSphere MQ System Administration and the WebSphere MQ Application Programming Reference books. These are available from the WebSphere MQ messaging multiplatform and platform-specific books Web pages; for example, at <a href="http://www-3.ibm.com/software/ts/mqseries/library/manualsa/manuals/platspecific.html">http://www-3.ibm.com/software/ts/mqseries/library/manualsa/manuals/platspecific.html</a> , the IBM Publications Center , or from the WebSphere MQ collection kit, SK2T-0730.
hope this may be of some help
Andrew

Unable to get BPEL composite with JMS Adapter running.

Hello All,
I have tried to build a BPEL Composite to use JMS Adapter, by following the link http://blogs.sun.com/malkit/entry/oracle_soa_suite_bpel_to
Steps in WebLogic console:
1. Created a new JMS Server JMSServer-0 (file persistent store) this is targeted to AdminServer
1. Created a new JMS Module SystemModule-0
3. Created a connection factory in this module JNDI jms/SendRecvConnectionFactory
4. Created a queue in this module JNDI jms/ReceiveQueue
5. Created a SubDeployment Subdeployment0 for these two components.
6. Created a new JMSAdapter connection pool JNDI eis/tst/TestJMSConn and set the ConnectionFactoryLocation property to jms/SendRecvConnectionFactory
Next, I created a simple Java client and tested the JMS Queue to work fine. This went well.
Next, used JDeveloper to create a BPEL Composite to use JMSAdapater, and followed the guidelines given in the above URL to create the JCA file.
While deploying this BPEL composite, I hit a warning in SOA diagnostic server:
JMSAdapter JMSSampleProj JmsDDEndpoint_onFailure: Unable to resolve 'jms.ReceiveQueue'
As a result of this warning, the BPEL Composite instances do not get created when I send a message from the test client.
Please find herewith the log details.
I am using JDeveloper Build JDEVADF_11.1.1.4.0_GENERIC_101227.1736.5923 and FMW 11g R1 PS3 RC11.
Any help here?
[2011-04-20T08:33:12.098-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.bpel.engine.deployment] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] BPEL Component "default/JMSSampleProj!1.0*soa_8a1f7f5d-5ede-4e3a-8740-20fb90ffdab2/JMSampleProcess" successfully loaded.
[2011-04-20T08:33:12.098-05:00] [soa_server1] [NOTIFICATION] [] [oracle.integration.platform.blocks.deploy] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] [Deployment] Component: JMSampleProcess was successfully deployed to service engine:implementation.bpel, for composite:JMSSampleProj
[2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.OutBound/1.0] :init Initializing OutBound_jms.jca
[2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> OutBound JCAEndpointInteraction::initInteraction - Activating Endpoint Interaction, Endpoint Id='OutBound
[2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.OutBound/1.0] :init Successfully initialized OutBound_jms.jca
[2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.integration.platform.blocks.mesh] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] EventBus not null
[2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.integration.platform.blocks.mesh] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] component : Component Name: JMSampleProcess[[
implementation: oracle.fabric.composite.component.implementation.BPELImplementation@51db9e4
oracle.fabric.composite.model.ComponentTypeModel@51db9e6
[2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.bpel.engine] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] CubeServiceEngine=> initing default/JMSSampleProj!1.0*soa_8a1f7f5d-5ede-4e3a-8740-20fb90ffdab2/JMSampleProcess
[2011-04-20T08:33:12.458-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :load Loading InBound_jms.jca ..
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound Performing JCAEndpointActivation::prepareActivation for {PayloadType=TextMessage, UseMessageListener=false, DestinationName=jms/ReceiveQueue}
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::prepareActivation - Locating JCA Binding Component instance: SCA_AS11R1
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::initiateInboundJcaEndpoint - Creating and initializing inbound JCA endpoint for:[[
endpoint='InBound'
WSDL location='oramds:/deployed-composites/default/JMSSampleProj_rev1.0/InBound.wsdl'
portType='Consume_Message_ptt'
operation='Consume_Message'
activation properties={PayloadType=TextMessage, UseMessageListener=false, DestinationName=jms/ReceiveQueue}
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::initiateInboundJcaEndpoint - Creating endpoint (0) for InBound
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::prepareActivation - Done preparing JCAEndpointActivation for Service 'InBound'
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :load Successfully loaded InBound_jms.jca
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :init Initializing InBound_jms.jca
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::performActivation - Performing JCA Endpoint Activation, Endpoint Id='InBound'
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound Performing endpoint activation (1) for InBound
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj JCA Binding Component instance: SCA_AS11R1 - endpointActivation for portType=Consume_Message_ptt, operation=Consume_Message
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj Creating new instance of Resource Adapter oracle.tip.adapter.jms.JmsResourceAdapter
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj JCA Binding Component instance: SCA_AS11R1 - starting Resource Adapter oracle.tip.adapter.jms.JmsResourceAdapter
[2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JmsResourceAdapter_start: Jms Adapter started
[2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JmsResourceAdapter_endpointActivation: Activating endpoint Endpoint_1
[2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JMSSampleProj JmsDDEndpoint_start: Starting endpoint Endpoint_1
[2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JMSSampleProj JmsDDEndpoint_run: Calling register...
[2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj JCA Binding Component instance: SCA_AS11R1 - successfully completed endpointActivation for portType=Consume_Message_ptt, operation=Consume_Message
[2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :init Successfully initialized InBound_jms.jca
[2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> :defaultRevisionChanged - updated default revision to default/JMSSampleProj!1.0 for default/JMSSampleProj
[2011-04-20T08:33:12.567-05:00] [soa_server1] [NOTIFICATION] [SOA-21538] [oracle.integration.platform.blocks.deploy.servlet] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] Removing temporary directory: C:\DOCUME~1\abhatika\LOCALS~1\Temp\1\sar_base_dir_1303306387379.
[2011-04-20T08:33:12.567-05:00] [soa_server1] [NOTIFICATION] [SOA-21557] [oracle.integration.platform.blocks.deploy.servlet] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] CompositeDeploymentServlet-----> completed deploying sca_JMSSampleProj_rev1.0.jar successfully. Time spent: 5.188 sec.
[2011-04-20T08:33:13.036-05:00] [soa_server1] [WARNING] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041fd,0] [APP: soa-infra] JMSAdapter JMSSampleProj JmsDDEndpoint_onFailure: Unable to resolve 'jms.ReceiveQueue'. Resolved 'jms'

Hi,
Try targetting it to soa_server1 instead of admin server.

How to install Oracle AS JMS Adapter on Websphere (or any J2EE server)

Hi,
We have a requirement in which the client wants to connect to the OC4J JMS running in SOA Suite (Oracle Application Server 10.1.3.4).
They are using Websphere. We are exploring ways by which they can connect from Websphere application to Oracle AS OC4J JMS.
One option is - deploy the Oracle AS JMS adapter in Websphere and then use it to connect to the OC4J JMS.
Please let us know if this is the right approach. Also, if so, kindly point to the documentation regarding how to install the JMS adapter on 3rd party J2EE servers such as websphere.
Rgds,
Amit

While searching the knowledge base I found the following note, which seems to suggest that Oracle Adapters are not deployble on other J2EE application servers:
Support For Jca Adapter In Other Application Servers Like Jboss [ID 1114738.1]
==============================================
From the statements in documentation it may be implied that jca adapter should be deployable on any application server that is compliant with j2ee/jca. Please note that this cannot be implied at this time and jca adapter cannot be deployed on other application servers than OAS in BRM 731 due to some technical constraints. So currently we can support only OAS and not JBoss or another application server , in BRM 731. The documentation will be updated accordingly to reflect this.

JMS adapter settings for response to dynamic queue

Hello,
We are sending a message through JMS to SAP in a synchronous manner (client waiting for the reply after sending the request). The SAP is receiving and processing the message.
We configured the JMS Sender & Receiver channel as per solution given in SDN for the quetion. ( (2.8) Does the JMS Adapter support the JMSReplyTo feature? )
1. In Sender communication channel, checked the "JMS Message ReplyTo Destination" attribute of 'Adapter specific message attributes'
2. In Receiver communication channel, added the "JMS.Message.DynamicDestination" parameter and value 'true' (without quotes for both strings) in "Set JMS Additional Parameters" table
3. Added the "JMSReplyTo" header syntax in input xml message as below:
 a. Message : <?xml version="1.0" encoding="UTF-8"?>
 <ns0:getEmployeeInfo xmlns:ns0="namespace">
 <employeeId>0000001</employeeId>
 </ns0:getEmployeeInfo>
 b. Destination = com.someDestination
 c. JMSReplyTo= com.someReplyQueue
We have selected Transport protocol option "Access JMS Provider Generically"
But it is not able to send the reply to replyTo destination of the message.
Wondering if there is anything in the JMS Adapter setting like reply to Destination (technical term DCJMSReplyTo) which can be set to reply queue of the message (to a dynamic destination).
Please let me know in case anybody knows about the same.
Thanks & Regards,
Jayashri Rade

Refer: http://docs.oracle.com/cd/B14099_19/integrate.1012/b25307/adptr_jms.htm
•The JMS API specifies three types of acknowledgments that can be sent by the JMS publisher:
◦DUPS_OK_ACKNOWLEDGE, for consumers that are not concerned about duplicate messages
◦AUTO_ACKNOWLEDGE, in which the session automatically acknowledges the receipt of a message
◦CLIENT_ACKNOWLEDGE, in which the client acknowledges the message by calling the message's acknowledge method

How to set JMS user property in JMS Adapter.

I am using Jdeveloper and SOA 11g. I want to filter some JMS messages from a topic based on a JMS user property. It is consumed using (JMS Adapter) consumer --> Mediator---> DBAdapter.
My Question is how to define a JMS user property using Jdeveloper 11g.
Thanks
Edited by: user5108636 on 24/06/2010 16:10

In Mediator mplan Assign Values use a property expression in the "to" side like:
jca.jms.JMSProperty.XXX
where XXX is the name of the property you would like to have created and populated. In source it will look like:
<Mediator name="A03QueueWFeedMediator" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://xmlns.oracle.com/sca/1.0/mediator"
wsdlTargetNamespace="http://www.oracle.com/integration/b2b/A03QueueWFeedFromB2B/">
<operation name="receive" deliveryPolicy="AllOrNothing" priority="4"
validateSchema="false">
<switch>
<case executionType="direct" name="A03QueueWFeedToJMS.Produce_Message">
<action>
<transform>
<part name="$out.body"
function="xslt(xsl/ADT_AXX_To_ADT_AXX.xsl, $in.body)"/>
</transform>
<assign>
<copy target="$out.body/imp1:ADT_AXX/imp1:MSH/@Type"
value="$in.property.b2b.documentDefinitionName"
xmlns:imp1="NS_64FCBED013AA409D933F624674E67BF220070423183755"/>
<copy target="$out.body/imp1:ADT_AXX/imp1:MSH/@ID"
value="$in.property.b2b.fromTradingPartnerId"
xmlns:imp1="NS_64FCBED013AA409D933F624674E67BF220070423183755"/>
<copy target="$out.body/imp1:ADT_AXX/imp1:MSH/@Name"
value="$in.property.b2b.toTradingPartnerId"
xmlns:imp1="NS_64FCBED013AA409D933F624674E67BF220070423183755"/>
<copy target="$out.property.b2b.conversationId"
value="$in.property.b2b.conversationId"/>
<copy target="$out.property.b2b.documentDefinitionName"
value="$in.property.b2b.documentDefinitionName"/>
<copy target="$out.property.b2b.documentProtocolName"
value="$in.property.b2b.documentProtocolName"/>
<copy target="$out.property.b2b.documentProtocolVersion"
value="$in.property.b2b.documentProtocolVersion"/>
<copy target="$out.property.b2b.documentTypeName"
value="$in.property.b2b.documentTypeName"/>
<copy target="$out.property.b2b.fromTradingPartnerId"
value="$in.property.b2b.fromTradingPartnerId"/>
<copy target="$out.property.b2b.fromTradingPartnerIdType"
value="$in.property.b2b.fromTradingPartnerIdType"/>
<copy target="$out.property.b2b.toTradingPartnerId"
value="$in.property.b2b.toTradingPartnerId"/>
<copy target="$out.property.b2b.toTradingPartnerIdType"
value="$in.property.b2b.toTradingPartnerIdType"/>
*<copy target="$out.property.jca.jms.JMSProperty.conversationId"*
value="$in.property.b2b.conversationId"/> <copy target="$out.property.jca.jms.JMSProperty.documentDefinitionName"
value="$in.property.b2b.documentDefinitionName"/>
<copy target="$out.property.jca.jms.JMSProperty.documentProtocolName"
value="$in.property.b2b.documentProtocolName"/>
<copy target="$out.property.jca.jms.JMSProperty.documentProtocolVersion"
value="$in.property.b2b.documentProtocolVersion"/>
<copy target="$out.property.jca.jms.JMSProperty.documentTypeName"
value="$in.property.b2b.documentTypeName"/>
<copy target="$out.property.jca.jms.JMSProperty.fromTradingPartnerId"
value="$in.property.b2b.fromTradingPartnerId"/>
<copy target="$out.property.jca.jms.JMSProperty.fromTradingPartnerIdType"
value="$in.property.b2b.fromTradingPartnerIdType"/>
<copy target="$out.property.jca.jms.JMSProperty.toTradingPartnerId"
value="$in.property.b2b.toTradingPartnerId"/>
<copy target="$out.property.jca.jms.JMSProperty.toTradingPartnerIdType"
value="$in.property.b2b.toTradingPartnerIdType"/>
</assign>
<invoke reference="A03QueueWFeedToJMS" operation="Produce_Message"/>
</action>
</case>
</switch>
</operation>
</Mediator>
The runtime will see something like:
[2010-09-09T11:48:06.353+10:00] [AdminServer] [TRACE] [] [oracle.soa.adapter] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@60ddbc76] [userId: weblogic] [ecid: 0000Ifo9olH2zGWjLxmJOA1CY0sg0001jY,0] [SRC_CLASS: oracle.integration.platform.blocks.adapter.fw.log.LogManagerImpl] [APP: soa-infra] [dcid: 02d1ff4621073810:26418f01:12af379c141:-7fd3-0000000000000219] [SRC_METHOD: log] Jms Adapter A03QueueWFeed:A03QueueWFeedToJMS [ Produce_Message_ptt::Produce_Message(body) ] XMLHelper_convertJmsMessageHeadersAndPropertiesToXML: <JMSInboundHeadersAndProperties xmlns="http://xmlns.oracle.com/pcbpel/adapter/jms/">[[
<JMSInboundHeaders>
<JMSCorrelationID></JMSCorrelationID>
<JMSDeliveryMode>2</JMSDeliveryMode>
<JMSExpiration>0</JMSExpiration>
<JMSMessageID>ID:<911867.1283996886119.0></JMSMessageID>
<JMSPriority>4</JMSPriority>
<JMSRedelivered>false</JMSRedelivered>
<JMSType></JMSType>
<JMSTimestamp>1283996886119</JMSTimestamp>
</JMSInboundHeaders>
<JMSInboundProperties>
<Property name="documentProtocolVersion" value="2.3"/>
<Property name="toTradingPartnerIdType" value="Name"/>
*<Property name="conversationId" value="C0A83C0712AF42D840E0000074BA3CCC"/>* <Property name="documentTypeName" value="ADT"/>
<Property name="tracking_conversationId" value="C0A83C0712AF42D866F0000074BA3CD9"/>
<Property name="tracking_ecid" value="C0A83C0712AF42D866F0000074BA3CDA"/>
<Property name="tracking_compositeInstanceId" value="60019"/>
<Property name="documentProtocolName" value="HL7"/>
<Property name="documentDefinitionName" value="QH_ADT_Generic"/>
<Property name="tracking_parentComponentInstanceId" value="mediator:45E076D0BBB411DFAF05817F5F0DD1A1"/>
<Property name="fromTradingPartnerIdType" value="Name"/>
<Property name="fromTradingPartnerId" value="HOMER"/>
<Property name="toTradingPartnerId" value="Self"/>
<Property name="JMSXDeliveryCount" type="integer" value="1"/>
</JMSInboundProperties>
</JMSInboundHeadersAndProperties>
Edited by: Michael.Czapski on 8/09/2010 18:58

Problem Encountered in JMS adapter using SEEBURGER module

While testing the receiver JMS adapter for XML to EDI conversion using Seeburger module, I am facing errors.
1. The error encountered is :
Error while processing message '4720bc32-2dfc-03d8-0000-00000a2050d3'; detailed error description: java.lang.NullPointerException at com.sap.aii.adapter.jms.core.connector.SendContextImpl.send(SendContextImpl.java:43) ...
SEEBURGER BICXIADAPTER --- Conversion of synchronous request from module chain ended with errors ---Error: [Error:ID=2061;LEVEL=1] XMLDocReader moveNext(): Cannot move to next trigger : Error in line 1: XML file should begin with white spaces or <. (Found char :U(Hex :85). DESCRIPTION: XMLDocReader Exception: Not able to move to next trigger [not specified] - trigger may not right set.
2. The targer PAYMUL xml is as follows :
( At receiver channel, the above should be converted to EDI-Paymul using the Seeburger Module)
PAYMUL XML
<?xml version="1.0" encoding="UTF-8" ?>
- <LIST>
- <S_UNA>
<D_DELIMITER>:+.? '</D_DELIMITER>
</S_UNA>
- <S_UNB>
- <C_S001>
<D_0001>UNOA</D_0001>
<D_0002>2</D_0002>
</C_S001>
- <C_S002>
<D_0004>SAPDM</D_0004>
<D_0007>ZZ</D_0007>
</C_S002>
- <C_S003>
<D_0010>000000000000</D_0010>
<D_0007>55</D_0007>
</C_S003>
- <C_S004>
<D_0017>070201</D_0017>
<D_0019>1150</D_0019>
</C_S004>
<D_0020>01945678912345</D_0020>
- <S_UNH>
<D_0062>1</D_0062>
- <C_S009>
<D_0065>PAYMUL</D_0065>
<D_0052>D</D_0052>
<D_0054>96A</D_0054>
<D_0051>UN</D_0051>
<D_0057>FUN01G</D_0057>
</C_S009>
- <S_BGM>
- <C_C002>
<D_1001>452</D_1001>
</C_C002>
<D_1004>01945678912345</D_1004>
<D_1225>9</D_1225>
</S_BGM>
- <S_DTM>
- <C_C507>
<D_2005>137</D_2005>
<D_2380>20070201</D_2380>
<D_2379>102</D_2379>
</C_C507>
</S_DTM>
- <G_SSG4>
- <S_LIN>
<D_1082>1</D_1082>
- <S_DTM>
- <C_C507>
<D_2005>203</D_2005>
<D_2380>20070201</D_2380>
<D_2379>102</D_2379>
</C_C507>
</S_DTM>
- <S_RFF>
- <C_C506>
<D_1153>ACK</D_1153>
<D_1154>01945678912345</D_1154>
</C_C506>
</S_RFF>
- <S_RFF>
- <C_C506>
<D_1153>AEK</D_1153>
<D_1154>01945678912345</D_1154>
</C_C506>
</S_RFF>
- <S_BUS>
<D_3279>IR</D_3279>
- <C_C551>
<D_4383>UGI</D_4383>
</C_C551>
</S_BUS>
- <G_SSG5>
- <S_MOA>
- <C_C516>
<D_5025>9</D_5025>
<D_5004>5000</D_5004>
<D_6345>EUR</D_6345>
</C_C516>
</S_MOA>
</G_SSG5>
- <G_SSG6>
- <S_FII>
<D_3035>OR</D_3035>
- <C_C078>
<D_3194>ES921998500000000012</D_3194>
<D_6345>EUR</D_6345>
</C_C078>
- <C_C088>
<D_3433>ABNAES17000</D_3433>
<D_1131>25</D_1131>
<D_3055>5</D_3055>
</C_C088>
<D_3207>ES</D_3207>
</S_FII>
</G_SSG6>
- <G_SSG7>
- <S_NAD>
<D_3035>OY</D_3035>
- <C_C080>
<D_3036>XYZ CORPORATION LTD</D_3036>
</C_C080>
- <C_C059>
<D_3042>XX</D_3042>
</C_C059>
<D_3164>XX</D_3164>
<D_3207>ES</D_3207>
</S_NAD>
</G_SSG7>
- <G_SSG11>
- <S_SEQ>
- <C_C286>
<D_1050>1</D_1050>
</C_C286>
- <S_MOA>
- <C_C516>
<D_5025>9</D_5025>
<D_5004>5000</D_5004>
<D_6345>EUR</D_6345>
</C_C516>
</S_MOA>
- <S_DTM>
- <C_C507>
<D_2005>227</D_2005>
<D_2380>2007-02-01</D_2380>
<D_2379>102</D_2379>
</C_C507>
</S_DTM>
- <S_RFF>
- <C_C506>
<D_1153>AIK</D_1153>
<D_1154>01901234567890</D_1154>
</C_C506>
</S_RFF>
- <S_RFF>
- <C_C506>
<D_1153>CR</D_1153>
<D_1154>01901234567890</D_1154>
</C_C506>
</S_RFF>
- <S_FCA>
<D_4471>13</D_4471>
</S_FCA>
- <G_SSG12>
- <S_FII>
<D_3035>BF</D_3035>
- <C_C078>
<D_3194>AT921998500000000011</D_3194>
<D_6345>EUR</D_6345>
</C_C078>
- <C_C088>
<D_3433>ABNAAT14000</D_3433>
<D_1131>25</D_1131>
<D_3055>5</D_3055>
</C_C088>
<D_3207>ES</D_3207>
</S_FII>
</G_SSG12>
- <G_SSG13>
- <S_NAD>
<D_3035>BE</D_3035>
- <C_C080>
<D_3036>ABC CORPORATION 1</D_3036>
</C_C080>
- <C_C059>
<D_3042>XX</D_3042>
</C_C059>
<D_3164>XX</D_3164>
<D_3207>ES</D_3207>
</S_NAD>
</G_SSG13>
- <G_SSG16>
- <S_PRC>
- <C_C242>
<D_7187>11</D_7187>
</C_C242>
- <S_FTX>
<D_4451>PMD</D_4451>
- <C_C108>
<D_4440>SENDERPN1</D_4440>
</C_C108>
</S_FTX>
</S_PRC>
</G_SSG16>
</S_SEQ>
</G_SSG11>
</S_LIN>
</G_SSG4>
- <S_CNT>
- <C_C270>
<D_6069>2</D_6069>
<D_6066>1</D_6066>
</C_C270>
</S_CNT>
- <S_UNT>
<D_0074>1</D_0074>
<D_0062>1</D_0062>
</S_UNT>
</S_UNH>
- <S_UNZ>
<D_0036>1</D_0036>
<D_0020>01945678912345</D_0020>
</S_UNZ>
</S_UNB>
</LIST>
3. The module parameters for Seeburger inputs :
( In receiver communication channel)
Processing Sequence
localejbs/CallBicXIRaBean Local Ent Bean x2e_bic_paymul
SAP XI JMS Adapter/ConvertMessageToBinary Local Ent Bean convert_XI2Bin
SAP XI JMS Adapter/SendBinarytoXIJMSService Local Ent Bean
 exit
Module Key
x2e_bic_paymul destSourceMsg MainDocument
x2e_bic_paymul destTargetMsg MainDocument
x2e_bic_paymul logAttID ConverterLog
x2e_bic_paymul mappingName See_X2E_PAYMUL_UN_D96A
x2e_bic_paymul newLine true
x2e_bic_paymul saveSourceMsg XMLEDI

Hi,
Check Below links,
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
Regards,
Phani

Jms adapter not polling messages from jms topic

Hi
We have a jms adapter configured in BPEL process which need to poll messages from JMS topic.Unfortunately its not polling message from JMS Topic if we add Message Selector and Durable Subscriber properties in jca file.Please find jca file content below
<adapter-config name="SyncCustomerPartyListCDHJMSConsumer" adapter="JMS Adapter" wsdlLocation="oramds:/apps/AIAMetaData/AIAComponents/ApplicationConnectorServiceLibrary/CDH/V1/ProviderABCS/SyncCustomerPartyListCDHProvABCSImpl.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<connection-factory location="eis/jms/aia/syncCustomerParty_cf" UIJmsProvider="WLSJMS" UIConnectionName="Dev"/>
<endpoint-activation portType="Consume_Message_ptt" operation="Consume_Message">
 <activation-spec className="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec">
 
 <property name="PayloadType" value="TextMessage"/>
 
 <property name="UseMessageListener" value="true"/>
 <property name="DestinationName" value="jms/aia/Topic.jms.COMMON.CustomerParty.PUBLISH"/>
 </activation-spec>
</endpoint-activation>
</adapter-config>
If we remove Durable subscriber and message selector properties,its able to poll messages.
Any pointer will help
thanks in advance
Baji

After changing below property in jca file.JMS adapter is able to poll messages from JMS Topic.
<property name="UseMessageListener" value="false"/>
But if i un comment below line and deploy my code again, it stop pulling the messages from topic.
<property name="DurableSubscriber" value="XYZ"/>
If i bounce the server after above change and deployment ,it will start polling the message.I am not sure why i need to restart my server after adding above property.
Thanks
Baji

JMS Adapter Destination Name value

Hi
I am trying to connect to a WLS remote distributed queue using the JMS Adapter but I am struggling to find the correct format for the destination name property as each time it gives various JMSExceptions stating that it cannot find the queue. Below is the .jca properties
<connection-factory location="eis/wls/Queue" UIConnectionName="OSB_Test" UIJmsProvider="WLSJMS" adapterRef=""/>
<endpoint-activation portType="Consume_Message_ptt" operation="Consume_Message">
<activation-spec className="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec">
<property name="DestinationName" value="jndiEmployeeDQ"/>
<property name="UseMessageListener" value="false"/>
<property name="PayloadType" value="TextMessage"/>
</activation-spec>
</endpoint-activation>
I have also set the factory properties of the outbound connection pool as follows
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory; java.naming.provider.url= t3://<remote-hostname>:<port>;java.naming.security.principal= <username>;java.naming.security.credentials=<password>
Below is the message I am receiving
<01-Feb-2011 11:35:32 o'clock GMT> <Warning> <oracle.soa.adapter> <BEA-000000> <JMSAdapter TestEmployeeQueueA
BINDING.JCA-12135
ERRJMS_ERR_CR_QUEUE_CONS.
ERRJMS_ERR_CR_QUEUE_CONS.
Unable to create Queue consumer due to JMSException.
Please examine the log file to determine the problem.
 at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:620)
 at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:497)
 at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:342)
 at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:913)
 at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:862)
 at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:163)
 at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
 at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
 at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: weblogic.jms.common.JMSException: [JMSExceptions:045101]The destination name passed to createTopic or createQueue "jndiEmployeeDQ" is invalid. If the destination name does not contain a "/" character then it must be the name of a distributed destination that is available in the cluster to which the client is attached. If it does contain a "/" character then the string before the "/" must be the name of a JMSServer or a ".". The string after the "/" is the name of a the desired destination. If the "./" version of the string is used then any destination with the given name on the local WLS server will be returned.
 at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
 at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
 at weblogic.jms.client.JMSSession.createDestination(JMSSession.java:3192)
 at weblogic.jms.client.JMSSession.createQueue(JMSSession.java:2577)
 at weblogic.jms.client.WLSessionImpl.createQueue(WLSessionImpl.java:938)
 at oracle.tip.adapter.jms.JMS.JMSDestination.getQueue(JMSDestination.java:83)
 at oracle.tip.adapter.jms.JMS.JMSConnection.createConsumer(JMSConnection.java:605)
 ... 8 more
Has anyone encountered this problem before?
Damien

Could you connect to same destination using any other client (like java). I think issue is either in the queue deployment or in the connection pool configuration at your side. Make sure that queue is available (by connecting to same queue using any other client) and cross check you connection pool configuration.
Let us know the version of products you are using and connecting to.
Regards,
Anuj

JMS adapter IBM MQ Server integration with SSL

Hello,
We have a integration between PI and IBM Websphere MQ,normally we can able to do this with JMS adapter.
But MQ Server side is using SSL and they will send us a certificate, so we need to communicate JMS and MQ queue and JMS does not support SSL directly.
i have done some searches in sdn but i can't find a good guide or explained solve.
i will be very appriciated for any help or idea about this issue.
Our PI system: SAP PI 7.1 EHP1
Integration flow like this;
ERP -> PI -> IBM MQ Queue (SSL),
IBM MQ Queue (SSL) -> PI -> ERP

Hi all,
We have integrated PI and IBM Websphere MQ with JMS adapter and this is working any problems.
Now we want apply the note 1869690
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3138363936393026
and securize the interface.
We have SAP PI 7.1 EHP 1 SP12 , it's possible aply this note? or we need to develop adapter module?
Can you help us?
Thanks and regards

Jms adapter is very slow

hi all
I've got two bpel processes deployed: one is writing message into a queue (created in 10g Oracle DB) using jms adapter, second one is supposed to read message from the queue. It seems to work very slowly, bpel part is executed fast (everything is deployed on fast linux server) but reading from a queue is a bottleneck. It takes rougly 1 second to read a single message from the queue !!!!
I tried with and without connection pooling and I get the same results.
I also tried to read from the same queue from a standalone java application: it takes 50-150ms to read one message after obtaining connection.
My configuration:
As 10.1.3.1
adapter wsdl relevant part:
<binding name="Consume_Message_binding" type="tns:Consume_Message_ptt">
<pc:inbound_binding />
<operation name="Consume_Message">
<jca:operation
ActivationSpec="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec"
DestinationName="java:comp/resource/ASDBResource/Queues/LSP_INPUT_Q_BRIDGE"
UseMessageListener="false"
PayloadType="BytesMessage"
OpaqueSchema="true" >
</jca:operation>
</binding>
<service name="InboundJMS">
<port name="Consume_Message_pt" binding="tns:Consume_Message_binding">
<jca:address location="eis/Jms/JMSDBConnection" UIConnectionName="JMSDBConnection"
ManagedConnectionFactory="oracle.tip.adapter.jms.JmsManagedConnectionFactory"
mcf.ConnectionFactoryLocation="java:comp/resource/ASDBResource/QueueConnectionFactories/QCF"
mcf.IsTopic="false"
mcf.IsTransacted="true"
mcf.FactoryProperties=""
UIJmsProvider="OJMS" />
</port>
</service>
ASDBResource is configured in application.xml to point to a proper machine.
When I set useMessageListener to "true" I get even worse performance.
I found following text in adapters faq, maybe there is an option to change pooling interval ?
<The JMS API supports both synchronous or asynchronous communication for <message consumption. In the
<synchronous case, the consumer explicitly calls the receive() method on the <topic or queue. In the
<asynchronous case, the JMS client registers a MessageListener for the topic or <queue and the message is
<delivered by calling the listener’s onMessage() method. By default, the consumer <uses a polling method. The
<Adapter design-time is used for overriding the default behavior and can be used to <configure a message listener
<for receiving JMS messages in an asynchronous fashion.
cheers
Przemek

If speed is of essence, have you considered using the AQ adapter instead ? That should be faster when compared to the jms route, assuming you are going against Oracle AQs.

Platforms supported by JMS adapter

Similar Messages

Maybe you are looking for