Customizing SOA Composite Applications
Customizing SOA composites provide the ability to retain the out-of-the-box implementation, but to adjust the functionality according to new business needs. In future Oracle releases these customizations will not be overwritten by the new versions.
To implement custom SOA composites, refer to the
Customizing SOA Composite Applications section in the SOA documentation:
https://docs.oracle.com/en/middleware/soa-suite/soa/14.1.2/develop/customizing-soa-composite-applications.html.
This section provides a summary of the required steps:
1. Obtain the Composite Archive (SAR) file for the base composite that is to be customized. This SAR file may be obtained in one of a few ways:
• If the composite has already been installed and deployed as part of a process integration pack (PIP), the composite project may be found under the CCB- EBS\services\industry\Utilities\EBF\CCBToEBSGLBPELProcess/... directory tree and within the project's deploy subdirectory you may find the SAR file.
• If the composite has already been deployed, you can export the SAR from the server using EM console or WLST or Ant commands.
• Open the project in JDeveloper (default role) and deploy it to a SAR file.
2. Open JDeveloper (default role) and create a new SOA or use your existing application. If a new application uses the default settings, a new project “Project1” is created that can be deleted later.
3. In the Application Navigator pane, click the project name to select it.
4. Select File > Import... from the main JDeveloper menu.
5. Choose SOA Archive Into SOA Project.
The template will create a new project. The SOA project should be named with a distinguishing prefix (such as "XX") followed by the original project or composite name.
Example: XXCCBToEBSGLBPELProcess
6. Browse for the SAR file obtained in step 1. The composite name will populate automatically after selecting the SAR file. Verify that it is correct.
7. Select the Import for Customization checkbox and click Finish. The project is now ready for customization.
Note: In case of any compilation errors like MDS-00054 : MDS Exception, make sure adf-config.xml has the MDS database (where CCB-EBS integration is deployed) details.
8. Customization class jar "ugbucust.jar" must be added to your SOA composite project. This file is located in $PRODUCT_HOME/install/util/lib/ugucust.jar.
9. The SOA Application in JDeveloper must be configured to use the customization class and layer:
• In the Applications window, expand Application Resources > Descriptors > ADF META_INF.
• Open the adf-config.xml file and select the MDS tab.
• Click the Add icon to add "UGBUCustomerExtensionCustomizationClass" customization class.
• To add application-specific layer values, click the Configure Design Time Customization Layer Values link.
• Add the below snippet to add "UGBUCustomizationLayer" value in CustomizationLayerValues.xml.
<cust-layer name="UGBUCustomizationLayer" id-prefix="ugbuext">
<cust-layer-value value="UGBUCustomizationLayer" display- name="UGBU Customer Extension"/>
</cust-layer>
</cust-layers>
10. Save all the changes.
11. From the Tools menu, select Switch Roles > Customization Developer.
12. Restart Oracle JDeveloper.
The Customization Context dialog displays the available customization layers and layer values.
13. Select “UGBUCustomizationLayer” layer and value to customize.
14. Customize the BPEL process. You can make required changes to the composite and its BPEL components.
Note: Only scopes that have been marked as customizable in BPEL will be editable. Non-editable activities appear greyed out.
After making the customizations, the project can be deployed to the SOA server and/or a SAR file.
For more information about implementing custom SOA composites, refer to the
Customizing SOA Composite Applications section at:
https://docs.oracle.com/en/middleware/soa-suite/soa/14.1.2/develop/customizing-soa-composite-applications.htmlNote that the Cancel Adjustment Service (C1AdjustmentMaintenance) is part of the adjustment management functionality within CCB-EBS integration. This service is deployed as an XAI Service and exposed via Inbound Web Services (IWS).