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.
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.