OSF DCE Administration Guide--Core Components

DCE Application Administration
-object {76030c42-98d5-11cd-88bc-0000c08adf56}
10.4.1.4 Importing Binding Information from a Server Entry in CDS
Application client programs can automatically import server binding information from
CDS and use it in their quest to find and communicate with a server. But occasionally,
an administrator might want to import a binding. For instance, a client might lack access
to CDS but it could still communicate with the server if you supplied it with a valid
binding.
Use an rpcentry import operation to return a server’s binding information, as follows:
dcecp> rpcentry import /.:/subsys/applications/bbs_server \
-interface {458ffcbe-98c1-11cd-bd93-0000c08adf56 1.0}
{ncacn_ip_tcp 130.105.1.227}
10.4.1.5 Viewing Information in a Server Entry
When clients are having difficulty communicating with servers, you might want to see
what binding information is contained in a server entry as a troubleshooting step. Or say
you are adding object UUIDs to server entries and you wonder whether a server entry has
been overlooked. You can use an rpcentry show operation to view the information in a
server entry as illustrated in the following example. The returned information includes
the interface identifier, two bindings over which the server can be reached, and an object
UUID of a resource maintained by the server.
dcecp> rpcentry show /.:/subsys/applications/bbs_server
{458ffcbe-98c1-11cd-bd93-0000c08adf56 1.0
{ncadg_ip_udp 130.105.1.227}
{ncacn_ip_tcp 130.105.1.227}}
{76030c42-98d5-11cd-88bc-0000c08adf56}
10.4.1.6 Removing Binding Information from a Server Entry in CDS
Occasionally, you might want to remove binding information from a server entry. If a
server host crashes, its servers cannot remove their server entries from CDS. To prevent
clients from trying to communicate with these phantom servers, you should unexport the
bindings from CDS manually. Unlike the endpoint delete operation, this operation does
not remove the entry name from CDS.
124243 Tandem Computers Incorporated 10− 23