Verify an installation

Configure an X Window system‌

If you have an X Window system, configure it as follows:

  1. Log in as user root.

  2. Set up the Dimensions CM pcms_sdp network service.

  3. Locally, or on a NIS server, edit the file /etc/services and add the following to the end:

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

    This entry is required by dmcli, the command-line client.

  4. Give all users permission to use the display: 

    # xhost +

    Some UNIX systems do not allow you to directly output X11 programs to your local display. Export the X11 display to another X11 system or run this command:

    $ ssh -X root@localhost

Set up the Dimensions CM environment‌

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

    # cd /opt/opentext/dimensions/<version>/cm

  2. Run the following command:

    • Bourne shell: $ . ./dmprofile

    • C shell: $ source dmlogin

Verify server and agent installations

X Window System

  1. Invoke the Dimensions CM command-line client: dmcli

  2. Enter details in the Dimensions login dialog box. The output should be a Dimensions CM banner and copyright message followed by a Dimensions> prompt.

  3. Enter exit

Command Prompt

  1. Log in as user root.

  2. Give all users permission to use the display: 

    # xhost +

  3. Invoke the Dimensions CM command-line client:

    dmcli -user dmsys -pass <dmsys_passwd> -host 
  <host_name> -dbname <db_name>@<connect_string>

    For example:

    dmcli -user dmsys -pass <dmsys_passwd> 
  -host sun1 -dbname cm_typical@dim14

    The output should be a Dimensions CM banner and copyright message followed by a Dimensions> prompt.

  4. Enter exit.

Check the command-line client

X Window System

  1. Invoke the Dimensions CM command-line client: 

    dmcli

  2. Enter details in the Dimensions login dialog box. The output should be a Dimensions CM banner and copyright message followed by a Dimensions> prompt.

  3. Enter exit.

Command Prompt

  1. Invoke the Dimensions CM command-line client:

    dmcli -user dmsys -pass <dmsys_passwd> -host 
  <host_name> -dbname <db_name>@<connect_string>

    For example:

    dmcli -user dmsys -pass <dmsys_passwd> 
  -host sun1 - dbname cm_typical@dim14

    The output should be a Dimensions CM banner and copyright message followed by a Dimensions> prompt.

  2. Enter exit.

Verify command files‌

Check that the following shell scripts have been successfully installed:

  • Server, agent, client: $installdir / dmlogin

    dmlogin is a C shell script for setting the environment variables required to run Dimensions CM. It resides in the $installdir directory. Invoke this script as part of the .login file of every Dimensions CM user using C shell, for example:

    % source /opt/opentext/dimensions/<version>/cm/dmlogin

  • Server, agent, client: $installdir / dmprofile

    dmprofile is the Bourne shell equivalent of dmlogin. Invoke this script as part of the .profile file of every Dimensions CM user using Bourne shell, for example:

    $ . /opt/opentext/dimensions/<version>/cm/dmprofile

  • Server, agent: $DM_PROG / dmstartup

    Run dmstartup as user root to start the Dimensions listener. This starts a single listener process and many "apps server" processes.

    If you do not want these processes to be automatically invoked, edit dmstartup and comment out the appropriate statements. You may run this as part of your system boot procedure.

  • Server, agent: $DM_PROG / dmshutdown

    Run $DM_PROG as user root to shut down the Dimensions listener. This stops a single listener process and many "apps server" processes.

    If you do not want these processes to be automatically shut down, edit dmshutdown and comment out the appropriate statements. You may run this script as part of the UNIX system shutdown procedure.

  • Server: $DM_PROG / dm_control

    Run dm_control as user root to:

    • Start up, shut down, and restart the database.

    • Start up, shutdown, and restart the Dimensions CM server.

    Enter dm_control to display the syntax or see the Administration Guide.

  • Server: $installdir/../common/tomcat/<tomcat-version>/bin/ startup.sh

    Run startup.sh as user dmsys to start up the Common Tomcat server. You can run this as part of your system boot procedure.

  • Server: $installdir/../common/tomcat/<tomcat-version>/bin/ shutdown.sh

    Run shutdown.sh as user dmsys to shut down the Common Tomcat server. You may run this script as part of the UNIX system shutdown procedure.

Caution: Avoid starting or stopping Common Tomcat as user root. It must be stopped by the user who owns the Dimensions CM files (by default, dmsys).

Ensure OS access to Dimensions files‌

On server, agent, and client systems, the Dimensions CM system administrator OS account (by default dmsys) must belong to the group dmtool. OS accounts for non-administrative users should not be placed in this group. However, user accounts with Dimensions CM ADMIN privileges should be placed in the dmtool group. This ensures that access to the Dimensions $DM_DBASE utilities are restricted to administrative users.

Command-line acceptance tests‌

Run these tests on server, client, and agent systems to verify that the command-line interface is installed correctly. You should be familiar CM commands.

  1. Run dmcli to access the command prompt. See Check the command-line client.

  2. Run the LWS command and verify that a list of projects is returned.

  3. Run the SCWS command and verify that the correct project details are displayed.

  4. Run the LWSD /RECURSIVE command and verify that a list of project directories and items is displayed.

Test client URLs‌

Before you can test the web client and Administration Console URLs, the Common Tomcat process must be running. See Start Tomcat‌.

To launch the web client enter the following URL:

 http(s)://<dimensions_server_host-id>:8080/dimensions/

To launch the Administration Console, enter the following URL: 

http(s)://<dimensions_server_host-id>:8080/adminconsole/