Having installed and tested ServiceOptimizer (see the ServiceOptimizer Install Guide) you are now ready to set up your Instance for day to day running.
...
The following must be considered:
Start/Stop Mechanisms
| Panel | ||
|---|---|---|
| ||
|
Presumably some form of automation would be ideal for a production system, but test and development systems may be required to be manually started/stopped to give more immediate control. A number of Admin ServiceOptimizer Further Detail Scripts and Utilities are provided with the installation to help to automate these processes.
...
The instance cannot start without a running database instance, so ensure any Start/Stop automation takes this into account.
Database Instance
| Panel |
|---|
|
In general, for a brand new Instance, the ServicePower consultancy team will have provided an initialized database for use within your business. There may need to be additional Admin ServiceOptimizer System Configuration within the database before the instance is fully configured - this can be done in one of 2 ways:
- Manual updates via SQL (see Admin ServiceOptimizer Further Detail Loading Bulk Data)
- Updates through the ServiceManager application.
...
When a new version of the product is released, there may be further changes required in order to configure new functionality. Any such requirements will be mentioned in the Changes from Previous Issues section of this Guide.
All client Users of the Instance need to be set up in the Database. See New Instance Set UpUser Access for further detail on this.
There must be connectivity available to the database server for all components and appropriate Environment Variables set up.
Include Page Database Connection Database Connection
User Access
| Panel |
|---|
|
All access to ServiceOptimizer, via client applications, or via APIs, is subject to authentication and permission control. This is discussed in detail in Admin ServiceOptimizer Further Detail Access Control. It is important to remember that this control may need to be different for different types of Instance, such as Production-v-Development, so where database instances are being shared it may be necessary to ensure the database tables supporting this process are appropriately managed.
Environment Resources
| Panel |
|---|
|
Admin ServiceOptimizer Further Detail Resources discusses the various environmental resources required by a running ServiceOptimizer Instance. It is important to reassess these requirements regularly and specifically when:
...
| Warning | ||
|---|---|---|
| ||
Ensure there is a System test of a Production equivalent environment, from a resource perspective, prior to putting a new installation into production. |
Configuring your System
| Panel |
|---|
|
ServiceOptimizer consists of a number of Admin ServiceOptimizer Further Detail Core Processes. As seen, in New Instance Set Up Start/Stop Mechanisms above, in the main the system is driven by just the single process spsysmon, however the database needs to be configured for how these other processes are to be run; this is covered in the Admin ServiceOptimizer System Configuration documentation.
Setting up for Business As Usual (BAU)
| Panel |
|---|
|
Once everything is set up and you are ready to start the system for BAU, you need to give some thought as to how the system is to be managed on an on going basis. It is the case that each component of the system must be restarted on a regular basis, and the fru components particularly must be restarted daily. Planned restart of Components covers the reasons why this is necessary, and how it can be achieved.