OIC, Oracle SOA, OSB, Weblogic

The new version of SOA Suite PS6 is now available at Oracle eDelivery. The new features that introduced in 11.1.1.7 version are below:  BPEL / Infrastructure: Purge – Strategies for majority data removal – TRS/Truncate Support for tokens and global variables Idempotent setting at operation level Recovery tab – Abort and Cancel Certificate selection for dynamic partnerlinks Uniform Approach to Marking Stale Instances Business Rules: Rules translation support Usability improvements B2B / Healthcare: Simplified Installation New standards Performance Cross-Product Integration UI Enhancements Event Processing: Product artifact rename “Complex Event Processing” to “Event Processing” Solutions/Packaging Big Data Integration User Defined CQL Fault Handlers List-based Aggregations Support for Eclipse Indigo (3.7.2) Usability Performance Optimizations Business Activity Monitoring: ODI 11g Support BAM T2P Plugin IComma

Hi ALL, Today i want to share some thing very interesting thing about XSLT execution in weblogic server.. For XSLT, those DEV/TEST/UAT/PROD server references in source/target are not harmful as these will be treated as comments by the XML parser while doing the transformations at the run-time. But these commented lines should be required while opening that XSLT in transformation because, jdeveloper studio will get the source/target details from the commented lines only.

how to call a preference value in XSLT in SOA? Solution: Function to retrieve the preference : http://www.xenta.nl/blog/2009/10/28/oracle-soa-suite-11g-setting-and-getting-preferences/ Create a new xsl mapping and let the 'first' parameter be some messageType variable (for example the inputVariable, or some other variable you use for your main input). In the xslt add between the "<xsl:stylesheet>"-tag and the "<xsl:template match=".">"-tag something like  "<xsl:param name="myPref" />" Your xsl is ready to receive the extra input parameter. Now in your bpel process do something like this       <copy>         <from expression="ora:doXSLTransformForDoc('xsl/myxslt.xsl', $inputVariable.input, 'myPref', ora:getPreference(myPref))"/>         <to variable="myresult"/>       </copy>    or first assign ora:getPreference(myPre

We have a inbound file adapter. It will read the files from one source location. If inbound file adapter was down for some time. After some time it is up running, meanwhile list of files will be placed in inbound source folder. The requirement here is, the file adapter has to read the files in the order in which the files written. (means, in FIFO order) How to fulfill the requirement via file adapter. Solution: We can use the ListSorter File Adapter Configuration property to sort based on timestamp. Basically a dd the following property to the inbound JCA file: <property name="ListSorter" value="oracle.tip.adapter.file.inbound.listing.TimestampSorterAscending"/> <property name="SingleThreadModel" value="true"/> More info see section 4.2.6 in http://docs.oracle.com/cd/E23943_01/integration.1111/e10231/adptr_file.htm

I got a requirement in SOA 11.1.1.6--- From a webservice call to db insert XSLT,  i have 10 elements at source side and 11 elements at target side. From source to target first 10 mappings are done. Now requirement is, for the 11th element in target- we need pass a sequence number to the targeted database, means---(sequence number has to be generated for every execution of XSLT)  How to do the last point??? Solution:  We can pass the sequence number in the 11th element using oraext:sequence-next-val("Sequence name as a string", "Datasource as a string") function.

I wanted to share some information about difference between SOA 10g and 11g. JDeveloper 10g doesn’t need any manual installation of SOA extension. 10g is designed for SOA by default. When you create an application in 10g, these are created as standalone and independent of SOA tier unlike 11g. Projects are created inside applications which are tier specific like SOA (BPEL/ESB/Empty) or others. Unlike 11g, there are no composites here. There is direct BPEL built. The details that are mentioned in the composite.xml files in 11g, it is bpel.xml in 10g. All the policies and preferences would be going into bpel.xml instead of composite.xml When you create adapters, the details are stored in the wsdl file unlike the .jca file in 11g. While creating the connection to the server, you will need to make the connections for both integration and the application server one by one. The header properties of the adapters are taken from the header wsdl which is formed

Problem : Whenever we have a long running two-way OSB-DB API call...it takes much time to complete. It will show us the weblogic.socket.MaxMessageSizeExceededException in sbconsole debug console. Cause : weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '10000080' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3' Solution : 1. Go to servers--->protocols--->general--->max message size--->change the value to sufficient memory (Do this for both the admin and the osb/soa) Note: Do it for all the OSB/SOA nodes in the cluster 2. Go to servers--->configuration--->server start--->arguments--->-Dweblogic.MaxMessageSize = 20000000 3. Restart all the servers. Hope this will help you to resolve this issue.