CAN CSA-ISO IEC 19500-2-2013 Information technology - Object Management Group - Common Object Request Broker Architecture (CORBA) - Part 2 Interoperability.pdf

1、Information technology Object Management Group Common Object Request Broker Architecture (CORBA) Part 2: InteroperabilityCAN/CSA-ISO/IEC 19500-2:13(ISO/IEC 19500-2:2012, IDT)National Standard of CanadaNOT FOR RESALE. / PUBLICATION NON DESTINE LA REVENTE.Legal Notice for StandardsCanadian Standards A

2、ssociation (operating as “CSA Group”) develops standards through a consensus standards development process approved by the Standards Council of Canada. This process brings together volunteers representing varied viewpoints and interests to achieve consensus and develop a standard. Although CSA Group

3、 administers the process and establishes rules to promote fairness in achieving consensus, it does not independently test, evaluate, or verify the content of standards.Disclaimer and exclusion of liabilityThis document is provided without any representations, warranties, or conditions of any kind, e

4、xpress or implied, including, without limitation, implied warranties or conditions concerning this documents fitness for a particular purpose or use, its merchantability, or its non-infringement of any third partys intellectual property rights. CSA Group does not warrant the accuracy, completeness,

5、or currency of any of the information published in this document. CSA Group makes no representations or warranties regarding this documents compliance with any applicable statute, rule, or regulation. IN NO EVENT SHALL CSA GROUP, ITS VOLUNTEERS, MEMBERS, SUBSIDIARIES, OR AFFILIATED COMPANIES, OR THE

6、IR EMPLOYEES, DIRECTORS, OR OFFICERS, BE LIABLE FOR ANY DIRECT, INDIRECT, OR INCIDENTAL DAMAGES, INJURY, LOSS, COSTS, OR EXPENSES, HOWSOEVER CAUSED, INCLUDING BUT NOT LIMITED TO SPECIAL OR CONSEQUENTIAL DAMAGES, LOST REVENUE, BUSINESS INTERRUPTION, LOST OR DAMAGED DATA, OR ANY OTHER COMMERCIAL OR EC

7、ONOMIC LOSS, WHETHER BASED IN CONTRACT, TORT (INCLUDING NEGLIGENCE), OR ANY OTHER THEORY OF LIABILITY, ARISING OUT OF OR RESULTING FROM ACCESS TO OR POSSESSION OR USE OF THIS DOCUMENT, EVEN IF CSA GROUP HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, INJURY, LOSS, COSTS, OR EXPENSES.In publishi

8、ng and making this document available, CSA Group is not undertaking to render professional or other services for or on behalf of any person or entity or to perform any duty owed by any person or entity to another person or entity. The information in this document is directed to those who have the ap

9、propriate degree of experience to use and apply its contents, and CSA Group accepts no responsibility whatsoever arising in any way from any and all use of or reliance on the information contained in this document. CSA Group is a private not-for-profit company that publishes voluntary standards and

10、related documents. CSA Group has no power, nor does it undertake, to enforce compliance with the contents of the standards or other documents it publishes. Intellectual property rights and ownershipAs between CSA Group and the users of this document (whether it be in printed or electronic form), CSA

11、 Group is the owner, or the authorized licensee, of all works contained herein that are protected by copyright, all trade-marks (except as otherwise noted to the contrary), and all inventions and trade secrets that may be contained in this document, whether or not such inventions and trade secrets a

12、re protected by patents and applications for patents. Without limitation, the unauthorized use, modification, copying, or disclosure of this document may violate laws that protect CSA Groups and/or others intellectual property and may give rise to a right in CSA Group and/or others to seek legal red

13、ress for such use, modification, copying, or disclosure. To the extent permitted by licence or by law, CSA Group reserves all intellectual property rights in this document.Patent rightsAttention is drawn to the possibility that some of the elements of this standard may be the subject of patent right

14、s. CSA Group shall not be held responsible for identifying any or all such patent rights. Users of this standard are expressly advised that determination of the validity of any such patent rights is entirely their own responsibility.Authorized use of this documentThis document is being provided by C

15、SA Group for informational and non-commercial use only. The user of this document is authorized to do only the following:If this document is in electronic form:sLOADTHISDOCUMENTONTOACOMPUTERFORTHESOLEPURPOSEOFREVIEWINGITsSEARCHANDBROWSETHISDOCUMENTANDsPRINTTHISDOCUMENTIFITISIN0$ this remains the con

16、tinuing responsibility of the SDO. An NSC reflects a consensus of a number of capable individuals whose collective interests provide, to the greatest practicable extent, a balance of representation of general interests, producers, regulators, users (including consumers), and others with relevant int

17、erests, as may be appropriate to the subject in hand. It normally is a standard which is capable of making a significant and timely contribution to the national interest.Those who have a need to apply standards areencouraged to use NSCs. These standards are subjectto periodic review. Users of NSCs a

18、re cautionedto obtain the latest edition from the SDO which publishes the standard.The responsibility for approving standards as National Standards of Canada rests with theStandards Council of Canada270 Albert Street, Suite 200Ottawa, Ontario, K1P 6N7CanadaAlthough the intended primary application o

19、f this Standard is stated in its Scope, it is importantto note that it remains the responsibility of the users to judge its suitability for their particular purpose.Registered trade-mark of Canadian Standards AssociationCette norme est offerte en anglais seulement pour le moment. Le Groupe CSA publi

20、era la versionen franais ds quelle sera produite par lorganisme rdacteur.TMA trade-mark of the Canadian Standards Association, operating as “CSA Group”National Standard of CanadaPublished in January 2013 by CSA GroupA not-for-profit private sector organization5060 Spectrum Way, Suite 100,January 201

21、3 Mississauga, Ontario, Canada L4W 5N61-800-463-6727 416-747-4044Visit our Online Store at shop.csa.caApproved byStandards Council of CanadaCAN/CSA-ISO/IEC 19500-2:13Information technology Object Management Group Common Object Request Broker Architecture (CORBA) Part 2: InteroperabilityPrepared by I

22、nternationalOrganizationforStandardization/ International Electrotechnical CommissionReviewed byCAN/CSA-ISO/IEC 19500-2:13Information technology Obje ct Management Group CommonObject Request Broker Architecture (CORBA) Part 2: InteroperabilityCSA/4 2013 CSA Group January 2013CAN/CSA-ISO/IEC 19500-2:

23、13Information technology Object Management Group Common Object Request Broker Architecture (CORBA) Part 2: InteroperabilityCSA PrefaceStandards development within the Information Technology sector is harmonized with international standards development. Through the CSA Technical Committee on Informat

24、ion Technology (TCIT), Canadians serve as the Canadian Advisory Committee (CAC) on ISO/IEC Joint Technical Committee 1 on Information Technology (ISO/IEC JTC1) for the Standards Council of Canada (SCC), the ISO member body for Canada and sponsor of the Canadian National Committee of the IEC. Also, a

25、s a member of the International Telecommunication Union (ITU), Canada participates in the International Telegraph and Telephone Consultative Committee (ITU-T).This Standard supersedes CAN/CSA-ISO/IEC 19500-2-04 (adoption of ISO/IEC 19500-2:2003).At the time of publication, ISO/IEC 19500-2:2012 is av

26、ailable from ISO and IEC in English only. CSA Group will publish the French version when it becomes available from ISO and IEC.This International Standard was reviewed by the TCIT under the jurisdiction of the Strategic Steering Committee on Information Technology and deemed acceptable for use in Ca

27、nada. From time to time, ISO/IEC may publish addenda, corrigenda, etc. The TCIT will review these documents for approval and publication. For a listing, refer to the Current Standards Activities page at standardsactivities.csa.ca. This Standard has been formally approved, without modification, by th

28、e Technical Committee and has been approved as a National Standard of Canada by the Standards Council of Canada. 2013 CSA GroupAll rights reserved. No part of this publication may be reproduced in any form whatsoever without the prior permission of thepublisher. ISO/IEC material is reprinted with pe

29、rmission. Where the words “this International Standard” appear in the text, they should be interpreted as “this National Standard of Canada”.Inquiries regarding this National Standard of Canada should be addressed toCSA Group5060 Spectrum Way, Suite 100, Mississauga, Ontario, Canada L4W 5N61-800-463

30、-6727 416-747-4000http:/csa.caTo purchase standards and related publications, visit our Online Store at shop.csa.ca or call toll-free 1-800-463-6727 or 416-747-4044.This Standard is subject to periodic review, and suggestions for its improvement will be referred to the appropriate committee. To subm

31、it a proposal for change, please send the following information to inquiriescsagroup.org and include “Proposal for change” in the subject line:(a) Standard designation (number);(b) relevant clause, table, and/or figure number;(c) wording of the proposed change; and(d) rationale for the change.Refere

32、nce numberISO/IEC 19500-2:2012(E)ISO/IEC 2012INTERNATIONAL STANDARD ISO/IEC19500-2Second edition2012-04-15Information technology Object Management Group Common Object Request Broker Architecture (CORBA) Part 2: Interoperability Technologies de linformation OMG (Object Management Group) CORBA (Common

33、 Object Request Broker Architecture) Partie 2: Interoprabilit ISO/IEC 19500-2:2012(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2012 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including

34、photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org ii ISO/IEC 2

35、012 All rights reservedCAN/CSA-ISO/IEC 19500-2:13ISO/IEC 19500-2:2012(E) ISO/IEC 2012 - All rights reserved iiiTable of ContentsForeword ixIntroduction xi1 Scope . 12 Conformance and Compliance 12.1 Unreliable Multicast 23 Normative References . 23.1 Other Specifications . 34 Terms and definitions .

36、 34.1 Recommendations | International Standards 44.2 Terms Defined in this Part of ISO/IEC 19500. 44.3 Keywords for Requirment statements 55 Symbols (and abbreviated terms) 66 Interoperability Overview . 76.1 General. 76.2 Elements of Interoperability 76.2.1 ORB Interoperability Architecture .76.2.2

37、 Inter-ORB Bridge Support .76.2.3 General Inter-ORB Protocol (GIOP) .86.2.4 Internet Inter-ORB Protocol (IIOP) .86.2.5 Environment-Specific Inter-ORB Protocols (ESIOPs) .96.3 Relationship to Previous Versions of CORBA 96.4 Examples of Interoperability Solutions . 106.4.1 Example 1 .106.4.2 Example 2

38、 .10CAN/CSA-ISO/IEC 19500-2:13ISO/IEC 19500-2:2012(E)iv ISO/IEC 2012 - All rights reserved 6.4.3 Example 3 .106.4.4 Interoperability Compliance 106.5 Motivating Factors 136.5.1 ORB Implementation Diversity 136.5.2 ORB Boundaries .136.5.3 ORBs Vary in Scope, Distance, and Lifetime .136.6 Interoperabi

39、lity Design Goals 146.6.1 Non-Goals .147 ORB Interoperability Architecture . 157.1 Overview. 157.1.1 Domains 157.1.2 Bridging Domains 157.2 ORBs and ORB Services 167.2.1 The Nature of ORB Services 167.2.2 ORB Services and Object Requests .167.2.3 Selection of ORB Services 177.3 Domains 177.3.1 Defin

40、ition of a Domain .187.3.2 Mapping Between Domains: Bridging .197.4 Interoperability Between ORBs. 197.4.1 ORB Services and Domains .197.4.2 ORBs and Domains 207.4.3 Interoperability Approaches 207.4.4 Policy-Mediated Bridging 227.4.5 Configurations of Bridges in Networks 227.5 Object Addressing 237

41、.5.1 Domain-relative Object Referencing .247.5.2 Handling of Referencing Between Domains .247.6 An Information Model for Object References 257.6.1 What Information Do Bridges Need? 257.6.2 Interoperable Object References: IORs 257.6.3 IOR Profiles .267.6.4 Standard IOR Profiles .287.6.5 IOR Componen

42、ts 297.6.6 Standard IOR Components .297.6.7 Profile and Component Composition in IORs .317.6.8 IOR Creation and Scope .327.6.9 Stringified Object References .32CAN/CSA-ISO/IEC 19500-2:13ISO/IEC 19500-2:2012(E) ISO/IEC 2012 - All rights reserved v7.6.10 Object URLs 337.7 Service Context 377.7.1 Stand

43、ard Service Contexts .387.7.2 Service Context Processing Rules 407.8 Coder/Decoder Interfaces 407.8.1 Codec Interface .407.8.2 Codec Factory .427.9 Feature Support and GIOP Versions 437.10 Code Set Conversion . 457.10.1 Character Processing Terminology .457.10.2 Code Set Conversion Framework .487.10

44、.3 Mapping to Generic Character Environments .547.10.4 Example of Generic Environment Mapping .567.10.5 Relevant OSFM Registry Interfaces 568 Building Inter-ORB Bridges 638.1 Introduction. 638.2 In-Line and Request-Level Bridging . 638.2.1 In-line Bridging 648.2.2 Request-level Bridging 648.2.3 Coll

45、ocated ORBs 658.3 Proxy Creation and Management. 668.4 Interface-specific Bridges and Generic Bridges . 668.5 Building Generic Request-Level Bridges 668.6 Bridging Non-Referencing Domains . 678.7 Bootstrapping Bridges 689 General Inter-ORB Protocol . 699.1 Overview. 699.2 Goals of the General Inter-

46、ORB Protocol . 699.3 GIOP Overview. 699.3.1 Common Data Representation (CDR) 709.3.2 GIOP Message Overview .709.3.3 GIOP Message Transfer .719.4 CDR Transfer Syntax . 71CAN/CSA-ISO/IEC 19500-2:13ISO/IEC 19500-2:2012(E)vi ISO/IEC 2012 - All rights reserved 9.4.1 Primitive Types .729.4.2 OMG IDL Const

47、ructed Types 779.4.3 Encapsulation .799.4.4 Value Types 809.4.5 Pseudo-Object Types .879.4.6 Object References 939.4.7 Abstract Interfaces 939.5 GIOP Message Formats. 939.5.1 GIOP Message Header .949.5.2 Request Message .969.5.3 Reply Message .999.5.4 CancelRequest Message 1029.5.5 LocateRequest Mes

48、sage 1039.5.6 LocateReply Message 1049.5.7 CloseConnection Message .1069.5.8 MessageError Message 1069.5.9 Fragment Message .1069.6 GIOP Message Transport. 1079.6.1 Connection Management 1089.6.2 Message Ordering 1099.7 Object Location. 1109.8 Internet Inter-ORB Protocol (IIOP) 1119.8.1 TCP/IP Conne

49、ction Usage 1119.8.2 IIOP IOR Profiles 1129.8.3 IIOP IOR Profile Components .1149.9 Bi-Directional GIOP 1159.9.1 Bi-directional IIOP .1179.10 Bi-directional GIOP policy. 1189.11 OMG IDL. 1189.11.1 GIOP Module .1189.11.2 IIOP Module .1239.11.3 BiDirPolicy Module .12410 Secure Interoperability . 12510.1 Overview. 12510.1.1 Assump