Document toolboxDocument toolbox

14.1 Example Configurations

Owned by Billy Sewell (Unlicensed)
Jan 26, 2024

On This Page:

This page gives detailed examples of a ServiceOptimizer set up.

Non-Distributed System

This section is a guide to getting started with ServiceOptimizer. It describes an example system and gives details of how to configure this system. See schematic diagram Figure 1, opposite: 


A description of the tables and parameters that must be configured is given the page links below. 

The minimum configuration of the example system is given here.

 

 sp400_components

Column

System
Monitor

API
Agent

Gantt
Router

FRU
Process 1

FRU
Process 2

FRU
Process 3

component_no

1

2

3

4

5

6

component_id

'monitor'

'apia'

'grouter'

'fru1'

'fru2'

'fru3'

component_type

1

2

3

4

4

4

parameters

 

 

 

 

 

 

host_machine

 

 

 

 

 

 

fru_no

 

 

 

317

318

319

active

1

1

1

1

1

1

max_restarts

0

3

3

3

3

3

trace_mask_no

1

1

1

1

1

1

max_log_file_size

10

10

10

10

10

10

 sp401_componenet_hierarchy

Column

API Agent / FRU1

Gantt Router / FRU1

API Agent / FRU2

Gantt Router / FRU2

API Agent / FRU3

Gantt Router / FRU3

component_no

2

3

2

3

2

3

is_client_of

4

4

5

5

6

6

 sp406_monitors

Columns

Entry for System Monitor

component_no

1

heartbeat_port

 

heartbeat_address

 

monitor_state

1

pid

 

pci_port

 

pci_address

 

 sp409_component_ports

Column

API Agent 
C API Port

API Agent 
SOAP Port

Gantt Router Port

component_no

2

2

3

port_type

1

3

1

port_no

10021

10022

10028

port_address

 

 

 

listener_count

8

8

8

Figure 1: Example Non-Distributed ServiceOptimizer Instance

 

Distributed System

NOTE: In this example, every computer has been configured identically, with a ServiceOptimizer SPHOME installation and Travel Matrix on every computer – even though for example the Travel Matrix is not used on host poseidon and the API Agent is not run on host artemis. SPHOME and/or Travel Matrix could be on a shared filesystem if required.

The following alterations need to be made to the above settings:

 sp400_components (monitors)

Rename component_id for component_no 1 and add new entries for slave system monitors:

Column

Master System
Monitor

Slave System Monitor #1

Slave System Monitor #2

component_no

1

7

8

component_id

'mastermon'

'slavemon1'

'slavemon2'

component_type

1

1

1

parameters

 

 

 

host_machine

 

 

 

fru_no

 

 

 

active

1

1

1

max_restarts

0

0

0

trace_mask_no

1

1

1

max_log_file_size

10

10

10

 sp406_monitors

Add new entries for slave system monitors:

Columns

Master System Monitor

Slave System Monitor #1

Slave System Monitor #2

component_no

1

7

8

heartbeat_port

 

 

 

heartbeat_address

 

 

 

monitor_state

1

1

1

pid

 

 

 

pci_port

 

 

 

pci_address

 

 

 

 sp416_host_machines

Rename existing single entry for host "poseidon" and add new entries for "heracles" and "artemis".

Columns

Poseidon

Heracles

Artemis

host_machine

'poseidon'

'heracles'

'artemis'

description

 

 

 

monitor_no

1

7

8

archive_location

 

 

 

 sp083_system_parameters

Update the entry for value "mon_controlling_host" to specify which sp416_host_machine entry is the designated master.

Column

 

name

'mon_controlling_host'

value

'poseidon'

 sp400_components (components)

Map the components to the hosts on which they are to run:

Column

API
Agent

Gantt
Router

FRU
Process 1

FRU
Process 2

FRU
Process 3

component_no

2

3

4

5

6

component_id

'apia'

'grouter'

'fru1'

'fru2'

'fru3'

component_type

2

3

4

4

4

parameters

 

 

 

 

 

host_machine

'poseidon'

'poseidon'

'heracles'

'heracles'

'artemis'

fru_no

 

 

317

318

319

active

1

1

1

1

1

max_restarts

3

3

3

3

3

trace_mask_no

1

1

1

1

1

max_log_file_size

10

10

10

10

10

 sp406_monitors
Entries for the system monitors are unchanged:

 

Column

Master Sysmon

Slave Sysmon #1

Slave Sysmon #2

component_no

1

7

8

component_id

'mastermon'

'slavemon1'

'slavemon2'

component_type

1

1

1

parameters

 

 

 

host_machine

 

 

 

fru_no

 

 

 

active

1

1

1

max_restarts

0

0

0

trace_mask_no

1

1

1

max_log_file_size

10

10

10

Figure 2: Example Distributed ServiceOptimizer Instance

.. 

Travel Matrix Configuration