Can COS Naming Service work with the EJB Kodiak Server?
Yes, it has been certified against the Kodiak Server. It can work both as an inprocess as well as an external service. ; Configuring and Administering the Naming Service ; ; NS500-Do I need the Osagent to be running when I start the Naming Service? Currently you still need Osagent to be running in the background before activating the Naming Service. This is needed for bootstrapping purposes. The Naming Server still needs to register with Osagent when it is starting up. This allows the clients to retrieve the initial root context while issuing the resolve_initial_references call. The resolving function works through the Osagent for the retrieval of the required references. Similarly, Naming Servers that participate in a federation also uses the same mechanism for setting up a federation. ; NS501-What is the simplest way to activate the Naming Service? The simplest way to activate the Naming Service is to startup the Naming Service with the following command: nameserv This will activate
Related Questions
- My server/IP phone/device cannot tag Class of Service (CoS) values. Can the Catalyst 2900 XL and 3500 XL series switches tag the traffic from the server/device for a specific CoS value?
- Are the client and server applications aware of the port number (and machine name, if applicable) where the Naming Service is running?
- Can COS Naming Service work with the EJB Kodiak Server?
