Hitachi

uCosminexus Application Server Expansion Guide


2.5.1 Naming management functionality that you can use on a batch server

The following table describes the naming management functionality that you can use on a batch server. For details on the naming management functionality, see 2. Naming management in the uCosminexus Application Server Common Container Functionality Guide.

Table 2‒16: Naming management functionality

Functionality

Explanation

Binding and lookup of objects to JNDI namespace

Bind and manage objects as name of JNDI namespace. You can perform lookup from batch applications by using bound names. In a batch application, you cannot use lookup in java:comp/env.

Assigning optional name to Enterprise Bean or J2EE resources (user-specified namespace functionality)

You can assign optional name to J2EE resources. You can perform lookup from a batch application with any name set up as an optional name. When connecting to a database from a batch application, make sure to specify optional name to J2EE resources.

For details on J2EE resources, see 2.6 Assigning optional name to Enterprise Bean or J2EE server (user-specified name space functionality) in the uCosminexus Application Server Common Container Functionality Guide. In a batch application, description of Enterprise Bean is not applicable.

Searching the CORBA Naming Service by round-robin policy

You can perform lookup of EJB home object references having the same name (optional name) registered on multiple CORBA Naming Service, in compliance with round robin policy.

Caching by the naming management functionality

You can perform caching of already looked up EJB home object references. You can decrease the time required for processing when you perform lookup of the same object from second time onwards.

Switching CORBA Naming Service

You can switch JNDI namespace to be targeted for lookup by using instance prefix judgment of the InitialContext class.

With the JNDI of naming management functionality, objects (remote objects of RMI-IIOP and objects such as JDBC data source) other than the CORBA object reference are handled as follows: