NAME

DESCRIPTION

The routines described on this reference page are used by servers to register themselves with DCE. This includes registering with the RPC runtime, the local endpoint mapper, and the namespace. Routines are also available to set up DCE security so that servers can receive and invoke authenticated RPCs.

The DCE Server Routines

The server routines are as follows, listed in alphabetical order:

dce_server_disable_service()

Unregisters an individual interface of a DCE server from the RPC runtime, and marks the server's endpoints as disabled in the dced's endpoint mapper service.

dce_server_enable_service()

Registers an individual interface (application service) of a DCE server with the RPC runtime, and marks the server's endpoints as enabled in the dced's endpoint mapper service.

dce_server_inq_attr()

Obtains application-specific attribute data from the dced server configuration data.

dce_server_inq_server()

Obtains the server configuration data dced used to start the server.

dce_server_inq_uuids()

Obtains the UUIDs that dced used in its srvrconf and srvrexec facilities to identify the server's configuration and execution data.

dce_server_register()

Registers a DCE server by establishing a server's binding information, registering its services (represented by interface IDs) with the RPC runtime, and entering its endpoints in the dced's endpoint mapper service.

dce_server_sec_begin()

Prepares a server to receive and generate authenticated RPCs.

dce_server_sec_done()

Releases the resources previously set up by a call to dce_server_sec_begin().

dce_server_unregister()

Unregisters a DCE server by unregistering a servers services (interfaces) from the RPC runtime, and removing the server's endpoints from the dced's endpoint mapper service.

dce_server_use_protseq()

Registers a protocol sequence to use for the server.

Data Types and Structures

dce_server_handle_t

An opaque data structure containing information the runtime uses to establish the server with DCE.

dce_server_register_data_t

A structure that contains an interface handle (generated by IDL), a default EPV, and a count and array of dce_server_type_ts for services that use RPC object types.

dce_server_type_t

A structure containing a manager type UUID and an RPC entry-point vector (EPV) that specified which routines implement the IDL interface for the specific type.

server_t

See: dced_intro(3dce)
for a complete description of server_t.

FILES

dce/dced.h

dce/dced_base.idl

RELATED INFORMATION

Books: OSF DCE Application Development Guide