Billing

CA_MDM_Integration
Author: Infinite Date: Nov 14, 2011
Table of contents.
Nov 14, 2011
Table of contents
1 Module "RAPDRPBillingMeteringServiceModule".......................................................................................................................................8 1.1 Overview................................................................................................................................................................................................. 8 1.2 All Resources.......................................................................................................................................................................................... 8 2 Assembly Diagram "RAPDRPBillingMeteringServiceModule".................................................................................................................. 10 2.1 Overview............................................................................................................................................................................................... 10 2.2 Assembly Diagram Settings.................................................................................................................................................................. 10 2.3 Component Overview............................................................................................................................................................................10 2.4 Wires..................................................................................................................................................................................................... 10 2.5 Quality of Service Qualifiers Overview.................................................................................................................................................. 11 2.5.1 Asynchronous invocation.................................................................................................................................................................. 11 2.5.2 Join transaction................................................................................................................................................................................. 11 2.5.3 Reliability...........................................................................................................................................................................................11 2.5.4 Suspend transaction......................................................................................................................................................................... 11 2.6 Component Settings..............................................................................................................................................................................12 2.6.1 Export "MeteringBillingTxInfExport1"................................................................................................................................................ 12 2.6.1.1 General Settings........................................................................................................................................................................... 12 2.6.1.2 Interfaces...................................................................................................................................................................................... 12 2.6.1.2.1 Interface "MeteringBillingTxInf".................................................................................................................................................12 2.6.2 Mediation Flow "RAPDRPBillingMeteringServiceModule"................................................................................................................ 12 2.6.2.1 General Settings........................................................................................................................................................................... 12 2.6.2.2 Interfaces...................................................................................................................................................................................... 12 2.6.2.2.1 Interface "MeteringBillingTxInf".................................................................................................................................................12 2.6.2.2.2 Interface "OptimumRouteInf".................................................................................................................................................... 13 2.6.2.3 References....................................................................................................................................................................................13 2.6.2.3.1 Partner Reference "NotifyTheftServicePartner"........................................................................................................................13 2.6.2.3.1.1 Interface "NotifyTheftService"...............................................................................................................................................14 2.6.2.3.2 Partner Reference "NotifyMeterReplacementServicePartner"................................................................................................. 14 2.6.2.3.2.1 Interface "NotifyMeterReplacementService"........................................................................................................................ 14 2.6.2.3.3 Partner Reference "OptimumroutemapforBillDistributionMeterReadingPartner"......................................................................14 2.6.2.3.3.1 Interface "OptimumroutemapforBillDistributionMeterReading".............................................................................................15 2.6.2.3.4 Partner Reference "OptimumRouteMapforConsumerPartner"................................................................................................. 15 2.6.2.3.4.1 Interface "OptimumRouteMapforConsumer"........................................................................................................................ 15 2.6.2.4 Implementation............................................................................................................................................................................. 15 2.6.3 Import "NotifyMeterReplacementServiceImport1".............................................................................................................................15 2.6.3.1 General Settings........................................................................................................................................................................... 15 2.6.3.2 Interfaces...................................................................................................................................................................................... 16 2.6.3.2.1 Interface "NotifyMeterReplacementService".............................................................................................................................16 2.6.4 Import "NotifyTheftServiceImport1"...................................................................................................................................................16 2.6.4.1 General Settings........................................................................................................................................................................... 16 2.6.4.2 Interfaces...................................................................................................................................................................................... 16 2.6.4.2.1 Interface "NotifyTheftService"...................................................................................................................................................16 2.6.5 Import "OptimumRouteMapforConsumerImport1"............................................................................................................................ 16 2.6.5.1 General Settings........................................................................................................................................................................... 16 2.6.5.2 Interfaces...................................................................................................................................................................................... 17 2.6.5.2.1 Interface "OptimumRouteMapforConsumer"............................................................................................................................ 17 2.6.6 Import "OptimumroutemapforBillDistributionMeterReadingImport1".................................................................................................17 2.6.6.1 General Settings........................................................................................................................................................................... 17 2.6.6.2 Interfaces...................................................................................................................................................................................... 17 2.6.6.2.1 Interface "OptimumroutemapforBillDistributionMeterReading".................................................................................................17 3 Business Object Map "BusinessFault1Map"............................................................................................................................................. 18 3.1 Overview............................................................................................................................................................................................... 18 3.2 Business Object Map Settings.............................................................................................................................................................. 18 3.3 Transformation Objects......................................................................................................................................................................... 18 3.3.1 Input Objects..................................................................................................................................................................................... 18 3.3.2 Output Objects.................................................................................................................................................................................. 18 3.4 Transforms............................................................................................................................................................................................ 18 3.4.1 Transform - 1 "Join".......................................................................................................................................................................... 18 3.4.2 Transform - 2 "Move"........................................................................................................................................................................ 18 3.4.3 Transform - 3 "Assign"...................................................................................................................................................................... 19
-3-
Table of contents.
Nov 14, 2011
3.4.4 Transform - 4 "Assign"...................................................................................................................................................................... 19 4 Business Object Map "BusinessFaultMap"............................................................................................................................................... 20 4.1 Overview............................................................................................................................................................................................... 20 4.2 Business Object Map Settings.............................................................................................................................................................. 20 4.3 Transformation Objects......................................................................................................................................................................... 20 4.3.1 Input Objects..................................................................................................................................................................................... 20 4.3.2 Output Objects.................................................................................................................................................................................. 20 4.4 Transforms............................................................................................................................................................................................ 20 4.4.1 Transform - 1 "Join".......................................................................................................................................................................... 20 4.4.2 Transform - 2 "Move"........................................................................................................................................................................ 20 4.4.3 Transform - 3 "Assign"...................................................................................................................................................................... 21 4.4.4 Transform - 4 "Assign"...................................................................................................................................................................... 21 5 Business Object Map "ConsumerMapRequest"........................................................................................................................................ 22 5.1 Overview............................................................................................................................................................................................... 22 5.2 Business Object Map Settings.............................................................................................................................................................. 22 5.3 Transformation Objects......................................................................................................................................................................... 22 5.3.1 Input Objects..................................................................................................................................................................................... 22 5.3.2 Output Objects.................................................................................................................................................................................. 22 5.4 Transforms............................................................................................................................................................................................ 22 5.4.1 Transform - 1 "Move"........................................................................................................................................................................ 22 5.4.2 Transform - 2 "Move"........................................................................................................................................................................ 22 5.4.3 Transform - 3 "Move"........................................................................................................................................................................ 23 5.4.4 Transform - 4 "Move"........................................................................................................................................................................ 23 6 Business Object Map "NotifyMeterReplacementBOMap"......................................................................................................................... 24 6.1 Overview............................................................................................................................................................................................... 24 6.2 Business Object Map Settings.............................................................................................................................................................. 24 6.3 Transformation Objects......................................................................................................................................................................... 24 6.3.1 Input Objects..................................................................................................................................................................................... 24 6.3.2 Output Objects.................................................................................................................................................................................. 24 6.4 Transforms............................................................................................................................................................................................ 24 6.4.1 Transform - 1 "Move"........................................................................................................................................................................ 24 6.4.2 Transform - 2 "Move"........................................................................................................................................................................ 24 6.4.3 Transform - 3 "Move"........................................................................................................................................................................ 25 6.4.4 Transform - 4 "Move"........................................................................................................................................................................ 25 6.4.5 Transform - 5 "Move"........................................................................................................................................................................ 25 6.4.6 Transform - 6 "Move"........................................................................................................................................................................ 25 7 Business Object Map "NotifyMeterReplacementBusinessExMap"............................................................................................................26 7.1 Overview............................................................................................................................................................................................... 26 7.2 Business Object Map Settings.............................................................................................................................................................. 26 7.3 Transformation Objects......................................................................................................................................................................... 26 7.3.1 Input Objects..................................................................................................................................................................................... 26 7.3.2 Output Objects.................................................................................................................................................................................. 26 7.4 Transforms............................................................................................................................................................................................ 26 7.4.1 Transform - 1 "Move"........................................................................................................................................................................ 26 7.4.2 Transform - 2 "Move"........................................................................................................................................................................ 26 7.4.3 Transform - 3 "Assign"...................................................................................................................................................................... 26 7.4.4 Transform - 4 "Assign"...................................................................................................................................................................... 27 8 Business Object Map "NotifyMeterReplacementResponseBOMap"......................................................................................................... 28 8.1 Overview............................................................................................................................................................................................... 28 8.2 Business Object Map Settings.............................................................................................................................................................. 28 8.3 Transformation Objects......................................................................................................................................................................... 28 8.3.1 Input Objects..................................................................................................................................................................................... 28 8.3.2 Output Objects.................................................................................................................................................................................. 28 8.4 Transforms............................................................................................................................................................................................ 28 8.4.1 Transform - 1 "Move"........................................................................................................................................................................ 28 9 NotifyMeterReplacementRuntimeFault_res_1.map (NotifyMeterReplacementRuntimeFault_res_1)....................................................... 29 10 NotifyTheftGISFault_res_1.map (NotifyTheftGISFault_res_1)................................................................................................................ 30 11 Business Object Map "NotifyTheftRequestBOMap"................................................................................................................................ 31 11.1 Overview............................................................................................................................................................................................. 31 11.2 Business Object Map Settings............................................................................................................................................................ 31 11.3 Transformation Objects....................................................................................................................................................................... 31
-4-
Table of contents.
Nov 14, 2011
11.3.1 Input Objects................................................................................................................................................................................... 31 11.3.2 Output Objects................................................................................................................................................................................ 31 11.4 Transforms.......................................................................................................................................................................................... 31 11.4.1 Transform - 1 "Submap"..................................................................................................................................................................31 12 NotifyTheftRequestMapFail_req_1.map (NotifyTheftRequestMapFail_req_1)........................................................................................32 13 Business Object Map "NotifyTheftRequestSubMap"...............................................................................................................................33 13.1 Overview............................................................................................................................................................................................. 33 13.2 Business Object Map Settings............................................................................................................................................................ 33 13.3 Transformation Objects....................................................................................................................................................................... 33 13.3.1 Input Objects................................................................................................................................................................................... 33 13.3.2 Output Objects................................................................................................................................................................................ 33 13.4 Transforms.......................................................................................................................................................................................... 33 13.4.1 Transform - 1 "Move"...................................................................................................................................................................... 33 13.4.2 Transform - 2 "Move"...................................................................................................................................................................... 33 13.4.3 Transform - 3 "Move"...................................................................................................................................................................... 33 14 Business Object Map "NotifyTheftResponseBOMap"............................................................................................................................. 34 14.1 Overview............................................................................................................................................................................................. 34 14.2 Business Object Map Settings............................................................................................................................................................ 34 14.3 Transformation Objects....................................................................................................................................................................... 34 14.3.1 Input Objects................................................................................................................................................................................... 34 14.3.2 Output Objects................................................................................................................................................................................ 34 14.4 Transforms.......................................................................................................................................................................................... 34 14.4.1 Transform - 1 "Move"...................................................................................................................................................................... 34 15 Business Object Map "OptimumRouteMapConsumerRspMap"..............................................................................................................35 15.1 Overview............................................................................................................................................................................................. 35 15.2 Business Object Map Settings............................................................................................................................................................ 35 15.3 Transformation Objects....................................................................................................................................................................... 35 15.3.1 Input Objects................................................................................................................................................................................... 35 15.3.2 Output Objects................................................................................................................................................................................ 35 15.4 Transforms.......................................................................................................................................................................................... 35 15.4.1 Transform - 1 "Move"...................................................................................................................................................................... 35 15.4.2 Transform - 2 "Move"...................................................................................................................................................................... 35 15.4.3 Transform - 3 "Move"...................................................................................................................................................................... 36 15.4.4 Transform - 4 "Move"...................................................................................................................................................................... 36 16 Business Object Map "OptimumRouteMapReqMap".............................................................................................................................. 37 16.1 Overview............................................................................................................................................................................................. 37 16.2 Business Object Map Settings............................................................................................................................................................ 37 16.3 Transformation Objects....................................................................................................................................................................... 37 16.3.1 Input Objects................................................................................................................................................................................... 37 16.3.2 Output Objects................................................................................................................................................................................ 37 16.4 Transforms.......................................................................................................................................................................................... 37 16.4.1 Transform - 1 "Move"...................................................................................................................................................................... 37 17 Business Object Map "OptimumRouteMapRspMap".............................................................................................................................. 38 17.1 Overview............................................................................................................................................................................................. 38 17.2 Business Object Map Settings............................................................................................................................................................ 38 17.3 Transformation Objects....................................................................................................................................................................... 38 17.3.1 Input Objects................................................................................................................................................................................... 38 17.3.2 Output Objects................................................................................................................................................................................ 38 17.4 Transforms.......................................................................................................................................................................................... 38 17.4.1 Transform - 1 "Move"...................................................................................................................................................................... 38 17.4.2 Transform - 2 "Move"...................................................................................................................................................................... 38 17.4.3 Transform - 3 "Move"...................................................................................................................................................................... 38 17.4.4 Transform - 4 "Move"...................................................................................................................................................................... 39 17.4.5 Transform - 5 "Move"...................................................................................................................................................................... 39 17.4.6 Transform - 6 "Move"...................................................................................................................................................................... 39 18 XSLTransformation1_req_1.map (XSLTransformation1_req_1).............................................................................................................40 19 XSLTransformation1_res_1.map (XSLTransformation1_res_1)............................................................................................................. 41 20 XSLTransformation1_res_2.map (XSLTransformation1_res_2)............................................................................................................. 42 21 XSLTransformation2_req_1.map (XSLTransformation2_req_1).............................................................................................................43 22 XSLTransformation2_res_1.map (XSLTransformation2_res_1)............................................................................................................. 44 23 Mediation flow "RAPDRPBillingMeteringServiceModule"........................................................................................................................45
-5-
Table of contents.
Nov 14, 2011
23.1 Overview............................................................................................................................................................................................. 45 23.2 Source interfaces................................................................................................................................................................................ 45 23.2.1 Interface "MeteringBillingTxInf"....................................................................................................................................................... 45 23.2.2 Interface "OptimumRouteInf".......................................................................................................................................................... 45 23.3 References.......................................................................................................................................................................................... 45 23.3.1 Reference "NotifyTheftServicePartner"...........................................................................................................................................45 23.3.2 Reference "NotifyMeterReplacementServicePartner".....................................................................................................................46 23.3.3 Reference "OptimumroutemapforBillDistributionMeterReadingPartner".........................................................................................46 23.3.4 Reference "OptimumRouteMapforConsumerPartner".................................................................................................................... 46 23.4 Mediation flows....................................................................................................................................................................................46 23.4.1 Interface "MeteringBillingTxInf" operation "notifyTheftArea"........................................................................................................... 46 23.4.1.1 Request...................................................................................................................................................................................... 46 23.4.1.1.1 Input "notifyTheftArea : MeteringBillingTxInf"......................................................................................................................... 47 23.4.1.1.2 Input Response "notifyTheftArea : MeteringBillingTxInf"........................................................................................................ 48 23.4.1.1.3 Input Fault "notifyTheftArea : MeteringBillingTxInf"................................................................................................................ 48 23.4.1.1.4 Callout "getNotifyTheft : NotifyTheftServicePartner".............................................................................................................. 48 23.4.1.1.5 Custom Mediation "NotifyTheft Input".....................................................................................................................................49 23.4.1.1.6 Business Object Map "NotifyTheftReqMap"........................................................................................................................... 50 23.4.1.1.7 Custom Mediation "NotifyTheftGIS Request"......................................................................................................................... 51 23.4.1.1.8 XSL Transformation "NotifyTheftRequestMapFail".................................................................................................................52 23.4.1.2 Response....................................................................................................................................................................................53 23.4.1.2.1 Callout Response "getNotifyTheft : NotifyTheftServicePartner"............................................................................................. 53 23.4.1.2.2 Callout Fault "getNotifyTheft : NotifyTheftServicePartner"..................................................................................................... 54 23.4.1.2.3 Input Response "notifyTheftArea : MeteringBillingTxInf"........................................................................................................ 54 23.4.1.2.4 Input Fault "notifyTheftArea : MeteringBillingTxInf"................................................................................................................ 55 23.4.1.2.5 Custom Mediation "NotifyTheft Response".............................................................................................................................55 23.4.1.2.6 Business Object Map "NotifyTheft rsp map"...........................................................................................................................56 23.4.1.2.7 XSL Transformation "NotifyTheftGISFault".............................................................................................................................56 23.4.1.2.8 XSL Transformation "XSLTransformation1"........................................................................................................................... 57 23.4.1.2.9 Custom Mediation "CustomMediation1"................................................................................................................................. 58 23.4.1.2.10 Custom Mediation "CustomMediation11"............................................................................................................................. 59 23.4.2 Interface "MeteringBillingTxInf" operation "notifyMeterReplacement"............................................................................................ 60 23.4.2.1 Request...................................................................................................................................................................................... 60 23.4.2.1.1 Input "notifyMeterReplacement : MeteringBillingTxInf"...........................................................................................................61 23.4.2.1.2 Input Response "notifyMeterReplacement : MeteringBillingTxInf"......................................................................................... 61 23.4.2.1.3 Input Fault "notifyMeterReplacement : MeteringBillingTxInf"..................................................................................................62 23.4.2.1.4 Callout "getNotifyMeterReplacement : NotifyMeterReplacementServicePartner".................................................................. 62 23.4.2.1.5 Business Object Map "NotifyMeterReplacement Map"...........................................................................................................63 23.4.2.1.6 Custom Mediation "NotifyMeterReplacement request"...........................................................................................................63 23.4.2.2 Response....................................................................................................................................................................................64 23.4.2.2.1 Callout Response "getNotifyMeterReplacement : NotifyMeterReplacementServicePartner".................................................65 23.4.2.2.2 Callout Fault "getNotifyMeterReplacement : NotifyMeterReplacementServicePartner"......................................................... 66 23.4.2.2.3 Input Response "notifyMeterReplacement : MeteringBillingTxInf"......................................................................................... 66 23.4.2.2.4 Input Fault "notifyMeterReplacement : MeteringBillingTxInf"..................................................................................................67 23.4.2.2.5 Custom Mediation "NotifyMeterReplacement response"........................................................................................................67 23.4.2.2.6 Business Object Map "NotifyMeterReplacement response"...................................................................................................68 23.4.2.2.7 XSL Transformation "NotifyMeterReplacementRuntimeFault"............................................................................................... 69 23.4.2.2.8 Business Object Map "NotifyMeterReplacementBusinessEx"................................................................................................69 23.4.2.2.9 Custom Mediation "CustomMediation1"................................................................................................................................. 70 23.4.2.2.10 Custom Mediation "CustomMediation11"............................................................................................................................. 71 23.4.3 Interface "MeteringBillingTxInf" operation "optimumRouteMap"..................................................................................................... 72 23.4.3.1 Request...................................................................................................................................................................................... 72 23.4.3.1.1 Input "optimumRouteMap : MeteringBillingTxInf"................................................................................................................... 74 23.4.3.1.2 Input Response "optimumRouteMap : MeteringBillingTxInf".................................................................................................. 74 23.4.3.1.3 Input Fault "optimumRouteMap : MeteringBillingTxInf".......................................................................................................... 75 23.4.3.1.4 Callout "getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner".......................................................................................................................... 75 23.4.3.1.5 Custom Mediation "OptimumRouteReq"................................................................................................................................ 76 23.4.3.1.6 Custom Mediation "OptimumRouteReq1".............................................................................................................................. 77 23.4.3.1.7 Business Object Map "OptimumRouteRequestMap"..............................................................................................................78 23.4.3.1.8 Callout "getRouteMap : OptimumRouteMapforConsumerPartner".........................................................................................79 23.4.3.1.9 Custom Mediation "RouteMapRequest1"............................................................................................................................... 79
-6-
Table of contents.
Nov 14, 2011
23.4.3.1.10 Business Object Map "ConsumerMap".................................................................................................................................80 23.4.3.1.11 Custom Mediation "RouteMapRequest2"............................................................................................................................. 81 23.4.3.1.12 Message Filter "MessageFilter1".......................................................................................................................................... 82 23.4.3.1.13 XSL Transformation "XSLTransformation1"......................................................................................................................... 83 23.4.3.1.14 Custom Mediation "CustomMediation1"............................................................................................................................... 84 23.4.3.1.15 XSL Transformation "XSLTransformation2"......................................................................................................................... 85 23.4.3.1.16 Custom Mediation "CustomMediation2"............................................................................................................................... 86 23.4.3.2 Response....................................................................................................................................................................................87 23.4.3.2.1 Callout Response "getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner"..................................................................................................................................................................................................... 89 23.4.3.2.2 Callout Fault "getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner"................................................................................................................................................................................................................ 89 23.4.3.2.3 Input Response "optimumRouteMap : MeteringBillingTxInf".................................................................................................. 90 23.4.3.2.4 Input Fault "optimumRouteMap : MeteringBillingTxInf".......................................................................................................... 90 23.4.3.2.5 Custom Mediation "OptimumRouteReq"................................................................................................................................ 91 23.4.3.2.6 Custom Mediation "OptimumRouteReq1".............................................................................................................................. 92 23.4.3.2.7 Custom Mediation "OptimumRouteReq2".............................................................................................................................. 93 23.4.3.2.8 Custom Mediation "OptimumRouteReq3".............................................................................................................................. 94 23.4.3.2.9 Business Object Map "OptimumRouteMapRsp".....................................................................................................................95 23.4.3.2.10 Business Object Map "BusinessFault"..................................................................................................................................96 23.4.3.2.11 XSL Transformation "XSLTransformation1"......................................................................................................................... 96 23.4.3.2.12 Callout Response "getRouteMap : OptimumRouteMapforConsumerPartner"..................................................................... 97 23.4.3.2.13 Callout Fault "getRouteMap : OptimumRouteMapforConsumerPartner"..............................................................................98 23.4.3.2.14 Custom Mediation "OptimumRouteMapConsumer"............................................................................................................. 98 23.4.3.2.15 Business Object Map "OptimumRouteMapConsumer"........................................................................................................ 99 23.4.3.2.16 Custom Mediation "OptimumRouteMapConsumer2"......................................................................................................... 100 23.4.3.2.17 Business Object Map "BusineeFault1"............................................................................................................................... 101 23.4.3.2.18 XSL Transformation "XSLTransformation2"....................................................................................................................... 101 23.4.3.2.19 Custom Mediation "OptimumRouteMapConsumer3"......................................................................................................... 102 23.4.4 Interface "OptimumRouteInf" operation "optimumRouteDataService"..........................................................................................103 23.4.4.1 Request.................................................................................................................................................................................... 103 23.4.5 Interface "OptimumRouteInf" operation "optimumRouteMapService".......................................................................................... 103 23.4.5.1 Request.................................................................................................................................................................................... 103 24 Cross Reference....................................................................................................................................................................................104 25 Documentation generation settings....................................................................................................................................................... 109
-7-
Module "RAPDRPBillingMeteringServiceModule".
Nov 14, 2011
1 Module "RAPDRPBillingMeteringServiceModule"
1.1 Overview
1.2 All Resources

Assembly Diagram
- Assembly Diagram
Mediation Flows
- RAPDRPBillingMeteringServiceModule
Data Maps
- BusinessFault1Map - BusinessFaultMap - ConsumerMapRequest - NotifyMeterReplacementBOMap - NotifyMeterReplacementBusinessExMap - NotifyMeterReplacementResponseBOMap - NotifyMeterReplacementRuntimeFault_res_1 - NotifyTheftGISFault_res_1 - NotifyTheftRequestBOMap - NotifyTheftRequestMapFail_req_1 - NotifyTheftRequestSubMap - NotifyTheftResponseBOMap - OptimumRouteMapConsumerRspMap - OptimumRouteMapReqMap - OptimumRouteMapRspMap - XSLTransformation1_req_1 - XSLTransformation1_res_1 - XSLTransformation1_res_2 - XSLTransformation2_req_1 - XSLTransformation2_res_1
Exports
- MeteringBillingTxInfExport1
Imports
- NotifyMeterReplacementServiceImport1 - NotifyTheftServiceImport1
-8-
Module "RAPDRPBillingMeteringServiceModule".
- OptimumroutemapforBillDistributionMeterReadingImport1 - OptimumRouteMapforConsumerImport1
Nov 14, 2011
-9-
Assembly Diagram "RAPDRPBillingMeteringServiceModule".
Nov 14, 2011
2 Assembly Diagram "RAPDRPBillingMeteringServiceModule"

2.1 Overview
2.2 Assembly Diagram Settings

Name: RAPDRPBillingMeteringServiceModule
2.3 Component Overview

Exports
Display Name MeteringBillingTxInfExport1 Name MeteringBillingTxInfExport1 Binding Web Service Binding
Mediation Flows
Display Name RAPDRPBillingMeteringServiceModule Name RAPDRPBillingMeteringServiceModule Implementation RAPDRPBillingMeteringServiceModule.mfc
Imports
Display Name NotifyMeterReplacementServiceImport1 NotifyTheftServiceImport1 OptimumRouteMapforConsumerImport1 OptimumroutemapforBillDistributionMeterReadingImport1 Name NotifyMeterReplacementServiceImport1 NotifyTheftServiceImport1 OptimumRouteMapforConsumerImport1 OptimumroutemapforBillDistributionMeterReadingImport1 Binding Web Service Binding Web Service Binding Web Service Binding Web Service Binding
2.4 Wires
Component Wires
Source Component Name RAPDRPBillingMeteringServiceModule RAPDRPBillingMeteringServiceModule Reference Name NotifyTheftServicePartner Component Name NotifyTheftServiceImport1 Target Interface Name NotifyTheftService (http://www.upcl.com/NotifyTh eft) NotifyMeterReplacementService (http://www.upcl.com/NotifyMet erReplacementService)
NotifyMeterReplacementServi- NotifyMeterReplacementSercePartner viceImport1
- 10 -

Source Component Name RAPDRPBillingMeteringServiceModule Reference Name OptimumroutemapforBillDistributionMeterReadingPartner Component Name OptimumroutemapforBillDistributionMeterReadingImport1 Target Interface Name
Nov 14, 2011
OptimumroutemapforBillDistributionMeterReading (http://www.upcl.com/Optimum routemapforBillDistributionMeterReading) OptimumRouteMapforConsumer (http://www.upcl.com/Optimum RouteMapforConsumer)
RAPDRPBillingMeteringServiceModule
OptimumRouteMapforConsumerPartner
OptimumRouteMapforConsumerImport1
Export Wires
Export MeteringBillingTxInfExport1 Target RAPDRPBillingMeteringServiceModule Interface Name MeteringBillingTxInf
2.5 Quality of Service Qualifiers Overview

2.5.1 Asynchronous invocation
Node RAPDRPBillingMeteringServiceModule RAPDRPBillingMeteringServiceModule RAPDRPBillingMeteringServiceModule RAPDRPBillingMeteringServiceModule Where set Partner Reference "NotifyMeterReplacementServicePartner" Partner Reference "NotifyTheftServicePartner" Value commit commit
Partner Reference "OptimumRouteMapfor- commit ConsumerPartner" Partner Reference "Optimumroutemapfor- commit BillDistributionMeterReadingPartner"
2.5.2 Join transaction

Node NotifyMeterReplacementServiceImport1 NotifyTheftServiceImport1 OptimumRouteMapforConsumerImport1 OptimumroutemapforBillDistributionMeterReadingImport1 RAPDRPBillingMeteringServiceModule RAPDRPBillingMeteringServiceModule Where set Interface "NotifyMeterReplacementService" Interface "NotifyTheftService" Interface "OptimumRouteMapforConsumer" Interface "OptimumroutemapforBillDistributionMeterReading" Interface "MeteringBillingTxInf" Interface "OptimumRouteInf" Value false false false false true true
2.5.3 Reliability
Node RAPDRPBillingMeteringServiceModule RAPDRPBillingMeteringServiceModule RAPDRPBillingMeteringServiceModule RAPDRPBillingMeteringServiceModule Where set Partner Reference "NotifyMeterReplacementServicePartner" Partner Reference "NotifyTheftServicePartner" Value assured assured
Partner Reference "OptimumRouteMapfor- assured ConsumerPartner" Partner Reference "Optimumroutemapfor- assured BillDistributionMeterReadingPartner"
2.5.4 Suspend transaction

- 11 -

Node RAPDRPBillingMeteringServiceModule RAPDRPBillingMeteringServiceModule RAPDRPBillingMeteringServiceModule RAPDRPBillingMeteringServiceModule Where set Partner Reference "NotifyMeterReplacementServicePartner" Partner Reference "NotifyTheftServicePartner" Value false false
Nov 14, 2011
Partner Reference "OptimumRouteMapfor- false ConsumerPartner" Partner Reference "Optimumroutemapfor- false BillDistributionMeterReadingPartner"
2.6 Component Settings

2.6.1 Export "MeteringBillingTxInfExport1" 2.6.1.1 General Settings
Display name: Name: Target: Default endpoint reference: MeteringBillingTxInfExport1 MeteringBillingTxInfExport1 RAPDRPBillingMeteringServiceModule false
2.6.1.2 Interfaces 2.6.1.2.1 Interface "MeteringBillingTxInf"

Namespace: Preferred interaction style: http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf sync
Operations
notifyTheftArea notifyMeterReplacement optimumRouteMap
2.6.2 Mediation Flow "RAPDRPBillingMeteringServiceModule" 2.6.2.1 General Settings

Display name: Name: RAPDRPBillingMeteringServiceModule RAPDRPBillingMeteringServiceModule
2.6.2.2 Interfaces 2.6.2.2.1 Interface "MeteringBillingTxInf"

Namespace: Preferred interaction style: http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf any
Quality of service (QOS) Qualifiers: Join transaction

Value: true
Operations
notifyTheftArea notifyMeterReplacement optimumRouteMap
Operation "notifyTheftArea"
- 12 -

Inherited from: Value: MeteringBillingTxInf true
Nov 14, 2011
Operation "notifyMeterReplacement" Quality of service (QOS) Qualifiers: Join transaction

Operation "optimumRouteMap" Quality of service (QOS) Qualifiers: Join transaction

2.6.2.2.2 Interface "OptimumRouteInf"

Namespace: Preferred interaction style: http://upcl.com/RAPDRPBillingMeteringServiceLib/inf/OptimumRouteInf any

Value: true
Operations
optimumRouteDataService optimumRouteMapService
Operation "optimumRouteDataService" Quality of service (QOS) Qualifiers: Join transaction

Inherited from: Value: OptimumRouteInf true
Operation "optimumRouteMapService" Quality of service (QOS) Qualifiers: Join transaction

Inherited from: Value: OptimumRouteInf true
2.6.2.3 References 2.6.2.3.1 Partner Reference "NotifyTheftServicePartner"

Interface Multiplicity: NotifyTheftService 1..1
Wires:
Target NotifyTheftServiceImport1 Interface Name NotifyTheftService (http://www.upcl.com/NotifyTheft)
- 13 -

Quality of service (QOS) Qualifiers: Suspend transaction
Value: false
Nov 14, 2011
Asynchronous invocation
Value: commit
Reliability
Value: assured
2.6.2.3.1.1 Interface "NotifyTheftService"

Namespace: Preferred interaction style: http://www.upcl.com/NotifyTheft any
Operations
getNotifyTheft
2.6.2.3.2 Partner Reference "NotifyMeterReplacementServicePartner"

Interface Multiplicity: NotifyMeterReplacementService 1..1
Wires:
Target NotifyMeterReplacementServiceImport1 Interface Name NotifyMeterReplacementService (http://www.upcl.com/NotifyMeterReplacementService)

Value: false
Value: commit
Reliability
Value: assured
2.6.2.3.2.1 Interface "NotifyMeterReplacementService"

Namespace: Preferred interaction style: http://www.upcl.com/NotifyMeterReplacementService any
Operations
getNotifyMeterReplacement
2.6.2.3.3 Partner Reference "OptimumroutemapforBillDistributionMeterReadingPartner"

Interface Multiplicity: OptimumroutemapforBillDistributionMeterReading 1..1
Wires:
Target OptimumroutemapforBillDistributionMeterReadingImport1 Interface Name OptimumroutemapforBillDistributionMeterReading (http://www.upcl.com/OptimumroutemapforBillDistributionMeter Reading)
- 14 -

Value: false
Nov 14, 2011
Value: commit
Reliability
Value: assured
2.6.2.3.3.1 Interface "OptimumroutemapforBillDistributionMeterReading"

Namespace: Preferred interaction style: http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading any
Operations
getOptimumroutemapforBillDistributionMeterReading
2.6.2.3.4 Partner Reference "OptimumRouteMapforConsumerPartner"

Interface Multiplicity: OptimumRouteMapforConsumer 1..1
Wires:
Target OptimumRouteMapforConsumerImport1 Interface Name OptimumRouteMapforConsumer (http://www.upcl.com/OptimumRouteMapforConsumer)

Value: false
Value: commit
Reliability
Value: assured
2.6.2.3.4.1 Interface "OptimumRouteMapforConsumer"

Namespace: Preferred interaction style: http://www.upcl.com/OptimumRouteMapforConsumer any
Operations
getRouteMap
2.6.2.4 Implementation
Mediation Flow: RAPDRPBillingMeteringServiceModule.mfc Contains the mediation flow logic and implementation
Quality of service (QOS) Qualifiers: Transaction

Value: Local transaction boundary global activitySession
2.6.3 Import "NotifyMeterReplacementServiceImport1" 2.6.3.1 General Settings

Display name: Name: NotifyMeterReplacementServiceImport1 NotifyMeterReplacementServiceImport1
- 15 -
Nov 14, 2011
2.6.3.2 Interfaces 2.6.3.2.1 Interface "NotifyMeterReplacementService"

Namespace: Preferred interaction style: http://www.upcl.com/NotifyMeterReplacementService sync

Value: false
Operations
getNotifyMeterReplacement
Operation "getNotifyMeterReplacement" Quality of service (QOS) Qualifiers: Join transaction

Inherited from: Value: NotifyMeterReplacementService false
2.6.4 Import "NotifyTheftServiceImport1" 2.6.4.1 General Settings

Display name: Name: NotifyTheftServiceImport1 NotifyTheftServiceImport1
2.6.4.2 Interfaces 2.6.4.2.1 Interface "NotifyTheftService"

Namespace: Preferred interaction style: http://www.upcl.com/NotifyTheft sync

Value: false
Operations
getNotifyTheft
Operation "getNotifyTheft" Quality of service (QOS) Qualifiers: Join transaction

Inherited from: Value: NotifyTheftService false
2.6.5 Import "OptimumRouteMapforConsumerImport1" 2.6.5.1 General Settings

Display name: Name: OptimumRouteMapforConsumerImport1 OptimumRouteMapforConsumerImport1
- 16 -
Nov 14, 2011
2.6.5.2 Interfaces 2.6.5.2.1 Interface "OptimumRouteMapforConsumer"

Namespace: Preferred interaction style: http://www.upcl.com/OptimumRouteMapforConsumer sync

Value: false
Operations
getRouteMap
Operation "getRouteMap" Quality of service (QOS) Qualifiers: Join transaction

Inherited from: Value: OptimumRouteMapforConsumer false
2.6.6 Import "OptimumroutemapforBillDistributionMeterReadingImport1" 2.6.6.1 General Settings

Display name: Name: OptimumroutemapforBillDistributionMeterReadingImport1 OptimumroutemapforBillDistributionMeterReadingImport1
2.6.6.2 Interfaces 2.6.6.2.1 Interface "OptimumroutemapforBillDistributionMeterReading"

Namespace: Preferred interaction style: http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading sync

Value: false
Operations
getOptimumroutemapforBillDistributionMeterReading
Operation "getOptimumroutemapforBillDistributionMeterReading" Quality of service (QOS) Qualifiers: Join transaction

Inherited from: Value: OptimumroutemapforBillDistributionMeterReading false
- 17 -
Business Object Map "BusinessFault1Map".
Nov 14, 2011
3 Business Object Map "BusinessFault1Map"

3.1 Overview
3.2 Business Object Map Settings

Name: Namespace: BusinessFault1Map http://RAPDRPBillingMeteringServiceModule
3.3 Transformation Objects

3.3.1 Input Objects
Name GISFaultInfo Namespace Variable name smo://smo/name=wsdl-body/message=%7Bhttp%3 GISFaultInfo A%2F%2Fwww.upcl.com%2FOptimumRouteMapfor Consumer%7DGISFaultInfo/xpath=%2Fbody/namespac e=BOMap/smo.xsd
3.3.2 Output Objects

Name Namespace Variable name optimumsmo://smo/name=wsdl-body/message=%7Bhttp%3 optimumRouteMap_optimumRouteMapFaultMs A%2F%2Fupcl.com%2FRAPDRPBillingMeteringSer RouteMap_optimumRouteMapFaultMs g viceLg ib%2FBillingTxInf%7DoptimumRouteMap_optimum RouteMapFaultMsg/ xpath=%2Fbody/namespace=BOMap/smo.xsd
3.4 Transforms
3.4.1 Transform - 1 "Join"
Execution Order: Transform Type: Sources: Target: Default delimiter (in []): Source GISFaultInfo/GISFaultInfo/message GISFaultInfo/GISFaultInfo/faultInfoBean/userMessage 1 Join GISFaultInfo/GISFaultInfo/message GISFaultInfo/GISFaultInfo/faultInfoBean/userMessage optimumRouteMap_optimumRouteMapFaultMsg/operation1Fault1_optimumRouteMapFault/FaultStrin g [] Delimiter (in []) [] []
3.4.2 Transform - 2 "Move"

Execution Order: Transform Type: 2 Move
- 18 -
Business Object Map "BusinessFault1Map".

Source: Target:
Nov 14, 2011
GISFaultInfo/GISFaultInfo/faultInfoBean/errorCode optimumRouteMap_optimumRouteMapFaultMsg/operation1Fault1_optimumRouteMapFault/FaultCod e
3.4.3 Transform - 3 "Assign"

Execution Order: Transform Type: Target: Assign Type: Value: 3 Assign optimumRouteMap_optimumRouteMapFaultMsg/operation1Fault1_optimumRouteMapFault/TxName User defined value Optimum Route Map for Consumers

Execution Order: Transform Type: Target: Assign Type: Value: 4 Assign optimumRouteMap_optimumRouteMapFaultMsg/operation1Fault1_optimumRouteMapFault/FaultOrigi nator User defined value GIS Application
- 19 -
Business Object Map "BusinessFaultMap".
Nov 14, 2011
4 Business Object Map "BusinessFaultMap"

4.1 Overview

Name: Namespace: BusinessFaultMap http://RAPDRPBillingMeteringServiceModule

4.3.1 Input Objects
Name GISFaultInfo Namespace smo://smo/name=wsdl-body/message=%7Bhttp%3 A%2F%2Fwww.upcl.com%2FOptimumroutemapfor BillDistributionMeterReading%7DGISFaultInfo/xpath=%2Fbody/namespace= BOMap/smo.xsd Variable name GISFaultInfo

Name Namespace Variable name optimumsmo://smo/name=wsdl-body/message=%7Bhttp%3 optimumRouteMap_optimumRouteMapFaultMs A%2F%2Fupcl.com%2FRAPDRPBillingMeteringSer RouteMap_optimumRouteMapFaultMs g viceLg ib%2FBillingTxInf%7DoptimumRouteMap_optimum RouteMapFaultMsg/ xpath=%2Fbody/namespace=BOMap/smo.xsd
4.4 Transforms
4.4.1 Transform - 1 "Join"
Execution Order: Transform Type: Sources: Target: Default delimiter (in []): Source GISFaultInfo/GISFaultInfo/message GISFaultInfo/GISFaultInfo/faultInfoBean/userMessage 1 Join GISFaultInfo/GISFaultInfo/message GISFaultInfo/GISFaultInfo/faultInfoBean/userMessage optimumRouteMap_optimumRouteMapFaultMsg/operation1Fault1_optimumRouteMapFault/FaultStrin g [] Delimiter (in []) [] []

Execution Order: Transform Type: 2 Move
- 20 -
Business Object Map "BusinessFaultMap".

Source: Target:
Nov 14, 2011
GISFaultInfo/GISFaultInfo/faultInfoBean/errorCode optimumRouteMap_optimumRouteMapFaultMsg/operation1Fault1_optimumRouteMapFault/FaultCod e

Execution Order: Transform Type: Target: Assign Type: Value: 3 Assign optimumRouteMap_optimumRouteMapFaultMsg/operation1Fault1_optimumRouteMapFault/TxName User defined value Optimum Route Map

Execution Order: Transform Type: Target: Assign Type: Value: 4 Assign optimumRouteMap_optimumRouteMapFaultMsg/operation1Fault1_optimumRouteMapFault/FaultOrigi nator User defined value GIS Application
- 21 -
Business Object Map "ConsumerMapRequest".
Nov 14, 2011
5 Business Object Map "ConsumerMapRequest"

5.1 Overview

Name: Namespace: ConsumerMapRequest http://RAPDRPBillingMeteringServiceModule

5.3.1 Input Objects
Name optimumRouteMapRequestMsg Namespace Variable name smo://smo/name=wsdl-body/message=%7Bhttp%3 optimumRouteMapRequestMsg A%2F%2Fupcl.com%2FRAPDRPBillingMeteringSer viceLib%2FBillingTxInf%7DoptimumRouteMapRequestM sg/xpath=%2Fbody/namespace=BOMap/smo.xsd

Name getRouteMap Namespace Variable name smo://smo/name=wsdl-body/message=%7Bhttp%3 getRouteMap A%2F%2Fwww.upcl.com%2FOptimumRouteMapfor Consumer%7DgetRouteMap/xpath=%2Fbody/namespa ce=BOMap/smo.xsd
5.4 Transforms
Execution Order: Transform Type: Source: Target: 1 Move optimumRouteMapRequestMsg/optimumRouteMap/optimumRootMapRequest/forConsumer/CIN getRouteMap/getRouteMap/optimumrouteinput/CIN

Execution Order: 2
- 22 -
Business Object Map "ConsumerMapRequest".

Transform Type: Source: Target: Move optimumRouteMapRequestMsg/optimumRouteMap/optimumRootMapRequest/forConsumer/Reg_No getRouteMap/getRouteMap/optimumrouteinput/reg_Id
Nov 14, 2011

Execution Order: Transform Type: Source: Target: 3 Move optimumRouteMapRequestMsg/optimumRouteMap/optimumRootMapRequest/forConsumer/options getRouteMap/getRouteMap/optimumrouteinput/OPTION

Execution Order: Transform Type: Source: Target: 4 Move optimumRouteMapRequestMsg/optimumRouteMap/optimumRootMapRequest/forConsumer/SS_AIN getRouteMap/getRouteMap/optimumrouteinput/ss_Ain
- 23 -
Business Object Map "NotifyMeterReplacementBOMap".
Nov 14, 2011
6 Business Object Map "NotifyMeterReplacementBOMap"

6.1 Overview

Name: Namespace: NotifyMeterReplacementBOMap http://RAPDRPBillingMeteringServiceModule

6.3.1 Input Objects
Name notifyMeterReplacementRequestMsg Namespace Variable name smo://smo/name=wsdl-body/message=%7Bhttp%3 notifyMeterReplacementRequestMsg A%2F%2Fupcl.com%2FRAPDRPBillingMeteringSer viceLib%2FBillingTxInf%7DnotifyMeterReplacementRequ estMsg/ xpath=%2Fbody/namespace=BOMap/smo.xsd

Name getNotifyMeterReplacement Namespace Variable name smo://smo/name=wsdl-body/message=%7Bhttp%3 getNotifyMeterReplacement A%2F%2Fwww.upcl.com%2FNotifyMeterReplacem entService%7DgetNotifyMeterReplacement/xpath=%2Fbo dy/namespace=BOMap/smo.xsd
6.4 Transforms
Execution Order: Transform Type: Source: Target: 1 Move notifyMeterReplacementRequestMsg/notifyMeterReplacement/notifyMeterReplacementRequest/meterDetails/CIN getNotifyMeterReplacement/getNotifyMeterReplacement/CIN

Execution Order: Transform Type: Source: Target: 2 Move notifyMeterReplacementRequestMsg/notifyMeterReplacement/notifyMeterReplacementRequest/meterDetails/MeterSerialNo getNotifyMeterReplacement/getNotifyMeterReplacement/MeterNumber
- 24 -
Business Object Map "NotifyMeterReplacementBOMap".
Nov 14, 2011

Execution Order: Transform Type: Source: Target: 3 Move notifyMeterReplacementRequestMsg/notifyMeterReplacement/notifyMeterReplacementRequest/meterDetails/MeterMake getNotifyMeterReplacement/getNotifyMeterReplacement/MeterMake

Execution Order: Transform Type: Source: Target: 4 Move notifyMeterReplacementRequestMsg/notifyMeterReplacement/notifyMeterReplacementRequest/meterDetails/MeterType getNotifyMeterReplacement/getNotifyMeterReplacement/MeterType

Execution Order: Transform Type: Source: Target: 5 Move notifyMeterReplacementRequestMsg/notifyMeterReplacement/notifyMeterReplacementRequest/meterDetails/MeterClass getNotifyMeterReplacement/getNotifyMeterReplacement/MeterClass

Execution Order: Transform Type: Source: Target: 6 Move notifyMeterReplacementRequestMsg/notifyMeterReplacement/notifyMeterReplacementRequest/meterDetails/InstallationDate getNotifyMeterReplacement/getNotifyMeterReplacement/MeterInstallationDate
- 25 -
Business Object Map "NotifyMeterReplacementBusinessExMap".
Nov 14, 2011
7 Business Object Map "NotifyMeterReplacementBusinessExMap"

7.1 Overview

Name: Namespace: NotifyMeterReplacementBusinessExMap http://RAPDRPBillingMeteringServiceModule

7.3.1 Input Objects
Name GISFaultInfo Namespace Variable name smo://smo/name=wsdl-body/message=%7Bhttp%3 GISFaultInfo A%2F%2Fwww.upcl.com%2FNotifyMeterReplacem entService%7DGISFaultInfo/xpath=%2Fbody/namespace= BOMap/smo.xsd

Name Namespace Variable name notifyMeterReplacesmo://smo/name=wsdl-body/message=%7Bhttp%3 notifyMeterReplacement_notifyMeterReplacementFaultMs A%2F%2Fupcl.com%2FRAPDRPBillingMeteringSer ment_notifyMeterReplacementFaultMs g viceLg ib%2FBillingTxInf%7DnotifyMeterReplacement_noti fyMeterReplacementFaultMsg/ xpath=%2Fbody/namespace=BOMap/smo.xsd
7.4 Transforms
Execution Order: Transform Type: Source: Target: 1 Move GISFaultInfo/GISFaultInfo/faultInfoBean/errorCode notifyMeterReplacement_notifyMeterReplacementFaultMsg/operation1Fault1_replaceMeterFault/FaultCode

Execution Order: Transform Type: Source: Target: 2 Move GISFaultInfo/GISFaultInfo/faultInfoBean/userMessage notifyMeterReplacement_notifyMeterReplacementFaultMsg/operation1Fault1_replaceMeterFault/FaultString

Execution Order: Transform Type: 3 Assign
- 26 -
Business Object Map "NotifyMeterReplacementBusinessExMap".

Target: Assign Type: Value:
Nov 14, 2011
notifyMeterReplacement_notifyMeterReplacementFaultMsg/operation1Fault1_replaceMeterFault/FaultOriginator User defined value GIS Application

Execution Order: Transform Type: Target: Assign Type: Value: 4 Assign notifyMeterReplacement_notifyMeterReplacementFaultMsg/operation1Fault1_replaceMeterFault/TxName User defined value Notify Meter Replacement Tx
- 27 -
Business Object Map "NotifyMeterReplacementResponseBOMap".
Nov 14, 2011
8 Business Object Map "NotifyMeterReplacementResponseBOMap"

8.1 Overview

Name: Namespace: NotifyMeterReplacementResponseBOMap http://RAPDRPBillingMeteringServiceModule

8.3.1 Input Objects
Name Namespace Variable name getNotifyMeterReplacementResponse smo://smo/name=wsdl-body/message=%7Bhttp%3 getNotifyMeterReplacementResponse A%2F%2Fwww.upcl.com%2FNotifyMeterReplacem entService%7DgetNotifyMeterReplacementResponse/xpat h=%2Fbody/namespace=BOMap/smo.xsd

Name notifyMeterReplacementResponseMsg Namespace Variable name smo://smo/name=wsdl-body/message=%7Bhttp%3 notifyMeterReplacementResponA%2F%2Fupcl.com%2FRAPDRPBillingMeteringSer seMsg viceLib%2FBillingTxInf%7DnotifyMeterReplacementResp onseMsg/ xpath=%2Fbody/namespace=BOMap/smo.xsd
8.4 Transforms
Execution Order: Transform Type: Source: Target: 1 Move getNotifyMeterReplacementResponse/getNotifyMeterReplacementResponse/return/successFlag notifyMeterReplacementResponseMsg/notifyMeterReplacementResponse/notifyMeterReplacementResponse/meterDetails/updateStatus
- 28 -
NotifyMeterReplacementRuntimeFault_res_1.map (NotifyMeterReplacementRuntimeFault_res_1).
Nov 14,
9 NotifyMeterReplacementRuntimeFault_res_1.map (NotifyMeterReplacementRuntimeFault_res_1)
Documentation Unit plug-in could not create a chapter of the documentation on the base of NotifyMeterReplacementRuntimeFault_res_1.map.
- 29 -
NotifyTheftGISFault_res_1.map (NotifyTheftGISFault_res_1).
Nov 14, 2011
10 NotifyTheftGISFault_res_1.map (NotifyTheftGISFault_res_1)
Documentation Unit plug-in could not create a chapter of the documentation on the base of NotifyTheftGISFault_res_1.map.
- 30 -
Business Object Map "NotifyTheftRequestBOMap".
Nov 14, 2011
11 Business Object Map "NotifyTheftRequestBOMap"

11.1 Overview

Name: Namespace: NotifyTheftRequestBOMap http://RAPDRPBillingMeteringServiceModule

11.3.1 Input Objects
Name notifyTheftAreaRequestMsg Namespace Variable name smo://smo/name=wsdl-body/message=%7Bhttp%3 notifyTheftAreaRequestMsg A%2F%2Fupcl.com%2FRAPDRPBillingMeteringSer viceLib%2FBillingTxInf%7DnotifyTheftAreaRequestMsg/x path=%2Fbody/namespace=BOMap/smo.xsd

Name getNotifyTheft Namespace Variable name smo://smo/name=wsdl-body/message=%7Bhttp%3 getNotifyTheft A%2F%2Fwww.upcl.com%2FNotifyTheft%7DgetNo tifyTheft/ xpath=%2Fbody/namespace=BOMap/smo.xsd
11.4 Transforms
11.4.1 Transform - 1 "Submap"
Execution Order: Transform Type: Submap Name: 1 Submap NotifyTheftRequestSubMap {http://RAPDRPBillingMeteringServiceModule}
Submap inputs
Transform Source notifyTheftAreaRequestMsg/notifyTheftArea/notifyTheftRequest/notifyTheftList/notifyTheft Submap input variable NotifyTheft
Submap outputs
Transform Target getNotifyTheft/getNotifyTheft/NotifyTheft Submap output variable notifyTheftInput
- 31 -
NotifyTheftRequestMapFail_req_1.map (NotifyTheftRequestMapFail_req_1).
Nov 14, 2011
12 NotifyTheftRequestMapFail_req_1.map (NotifyTheftRequestMapFail_req_1)
Documentation Unit plug-in could not create a chapter of the documentation on the base of NotifyTheftRequestMapFail_req_1.map.
- 32 -
Business Object Map "NotifyTheftRequestSubMap".
Nov 14, 2011
13 Business Object Map "NotifyTheftRequestSubMap"

13.1 Overview

Name: Namespace: NotifyTheftRequestSubMap http://RAPDRPBillingMeteringServiceModule

Name NotifyTheft Namespace http://upcl.com/RAPDRPBillingServiceLib/BOs Variable name NotifyTheft

Name notifyTheftInput Namespace http://www.upcl.com/NotifyTheft Variable name notifyTheftInput
13.4 Transforms
Execution Order: Transform Type: Source: Target: 1 Move NotifyTheft/AreaCode notifyTheftInput/areaID

Execution Order: Transform Type: Source: Target: 2 Move NotifyTheft/CIN notifyTheftInput/CIN

Execution Order: Transform Type: Source: Target: 3 Move NotifyTheft/AIN notifyTheftInput/AIN
- 33 -
Business Object Map "NotifyTheftResponseBOMap".
Nov 14, 2011
14 Business Object Map "NotifyTheftResponseBOMap"

14.1 Overview

Name: Namespace: NotifyTheftResponseBOMap http://RAPDRPBillingMeteringServiceModule

Name getNotifyTheftResponse Namespace Variable name smo://smo/name=wsdl-body/message=%7Bhttp%3 getNotifyTheftResponse A%2F%2Fwww.upcl.com%2FNotifyTheft%7DgetNo tifyTheftResponse/ xpath=%2Fbody/namespace=BOMap/smo.xsd

Name notifyTheftAreaResponseMsg Namespace Variable name smo://smo/name=wsdl-body/message=%7Bhttp%3 notifyTheftAreaResponseMsg A%2F%2Fupcl.com%2FRAPDRPBillingMeteringSer viceLib%2FBillingTxInf%7DnotifyTheftAreaResponseMsg /xpath=%2Fbody/namespace=BOMap/smo.xsd
14.4 Transforms
Execution Order: Transform Type: Source: Target: 1 Move getNotifyTheftResponse/getNotifyTheftResponse/return/successFlag notifyTheftAreaResponseMsg/notifyTheftAreaResponse/notifyTheftResponse/notifyTheftList/sucessFlag
- 34 -
Business Object Map "OptimumRouteMapConsumerRspMap".
Nov 14, 2011
15 Business Object Map "OptimumRouteMapConsumerRspMap"

15.1 Overview

Name: Namespace: OptimumRouteMapConsumerRspMap http://RAPDRPBillingMeteringServiceModule

Name getRouteMapResponse Namespace Variable name smo://smo/name=wsdl-body/message=%7Bhttp%3 getRouteMapResponse A%2F%2Fwww.upcl.com%2FOptimumRouteMapfor Consumer%7DgetRouteMapResponse/xpath=%2Fbody /namespace=BOMap/smo.xsd

Name optimumRouteMapResponseMsg Namespace Variable name smo://smo/name=wsdl-body/message=%7Bhttp%3 optimumRouteMapResponseMsg A%2F%2Fupcl.com%2FRAPDRPBillingMeteringSer viceLib%2FBillingTxInf%7DoptimumRouteMapResponse Msg/xpath=%2Fbody/namespace=BOMap/smo.xsd
15.4 Transforms
Execution Order: Transform Type: Source: Target: 1 Move getRouteMapResponse/getRouteMapResponse/return/CIN optimumRouteMapResponseMsg/optimumRouteMapResponse/optimumRouteMapResponse/forConsumer/CIN

Execution Order: Transform Type: Source: 2 Move getRouteMapResponse/getRouteMapResponse/return/FLAG
- 35 -
Business Object Map "OptimumRouteMapConsumerRspMap".

Target: optimumRouteMapResponseMsg/optimumRouteMapResponse/optimumRouteMapResponse/forConsumer/options
Nov 14, 2011

Execution Order: Transform Type: Source: Target: 3 Move getRouteMapResponse/getRouteMapResponse/return/reg_Id optimumRouteMapResponseMsg/optimumRouteMapResponse/optimumRouteMapResponse/forConsumer/Reg_No

Execution Order: Transform Type: Source: Target: 4 Move getRouteMapResponse/getRouteMapResponse/return/URL optimumRouteMapResponseMsg/optimumRouteMapResponse/optimumRouteMapResponse/forConsumer/mapURL
- 36 -
Business Object Map "OptimumRouteMapReqMap".
Nov 14, 2011
16 Business Object Map "OptimumRouteMapReqMap"

16.1 Overview

Name: Namespace: OptimumRouteMapReqMap http://RAPDRPBillingMeteringServiceModule

Name optimumRouteMapRequestMsg Namespace Variable name smo://smo/name=wsdl-body/message=%7Bhttp%3 optimumRouteMapRequestMsg A%2F%2Fupcl.com%2FRAPDRPBillingMeteringSer viceLib%2FBillingTxInf%7DoptimumRouteMapRequestM sg/xpath=%2Fbody/namespace=BOMap/smo.xsd

Name getOptimumroutemapforBillDistributionMeterReading Namespace Variable name smo://smo/name=wsdl-body/message=%7Bhttp%3 getOptimumroutemapforBillDistribuA%2F%2Fwww.upcl.com%2FOptimumroutemapfor tionMeterReading BillDistributionMeterReading%7DgetOptimumroutemapforBillDistributionMete rReading/ xpath=%2Fbody/namespace=BOMap/smo.xsd
16.4 Transforms
Execution Order: Transform Type: Source: Target: 1 Move optimumRouteMapRequestMsg/optimumRouteMap/optimumRootMapRequest/DTR_AIN getOptimumroutemapforBillDistributionMeterReading/getOptimumroutemapforBillDistributionMeterReading/RoutemapinputRequest/DTRAIN
- 37 -
Business Object Map "OptimumRouteMapRspMap".
Nov 14, 2011
17 Business Object Map "OptimumRouteMapRspMap"

17.1 Overview

Name: Namespace: OptimumRouteMapRspMap http://RAPDRPBillingMeteringServiceModule

Name getOptimumroutemapforBillDistributionMeterReadingResponse Namespace Variable name smo://smo/name=wsdl-body/message=%7Bhttp%3 getOptimumroutemapforBillDistribuA%2F%2Fwww.upcl.com%2FOptimumroutemapfor tionMeterReadingResponse BillDistributionMeterReading%7DgetOptimumroutemapforBillDistributionMete rReadingResponse/ xpath=%2Fbody/namespace=BOMap/smo.xsd

Name optimumRouteMapResponseMsg Namespace Variable name smo://smo/name=wsdl-body/message=%7Bhttp%3 optimumRouteMapResponseMsg A%2F%2Fupcl.com%2FRAPDRPBillingMeteringSer viceLib%2FBillingTxInf%7DoptimumRouteMapResponse Msg/xpath=%2Fbody/namespace=BOMap/smo.xsd
17.4 Transforms
Execution Order: Transform Type: Source: Target: 1 Move getOptimumroutemapforBillDistributionMeterReadingResponse/getOptimumroutemapforBillDistributionMeterReadingResponse/RoutemapOutPutResponse/DISTANCE optimumRouteMapResponseMsg/optimumRouteMapResponse/optimumRouteMapResponse/Distence

Execution Order: Transform Type: Source: Target: 2 Move getOptimumroutemapforBillDistributionMeterReadingResponse/getOptimumroutemapforBillDistributionMeterReadingResponse/RoutemapOutPutResponse/ENDPOINT optimumRouteMapResponseMsg/optimumRouteMapResponse/optimumRouteMapResponse/EndPoint

- 38 -
Business Object Map "OptimumRouteMapRspMap".

Execution Order: Transform Type: Source: Target:
Nov 14, 2011
3 Move getOptimumroutemapforBillDistributionMeterReadingResponse/getOptimumroutemapforBillDistributionMeterReadingResponse/RoutemapOutPutResponse/NOOFCONSUMER optimumRouteMapResponseMsg/optimumRouteMapResponse/optimumRouteMapResponse/NoOfConsumers

Execution Order: Transform Type: Source: Target: 4 Move getOptimumroutemapforBillDistributionMeterReadingResponse/getOptimumroutemapforBillDistributionMeterReadingResponse/RoutemapOutPutResponse/STARTPOINT optimumRouteMapResponseMsg/optimumRouteMapResponse/optimumRouteMapResponse/StartPoint

Execution Order: Transform Type: Source: Target: 5 Move getOptimumroutemapforBillDistributionMeterReadingResponse/getOptimumroutemapforBillDistributionMeterReadingResponse/RoutemapOutPutResponse/SUCCESSFLAG optimumRouteMapResponseMsg/optimumRouteMapResponse/optimumRouteMapResponse/flag

Execution Order: Transform Type: Source: Target: 6 Move getOptimumroutemapforBillDistributionMeterReadingResponse/getOptimumroutemapforBillDistributionMeterReadingResponse/RoutemapOutPutResponse/URL optimumRouteMapResponseMsg/optimumRouteMapResponse/optimumRouteMapResponse/mapURL
- 39 -
XSLTransformation1_req_1.map (XSLTransformation1_req_1).
Nov 14, 2011
18 XSLTransformation1_req_1.map (XSLTransformation1_req_1)
Documentation Unit plug-in could not create a chapter of the documentation on the base of XSLTransformation1_req_1.map.
- 40 -
XSLTransformation1_res_1.map (XSLTransformation1_res_1).
Nov 14, 2011
19 XSLTransformation1_res_1.map (XSLTransformation1_res_1)
Documentation Unit plug-in could not create a chapter of the documentation on the base of XSLTransformation1_res_1.map.
- 41 -
Nov 14, 2011
- 42 -
XSLTransformation2_req_1.map (XSLTransformation2_req_1).
Nov 14, 2011
21 XSLTransformation2_req_1.map (XSLTransformation2_req_1)
Documentation Unit plug-in could not create a chapter of the documentation on the base of XSLTransformation2_req_1.map.
- 43 -
Nov 14, 2011
- 44 -
Mediation flow "RAPDRPBillingMeteringServiceModule".
Nov 14, 2011
23 Mediation flow "RAPDRPBillingMeteringServiceModule"

23.1 Overview
23.2 Source interfaces

23.2.1 Interface "MeteringBillingTxInf"
Namespace: http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf
Operations
Operation name Property Connected to Reference notifyTheftArea notifyMeterReplacement optimumRouteMap optimumRouteMap request response request response request response request response NotifyTheftServicePartner Operation getNotifyTheft
NotifyMeterReplacementServi- getNotifyMeterReplacement cePartner OptimumroutemapforBillDistributionMeterReadingPartner OptimumRouteMapforConsumerPartner getOptimumroutemapforBillDistributionMeterReading getRouteMap
23.2.2 Interface "OptimumRouteInf"

Namespace: http://upcl.com/RAPDRPBillingMeteringServiceLib/inf/OptimumRouteInf
Operations
Operation name Property Connected to Reference optimumRouteDataService optimumRouteMapService request response request response Operation
23.3 References
23.3.1 Reference "NotifyTheftServicePartner"
Namespace: Interface: http://www.upcl.com/NotifyTheft NotifyTheftService
Operations
- 45 -

Operation name Property Connected from Interface getNotifyTheft request response Operation
Nov 14, 2011
MeteringBillingTxInf notifyTheftArea (http://upcl.com/RAPDRPBillin gMeteringServiceLib/BillingTxInf)
23.3.2 Reference "NotifyMeterReplacementServicePartner"

Namespace: Interface: http://www.upcl.com/NotifyMeterReplacementService NotifyMeterReplacementService
Operations
Operation name Property Connected from Interface getNotifyMeterReplacement request response Operation
MeteringBillingTxInf notifyMeterReplacement (http://upcl.com/RAPDRPBillin gMeteringServiceLib/BillingTxInf)
23.3.3 Reference "OptimumroutemapforBillDistributionMeterReadingPartner"

Namespace: Interface: http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading OptimumroutemapforBillDistributionMeterReading
Operations
Operation name Property Connected from Interface getOptimumroutemapforBillDistributionMeterReading request response Operation
MeteringBillingTxInf optimumRouteMap (http://upcl.com/RAPDRPBillin gMeteringServiceLib/BillingTxInf)
23.3.4 Reference "OptimumRouteMapforConsumerPartner"

Namespace: Interface: http://www.upcl.com/OptimumRouteMapforConsumer OptimumRouteMapforConsumer
Operations
Operation name Property Connected from Interface getRouteMap request response Operation
MeteringBillingTxInf optimumRouteMap (http://upcl.com/RAPDRPBillin gMeteringServiceLib/BillingTxInf)
23.4 Mediation flows

23.4.1 Interface "MeteringBillingTxInf" operation "notifyTheftArea"
Targets
Reference NotifyTheftServicePartner Target operation getNotifyTheft
23.4.1.1 Request
- 46 -
Nov 14, 2011
Promoted properties
Primitive Property Promoted no no no no no no no no no no no no no no no no Group
notifyTheftArea : MeteringBillingTxInf Automatically convert the ServiceGateway message notifyTheftArea : MeteringBillingTxInf Use dynamic endpoint if set in the message header getNotifyTheft : NotifyTheftServicePartner getNotifyTheft : NotifyTheftServicePartner getNotifyTheft : NotifyTheftServicePartner getNotifyTheft : NotifyTheftServicePartner getNotifyTheft : NotifyTheftServicePartner getNotifyTheft : NotifyTheftServicePartner getNotifyTheft : NotifyTheftServicePartner NotifyTheft Input NotifyTheft Input NotifyTheftGIS Request NotifyTheftGIS Request NotifyTheftRequestMapFail NotifyTheftRequestMapFail NotifyTheftRequestMapFail Use dynamic endpoint if set in the message header Async timeout (seconds) Invocation Style Retry on Retry count Retry delay (seconds) Try alternate endpoints Operation Reference Operation Reference Root Mapping file Validate input
23.4.1.1.1 Input "notifyTheftArea : MeteringBillingTxInf"

The input node is the starting point for the request flow. It sends the message from the source operation into the request flow. Name: MeteringBillingTxInf_notifyTheftArea_Input
Promoted properties Promoted property "Automatically convert the ServiceGateway message"

Promoted: no
Outputs Terminal "out"

Propagates the message to the primitive or node to which it is wired. Terminal name: out
- 47 -

Message type:
Nov 14, 2011
{http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyTheftAreaRequestMs g
Connections to
From terminal out Mediation node NotifyTheft Input
23.4.1.1.2 Input Response "notifyTheftArea : MeteringBillingTxInf"

The input response node is an end point in the request and response flows. It returns the processed message as a response to the source operation. Name: MeteringBillingTxInf_notifyTheftArea_InputResponse
Promoted properties Promoted property "Use dynamic endpoint if set in the message header"
Promoted: no
Inputs Terminal "in"

Receives the processed message at the end of the flow. Terminal name: Message type: in {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyTheftAreaResponseM sg
23.4.1.1.3 Input Fault "notifyTheftArea : MeteringBillingTxInf"

The input fault node is an end point in the request flow. It has an input terminal for each fault message type defined in the source operation. Any message propagated to an input fault terminal will result in a WSDL fault of the source operation. Name: MeteringBillingTxInf_notifyTheftArea_InputFault

Terminal name: Message type: notifyTheftArea_notifyTheftFaultMsg {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyTheftArea_notifyTheft FaultMsg
Connections from
From terminal out Mediation node NotifyTheftRequestMapFail
23.4.1.1.4 Callout "getNotifyTheft : NotifyTheftServicePartner"

A callout node is an end point in the request flow. It sends the processed message to the target operation. Name: Reference name: Operation name: Include the original request message Use Dynamic Endpoint: Async Timeout: Force Sync: Retry on: Retry count: Retry delay: Try Alternate Endpoints: NotifyTheftServicePartner_getNotifyTheft_Callout NotifyTheftServicePartner getNotifyTheft no true 5 false 0 0 0 true
Promoted: no
Promoted property "Async timeout (seconds)"
- 48 -

Promoted: no
Nov 14, 2011
Promoted property "Invocation Style"

Promoted: no
Promoted property "Retry on"

Promoted: no
Promoted property "Retry count"

Promoted: no
Promoted property "Retry delay (seconds)"

Promoted: no
Promoted property "Try alternate endpoints"

Promoted: no

Receives the processed message at the end of the flow. Terminal name: Message type: in {http://www.upcl.com/NotifyTheft}getNotifyTheft
Connections from
From terminal out Mediation node NotifyTheftGIS Request
23.4.1.1.5 Custom Mediation "NotifyTheft Input"

Define custom mediation behavior using your own Java code or visual snippet. Name: Root: NotifyTheft_Input /
Implementation
Promoted properties Promoted property "Operation"

Promoted: no
Promoted property "Reference"

Promoted: no
Inputs
- 49 -

Terminal "in"
Receives the input message. Terminal name: Message type:
Nov 14, 2011
in {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyTheftAreaRequestMs g

Terminal name: Message type: out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyTheftAreaRequestMs g
Fails Terminal "fail"

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyTheftAreaRequestMs g
Connections from
From terminal out Mediation node notifyTheftArea : MeteringBillingTxInf
Connections to
From terminal out Mediation node NotifyTheftReqMap
23.4.1.1.6 Business Object Map "NotifyTheftReqMap"

Transform messages using business object maps. Name: Root: Mapping file: NotifyTheftReqMap /body NotifyTheftRequestBOMap.map

Receives the input message. Terminal name: Message type: in {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyTheftAreaRequestMs g

Propagates the updated message, if the mediation is successful. Terminal name: Message type: out {http://www.upcl.com/NotifyTheft}getNotifyTheft

Connections from
- 50 -

From terminal out Mediation node NotifyTheft Input
Nov 14, 2011
Connections to
From terminal out fail Mediation node NotifyTheftGIS Request NotifyTheftRequestMapFail
23.4.1.1.7 Custom Mediation "NotifyTheftGIS Request"

Define custom mediation behavior using your own Java code or visual snippet. Name: Root: NotifyTheftGIS_Request /
Implementation

Promoted: no

Promoted: no

Receives the input message. Terminal name: Message type: in {http://www.upcl.com/NotifyTheft}getNotifyTheft

Terminal name: Message type: out {http://www.upcl.com/NotifyTheft}getNotifyTheft

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://www.upcl.com/NotifyTheft}getNotifyTheft
- 51 -

Connections from
From terminal out Mediation node NotifyTheftReqMap
Nov 14, 2011
Connections to
From terminal out Mediation node getNotifyTheft : NotifyTheftServicePartner
23.4.1.1.8 XSL Transformation "NotifyTheftRequestMapFail"

Transform message formats, or change message content, by using an XSL style sheet to map between source and target message types. Name: Root: Mapping file: Validate input: NotifyTheftRequestMapFail /body xslt/NotifyTheftRequestMapFail_req_1.map no
Promoted properties Promoted property "Root"

Promoted: no
Promoted property "Mapping file"

Promoted: no
Promoted property "Validate input"

Promoted: no

Receives the input message. Terminal name: Message type: in {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyTheftAreaRequestMs g

Propagates the updated message, if the mediation is successful. Terminal name: Message type: out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyTheftArea_notifyTheft FaultMsg

Connections from
From terminal fail Mediation node NotifyTheftReqMap
Connections to
- 52 -
Nov 14, 2011
23.4.1.2 Response
Promoted properties
Primitive getNotifyTheft : NotifyTheftServicePartner getNotifyTheft : NotifyTheftServicePartner getNotifyTheft : NotifyTheftServicePartner Property Promoted Group
Include the original request message no Automatically convert the ServiceGateway message Automatically convert the ServiceGateway message no no no no no no no no no no no no no no no
notifyTheftArea : MeteringBillingTxInf Use dynamic endpoint if set in the message header NotifyTheft Response NotifyTheft Response NotifyTheftGISFault NotifyTheftGISFault NotifyTheftGISFault XSLTransformation1 XSLTransformation1 XSLTransformation1 CustomMediation1 CustomMediation1 CustomMediation11 CustomMediation11 Operation Reference Root Mapping file Validate input Root Mapping file Validate input Operation Reference Operation Reference
23.4.1.2.1 Callout Response "getNotifyTheft : NotifyTheftServicePartner"

A callout response node is a starting point for the response flow. It forwards the message received from the target operation into the response flow. Name: Reference name: Operation name: Include the original request message NotifyTheftServicePartner_getNotifyTheft_CalloutResponse NotifyTheftServicePartner getNotifyTheft no
Promoted properties Promoted property "Include the original request message"
- 53 -

Promoted: no
Nov 14, 2011
Promoted property "Automatically convert the ServiceGateway message"

Promoted: no

Propagates the message to the primitive or node to which it is wired. Terminal name: Message type: out {http://www.upcl.com/NotifyTheft}getNotifyTheftResponse

Propagates a generic message or the original message to the fail output terminal if an exception that has not been explicitly described in the WSDL used in the callout occurs when invoking the callout. Exception information will be added to the transient header of the SMO. By default, a generic message is propagated to the fail output terminal. Terminal name: Message type: fail {http://www.upcl.com/NotifyTheft}getNotifyTheft
Connections to
From terminal out fail Mediation node NotifyTheft Response XSLTransformation1
23.4.1.2.2 Callout Fault "getNotifyTheft : NotifyTheftServicePartner"

A callout fault node is a starting point for the response flow. It has an output terminal for each fault message type defined in the target operation. When a WSDL fault occurs, the callout fault node propagates the message to the primitive or node to which it is wired. Name: Reference name: Operation name: NotifyTheftServicePartner_getNotifyTheft_CalloutFault NotifyTheftServicePartner getNotifyTheft

Promoted: no

Terminal name: Message type: GISFaultInfo {http://www.upcl.com/NotifyTheft}GISFaultInfo
Connections to
From terminal GISFaultInfo Mediation node NotifyTheftGISFault
23.4.1.2.3 Input Response "notifyTheftArea : MeteringBillingTxInf"

The input response node is an end point in the request and response flows. It returns the processed message as a response to the source operation. Name: MeteringBillingTxInf_notifyTheftArea_InputResponse
Promoted: no
- 54 -

Receives the processed message at the end of the flow. Terminal name: Message type:
Nov 14, 2011
in {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyTheftAreaResponseM sg
Connections from
From terminal out Mediation node NotifyTheft rsp map
23.4.1.2.4 Input Fault "notifyTheftArea : MeteringBillingTxInf"

The input fault node is an end point in the request flow. It has an input terminal for each fault message type defined in the source operation. Any message propagated to an input fault terminal will result in a WSDL fault of the source operation. Name: MeteringBillingTxInf_notifyTheftArea_InputFault

Terminal name: Message type: notifyTheftArea_notifyTheftFaultMsg {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyTheftArea_notifyTheft FaultMsg
Connections from
From terminal out out Mediation node CustomMediation1 CustomMediation11
23.4.1.2.5 Custom Mediation "NotifyTheft Response"

Define custom mediation behavior using your own Java code or visual snippet. Name: Root: NotifyTheft_Response /
Implementation
out.fire(smo); // propagate the service message object to the primitive that is wired to the 'out' terminal

Promoted: no

Promoted: no

Receives the input message. Terminal name: Message type: in {http://www.upcl.com/NotifyTheft}getNotifyTheftResponse

Terminal name: Message type: out {http://www.upcl.com/NotifyTheft}getNotifyTheftResponse
- 55 -
Nov 14, 2011
Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://www.upcl.com/NotifyTheft}getNotifyTheftResponse
Connections from
From terminal out Mediation node getNotifyTheft : NotifyTheftServicePartner
Connections to
From terminal out Mediation node NotifyTheft rsp map
23.4.1.2.6 Business Object Map "NotifyTheft rsp map"

Transform messages using business object maps. Name: Root: Mapping file: NotifyTheft_rsp_map /body NotifyTheftResponseBOMap.map

Receives the input message. Terminal name: Message type: in {http://www.upcl.com/NotifyTheft}getNotifyTheftResponse

Propagates the updated message, if the mediation is successful. Terminal name: Message type: out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyTheftAreaResponseM sg

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://www.upcl.com/NotifyTheft}getNotifyTheftResponse
Connections from
From terminal out Mediation node NotifyTheft Response
Connections to
23.4.1.2.7 XSL Transformation "NotifyTheftGISFault"

Transform message formats, or change message content, by using an XSL style sheet to map between source and target message types. Name: Root: Mapping file: Validate input: NotifyTheftGISFault /body xslt/NotifyTheftGISFault_res_1.map no
Promoted properties
- 56 -

Promoted property "Root"
Promoted: no
Nov 14, 2011

Promoted: no

Promoted: no

Receives the input message. Terminal name: Message type: in {http://www.upcl.com/NotifyTheft}GISFaultInfo


Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://www.upcl.com/NotifyTheft}GISFaultInfo
Connections from
From terminal GISFaultInfo Mediation node getNotifyTheft : NotifyTheftServicePartner
Connections to
From terminal out Mediation node CustomMediation1
23.4.1.2.8 XSL Transformation "XSLTransformation1"

Transform message formats, or change message content, by using an XSL style sheet to map between source and target message types. Name: Root: Mapping file: Validate input: XSLTransformation1 /body xslt/XSLTransformation1_res_1.map no

Promoted: no

Promoted: no

Promoted: no
Inputs
- 57 -

Terminal "in"
Receives the input message. Terminal name: Message type: in {http://www.upcl.com/NotifyTheft}getNotifyTheft
Nov 14, 2011


Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://www.upcl.com/NotifyTheft}getNotifyTheft
Connections from
From terminal fail Mediation node getNotifyTheft : NotifyTheftServicePartner
Connections to
23.4.1.2.9 Custom Mediation "CustomMediation1"

Define custom mediation behavior using your own Java code or visual snippet. Name: Root: CustomMediation1 /
Implementation

Promoted: no

Promoted: no
- 58 -

Nov 14, 2011
in {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyTheftArea_notifyTheft FaultMsg

Terminal name: Message type: out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyTheftArea_notifyTheft FaultMsg

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyTheftArea_notifyTheft FaultMsg
Connections from
From terminal out Mediation node NotifyTheftGISFault
Connections to

Implementation

Promoted: no
- 59 -

Promoted: no
Nov 14, 2011

Receives the input message. Terminal name: Message type: in {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyTheftArea_notifyTheft FaultMsg

Terminal name: Message type: out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyTheftArea_notifyTheft FaultMsg

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyTheftArea_notifyTheft FaultMsg
Connections from
From terminal out Mediation node XSLTransformation1
Connections to
23.4.2 Interface "MeteringBillingTxInf" operation "notifyMeterReplacement"

Targets
Reference NotifyMeterReplacementServicePartner Target operation getNotifyMeterReplacement
23.4.2.1 Request
Promoted properties
Primitive notifyMeterReplacement : MeteringProperty Automatically convert the ServiceGPromoted no Group
- 60 -

Primitive BillingTxInf notifyMeterReplacement : MeteringBillingTxInf getNotifyMeterReplacement : NotifyMeterReplacementServicePartner getNotifyMeterReplacement : NotifyMeterReplacementServicePartner getNotifyMeterReplacement : NotifyMeterReplacementServicePartner getNotifyMeterReplacement : NotifyMeterReplacementServicePartner getNotifyMeterReplacement : NotifyMeterReplacementServicePartner getNotifyMeterReplacement : NotifyMeterReplacementServicePartner getNotifyMeterReplacement : NotifyMeterReplacementServicePartner NotifyMeterReplacement request NotifyMeterReplacement request Property ateway message Use dynamic endpoint if set in the message header Use dynamic endpoint if set in the message header Async timeout (seconds) Invocation Style Retry on Retry count Retry delay (seconds) Try alternate endpoints Operation Reference no no no no no no no no no no Promoted Group
Nov 14, 2011
23.4.2.1.1 Input "notifyMeterReplacement : MeteringBillingTxInf"

The input node is the starting point for the request flow. It sends the message from the source operation into the request flow. Name: MeteringBillingTxInf_notifyMeterReplacement_Input

Promoted: no

Propagates the message to the primitive or node to which it is wired. Terminal name: Message type: out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyMeterReplacementRe questMsg
Connections to
From terminal out Mediation node NotifyMeterReplacement request
23.4.2.1.2 Input Response "notifyMeterReplacement : MeteringBillingTxInf"

The input response node is an end point in the request and response flows. It returns the processed message as a response to the source operation. Name: MeteringBillingTxInf_notifyMeterReplacement_InputResponse
Promoted: no

Receives the processed message at the end of the flow. Terminal name: Message type: in {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyMeterReplacementRe
- 61 -

sponseMsg
Nov 14, 2011
23.4.2.1.3 Input Fault "notifyMeterReplacement : MeteringBillingTxInf"

The input fault node is an end point in the request flow. It has an input terminal for each fault message type defined in the source operation. Any message propagated to an input fault terminal will result in a WSDL fault of the source operation. Name: MeteringBillingTxInf_notifyMeterReplacement_InputFault

Terminal name: Message type: notifyMeterReplacement_notifyMeterReplacementFaultMsg {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyMeterReplacement_n otifyMeterReplacementFaultMsg
23.4.2.1.4 Callout "getNotifyMeterReplacement : NotifyMeterReplacementServicePartner"

A callout node is an end point in the request flow. It sends the processed message to the target operation. Name: Reference name: Operation name: Include the original request message Use Dynamic Endpoint: Async Timeout: Force Sync: Retry on: Retry count: Retry delay: Try Alternate Endpoints: NotifyMeterReplacementServicePartner_getNotifyMeterReplacement_Callout NotifyMeterReplacementServicePartner getNotifyMeterReplacement no true 5 false 0 0 0 true
Promoted: no

Promoted: no

Promoted: no

Promoted: no

Promoted: no

Promoted: no

Promoted: no

Receives the processed message at the end of the flow. Terminal name: Message type: in {http://www.upcl.com/NotifyMeterReplacementService}getNotifyMeterReplacement
Connections from
From terminal out Mediation node NotifyMeterReplacement Map
- 62 -
Nov 14, 2011
23.4.2.1.5 Business Object Map "NotifyMeterReplacement Map"

Transform messages using business object maps. Name: Root: Mapping file: NotifyMeterReplacement_Map /body NotifyMeterReplacementBOMap.map

Receives the input message. Terminal name: Message type: in {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyMeterReplacementRe questMsg

Propagates the updated message, if the mediation is successful. Terminal name: Message type: out {http://www.upcl.com/NotifyMeterReplacementService}getNotifyMeterReplacement

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyMeterReplacementRe questMsg
Connections from
From terminal out Mediation node NotifyMeterReplacement request
Connections to
From terminal out Mediation node getNotifyMeterReplacement : NotifyMeterReplacementServicePartner
23.4.2.1.6 Custom Mediation "NotifyMeterReplacement request"

Define custom mediation behavior using your own Java code or visual snippet. Name: Root: NotifyMeterReplacement_request /
Implementation
- 63 -
Nov 14, 2011

Promoted: no

Promoted: no

Receives the input message. Terminal name: Message type: in {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyMeterReplacementRe questMsg

Terminal name: Message type: out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyMeterReplacementRe questMsg

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyMeterReplacementRe questMsg
Connections from
From terminal out Mediation node notifyMeterReplacement : MeteringBillingTxInf
Connections to
From terminal out Mediation node NotifyMeterReplacement Map
23.4.2.2 Response
- 64 -
Nov 14, 2011
Promoted properties
Primitive getNotifyMeterReplacement : NotifyMeterReplacementServicePartner getNotifyMeterReplacement : NotifyMeterReplacementServicePartner getNotifyMeterReplacement : NotifyMeterReplacementServicePartner notifyMeterReplacement : MeteringBillingTxInf NotifyMeterReplacement response NotifyMeterReplacement response NotifyMeterReplacementRuntimeFault NotifyMeterReplacementRuntimeFault NotifyMeterReplacementRuntimeFault CustomMediation1 CustomMediation1 CustomMediation11 CustomMediation11 Property Promoted Group
Include the original request message no Automatically convert the ServiceGateway message Automatically convert the ServiceGateway message Use dynamic endpoint if set in the message header Operation Reference Root Mapping file Validate input Operation Reference Operation Reference no no no no no no no no no no no no
23.4.2.2.1 Callout Response "getNotifyMeterReplacement : NotifyMeterReplacementServicePartner"

A callout response node is a starting point for the response flow. It forwards the message received from the target operation into the response flow. Name: Reference name: Operation name: Include the original request message NotifyMeterReplacementServicePartner_getNotifyMeterReplacement_CalloutResponse NotifyMeterReplacementServicePartner getNotifyMeterReplacement no

Promoted: no

Promoted: no
Outputs
- 65 -

Terminal "out"
Propagates the message to the primitive or node to which it is wired. Terminal name: Message type:
Nov 14, 2011
out {http://www.upcl.com/NotifyMeterReplacementService}getNotifyMeterReplacementRespon se

Propagates a generic message or the original message to the fail output terminal if an exception that has not been explicitly described in the WSDL used in the callout occurs when invoking the callout. Exception information will be added to the transient header of the SMO. By default, a generic message is propagated to the fail output terminal. Terminal name: Message type: fail {http://www.upcl.com/NotifyMeterReplacementService}getNotifyMeterReplacement
Connections to
From terminal out fail Mediation node NotifyMeterReplacement response NotifyMeterReplacementRuntimeFault
23.4.2.2.2 Callout Fault "getNotifyMeterReplacement : NotifyMeterReplacementServicePartner"

A callout fault node is a starting point for the response flow. It has an output terminal for each fault message type defined in the target operation. When a WSDL fault occurs, the callout fault node propagates the message to the primitive or node to which it is wired. Name: Reference name: Operation name: NotifyMeterReplacementServicePartner_getNotifyMeterReplacement_CalloutFault NotifyMeterReplacementServicePartner getNotifyMeterReplacement

Promoted: no

Terminal name: Message type: GISFaultInfo {http://www.upcl.com/NotifyMeterReplacementService}GISFaultInfo
Connections to
From terminal GISFaultInfo Mediation node NotifyMeterReplacementBusinessEx
23.4.2.2.3 Input Response "notifyMeterReplacement : MeteringBillingTxInf"

The input response node is an end point in the request and response flows. It returns the processed message as a response to the source operation. Name: MeteringBillingTxInf_notifyMeterReplacement_InputResponse
Promoted: no

Receives the processed message at the end of the flow. Terminal name: Message type: in {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyMeterReplacementRe sponseMsg
- 66 -

Connections from
From terminal out Mediation node NotifyMeterReplacement response
Nov 14, 2011
23.4.2.2.4 Input Fault "notifyMeterReplacement : MeteringBillingTxInf"

The input fault node is an end point in the request flow. It has an input terminal for each fault message type defined in the source operation. Any message propagated to an input fault terminal will result in a WSDL fault of the source operation. Name: MeteringBillingTxInf_notifyMeterReplacement_InputFault

Terminal name: Message type: notifyMeterReplacement_notifyMeterReplacementFaultMsg {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyMeterReplacement_n otifyMeterReplacementFaultMsg
Connections from
23.4.2.2.5 Custom Mediation "NotifyMeterReplacement response"

Define custom mediation behavior using your own Java code or visual snippet. Name: Root: NotifyMeterReplacement_response /
Implementation

Promoted: no

Promoted: no

Receives the input message. Terminal name: in
- 67 -

Message type:
Nov 14, 2011
{http://www.upcl.com/NotifyMeterReplacementService}getNotifyMeterReplacementRespon se

Terminal name: Message type: out {http://www.upcl.com/NotifyMeterReplacementService}getNotifyMeterReplacementRespon se

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://www.upcl.com/NotifyMeterReplacementService}getNotifyMeterReplacementRespon se
Connections from
From terminal out Mediation node getNotifyMeterReplacement : NotifyMeterReplacementServicePartner
Connections to
23.4.2.2.6 Business Object Map "NotifyMeterReplacement response"

Transform messages using business object maps. Name: Root: Mapping file: NotifyMeterReplacement_response1 /body NotifyMeterReplacementResponseBOMap.map

Receives the input message. Terminal name: Message type: in {http://www.upcl.com/NotifyMeterReplacementService}getNotifyMeterReplacementRespon se

Propagates the updated message, if the mediation is successful. Terminal name: Message type: out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyMeterReplacementRe sponseMsg

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://www.upcl.com/NotifyMeterReplacementService}getNotifyMeterReplacementRespon se
Connections from
- 68 -

Connections to
Nov 14, 2011
23.4.2.2.7 XSL Transformation "NotifyMeterReplacementRuntimeFault"

Transform message formats, or change message content, by using an XSL style sheet to map between source and target message types. Name: Root: Mapping file: Validate input: NotifyMeterReplacementRuntimeFault /body xslt/NotifyMeterReplacementRuntimeFault_res_1.map no

Promoted: no

Promoted: no

Promoted: no

Receives the input message. Terminal name: Message type: in {http://www.upcl.com/NotifyMeterReplacementService}getNotifyMeterReplacement

Propagates the updated message, if the mediation is successful. Terminal name: Message type: out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyMeterReplacement_n otifyMeterReplacementFaultMsg

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://www.upcl.com/NotifyMeterReplacementService}getNotifyMeterReplacement
Connections from
From terminal fail Mediation node getNotifyMeterReplacement : NotifyMeterReplacementServicePartner
Connections to
23.4.2.2.8 Business Object Map "NotifyMeterReplacementBusinessEx"

Transform messages using business object maps. Name: Root: Mapping file: NotifyMeterReplacementBusinessEx /body NotifyMeterReplacementBusinessExMap.map
- 69 -

Receives the input message. Terminal name: Message type: in {http://www.upcl.com/NotifyMeterReplacementService}GISFaultInfo
Nov 14, 2011

Propagates the updated message, if the mediation is successful. Terminal name: Message type: out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyMeterReplacement_n otifyMeterReplacementFaultMsg

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://www.upcl.com/NotifyMeterReplacementService}GISFaultInfo
Connections from
From terminal GISFaultInfo Mediation node getNotifyMeterReplacement : NotifyMeterReplacementServicePartner
Connections to

Implementation

Promoted: no
- 70 -

Promoted: no
Nov 14, 2011

Receives the input message. Terminal name: Message type: in {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyMeterReplacement_n otifyMeterReplacementFaultMsg

Terminal name: Message type: out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyMeterReplacement_n otifyMeterReplacementFaultMsg

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyMeterReplacement_n otifyMeterReplacementFaultMsg
Connections from
From terminal out Mediation node NotifyMeterReplacementBusinessEx
Connections to

Implementation

Promoted: no
- 71 -

Promoted: no
Nov 14, 2011

Receives the input message. Terminal name: Message type: in {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyMeterReplacement_n otifyMeterReplacementFaultMsg

Terminal name: Message type: out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyMeterReplacement_n otifyMeterReplacementFaultMsg

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}notifyMeterReplacement_n otifyMeterReplacementFaultMsg
Connections from
From terminal out Mediation node NotifyMeterReplacementRuntimeFault
Connections to
23.4.3 Interface "MeteringBillingTxInf" operation "optimumRouteMap"

Targets
Reference OptimumroutemapforBillDistributionMeterReadingPartner OptimumRouteMapforConsumerPartner Target operation getOptimumroutemapforBillDistributionMeterReading getRouteMap
23.4.3.1 Request
- 72 -
Nov 14, 2011
Promoted properties
Primitive optimumRouteMap : MeteringBillingTxInf optimumRouteMap : MeteringBillingTxInf getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner OptimumRouteReq OptimumRouteReq OptimumRouteReq1 OptimumRouteReq1 getRouteMap : OptimumRouteMapforConsumerPartner getRouteMap : OptimumRouteMapforConsumerPartner Property Automatically convert the ServiceGateway message Use dynamic endpoint if set in the message header Use dynamic endpoint if set in the message header Promoted no no no Group
Async timeout (seconds)
no
Invocation Style
no
Retry on
no
Retry count
no
Retry delay (seconds)
no
Try alternate endpoints
no
Operation Reference Operation Reference Use dynamic endpoint if set in the message header Async timeout (seconds)
no no no no no no
- 73 -

Primitive getRouteMap : OptimumRouteMapforConsumerPartner getRouteMap : OptimumRouteMapforConsumerPartner getRouteMap : OptimumRouteMapforConsumerPartner getRouteMap : OptimumRouteMapforConsumerPartner getRouteMap : OptimumRouteMapforConsumerPartner RouteMapRequest1 RouteMapRequest1 RouteMapRequest2 RouteMapRequest2 MessageFilter1 MessageFilter1 MessageFilter1 MessageFilter1 XSLTransformation1 XSLTransformation1 XSLTransformation1 CustomMediation1 CustomMediation1 XSLTransformation2 XSLTransformation2 XSLTransformation2 CustomMediation2 CustomMediation2 Property Invocation Style Retry on Retry count Retry delay (seconds) Try alternate endpoints Operation Reference Operation Reference Enabled Distribution mode match1 [Pattern] match2 [Pattern] Root Mapping file Validate input Operation Reference Root Mapping file Validate input Operation Reference Promoted no no no no no no no no no no no no no no no no no no no no no no no Group
Nov 14, 2011
23.4.3.1.1 Input "optimumRouteMap : MeteringBillingTxInf"

The input node is the starting point for the request flow. It sends the message from the source operation into the request flow. Name: MeteringBillingTxInf_optimumRouteMap_Input

Promoted: no

Propagates the message to the primitive or node to which it is wired. Terminal name: Message type: out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMapRequest Msg
Connections to
From terminal out Mediation node MessageFilter1
23.4.3.1.2 Input Response "optimumRouteMap : MeteringBillingTxInf"

The input response node is an end point in the request and response flows. It returns the processed message as a response to the source operation.
- 74 -

Name: MeteringBillingTxInf_optimumRouteMap_InputResponse
Nov 14, 2011
Promoted: no

Receives the processed message at the end of the flow. Terminal name: Message type: in {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMapRespon seMsg
23.4.3.1.3 Input Fault "optimumRouteMap : MeteringBillingTxInf"

The input fault node is an end point in the request flow. It has an input terminal for each fault message type defined in the source operation. Any message propagated to an input fault terminal will result in a WSDL fault of the source operation. Name: MeteringBillingTxInf_optimumRouteMap_InputFault

Terminal name: Message type: optimumRouteMap_optimumRouteMapFaultMsg {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMap_optimu mRouteMapFaultMsg
Connections from
23.4.3.1.4 Callout "getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner"

A callout node is an end point in the request flow. It sends the processed message to the target operation. Name: Reference name: Operation name: Include the original request message Use Dynamic Endpoint: Async Timeout: Force Sync: Retry on: Retry count: Retry delay: Try Alternate Endpoints: OptimumroutemapforBillDistributionMeterReadingPartner_getOptimumroutemapforBillDistributionMeterReading_Callout OptimumroutemapforBillDistributionMeterReadingPartner getOptimumroutemapforBillDistributionMeterReading no true 5 false 0 0 0 true
Promoted: no

Promoted: no

Promoted: no

Promoted: no
- 75 -

Promoted: no
Nov 14, 2011

Promoted: no

Promoted: no

Receives the processed message at the end of the flow. Terminal name: Message type: in {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}getOptimumroute mapforBillDistributionMeterReading
Connections from
From terminal out Mediation node OptimumRouteReq1
23.4.3.1.5 Custom Mediation "OptimumRouteReq"

Define custom mediation behavior using your own Java code or visual snippet. Name: Root: OptimumRouteReq /
Implementation

Promoted: no

Promoted: no

Receives the input message. Terminal name: Message type: in {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMapRequest
- 76 -

Msg
Nov 14, 2011

Terminal name: Message type: out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMapRequest Msg

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMapRequest Msg
Connections from
From terminal match1 Mediation node MessageFilter1
Connections to
From terminal out Mediation node OptimumRouteRequestMap
23.4.3.1.6 Custom Mediation "OptimumRouteReq1"

Define custom mediation behavior using your own Java code or visual snippet. Name: Root: OptimumRouteReq1 /
Implementation

Promoted: no

Promoted: no
Inputs
- 77 -

Terminal "in"
Nov 14, 2011
in {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}getOptimumroute mapforBillDistributionMeterReading

Terminal name: Message type: out {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}getOptimumroute mapforBillDistributionMeterReading

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}getOptimumroute mapforBillDistributionMeterReading
Connections from
From terminal out Mediation node OptimumRouteRequestMap
Connections to
From terminal out Mediation node getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner
23.4.3.1.7 Business Object Map "OptimumRouteRequestMap"

Transform messages using business object maps. Name: Root: Mapping file: OptimumRouteRequestMap /body OptimumRouteMapReqMap.map

Receives the input message. Terminal name: Message type: in {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMapRequest Msg

Propagates the updated message, if the mediation is successful. Terminal name: Message type: out {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}getOptimumroute mapforBillDistributionMeterReading

- 78 -

Connections from
From terminal out Mediation node OptimumRouteReq
Nov 14, 2011
Connections to
23.4.3.1.8 Callout "getRouteMap : OptimumRouteMapforConsumerPartner"

A callout node is an end point in the request flow. It sends the processed message to the target operation. Name: Reference name: Operation name: Include the original request message Use Dynamic Endpoint: Async Timeout: Force Sync: Retry on: Retry count: Retry delay: Try Alternate Endpoints: OptimumRouteMapforConsumerPartner_getRouteMap_Callout OptimumRouteMapforConsumerPartner getRouteMap no true 5 false 0 0 0 true
Promoted: no

Promoted: no

Promoted: no

Promoted: no

Promoted: no

Promoted: no

Promoted: no

Receives the processed message at the end of the flow. Terminal name: Message type: in {http://www.upcl.com/OptimumRouteMapforConsumer}getRouteMap
Connections from
From terminal out Mediation node RouteMapRequest2
23.4.3.1.9 Custom Mediation "RouteMapRequest1"

Define custom mediation behavior using your own Java code or visual snippet. Name: RouteMapRequest1
- 79 -

Root: /
Nov 14, 2011
Implementation

Promoted: no

Promoted: no


Terminal name: Message type: out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMapRequest Msg

Connections from
From terminal match2 Mediation node MessageFilter1
Connections to
From terminal out Mediation node ConsumerMap
23.4.3.1.10 Business Object Map "ConsumerMap"

Transform messages using business object maps.
- 80 -

Name: Root: Mapping file: ConsumerMap /body ConsumerMapRequest.map
Nov 14, 2011


Propagates the updated message, if the mediation is successful. Terminal name: Message type: out {http://www.upcl.com/OptimumRouteMapforConsumer}getRouteMap

Connections from
Connections to
23.4.3.1.11 Custom Mediation "RouteMapRequest2"

Define custom mediation behavior using your own Java code or visual snippet. Name: Root: RouteMapRequest2 /
Implementation
- 81 -

Promoted: no
Nov 14, 2011

Promoted: no

Receives the input message. Terminal name: Message type: in {http://www.upcl.com/OptimumRouteMapforConsumer}getRouteMap

Terminal name: Message type: out {http://www.upcl.com/OptimumRouteMapforConsumer}getRouteMap

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://www.upcl.com/OptimumRouteMapforConsumer}getRouteMap
Connections from
From terminal out Mediation node ConsumerMap
Connections to
From terminal out Mediation node getRouteMap : OptimumRouteMapforConsumerPartner
23.4.3.1.12 Message Filter "MessageFilter1"

Conditionally route a message based on the message content, by comparing the message against a list of user defined expressions. Name: Distribution mode: Root: MessageFilter1 First /
Filters
Pattern /body/optimumRouteMap/optimumRootMapRequest/DTR_AIN / body/optimumRouteMap/optimumRootMapRequest/forConsumer Terminal name match1 match2
Promoted properties Promoted property "Enabled"

Promoted: no
Promoted property "Distribution mode"

Promoted: no
Promoted property "match1 [Pattern]"

Promoted: no
Promoted property "match2 [Pattern]"

Promoted: no
- 82 -

Nov 14, 2011
in {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMapRequest Msg
Outputs Terminal "default"

Propagates the original message, on successful processing, if the message does not match any of the XPath expressions defined in the patternList. Terminal name: Message type: default {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMapRequest Msg
Terminal "match"
Terminal name: Message type: match1 {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMapRequest Msg
Terminal "match"
Terminal name: Message type: match2 {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMapRequest Msg

Connections from
From terminal out Mediation node optimumRouteMap : MeteringBillingTxInf
Connections to
From terminal default match1 match2 fail Mediation node XSLTransformation2 OptimumRouteReq RouteMapRequest1 XSLTransformation1

Transform message formats, or change message content, by using an XSL style sheet to map between source and target message types. Name: Root: Mapping file: Validate input: XSLTransformation1 /body xslt/XSLTransformation1_req_1.map no

Promoted: no
- 83 -

Promoted: no
Nov 14, 2011

Promoted: no


Propagates the updated message, if the mediation is successful. Terminal name: Message type: out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMap_optimu mRouteMapFaultMsg

Connections from
From terminal fail Mediation node MessageFilter1
Connections to

Implementation
- 84 -
Nov 14, 2011

Promoted: no

Promoted: no

Receives the input message. Terminal name: Message type: in {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMap_optimu mRouteMapFaultMsg

Terminal name: Message type: out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMap_optimu mRouteMapFaultMsg

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMap_optimu mRouteMapFaultMsg
Connections from
Connections to

Transform message formats, or change message content, by using an XSL style sheet to map between source and target message types. Name: XSLTransformation2
- 85 -

Root: Mapping file: Validate input: /body xslt/XSLTransformation2_req_1.map no
Nov 14, 2011

Promoted: no

Promoted: no

Promoted: no



Connections from
From terminal default Mediation node MessageFilter1
Connections to

Implementation
- 86 -
Nov 14, 2011

Promoted: no

Promoted: no



Connections from
Connections to
23.4.3.2 Response
- 87 -
Nov 14, 2011
Promoted properties
Primitive getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner optimumRouteMap : MeteringBillingTxInf OptimumRouteReq OptimumRouteReq OptimumRouteReq1 OptimumRouteReq1 OptimumRouteReq2 OptimumRouteReq2 OptimumRouteReq3 OptimumRouteReq3 XSLTransformation1 XSLTransformation1 XSLTransformation1 getRouteMap : OptimumRouteMapforConsumerPartner getRouteMap : OptimumRouteMapforConsumerPartner Property Promoted Group
Include the original request message no
Automatically convert the ServiceGateway message
no
Automatically convert the ServiceGateway message
no
Use dynamic endpoint if set in the message header Operation Reference Operation Reference Operation Reference Operation Reference Root Mapping file Validate input
no no no no no no no no no no no no
Include the original request message no Automatically convert the ServiceGateway message no
- 88 -

Primitive getRouteMap : OptimumRouteMapforConsumerPartner OptimumRouteMapConsumer OptimumRouteMapConsumer OptimumRouteMapConsumer2 OptimumRouteMapConsumer2 XSLTransformation2 XSLTransformation2 XSLTransformation2 OptimumRouteMapConsumer3 OptimumRouteMapConsumer3 Property Automatically convert the ServiceGateway message Operation Reference Operation Reference Root Mapping file Validate input Operation Reference Promoted no no no no no no no no no no Group
Nov 14, 2011
23.4.3.2.1 Callout Response "getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner"

A callout response node is a starting point for the response flow. It forwards the message received from the target operation into the response flow. Name: Reference name: Operation name: Include the original request message OptimumroutemapforBillDistributionMeterReadingPartner_getOptimumroutemapforBillDistributionMeterReading_CalloutResponse OptimumroutemapforBillDistributionMeterReadingPartner getOptimumroutemapforBillDistributionMeterReading no

Promoted: no

Promoted: no

Propagates the message to the primitive or node to which it is wired. Terminal name: Message type: out {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}getOptimumroute mapforBillDistributionMeterReadingResponse

Propagates a generic message or the original message to the fail output terminal if an exception that has not been explicitly described in the WSDL used in the callout occurs when invoking the callout. Exception information will be added to the transient header of the SMO. By default, a generic message is propagated to the fail output terminal. Terminal name: Message type: fail {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}getOptimumroute mapforBillDistributionMeterReading
Connections to
From terminal out fail Mediation node OptimumRouteReq OptimumRouteReq2
23.4.3.2.2 Callout Fault "getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner"

A callout fault node is a starting point for the response flow. It has an output terminal for each fault message type defined in the target operation. When a WSDL fault occurs, the callout fault node propagates the message to the primitive or node to which it is wired.
- 89 -

Name: Reference name: Operation name: OptimumroutemapforBillDistributionMeterReadingPartner_getOptimumroutemapforBillDistributionMeterReading_CalloutFault OptimumroutemapforBillDistributionMeterReadingPartner getOptimumroutemapforBillDistributionMeterReading
Nov 14, 2011

Promoted: no

Terminal name: Message type: GISFaultInfo {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}GISFaultInfo
Connections to
From terminal GISFaultInfo Mediation node OptimumRouteReq1
23.4.3.2.3 Input Response "optimumRouteMap : MeteringBillingTxInf"

The input response node is an end point in the request and response flows. It returns the processed message as a response to the source operation. Name: MeteringBillingTxInf_optimumRouteMap_InputResponse
Promoted: no

Receives the processed message at the end of the flow. Terminal name: Message type: in {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMapRespon seMsg
Connections from
From terminal out out Mediation node OptimumRouteMapRsp OptimumRouteMapConsumer
23.4.3.2.4 Input Fault "optimumRouteMap : MeteringBillingTxInf"

The input fault node is an end point in the request flow. It has an input terminal for each fault message type defined in the source operation. Any message propagated to an input fault terminal will result in a WSDL fault of the source operation. Name: MeteringBillingTxInf_optimumRouteMap_InputFault

Terminal name: Message type: optimumRouteMap_optimumRouteMapFaultMsg {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMap_optimu mRouteMapFaultMsg
Connections from
From terminal out out Mediation node OptimumRouteReq3 BusinessFault
- 90 -

From terminal out out Mediation node BusineeFault1 OptimumRouteMapConsumer3
Nov 14, 2011
23.4.3.2.5 Custom Mediation "OptimumRouteReq"

Define custom mediation behavior using your own Java code or visual snippet. Name: Root: OptimumRouteReq /
Implementation

Promoted: no

Promoted: no

Receives the input message. Terminal name: Message type: in {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}getOptimumroute mapforBillDistributionMeterReadingResponse

Terminal name: Message type: out {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}getOptimumroute mapforBillDistributionMeterReadingResponse

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}getOptimumroute mapforBillDistributionMeterReadingResponse
- 91 -

Connections from
From terminal out Mediation node
Nov 14, 2011
getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner
Connections to
From terminal out Mediation node OptimumRouteMapRsp

Implementation

Promoted: no

Promoted: no

Receives the input message. Terminal name: Message type: in {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}GISFaultInfo

Terminal name: Message type: out {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}GISFaultInfo

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be
- 92 -

added to the failInfo context of the SMO. Terminal name: Message type:
Nov 14, 2011
fail {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}GISFaultInfo
Connections from
From terminal GISFaultInfo Mediation node getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner
Connections to
From terminal out Mediation node BusinessFault

Implementation

Promoted: no

Promoted: no

Receives the input message. Terminal name: Message type: in {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}getOptimumroute mapforBillDistributionMeterReading

Terminal name: Message type: out {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}getOptimumroute
- 93 -

mapforBillDistributionMeterReading
Nov 14, 2011

Connections from
From terminal fail Mediation node getOptimumroutemapforBillDistributionMeterReading : OptimumroutemapforBillDistributionMeterReadingPartner
Connections to

Implementation

Promoted: no

Promoted: no

- 94 -

Terminal name: Message type:
Nov 14, 2011
out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMap_optimu mRouteMapFaultMsg

Connections from
Connections to
23.4.3.2.9 Business Object Map "OptimumRouteMapRsp"

Transform messages using business object maps. Name: Root: Mapping file: OptimumRouteMapRsp /body OptimumRouteMapRspMap.map

Receives the input message. Terminal name: Message type: in {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}getOptimumroute mapforBillDistributionMeterReadingResponse

Propagates the updated message, if the mediation is successful. Terminal name: Message type: out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMapRespon seMsg

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}getOptimumroute mapforBillDistributionMeterReadingResponse
Connections from
From terminal out Mediation node OptimumRouteReq
Connections to
- 95 -

Nov 14, 2011
23.4.3.2.10 Business Object Map "BusinessFault"

Transform messages using business object maps. Name: Root: Mapping file: BusinessFault /body BusinessFaultMap.map

Receives the input message. Terminal name: Message type: in {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}GISFaultInfo


Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}GISFaultInfo
Connections from
Connections to


Promoted: no

Promoted: no

Promoted: no
Inputs
- 96 -

Terminal "in"
Nov 14, 2011
in {http://www.upcl.com/OptimumroutemapforBillDistributionMeterReading}getOptimumroute mapforBillDistributionMeterReading


Connections from
Connections to
23.4.3.2.12 Callout Response "getRouteMap : OptimumRouteMapforConsumerPartner"

A callout response node is a starting point for the response flow. It forwards the message received from the target operation into the response flow. Name: Reference name: Operation name: Include the original request message OptimumRouteMapforConsumerPartner_getRouteMap_CalloutResponse OptimumRouteMapforConsumerPartner getRouteMap no

Promoted: no

Promoted: no

Propagates the message to the primitive or node to which it is wired. Terminal name: Message type: out {http://www.upcl.com/OptimumRouteMapforConsumer}getRouteMapResponse

Propagates a generic message or the original message to the fail output terminal if an exception that has not been explicitly described in the WSDL used in the callout occurs when invoking the callout. Exception information will be added to the transient header of the SMO. By default, a generic message is propagated to the fail output terminal. Terminal name: fail
- 97 -

Message type: {http://www.upcl.com/OptimumRouteMapforConsumer}getRouteMap
Nov 14, 2011
Connections to
From terminal out fail Mediation node OptimumRouteMapConsumer XSLTransformation2
23.4.3.2.13 Callout Fault "getRouteMap : OptimumRouteMapforConsumerPartner"

A callout fault node is a starting point for the response flow. It has an output terminal for each fault message type defined in the target operation. When a WSDL fault occurs, the callout fault node propagates the message to the primitive or node to which it is wired. Name: Reference name: Operation name: OptimumRouteMapforConsumerPartner_getRouteMap_CalloutFault OptimumRouteMapforConsumerPartner getRouteMap

Promoted: no

Terminal name: Message type: GISFaultInfo {http://www.upcl.com/OptimumRouteMapforConsumer}GISFaultInfo
Connections to
From terminal GISFaultInfo Mediation node OptimumRouteMapConsumer2
23.4.3.2.14 Custom Mediation "OptimumRouteMapConsumer"

Define custom mediation behavior using your own Java code or visual snippet. Name: Root: OptimumRouteMapConsumer /
Implementation

Promoted: no

Promoted: no
- 98 -

Nov 14, 2011
in {http://www.upcl.com/OptimumRouteMapforConsumer}getRouteMapResponse

Terminal name: Message type: out {http://www.upcl.com/OptimumRouteMapforConsumer}getRouteMapResponse

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://www.upcl.com/OptimumRouteMapforConsumer}getRouteMapResponse
Connections from
From terminal out Mediation node getRouteMap : OptimumRouteMapforConsumerPartner
Connections to
From terminal out Mediation node OptimumRouteMapConsumer
23.4.3.2.15 Business Object Map "OptimumRouteMapConsumer"

Transform messages using business object maps. Name: Root: Mapping file: OptimumRouteMapConsumer1 /body OptimumRouteMapConsumerRspMap.map

Receives the input message. Terminal name: Message type: in {http://www.upcl.com/OptimumRouteMapforConsumer}getRouteMapResponse

Propagates the updated message, if the mediation is successful. Terminal name: Message type: out {http://upcl.com/RAPDRPBillingMeteringServiceLib/BillingTxInf}optimumRouteMapRespon seMsg

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://www.upcl.com/OptimumRouteMapforConsumer}getRouteMapResponse
Connections from
- 99 -

From terminal out Mediation node OptimumRouteMapConsumer
Nov 14, 2011
Connections to
23.4.3.2.16 Custom Mediation "OptimumRouteMapConsumer2"

Define custom mediation behavior using your own Java code or visual snippet. Name: Root: OptimumRouteMapConsumer2 /
Implementation

Promoted: no

Promoted: no

Receives the input message. Terminal name: Message type: in {http://www.upcl.com/OptimumRouteMapforConsumer}GISFaultInfo

Terminal name: Message type: out {http://www.upcl.com/OptimumRouteMapforConsumer}GISFaultInfo

Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://www.upcl.com/OptimumRouteMapforConsumer}GISFaultInfo
Connections from
- 100 -

From terminal GISFaultInfo Mediation node getRouteMap : OptimumRouteMapforConsumerPartner
Nov 14, 2011
Connections to
From terminal out Mediation node BusineeFault1
23.4.3.2.17 Business Object Map "BusineeFault1"

Transform messages using business object maps. Name: Root: Mapping file: BusineeFault1 /body BusinessFault1Map.map

Receives the input message. Terminal name: Message type: in {http://www.upcl.com/OptimumRouteMapforConsumer}GISFaultInfo


Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://www.upcl.com/OptimumRouteMapforConsumer}GISFaultInfo
Connections from
From terminal out Mediation node OptimumRouteMapConsumer2
Connections to


Promoted: no

Promoted: no
- 101 -

Promoted: no
Nov 14, 2011

Receives the input message. Terminal name: Message type: in {http://www.upcl.com/OptimumRouteMapforConsumer}getRouteMap


Propagates the original message, if an exception occurs during the processing of the input message. Exception information will be added to the failInfo context of the SMO. Terminal name: Message type: fail {http://www.upcl.com/OptimumRouteMapforConsumer}getRouteMap
Connections from
From terminal fail Mediation node getRouteMap : OptimumRouteMapforConsumerPartner
Connections to
From terminal out Mediation node OptimumRouteMapConsumer3
23.4.3.2.19 Custom Mediation "OptimumRouteMapConsumer3"

Define custom mediation behavior using your own Java code or visual snippet. Name: Root: OptimumRouteMapConsumer3 /
Implementation
- 102 -

Promoted: no
Nov 14, 2011

Promoted: no



Connections from
Connections to
23.4.4 Interface "OptimumRouteInf" operation "optimumRouteDataService"

23.4.4.1 Request
23.4.5 Interface "OptimumRouteInf" operation "optimumRouteMapService"

23.4.5.1 Request
- 103 -
Cross Reference.
Nov 14, 2011
24 Cross Reference
The lists in this section show how resources are related to one another.
References list NotifyTheftRequestBOMap.map (NotifyTheftRequestBOMap) references

\RAPDRPBillingMeteringServiceModule\NotifyTheftRequestSubMap.map (NotifyTheftRequestSubMap)
NotifyTheftRequestSubMap.map (NotifyTheftRequestSubMap) references

\RAPDRPBillingMeteringServiceLib\BOs\NotifyTheft.xsd (NotifyTheft) \RAPDRPGISServiceforBillingMeteringLib\com\upcl\www\NotifyTheft\notifyTheftInput.xsd (notifyTheftInput)
RAPDRPBillingMeteringServiceModule (RAPDRPBillingMeteringServiceModule) references

\RAPDRPBillingMeteringServiceModule\BusinessFault1Map.map (BusinessFault1Map) \RAPDRPBillingMeteringServiceModule\BusinessFaultMap.map (BusinessFaultMap) \RAPDRPBillingMeteringServiceModule\ConsumerMapRequest.map (ConsumerMapRequest) \RAPDRPBillingMeteringServiceModule\MeteringBillingTxInfExport1.export (MeteringBillingTxInfExport1) \RAPDRPBillingMeteringServiceModule\NotifyMeterReplacementBOMap.map (NotifyMeterReplacementBOMap) \RAPDRPBillingMeteringServiceModule\NotifyMeterReplacementBusinessExMap.map (NotifyMeterReplacementBusinessExMap) \RAPDRPBillingMeteringServiceModule\NotifyMeterReplacementResponseBOMap.map (NotifyMeterReplacementResponseBOMap) \RAPDRPBillingMeteringServiceModule\xslt\NotifyMeterReplacementRuntimeFault_res_1.map (NotifyMeterReplacementRuntimeFault_res_1) \RAPDRPBillingMeteringServiceModule\NotifyMeterReplacementServiceImport1.import (NotifyMeterReplacementServiceImport1) \RAPDRPBillingMeteringServiceModule\xslt\NotifyTheftGISFault_res_1.map (NotifyTheftGISFault_res_1) \RAPDRPBillingMeteringServiceModule\NotifyTheftRequestBOMap.map (NotifyTheftRequestBOMap) \RAPDRPBillingMeteringServiceModule\xslt\NotifyTheftRequestMapFail_req_1.map (NotifyTheftRequestMapFail_req_1) \RAPDRPBillingMeteringServiceModule\NotifyTheftRequestSubMap.map (NotifyTheftRequestSubMap) \RAPDRPBillingMeteringServiceModule\NotifyTheftResponseBOMap.map (NotifyTheftResponseBOMap) \RAPDRPBillingMeteringServiceModule\NotifyTheftServiceImport1.import (NotifyTheftServiceImport1) \RAPDRPBillingMeteringServiceModule\OptimumRouteMapConsumerRspMap.map (OptimumRouteMapConsumerRspMap) \RAPDRPBillingMeteringServiceModule\OptimumRouteMapReqMap.map (OptimumRouteMapReqMap) \RAPDRPBillingMeteringServiceModule\OptimumRouteMapRspMap.map (OptimumRouteMapRspMap) \RAPDRPBillingMeteringServiceModule\OptimumRouteMapforConsumerImport1.import (OptimumRouteMapforConsumerImport1) \RAPDRPBillingMeteringServiceModule\OptimumroutemapforBillDistributionMeterReadingImport1.import (OptimumroutemapforBillDistributionMeterReadingImport1) \RAPDRPBillingMeteringServiceModule\RAPDRPBillingMeteringServiceModule.mfc (RAPDRPBillingMeteringServiceModule) \RAPDRPBillingMeteringServiceModule\xslt\XSLTransformation1_req_1.map (XSLTransformation1_req_1) \RAPDRPBillingMeteringServiceModule\xslt\XSLTransformation1_res_1.map (XSLTransformation1_res_1) \RAPDRPBillingMeteringServiceModule\xslt\XSLTransformation1_res_2.map (XSLTransformation1_res_2) \RAPDRPBillingMeteringServiceModule\xslt\XSLTransformation2_req_1.map (XSLTransformation2_req_1) \RAPDRPBillingMeteringServiceModule\xslt\XSLTransformation2_res_1.map (XSLTransformation2_res_1) \RAPDRPBillingMeteringServiceModule\sca.module (RAPDRPBillingMeteringServiceModule)
RAPDRPBillingMeteringServiceModule.mfc (RAPDRPBillingMeteringServiceModule) references

\RAPDRPBillingMeteringServiceModule\BusinessFault1Map.map (BusinessFault1Map) \RAPDRPBillingMeteringServiceModule\BusinessFaultMap.map (BusinessFaultMap) \RAPDRPBillingMeteringServiceModule\ConsumerMapRequest.map (ConsumerMapRequest)
- 104 -
Cross Reference.
\RAPDRPBillingMeteringServiceLib\inf\MeteringBillingTxInf.wsdl (MeteringBillingTxInf)
Nov 14, 2011
\RAPDRPBillingMeteringServiceModule\NotifyMeterReplacementBOMap.map (NotifyMeterReplacementBOMap) \RAPDRPBillingMeteringServiceModule\NotifyMeterReplacementBusinessExMap.map (NotifyMeterReplacementBusinessExMap) \RAPDRPBillingMeteringServiceModule\NotifyMeterReplacementResponseBOMap.map (NotifyMeterReplacementResponseBOMap) \RAPDRPBillingMeteringServiceModule\xslt\NotifyMeterReplacementRuntimeFault_res_1.map \RAPDRPBillingMeteringServiceModule\xslt\NotifyTheftGISFault_res_1.map \RAPDRPBillingMeteringServiceModule\NotifyTheftRequestBOMap.map (NotifyTheftRequestBOMap) \RAPDRPBillingMeteringServiceModule\xslt\NotifyTheftRequestMapFail_req_1.map \RAPDRPBillingMeteringServiceModule\NotifyTheftResponseBOMap.map (NotifyTheftResponseBOMap) \RAPDRPBillingMeteringServiceLib\inf\OptimumRouteInf.wsdl (OptimumRouteInf) \RAPDRPBillingMeteringServiceModule\OptimumRouteMapConsumerRspMap.map (OptimumRouteMapConsumerRspMap) \RAPDRPBillingMeteringServiceModule\OptimumRouteMapReqMap.map (OptimumRouteMapReqMap) \RAPDRPBillingMeteringServiceModule\OptimumRouteMapRspMap.map (OptimumRouteMapRspMap) \RAPDRPGISServiceforBillingMeteringLib\OptimumroutemapforBillDistributionMeterReadingService.wsdl (OptimumroutemapforBillDistributionMeterReading) \RAPDRPBillingMeteringServiceModule\xslt\XSLTransformation1_req_1.map \RAPDRPBillingMeteringServiceModule\xslt\XSLTransformation1_res_1.map \RAPDRPBillingMeteringServiceModule\xslt\XSLTransformation1_res_2.map \RAPDRPBillingMeteringServiceModule\xslt\XSLTransformation2_req_1.map \RAPDRPBillingMeteringServiceModule\xslt\XSLTransformation2_res_1.map \RAPDRPGISServiceforBillingMeteringLib\_230\_163\_30\_124\notifymeterreplacement\notifymeterreplacementservice_wsdl. wsdl (NotifyMeterReplacementService) \RAPDRPGISServiceforBillingMeteringLib\_230\_163\_30\_124\notifytheft\notifytheftservice_wsdl.wsdl (NotifyTheftService) \RAPDRPGISServiceforBillingMeteringLib\_200\_8\_1\_10\optimumroutemap\optimumroutemapforconsumer_wsdl.wsdl (OptimumRouteMapforConsumer)
sca.module (RAPDRPBillingMeteringServiceModule) references

\RAPDRPBillingMeteringServiceLib\inf\MeteringBillingTxInf.wsdl (MeteringBillingTxInf) \RAPDRPBillingMeteringServiceLib\inf\OptimumRouteInf.wsdl (OptimumRouteInf) \RAPDRPGISServiceforBillingMeteringLib\OptimumroutemapforBillDistributionMeterReadingService.wsdl (OptimumroutemapforBillDistributionMeterReading) \RAPDRPBillingMeteringServiceModule\RAPDRPBillingMeteringServiceModule.mfc \RAPDRPGISServiceforBillingMeteringLib\_230\_163\_30\_124\notifymeterreplacement\notifymeterreplacementservice_wsdl. wsdl (NotifyMeterReplacementService) \RAPDRPGISServiceforBillingMeteringLib\_230\_163\_30\_124\notifytheft\notifytheftservice_wsdl.wsdl (NotifyTheftService) \RAPDRPGISServiceforBillingMeteringLib\_200\_8\_1\_10\optimumroutemap\optimumroutemapforconsumer_wsdl.wsdl (OptimumRouteMapforConsumer)
Referenced by list \RAPDRPBillingMeteringServiceLib\BOs\NotifyTheft.xsd (NotifyTheft) is referenced by

NotifyTheftRequestSubMap.map (NotifyTheftRequestSubMap)
\RAPDRPBillingMeteringServiceLib\inf\MeteringBillingTxInf.wsdl (MeteringBillingTxInf) is referenced by

sca.module (RAPDRPBillingMeteringServiceModule) RAPDRPBillingMeteringServiceModule.mfc (RAPDRPBillingMeteringServiceModule)
\RAPDRPBillingMeteringServiceLib\inf\OptimumRouteInf.wsdl (OptimumRouteInf) is referenced by

- 105 -
Cross Reference.
Nov 14, 2011
\RAPDRPBillingMeteringServiceModule\BusinessFault1Map.map (BusinessFault1Map) is referenced by

RAPDRPBillingMeteringServiceModule (RAPDRPBillingMeteringServiceModule) RAPDRPBillingMeteringServiceModule.mfc (RAPDRPBillingMeteringServiceModule)
\RAPDRPBillingMeteringServiceModule\BusinessFaultMap.map (BusinessFaultMap) is referenced by

\RAPDRPBillingMeteringServiceModule\ConsumerMapRequest.map (ConsumerMapRequest) is referenced by

\RAPDRPBillingMeteringServiceModule\MeteringBillingTxInfExport1.export (MeteringBillingTxInfExport1) is
referenced by RAPDRPBillingMeteringServiceModule (RAPDRPBillingMeteringServiceModule)
\RAPDRPBillingMeteringServiceModule\NotifyMeterReplacementBOMap.map (NotifyMeterReplacementBOMap) is referenced by

\RAPDRPBillingMeteringServiceModule\NotifyMeterReplacementBusinessExMap.map (NotifyMeterReplacementBusinessExMap) is referenced by

\RAPDRPBillingMeteringServiceModule\NotifyMeterReplacementResponseBOMap.map (NotifyMeterReplacementResponseBOMap) is referenced by

\RAPDRPBillingMeteringServiceModule\NotifyMeterReplacementServiceImport1.import (NotifyMeterReplacementServiceImport1) is referenced by

RAPDRPBillingMeteringServiceModule (RAPDRPBillingMeteringServiceModule)
\RAPDRPBillingMeteringServiceModule\NotifyTheftRequestBOMap.map (NotifyTheftRequestBOMap) is referenced by RAPDRPBillingMeteringServiceModule (RAPDRPBillingMeteringServiceModule) RAPDRPBillingMeteringServiceModule.mfc (RAPDRPBillingMeteringServiceModule)
\RAPDRPBillingMeteringServiceModule\NotifyTheftRequestSubMap.map (NotifyTheftRequestSubMap) is referenced by RAPDRPBillingMeteringServiceModule (RAPDRPBillingMeteringServiceModule) NotifyTheftRequestBOMap.map (NotifyTheftRequestBOMap)
\RAPDRPBillingMeteringServiceModule\NotifyTheftResponseBOMap.map (NotifyTheftResponseBOMap) is referenced by RAPDRPBillingMeteringServiceModule (RAPDRPBillingMeteringServiceModule) RAPDRPBillingMeteringServiceModule.mfc (RAPDRPBillingMeteringServiceModule)
\RAPDRPBillingMeteringServiceModule\NotifyTheftServiceImport1.import (NotifyTheftServiceImport1) is referenced by RAPDRPBillingMeteringServiceModule (RAPDRPBillingMeteringServiceModule)
\RAPDRPBillingMeteringServiceModule\OptimumRouteMapConsumerRspMap.map (OptimumRouteMapConsumerRspMap) is referenced by

- 106 -
Cross Reference.
Nov 14, 2011
\RAPDRPBillingMeteringServiceModule\OptimumRouteMapReqMap.map (OptimumRouteMapReqMap) is referenced by RAPDRPBillingMeteringServiceModule (RAPDRPBillingMeteringServiceModule) RAPDRPBillingMeteringServiceModule.mfc (RAPDRPBillingMeteringServiceModule)
\RAPDRPBillingMeteringServiceModule\OptimumRouteMapRspMap.map (OptimumRouteMapRspMap) is referenced by RAPDRPBillingMeteringServiceModule (RAPDRPBillingMeteringServiceModule) RAPDRPBillingMeteringServiceModule.mfc (RAPDRPBillingMeteringServiceModule)
\RAPDRPBillingMeteringServiceModule\OptimumRouteMapforConsumerImport1.import (OptimumRouteMapforConsumerImport1) is referenced by

\RAPDRPBillingMeteringServiceModule\OptimumroutemapforBillDistributionMeterReadingImport1.import (OptimumroutemapforBillDistributionMeterReadingImport1) is referenced by

\RAPDRPBillingMeteringServiceModule\RAPDRPBillingMeteringServiceModule.mfc is referenced by
sca.module (RAPDRPBillingMeteringServiceModule)
\RAPDRPBillingMeteringServiceModule\RAPDRPBillingMeteringServiceModule.mfc (RAPDRPBillingMeteringServiceModule) is referenced by

\RAPDRPBillingMeteringServiceModule\sca.module (RAPDRPBillingMeteringServiceModule) is referenced by

\RAPDRPBillingMeteringServiceModule\xslt\NotifyMeterReplacementRuntimeFault_res_1.map is referenced by
RAPDRPBillingMeteringServiceModule.mfc (RAPDRPBillingMeteringServiceModule)
\RAPDRPBillingMeteringServiceModule\xslt\NotifyMeterReplacementRuntimeFault_res_1.map (NotifyMeterReplacementRuntimeFault_res_1) is referenced by

\RAPDRPBillingMeteringServiceModule\xslt\NotifyTheftGISFault_res_1.map is referenced by
\RAPDRPBillingMeteringServiceModule\xslt\NotifyTheftGISFault_res_1.map (NotifyTheftGISFault_res_1) is referenced by RAPDRPBillingMeteringServiceModule (RAPDRPBillingMeteringServiceModule)
\RAPDRPBillingMeteringServiceModule\xslt\NotifyTheftRequestMapFail_req_1.map is referenced by
\RAPDRPBillingMeteringServiceModule\xslt\NotifyTheftRequestMapFail_req_1.map (NotifyTheftRequestMapFail_req_1) is referenced by

\RAPDRPBillingMeteringServiceModule\xslt\XSLTransformation1_req_1.map is referenced by
\RAPDRPBillingMeteringServiceModule\xslt\XSLTransformation1_req_1.map (XSLTransformation1_req_1) is
\RAPDRPBillingMeteringServiceModule\xslt\XSLTransformation1_res_1.map is referenced by
\RAPDRPBillingMeteringServiceModule\xslt\XSLTransformation1_res_1.map (XSLTransformation1_res_1) is
- 107 -
Cross Reference.
Nov 14, 2011
\RAPDRPBillingMeteringServiceModule\xslt\XSLTransformation2_req_1.map is referenced by
\RAPDRPBillingMeteringServiceModule\xslt\XSLTransformation2_req_1.map (XSLTransformation2_req_1) is
\RAPDRPGISServiceforBillingMeteringLib\OptimumroutemapforBillDistributionMeterReadingService.wsdl (OptimumroutemapforBillDistributionMeterReading) is referenced by

\RAPDRPGISServiceforBillingMeteringLib\_200\_8\_1\_10\optimumroutemap\optimumroutemapforconsumer_ wsdl.wsdl (OptimumRouteMapforConsumer) is referenced by

\RAPDRPGISServiceforBillingMeteringLib\_230\_163\_30\_124\notifymeterreplacement\notifymeterreplacemen tservice_wsdl.wsdl (NotifyMeterReplacementService) is referenced by

\RAPDRPGISServiceforBillingMeteringLib\_230\_163\_30\_124\notifytheft\notifytheftservice_wsdl.wsdl (NotifyTheftService) is referenced by

\RAPDRPGISServiceforBillingMeteringLib\com\upcl\www\NotifyTheft\notifyTheftInput.xsd (notifyTheftInput) is
referenced by NotifyTheftRequestSubMap.map (NotifyTheftRequestSubMap)
- 108 -
Documentation generation settings.
Nov 14, 2011
25 Documentation generation settings

General settings
Title: Author: Date: TOC nesting level: CA_MDM_Integration Infinite Nov 14, 2011 7
Utilized documentation units BusinessFault1Map.map (BusinessFault1Map)

Documentation unit: Documentation type: Business Object Map Documentation Unit detailed
BusinessFaultMap.map (BusinessFaultMap)
ConsumerMapRequest.map (ConsumerMapRequest)
NotifyMeterReplacementBOMap.map (NotifyMeterReplacementBOMap)
NotifyMeterReplacementBusinessExMap.map (NotifyMeterReplacementBusinessExMap)
NotifyMeterReplacementResponseBOMap.map (NotifyMeterReplacementResponseBOMap)
NotifyMeterReplacementRuntimeFault_res_1.map (NotifyMeterReplacementRuntimeFault_res_1)
NotifyTheftGISFault_res_1.map (NotifyTheftGISFault_res_1)
NotifyTheftRequestBOMap.map (NotifyTheftRequestBOMap)
NotifyTheftRequestMapFail_req_1.map (NotifyTheftRequestMapFail_req_1)
NotifyTheftRequestSubMap.map (NotifyTheftRequestSubMap)
NotifyTheftResponseBOMap.map (NotifyTheftResponseBOMap)
OptimumRouteMapConsumerRspMap.map (OptimumRouteMapConsumerRspMap)
OptimumRouteMapReqMap.map (OptimumRouteMapReqMap)
Documentation unit: Business Object Map Documentation Unit
- 109 -
Documentation generation settings.

Documentation type: detailed
Nov 14, 2011
OptimumRouteMapRspMap.map (OptimumRouteMapRspMap)
Documentation unit: Documentation type: Business Integration Module Documentation Unit detailed
Documentation unit: Documentation type: Mediation Flow Documentation Unit detailed
XSLTransformation1_req_1.map (XSLTransformation1_req_1)
XSLTransformation1_res_1.map (XSLTransformation1_res_1)
XSLTransformation2_req_1.map (XSLTransformation2_req_1)
sca.module (RAPDRPBillingMeteringServiceModule)
Documentation unit: Documentation type: Assembly Diagram Documentation Unit detailed
- 110 -

Billing

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Billing

Transféré par

Droits d'auteur :

Formats disponibles

CA_MDM_Integration

Author: Infinite Date: Nov 14, 2011

Nov 14, 2011

Nov 14, 2011

Nov 14, 2011

Nov 14, 2011

Nov 14, 2011

Nov 14, 2011

1.2 All Resources

Nov 14, 2011

Assembly Diagram "RAPDRPBillingMeteringServiceModule".

Nov 14, 2011

2 Assembly Diagram "RAPDRPBillingMeteringServiceModule"

2.2 Assembly Diagram Settings

2.3 Component Overview

NotifyMeterReplacementServi- NotifyMeterReplacementSercePartner viceImport1

Assembly Diagram "RAPDRPBillingMeteringServiceModule".

Nov 14, 2011

OptimumroutemapforBillDistributionMeterReading (http://www.upcl.com/Optimum routemapforBillDistributionMeterReading) OptimumRouteMapforConsumer (http://www.upcl.com/Optimum RouteMapforConsumer)

2.5 Quality of Service Qualifiers Overview

2.5.2 Join transaction

2.5.4 Suspend transaction

Assembly Diagram "RAPDRPBillingMeteringServiceModule".

Nov 14, 2011

2.6 Component Settings

2.6.1.2 Interfaces 2.6.1.2.1 Interface "MeteringBillingTxInf"

2.6.2 Mediation Flow "RAPDRPBillingMeteringServiceModule" 2.6.2.1 General Settings

2.6.2.2 Interfaces 2.6.2.2.1 Interface "MeteringBillingTxInf"

Quality of service (QOS) Qualifiers: Join transaction

Assembly Diagram "RAPDRPBillingMeteringServiceModule".

Nov 14, 2011

Operation "notifyMeterReplacement" Quality of service (QOS) Qualifiers: Join transaction

Operation "optimumRouteMap" Quality of service (QOS) Qualifiers: Join transaction

2.6.2.2.2 Interface "OptimumRouteInf"

Quality of service (QOS) Qualifiers: Join transaction

Operation "optimumRouteDataService" Quality of service (QOS) Qualifiers: Join transaction

Operation "optimumRouteMapService" Quality of service (QOS) Qualifiers: Join transaction

2.6.2.3 References 2.6.2.3.1 Partner Reference "NotifyTheftServicePartner"

Assembly Diagram "RAPDRPBillingMeteringServiceModule".

Nov 14, 2011

2.6.2.3.1.1 Interface "NotifyTheftService"

2.6.2.3.2 Partner Reference "NotifyMeterReplacementServicePartner"

Quality of service (QOS) Qualifiers: Suspend transaction

2.6.2.3.2.1 Interface "NotifyMeterReplacementService"

2.6.2.3.3 Partner Reference "OptimumroutemapforBillDistributionMeterReadingPartner"

Quality of service (QOS) Qualifiers: Suspend transaction

Assembly Diagram "RAPDRPBillingMeteringServiceModule".

Nov 14, 2011

2.6.2.3.3.1 Interface "OptimumroutemapforBillDistributionMeterReading"

2.6.2.3.4 Partner Reference "OptimumRouteMapforConsumerPartner"

Quality of service (QOS) Qualifiers: Suspend transaction

2.6.2.3.4.1 Interface "OptimumRouteMapforConsumer"

Quality of service (QOS) Qualifiers: Transaction

2.6.3 Import "NotifyMeterReplacementServiceImport1" 2.6.3.1 General Settings

Assembly Diagram "RAPDRPBillingMeteringServiceModule".

Nov 14, 2011

2.6.3.2 Interfaces 2.6.3.2.1 Interface "NotifyMeterReplacementService"

Quality of service (QOS) Qualifiers: Join transaction

Operation "getNotifyMeterReplacement" Quality of service (QOS) Qualifiers: Join transaction

2.6.4 Import "NotifyTheftServiceImport1" 2.6.4.1 General Settings

2.6.4.2 Interfaces 2.6.4.2.1 Interface "NotifyTheftService"

Quality of service (QOS) Qualifiers: Join transaction

Operation "getNotifyTheft" Quality of service (QOS) Qualifiers: Join transaction

2.6.5 Import "OptimumRouteMapforConsumerImport1" 2.6.5.1 General Settings