Name bindings are initially defined in Ant configuration files. When the Ant files are run, the bindings are copied into component and package property files, which are distributed during cluster synchronization. EAServer loads name bindings into memory when a deployed module is started or refreshed.
Initially, the Ant configuration files contain settings read from the EJB-JAR deployment descriptor. You can customize properties, such as bindings, in a user-configuration file for an EJB module or Web application. For example, you can bind a name to a data source, and you can bind a data source to all the resource references in a package. See “Commonly configured properties” in Chapter 2, “Deploying and Configuring EJB Components,” in the EAServer Enterprise JavaBeans User’s Guide.
For details on working with Ant configuration files, see Chapter 2, “Ant-Based Configuration,” in the EAServer Automated Configuration Guide.
Viewing a server’s name bindings
Expand the Servers folder, and select the server.
Highlight the Name Bindings icon. The window in the right pane displays:
Bind Name – the name you can use to access an object.
Bind Object – the object to which the bind name refers.
Scope – the scope (client, cluster, server, package, or component) in which the name binding is valid.
Status – the status of the name binding; active or inactive.
