Exporting Binding Information to a Server Entry in CDS
Servers usually export their own binding information to CDS when they initialize or when they are configured after installation. But sometimes, binding information may have been removed for some reason or by accident and you want to restore it. Or another transport has been added and you want to export the binding for the new transport.
You can manually export server binding information to a server entry using an rpcentry export operation. If the entry does not already exist, the rpcentry export operation creates it provided the directory already exists and you have the necessary permissions.
The following example illustrates exporting a server's binding information to a server entry named /.:/subsys/applications/bbs_server. The object UUID identifies the data file resource used by the bbs_server.
dcecp> rpcentry export /.:/subsys/applications/bbs_server \
>-interface {458ffcbe-98c1-11cd-bd93-0000c08adf56 1.0} \
>-binding {ncacn_ip_tcp 130.105.1.227} \
>-object {76030c42-98d5-11cd-88bc-0000c08adf56}
dcecp>