The MSI installation is a Windows only application. It presents the user with a standard Windows Installation User Interface providing the means for the user to configure the ServiceManager installation to the needs on an individual customer/deployment.
The MSI installation is instigated by running the servicemanager.msi application. This same application is also executed if/when the user wishes to modify any of the system parameters outlined in Install ServiceManager Deploying ServiceManager Server Configuration Parameter Requirements. In general customers using the MSI mode of deployment should never need to manually edit any of ServiceManager's configuration files.
The following section presents the key MSI dialogs presented to the user during installation, their meaning and expected user response.
Installation Process
Microsoft Vista/Windows7/Server 2008 place a number of security restrictions upon its users. As such the deployment / configuration process used to install, update and maintain a ServiceManager installation is different to that required for a standard installation on earlier Microsoft platforms.
In terms of ServiceManager, windows:
- Restricts the user’s ability to install/update files within the
Program Filesdirectory - Restricts the user’s ability to install Tomcat as a service
To resolve the above the user should undertake the installation/configuration (be that via the MSI or ZIP bundles) from a command line prompt that has been started with administrator privileges (see Fig 1. opposite)
Note that whilst the user can invoke the MSI from within Explorer, this mode of operation will not install ServiceManager correctly so must not be used.
More specifically, because of the security restrictions, the installer will fail to update the system Registry and also fail to update the ServiceManager configuration files ( hibernate.cfg.xml and service_manager.properties ).
Installation (Fig 2)
Once an Administrator Command Prompt has been created, the user can now install ServiceManager using either the MSI or the ZIP bundle from that command prompt.
Service Registration (Fig 3)
Once ServiceManager has been installed it needs to be registered as a service. Because of Window’s security restrictions this should be done from an Administrator Command Prompt. See Install ServiceManager Deploying ServiceManager Server Execution Environment, for further details.
The First Execution of ServiceManager
Apart from the first invocation of ServiceManager, ServiceManager should be controlled through the Windows Services application. However the first invocation should take place from within an Administrator Command Prompt. This is because the Windows firewall will attempt to notify the user of a potential threat (ServiceManager’s Tomcat instance attempting to set up its socket instances). If the first invocation is from within the Windows Services application, the user will not see this notification and Tomcat/ServiceManager will fail to start. With the first execution being undertaken from the command prompt, Windows will automatically display this firewall warning and so allow the user to take control of the process.
Installation Process
Destination Folder (see Fig 4.)
The ServiceManager application set can be installed in any location on the target machine. By default this location is a SERVICEManager directory located within:
C:\Program Files(x86)\ServicePower
This location may be overridden. Note that the SERVICEManager directory will be automatically created within the defined location.
Installation Type (see Fig 5.)
The user can choose from a small number of different installation types (Typical, Complete and Custom). It is strongly recommended that the user choose either Typical or Complete. Custom is provided for advanced users wishing to install only specific components of the ServiceManager package.
Service and Application Details (see Fig 6.)
This dialog presents an opportunity to change the name of the web application from the default of SERVICEManager, the configuration of the SOAP connectivity details and the modules directory (see also Install ServiceManager Deploying ServiceManager Server Configuration Parameter Requirements). Note that the SOAP connection endpoint must specify not only the URL but also the port number configured for the SOAP Services in your ServiceScheduling instance database. (see Install ServiceManager Deploying ServiceManager Server Configuration Parameter Requirements)
Database Connection Details (Fig 7.)
ServiceManager may be connected to either an Oracle or a Microsoft SQL Server database. Within this dialog the user specifies the appropriate connection URL and trusted username/password combination.
jdbc:oracle:thin: or jdbc:jtds:sqlserver: ) dependent upon the database type. The user is only required to specify the specific connection string details.
For more information on the format of the database connect strings for Oracle and SQL Server, see Configuration Parameter Requirements
Ready to Install the Application (Fig 8.)
Upon completion of ServiceManager's configuration details the application bundle can be installed. This final dialog presents an opportunity to either completely cancel the installation, or to return to some preceding dialog and update some of the information presented. Pressing the "Next" button here will automatically install ServiceManager.
Fig 4.
| Fig 5.
|
Fig 6. 
| Fig 7. 
|
Reconfiguring ServiceManager Parameters after Installation
From within the MSI application it is possible to modify any/all of the installation parameters specified previously during the installation process.
Systems installed using the MSI application should use the MSI application to modify that system's parameters. Changes entered by any other means could lead to inconsistent behaviour of either ServiceManager or the installation application.
Application Maintenance (see Fig 9.)
When executing the MSI application from a currently installed machine, the MSI is run in application maintenance mode. This provides two basic options, either an uninstallation of the complete application set (select "Remove") or modification of the current installation (select "Modify").
Select the "Modify" option to update the ServiceManager application configuration
Select Features (see Fig 10.)
The Select Features dialog allows modification of which features are installed as part of the ServiceManager application. Modification of these features is not recommended; simply press "Next" to move on to the update ServiceManager parameters option.
Update ServiceManager Parameters
After selecting "Next" from the previous dialog the application presents the user with the "Service and Application Details" and "Database Connection Details" dialogs. These are pre-populated with the installation's current settings and should be modified inline with the details presented in sections Service and Application Details and Database Connection Details respectively.
