OSF DCE Administration Guide--Core Components

DCE Application Administration
10.4.3.4 Importing Binding Information from a Profile 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. In the case where a client lacks access
to CDS, it could still communicate with the server if you supplied the client with a valid
binding.
You can use an rpcprofile import operation to return a server’s binding information.
You must specify an interface by using the -interface option as shown in the following
example:
dcecp> rpcprofile import /.:/subsys/applications/wards_profile \
-interface {458ffcbe-98c1-11cd-88bc-0000c08adf56 1.0}
{ncacn_ip_tcp 130.105.1.202}
{ncacn_ip_tcp 130.105.1.227}
You can use other options such as -version and -object to further specify a binding. Use
the -max option to limit the number of bindings returned, as shown in the following
example:
dcecp> rpcprofile import /.:/subsys/applications/wards_profile \
-interface {458ffcbe-98c1-11cd-88bc-0000c08adf56 1.0} \
-max 1
{ncacn_ip_tcp 130.105.1.202}
10.4.3.5 Removing Members from a Profile Entry in CDS
Over time, organizational changes can require you to redeploy servers in your DCE cell.
You might, for instance, want to move server entries from one profile entry into another.
Use an rpcprofile remove operation to remove one or more members from a profile. In
the following example, the rpcprofile remove operation removes member
/.:/subsys/applications/admin_bbs_servers from the profile
/.:/subsys/applications/wards_profile:
dcecp> rpcprofile remove /.:/subsys/applications/wards_profile \
-member /.:/subsys/applications/admin_bbs_servers \
-interface {458ffcbe-98c1-11cd-88bc-0000c08adf56 1.0}
10.4.3.6 Deleting a Profile Entry from CDS
124243 Tandem Computers Incorporated 10− 33