Scenario 6: CC&B + 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 steps configured in the scenario 5, you must complete the following steps in Oracle Utilities Work and Asset Management/Oracle Utilities Operational Device Management v2.1.x to configure the integration:

1. Configure the admin data to support the integration:

• Service Area

• Asset Location Type

• Storage Location Type

• Manufacturer

• TimeZone

• Activity Type

• Service History Type

• Cost Center

2. Configure Master Data.

3. Configure Extendable Lookups.

4. Configure Message Senders to pass messages with the integration layer.

5. Configure CCB Integration Master Configuration cost center created above as default cost center to sync Item service points from Oracle Utilities Customer Care and Billing to the Connected Linear/Distributed Asset.

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 X -> XAI JNDI server.

2. Enter the JNDI server name.

Example: CCB_JNDI

3. Enter the JNDI server description.

Example: CCB Integration server

4. Enter the Provider URL in the format t3//<SOA Server>: <SOA Port>.

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 Work and Asset Management/Oracle Utilities Operational Device Management v2.1.x sends 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 Work and Asset Management/Oracle Utilities Operational Device Management v2.1.x.

• Description – Indicates queue description.

• Queue Name – Indicates the JNDI name of the queue on the Integration server.

Example: jms/aia/AIA_OUODMOUCCBSPSyncRespQueue

• 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 Work and Asset Management/Oracle Utilities Operational Device Management v2.1.x.

• Description – Additional information about the JMS Connection.

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

• JNDI ConnectionFactory – JNDI name of the connection factory on the Integration server.

Example: jms/aia/AIAOUWAMCF

Creating Outbound Messages

Create the SP Outbound message type using the following business object.

Business Object: W1-OutboundAcknowledgeMessage

Creating an HTTP Sender for SP Sync

Create a new Message Sender which points to the Oracle Utilities Customer Care and BillingEBF for the 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 values:

• JMS Connection: Point to the JMS connection created above.

• JMS Queue: Point to the JMS queue created above 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 External System

Create a new External System for the integration layer.

1. Navigate to Admin -> External System.

Example: CCB

2. Enter a unique External System and Description.

3. Set Our Name in Their System to FWI-PIP.

4. Add the SP outbound message types created above.

• SP Sync Request Outbound Message Type - created above

• Processing Method - Real-time

• Message Sender - new Message Sender for SP sync created below

• Date/Time Format – XSD

• Message XSL - W1-CCBWAMResponseAddNamespace.xsl