The following is a list of the pre-requisites that must be in place before a ServiceManager installation can commence.
IT Knowledge Prerequisites
ServicePower assumes that any customer deciding to install and manage the application has the required knowledge to support complex IT systems. Specifically, customers must be knowledgeable in the following areas:
- The setup, configuration, management and monitoring of their chosen operating system and database;
- The setup, configuration, management and monitoring of the Java VM;
- The setup, configuration, management and monitoring of the Apache Tomcat Java Application Server;
- 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);
- Server / database clustering;
- Master / slave failover configuration;
- Server and network monitoring; and
Server backup and restoring.
It is not possible to specify hardware requirements within this document as the sizing of the system depends on things such as number of employees being scheduled, the number of jobs being scheduled, the workflow used for those jobs, etc.
ServicePower strongly recommends that you work with our consultancy team to determine the hardware requirements for your specific ServiceManager use case.
However, the following hardware requirements must be met:
Note that ServiceManager is a multi-user, data intensive application. The supplied Java Application Server can use up to 8 Gb of memory.
Note that ServiceManager is a 64-bit application; the operating system must support 64-bit applications.
|Java Runtime Environment|
Note that ServiceManager ships with this version of the JRE.
|Java Application Server|
A headless environment is one that is capable of creating graphical images without the need of physical display hardware. In general, any Java application that creates/manipulates graphical images must be capable of creating these images. For desktop applications this means having the JRE communicate with the underlying display hardware, however for server applications like ServiceManager, access to such hardware is sometimes not possible.
To resolve this issue, Java applications can be made to execute in headless mode. In doing so, they can process graphical images without recourse to the underlying hardware.
By default, when installed, ServiceManager will attempt to configure itself to run in a headless environment. For the standard ServiceManager installation (i.e. ServiceManager being the solely deployed web application within the application server) headless configuration is performed during ServiceManager initialisation.
However, if ServiceManager is to be deployed within an application server running other web applications, it is incumbent on the administrator to ensure that these other applications are not adversely affected.
Connectivity to the ServiceOptimizer's Oracle or MS SQL Server database is required.
In order to interact with the chosen database the appropriate Java (JDBC) database drivers are required - a default set are supplied with ServiceManager.
ServiceManager's functionality is accessed by end users via a web browser.
ServiceManager has been developed to work with the following web browsers:
ServiceManager uses the following client side technologies:
ServiceManager specifies the following font ‘preference path’ within its default Cascading Style Sheet:
Arial, Geneva, Sans-serif. The quality of the layout may be compromised if none of these fonts are available.
ServiceManager does not rely on the use of persistent cookies.