Specify binding type settings

Use this panel to select the type of name space binding that you want.

To view this administrative console panel, click Environment > Naming > Name Space Bindings > New.

You can configure a name space binding for any of the following objects:

On this panel, select a binding type and then click Next.

Binding type

Specifies the type of binding configured.

String Select String to configure a name space binding for a string constant value.

To configure a String binding, you need the following information:

  • The string constant value
  • The target root context for the configured binding (scope)
  • The name of the configured binding, relative to the target root context

If variable substitution is enabled, you can create a file that maps multiple variable names to values and specify the file name for the String value. By default, a name server does not perform variable substitution on the string value of a String name space binding. Thus, by default, the com.ibm.websphere.naming.expandStringBindings property is set to false and a name server does not expand the value of String bindings.

Tip: To enable variable substitution on the String value, create a custom property with Name set to com.ibm.websphere.naming.expandStringBindings and Value set to true. You can define a custom property at the cell, node, server, or name server scope. Create the custom property on a console page for the appropriate scope:
Cell scope
Click System administration > Cell > Custom Properties > New.
Node scope
Click System administration > Nodes > node_name > Custom Properties > New.
Server scope
Click Application servers > server_name > Administration > Custom Properties > New.
Name server scope
Click Application servers > server_name > Administration > Server Components > Name Server > Custom Properties > New.
All name servers within the specified custom property scope apply the setting. Settings at a narrower scope override settings at a wider scope. For example, on multiple-server products, settings at the node scope override settings at the cell scope. Select a custom property scope that is at least as wide as the name space binding scope. Thus, to expand a variable reference in a cell-scoped String name space binding, define the custom property at the cell scope. If the custom property has a scope narrower than the name space binding, only name servers within the scope expand the variable reference in the String name space binding. Name servers outside of the scope do not expand the variable reference and handle the reference differently.
EJB Select EJB to configure a name space binding for an EJB home installed on a server in the cell. Use a cell-scoped EJB binding to create a fixed qualified lookup name for an enterprise bean. A fixed qualified lookup name is not dependent on the cell topology.

To configure an EJB home binding, you need the following information:

  • The JNDI name of the EJB server or server cluster where the enterprise bean is deployed
  • The target root context for the configured binding (scope)
  • The name of the configured binding, relative to the target root context

On standalone servers, do not configure an EJB binding that resolves to another server. The name server cannot read configuration data for other servers. That data is required to construct the binding.

CORBA Select CORBA to configure a name space binding for a Common Object Request Broker: Architecture and Specification (CORBA) object available from a Object Management Group (OMG) Interoperable Naming (CosNaming) name server. Identify a CORBA object bound into an INS compliant CosNaming server with a corbaname URL. The referenced object does not have to be available until the binding is actually referenced by an application.

To configure a CORBA binding, you need the following information:

  • The corbaname URL of the CORBA object
  • An indicator if the bound object is a context or leaf node object (to set the correct CORBA binding type of context or object)
  • The target root context for the configured binding
  • The name of the configured binding, relative to the target root context
Indirect Select Indirect to configure a name space binding for an object bound in a WebSphere Application Server name space that is accessible using a Java Naming and Directory Interface (JNDI) indirect lookup. You can select Indirect for CORBA objects as well as for javax.naming.Referenceable, javax.naming.Reference, and java.io.Serializable objects.

The target object itself is not bound to the name space. Only the information required to look up the object is bound. Therefore, the referenced name server does not have to be running until the binding is actually referenced by some application.

To configure an indirect JNDI lookup binding, you need the following information:

  • The JNDI provider URL of the name server where the object resides
  • The JNDI lookup name of the object
  • The target root context for the configured binding (scope)
  • The name of the configured binding, relative to the target root context

The following information is optional:

  • The JNDI initial context factory class name. The default is the WebSphere Application Server initial context factory, com.ibm.websphere.naming.WsnInitialContextFactory.
  • Additional properties to pass to the javax.naming.InitialContext constructor.

A cell-scoped indirect binding is useful when creating a fixed qualified lookup name for a bound object so that the qualified lookup name is not dependent on the cell topology.




Related tasks
Configuring name space bindings
Related reference
Name space binding collection
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 8:21:57 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-express-iseries&topic=unam_rbinding_type
File name: unam_rbinding_type.html