Migrating Custom Components

This section includes:

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. Ensure you have a proper backup of the 12c process before upgrading from 12c to 14c.

Open the 12c composite in JDeveloper 14.1.2 and save the composite. The directory structure of the composite has not changed, but to open the diagrams in the Enterprise Manager, the SCA-INF folder should be included during the deployment. Some files are added and deleted.

Perform these manual changes when migrating from 12c to 14c:

1. Right-click the project and select “Rebuild {compositeName}.jpr” or select the project and press Alt+F9.

This will create the SCA-INF in the background, but it will only show in JDeveloper after refreshing (F5) the project.

2. Save the project.

3. Ensure that there are no errors during the rebuild and deploy directly from JDeveloper or using DeployUndeployUtility.xml file.

Note: If you generate a SAR to deploy manually to the Enterprise Manager, include the SOA Configuration Plan to customize the endpoints.

Perform the following steps 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, then 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 composites refer to the Oracle Utilities Customer Care and Billing Integration to Oracle E-Business Suite Financials for General Ledger and Accounts Payable Release 12.1 Media Pack Installation Guide, under Deploying/Undeploying Individual Composites.

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

Migrating Custom XSL

No changes are needed to the previous 12c custom XSL and will be included if you used the migration steps documented above.