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>

Oracle SOA Suite 10g to 11g Migration - Unable to access the following endpoint : REPLACE_WITH_ACTUAL_URL

Unable to access the following endpoint : REPLACE_WITH_ACTUAL_URL:

The invocation of the synchronous web service from the composite has failed with the following error after migrating the code to Oracle SOA Suite 11g.

"Unable to access the following endpoint : REPLACE_WITH_ACTUAL_URL"

After a long struggle ,we have identified the issue .The issue was with the callback interface was wrongly configured with the value same us interface during the migration in the composite.xml and the component files of the composite that invokes the web service(synchronous) that doesn't support any callback .

Composite.xml with callback configured as same as interface:

Component file with callback configured as same as interface:

Oracle SOA Suite 10g to 11g Migration - Unable to register a service endpoint for a defined reference callback

Unable to register a service endpoint for a defined reference callback:

The invocation of the asynchronous web service from the composite has failed with the following error after migrating the code to Oracle SOA Suite 11g.

"Unable to register a service endpoint for a defined reference callback. Please ensure the WSDL and reference configuration are correct".

After a long struggle ,we have identified the issue .The issue was with the callback interface was wrongly configured with the value same us interface(no separate callback port is defined in the WSDL) during the migration in the composite.xml and the component files of the composite that invokes the asynchronous web service that doesn't have any callback defined.

Composite.xml with callback configured:



Component file with callback configured:

Oracle SOA Suite - Viewing Performance Metrics Using Fusion Middleware Control(EM)

Oracle SOA Suite - Viewing Performance Metrics Using Fusion Middleware Control (EM)

If you encounter a problem, such as an application that is running slowly or is hanging, you can view more detailed performance information, including performance metrics.

Oracle SOA Suite 11g:

Monitoring the performance of an Oracle WebLogic Server

1. Login to the EM console - domain.

2. Select the server to monitor.

3. The Managed Server home page is displayed.

4. From the WebLogic Server menu, choose Performance Summary

5. The Performance Summary page is displayed. 

6. To see additional metrics, click Show Metric Palette and expand the metric Categories in the right side panel.

7. To view the metrics about data source select the Data Source Metrics and the data source that need to be monitored and the required metrics data from the right panel, the metrics details will be displayed in left panel.

Oracle SOA Suite – Attaching the Common/Generic deployment plan file to all the SOA Composites.

Oracle SOA Suite – Attaching the Common/Generic deployment plan file to all the SOA Composites:

The deployment plan file can be used to change the run time configurations like WSDL endpoint, value of the partner link properties and the host details across the environments.

The plan file need to be created for each composite and the same has to be attached during the deployment.

Generic plan file also can be created and attached to deploy all the composites.

By using the generic plan file all the configuration changes can be maintained in same place also no need of creating different plan files for each composite.

Generic Plan file:

The blow is the sample Generic plan file that can be used across the composites deployment.

The generic plan file will have the configuration details for all the composites.

When deploying, attach this Plan file to all the Composites.

Before deploying the composite ,replace the tokens in the plan file with the actual values.

The below ant script can be used to deploy the composites with the plan file to the server.

ant -f ant-sca-deploy.xml

-DserverURL=http://localhost:8001

-DsarLocation=C:\demo\Project\deploy\sca_Project_rev6.jar

-Doverwrite=true

-Duser=weblogic

-DforceDefault=true

-Dconfigplan=C:\demo\deploymentplan.xml

Attached the sample plan file for your reference.

DOWNLOAD Generic Plan File