Previous | Table of Contents | Next |
The following are standard IOR components that can be included in TAG_INTERNET_IOP and TAG_MULTIPLE_COMPONENTS profiles, and
may apply to IIOP, other GIOPs, ESIOPs, or other protocols. An ORB must not drop these components from an existing IOR.
module IOP { const ComponentId TAG_ORB_TYPE = 0; const ComponentId TAG_CODE_SETS = 1; const ComponentId TAG_POLICIES = 2;
const ComponentId TAG_ALTERNATE_IIOP_ADDRESS = 3;
const ComponentId TAG_ASSOCIATION_OPTIONS = 13; const ComponentId TAG_SEC_NAME = 14; const ComponentId TAG_SPKM_1_SEC_MECH
= 15; const ComponentId TAG_SPKM_2_SEC_MECH = 16; const ComponentId TAG_KerberosV5_SEC_MECH = 17; const ComponentId TAG_CSI_ECMA_Secret_SEC_MECH
= 18; const ComponentId TAG_CSI_ECMA_Hybrid_SEC_MECH = 19; const ComponentId TAG_SSL_SEC_TRANS = 20; const ComponentId TAG_CSI_ECMA_Public_SEC_MECH
= 21; const ComponentId TAG_ GENERIC_SEC_MECH = 22; const ComponentId TAG_FIREWALL_TRANS = 23; const ComponentId TAG_SCCP_CONTACT_INFO
= 24; const ComponentId TAG_JAVA_CODEBASE = 25; const ComponentId TAG_TRANSACTION_POLICY = 26; const ComponentId TAG_MESSAGE_ROUTERS
= 30; const ComponentId TAG_OTS_POLICY = 31; const ComponentId TAG_INV_POLICY = 32; const ComponentId TAG_CSI_SEC_MECH_LIST
= 33; const ComponentId TAG_NULL_TAG = 34; const ComponentId TAG_SECIOP_SEC_TRANS = 35; const ComponentId TAG_TLS_SEC_TRANS
= 36; const ComponentId TAG_ACTIVITY_POLICY = 37; const ComponentId TAG_INET_SEC_TRANS = 123; };
The following additional components that can be used by other protocols are specified in the DCE ESIOP chapter of this document
and CORBAServices, Security Service, in the Security Service for DCE ESIOP section:
const ComponentId TAG_COMPLETE_OBJECT_KEY = 5; const ComponentId TAG_ENDPOINT_ID_POSITION = 6; const ComponentId TAG_LOCATION_POLICY
= 12; const ComponentId TAG_DCE_STRING_BINDING = 100; const ComponentId TAG_DCE_BINDING_NAME = 101; const ComponentId TAG_DCE_NO_PIPES
= 102; const ComponentId TAG_DCE_SEC_MECH = 103; // Security Service
13.6.6.1 TAG_ORB_TYPE Component
It is often useful in the real world to be able to identify the particular kind of ORB an object reference is coming from,
to work around problems with that particular ORB, or exploit shared efficiencies.
The TAG_ORB_TYPE component has an associated value of type unsigned long, encoded as a CDR encapsulation, designating an ORB
type ID allocated by the OMG for the ORB type of the originating ORB. Anyone may register any ORB types by submitting a short
(one-paragraph) description of the ORB type to the OMG, and will receive a new ORB type ID in return. A list of ORB type descriptions
and values will be made available on the OMG web server.
The TAG_ORB_TYPE component can appear at most once in any IOR profile. For profiles supporting IIOP 1.1 or greater, it is
optionally present.
13.6.6.2 TAG_ALTERNATE_IIOP_ADDRESS Component
In cases where the same object key is used for more than one internet location, the following standard IOR Component is defined
for support in IIOP version 1.2.
The TAG_ALTERNATE_IIOP_ADDRESS component has an associated value of type
struct {string HostID,unsigned short Port
};
encoded as a CDR encapsulation.
Zero or more instances of the TAG_ALTERNATE_IIOP_ADDRESS component type may be included in a version 1.2 TAG_INTERNET_IOP
Profile. Each of these alternative addresses may be used by the client orb, in addition to the host and port address expressed
in the body of the Profile. In cases where one or more TAG_ALTERNATE_IIOP_ADDRESS components are present in a TAG_INTERNET_IOP
Profile, no order of use is prescribed by Version 1.2 of IIOP.
13.6.6.3 Other Components
The following standard components are specified in various OMG specifications:
• TAG_CODE_SETS - See Section 13.10.2.4, “CodeSet Component of IOR Multi- Component Profile? on page 13-43.
• TAG_POLICIES - See CORBA Messaging - chapter 22.
• TAG_SEC_NAME - See the Security Service specification, Mechanism Tags section.
• TAG_ASSOCIATION_OPTIONS - See the Security Service specification, Tag Association Options section.
• TAG_SSL_SEC_TRANS - See the Security Service specification, Mechanism Tags section.
• TAG_GENERIC_SEC_MECH and all other tags with names in the form TAG_*_SEC_MECH - See the Security Service specification, Mechanism Tags section.
• TAG_FIREWALL_SEC -See the Firewall specification (orbos/98-05-04).
• TAG_SCCP_CONTACT_INFO - See the CORBA/IN Interworking specification (telecom/98-10-03).
• TAG_JAVA_CODEBASE - See the Java to IDL Language Mapping specification (formal/99-07-59), Codebase Transmission section.
• TAG_TRANSACTION_POLICY - See the Object Transaction Service specification (formal/00-06-28).
• TAG_MESSAGE_ROUTERS - See CORBA Messaging (chapter 22).
• TAG_OTS_POLICY - See the Object Transaction Service specification (formal/00-06-28).
• TAG_INV_POLICY - See the Object Transaction Service specification (formal/00-06-28).
• TAG_INET_SEC_TRANS - See the Security Service specification (formal/00-06-25).
• TAG_CSI_SEC_MECH_LIST, TAG_NULL_TAG, TAG_SECIOP_SEC_TRANS, TAG_TLS_SEC_TRANS - See the Secure Interoperability chapter.
• TAG_ACTIVITY_POLICY - See the Additional Structuring Mechanisms for OTS specification (orbos/01-11-08).
• TAG_COMPLETE_OBJECT_KEY (See Section 16.5.4, “Complete Object Key Component? on page 16-19).
• TAG_ENDPOINT_ID_POSITION (See Section 16.5.5, “Endpoint ID Position Component? on page 16-20).
• TAG_LOCATION_POLICY (See Section 16.5.6, “Location Policy Component? on page 16-20).
• TAG_DCE_STRING_BINDING (See Section 16.5.1, “DCE-CIOP String Binding Component? on page 16-17).
• TAG_DCE_BINDING_NAME (See Section 16.5.2, “DCE-CIOP Binding Name Component? on page 16-18).
• TAG_DCE_NO_PIPES (See Section 16.5.3, “DCE-CIOP No Pipes Component? on page 16-19 ).