11.10.4 WAS V4 clientIn WAS V4, there is no need to specify a path to a named object, because all objects are registered in a single global name space. Although convenient, this causes naming conflicts because no two objects can be registered across all appservers with the same names. The use of configured bindings, aliases, in the cell persistent root provides a mechanism by which the V4 naming structure can be mapped to the fully qualified names of V6. This is illustrated in Figure 11-8.
Figure 11-8 WAS V4 client Table 11-10 illustrates the Provider URL settings required. Table 11-10 Lookup settings for WAS V4 client interoperability
CustHome is the name registered in the cell-level persistent root (the legacy root), for cell/nodes/<nodename>/servers/<servername>/CustomerHome. The WAS V4 client accesses the JNDI alias registered in the cell persistent root of the WAS V6 cell. The WAS V6 run time transparently redirects the client to the JNDI entry located in a specific local name space hosted by one of the name servers of the cell. |
