Start UNIX server processes

Check the installation logs‌‌

Check the installation logs for any issues:

/tmp/dminet_Installxxxxx.log
/tmp/dimensons_install/*

Start the RDBMS‌

Verify if your Oracle processes are running:

ps -eaf | grep ora

If you have logged out from or rebooted your system prior to starting the server you must manually restart the Oracle processes.

To restart your Oracle Enterprise services, consult your DBA or vendor documentation.

Start a server as the root user‌

Log in as user root.
To set up the pcms_sdp network service, locally or on a NIS server, edit the file /etc/services and add this to the end of the file:
```
pcms_sdp<white-space><port>/tcp<white-space># <comment>
```
This entry is required by the Dimensions CM app servers (dmappsrv.x) and listener.

<port> default: 671
Start Dimensions CM:
1. Go to the root directory. For example:
```
# cd /opt/opentext/dimensions/<version>/cm
```
2. Give yourself the environment by running the following if C shell:
```
% source /opt/opentext/dimensions/<version>/cm/ dmlogin
```
  or the following if Bourne shell (or a derivative):
```
$ . /opt/opentext/dimensions/<version>/cm/dmprofile
```
3. Go to the Dimensions CM prog directory, for example:
```
# cd /opt/opentext/dimensions/<version>/cm/prog
```
4. Run the following command:
```
# dm_control cm_start
```
Verify that the Dimensions CM processes have started:
```
# ps -eaf | grep dm[pal]
```
You should see services such as dmappsrv.x and dmpool.x.
As a further check, run "getpoolstats":
```
# getpoolstats
```
A message is displayed that a number of dbs processes are running.

Starting a server as the administrator user‌

By default the server's listener service is owned by the user root. However, you can change the listener's owner to the system administrator (by default, dmsys).

Log in as user root.
To set up the 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 entry is required for use by the Dimensions CM "app servers" (dmappsrv.x) and listener.
Log out as user root and log back in as the system administrator (by default dmsys).
Go to:
```
$installdir/dfs
```
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 server (typically dmsys).

Start Dimensions CM:

Go to the root directory, for example:

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

Set up the CM environment:

C shell:

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

Bourne shell (or a derivative):

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

Go to the prog directory, for example:

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

Run the following command:
```
# dm_control cm_start
```

Verify that the processes have started:
```
# ps -eaf | grep dm[pal]
```
You should see services such as dmappsrv.x and dmpool.x.
As a further check, run "getpoolstats":
```
# getpoolstats
```
A message is displayed that a number of dbs processes are running.

Important:

When running a server in restricted mode, area/remote node authentication credentials are not used. Files in a remote area are owned by the user running the dmpool process (by default dmsys), regardless which user ID is set for the area or is specified in Remote Node Authentication.
Verify 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. To do this:
1. Delete the "local connect pipe" (typically /tmp/dimensions_local_connect). Note that it is recreated when the listener is restarted.
2. 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.

Start Tomcat‌

Start the common Tomcat:

$ cd $installdir/../common/tomcat/<tomcat-version>/bin
$ ./startup.sh

To verify that Tomcat is running, check the process list for the tomcat process.