Setting Up the IBM Connect:Direct Server

After you install Connect:Direct® for UNIX, define the parameters needed by the Server for startup. If you installed the Server, the process to customize the Server starts automatically. To customize the server, enter the node to customize.

Procedure

  1. Type the name of the node, up to 16 characters, that you want to customize and press Enter.
    Important: Characters used in Netmap Node Names (or Secure+ Node Names or Secure+ Alias Names) should be restricted to A-Z, a-z, 0-9 and @ # $ . _ - to ensure that the entries can be properly managed by Control Center, Connect:Direct Browser User Interface, or IBM® Sterling Connect:Direct Application Interface for Java™ for Java (AIJ) programs. However, use of ‘@’ characters in a node name is discouraged, as it will cause some clients to display proxy records incorrectly. If the ‘@’ character is at the end of a node name, client display of a proxy record with this node name will fail.
  2. Enter the TCP/IP port number that Control Center Director will use to communicate with Install Agent included with Connect:Direct. Use the default port, 1365, if available. If the default port number is being used by another service, use any other available port.
  3. Type y to start Install Agent after installation or n to avoid starting Install Agent and press Enter. This value is entered into the initialization parameters file in the agent.enable parameter.
  4. Enter the TCP/IP port number that Connect:Direct monitors for requests from remote nodes. Use the default port, 1364, if available. If the default port number is being used by another service, use any other available port. This value is entered into the initialization parameters file in the comm.info parameter.
  5. Type the hostname or IP address that Connect:Direct Monitors for requests from remote nodes.

    If you use 0.0.0.0, Connect:Direct will listen for requests from remote nodes on all network adapters configured on the UNIX server.

    This value is entered into the initialization parameters file in the comm.info parameter.

  6. Type the TCP/IP port number that Connect:Direct monitors for requests from Clients. If available, use the default value of 1363. If the default port number is being used by another service, use any other available port.

    This value is entered into the network map file in the tcp.api parameter.

  7. Type the hostname or IP address that Connect:Direct monitors for requests from Clients.

    This value is entered into the network map file in the tcp.api parameter.

    Connect:Direct creates the network map file and displays the directory path and file name.

    After you define the initialization parameters file, the customization script creates the network map file. A remote node record is added to the network map file. The remote node record is assigned the name of the local node you specified.

  8. Press Enter. The netmap file is automatically created.

Customizing the User Authorization Information File

After the user authorization information file is created, you are ready to customize the file. Use this procedure to map remote user IDs to local user IDs and create remote user information records in the user authorization information file.

About this task

After the user authorization information file is created, the following message is displayed to prompt you to create an authorization information record for a remote user:

Insert remote user record? [Y/n]

Procedure

  1. Press Enter to add a remote user record.
  2. Type the login or ID of the remote user and press Enter.
  3. Type the name of the remote node and press Enter. The submitter ID and remote node name become the record name for the remote user information record.
  4. Type the local user ID where the remote user ID will be mapped and press Enter. The local user ID is the UNIX account name. This value is associated with local.id in the remote user information record and defines the local user ID used to check security for the remote user.
  5. Do one of the following:
    • To create another remote user record, press Enter and repeat steps 2-4.
    • Type n and press Enter if you do not want to create another remote user record.
  6. Do one of the following:
    • If you do not want to create a local user record, type n and press Enter.
    • To create a local user record, press Enter.
  7. Type the user ID for the local user and press Enter. This value is associated with userid in the user authorization information file.
  8. Press Enter to grant administrative authority to the local user ID. All IBM Connect:Direct capabilities that you specify in the local user information record are assigned to the user.

    This value is assigned to admin.auth in the local user information record.

  9. Do one of the following:
    • Press Enter and repeat this procedure to create another local user record.
    • Type n and press Enter to continue to the next task.

Creating an Authentication Key File

A server authentication key file verifies connection requests. Only authorized clients are granted a connection. IBM Connect:Direct generates the server authentication key file automatically. A message is displayed when the authenticaton key file is generated.

Before you begin

Press Enter to continue.