Extract Request Configuration Steps
This section outlines the objects that must be configured to support batch extracts of usage and events from an NES head-end system. To configure the NES Adapter to support sending extract requests for usage and events, you must do the following:
• Create message senders (one for usage, one for events) to send extract requests.
• Create Outbound Message Types (one for usage, one for events) for extract requests.
• Associate the message senders and Outbound Message Types to the External System used with the head-end system service provider
• Create “NES Usage Extract Scheduler Type” and “NES Event Extract Scheduler Type” activity types.
• Create “NES Usage Extract Scheduler” and “NES Event Extract Scheduler” activities.
The following sections provide details for configuring these object. Refer to the Oracle Utilities Application Framework documentation for more information about creating message senders, Outbound Message Types, and External Systems.
Note: Configuration of the OSB and BPEL services used by this process is done when installing and configuring the OSB and BPEL components of the NES Adapter.
Message Sender - NES Handle Batch Event
Create an message sender for event extracts as follows:
Main Tab:
• Message Sender: Enter a code for the batch event message sender (D4-HNLBATEVT)
• Description: NES Handle Batch Event
• Invocation Type: Real-time
• Message Class: RTHTTPSNDR (Sender routes messages via HTTP real-time)
• Active: True (checked)
• MSG Encoding: UTF-8 message encoding
Context Tab:
• HTTP Header: SOAPAction:http://xmlns.oracle.com/ouaf/NES/GrabBatchEvents
• HTTP Login User: <USER_​ID>
• HTTP Login Password: <PASSWORD>
• HTTP Method: POST
• HTTP URL 1: http://<EM_​SERVER>:<EM_​SERVER_​PORT>/soa-infra/services/NES/HandleBatchEvent/BatchEventHandler
where:
◦ <USER_​ID>: the user ID used to log into WebLogic Enterprise Manager
◦ <PASSWORD>: the password used to log into WebLogic Enterprise Manager
◦ <EM_​SERVER>: the machine name or IP address of server where the WebLogic Enterprise Manager is installed
◦ <EM_​SERVER_​PORT>: the port where the WebLogic Enterprise Manager is installed
Message Sender - NES Handle Batch Usage
Create an message sender for usage extracts as follows:
Main Tab:
• Message Sender: Enter a code for the batch usage message sender (D4-HNLBATUSG)
• Description: NES Handle Batch Usage
• Invocation Type: Real-time
• Message Class: RTHTTPSNDR (Sender routes messages via HTTP real-time)
• Active: True (checked)
• MSG Encoding: UTF-8 message encoding
Context Tab:
• HTTP Header: SOAPAction:http://xmlns.oracle.com/ouaf/NES/GrabBatchUsage
• HTTP Login User: <USER_​ID>
• HTTP Login Password: <PASSWORD>
• HTTP Method: POST
• HTTP URL 1: http://<EM_​SERVER>:<EM_​SERVER_​PORT>/soa-infra/services/NES/HandleBatchUsage/BatchUsageHandler
where:
◦ <USER_​ID>: the user ID used to log into WebLogic Enterprise Manager
◦ <PASSWORD>: the password used to log into WebLogic Enterprise Manager
◦ <EM_​SERVER>: the machine name or IP address of server where the WebLogic Enterprise Manager is installed
◦ <EM_​SERVER_​PORT>: the port where the WebLogic Enterprise Manager is installed
Outbound Message Type - NES Handle Batch Event
Create an Outbound Message Type for event extract requests as follows:
• Outbound Message Type: Enter a code for the batch event Outbound Message Type (D4-HNLBATEVT)
• Description: NES Handle Batch Event
• Business Object: D1-OutboundMessage
• Priority: - Priority 20 (or lower)
Outbound Message Type - NES Handle Batch Usage
Create an Outbound Message Type for usage extract requests as follows:
• Outbound Message Type: Select a code for batch usage Outbound Message Type (D4-HNLBATUSG)
• Description: NES Handle Batch Usage
• Business Object: D1-OutboundMessage
• Priority: Priority 20 (or lower)
External Systems
Add the event and usage extract Outbound Message Types and message senders to the external system used for the NES head-end system as follows:
• External System: NES
• Description: NES
• Outbound Message Types:
Outbound Message Type
Message Sender
D4-HNLBATEVT
D4-HNLBATEVT
D4-HNLBATUSG
D4-HNLBATUSG
Note: The following apply to the above outbound message types:
• Processing Method: Real-time
• Message XSL: D4-Request xsl
• Response XSL: D4-Response.xsl
Activity Type - NES Event Extract Scheduler
Create an Activity Type for event extract requests as follows:
• Activity Type: Enter a code for the activity type (NES-EVENT-EXTRACT)
• Description: Enter a description for the activity type (NES Event Extract Scheduler Type)
• Related Transaction BO: NES Event Extract Scheduler
• Activity Type Status: Active
• Outbound Message Type: NES Handle Batch Event
• External System: The external system used for the NES head-end system
• Exception Handling:
◦ To Do Type: Activity To Do Type
◦ To Do Role: System Default Role
◦ Retry Frequency: Select retry frequency in case if Activity reaches an error state (00:03:00)
◦ Maximum Retries: Select max number of times the activity will be retried - since it reached the error state (1)
◦ Discard Reason: Select from the dropdown if available.
Activity Type - NES Usage Extract Scheduler
Create an Activity Type for usage extract requests as follows:
• Activity Type: Enter a code for the activity type (NES-USAGE-EXTRACT)
• Description: Enter a description for the activity type (NES Usage Extract Scheduler Type)
• Related Transaction BO: NES Usage Extract Scheduler
• Activity Type Status: Active
• Outbound Message Type: NES Handle Batch Usage
• External System: The external system used for the NES head-end system
• Exception Handling:
◦ To Do Type: Activity To Do Type
◦ To Do Role: System Default Role
◦ Retry Frequency: Select retry frequency in case if Activity reaches an error state (00:03:00)
Maximum Retries: Select max number of times the activity will be retried - since it reached the error state (1)
◦ Discard Reason: Select from the dropdown if available.
Activity - NES Event Extract Scheduler
Initiate an Activity for event extract requests as follows:
1. Select Main->Communication->Activity+
2. Select "NES Event Extract Scheduler Type" from the Activity Type drop-down list.
3. Enter the number of hours for each extract request in the Number of Hours of Data Request field. The default is 24.
4. Optional: Enter start and end dates and times for the first extract request in the Current Request Start Date/Time and Current Request End Date/Time fields.
Note that these are optional fields. If not populated, the values are populated as follows:
◦ Current Request Start Date/Time: taken from the last request stop date/time (which is populated by the “Event Extract Scheduler Send Request” algorithm (D4-EVTSNDREQ)
◦ Current Request End Date/Time: the Current Request Start Date/Time plus the number of hours in the Number of Hours of Data Request field.
Activity - NES Usage Extract Scheduler
Initiate an Activity for usage extract requests as follows:
1. Select Main->Communication->Activity+
2. Select "NES Usage Extract Scheduler Type" from the Activity Type drop-down list.
3. Enter the number of hours for each extract request in the Number of Hours of Data Request field. The default is 24.
4. Optional: Enter start and end dates and times for the first extract request in the Current Request Start Date/Time and Current Request End Date/Time fields.
Note that these are optional fields. If not populated, the values are populated as follows:
◦ Current Request Start Date/Time: taken from the last request stop date/time (which is populated by the “Usage Extract Scheduler Send Request” algorithm (D4-USGSNDREQ)
◦ Current Request End Date/Time: the Current Request Start Date/Time plus the number of hours in the Number of Hours of Data Request field.