XAI Configuration
The following sections identify settings required to send messages to the integration layer, including:
XAI JNDI Server
To create a new XAI JNDI server to communicate with the integration layer:
1. Navigate to Admin > Integration > XAI JNDI Server.
Example: CI_NMS_JNDI
2. Enter XAI JNDI Server name and description.
Example: CCB-NMS Integration server
3. Populate the Provider URL in the format: t3//<SOA Server>: <SOA Port>
Example: t3://soaserver.us.oracle.com:8002
XAI JMS Queue
Perform the following steps to create a new XAI JMS queue:
1. Navigate to Admin > Integration > XAI JMS Queue.
2. Enter the following:
• XAI JMS Queue - Queue name in Oracle Utilities Customer Care and Billing
• Description - Queue description
• Queue Name - JNDI name of the queue on the Integration server
Example: jms/CCB-NMS/OUCCBNMSCustomerDataRequest
• Target Client Flag - JMS
• XAI JNDI Server - Select XAI JNDI Server created for the integration as described in the
XAI JNDI Server section.
Example: Customer Data Sync Integration Point
XAI JMS Connection
To create XAI JMS connection:
1. Navigate to Admin > Integration > XAI JMS Connection.
2. Enter the following:
• XAI JMS Connection - Connection name in Oracle Utilities Customer Care and Billing.
• Description - Connection description.
• XAI JNDI Server - Select the XAI JNDI Server created for the integration as described in the
XAI JNDI Server section.
• JNDI ConnectionFactory - JNDI name of the Connection factory on the Integration server.
Example: jms/CCB-NMS/CCBNMSCF
Message Sender
To create a real-time Message Sender configured to communicate with the integration layer:
1. Navigate to Admin > Integration > Message Server.
2. Enter a unique Message Sender and Description.
3. Populate values:
• Message Sender - Sender name in Oracle Utilities Customer Care and Billing
• Description - Sender description
• Invocation Type - Real-time
• XAI Class - RTJMSQSNDR (Realtime JMS Queue Sender)
• Active - Select the checkbox
• MSG Encoding - UTF-8 message encoding
• XAI JMS Connection - XAI JMS connection created for the integration
• XAI JMS Queue - XAI JMS Queue created for the Oracle Utilities Customer Care and Billing Outbound Queue.
4. Select the Context tab and set values for the following context types:
• JMS Message Type (Bytes(Y)/Text(N)) - N
• JMS User Name - user for the SOA server to be accessed
• JMS User Password - Password for the SOA server to be accessed
Example:
Message Sender for Trouble Call Interface
To create a new Message Sender which points to the Trouble Call Interface EBF endpoint URL for the Trouble Call Interface the integration point:
1. Navigate to Admin >Integration >Message Sender.
2. Enter a unique Message Sender and Description.
3. Populate values:
Invocation Type = Real-time
XAI Class = RTHTTPSNDR. (Real Time Sender to route messages via HTTP)
4. Select the Active checkbox.
MSG Encoding = UTF-8 message encoding
5. Select the Context tab and set values for the following Context Types:
• HTTP Login User - User ID for the URL to be accessed
• HTTP Login Password - Password for the URL to be accessed
• HTTP Header - SOAPAction: "process"
• HTTP Method (POST/GET) - POST
• HTTP Proxy Host - Set the proxy server name if applicable
• HTTP Proxy Port - Port for the proxy server if applicable
• HTTP Transport Method - SendReceive
• HTTP Timeout: 60 (put timeout 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 Trouble Call Interface EBF.
Example: http://demoenv/soa-infra/services/CCB-NMS/OUCCBOUNMSTroubleCallInterfaceEBF /ouccbounmstroublecallinterfaceebf_client_ep
Message Sender for Job History Query
To create the Message Sender configured to communicate with the integration layer:
1. Navigate to Admin > Integration > Message Sender.
2. Enter a unique Message Sender and description.
3. Populate values:
• Invocation Type = Real-time
• XAI Class = RTHTTPSNDR. (Real Time Sender to route messages via HTTP)
• Select the Active checkbox.
• MSG Encoding = UTF-8 message encoding
4. Select the Context tab and set values for the following context types:
• HTTP Login User - User ID for the URL to be accessed
• HTTP Login Password - Password for the URL to be accessed
• HTTP Header - SOAPAction: "process"
• HTTP Method (POST/GET) - POST
• HTTP Proxy Host - Set the proxy server name if applicable
• HTTP Proxy Port - Port for the proxy server if applicable
• HTTP Transport Method - SendReceive
• HTTP Timeout: 60 (put timeout 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 Query Job History EBF.
Example: http://demoenv/soa-infra/services/CCB-NMS/ OUCCBOUNMSJobHistoryQueryEBF/ouccbounmsjobhistoryquery_client_ep
Message Sender for Trouble Call History Query
Perform the following steps to create Message Sender for Trouble Call History Query:
1. Navigate to Admin > Integration > Message Sender.
2. Enter a unique Message Sender and Description.
3. Populate values:
• Invocation Type = Real-time
• XAI Class = RTHTTPSNDR. (Real Time Sender to route messages via HTTP)
• Select the Active checkbox.
• MSG Encoding = UTF-8 message encoding
4. Select the Context tab and set values for the following Context Types:
• HTTP Login User - User ID for the URL to be accessed
• HTTP Login Password - Password for the URL to be accessed
• HTTP Header - SOAPAction: "process"
• HTTP Method (POST/GET) - POST
• HTTP Proxy Host - Set the proxy server name if applicable
• HTTP Proxy Port - Port for the proxy server if applicable
• HTTP Transport Method - SendReceive
• HTTP Timeout: 60 (put timeout 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 Query Trouble Call History EBF.
Example: http://demoenv/soa-infra/services/CCB-NMS/OUCCBOUNMSTroubleCallsQueryEBF/OU CCBOUNMSTroubleCallsQueryEBF_ep
Message Sender for Planned Outages Query
Create a new Message Sender which points to the Planned Outages Query EBF endpoint URL for Planned Outages Query the integration point.
To create an HTTP sender configured to communicate with the integration layer:
1. Navigate to Admin > Integration > Message Sender.
2. Enter a unique Message Sender and Description.
3. Populate values:
• Invocation Type = Real-time
• XAI Class = RTHTTPSNDR. (Real Time Sender to route messages via HTTP)
• Select the Active checkbox.
• MSG Encoding = UTF-8 message encoding
4. Select the Context tab and set values for the following Context Types:
• HTTP Login User - User ID for the URL to be accessed
• HTTP Login Password - Password for the URL to be accessed
• HTTP Header - SOAPAction: "process"
• HTTP Method (POST/GET) - POST
• HTTP Proxy Host - Set the proxy server name if applicable
• HTTP Proxy Port - Port for the proxy server if applicable
• HTTP Transport Method - SendReceive
• HTTP Timeout: 60 (put timeout 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 Query Planned Outage EBF.
Example: http://demoenv/soa-infra/services/CCB-NMS/ OUCCBOUNMSOutageHistoryQueryEBF/ OUCCBOUNMSOutageHistoryQueryEBF_ep
Message Sender for Notify of Communication Preference
To create Message Sender for Notify of Communication Preference:
1. Navigate to Admin >Integration >Message Sender.
2. Enter a unique Message Sender and Description.
3. Populate values:
• Invocation Type = Real-time
• XAI Class = RTHTTPSNDR. (Real Time Sender to route messages via HTTP)
• Select the Active checkbox.
• MSG Encoding = UTF-8 message encoding
4. Select the Context tab and set values for the following Context Types:
• HTTP Login User - User ID for the URL to be accessed
• HTTP Login Password - Password for the URL to be accessed
• HTTP Header - SOAPAction: "process"
• HTTP Method (POST/GET) - POST
• HTTP Proxy Host - Set the proxy server name if applicable
• HTTP Proxy Port - Port for the proxy server if applicable
• HTTP Transport Method - SendReceive
• HTTP Timeout: 60 (put timeout 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 Query Trouble Call History EBF.
Example:
http://demoenv/soa-infra/services/CCB-NMS/ OUCCBOUNMSNotifyPreferenceEBF /ouccbounmsnotifypreferenceebf_client_ep
Outbound Message Type
To create Outbound Message Type, perform the following steps:
1. Navigate to Admin > Integration > Outbound Message Type.
2. Enter a unique Outbound Message Type and Description.
3. Populate values:
• Business Object = C1-NMSSPSyncReqOutMsg (Customer Sync Outbound Message BO)
• Priority = (choose from the selection)
Trouble Calls Interface
1. Navigate to Admin menu >Outbound Message Type.
2. Enter a unique Outbound Message Type and Description.
3. Populate values:
• Business Object =C1-OutageCallOutboundMsg (Outage Call Outbound Message BO)
• Priority = (choose from the selection)
Query Job History
1. Navigate to Admin > Integration > Outbound Message Type.
2. Enter a unique Outbound Message Type and Description.
3. Populate values:
• Business Object = C1-OutageJobHistory (Job History Query Outbound Message BO)
• Priority = (choose from the selection)
Query Trouble Call History
1. Navigate to Admin menu >Outbound Message Type.
2. Enter a unique Outbound Message Type and Description.
3. Populate values:
• Business Object = C1-OutageCallHistory (Call History Query Outbound Message BO)
• Priority = (choose from the selection)
Query Planned Outages
1. Navigate to Admin > Integration > Outbound Message Type.
2. Enter a unique Outbound Message Type and Description.
3. Populate values:
• Business Object = C1-PlannedOutages (Planned Outages Query Outbound Message BO)
• Priority = (choose from the selection)
Edge Application Communication Preference
1. Navigate to Admin > Integration > Outbound Message Type.
2. Enter a unique Outbound Message Type and Description.
3. Populate values:
• Business Object = C1-NotifyEdgeApplicationOutMsg (Notify Edge Applications Outbound Message
• Priority = (choose from the selection)
External System
Perform the following steps to create a new External System for direct the integration:
1. Navigate to Admin > Integration > External System.
2. Enter a unique External System and Description.
3. Set Our Name in Their System to “CC&B”.
4. Define the Outbound Message Types associated to the integration.
• For Customer Data Synchronization Outbound Message Type, populate values:
• Outbound Message Type = (Outbound Message Type for Customer Data Synchronization)
• Processing Method = Real-time
• Message Sender = (Message Sender for Customer Data Synchronization)
• Message XSL = CDxAddEnvelope-SOAP1-2.xsl
• Response XSL =
• For Trouble Calls Interface Outbound Message Type, populate values:
• Outbound Message Type = (Outbound Message Type for Trouble Call Interface)
• Processing Method = Real-time
• Message Sender = (Message Sender for Trouble Call Interface)
• Message XSL = CDxAddEnvelope-SOAP1-2.xsl
• Response XSL =
• For Query Job History Outbound Message Type, populate values:
• Outbound Message Type = (Outbound Message Type for Job History Query)
• Processing Method = Real-time
• Message Sender = (Message Sender for Job History Query)
• Message XSL = CDxAddEnvelope-SOAP1-2.xsl
• Response XSL = C1-NMSRemoveEnvelopeJobHist.xsl
• For Query Trouble Call History Outbound Message Type, populate values:
• Outbound Message Type = (Outbound Message Type for Trouble Call History Query)
• Processing Method = Real-time
• Message Sender = (Message Sender for Trouble Call History Query)
• Message XSL = CDxAddEnvelope-SOAP1-2.xsl
• Response XSL = C1-NMSRemoveEnvelopeCallHist.xsl
• For Query Planned Outages Outbound Message Type, populate values:
• Outbound Message Type = (Outbound Message Type for Planned Outages Query)
• Processing Method = Real-time
• Message Sender = (Message Sender for Planned Outages Query)
• Message XSL = CDxAddEnvelope-SOAP1-2.xsl
• Response XSL = C1-NMSRemoveEnvelopePlanOut.xsl