OSF DCE Administration Guide--Core Components

OSF DCE Administration Guide—Core Components

Organization changes or server redeployments can make some proﬁles obsolete. When

you want to remove a proﬁle entry from CDS, use an rpcproﬁle delete operation. The

following example illustrates removing an obsolete proﬁle entry called

/.:/subsys/admin/temporaries/74232_proﬁle from CDS:

dcecp> rpcproﬁle delete /.:/subsys/admin/temporaries/74232_proﬁle

10.5 Client Administration

So far, this chapter has focused on server administration issues. We’ve seen how to

control some server operations, and how to store server binding information in CDS and

in the host endpoint map where clients can ﬁnd it. This section discussses the

administration needs of application clients. Although client administration is very

simple— there are just two related operations—it’s an essential step in getting clients

and servers working together.

We know that CDS is a hierarchical system of directories that stores server binding

information in the form of server entries. We also know that CDS offers group entries

and proﬁle entries as a way to direct clients to appropriate servers. But how do clients

know where to begin looking for a server?

As we discussed earlier in this chapter, servers register interfaces and their bindings in

CDS. Each interface-binding combination is registered under a server entry name.

When a client makes a remote procedure call, it passes a server entry name (or a group or

proﬁle entry name) to CDS along with the UUID of an interface that offers the remote

procedure. CDS uses the server entry name (or group or proﬁle entry name) as a starting

point in the search for a binding that contains an interface UUID and version matching

that passed by the client. This method presumes the client has previously acquired the

server entry name (or group or proﬁle name) used by the server.

Getting clients to use an appropriate server entry name is a 2-step process:

1. Determine what entry name a client should use.

2. Pass the name to the client program.

Note that a client uses whatever name you supply. The client program cannot distinguish

whether the name is a server entry name or group entry name or proﬁle entry name. To

the client, all of these names look and behave the same.

10.5.1 Determining the Entry Name

You need to know the entry name exported by a server so you can provide it to client

programs when you conﬁgure them. Here, we’re just calling this name an entry name,

but it can be a server entry name or group entry name or proﬁle entry name. Your

application documentation should help you decide which kind of entry to use.

10 − 34 Tandem Computers Incorporated 124243