Setting up the Integration JMS Wrapper Processes

This section describes how to configure the Integration JMS Wrapper processes to allow CCB and MDM to communicate with the CCB-MDM asynchronous integration processes through webservices and not access the queues directly.

The configuration steps include the following:

• Setting Configuration Properties for JMS Wrapper Processes

• Setting Outbound Message Configuration for CCB and MDM

Setting Configuration Properties for JMS Wrapper Processes

Various configurations that apply to specific JMS Wrapper integration processes are stored in the JMSWrapperConfigurationProperties.xml file located in MDS under the apps/CCB2-MDM2/AIAMetaData/config directory.

The JMSWrapperConfigurationProperties file holds the edge application's endpoint references that are picked up by the Integration JMS Read processes at runtime to use to call the specific edge application's webservices.

Note: Whenever the JMSWrapperConfigurationProperties.xml file is updated, the file must be reloaded to MDS for updates to be reflected in the applications or services that use the updated properties. You can perform the reload by restarting the SOA server.

Refer to Appendix D: JMS Wrapper Configuration Properties File for more information on how to configure the JMS Wrapper Configuration Properties File values.

Setting Outbound Message Configuration for CCB and MDM

Message senders should be created in Oracle Utilities Customer Care and Billing and Oracle Utilities Meter Data Management to invoke the Integration JMS Wrapper Write Services. These message senders should be linked to the Oracle Utilities Customer Care and Billing or Oracle Utilities Meter Data Management external system.

Note: When using the Integration JMS Wrapper processes, some outbound message configurations like the JNDI Server, JMS Queues and Connection configurations are not needed in Oracle Utilities Customer Care and Billing and Oracle Utilities Meter Data Management.

The Inbound Message Configurations, the JMS and MDB setup, for both Oracle Utilities Customer Care and Billing and Oracle Utilities Meter Data Management applications, are also not needed.

Refer to the Oracle Utilities Customer Care and Billing Configuration and Oracle Utilities Meter Data Management Configuration sections for more details.