When multiple servers are involved in your application, the naming service allows you to specify logical server names rather than server addresses. For example, instead of connecting to your finance component server at host badger using port 9000, you can specify the initial naming context for that server, such as USA/MyCompany/FinanceServer. Components are identified by specifying an initial server name context plus the package and component name. For example:
USA/MyCompany/FinanceServer/FinancePackage/PayrollAdmin
This layer of abstraction allows you to move a server to another host without affecting deployed client applications.
Each instance of EAServer operates its own independent name service. In an EAServer cluster, each server in the cluster knows the connection information for all the servers in the cluster. Therefore, an EAServer client can choose one or more cluster members as name servers.
For detailed instructions, see Chapter 5, “Naming Services,” in the EAServer System Administration Guide.
For Java and C++ clients, EAServer provides industry-standard client-side APIs for naming services.
For Java clients, EAServer provides implementations of:
Java Naming and Directory (JNDI) API—see Chapter 3, “Developing EJB Clients,” in the EAServer Enterprise JavaBeans User’s Guide
CORBA standard CosNaming API—see Chapter 8, “Developing CORBA/C++ Components,” in the EAServer CORBA Components Guide
For C++ clients, EAServer provides an implementation of the CORBA standard CosNaming API. See Chapter 9, “Developing CORBA/C++ Clients,” in the EAServer CORBA Components Guide.
PowerBuilder clients use the naming service implicitly. Name resolution is performed automatically when you create EAServer component instances using the CreateInstance and Lookup functions of the Connection object. You can browse the naming service using the CosNaming API, but such complexity is not necessary. See Application Techniques.
