Pass Data without Extending the EBO

In some cases it is necessary to pass a number of fields from one application to another without using the integration layer transformation.

For example, the Oracle Utilities Mobile Workforce Management task completion process can be customized to pass information to Oracle Utilities Customer Care and Billing to be stored in Oracle Utilities Customer Care and Billing as characteristics or in a CLOB field. If this information does not need to be translated using DVMs, it can simply pass through the integration layer.

In this case Oracle Utilities Mobile Workforce Management uses a custom BO to pass additional information on completion.

Refer to the Oracle Utilities Mobile Workforce Management Configuration Guide for information of custom extensions.

Pass Data without Customizing the EBO

1. Configure the source application to pass the new custom element in escaped xml format.

This can be done using XSL on the outbound message in the source application.

2. Configure a custom xsl in the integration layer Requester ABCS (for example, Oracle Utilities Mobile Workforce Management Requester ABCS) to map the source data (for example, Oracle Utilities Mobile Workforce Management ABM element) to a custom element in EBM (for example, custom area on Work Order EBM)

This data can then be passed across to the target.

3. Configure a custom xsl in the integration layer Provider ABCS (for example, CCB Provider ABCS) to map the custom element in EBM to the Oracle Utilities Customer Care and Billing service ABM.

The target application is now able to receive the escaped xml in a custom element and process it.