Install ServiceManager Deploying ServiceManager Server Configuration Parameter Requirements

Whether installing via MSI or manually extracting from the Zip, the following configuration details will be required in order to complete the install process and successfully execute Tomcat and the ServiceManager web application.

• Target location of the installation (default C:\Program Files(x86)\ServicePower - ServiceManager is a 32 bit application and hence would not normally be installed into Program Files)
• Desired application name (default SERVICEManager)
• SOAP connectivity parameters (no default provided)
• Database connectivity parameters (no default provided)

If you are manually extracting ServiceManager from the Zip file, refer to Install ServiceManager Deploying ServiceManager Server Manual Installation for details on where these configuration parameters need to be specified; otherwise you will be prompted for them when running the MSI.

Target Install Location

This is the fully qualified path to the directory where the release bundle will be deployed.  By default, within the MSI application, this is C:\Program Files (x86)\ServicePower but this could be any valid directory location.  It should be noted that the actual application bundle will reside within a sub directory of this install location entitled ServiceManager.

Web Application Name

"SERVICEManager" is the default name for the ServiceManager web application.  This name is visible to the client browser, as it is part of the endpoint URL required to connect to ServiceManager.  It is perfectly legal for customers to rename the web application to some other name more appropriate to their environment.  For example if the application was renamed "admin" and the URL of the application server was www.mycompany.com then the URL specified by the client browser would now be: http://www.mycompany.com:8080/admin.

SOAP Connectivity

ServiceManager interacts with the ServiceOptimizer via ServiceScheduling’s SOAP implementation of its API.  In order to achieve this connection, ServiceManager needs two specific pieces of information:

• the endpoint URL of ServiceScheduling's SOAP server
• the database user/schema name to connect to

It should be noted that the endpoint URL must also include the correct port number at the end of the URL, for example (http://spdev:18081).  ServiceScheduling's SOAP port number is defined within the database table database sp409_component_ports.

Database Connectivity

ServiceManager retrieves most of its data from the ServiceScheduling database.  To do this the ServiceManager installation needs to know the following information:

• the database type (Oracle or SQL Server)
• the connection URL
• the trusted user and password credentials

Note that the connection URL differs between Oracle and SQL Server.

Oracle:                  @<host>[:<port_no>]:database

SQL Server:           //<host>:<port_no>;databaseName=<database_name>

ServiceManager Modules Directory

ServiceManager functionality can be enhanced by the subsequent installation of modules.  These modules need to be installed into a location that is known to ServiceManager.  This is known as the modules directory.  For each module the modules directory provides a repository of files and a means of getting files copied across to the correct location in ServiceManager’s deployment directory.

On start-up, ServiceManager will search through its defined modules directory.  The contents of each sub-directory will get copied across to the deployment directory in accordance to the following rules:

• Any files at the top-level of the subdirectory are copied across to WEB-INF/classes.  The exception is that war files do not get copied.
• Any directory, along with its contents, gets copied across to the deployment directory.  This is inhibited when a file called nocopy is encountered within that directory.
• Files are only copied if they are newer in the extension directory than they are in the deployment directory or if the files are not present in the deployment directory.