Chapter 5 Naming Services

Configuring the EAServer naming service

Use the Naming Service tab on the Server Properties window to set a server's naming service options. You can use the Naming Service properties to configure a server to be a name server, or point to another server as its name server.

The Naming Service property sheet includes:

This server's initial context.
Whether or not this server is enabled as a name server.
If this server is not a name server, the URL for the server that is acting as the name server.
Heartbeat detection - periodically verifies that clustered name servers are either accepting client connections or have failed. See "Heartbeat detection" for more information.
If you are using an LDAP server to provide persistent name storage, the URL of the LDAP name server, as well as the manager DN (distinguished name) for the LDAP server and the manager's password.

For complete information about setting Naming Service properties, see "Naming Service".

Name binding password security

You can establish password protection on the naming service to allow name binding only from a designated EAServer installation. This prevents unauthorized applications from creating name bindings using an EAServer name server.

To use the name binding password feature, you must set the com.sybase.jaguar.server.CosNaming.bindpassword property for the name server and each server participating in the naming service. You set this property using the All Properties tab in the Server Properties window. The default value is "jaguar."

All servers participating in the password-protected name service must have the same password as the name server. If the bindpassword property is empty, or does not exist in the property file for a name server, the name server accepts binds from any source.