Install a UNIX agent

  1. Run the agent installer. Read and accept the license agreement.

  2. Click New Install and then Agent.

  3. Accept the default installation directory or select a different one.

  4. (Optional) Select Deployment Automation Agent.

  5. Enter the host name and port number of the server that provides auto update install packages.

  6. If you are installing the Deployment Automation agent:

    • Specify the name of the agent.

    • (Optional) Use Mutual Authentication with SSL for the agent to communicate with the Deployment Automation server.

    • (Optional) Connect to an agent relay instead of directly to the Deployment Automation server. Default: no

      Specify the following parameters for the agent relay:

      • Host name or address

      • Communication port

        • HTTP proxy port

    • The host name or address of the Dimensions CM server.

    • The Java Message Service (JMS) communication port.

  7. Enter the OS login name and password for the Dimensions system administrator. Default: dmsys.

  8. Click Install to start the agent installation.

    When the installation is complete, click Finish.

Start agent services as the root user

  1. Log in as user root.

  2. Set up the Dimensions CM pcms_sdp network service. Either locally, or on a NIS server, edit the file /etc/services and add the following to the end of the file:

    pcms_sdp<white-space><port>/tcp<white-space># <comment>

    This entry is required by the Dimensions CM listener.

    <port> default: 671

  3. Perform the following check:

    1. Go to the Dimensions CM dfs directory, for example:

      # cd /opt/opentext/dimensions/<version>/cm/dfs
    2. Open the listener.dat file in a text editor.

    3. Check that the file contains the following entry:

      -agent
    4. If not, add the entry and save the file.

  4. Start the Dimensions listener as follows:

    1. Go to the Dimensions CM prog directory, for example:

      # cd /opt/opentext/dimensions/<version>/cm/prog
    2. Run the following command:
      # ./dmstartup

    Note: The dmstartup script also exports the Dimensions CM environment variables to the user root. It runs the following Bourne shell login script located in the Dimensions CM root directory ($installdir):

    dmprofile
  5. Check the Dimensions CM processes:

    # ps -eaf | grep dm

    You should see the services dmlsnr and dmpool.x.

Start agent services as the administrator user

By default the Agent's listener service is owned by the user root. You can change the listener's owner to the system administrator (by default, dmsys):

  1. Log in as user root.

  2. Set up the Dimensions CM pcms_sdp network service. Either locally, or on a NIS server, edit the file /etc/services and add the following to the end of the file:

    pcms_sdp<white-space>671/tcp<white-space># <comment>

    This is required by the Dimensions CM listener and dmcli.

  3. Give all users permission to use the display:

    # xhost +
  4. Perform the following check:

    1. Go to the Dimensions CM dfs directory, for example:

      # cd /opt/opentext/dimensions/<version>/cm/dfs
    2. Open the listener.dat file in a text editor.

    3. Check that the file contains the following entry:

      -agent
    4. If not, add that entry and save the file.

  5. Log out as user root and log back in as the Dimensions System Administrator (by default user dmsys).

  6. Navigate to: $installdir/dfs

  7. Edit the file listener.dat and add the following:

    -user <DSA_username>
    -restricted_mode

    where <DSA_username> is the system administrator non-root user that is running the listener on the Dimensions agent. Typically this is dmsys.

  8. Start the Dimensions Agent listener as follows:

    1. Go to the Dimensions CM prog directory, for example:

      # cd /opt/opentext/dimensions/<version>/cm/prog
    2. Run the following command:

      # ./dmstartup
  9. Check that the Dimensions CM processes have started:

    # ps -eaf | grep dm

    You should see the services dmlsnr and dmpool.x.

  • When running the agent in restricted mode, area and remote node authentication credentials are not used. In restricted mode, files in a remote area are owned by the user running the dmpool process (by default dmsys), regardless of which user ID is set for the area or specified in Remote Node Authentication.

  • Check that the service specified by the listener.dat -service parameter (by default pcms_sdp) uses a port number of 1025 or higher rather than the default of 671:

    • Delete the local connect pipe, typically

      /tmp/dimensions_local_connect 

      This is recreated when the listener is restarted.

    • Change the ownership and/or permissions on $installdir/prog/dmstartup and $installdir/prog/dmshutdown, so that they are executable by the non-root user specified by the -user flag in $installdir/dfs/listener.dat.

      This new port number must also be used on the server node.