DBAdapter or JMS/AQ

Hi,
We are on SOA 11.1.1.3 and need some info.
Does using huge number of DBAdapters in composites affect on the performance, memory, cpu, db processes etc on the middleware and database. Actually we may end up with large numbr composites exceeding 200 or so each with atleast 6 or 7 DBAdapters most pooling and only some insert,select,update etc. in the end maybe close to above 700 DBAdapters. So wanted to check if using that many DBAdapters will have any adverse affect i.e. memory, performance, cpu etc. We only have 3 node cluster each with 12 GB RAM.
Is it better to use all DBAdapters or is it a good design to off load to JMS or AQ rather than doing pooling and only use where necessary. Wanted to make sure we start off with what will be a good way so we don't suffer in the end.
Again we have to pool on both SQL Server and Oracle Database so just a bit hestitant on DBAdpater approach so looking for some alternative which is good from maintainance, performance,memory etc. Any ideas.
Thanks

Your business requirement seem to be more of a use case for using an ETL implementations.
You might want to consider using ODI instead (http://www.oracle.com/technetwork/middleware/data-integrator/overview/index.html).
Thanks,
Patrick

Similar Messages

Invoke Error while inserting consumed JMS Topic msg in table thru DBadapter

Hi All,
To brief abt my requirement, I am integrating Peoplesoft HRMS module with Oracle SOA i.e.,
+
1. PS HRMS module will publish a JMS msg into a JMS Topic
2. I will consume the same msg using JMS adapter consume operation in my SOA project
3. The Payload(msg) is coming into RECEIVE activity and thru ASSIGN activity invoking the DB adapter to insert the msg into a table.
4. INVOKE activity is throwing the below error(along with the error, able to see the payload in INVOKE activity )
<part name="summary"> +
<summary>*Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'insert' failed due to: Mapping Not Found Exception. The mapping [EMPLID] for descriptor [class insert.Employee] could not be found. The input xml record had an element [Employee/EMPLID]. Most likely the wrong xml input variable (not matching the expected xsd) was passed to this invoke. Make sure that the input xml is valid relative to the xsd and that the mapping exists in the Mappings.xml. If an old version of the descriptor without this mapping has been loaded by the database adapter, you may need to bounce the app server. If the same descriptor is described in two separate Mappings.xml files, make sure both versions include this attribute/mapping. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. *</summary>
</part>
Please, provide some suggestions.
Regards,
Satya

Hi Satya,
Try replacing the Assign activity with a Transform acitivity.
Also please check the schema that comes of the DB adapter is having the similar sort of definition that you are getting in your input.
What I mean is to check for length of fields, type of the fields etc.
Thanks,
Deepak.
Edited by: DeepakDabbiru on Oct 23, 2012 3:29 AM

Having multiple service operations in a single JMS adapter best practice

Hi All,
I am using JDeveloper and SOA Suite 11.1.1.6. I need to read from multiple JMS Topics and transform and enhance the messages through the Mediator and then persist into Database.
My question is
What is the best practice to consume from multiple topics, Should I configure separate JMS adapter for each of the Topic destination
OR
have a single JMS adapter with multiple operations by manually changing the JMS adapter wsdl and jca file?
I find cannot have
Please suggest.
Thanks in advance
Edited by: user5108636 on 15/05/2013 11:36

Hi Vijay,
did you actually test this? When I finish creating a DBAdapter, there is a operation present. Then when I click edit again on the DBAdapter, and I create another select, when I finish only the first operation is gone, and I can only see the one I've created via the last edit.
I dont understand your reply. Can I have two operations, each one with select underneath, in the same adapter?
Edited by: user13604541 on Jan 30, 2012 11:19 AM

How to modify Fileadapter filename with val from JMS msg using xsl?

In my case I need to name the file based on information received in a JMS message.
I would like to receive an xml document from a JMS queue, the document will contain content as well as the name of a file to be saved off. I found references to something similar in the BPEL and ESB documentation for the file adapter by using "ehdr:setOutboundHeader(" as a means to set the outbound header value but I cannot find the mechanics of how to accomplish getting that set with a value that is selected from an incoming message in XSL code.
The examples shown indicate the creation of a pass through mechanism that would take a message from a request header and pass it along to the outbound header which is great but I need a snippet of code to get me through setting the outbound header with an element value that is sourced from the inbound message.
I also found an incomplete reference in a "Oracle SOA Suite Enterprise Server Bus" powerpoint presentation that indicates JMS custom properties support for "Property[@name="Country"]/@value" but no details were provided to assist further.
I would greatly appreciate any information you can provide.
Thank You,
John

Ok I was able to get fileadapter filenames modified.
First you cannot do this after a dbadapter query as that functionality seems to be broken. The best way to solve it for me was to simplify the problem, I started with placing the setoutbound header data after reading a simple file and ignoring the files content altogether. I do the set inside a match of the xslt using a constant value, again for simplicity. For the test just put in 'ateststring.txt' in the setoutbound header call, no need to select data from the document at this point; we will get to that. Now get that to work.
Once you have that working take a value from the incoming document and select it into a variable named myvariable then replace the 'ateststring.txt' with $myvariable. So basically its a three step process for the final solution. Select the data of interest from the document into a variable. add a select statement to make the method call just after that. Make the method call inside the select statement and prepend the variable name with the $ symbol.
So far I have only tested this file to file and file to ftp, I suspect that jmsadapter to file will work fine too. So the trick for me was to understand that if an incoming document is the result of a query that just wont do. My requirement was to take an input JMS request, use that to drive a query, take the data from the query and write it to a filename as defined in the JMS request. No matter what I did to set the frustrating fileadapter/ftpadapter filename in the header I was unable to do so. I used constant strings etc in every part of the document ( before select, inside select, outside select etc ). It wasnt until I went file to file that I was able to get this to work at all. And then not in the xslt header etc, it MUST be in an area of the document that resulted in a select match, which after review makes sense.
To work around the query to file issue, I place the results of the data query into a temporary filename%SEQ%.tmp, along with the query results I add the real filename inside the document. I have a file listener that listens for the filename using wildcards filename*.tmp, it takes the file reads it in, pulls the permanent filename from the incoming document, and sets that filename in the header using the steps worked out above by selecting the filename into myvariable.
You cannot ( to my knowlege ) store variables in ESB so I found I had to put them inside the documents to move the data around. When I am all done with the work through the routing service I strip out the variable data fields that I needed to carry along with the data.
I hope this saves someone else a bit of frustration!
John

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

Difference between EDN-DB and EDN-JMS implementation

Experts,
Looking for a difference between EDN-DB and EDN-JMS implementation. We have EDN implementation going on, where multiple source systems will be publishing business events. Events can be published using SOA Suite or JMS Bridge from AQ and MQ. In this scenario which implementation approach is suited better ?

Oracle Apps Adapter can be used for many other products other than E-Business Suite (JD Edwards E1, OTM, and others). The apps adapter was mainly used in ERP systems and was strong when you needed have added functionality other than just polling a db for a status / calling a stored procedure... It could connect out to other business services, xml gateways and so-on.
From a technical aspect / development perspective I always thought of that the Oracle Apps Adapter simplifies the development but, may is not flexible. The App Adapter's strength is the services that are difficult to integrate with (business services, xml gateway). If you need to hook in to these types of services, use the APPS adapter. (Again like it is named the "Apps Adapter" its for interacting w/ other applications to enable real-time processing / functionality.
That being said the dbAdapter can be very powerful but, like it is named is database focused (to poll some table to know when to kick off other logic and enable real-time functionality through database interaction.
Looking at the Oracle 12C Roadmap I had heard that there is more planned for the Oracle Apps Adapter moving forward, especially as Anuj said in the "Financial Apps" side of the isle at Oracle. Who knows what is real and what isn't though =]
Hope this helps!
-Luke

JMS-&DB Adapter are missing after Installation SOA 10.1.3 W2K with XE

I've observed that the JMS/DB adapter are missing under %OH%/j2ee/oc4j_soa/connectors and %OH%/j2ee/oc4j_soa/application-deployments/default. The installer produces errors for both with java.util.zip.ZipException: error in opening zip file
Checked Dbadapter.rar and JMSadapter.rar under %OH%/bpel/system/services/lib, they are empty. I have downloaded the Windows version from otn soa101310_win32_060807.0728.zip (565 MB (593,247,278 bytes)). Could you please advise?
Thanks

Hi Clemens,
I'm missing the adapters also. I did a 1st time, advanced installation of the 10.1.3.1 prod. release SOA Suite on suse linux. The installed adapter in both OC4J:home/default and OC4J:soa/default are:
* jmsrouter_ejb
* defaultWebApp
* jmsrouter_web
* OracleASjms
On a previous standard (with olite) install of the same SOA Suite version on Windows a got more (all?) adapters.
How can I fix the problem on the linux box?
Kind regards,
H
I dug a little further into the problem by roaming through the installation log files.
According the logfile the Deployment manager, whatever that may be is not running!?
logfile:
Result: 150
Running batch script by:
java admin_client.jar deployer:oc4j:opmn://asterix.harminge:6003/home -script /ora01/soaSuite_10.1.3.1/integration/esb/install/ant-tasks/esb_deployadapters.txt
Failed at "Could not get DeploymentManager".
This is typically the result of an invalid deployer URI format being supplied, the target server not being in a started state or incorrect authentication details being supplied.
Is it possible to rerun the "esb_deployadapter.txt" after the installation/configuration is complete?

BAM get data from ESB via JMS

Now, I only have ESB and BAM, not BPEL. This is want I have to do. I have to get data from Database and send the data to JMS, which BAM also connect to the JMS. How do I do that? Please provide me and example or any URL would be appreciated. I also try using DbAdapter, but ESB do not allow me to use DBAdapter as Inbound. I'm very new to SOA. Thanks

Hi,
Since I still have problems on this subject, I would like to share on how it progresses.
Currently I have a problem of timeout in step "Truncate XML Schema" with the URL that I mentioned above.
The exact error is the following : 7000 : null : com.sunopsis.sql.l: Oracle Data Integrator TimeOut : connection with URL [...]
The connection test is still OK.
I tried to increase the value in the user's pref but there's no change.

OSB: Cannot acquire data source error while using JCA DBAdapter in OSB

Hi All,
I've entered 'Cannot acquire data source' error while using JCA DBAdapter in OSB.
Error infor are as follows:
The invocation resulted in an error: Invoke JCA outbound service failed with application error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/DBAdapter1/RetrievePersonService [ RetrievePersonService_ptt::RetrievePersonServiceSelect(RetrievePersonServiceSelect_inputParameters,PersonTCollection) ] - WSIF JCA Execute of operation 'RetrievePersonServiceSelect' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by Exception [EclipseLink-7060] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Cannot acquire data source [jdbc/soademoDatabase].
Internal Exception: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.soademoDatabase'. Resolved 'jdbc'; remaining name 'soademoDatabase'.
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
JNDI Name for the Database pool: eis/DB/soademoDatabase
JNDI Name for the Data source: jdbc/soademoDatabase
I created a basic DBAdapter in JDeveloper, got the xsd file, wsdl file, .jca file and the topLink mapping file imported them into OSB project.
Then I used the .jca file to generate a business service, and tested, then the error occurs as described above.
Login info in RetrievePersonService-or-mappings.xml
<login xsi:type="database-login">
<platform-class>org.eclipse.persistence.platform.database.oracle.Oracle9Platform</platform-class>
<user-name></user-name>
<connection-url></connection-url>
</login>
jca file content are as follows:
<adapter-config name="RetrievePersonService" adapter="Database Adapter" wsdlLocation="RetrievePersonService.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<connection-factory location="eis/DB/soademoDatabase" UIConnectionName="Connection1" adapterRef=""/>
<endpoint-interaction portType="RetrievePersonService_ptt" operation="RetrievePersonServiceSelect">
<interaction-spec className="oracle.tip.adapter.db.DBReadInteractionSpec">
<property name="DescriptorName" value="RetrievePersonService.PersonT"/>
<property name="QueryName" value="RetrievePersonServiceSelect"/>
<property name="MappingsMetaDataURL" value="RetrievePersonService-or-mappings.xml"/>
<property name="ReturnSingleResultSet" value="false"/>
<property name="GetActiveUnitOfWork" value="false"/>
</interaction-spec>
</endpoint-interaction>
</adapter-config>
RetrievePersonService_db.wsdl are as follows:
<?xml version="1.0" encoding="UTF-8"?>
<WL5G3N0:definitions name="RetrievePersonService-concrete" targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/db/KnowledeMgmtSOAApplication/AdapterJDevProject/RetrievePersonService" xmlns:WL5G3N0="http://schemas.xmlsoap.org/wsdl/" xmlns:WL5G3N1="http://xmlns.oracle.com/pcbpel/adapter/db/KnowledeMgmtSOAApplication/AdapterJDevProject/RetrievePersonService" xmlns:WL5G3N2="http://schemas.xmlsoap.org/wsdl/soap/">
<WL5G3N0:import location="RetrievePersonService.wsdl" namespace="http://xmlns.oracle.com/pcbpel/adapter/db/KnowledeMgmtSOAApplication/AdapterJDevProject/RetrievePersonService"/>
<WL5G3N0:binding name="RetrievePersonService_ptt-binding" type="WL5G3N1:RetrievePersonService_ptt">
<WL5G3N2:binding style="document" transport="http://www.bea.com/transport/2007/05/jca"/>
<WL5G3N0:operation name="RetrievePersonServiceSelect">
<WL5G3N2:operation soapAction="RetrievePersonServiceSelect"/>
<WL5G3N0:input>
<WL5G3N2:body use="literal"/>
</WL5G3N0:input>
<WL5G3N0:output>
<WL5G3N2:body use="literal"/>
</WL5G3N0:output>
</WL5G3N0:operation>
</WL5G3N0:binding>
<WL5G3N0:service name="RetrievePersonService_ptt-bindingQSService">
<WL5G3N0:port binding="WL5G3N1:RetrievePersonService_ptt-binding" name="RetrievePersonService_ptt-bindingQSPort">
<WL5G3N2:address location="jca://eis/DB/soademoDatabase"/>
</WL5G3N0:port>
</WL5G3N0:service>
</WL5G3N0:definitions>
Any suggestion is appricated .
Thanks in advance!
Edited by: user11262117 on Jan 26, 2011 5:28 PM

Hi Anuj,
Thanks for your reply!
I found that the data source is registered on server soa_server1 as follows:
Binding Name: jdbc.soademoDatabase
Class: weblogic.jdbc.common.internal.RmiDataSource_1033_WLStub
Hash Code: 80328036
toString Results: ClusterableRemoteRef(8348400613458600489S:10.2.1.143:[8001,8001,-1,-1,-1,-1,-1]:base_domain:soa_server1 [8348400613458600489S:10.2.1.143:[8001,8001,-1,-1,-1,-1,-1]:base_domain:soa_server1/291])/291
Binding Name: jdbc.SOADataSource
Class: weblogic.jdbc.common.internal.RmiDataSource_1033_WLStub
Hash Code: 92966755
toString Results: ClusterableRemoteRef(8348400613458600489S:10.2.1.143:[8001,8001,-1,-1,-1,-1,-1]:base_domain:soa_server1 [8348400613458600489S:10.2.1.143:[8001,8001,-1,-1,-1,-1,-1]:base_domain:soa_server1/285])/285
I don't know how to determine which server the DBAdapter is targetted to.
But I found the following information:
Under Deoloyment->DBAdapter->Monitoring->Outbound Connection Pools
Outbound Connection Pool Server State Current Connections Created Connections
eis/DB/SOADemo AdminServer Running 1 1
eis/DB/SOADemo soa_server1 Running 1 1
eis/DB/soademoDatabase AdminServer Running 1 1
eis/DB/soademoDatabase soa_server1 Running 1 1
The DbAdapter is related to the following files:
C:\ Oracle\ Middleware\ home_11gR1\ Oracle_SOA1\ soa\ connectors\ DbAdapter. rar
C:\ Oracle\ Middleware\ home_11gR1\ Oracle_SOA1\ soa\ DBPlan\ Plan. xml
I unzipped DbAdapter.rar, opened weblogic-ra.xml and found that there's only one data source is registered:
<?xml version="1.0"?>
<weblogic-connector xmlns="http://www.bea.com/ns/weblogic/90">
<enable-global-access-to-classes>true</enable-global-access-to-classes>
<outbound-resource-adapter>
<default-connection-properties>
<pool-params>
<initial-capacity>1</initial-capacity>
<max-capacity>1000</max-capacity>
</pool-params>
<properties>
<property>
<name>usesNativeSequencing</name>
<value>true</value>
</property>
<property>
<name>sequencePreallocationSize</name>
<value>50</value>
</property>
<property>
<name>defaultNChar</name>
<value>false</value>
</property>
<property>
<name>usesBatchWriting</name>
<value>true</value>
</property>
<property>
<name>usesSkipLocking</name>
<value>true</value>
</property>
</properties>
          </default-connection-properties>
<connection-definition-group>
<connection-factory-interface>javax.resource.cci.ConnectionFactory</connection-factory-interface>
<connection-instance>
<jndi-name>eis/DB/SOADemo</jndi-name>
          <connection-properties>
               <properties>
               <property>
               <name>xADataSourceName</name>
               <value>jdbc/SOADataSource</value>
               </property>
               <property>
               <name>dataSourceName</name>
               <value></value>
               </property>
               <property>
               <name>platformClassName</name>
               <value>org.eclipse.persistence.platform.database.Oracle10Platform</value>
               </property>
               </properties>
          </connection-properties>
</connection-instance>
</connection-definition-group>
</outbound-resource-adapter>
</weblogic-connector>
Then I decided to use eis/DB/SOADemo for testing.
For JDeveloper project, after I deployed to weblogic server, it works fine.
But for OSB project referencing wsdl, jca and mapping file from JDeveloper project, still got the same error as follows:
BEA-380001: Invoke JCA outbound service failed with application error, exception:
com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/DBAdapterTest/DBReader [ DBReader_ptt::DBReaderSelect(DBReaderSelect_inputParameters,PersonTCollection) ] - WSIF JCA Execute of operation 'DBReaderSelect' failed due to: Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by Exception [EclipseLink-7060] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Cannot acquire data source [jdbc/SOADataSource].
Internal Exception: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.SOADataSource'. Resolved 'jdbc'; remaining name 'SOADataSource'.
; nested exception is:
BINDING.JCA-11622
Could not create/access the TopLink Session.
This session is used to connect to the datastore.
Caused by Exception [EclipseLink-7060] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Cannot acquire data source [jdbc/SOADataSource].
Internal Exception: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.SOADataSource'. Resolved 'jdbc'; remaining name 'SOADataSource'.
You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server. This exception is considered not retriable, likely due to a modelling mistake.
It almost drive me crazy!!:-(
What's the purpose of 'weblogic-ra.xml' under the folder of 'C:\Oracle\Middleware\home_11gR1\Oracle_OSB1\lib\external\adapters\META-INF'?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Setting the JMS Header from Payload

Hi Experts,
My requirement is to send the payment data coming from ECC to non sap system.Sender adapter is proxy and receiver is JMS.ECC will be sending the filename in one field and payload content as a string in another field.PI has to set the filename coming from ECC in JMS header property.What configuration changes should i need to make in JMS adapter to achieve it?
Converting the XML to string is possible in PI.But my question is converting the string XML data into XML fields is possible in SAP PI?If so how to do that?
Please provide your suggestion.
Regards,
Karthiga

Hi Karthiga,
The UDF is there in blog
DynamicConfiguration dynamicconfiguration = (DynamicConfiguration)param.get("DynamicConfiguration");
            DynamicConfigurationKey dynamicconfigurationkey = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/JMS", "DCJMSMessageProperty0");
            String s = dynamicconfiguration.get(dynamicconfigurationkey);
            CorrID.append(s);
Please let me know if you have any issue.
regards,
Harish

How to configure an Alert message if communicationChannel(JMS) stops

All,
Is there a way how to configure an alert when the communication channel stops.
<b>Scenario:</b>
In the path Runtime workbench->Component Monitoring->Adapter Engine->Communication Channel monitoring, if we see that a communication channel has stopped(RED traffic light as Status), then can we trigger an alert notification for same.
Currently we have alrerts configured for any message/s failure in the JMS Adapter Framework. So can we trigger simmilar alerts when a comm channel stops(for whatever reason).
Thanks in advance
RK

Hi Sreeram,
Thanks for the quick reply.
We have a scenario where we activate individual channels at a given time. So in this case, Adapter will always be in RED as all queues are never running in our scenario.
So we need an ALERT to be triggered for individual comm channels. Is theer any way that you can think of ?
Thanks and regards
RK

JDBC connection pool failures when used by JMS stores

          We are using WebLogic 6.1 sp2. We defined a separate connection pool for use by
          a JMS Store.
          <JDBCConnectionPool Name="sybaseJMSPool"
          Targets="cluster00"
          InitialCapacity="2"
          MaxCapacity="10"
          DriverName="com.sybase.jdbc2.jdbc.SybDriver"
          Properties="[email protected]@;[email protected]@;charset=utf8"
          URL="jdbc:sybase:Tds:@jms.db.host@/@jms.db.name@"/>
          (note that the @xxx@ string are replaced by actual values).
          We are using Sybase Jconnect 5.5 to a Sybase ASE 12.5 database.
          We deployed this configuration on a number of environments (testing, staging,
          ..). The actual hardware and network configuration is different for the different
          system, but the WebLogic domain stays the same regarding this issue.
          On the test system we frequently get the following exceptions:
          <Aug 13, 2002 1:56:04 PM CEST> <Alert> <JMS> <www00-test> <node00>
          <ExecuteThread: '6' for queue: 'JMS.TimerClientPool'> <> <> <040048>
          <JMSServer "JMSServer00", store failure while writing message for topic
          OrderChangeTopic, java.io.IOException: JMS JDBC store, connection pool =
          <sybaseJMSPool>, prefix = <JMS00>: write failed
          java.sql.SQLException: JZ006: Caught IOException:
          com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0: Connection is already
          closed.
          at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead
          (ErrorMessage.java:715)
          at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3124)
          at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1412)
          at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1341)
          at com.sybase.jdbc2.jdbc.SybStatement.doCancel(SybStatement.java:564)
          at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1672)
          at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate
          (SybStatement.java:1625)
          at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate
          (SybPreparedStatement.java:91)
          at com.p6spy.engine.logging.P6LogPreparedStatement.executeUpdate
          (P6LogPreparedStatement.java:179)
          at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:293)
          at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1246)
          at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
          at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          .>
          java.io.IOException: JMS JDBC store, connection pool = <sybaseJMSPool>, prefix
          = <JMS00>: write failed
          java.sql.SQLException: JZ006: Caught IOException:
          com.sybase.jdbc2.jdbc.SybConnectionDeadException: JZ0C0: Connection is already
          closed.
          at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead
          (ErrorMessage.java:715)
          at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3124)
          at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1412)
          at com.sybase.jdbc2.tds.Tds.cancel(Tds.java:1341)
          at com.sybase.jdbc2.jdbc.SybStatement.doCancel(SybStatement.java:564)
          at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1672)
          at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate
          (SybStatement.java:1625)
          at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate
          (SybPreparedStatement.java:91)
          at com.p6spy.engine.logging.P6LogPreparedStatement.executeUpdate
          (P6LogPreparedStatement.java:179)
          at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:293)
          at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1246)
          at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
          at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          at weblogic.jms.store.JDBCIOStream.throwIOException
          (JDBCIOStream.java:1213)
          at weblogic.jms.store.JDBCIOStream.write(JDBCIOStream.java:1256)
          at weblogic.jms.store.StoreRequest.doTheIO(StoreRequest.java:250)
          at weblogic.jms.store.JMSStore.execute(JMSStore.java:182)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          Before that this message appeared:
          <Aug 13, 2002 11:31:16 AM CEST> <Error> <ConnectionManager> <www00-test>
          <node00> <ExecuteThread: '26' for queue: 'default'> <> <> <000000>
          <Closing: 'weblogic.rjvm.t3.T3JVMConnection@795af6' because of: 'Server
          received a message over an uninitialized connection: 'JVMMessage from: 'null'
          to: '-4555218188801970213S:192.168.13.1:[7001,7001,7002,7002,7001,7002,-
          1]:ADIS:node00' cmd: 'CMD_REQUEST', QOS: '101', responseId: '1',
          invokableId: '287', flags: 'JVMIDs Not Sent, TX Context Not Sent', abbrev
          offset: '34'''>
          This problem did not occur on another system which was used during a 2 day stress
          testing session.
          It seems that the problem occurs after a period in which no user request where
          made. The user requests trigger EJB's that start sending JMS messages.
          When the problem occurs, the JMS messaging systems seems to lock up as no messages
          are received anymore by the different listeners (MDBs).
          Undeploying and redeploying the JBDC connection pool solves the problem. This
          solution is unacceptable in case of a production system.
          A similarly defined connection pool, which is used by the EJBs to make database
          connection, does not manifest this problem.
          <JDBCConnectionPool Name="sybasePool"
          Targets="cluster00"
          InitialCapacity="10"
          CapacityIncrement="5"
          MaxCapacity="50"
          PreparedStatementCacheSize="150"
          DriverName="com.sybase.jdbc2.jdbc.SybDriver"
          Properties="[email protected]@;[email protected]@;JCONNECT_VERSION=6;charset=utf8"
          URL="jdbc:sybase:Tds:@db.host@/@db.name@"/>
          The JDBC connection pool is used as follows by the JDBC store
          <JMSJDBCStore ConnectionPool="sybaseJMSPool" Name="JDBCStore00" PrefixName="JMS00"/>
          <JMSServer Name="JMSServer00" Store="JDBCStore00" Targets="node00">
          <JMSTopic JNDIName="ADIS.JMSError" JNDINameReplicated="false" Name="ErrorTopic"/>
          <JMSTopic JNDIName="ADIS.Status"
          Name="StatusTopic" RedeliveryDelayOverride="300000"/>
          <JMSTopic JNDIName="ADIS.OrderChange" JNDINameReplicated="false"
          Name="OrderChangeTopic" RedeliveryLimit="3"/>
          </JMSServer>
          Turning on the "Test Reserved Connection" with a appropriate test table does not
          help.
          Some sources on the internet tell us that JZ0C0 errors in the Jconnect driver
          can be related to network problems. Nevertheless the connection pool should be
          able to cope with this.
          Can you provide any solution for this ? Or give us hints what can cause the problem


Zhenhao Qi wrote:
thanks! Joe.
The SQL statement itself can no longer be simplified, the long excuation time is due to the database size and complicated Select criteria. I can easily reproduce the problem by using this SQL. I tried "BEA's Oracle driver (Type 4): Version 8.1.7,9.0.1,9.2.0". the question can be dissect into 2 pieces:
1) why the jdbc connection (using oracle.jdbc.OracleDriver) won't return anything if the SQL execution time > 5min, that is probably the Oracle's problem
2) why the occupied connection pool won't release even I set "Statementtimeout=600", this is Weblogic's problem.
ZhenhaoHi. Yes, (1) is oracle's problem. (2) may also be. The JDBC spec has very few
allowances for one thread to interrupt a second thread's JDBC call. If we
transmit your timeout request by calling setQueryTimeout() on the oracle
statement, and if you have a weblogic-controlled transaction we call
Statement.cancel() on any ongoing statement, we end up relying on whether
the Oracle driver implements and responds to those calls.
Are you doing weblogic-controlled transactions? Are you/can you
call Statement.setQueryTimeout() on your statements, or are these
generated JDBC queries?
If you can duplicate the problem using the weblogic.jdbc.oracle.OracleDriver
we have some other debug avenues. This would be good even if you really
want to use the thin driver, because we will do the same JDBC calls to
either driver, and the debug would prove (if) we set up a query timeout
and if we call cancel(). If we do, then we can know that it is the Oracle
driver failing in these regards.
Joe

Not all JMS consumers are created equal

Hi,
I am experiencing a very strange problem with weblogic 9.2 JMS.
I am using JMS as flow control in an application that allows our users to import data into our application.
the data to be imported varies in size from 100's of records to many hundred thousands of records.
JMS feed a MDB that takes the request and imports the data. The DD allows to 10 concurrent MDB's to service the requests.
The problem arises when the 11'th and 12th request comes in. Instead of waiting for the first availibe MDB to service the requests they seems to be put into the queue of the MDB that was started first. If this MDB is in the process of importing a very large file request 11 and 12 will sit and wait until the large one is done even though there are other MDB's that are idle.
I am hoping that there is an easy fix for this, but for the life of me, I cant seem to find it.
The DD for the MDB looks as follows
<weblogic-enterprise-bean>
<ejb-name>RuleEngineMDB</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>10</max-beans-in-free-pool>
<initial-beans-in-free-pool>10</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>com.company.product.RuleEngineRequestQueue</destination-jndi-name>
</message-driven-descriptor>
</weblogic-enterprise-bean>
the queue is defined in Weblog as
<queue name="RuleEngineReque
stQueue">
<sub-deployment-name>MyJMSServer</sub-deployment-name>
<delivery-params-overrides>
<delivery-mode>Non-Persistent</delivery-mode>
</delivery-params-overrides>
<message-logging-params>
<message-logging-enabled>true</message-logging-enabled>
<message-logging-format>%header%,%properties%,%body%</message-logging-format>
</message-logging-params>
<jndi-name>com.company.product.RuleEngineRequestQueue</jndi-name>
</queue>
regards,
Lars Hansson
CTO Compost Marketing AB.

A little more detail: You will need to configure and target a custom conection factory with "message maximum" set to 1 (the default is 10), and then modify the MDB descriptor to reference the JNDI name of the custom connection factory. The connection factory should be targeted to the entire cluster, and must be targeted to the same cluster that hosts distributed queue. If the MDB is transactional, ensure that that the custom connection factory is also "xa enabled".
Edited by: TomB on Mar 2, 2010 2:44 PM

JMS connection from SAP PI to Oracle AQ via JNDI...

Hi,
I am currently working on a project that requires connections between PI and Oracle AQ. It was advised that we shoule use PI JMS adpater with JNDI driver. However, it seems that not many people have tried this approach.
Has anyone had similar solutions in production ? How repliable it is ?
Your help is very much appreciated
Tim

Hi Tim,
We implemented a similar scenario and now itu2019s still working.
You have to configure a JNDI connection, but not directly with the Oracle AQ. The Oracle AQ are just queues, and you need a JMS provider in order to establish the connection with these queues. The solution we implemented was:
1. Configure one OC4J server as JMS provider for the Oracle AQ queues.
2. Configure JMS communication channels in SAP PI to establish the connection with the OC4J server.
Maybe you can use a different and newer JMS provider, as BEA Weblogic or SAP WAS (I donu2019t know if itu2019s possible).
We implement the scenario in SAP PI 7.0, and with this version we had a problem: When the communication between JMS adapter and the queues was broken (the DDBB fell down for example), the channel failed, itu2019s normal. But when the DDBB was already running the channel stayed in an error state, and we had to restart the channel manually. The response of SAP to this issue was that the channel behavior was correct because the connection failed.
But this problem occurred rarely, maybe once a month. The solution is very reliable, we exchange a lot of message with this solution, and support messages of any size with an excellent performance.
Best Regards,
Roberto

Using socket and JMS protocol in the same logic for OSB

Hi frnds,
In my organization...the only communication protocol used is "socket" protocol. However, I want to use JMS protocol to process incoming messages. Can somebody help me figuring out how to go about it.
Using some nice OSB blogs, I am able to create the JMS connection factory and JMS queues in weblogic. And that works fine when I select the communication protocol as JMS while creating the BS and PS.
What should be my message flow when the communication protocol used is "socket" for both BS and PS.
salil

Hi,
Make the BS as JMS and the PS as socket, in the PS's flow do a route for the BS... Then if an external call is made to the PS via socket, it will send a messages to a JMS queue...
Hope this helps...
Cheers,
Vlad

DBAdapter or JMS/AQ

Similar Messages

Maybe you are looking for