11.5 Configured bindings

With the configured bindings feature, you can add objects to the name space using the administrative interfaces. This feature allows an administrator to explicitly add bindings to the cell name space without having to write code. The administrator configures an alias in a persistent name space that refers to a real reference in one of the local name spaces, thus providing an additional level of indirection for names. (The configuration details are covered later in 11.12.1, Name space bindings.)

The functionality is useful in these areas:

As long as it is CORBA 2.3 compliant, supporting INS, the name space of other WAS V6 or V5 cells, WAS V4 administrative domains, third-party appservers and even CORBA servers can be federated into the cell's name space.

The default context of WAS V4 clients is the global, or legacy, context. However, WAS V6 processes bind their objects in local, transient name spaces. Therefore, WAS V4 clients looking up and accessing objects in WAS V6 without requiring changes to the client requires the WAS V6 object to be bound to the legacy name space accessible to the client. Enter configured bindings. An alias can be configured into the legacy name space. When used by the WAS V4 client, the client is transparently redirected to the real object reference in one of the cell's local name spaces.