Scenario 1: CC&B + MWM + WAM v1.9.1.x
In this scenario, the integration product coordinates processing between three Oracle Utilities application products based on the configuration settings described. All three application products and the integration product must be configured to enable this business scenario. This section of the document describes the configuration required for one of the application products.
Configure Oracle Utilities Mobile Workforce Management for Scenario 1
At a high-level, you must complete the following steps in Oracle Utilities Mobile Workforce Management to configure the integration:
1. Configure the admin tables to support the integration:
• Activity Types
• Batch Processes
• Service Areas
• Appointment Booking Group
2. Configure the extendable lookup tables to support the integration:
• Device Manufacturer
• Disconnect Location
• Meter Configuration Type
• Meter Location
• Payment Cancellation Reason
• Service Instructions
• Service Warnings
• Stock Locations
• Time Of Use
• Unit Of Measure
3. Configure message senders to pass messages with the integration layer.
Configure Administration Tables
This section describes unique setup issues related to configuring your system for the integration.
Activity Type
The codes defined here must exactly match values in the DVM for Order Type indicated. Refer to the section on FA Type for information on supported activity types.
Batch Processes
Batch jobs need to run to facilitate the transactions moving between the applications.
Service Areas
The codes defined here must exactly match values in the DVM for Dispatch Group indicated.
Appointment Booking Group
The codes defined here must exactly match values in the DVM for Slot Group indicated. Refer to the section on Slot Group for information on supported Appointment Booking Groups.
Configure Extendable Lookups
This section describes unique setup issues specifically related to configuring your system for the integration.
Disconnect Location
When a service point is disconnected from the supply source, a disconnect location must be specified. This location defines where service was severed. It also controls the type of field activity generated to reconnect service.
The codes defined here must exactly match values in the DVM for disconnect location code indicated.
Meter Configuration Type
Every meter configuration must reference a meter configuration type. The meter configuration type indicates the valid (required or optional) unit of measure and time of use registers for the configuration.
The codes defined here must exactly match values in the DVM for meter configuration type indicated.
Meter Location
A meter can be associated with the on-site installation location.
Stock Locations
A stock location is a physical or logical location at which meters and/or items are stored while they are not installed at a service point.
The codes defined here must exactly match values in the AIA configuration file for the Item and/or Meter Stock Location Codes indicated.
Time of Use
Every meter register can be associated with a time of use code.
The codes defined here must exactly match values in the DVM for Register time of use indicated.
Unit of Measure
Every meter register must be associated with a unit of measure (read type) code.
The codes defined here must exactly match values in the DVM for Read type indicated.
Configure Message Senders
The following sections identify settings required to communicate using message senders.
Create the Outbound Message Type Used to Send Activity Status Updates to the Integration
Create a new Outbound Message Type which maps to the appropriate business object.
1. Navigate to Admin, Outbound Message Type, and select plus.
2. Enter a unique Outbound Message Type and Description (for example, CM-ACTSTATUS).
3. Populate values as follows:
Business Object = M2-ActivityStatusUpdate
Priority = 50. You can set this to any other value as needed.
Create the Outbound Message Type Used to Send Activity Completion Details to the Integration
Create a new outbound message type which maps to the appropriate business object.
1. Navigate to Admin, Outbound Message Type, and select plus.
2. Enter a unique Outbound Message Type and Description
For example, CM-ACTCOMPLT.
3. Populate values as follows:
Business Object = M2-ActivityCompletionDetails
Priority = 50. You can set this to any other value.
Create the Outbound Message Type Used to Send Pickup Order (New Activity) Details to the Integration
Create a new outbound message type which maps to the appropriate business object.
1. Navigate to Admin, Outbound Message Type, and select plus.
2. Enter a unique Outbound Message Type and Description (for example, CM-NEWACTVTY).
3. Populate values as follows:
Business Object = M2-ActivityDataDetails
Priority = 50. You can set this to any other value.
Create the Outbound Message Type Used to Request Device Verification from the Integration
Create a new outbound message type which maps to the appropriate business object.
1. Navigate to Admin, Outbound Message Type, and select plus.
2. Enter a unique Outbound Message Type and Description (for example CM-DEVVERIFY).
3. Populate values as follows:
Business Object = M2-DeviceVerificationMessage
Priority = 50. You can set this to any other value.
Create an HTTP Sender for Pickup Orders
Create a new Message sender which points to the Oracle Utilities Mobile Workforce Management Requester ABCS for the Create Field Order 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 = 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: "ProcessOrderCreate"
• 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 Order Create Requester ABCS.
Example: http://[server]/services/default/ProcessWorkOrderCreateOUMWMUtilitiesReqABCSImplV2/ProcessWorkOrderCreateOUMWMUtilitiesReqABCSImplV2
Create an HTTP Sender for Activity Status Updates
Create a new Message Sender which points to the Oracle Utilities Mobile Workforce Management Requester ABCS for the Field Order Status Update 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 = 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: "ProcessOrderStatus"
• 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 Order Status Requester ABCS.
Example: http://sdc60017sems.us.oracle.com:8095/soa-infra/services/default/ProcessWorkOrderStatusOUMWMUtilitiesReqABCSImplV2/ProcessWorkOrderStatusOUMWMUtilitiesReqABCSImplV2
Create an HTTP Sender for Activity Completion Details
Create a new Message Sender which points to the Oracle Utilities Mobile Workforce Management Requester ABCS for the Field Order Completion 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 = 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: "ProcessOrderComplete"
• 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 Order Complete Requester ABCS.
Example: http://[server]/services/default/ProcessWorkOrderCompleteOUMWMUtilitiesReqABCSImplV2/ProcessWorkOrderCompleteOUMWMUtilitiesReqABCSImplV2
Create an HTTP Sender for Device Verification Messages
Create a new Message Sender which points to the Oracle Utilities Mobile Workforce Management Requester ABCS for the Validate Installed Product 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 = RTHTTPSNDR. This is the class for real-time sender to route messages using HTTP.
MSG Encoding = UTF-8 message encoding
Select the Active check box.
4. 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: "ValidateInstalledProduct"
• 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 Validate Installed Product Requester ABCS.
Example: http://[server]/services/default/ValidateInstalledProductOUMWMUtilitiesReqABCSImplV2/ValidateInstalledProductOUMWMUtilitiesReqABCSImplV2
Create an HTTP Sender for SP Query
Create a new Message Sender which points to the Oracle Utilities Mobile Workforce Management Requester ABCS for the SP Query 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 = 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: "QueryInstalledProductList"
• 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 Order Create Requester ABCS.
Example: http://[server]/services/default/ QueryInstalledProductListOUMWMUtilitiesReqABCSImplV2/QueryInstalledProductListOUMWMUtilitiesReqABCSImplV2
Create an 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 MWM.
4. Add the four outbound message types created above.
• Activity Data Details Outbound Message Type - created above
• Processing method - Real-time
• Message Sender - new Message Sender for New Activities created above
• Date/Time Format - XSD
• Message XSL - AddSOAPEnvelopeAndNamespace.xsl
• Response XSL - M2DataDetails_Response.xsl
• Activity Status Update Outbound Message Type - created above
• Processing method - Real-time
• Message Sender - new Message Sender for Activity Status Updates created above
• Date/Time Format - XSD
• Message XSL - AddSOAPEnvelopeAndNamespace.xsl
• Activity Completion Details Outbound Message Type - created above
• Processing method - Real-time
• Message Sender - new Message Sender for Activity Completion Details created above
• Date/Time Format - XSD
• Message XSL - AddSOAPEnvelopeAndNamespace.xsl
• Device Verification Outbound Message Type - created above
• Processing method - Real-time
• Message Sender - new Message Sender for Device Verification Messages created above
• Date/Time Format - XSD
• Message XSL - AddSOAPEnvelopeAndNamespace.xsl
• Response XSL - M2DeviceVerification_Response.xsl
• Message Sender - new Message Sender for SP Query Messages created above
• Date/Time Format - XSD
• Message XSL - AddSOAPEnvelopeAndNamespace.xsl
• Response XSL - RemoveSOAPEnvelopeAndNamespace.xsl
Manage Feature Configuration
1. Navigate to Admin > Feature Configuration.
2. Create new feature configuration with Schema Constants as the Feature Type and enter required values for the outbound message types you have created for this integration.