🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BS EN 61968-100:2013

BS EN 61968-100:2013

$215.11

Application integration at electric utilities. System interfaces for distribution management – Implementation profiles

Published By Publication Date Number of Pages
BSI 2013 116
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Category:

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

IEC 61968-100:2013 specifies an implementation profile for the application of the other parts of IEC 61968 using common integration technologies, including JMS and web services. This International Standard also provides guidance with respect to the use of Enterprise Service Bus (ESB) technologies. This provides a means to derive interoperable implementations of IEC 61968-3 to IEC 61968-9. At the same time, this International Standard can be leveraged beyond information exchanges defined by IEC 61968, such as for the integration of market systems or general enterprise integration.

PDF Catalog

PDF Pages PDF Title
6 English
CONTENTS
10 INTRODUCTION
11 1 Scope
Figures
Figure 1 – Overview of Scope
12 2 Normative References
3 Terms, definitions and abbreviations
3.1 Terms and definitions
3.2 Abbreviations
13 3.3 Terminology for common integration technologies
3.3.1 General
14 3.3.2 Enterprise Service Bus (ESB)
3.3.3 Java Messaging Service (JMS)
3.3.4 Service-Oriented Architecture (SOA)
3.3.5 Event-Driven Architecture (EDA)
3.3.6 Simple Object Access Protocol (SOAP)
15 3.3.7 Web Services (WS)
3.3.8 Web Services Definition Language (WSDL)
3.3.9 XML Schema (XSD)
16 3.3.10 Representational State Transfer (REST)
3.3.11 Queue
3.3.12 Topic
3.3.13 Message Destination
3.3.14 Request
3.3.15 Response
17 3.3.16 Query
3.3.17 Transaction
3.3.18 Event
4 Use Cases
4.1 General
18 4.2 Simple request/reply
4.3 Request/reply using an ESB
Figure 2 – Simple Request/Reply
19 4.4 Events
Figure 3 – Request/reply using intermediaries
20 4.5 Transactions
Figure 4 – Events
21 4.6 Callback
Figure 5 – Point-to-Point (One Way) Pattern
Figure 6 – Transaction Example
22 4.7 Adapters
Figure 7 – Callbacks
23 4.8 Complex messaging
Figure 8 – Use of Adapters
24 4.9 Orchestration
4.10 Application-level use cases
Figure 9 – Complex messaging
25 5 Integration Patterns
5.1 General
5.2 Client and server perspectives
5.2.1 General
Figure 10 – Application-level use case example
26 5.2.2 Basic web service pattern
5.2.3 Basic JMS request/reply pattern
Figure 11 – Basic request/reply using web services
27 Figure 12 – Basic request/reply using JMS
28 5.2.4 Event listeners
Figure 13 – Event listeners using JMS
29 5.2.5 Asynchronous request/reply pattern
5.3 Bus perspective
5.3.1 General
Figure 14 – Asynchronous request/reply pattern
30 5.3.2 ESB messaging pattern using JMS
Figure 15 – ESB content-based routing
31 5.3.3 ESB messaging patterns using web service request
5.3.4 ESB request handling to web service
Figure 16 – ESB with smart proxy and content-based routing
32 5.3.5 ESB request handling via adapter
Figure 17 – ESB with proxies, routers and adapters
33 5.3.6 Custom integration patterns
Figure 18 – ESB Integration to non-compliant resources
34 6 Message organization
6.1 General
6.2 IEC 61968 messages
6.2.1 General
35 6.2.2 Verbs
Figure 19 – Messaging between clients, servers and an ESB
36 6.2.3 Nouns
Tables
Table 1 – Verbs and their Usage
37 6.2.4 Payloads
Figure 20 – Example payload schema
38 6.3 Common message envelope
6.3.1 General
39 6.3.2 Message header structure
Figure 21 – Common message envelope
41 Figure 22 – Common message header structure
42 6.3.3 Request message structures
43 Figure 23 – Request message structure
44 Figure 24 – XML for example RequestMessage
45 6.3.4 Response Message Structures
Figure 25 – Example ‘Get’ profile
46 Figure 26 – ResponseMessage structure
47 Figure 27 – Reply message states
48 Figure 28 – Error structure
49 Figure 29 – XML for example ResponseMessage
Figure 30 – XML example of payload compression
50 6.3.5 Event message structures
Figure 31 – XML example for error ResponseMessage
Figure 32 – EventMessage structure
51 6.3.6 Fault message structures
Figure 33 – XML example for EventMessage
52 6.4 Payload structures
Figure 34 – Fault message structure
53 Figure 35 – Message payload container – Generic
55 6.5 Strongly-typed payloads
Table 2 – Payload usages
56 6.6 SOAP message envelope
Figure 36 – Message payload container – Type specific example
Figure 37 – SOAP bindings
57 6.7 Request processing
Figure 38 – SOAP envelope example for strong typing
58 6.8 Event processing
59 6.9 Message correlation
6.10 Complex transaction processing using OperationSet
6.10.1 General
60 Figure 39 – Message OperationSet Element
61 6.10.2 OperationSet Element
62 Figure 40 – OperationSet details
63 6.10.3 Patterns
Figure 41 – Transactional Request/Response (non-OperationSet)
64 Figure 42 – Published events (non-OperationSet)
Figure 43 – Transactional Request/Response (OperationSet)
65 6.10.4 OperationSet example
Figure 44 – Published event (OperationSet)
67 6.11 Representation of time
6.12 Other conventions and best practices
6.13 Technical interoperability
68 6.14 Service level agreements
6.15 Auditing, monitoring and management
7 Payload specifications
69 Figure 45 – Information Models, Profiles and Messages
Figure 46 – Contextual Profile Design in CIMTool
70 Figure 47 – Example message payload schema
71 Figure 48 – Example payload XML schema
72 8 Interface specifications
8.1 General
8.2 Application-level specifications
Figure 49 – Example message XML
74 8.3 Web service interfaces
8.3.1 General
8.3.2 WSDL Structure
Figure 50 – Example complex business process
75 8.3.3 Document style SOAP binding
Figure 51 – WSDL structure
76 8.3.4 Strongly-typed web services
78 8.4 JMS
8.4.1 General
Figure 52 – Web service usage example
79 8.4.2 Topic and queue naming
Figure 53 – Example Organization of Topics and Queues
80 8.4.3 JMS message fields
9 Security
81 10 Version control
83 Annex A (normative) XML schema for common message envelope
93 Annex B (normative) Verbs
Table B.1 – Normative definitions of verbs
95 Annex C (normative) Procedure for strongly typed WSDL generation
Figure C.1 – Process for WSDL Generation
96 Figure C.3 – WSDL folder structure
97 Figure C.4 – WSDL type definitions
108 Annex D (normative) Generic WSDL
Figure D.1 – Generic WSDL structure
110 Annex E (informative) AMQP
111 Annex F (informative) Payload Compression Example
113 Annex G (informative) XMPP
114 Bibliography

Related products

BS EN 61968-100:2013
$215.11