Migrating Custom Components

This section includes the following:

Migrating Custom Composites

All integration services provided with this integration pack have extension points available to extend the functionality using custom composites.

All custom extension composites can be migrated from 12c to 14c. Make sure you have a proper backup of the 12c process before doing the upgrade from 12c to 14c.

Open the 12c composite in Jdeveloper and save the composite. The directory structure of the composite changes and some files are added and deleted.

Manual Changes to be made when migrating from 12c to 14c:

1. All the transformations currently are either in xsl folder or under the composite directory, should be moved to Transformations folder and all references in the .bpel file should be changed accordingly.

2. All the WSDLs should be moved to the WSDLs folder manually.

3. .bpel should be moved to the BPEL folder.

4. All xsds should be moved to the Schemas folder.

5. All the adapter related files should be moved to Adapters folder.

6. All human task related artifacts should be moved to HumanTasks folder.

7. All the mediator artifacts should be moved to the Mediators folder.

Make sure that there are no errors and deploy directly from JDev or using DeploUndeployUtility.xml file.

To deploy individual composites using DeploUndeployUtility:

1. Execute the following commands in the Command prompt for Linux and Windows respectively:

Linux:

cd $PRODUCT_HOME/bin

ant -f DeployUndeployUtility.xml -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml DeployComposite

Windows:

cd %PRODUCT_HOME%\bin

ant -f DeployUndeployUtility.xml -DInstallProperties=%PRODUCT_HOME%/config/InstallProperties.xml DeployComposite

2. Validate the following parameters when prompted with default values during deployment. Press ENTER to use the default prompted value.

• Composite Name: Name of the custom composite to be deployed to SOA server. This parameter does not have a default value.

• Composite folder location: The folder name should be an absolute path beginning with %PRODUCT_HOME%/services/industry/Utilities/<EBF/utility>.

Example: To deploy the composite from %PRODUCT_HOME%/services/industry/Utilities/EBF, pass %PRODUCT_HOME%/services/industry/Utilities/EBF to this property.

The default value for this property is %PRODUCT_HOME%/services/ industry/Utilities/EBF, as most of the business-specific composites reside in this folder.

Note: Make sure the custom composite is located on the server physical directory/PRODUCT_HOME where the integration is running.

• Partition Name: The SOA partition name to which the composite should be deployed.

For more information on deploying/undeploying individual comspoites refer to the Deploying/undeploying Individual Composites section in the Oracle Utilities Customer Care and Billing Integration to Oracle Utilities Meter Data Management Installation Guide included in this release.

Note: It is not mandatory for customers to migrate their custom/extension composite from 12c to 14c. The 12c custom composite service can still be called by the 14c CCB-MDM2 flows.

Migrating Custom XSLs

Same Custom XSLs previously available in 12c are now available in 14c. To make sure that the source/target mapping feature is not lost, do not copy the XSL as is from 12c to 14c, but instead manually merge those changes from the 12c version of XSL to 14c version of XSL. Redeploy the modified processes either from Jdev or using the DeploUndeployUtility file.