Already a subscriber? 

MADCAD.com Free Trial
Sign up for a 3 day free trial to explore the MADCAD.com interface, PLUS access the
2009 International Building Code to see how it all works.
If you like to setup a quick demo, let us know at support@madcad.com
or +1 800.798.9296 and we will be happy to schedule a webinar for you.
Security check
Please login to your personal account to use this feature.
Please login to your authorized staff account to use this feature.
Are you sure you want to empty the cart?
BS EN 61968-100:2013 Application integration at electric utilities. System interfaces for distribution management - Implementation profiles, 2013
- 30288627-VOR.pdf [Go to Page]
- English [Go to Page]
- CONTENTS
- FOREWORD
- INTRODUCTION
- 1 Scope
- 2 Normative References
- 3 Terms, definitions and abbreviations [Go to Page]
- 3.1 Terms and definitions
- 3.2 Abbreviations
- 3.3 Terminology for common integration technologies [Go to Page]
- 3.3.1 General
- 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)
- 3.3.7 Web Services (WS)
- 3.3.8 Web Services Definition Language (WSDL)
- 3.3.9 XML Schema (XSD)
- 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
- 3.3.16 Query
- 3.3.17 Transaction
- 3.3.18 Event
- 4 Use Cases [Go to Page]
- 4.1 General
- 4.2 Simple request/reply
- 4.3 Request/reply using an ESB
- 4.4 Events
- 4.5 Transactions
- 4.6 Callback
- 4.7 Adapters
- 4.8 Complex messaging
- 4.9 Orchestration
- 4.10 Application-level use cases
- 5 Integration Patterns [Go to Page]
- 5.1 General
- 5.2 Client and server perspectives [Go to Page]
- 5.2.1 General
- 5.2.2 Basic web service pattern
- 5.2.3 Basic JMS request/reply pattern
- 5.2.4 Event listeners
- 5.2.5 Asynchronous request/reply pattern
- 5.3.3 ESB messaging patterns using web service request
- 5.3.4 ESB request handling to web service
- 5.3 Bus perspective [Go to Page]
- 5.3.1 General
- 5.3.2 ESB messaging pattern using JMS
- 5.3.5 ESB request handling via adapter
- 5.3.6 Custom integration patterns
- 6 Message organization [Go to Page]
- 6.1 General
- 6.2 IEC 61968 messages [Go to Page]
- 6.2.1 General
- 6.2.2 Verbs
- 6.2.3 Nouns
- 6.2.4 Payloads
- 6.3 Common message envelope [Go to Page]
- 6.3.1 General
- 6.3.2 Message header structure
- 6.3.3 Request message structures
- 6.3.4 Response Message Structures
- 6.3.5 Event message structures
- 6.3.6 Fault message structures
- 6.4 Payload structures
- 6.5 Strongly-typed payloads
- 6.6 SOAP message envelope
- 6.7 Request processing
- 6.8 Event processing
- 6.9 Message correlation
- 6.10 Complex transaction processing using OperationSet [Go to Page]
- 6.10.1 General
- 6.10.2 OperationSet Element
- 6.10.3 Patterns
- 6.10.4 OperationSet example
- 6.11 Representation of time
- 6.12 Other conventions and best practices
- 6.13 Technical interoperability
- 6.14 Service level agreements
- 6.15 Auditing, monitoring and management
- 7 Payload specifications
- 8 Interface specifications [Go to Page]
- 8.1 General
- 8.2 Application-level specifications
- 8.3 Web service interfaces [Go to Page]
- 8.3.1 General
- 8.3.2 WSDL Structure
- 8.3.3 Document style SOAP binding
- 8.3.4 Strongly-typed web services
- 8.4 JMS [Go to Page]
- 8.4.1 General
- 8.4.2 Topic and queue naming
- 8.4.3 JMS message fields
- 9 Security
- 10 Version control
- Annex A (normative) XML schema for common message envelope
- Annex B (normative) Verbs
- Annex C (normative) Procedure for strongly typed WSDL generation
- Annex D (normative) Generic WSDL
- Annex E (informative) AMQP
- Annex F (informative) Payload Compression Example
- Annex G (informative) XMPP
- Bibliography
- Figures [Go to Page]
- Figure 1 – Overview of Scope
- Figure 2 – Simple Request/Reply
- Figure 3 – Request/reply using intermediaries
- Figure 4 – Events
- Figure 5 – Point-to-Point (One Way) Pattern
- Figure 6 – Transaction Example
- Figure 7 – Callbacks
- Figure 8 – Use of Adapters
- Figure 9 – Complex messaging
- Figure 10 – Application-level use case example
- Figure 11 – Basic request/reply using web services
- Figure 12 – Basic request/reply using JMS
- Figure 13 – Event listeners using JMS
- Figure 14 – Asynchronous request/reply pattern
- Figure 15 – ESB content-based routing
- Figure 16 – ESB with smart proxy and content-based routing
- Figure 17 – ESB with proxies, routers and adapters
- Figure 18 – ESB Integration to non-compliant resources
- Figure 19 – Messaging between clients, servers and an ESB
- Figure 20 – Example payload schema
- Figure 21 – Common message envelope
- Figure 22 – Common message header structure
- Figure 23 – Request message structure
- Figure 24 – XML for example RequestMessage
- Figure 25 – Example 'Get' profile
- Figure 26 – ResponseMessage structure
- Figure 27 – Reply message states
- Figure 28 – Error structure
- Figure 29 – XML for example ResponseMessage
- Figure 30 – XML example of payload compression
- Figure 31 – XML example for error ResponseMessage
- Figure 32 – EventMessage structure
- Figure 33 – XML example for EventMessage
- Figure 34 – Fault message structure
- Figure 35 – Message payload container – Generic
- Figure 36 – Message payload container – Type specific example
- Figure 37 – SOAP bindings
- Figure 38 – SOAP envelope example for strong typing
- Figure 39 – Message OperationSet Element
- Figure 40 – OperationSet details
- Figure 41 – Transactional Request/Response (non-OperationSet)
- Figure 42 – Published events (non-OperationSet)
- Figure 43 – Transactional Request/Response (OperationSet)
- Figure 44 – Published event (OperationSet)
- Figure 45 – Information Models, Profiles and Messages
- Figure 46 – Contextual Profile Design in CIMTool
- Figure 47 – Example message payload schema
- Figure 48 – Example payload XML schema
- Figure 49 – Example message XML
- Figure 50 – Example complex business process
- Figure 51 – WSDL structure
- Figure 52 – Web service usage example
- Figure 53 – Example Organization of Topics and Queues
- Figure C.1 – Process for WSDL Generation
- Figure C.3 – WSDL folder structure
- Figure C.4 – WSDL type definitions
- Figure D.1 – Generic WSDL structure
- Tables [Go to Page]
- Table 1 – Verbs and their Usage
- Table 2 – Payload usages
- Table B.1 – Normative definitions of verbs
- Français [Go to Page]
- SOMMAIRE
- AVANT-PROPOS
- INTRODUCTION
- 1 Domaine d’application
- 2 Références normatives
- 3 Termes, définitions et abréviations [Go to Page]
- 3.1 Termes et définitions
- 3.2 Abréviations
- 3.3 Terminologie des technologies d'intégration communes [Go to Page]
- 3.3.1 Généralités
- 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)
- 3.3.7 Web Services (WS)
- 3.3.8 Web Services Definition Language (WSDL)
- 3.3.9 XML Schema (XSD)
- 3.3.10 Representational State Transfer (REST)
- 3.3.11 Queue
- 3.3.12 Thème
- 3.3.13 Destination de message
- 3.3.14 Demande (Request)
- 3.3.15 Réponse (Response)
- 3.3.16 Requête (Query)
- 3.3.17 Transaction
- 3.3.18 Evénement (Event)
- 4 Cas d’utilisation [Go to Page]
- 4.1 Généralités
- 4.2 Demande/ réponse simple
- 4.3 Demande/réponse au moyen d’un ESB
- 4.4 Evénements
- 4.5 Transactions
- 4.6 Procédure de rappel (Callback)
- 4.7 Adaptateurs
- 4.8 Messagerie complexe
- 4.9 Orchestration
- 4.10 Cas d’utilisation au niveau de l’application
- 5 Modèles d’intégration [Go to Page]
- 5.1 Généralités
- 5.2 Points de vue du client et du serveur [Go to Page]
- 5.2.1 Généralités
- 5.2.2 Modèle de service Web de base
- 5.2.3 Modèle demande/réponse JMS de base
- 5.2.4 Ecouteurs d’événements
- 5.2.5 Modèle Demande/réponse asynchrone
- 5.3 Point de vue du bus [Go to Page]
- 5.3.1 Généralités
- 5.3.2 Modèle de messagerie ESB qui utilise JMS
- 5.3.3 Modèles de messagerie ESB qui utilise une demande de service Web
- 5.3.4 Traitement de demande ESB à destination d’un service Web
- 5.3.5 Traitement de demande ESB via un adaptateur
- 5.3.6 Modèles d’intégration personnalisés
- 6 Organisation du message [Go to Page]
- 6.1 Généralités
- 6.2 Messages CEI 61968 [Go to Page]
- 6.2.1 Généralités
- 6.2.2 Verbes (Verbs)
- 6.2.3 Nouns
- 6.2.4 Charges utiles
- 6.3 Enveloppe de message commune [Go to Page]
- 6.3.1 Généralités
- 6.3.2 Structure de l’en-tête du message
- 6.3.3 Structures de RequestMessage (message de demande)
- 6.3.4 Structures de ResponseMessage (message de réponse)
- 6.3.5 Structures de EventMessage (message d’événement)
- 6.3.6 Structures de FaultMessage (message de défaut)
- 6.4 Structures de Payload (charge utile)
- 6.5 Charges utiles fortement typées
- 6.6 Enveloppe de message SOAP
- 6.7 Traitement de la demande
- 6.8 Traitement de l’événement
- 6.9 Corrélation de messages
- 6.10 Traitement de transactions complexes au moyen d’OperationSet [Go to Page]
- 6.10.1 Généralités
- 6.10.2 Elément OperationSet
- 6.10.3 Modèles (patterns)
- 6.10.4 Exemple de OperationSet
- 6.11 Représentation de l’heure
- 6.12 Autres conventions et meilleures pratiques
- 6.13 Interopérabilité technique
- 6.14 Contrats sur les niveaux de service
- 6.15 Audit, surveillance et gestion
- 7 Spécifications de la charge utile
- 8 Spécifications d’interface [Go to Page]
- 8.1 Généralités
- 8.2 Spécifications au niveau de l’application
- 8.3 Interfaces de services Web [Go to Page]
- 8.3.1 Généralités
- 8.3.2 Structure WSDL
- 8.3.3 Lien SOAP de style document
- 8.3.4 Services Web fortement typés
- 8.4 JMS [Go to Page]
- 8.4.1 Généralités
- 8.4.2 Désignation des thèmes et files d’attente
- 8.4.3 Champs de messages JMS
- 9 Sécurité
- 10 Contrôle de version
- Annexe A (normative) Schéma XML pour enveloppe de message commune
- Annexe B (normative) Verbes
- Annexe C (normative) Procédure pour les services Web fortement typés
- Annexe D (normative) WSDL générique
- Annexe E (informative) AMQP
- Annexe F (informative) Exemple de compression de charge utile
- Annexe G (informative) XMPP
- Bibliographie
- Figures [Go to Page]
- Figure 1 – Vue d'ensemble du domaine d'application
- Figure 2 – Demande/Réponse simple
- Figure 3 – Demande/réponse qui utilise des intermédiaires
- Figure 4 – Evénement
- Figure 5 – Modèle point-to-point (unidirectionnel)
- Figure 6 – Exemple de transaction
- Figure 7 – Procédures de rappel
- Figure 8 – Utilisation d’adaptateurs
- Figure 9 – Messagerie complexe
- Figure 10 – Exemple de cas d'utilisation au niveau de l'application
- Figure 11 – Demande/réponse de base qui utilise des services Web
- Figure 12 – Demande/réponse de base qui utilise JMS
- Figure 13 – Ecouteurs d'évènements qui utilisent JMS
- Figure 14 – Modèle Demande/Réponse asynchrone
- Figure 15 – Routage basé sur du contenu ESB
- Figure 16 – ESB avec Smart Proxy et routage basé sur du contenu
- Figure 17 – ESB avec proxies, routeurs et adaptateurs
- Figure 18 – Intégration d'ESB à des ressources non conformes
- Figure 19 – Messagerie entre clients, serveurs et un ESB
- Figure 20 – Exemple de schéma de charge utile
- Figure 21 – Enveloppe de message commune
- Figure 22 – Structure commune de l'en-tête de message
- Figure 23 – Structure d’un RequestMessage
- Figure 24 – Exemple XML de RequestMessage
- Figure 25 – Exemple de profil ‘'Get'’
- Figure 26 – Structure d’un ResponseMessage
- Figure 27 – Etats du message de réponse
- Figure 28 – Structure de Error (erreur)
- Figure 29 – Exemple XML de ResponseMessage
- Figure 30 – Exemple XML de Compression de charge utile
- Figure 31 – Exemple XML d’un Error ResponseMessage
- Figure 32 – Structure de EventMessage
- Figure 33 – Exemple XML de EventMessage
- Figure 34 – Structure de FaultMessage
- Figure 35 – Conteneur de charge utile du message – Générique
- Figure 36 – Conteneur de charge utile du message – Spécifique au Type
- Figure 37 – Liens SOAP
- Figure 38 – Exemple d’enveloppe SOAP à caractère fortement typé
- Figure 39 – Elément OperationSet du message
- Figure 40 – Détails de OperationSet
- Figure 41 – Demande/réponse transactionnelle (non OperationSet)
- Figure 42 – Evènements publiés (non OperationSet)
- Figure 43 – Demande/réponse transactionnelle (OperationSet)
- Figure 44 – Evènements publiés (OperationSet)
- Figure 45 – Modèles, profils et messages d'information
- Figure 46 – Conception de profil contextuel dans CIMTool
- Figure 47 – Exemple de schéma de charge utile du message
- Figure 48 – Exemple de schéma de charge utile XML
- Figure 49 – Exemple de message XML
- Figure 50 – Exemple de processus commercial complexe
- Figure 51 – Structure WSDL
- Figure 52 – Exemple d'utilisation d'un service internet
- Figure 53 – Exemple d'organisation des thèmes et files d'attente
- Figure C.1 – Processus de génération WSDL
- Figure C.3 – Structure d'un répertoire WSDL
- Figure C.4 – Définitions de type WSDL
- Figure D.1 – Structure WSDL générique
- Tableaux [Go to Page]
- Table 1 – Verbes et leur utilisation
- Table 2 – Utilisations de charge utile
- Tableau B.1 – Définitions normatives des verbes [Go to Page]