Thursday, November 10, 2011

Oracle SOA Suite - Setting Timeouts for Receive activities.

Oracle SOA Suite - Setting Timeouts for Receive activities:

Oracle SOA Suite 11g introduced a new feature setting the timeout for receive activity.
We can specify timeout duration for partner callbacks using this property. This property can be used in Oracle SOA Suite 12c to set the timeout in receive activity.

Timeout Settings Relative from When the Activity is invoked:


You can specify a timeout setting relative from when the activity is invoked.
This type uses the bpelx:for attribute to specify a static value or an XPath expression that must evaluate to an XML schema type duration.


Timeout Settings as an Absolute Date Time:


You can specify a timeout setting as an absolute deadline for receive activities.
The expected expiration time for the bpelx:until attribute must be at least two seconds ahead of the current time. Otherwise, the timer scheduling is ignored and skipped, just as if the timer was never specified. The bpelx:until attribute specifies a static value or an XPath expression that must evaluate to an XML schema type datetime or date.

Read more »
Posted by at No comments:
Labels: ,

Wednesday, November 9, 2011

Oracle SOA Suite 10g to 11g Migration – Migrating XREF Runtime Data.

Oracle SOA Suite 10g to 11g Migration – Migrating XREF Runtime Data:


If you have Oracle SOA Suite 10g cross reference (XREF) runtime data in an Oracle database (oraesb.XREF_DATA) then the same needs to be migrated to Oracle SOA Suite 11g (SOAINFRA.XREF_DATA).

The utility is required, as the XREF database schema table (XREF_DATA) has changed for Oracle Fusion Middleware 11g.
We had around 12 million records in our 10g environment and used the utility 

Upgrade10gXrefTo11gXref.sql provided by oracle to migrate the data.
This utility is using the DBLINK to get the data from 10g database because of this the migration was taking more time and could not able to complete.

We have done some modification to the SQL utility based our requirement and we were able to migrate the data successfully within 9hrs of time.
Instead of using the DBLIINK, we have used the Oracle DataPump Utility to transfer the data from Oracle SOA 10g database to Oracle SOA 11g database schema(SOAINFRA –Where the 11g XREF data is available ) and used the local table in the utility script.

The steps to execute the script:

- Using Oracle DataPump Utility, transfer the data from the table oraesb.XREF_DATA of SOA 10g source database to SOA 11g destination database table SOAINFRA.XREF_DATA_MIGRATION (the schema where the 11g XREF data is available).
- Change the MDS location 'oramds: /apps/EAIMetaData/Xref/' in the script, location where the XREF meta data has stored, with your value.
- Log in to Oracle database that hosts the Oracle SOA 11g XREF data as the SOAINFRA user and execute the script.
@Upgrade10gXrefTo11gXref.sql

All the corrupted/duplicated data will be inserted into the table XREF_DATA_CORRUPTED.
Refer the script attached with this blog

Upgrade10gXrefTo11gXref.sql
Posted by at 2 comments:
Labels: ,

Sunday, November 6, 2011

Oracle SOA Suite - Abstract WSDL - Resolving the composite dependency issue during deployment and server restart.

Oracle SOA Suite - Abstract WSDL - Resolving the composite dependency issue during deployment and server restart:


Dependency order is not recorded in SOA Suite for composites. So, during server start-up, there might be multiple retries before all composites are loaded to the server if a wrong dependency order is followed by the server.
This does not necessarily mean the composites are not loaded at all, but server may end up trying to load a composite multiple times before it is finally succeeds after restart. This results in multiple errors in logs and also overall time taken for restart. E.g., as seen in the diagram below, if the server tries to load A before B and C are deployed then the composite loading fails. This can also happen during deployment time if there is a circular dependency between composites.


Solution to this problem is isolating design time and runtime dependencies. This can be done by moving WSDL dependencies to abstract WSDL’s. We can store the abstract copies of all such WSDL’s in MDS.
Consider the XML snippets below which can be found in composite.xml.
<reference name="SubmitOrderToCOMPASSRS" ui:wsdlLocation="http://eaidev2:8004/soa-infra/services/MEDIATOR/CSOM_SubmitOrderToCOMPASS/CSOM_SubmitOrderToCOMPASSRS.wsdl">

<binding.ws port="******" location="http://eaidev2:8004/soa-infra/services/MEDIATOR/CSOM_SubmitOrderToCOMPASS/CSOM.SubmitOrderToCOMPASSRS_ep?WSDL" soapVersion="1.1">


ui:wsdlLocation signifies design time and binding.ws stands for runtime.
So, we need to change the value in ui: wsdlLocation, so that it refers to MDS rather than the deployed component through http. The changed value should look something similar as below to point it to MDS.
oramds:/apps/EAIMetaData/Abstract/WSDL/MEDIATOR/CSOM_SubmitOrderToCOMPASS/CSOM_SubmitOrderToCOMPASSRS.wsdl
By following the approach, during compile time the compiler finds all the references it needs and the runtime engine does not bother about the abstract WSDL’s once it is loaded. So for both initial deployment and subsequent server restarts this approach helps in avoiding design time dependencies.
Read more »
Posted by at 23 comments:
Labels: ,

Friday, November 4, 2011

Oracle SOA Suite 11g – Enabling the Test button in EM Console for the Composites initiated by the Polling Adapters (MQ, DB).

Oracle SOA Suite 11g – Enabling the Test button in EM Console for the Composites initiated by the Polling Adapters (MQ, DB).


In 11g the Test button in EM Console for the Composites initiated by the Polling Adapters like DB and MQ (Components that are initiated by DB/MQ Pollers) are not enabled by default but in 10g it was enabled by default.


In some scenarios we may need to test these (Composite initiated by polling) composites manually from EM console instead of polling the data from target.
By following the below steps the test button in EM console can be enabled for the Composites initiated by Poller.
1. Open the Composite.xml design view in JDeveloper.
2. Drag and drop web service from service Adapters to the Exposed Services section of the Composite.xml

Read more »
Posted by at 1 comment:
Labels: ,

Wednesday, November 2, 2011

Oracle SOA Suite 11g - Common adf-config.xml to deploy all the composites to different environments through ANT.

Oracle SOA Suite 11g - Common adf-config.xml to deploy all the composites to different environments through ANT.


The common adf-config.xml file can be used to deploy all the composites instead of using the adf-config file from the individual composite applications.
The adf-config file configurations can be changed at runtime through ant script to deploy the composites to different environments.

By this approach, we can reduce the maintenance of individual adf-config files also by using the same adf-config file the composites can be deployed to different environments.

1. Copy.adf folder from any of the Composite application to the common location.


2. Change the contents of the adf-config.xml with below contents (change the file according to your requirement.)
<?xml version="1.0" encoding="windows-1252" standalone="no"?>
<adf-config xmlns="http://xmlns.oracle.com/adf/config" xmlns:adf="http://xmlns.oracle.com/adf/config/properties" xmlns:config="http://xmlns.oracle.com/bc4j/configuration" xmlns:sec="http://xmlns.oracle.com/adf/security/config">
<adf-adfm-config xmlns="http://xmlns.oracle.com/adfm/config">
<defaults useBindVarsForViewCriteriaLiterals="true"/>
<startup>
<amconfig-overrides>
<config:Database jbo.locking.mode="optimistic"/>
</amconfig-overrides>
</startup>
</adf-adfm-config>
<sec:adf-security-child xmlns="http://xmlns.oracle.com/adf/security/config">
</sec:adf-security-child>
<adf-mds-config xmlns="http://xmlns.oracle.com/adf/mds/config">
<mds-config xmlns="http://xmlns.oracle.com/mds/config">
<persistence-config>
<metadata-namespaces>
<namespace metadata-store-usage="mstore-usage_2" path="/apps/EAIMetaData"/>
<namespace metadata-store-usage="mstore-usage_3" path="/soa/shared"/>
</metadata-namespaces>
<metadata-store-usages>
<metadata-store-usage id="mstore-usage_2">
<metadata-store class-name="oracle.mds.persistence.stores.db.DBMetadataStore">
<property name="jdbc-userid" value="@db.user@"/>
<property name="jdbc-password" value="@db.password@"/>
<property name="jdbc-url" value="@db.url@"/>
<property name="partition-name" value="@partition@"/>
</metadata-store>
</metadata-store-usage>
<metadata-store-usage id="mstore-usage_3">
<metadata-store class-name="oracle.mds.persistence.stores.db.DBMetadataStore">
<property name="jdbc-userid" value="@db.user@"/>
<property name="jdbc-password" value="@db.password@"/>
<property name="jdbc-url" value="@db.url@"/>
<property name="partition-name" value="@partition@"/>
</metadata-store>
</metadata-store-usage>
</metadata-store-usages>
</persistence-config>
</mds-config>
</adf-mds-config>
</adf-config>
Read more »
Posted by at 2 comments:
Labels: ,
Subscribe to: Posts (Atom)