Configuring the Uniface Server

You need to configure the Uniface Server so that it can find the databases and Uniface files, entities, and components that it needs.

The Uniface Server is usually started by the Uniface Router in response to a request from a Uniface client application. There can be settings in assignments files of the Uniface Server, the Uniface Router, and the client application that affect how a Uniface Server is run.

  • Uniface Server assignment file—contains default paths for locating databases, files, and components.
  • Uniface Router assignment file—defines the names and startup options for Uniface Servers. For more information, see Configuring the Uniface Router and Uniface Server Types (UST).
  • Client assignment file—defines the role of a Uniface Server, and whether it is shared or exclusive. The role of the Uniface Server determines the objects it needs.
  1. Create an assignment file for each Uniface Server you plan to use.

    The same assignment file is used by all servers belonging to the same UST. A default assignment file (userver.asn) is provided in the uniface\adm directory of your installation.

    Tip: When specifying a log file, use one of the $PUTMESS_LOG_FILE differentiators to ensure that each server's log file gets a unique name. For more information, see $PUTMESS_LOG_FILE.

  2. In each Uniface Server assignment file, define the default paths for locating databases, files, and components.

    The resources and locations you define depend on the roles this server is expected to fulfill.

    Uniface Server RoleConfiguration RequirementsField Section
    Database server (ANY or blank)Specify the DBMS path, as well as certain database driver settings[PATHS]
    Redirect entities to database table names, if required[ENTITIES]
    File server (FIL)Specify the locations of files.[FILES]
    Application server (SRU)Specify the component locations[RESOURCES]
    Specify the database paths for the data accessed by the components[PATHS]
    Component server (S3C)Specify the shared libraries and DLLs of non-Uniface components.

    You can also specify these when setting the implementation details for a C call-out in the Signature Editor.

    ANYSpecify all of the above, as required by your application.


    For more information, see Paths and Path Assignments.

    For example, specify the DBMS path and database connector, and if necessary, redirect entities to database table names:

    $DATA = DB2: SALES|user|pass
    *.* = $DATA:*.*
  3. Specify the role of the Uniface Server. You can do this in the client assignment file or, if you are starting a server manually, using the /drv switch on the server command line.

    For example:

    ;Path to database server on host
    $DATA = TCP:host|user|password|data + MSS:MyDB:|dbuser|dbpassword
    ;Path to file server on host
    $FILESERVER = TCP:host|user|password|files + FIL:||

    For more information, see /drv.

Related Topics