Oracle SOA Suite - Finding the Composite Instances waiting for callback

Oracle SOA Suite - Finding the Composite Instances waiting for callback:-

The below query can be used to identify the Composite instances waiting for the callback.

Select * from SOA_SOAINFRA.dlv_subscription where composite_name = ‘xxxxxxxxx’ and operation_name = 'xxxxxxxxxx' and state = 0 and properties like ‘#CorrelationString’

#CorrelationString –The correlation id used for the call back. This condition can be ignored if there is no correlation used.

Oracle SOA Suite - OutOfMemoryError when deploying the Composite

OutOfMemoryError when deploying the Composite:-

OutOfMemoryError has thrown when deploying the services to Oracle SOA Suite server from UNIX using ANT.

[wldeploy]
[wldeploy]
[wldeploy] Target Assignments:
[wldeploy] + UpdateStatus SOACluster
Exception in thread "J2EE-Deployment-task-poller" java.lang.OutOfMemoryError: PermGen space
[echo] There was an error while deploying: The following error occurred while executing this line:
[echo] code/config/scripts/WebServicesBuild.xml:96: java.lang.OutOfMemoryError: PermGen space

To overcome this issue increase the client memory (ANT) by executing the below comment and try the deployment again.

In Unix:

export ANT_OPTS=”-Xms512m -Xmx1024m -XX:MaxPermSize = 512m -XX: PermSize = 512m”

In Windows:

set ANT_OPTS=”-Xms512m -Xmx1024m -XX:MaxPermSize = 512m -XX: PermSize = 512m”

Oracle SOA Suite 10g to 11g Migration - Web service Invocation issue,Invalid URI "urn:#NewOperation"

Oracle SOA Suite 10g to 11g Migration  - Web service Invocation issue,Invalid URI "urn:#NewOperation":

The web service invocation has failed after migrating the web services to 11g with the following error

Caused By: oracle.j2ee.ws.common.addressing.api.AddressingException: Invalid URI "urn:#NewOperation" in Addressing element Action.

But the same web service was working properly in 10g.

To overcome this we have changed the soapaction "urn:#NewOperation" to empty string in web service WSDL manually and it resolved the issue.

10g:-

11g:-

Oracle SOA Suite 10g to 11g Migration - Instance Title for Composites and Components

Oracle SOA Suite 10g to 11g Migration -  Instance Title for Composites and Components:

Composite instance title:-

ora:setCompositeInstanceTitle() method can be used to set the composite instance title.

The composite instance title can be used to search the composite instances from em console but the wildcard search is not applicable on this field.

– There is no method provided to get the composite instance tile

We are only having the option to set the composite instance title using setCompositeInstanceTitle() method but no option to get the title.

BPEL Component instance Title:-

As like 10g we can use the setTitle() method to set the BPEL component title and getTitle() method to get the instance title.

BPEL Component instance Title can’t be used in em console to search the instances.

Oracle SOA Suite 10g to 11g Migration - Part3 - Things to consider post migration of the code.

Oracle SOA Suite 10g to 11g Migration - Part3  - Things to consider post migration of the code:

We have to consider the below points post migration of the code.

ValidateXML property:

During the migration,the property validateXML did not migrated by default to SOA 11g.The property needs to be added manually to the required partner links .

The below steps need to be followed to add the validateXML property(Enable the schema validation).

1.Open the .bpel file corresponding to the Composites that require the schema validation.

2. Double click the partnerlink that requires the schema validation for the request payload and select the property tab .

3.Add the validateXML property with the value true.

The added property will be available in the Composite.xml file as shown below.

DVM Issues:

1. Duplicate Rows:

In 10g, if the value in the source column is duplicated then the lookup function will return the last row for that key but in 11g the lookup will fail with the exception.

If we are looking for the value corresponding to the column “SiebelValue” by passing the “EAIVAlue” as “New”, in 10g the lookup function will return the result as “Awaiting Approval” but in 11g exception will be thrown for duplicate values.
To resolve this issue remove the duplicate rows from the DVM.

2. Invalid Column:

In 10g, if we are looking for a DVM column value that is not available in the DVM the lookup function will return the default value specified in the lookup function but in 11g the exception will be thrown for invalid column.

If the column “CANONICAL” is not available in DVM, in 10g the lookup function will return the default value (empty string) specified in the function but in 11g the exception will be thrown from the lookup function.

To resolve this issue make sure the columns specified in the lookup functions are valid.