A typical distributed ServiceOptimizer instance requires ServiceOptimizer to be installed on every node (computer) that is configured in Database sp416_host_machines. Each ServiceOptimizer installation should be of the same ServiceScheduling version and each must be installed following the instructions in the Install Guide. Small differences in version (bug maintenance version differences) are however allowed. How the update can be carried out incrementally, one distributed host at a time is described in Maintenance.
Every service or startup script (Admin ServiceOptimizer Further Detail Scripts and Utilities) should be configured to start System Monitor using the same command line parameters: the System Monitor determines whether it’s running as a Master System Monitor or as a Slave System Monitor from the database (Example Configurations).
| Tip |
|---|
| title | Shared Code Resources |
|---|
|
It is possible to configure a distributed ServiceOptimizer instance so that one or more of the nodes runs from the same SPHOME location. It’s even possible to share an SPHOME location between several ServiceOptimizer instances. Such configurations have the advantage of only requiring upgrade in a single location but | Warning |
|---|
| - common locations must be available on a shared filesystem
- the whole ServiceOptimizer instance has to be stopped in the event of an upgrade (see Admin ServiceOptimizer System Configuration Distributed System Maintenance)
- increased network activity may reduce performance
- concurrent access to the centralised location may become a bottleneck.
|
|
| Tip |
|---|
| title | Shared Travel Matrix |
|---|
|
| It is also possible to configure a distributed ServiceOptimizer instance so that one or more FRU Processes share a single Travel Matrix (see Admin ServiceOptimizer System Configuration Travel Matrix). |
