CORBA object services

CORBA object services interoperate by delivering context information, with messages, that establish service state and other parameters. Some older Object Request Brokers (ORBs) do not support the passing of this context or use proprietary context data that cannot interoperate with another server.

Conversely, because a service context is not part of the message normally seen at the programmer's level, solutions that involve a break in the normal flow of a message do not automatically propagate a service context. Such solutions include wrapper classes or messages manually propagated across co-existent ORBs. If context propagation is required under such circumstances, it must be explicitly or manually managed in the code. If available, request interceptors provide a useful way to propagate contexts.

Naming service
For CORBA applications, WebSphere Application Server supports the CORBA CosNaming service, which binds CORBA objects to a public name. Clients are "bootstrapped" according to the CORBA programming model. CORBA-compliant Interoperable Object References (IORs) must be obtained and server objects must be bound into the CORBA CosNaming service. (For CORBA client access to enterprise beans, the EJB home must be bound into the CORBA CosNaming service.)

For more information about the naming service, see "CORBA naming service".

Transaction service
WebSphere Application Server supports the CORBA object transaction service (OTS) as defined by the EJB specification. WebSphere Application Server follows the CORBA transaction service specification for propagating transaction contexts and forwards the transaction context to the server. For interoperation with other ORBs, incoming contexts are honored and outgoing transaction contexts are generated, as appropriate.

For more information about the transaction service, see "CORBA transaction service".

Security service
Security Service has been implemented to support C++ client applications accessing protected enterprise beans. To access the protected enterprise beans inside a secure WebSphere domain, a C++ client needs to propagate its identity over a transport protocol (often a secure one) to a server for authentication and authorization check. Successful authentication and authorization allows the client to invoke methods on the protected beans.

For more information about the security service, see "CORBA security service".


Related concepts
CORBA programming model
CORBA naming service
CORBA transaction service
CORBA security service



Searchable topic ID:   ccor_isrvce
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/corba/concepts/ccor_isrvce.html

Library | Support | Terms of Use | Feedback