Network Deployment (Distributed operating systems), v8.0 > Reference > Sets
String binding settings
Use this page to view or configure a string binding. From the console...
Environment > Naming > Name space bindings > string_namespace_binding . The settings on this page are similar to those on the Specify basic properties panel of the New name space binding wizard.
Scope
Shows the scope of the configured binding. This value indicates the configuration location for the namebindings.xml file.
The Scope setting is shown only when you edit an existing binding on the console page, and is not shown when you create a new binding on the wizard panel. This setting is for information purposes and cannot be updated.
If the configured binding is cell-scoped, the starting context is the cell persistent root context. If the configured binding is node-scoped, the starting context is the node persistent root context. If the configured binding is server-scoped, the starting context is the server's server root context.
On multiple-server installations, the configured binding can also be cluster-scoped. For cluster-scoped bindings, the starting context is the server's server root context.
Binding type
Shows the type of binding configured. Possible choices are String, EJB, CORBA, and Indirect. This setting is for information purposes only and cannot be updated.
Binding identifier
Name that uniquely identifies this configured binding.
Name in name space
Name used for this binding in the namespace. This name can be a simple or compound name depending on the portion of the namespace where this binding is configured.
String value
String to be bound into the namespace.
We 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 performs variable substitution on the string value of a String namespace binding. Thus, by default, the com.ibm.websphere.naming.expandStringBindings property is set to true and a name server expands the value of String bindings.
Tip: Variable substitution can result in errors or unexpected changes to a string. For example, with variable substitution, a $$ string is expanded as $. We can disable variable substitution and cause the name server to treat the String value as a literal or constant. Create a custom property with Name set to com.ibm.websphere.naming.expandStringBindings and Value set to false. We 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 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 namespace binding scope. Thus, to prevent variable expansion in a cell-scoped String namespace binding, define the custom property at the cell scope. If the custom property has a scope narrower than the namespace binding, only name servers within the scope prevent variable expansion in the String namespace binding. Name servers outside of the scope expand the variable reference and handle the reference differently.> Administration > Server components > Name server > Custom properties > New .
Configure namespace bindings
Related
Name space binding collection
Specify binding type settings