File Adapter Vs JMS Adapter ?

Hi,
We are planning to do some data transfers from some system A to a system B.
We don't have direct access to A's database, but we do have DB access to B.
We have two options, either get A's data into a topic, and use a combination of JMS and DB adapter to persist data into B.
Or, get A's data in a File and use a combination of File & DB adapter @ B.
So, which is a better solution from design and performance perspective ?
I think it depends manily on debating which is a better technology : File i/o or JMS ?
Would really appreciate if somebody could share there experiences/thoughts.

I agree with Marc.
One more thing to take into account: use of a JMS queue / topic may be regarded as more proper event driven processing than file polling.
But this argument may be meaningless if you do not have an eventhandling mechanism in your database and must revert to database batch processing, e.g. using dbms_job.

Similar Messages

Same file name using JMS adapter on sender side.

Hi Friends,
I got a requirement to capture file name using JMS adapter on the sender side.
Can some one help me in resolving this issue.
Regards,
Jeevan.

Hi ,
You can use Dynamic Configuration in mapping.
Create a UDF with input as file name and copy/paste this code
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
//conf.removeAll();
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
//String filename= conf.get(key);
conf.put(key, fileName);
key= null;
return fileName;
Thanks.

Difference between AQ Adapter and JMS Adapter

Hi All,
i am very new to SOA. let me know the difference between AQ Adapter and JMS Adapter.
thanks
Hari

Please go thru the bellow link
http://www.mscd.edu/~ittsdba/oradoc817/ois.817/a83729/adois07.htm#408020
Krishna

How to get the incoming file name using JMS adapter and SOAP adapter

Hi Everybody,
   In one of my interface i need to get the file name of incoming flat file using JMS adapter at sender side. and then i am using xslt to convert it to IDOC and then posting to SAP IDOC.
my incoming filname are in this form price<DateTimestamp>.txt. when i do the tranformation this incoming file name should be part of one element in the IDOC which i am posting.
EX:
<IDOC
<REF>price<DateTimestamp>.txt</REF>
</IDOC>
Hope it is clear to everybody. I need your suggestion how i can capture this incoming file name and send it as part of IDOC.
Thanks
raj

If they are passing it in message id or correlation id,
you can access it using
<xsl:variable name="dynamic-conf"
        select="map:get($inputparam, 'DynamicConfiguration')" />
    <xsl:variable name="dynamic-key"
        select="key:create('http://sap.com/xi/XI/System/JMS', 'DCJMSMessageID/ DCJMSCorrelationID')" />
    <xsl:variable name="dynamic-value"
        select="dyn:get($dynamic-conf, $dynamic-key)" />
Check this:
http://help.sap.com/saphelp_nw70/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
Thanks,
Beena.

Can we use 2 queue File in same JMS adapter

I am doing a scenario where 2 queues( Queue1file and Queue2file) are coming from MQ series but in the receiver end both are processing one after another or one only at a time. Can I achieve this using a single JMS adapter or can you suggest any other possible way?

The second submit is within an elsif so both programs will never get fired.
It will be either first or the second.
Also check if the program is getting launched but some other issues are preventing email. Try to submit some other program in the ELSE part.
Sandeep Gandhi

J2SE Adapter Engine / JMS Adapter

We need to connect to MQ Series 5.3 (Websphere MQ) from the XI (3.0 SP16) box.
1)Is J2SE adapter engine needs to be enabled/configured in order to use JMS Adapter? Cant we use J2EE JMSAdapter instead of J2SE JMS Adapter?
2) Where can I download the JMS Adapter libraries, for installation?
Ours is unix-based installation.
I have gone thru the thread
Installation and then Configuration of Plain J2se Adapter Engine
and the SAP Note: 747601 that talks about J2EE JMSAdapter MQSeries libraries.
TIA,
Steve

Hi Steve,
Check these ~
http://help.sap.com/saphelp_nw04/helpdata/en/6f/246b3de666930fe10000000a114084/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/03fd85cc-0201-0010-8ca4-a32a119a582d
J2Se adapter
Installation and then Configuration of Plain J2se Adapter Engine
Hope this helps,
Regards,
Moorthy

ORABPEL-12141 JMS Adapter

BPEL 10.1.2.0.2 Deployed on OAS on Linux OS.
Trying to use a BPEL Process which is trying to Connect to JMS on Weblogic Server but getting error as below in the domain.log
Added the weblogic.jar in the application.xml under integration/orabpel/system/appserver/oc4j/j2ee/home/config/application.xml
Entry added : <library path="/home/bpel/weblogic/server/lib/weblogic.jar"/>
XML file entry for JMS Adapter in BPEL :-
<connector-factory location="eis/jms/topic/rdh/Notification" connector-name="Jms Adapter">
<config-property name="connectionFactoryLocation" value="oracle.enterprise.crm.rdh.jms.connection.factory"/>
<config-property name="factoryProperties" value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://MYMACHINE:7050"/>
<config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
<config-property name="isTopic" value="true"/>
<config-property name="isTransacted" value="false"/>
<config-property name="username" value=""/>
<config-property name="password" value=""/>
</connector-factory>
Portion of Domain.log file :-
<2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: JNDI Naming exception when looking up oracle.enterprise.crm.rdh.jms.connection.factory: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
<2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: Will now try to determine if the 'ConnectionFactoryLocation' oracle.enterprise.crm.rdh.jms.connection.factory is a loadable Java class. If so, the above exception can be ignored.
<2007-08-17 03:25:29,148> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> Error while creating managed connection:
<2007-08-17 03:25:29,150> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound>
ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor oracle.enterprise.crm.rdh.jms.connection.factory neither through JNDI nor instantiate it as a Java class
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:206)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getTopicConnectionFactory(JMSConnectionFactoryFactory.java:109)
at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:123)
at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:107)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:365)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:356)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:319)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:101)
at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:94)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:201)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:158)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:115)
at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:113)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
at java.lang.Thread.run(Thread.java:534)
Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.java:186)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:133)
... 16 more
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
at com.evermind.naming.ContextClassLoader.findClass(ContextClassLoader.java:318)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:143)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.evermind.server.ApplicationContextClassLoader.findClass(ApplicationContextClassLoader.java:19)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
... 21 more

BPEL 10.1.2.0.2 Deployed on OAS on Linux OS.
Trying to use a BPEL Process which is trying to Connect to JMS on Weblogic Server but getting error as below in the domain.log
Added the weblogic.jar in the application.xml under integration/orabpel/system/appserver/oc4j/j2ee/home/config/application.xml
Entry added : <library path="/home/bpel/weblogic/server/lib/weblogic.jar"/>
XML file entry for JMS Adapter in BPEL :-
<connector-factory location="eis/jms/topic/rdh/Notification" connector-name="Jms Adapter">
<config-property name="connectionFactoryLocation" value="oracle.enterprise.crm.rdh.jms.connection.factory"/>
<config-property name="factoryProperties" value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://MYMACHINE:7050"/>
<config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
<config-property name="isTopic" value="true"/>
<config-property name="isTransacted" value="false"/>
<config-property name="username" value=""/>
<config-property name="password" value=""/>
</connector-factory>
Portion of Domain.log file :-
<2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: JNDI Naming exception when looking up oracle.enterprise.crm.rdh.jms.connection.factory: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
<2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: Will now try to determine if the 'ConnectionFactoryLocation' oracle.enterprise.crm.rdh.jms.connection.factory is a loadable Java class. If so, the above exception can be ignored.
<2007-08-17 03:25:29,148> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> Error while creating managed connection:
<2007-08-17 03:25:29,150> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound>
ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor oracle.enterprise.crm.rdh.jms.connection.factory neither through JNDI nor instantiate it as a Java class
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:206)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getTopicConnectionFactory(JMSConnectionFactoryFactory.java:109)
at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:123)
at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:107)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:365)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:356)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:319)
at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:101)
at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:94)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:201)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:158)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:115)
at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:113)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
at java.lang.Thread.run(Thread.java:534)
Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.java:186)
at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:133)
... 16 more
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
at com.evermind.naming.ContextClassLoader.findClass(ContextClassLoader.java:318)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:143)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.evermind.server.ApplicationContextClassLoader.findClass(ApplicationContextClassLoader.java:19)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
... 21 more

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

Sender JMS Adapter: Problem in Recordst

Hi All.
I am using Sender JMS Adapter along with content conversion.
I have put in Parameter:
Plain2XMLService xml.ignoreRecordsetName true
still the Inbound payload in SXI_MONITOR has Node Recordset, which should not be the case.
Please advice, does this ignoreRecordsetName works in JMS adapter, if Yes does it works same way as in File Adapter content conversion?
Thanks in Advance

Hi Pravesh,
Check this file on Sender JMS adapter if it helps you in anyway;
http://help.sap.com/saphelp_nw04s/helpdata/en/ca/e7673c86d19b35e10000000a11402f/frameset.htm
Also check this:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50061bd9-e56e-2910-3495-c5faa652b710
Regards,
Subhasha Ranjan

Complex XML to Plain in JMS adapter "Content conversion module"

Hi!
I have read the document on "How To use the content conversion module with XI3.0 J2EE JMS Adapter", and it says only SimpleXML can be converted in the receiver channel.
I had hoped for a solution at least as good as in the File/ftp adapter, where complex XML can be transformed to files.
Are there plans to include complex XML conversion in the JMS adapter?
I can not use the file adapter as I need to change the file name and destination, and that can not be done by adding own module to its single module.
Any idea how I can achieve what I want?
To only way I can find, is to create a file using the file/ftp adapter, and then pick it up again and treat all the lines as the same structure (one row = one xml field). Then output this new xml message to file, using the JMS adapter and add any modules with name and destination determination.
Appreciate any help!
Regards,
Oeystein Emhjellen

Hello,
Have you tried to use an XSLT mapping within the IE?
I have, at one customer site, created a XSLT message mapping which converts the XML to a fixed length ASCII file format. I than added the XSLT message mapping as a second mapping step on the interface mapping.
In this case I was able to publish a fairly complex fixed length file format to MQ Series via the JMS adapter.
/Johan

JMS Adapter Tuning in Oracle 10G SOA suite - Fixing the Errors

Hi All,
We are getting an error in Production environment while a BPEL process producing (enqueue) a message to a JMS queue by using JMS adapter. (partener link)
The error is as follows.
Adapter Framework unable to create outbound JCA connection.
file:/sw/appnew/product/SOA/10.1.3/bpel/domains/default/tmp/.bpel_CurrenListJMSProducer_1.0_4ec528ec93a8a6ff0278fab9701dcc71.tmp/CurrenListJMSProducerV1.wsdl [ Produce_Message_ptt::Produce_Message(OutputParameters) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: oracle.j2ee.connector.proxy.ProxyInterceptException: javax.resource.ResourceException: RollbackException: Transaction has been marked for rollback: null [Caused by: RollbackException: Transaction has been marked for rollback: null]
Please note that we are not getting this error every time, few BPEL instances are getting this error, around 3 out of 10 instances.
We are using Orcacle 10G SOA suite.
The BPEL process will take the messages from Oracle Apps adapter and send to the JMS queue, where we are getting error.
I can see in the BPEL.xml the "retryInterval" property set to '60' for both partner links (Apps adapter and JMS adapter).
But not set any other values. So,these values may be default.
We need to fix this issue soon.
I am requesting you all the Experts and Gurus, please let me know what can be done to fix this issue.
Thanks a lot in advance,
John.

Hi All,.
Is there any work around for the above issue?
I tried all the below JMS tunings, but not no improvement.
            <property name="useJCAConnectionPool">true</property>
            <property name="maxSizeJCAConnectionPool">500</property>
            <property name="retryMaxCount">10</property>
            <property name="retryInterval">60</property>
Please let
me know if any other logs or any other information is required in order to analyse the issue.
Thanks,
John

OCEP JMS Adapter implement InboundMessageConverter issue

Hello,
I'm new to OCEP. I have a JMS adapter receiving Weblogic JMS message. JMS Message is a TextMessage, so the default MapMessage can't convert it. I need to write my own converter which implement InboundMessageConvert. Eclipse compiles just fine, but when deploying into a runtime OCEP environment, I get an error saying that my custom converter class does not implement InboundMessageConverter which I did. Did anyone encounter this issue and how to get around it?
I also tried the sample code provided in Developer Guide and it doesn't work. My code bellow is a sample to by pass the deployment issue..
package com.converter;
import com.bea.wlevs.adapters.jms.api.InboundMessageConverter;
import com.bea.wlevs.adapters.jms.api.MessageConverterException;
import javax.jms.JMSException;
import javax.jms.Message;
import java.util.List;
public class MyMessageConverter
implements InboundMessageConverter
public MyMessageConverter(){
super();
public List convert(Message message) throws MessageConverterException, JMSException
return null;
--- error message when deploy to runtime environment ---
<Mar 22, 2010 10:30:57 AM PDT> <Error> <Deployment> <BEA-2045010> <The application context "FilteringEvent" could not be started: org.springframework.beans.FatalBeanException: Error in context lifecycle initialization; nested exception is java.lang.IllegalArgumentException: converter-bean com.converter.MyMessageConverter does not implement InboundMessageConverter
org.springframework.beans.FatalBeanException: Error in context lifecycle initialization; nested exception is java.lang.IllegalArgumentException: converter-bean com.converter.MyMessageConverter does not implement InboundMessageConverter
at com.bea.wlevs.spring.ApplicationContextLifecycle.onApplicationEvent(ApplicationContextLifecycle.java:136)
at org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78)
at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76)
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274)
at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736)
at org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235)
at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358)
at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:136)
at org.springframework.scheduling.commonj.DelegatingWork.run(DelegatingWork.java:61)
at weblogic.work.commonj.CommonjWorkManagerImpl$WorkWithListener.run(CommonjWorkManagerImpl.java:196)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Hi,
I have included the following two lines into the Manifest file, but this action has not fixed the problem:
com.bea.wlevs.adapters.jms;version="11.1.1.4_0",
com.bea.wlevs.adapters.jms.api;version="11.1.1.4_0"
My EPN file is as shown:
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:osgi="http://www.springframework.org/schema/osgi"
xmlns:wlevs="http://www.bea.com/ns/wlevs/spring"
xmlns:jdbc="http://www.oracle.com/ns/ocep/jdbc"
xmlns:spatial="http://www.oracle.com/ns/ocep/spatial"
xmlns:application="http://www.bea.com/ns/wlevs/config/application"
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/osgi
http://www.springframework.org/schema/osgi/spring-osgi.xsd
http://www.bea.com/ns/wlevs/spring
http://www.bea.com/ns/wlevs/spring/spring-wlevs-v11_1_1_3.xsd
http://www.oracle.com/ns/ocep/jdbc
http://www.oracle.com/ns/ocep/jdbc/ocep-jdbc.xsd
http://www.oracle.com/ns/ocep/spatial
http://www.oracle.com/ns/ocep/spatial/ocep-spatial.xsd
http://www.bea.com/ns/wlevs/config/application
http://www.bea.com/ns/wlevs/config/application/wlevs_application_config.xsd">
     <bean id="myConverter" class="com.bea.wlevs.adapter.example.jmsclient.JMSClient"/>
     <wlevs:adapter id="jmsInbound" provider="jms-inbound">
          <wlevs:instance-property name="converterBean" ref="myConverter"/>
     </wlevs:adapter>
     <application:jms-adapter>
<application:name>jmsInbound</application:name>
<application:jndi-provider-url>t3://localhost:9002</application:jndi-provider-url>
<application:destination-jndi-name>Queue1</application:destination-jndi-name>
<application:user>wlevs</application:user>
<application:password>123456</application:password>
<application:work-manager>JettyWorkManager</application:work-manager>
<application:concurrent-consumers>1</application:concurrent-consumers>
<application:session-transacted>false</application:session-transacted>
</application:jms-adapter>
<wlevs:event-type-repository>
The error showned by Eclipse is:
Multiple annotations found at this line:
     - cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'application:jms-adapter'.
     - schema_reference.4: Failed to read schema document 'http://www.bea.com/ns/wlevs/config/application/
     wlevs_application_config.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the
     document is not <xsd:schema>.
Thanks!
Edited by: 899693 on 15-dic-2011 2:48

URGENT: JMS Adapter With BPEL: Reply Only Scenario

Gurus,
I have the following scenario to be implemented:
1) BPEL Process A invokes an Async web-service (on some other SOA)
2) Process A then does some processing.
3) Then, process A waits for a reply message. The reply is sent in a JMS queue by the async Webservice.
4) I have an intermediate receive activity within the same BPEL process A that connects to the JMS Adapter. JMS Adapter is set up to consume messages from the queue.
I see messages pending in the queue but my receive doesn't continue.
Thanks-
Ashish

Hello,
There are interoperability issues between the Mid-tier and the RDBMS at present because the the mid-tier is using older version of the AQ jar files. At present the mid-tier is based on 10.1.0.5 and the backend will be whatever the backend is. Your issue sounds like a NLS issue given that bytes are fine but text is not. The characterset of the database will probably be important in this situation. So you check if the issue reproduces with different charactersets if possible. What characterset are you using and what is the Payload that the queue table is built on?
I would also suggest you try and build a standalone java application which reproduces the problem. You could most likely achieve this by creating a 10.1.0.5 RDBMS home and using the jar files from that install and then run it against your database to see if it reproduces the issue.
Anything that you can do to break down the problem will help Oracle Support identify what the issue is.
Thanks
Peter

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 Fail - Receiver channel. Details: Receive timed out

Its an IDOC to JMS scenario. IDOC gets processed through the pipeline in XI successfully, can see the checkered flag.
However in Adapter monitoring, JMS adapter is in red.
The error text against the Communication Channel is "Receiver channel. Details: Receive timed out".
I am trying to connect to the JMS queue provided by a third party on port 1100 ( as configured in JMS adapter).My initial analysis is to check if the port is open on the third party's firewall( Need to get the response back from them yet).
However i would like to know, if there is something else that i should look into?

Following are the error messages in RWB audit log for the message sent.
Exception caught by adapter framework: The JMS channel with channel ID 3f307d6854683859b39f978a43e88872 is errornous. Details:Receive timed out
Error Delivery of the message to the application using connection AFW failed, due to: The JMS channel with channel ID 3f307d6854683859b39f978a43e88872 is errornous. Details:Receive timed out.
what might be the problem?

File Adapter Vs JMS Adapter ?

Similar Messages

Maybe you are looking for