Scenario 6: CCB + WAM/ODM v2.1.x

In this scenario, the integration product coordinates processing between:

• Oracle Utilities Customer Care and Billing

• Oracle Utilities Work and Asset Management/ Oracle Utilities Operational Device Management v2.1.x

Apart from the above configurations follow the guidelines to configure Oracle Utilities Customer Care and Billing for Scenario 1 with the following exceptions:

• Billable Charge is not used.

• Customer Interactions are not used

• No customer and asset data synchronization processing is available in this scenario.

• Feature Configuration options related to data synchronization do not need to be configured

• To Type and To Do Roles for Billable Charge SA, Customer Contacts are created as result of customer information change or creation of are not in use.

• Data configurations needed for the Appointments integration points are not used in this scenario.

Configuring Outbound Services

The following sections identify settings required to communicate using outbound services.

Configuring JNDI Server

Create a new JNDI server configured to communicate with the integration layer. It should point to the Integration SOA server.

1. In the Admin menu, navigate to J -> JNDI server.

2. Enter the JNDI server name.
For example: ODM_JNDI

3. Enter the JNDI server description.
For example: ODM Integration server

4. Enter the Provider URL in the format t3//<SOA Server>: <SOA Port>.
For example: t3://soaserver.us.oracle.com:8002

5. Enter the Initial Context Factory.
It should be: weblogic.jndi.WLInitialContextFactory

Configuring JMS Queue

Create a new JMS queue for integration queue where Oracle Utilities Customer Care and Billing sends SP Sync Request outbound messages.

1. In the Admin menu, navigate to J -> JMS Queue.

2. Enter the following:

• JMS Queue – Refers to the queue name in Oracle Utilities Customer Care and Billing

• Description – Indicates queue description

• Queue Name – Indicates the JNDI name of the queue on the Integration server. For example: jms/aia/AIA_OUCCBOUODMSPSyncReqQueue

• Target Client Flag – JMS

• JNDI Server – Select the JNDI server created for integration

Creating JMS Connection

Create a new JMS connection used to connect to the integration queues.

1. In the Admin menu, navigate to JMS connection.

2. Enter the following:

• JMS Connection – Indicates the Connection name in Oracle Utilities Customer Care and Billing

• Description – Additional information about the JMS Connection

• JNDI Server – Select the JNDI server created for this integration (as described in the JNDI Server section)

• JNDI ConnectionFactory – JNDI name of the connection factory on the Integration server. For example: jms/aia/AIAOUCCBCF

Creating the SP Sync Request Outbound Message Type

This outbound message type will be used to send the SP Sync Request message. Create a new Outbound Message Type which maps to the appropriate business object.

1. Navigate to Admin, Outbound Message Type, and click Add.

2. Enter a unique Outbound Message Type and Description.
For example: CM_WAMSPSYNC.

3. Populate values as follows:

• Business Object = C1-ODMSPSyncReqOutMsg

• Priority = 50

You can set this to any other value as needed.

Creating the SP Installed Assets Overview Outbound Message Type

This outbound message type will be used to send the SP Installed Assets Overview message. Create a new Outbound Message Type which maps to the appropriate business object.

1. Navigate to Admin, Outbound Message Type, and click Add.

2. Enter a unique Outbound Message Type and Description. Example: CM_WAMSPAST

3. Populate values as follows:

• Business Object = C1-ODMSPInstalledAssetsOutMsg

• Priority = 50

You can set this to any other value as needed.

Creating the SP Sync Request Message Sender

Create a new Message Sender which points to the Oracle Utilities Work and Asset Management/ Oracle Utilities Operational Device Management EBF for the SP Sync Request integration point.

1. Navigate to Admin -> Message Sender.

2. Enter a unique Message Sender and Description.

3. Populate values as follows:

• Invocation Type = Real-time

• Message Class = RTJMSQSNDR.
Sender posts messages to JMS queue real-time.

• MSG Encoding = UTF-8 message encoding

4. Select the Active check box and set the following:

• JMS Connection: Point to the JMS connection created

• JMS Queue: Point to the JMS queue created for SP Sync

5. Select the Context tab and set values for the following Context Types:

• JMS Message Type (Bytes(Y)/Text(N)) – N

• JMS User Name – User ID for the url to be accessed

• JMS User Password – Password for the url to be accessed

Creating the SP Installed Assets Overview Message Sender

Create a new Message Sender which points to the Oracle Utilities Work and Asset Management/ Oracle Utilities Operational Device Management. Integration is not involved here as the service interacts directly with Oracle Utilities Work and Asset Management/ Oracle Utilities Operational Device Management.

1. Navigate to Admin -> Message Sender.

2. Enter a unique Message Sender and Description.

3. Populate values as follows:

• Invocation Type = Real-time

• Message Class = RTHTTPSNDR.
This is the class for real-time sender to route messages using HTTP.

• MSG Encoding = UTF-8 message encoding

4. Select the Active check box.

5. Select the Context tab and set values for the following Context Types:

• Character Encoding – UTF-8

• HTTP Login User – User ID for the url to be accessed

• HTTP Login Password – Password for the url to be accessed

• HTTP Header – SOAPAction: " http://your_wamorodm_serverhost/webservices/W1-RetrieveServicePointAssets#W1-RetrieveServicePointAssets "

• HTTP Method (POST/GET) – POST

• HTTP Transport Method – SendReceive

• HTTP Timeout: 60 (in seconds)

• HTTP URL 1 – Set the URL to be accessed.
If the URL value does not fit, use the additional HTTP URL types to set the complete URL. This should point to the Oracle Utilities Work and Asset Management/ Oracle Utilities Operational Device Management Service Point Assets service.

Example: https://your_wamorodm_serverhost:your_wamorodm_port/ouaf/webservices/W1-RetrieveServicePointAssets

Creating the External System

Create a new External System for the integration layer.

1. Navigate to Admin -> External System.

2. Enter a unique External System and Description.

3. Set Our Name in Their System to the external system used for identifying Oracle Utilities Customer Care and Billing in the Oracle Utilities Work and Asset Management/ Oracle Utilities Operational Device Management environment.

4. Add the SP outbound message types created.

• SP Sync Request Outbound Message Type - created above

• Processing Method - Real-time

• Message Sender - new Message Sender for SP sync created

• Date/Time Format – OUAF

• Message XSL - C1-CCB2JMSQAddNamespace.xsl

5. Add the SP Installed Assets Overview outbound message type created

• SP Installed Assets Overview Outbound Message Type - created above

• Processing Method - Real-time

• Message Sender - new Message Sender for SP Installed Assets Overview created below

• Date/Time Format – OUAF

• Message XSL - C1-RetrieveServicePoinAssetsRequest.xsl

• Response XSL - C1-RetrieveServicePoinAssetsResponse.xsl