Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

On This Page:

 

9.3.2 All changes from earlier versions of the document are signposted by (plus), or (minus) to reflect whether there is an addition/correction, or a removal of detail.

Introduction

The following sections provide a list of pre-requisites that must be in place before a ServiceOptimizer installation can commence.

It is not possible to specify exact sizing within this document as the sizing of the system heavily depends on things such as number of employees being scheduled, the number of jobs being scheduled, the workflow used for those jobs etc. Thus this specification gives the base levels required and ServicePower strongly recommends that you work with our consultancy team to determine specific sizing.

ServiceOptimizer is supported on a number of different O/S platforms and Database Platforms, so please ensure you read the appropriate sections below for the environment in use. ServicePower may be installed as a distributed instance, hence it may be that a combination of platforms are in use.

Disclaimer of Warranty

ServicePower makes no representations or warranties, either expressed or implied, by or with respect to anything in this document, and shall not be liable for any implied warranties of merchantability or fitness for a particular purpose or for any indirect, special or consequential damages.

Confidentiality and Copyright

This document contains information confidential to ServicePower Technologies plc. This information is patented under European Patent Number 97301142.2-2201 (Appointment booking and scheduling system). The information is supplied by ServicePower Technologies plc on the understanding that it will not be used in any way which is or may be detrimental to the commercial interests of ServicePower Technologies plc. In particular, the contents may not be disclosed in part or in whole to any other party without the prior written consent of ServicePower Technologies plc.

Copyright in this document remains vested in ServicePower Technologies plc and no copies may be made of this document or any part thereof except with the agreement of the company.

Copyright © 2002-2023, ServicePower plc

All rights reserved.

GOVERNMENT RIGHTS LEGEND: Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the applicable ServicePower license agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (Oct 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14, as applicable.

"ServicePower" and ServicePower’s products are trademarks of ServicePower Technologies plc. References to other companies and their products use trademarks owned by the respective companies and are for reference purpose only.

IT Knowledge Prerequisites

ServicePower assumes that any customer deciding to host the ServiceOptimizer solution have the required IT staff and required knowledge to support such a complex system. Specifically, the IT staff must be knowledgeable in the following areas:

  • Chosen operating system/version setup, configuration and monitoring
  • Java VM monitoring
  • Network firewall configuration
  • Network routing
  • Network load balancing
  • SSL certificates and configuration in a Java environment
  • High Availability (HA)
  • Network Attached Storage (NAS)
  • Storage Area Network (SAN)
  • RAID
  • Server / database clustering
  • Master / slave failover configuration
  • Server and network monitoring

  • Server backup and restoring 

 

Server Hardware Requirements

  • ServiceOptimizer is a 64-bit application.
  • Appropriately powerful server(s) must be available with the number of CPUs, and amounts of disk storage and memory that were recommended after the sizing exercise.
  • The server(s) require access to a CD-ROM drive.
  • Consult the documentation supplied with your operating system for sizing information.


 

An appropriate operating system will need to be installed. Supported versions are:

Oracle
SQL Server
Windows Server 2012
Windows 2008 SP1Windows Server 2012
Windows 2008 R2 SP1
Windows 2003 R2 SP2Windows 2008 R2 SP1
SUN – Solaris 10 (SPARC)Windows 2003 Server R2 SP2
HP-UX 11.23 IA64 (Itanium)Windows 2008 SP1

 

 

WINDOWS® Specific Software Requirements

The Windows MSI Installers for the products all require Windows Installer Version 2.0 or higher to be present on the machine on which the product is being installed

The appropriate version of the Microsoft Visual C++ Redistributable Package 2013 must be installed (available free from www.microsoft.com). 

 

UNIX Specific Software Requirements

  • On the SUN – Solaris operating system, the file /etc/system must contain an entry setting the maximum number of semaphores per id to at least 50, for example: set process_max_sem_semns=50
  • On SUN Solaris 10, the operating system must, as a minimum, be at version Solaris 10 06/06 with patch bundle dated 16th Nov 2007 (giving a kernel of 127111-03). 
  • Solaris will need the Sun package SUNWlldap
  • If developing applications on HP using the ServiceScheduling HP API library, then ALL source code must be compiled using the following pre-processing macro: __HPACC_THREAD_SAFE_RB_TREE. This macro is used to make ServiceScheduling HP libraries thread safe. Further information about this macro can be obtained from your ServicePower consultant.

 

ORACLE Server Requirements

Database Server

Oracle 11g (version 11.2.0, or above), or Oracle 12c Release 1, must be installed and at least one Oracle database instance must be available. (Multiple database instances may be desirable to support separate development/test/production environments, or to support multiple ServiceOptimizer instances.)

The Oracle server installation may be on a separate machine if required. If this is the case, note that the Oracle client libraries must be installed on the ServiceOptimizer application server.

Kernel parameters for shared memory must be configured on the database server as per the Oracle Installation Guide.

For disk and memory requirements for the database server, please consult the appropriate Oracle documentation for your chosen version - Oracle Concepts; Oracle Administrator's Guide; and Oracle Backup and Recovery Guide. Oracle configuration for the ServiceOptimizer instance will depend on your particular requirements and you should refer to your ServicePower consultant for advice on this.

As a general guideline however, you should allow for a minimum disk requirement of:

  • Oracle Software: 3,500 Mb
  • Database instance:Total: 7,600 Mb
    • System tablespace: 300 Mb
    • Temporary tablespace: 300 Mb
    • Undo tablespace: 500 Mb
    • Redo logs: 1,500 Mb
    • ServiceScheduling data (one instance): 1,500 Mb

Net

Oracle Net must be installed and configured to enable connections to the database instance. (This is true even if ServiceScheduling is installed on the same server machine as the Oracle database instance.)

Database User

A separate database user must be created for each ServiceOptimizer instance. Each user must be provided with a sufficient quota on one or more tablespaces to allow for the storage of the technician and job data for the ServiceOptimizer instance.

The amount of storage space required will depend on the number of technicians being scheduled and, most importantly, on the number of jobs carried out by each technician. Consideration should also be given to the amount of historical data to be stored. The ServicePower implementation team can provide advice on database storage requirements as part of the ServiceScheduling implementation process.

Database Privileges

Each ServiceScheduling database user will require the following privileges:

  • SELECT privilege on SYS.V_$SESSION

  • ALTER SESSION

  • CREATE PROCEDURE

  • CREATE SEQUENCE

  • CREATE SESSION

  • CREATE SYNONYM

  • CREATE TABLE

  • CREATE TRIGGER

  • CREATE VIEW

Database Initialisation Parameters

ServiceScheduling will run using the default value of all initialisation parameters, with one exception: OPEN_CURSORS should be checked to ensure it is set to a minimum of 300.

The ServicePower schema needs to be set to have the following:

  • The locale of the Database server is assumed to be UK
  • Database instance must have the following settings:
    • NLS_CHARACTERSET is AL32UTF8
    • NLS_LANG is English 

Client Libraries

ServiceOptimizer requires 64bit Oracle client libraries.

Perl

To run the ServiceOptimizer scripts, an installation of Perl will be required (N.B. 64 bit Perl required). The Perl installation must include the relevant DBI and DBD for the appropriate database (DBD::Oracle modules for Oracle, and DBD::ODBC for SQL Server); these may need to be installed separately, in addition to the main Perl installation.

The standard Oracle 11g & 12c installation includes a suitable version of Perl (including the DBI and DBD modules). If your database platform is Oracle 11g or 12c the PATH and PERL5LIB environment variables should be configured to use this version of Perl.

 

SQL Server Requirements

Database Server

Either SQL Server 2008 R2 or SQL Server 2012 must be installed, using mixed mode security. If ServiceOptimizer is running on a separate computer to the SQL Server instance, then both computers should be part of the same Windows Domain.

The computers OS should be configured as set out in Microsoft documentation and no specific modification to the default installation is required.

The SQL Server installation and configuration should also follow the guidelines and recommendations set out in the documentation provided by Microsoft. It should be noted that the default collation Latin1_General_CI_AS or similar case non-specific collation is used.

Database Initial Setup

The initial setup of the database will need to be done by a DBA, i.e. a user with the 'System Administrator' role.

Database Upgrades, and Database Maintenance (e.g. sp_dbtidy)

Users that need to upgrade the database will need to be able to perform schema changes. Such a user should be given at least the 'db_owner' role, and preferably the 'System Administrator' role.

A database tidy facility (called sp_dbtidy) needs to add and remove indexes, so also needs to be run as a user who is a member of the 'db_owner' role.

ServiceScheduling User

It is possible to run ServiceScheduling instances (spsysmon et al, or the ServiceScheduling clients' application server) in either trusted user mode or as a specific SQL Server login. This database user needs as a minimum full access to all tables, stored procedures/functions, and views within the ServiceScheduling database and full access to the TEMP db.

ServiceScheduling Clients Users

Other users who just access the database (such as a user of a ServiceScheduling Client that accesses the database) can be given lower access privileges; but as a minimum this should allow access to all tables, stored procedures/functions and views.

Disk Space

A typical installation would require the following disk space:

  • SQL Server Installation: 600MB
  • Typical ServiceScheduling Database Datafile: 1.0GB
  • Logfile: 1.5GB
  • No labels