/dnp

Register a client application or Uniface Server under a symbolic name with a Uniface Router.

/dnp=NetworkConnector: {HostID {+PortNumber} } {:TlsProfile} { |||SymbolicName}

Parameters

  • NetworkConnector—three-letter code for the network connector; one of TCP or TLS. Default is TCP, but it is not always possible to omit this value in path assignments.
  • HostId—host machine where the Uniface Router that handles requests for a server is running. If omitted, the default is localhost ( the current machine). It can be specified as:
    • A Domain Name Server (DNS) entry, such as mycompany.com
    • An Network Information Service (NIS) entry, such as examplehost
    • An IP address, such as 93.184.216.119 (TCP4) or 2606:2800:220:6d:26bf:1447:1097:aa7 (TCP6).

    The format of the IP address, either as specified or as resolved by the DNS or NIS entry, determines the version of the TCP/IP protocol used. For more information, see Host Identification for TCP/IP and TLS.

  • PortNumber—port number on which the server or Uniface Router listens. If omitted, the default depends on the type of server and protocol. For the Uniface Router on TCP, it is 13001.
  • TLSProfile—name of a TLS connection profile that is defined in the [NET_SETTINGS] section of the assignment file; applicable only if NetworkConnector is TLS. For more information, see TLS Connection Profiles.

  • SymbolicName—a logical client ID for the Uniface client, or a UST for the Uniface Server. In combination with the user name, it uniquely identifies the application process. If omitted, use the /ust command line switch to supply the symbolic name.

  • /altnet—this switch can only be specified in a UST definition in the urouter.asn file. For more information, see /altnet.
Note:  The assignment setting $DEFAULT_NET can be used to specify the default value for all the parameters except the SymbolicName. If $DEFAULT_NET is not specified, the parameter default (if there is one) is used.

Use

Use in the userver command lines defined in the [SERVERS] section of the Uniface Router assignment file, or on the command line of a Uniface Server that is started manually.

Description

For a Uniface client application, the only reason to register with the Uniface Router is to be able to receive postmessages. The combination of user name and symbolic name must be unique; otherwise, the registration will fail.

For an automatically-started Uniface Server, the Uniface Router appends this qualifier to the userver command line when it starts the server. The Uniface Server registers with the Uniface Router to let the Uniface Router know that the startup was successful, that it is available to handle client requests, and that it can receive postmessages.

Once an application or Uniface Server is registered under a client ID or UST, it cannot change its registration.

If a Uniface Server is started manually, /dnp and/or /ust must be supplied on the command line. For more information, see Starting Uniface Servers.

It can also be used to register a started server with another remote Uniface Router.

If SymbolicName is specified in both the /dnp command line switch and the $DNP setting, the SymbolicName in /dnp overrides the $DNP setting.

Uniface Server

The following example specifies that TCP port 13002 is the default network path for the Uniface file server on the fringe host. 

userver.exe /dnp=TCP:fringe+13002 /drv=FIL

Example: Client Application

The following example specifies that TCP port 13002 is the default network path for the Uniface client tiger on the mammal host. 

uniface.exe /dnp=TCP:mammal+13002|||tiger myapp.aps

Related Topics