/
Install ServiceOptimizer Installing a Server Installing the Processes

Install ServiceOptimizer Installing a Server Installing the Processes

To Start with...

If this is an upgrade...

If there is a previous installation then it is recommended that any initialisation files (e.g. the ServiceOptimizer users .profile, UNIX shell scripts, Windows batch files, Perl scripts, any database exports/backups stored underneath the ServiceOptimizer base directory) are copied to a safe place, prior to installing the server.

(warning) In particular, be sure to back up any SSL certificate files in the server\bin\test directory, and make a note to put these files back again once the new version of ServiceOptimizer has been installed.

The ServiceOptimizer Base directory should be appropriately named e.g. /servicepower/spowner/<vno> this then allows future releases to be installed in a different directory. For the purposes of illustration, the instructions below assume this directory structure. If a different structure is used, account must be taken of this.


...now do the actual install...

UNIX

Perform the following steps (in the order given)...
  1. Login as root.
  2. Insert the ServiceOptimizer DVD.
  3. Create a new base directory e.g. /servicepower/spowner/<vno>, and copy the .gz file(s) to the base directory

    mkdir <vno>
    cd <vno>
    cp <cdrom>/server/<gzfilename>
  4. Unzip the gzipped file(s) using the appropriate command e.g.

    gunzip <gzfilename>

    Before going to the next step, please note

    The setting of ‘umask’ will affect the file permissions that the unpacked files will have. The suggested value is 0 (zero), which will effectively cause ‘umask’ to have no effect on file permissions.

  5. Untar the resultant .tar file(s) using the appropriate command e.g.

    tar -xvpf <tarfilename>

    Check the results

    Check that the .tar file(s) unpacked correctly by examining the directories and files created.  These should match the directories and files specified in the Contents List.

    Ensure any running system is closed down

    Before continuing ensure all ServiceOptimizer processes have been stopped (e.g. enter the command: ps -ef | grep spuser to check this.)

  6. Optionally copy the client directories (/client and /doc) and their contents to the server for convenience.

     

  7. Give ownership and appropriate permissions to the spowner user, for all directories beneath and including /servicepower/spowner, for instance:

    cd /servicepower/<spowner>/<vno>
    chmod -R 755 *
  8. Log in to the UNIX server as the ServiceScheduling user spuser. If it does not already exist, create the sphome directory, cd to the sphome directory, and (if necessary) remove and recreate the symbolic links to the base directory with the command:

    ln -s /servicepower/<spowner>/<vno>/* 

 

 

WINDOWS

Perform the following steps (in the order given)...
  1. Login as administrator on the Server machine.
  2. Insert the ServiceScheduling CD-ROM.
  3. Run server\server_install.exe from the CD and follow the instructions given.
  4. Set up the environment variables for the Windows Service as described in the ServiceOptimizer Admin Guide.

 

...and finally

...if this was an upgrade...

Any directories and files you copied to a safe place can now be copied back into their original positions where appropriate