108
MIDAS 4.12 Installation Guide Worldline Germany GmbH

MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

  • Upload
    others

  • View
    4

  • Download
    0

Embed Size (px)

Citation preview

Page 1: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

MIDAS 4.12Installation Guide

Worldline Germany GmbH

Page 2: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Table of Content1. Information Road Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  1

1.1. Useful Links & Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  2

1.1.1. Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  2

2. Installing MIDAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  3

2.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  3

2.2. MIDAS Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  3

2.2.1. MIDAS Products and Add-Ons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  3

2.2.2. MIDAS Server Tiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  4

2.2.3. Choosing the Right MIDAS Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  5

2.3. Installer Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  6

2.3.1. MIDAS Installer Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  7

2.3.2. Graphical, Silent and Console installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  7

2.3.3. Installer Inventory File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  7

2.4. Technical Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  8

2.4.1. Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  8

2.4.2. Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  8

MIDAS Backend Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  8

MIDAS Web Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  9

2.4.3. Operating System Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  9

2.4.4. Software on User Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  9

2.4.5. Web Browser Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  9

2.4.6. X Server Redirection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  10

2.5. Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  11

2.5.1. HPOM Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  11

2.5.2. Create Local OS User for MIDAS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  11

2.5.3. HPOM Database Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  12

2.6. Installation Steps - Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  13

2.6.1. Installation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  13

2.7. Starting the MIDAS Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  15

2.7.1. Update/Upgrade a previous version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  15

2.7.2. New installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  16

2.8. GUI based Installation of the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  17

2.8.1. License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  18

2.8.2. Context Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  18

2.8.3. Cluster Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  19

2.8.4. Installation Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  19

2.8.5. Update/Upgrade Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  20

2.8.6. Product Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  20

2.8.7. User Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  21

2.8.8. Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  21

2.8.9. Common Port Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  22

2.8.10. Port Settings Derby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  24

2.8.11. HPOM Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  24

Oracle Settings for the Backend Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  24

Page 3: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Oracle Access for the Backend Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  25

2.8.12. Self Monitoring Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  26

2.8.13. Document Paper Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  27

2.8.14. CVS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  27

2.8.15. Configuration of MIDAS Web Application Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  28

2.8.16. Transfer Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  29

2.8.17. Automatic System Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  30

2.8.18. Pre-Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  30

2.8.19. Starting the Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  31

2.8.20. Post-Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  31

Installation Errors and Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  33

2.9. Installation of the Software without a GUI (console-based installer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  33

3. Multiple parallel MIDAS installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  39

3.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  39

3.2. Example Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  39

3.3. Parallel Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  39

3.4. Alternative Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  40

3.5. Installing Parallel MIDAS Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  40

3.6. Configuring the MIDAS Startup Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  40

3.6.1. HPOM 9.x ovcd Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  41

3.6.2. OS init Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  42

3.7. Configuring the MIDAS OS User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  42

3.8. Switching Between MIDAS Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  43

4. Testing and Verifying the MIDAS Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  44

4.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  44

4.2. Accessing the MIDAS Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  44

4.3. Accessing the MIDAS Backend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  45

4.3.1. Full MIDAS Installation on the HPOM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  45

4.3.2. Split MIDAS Web Application and MIDAS Backend Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  46

4.3.3. Registering MIDAS Backend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  47

4.3.4. Backend Coloring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  49

5. Installation Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  50

5.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  50

5.2. Display Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  50

5.2.1. X Server Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  50

Display Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  50

5.2.2. Wrong or Unknown HPOM Passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  52

Testing Passwords of Database Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  52

Updating the Password of the Database User opc_op . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  54

5.2.3. MIDAS GUI - No Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  55

5.2.4. Installation Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  56

6. Installing in a HA Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  57

6.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  57

6.2. Cluster Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  57

6.3. Installation in a High-Availability Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  57

6.3.1. MIDAS Full Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  58

6.3.2. MIDAS Pure Backend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  58

Page 4: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

6.3.3. Other Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  59

6.4. Installation Locations in a High-Availability Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  59

6.4.1. Installing MIDAS on the Active Cluster Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  59

6.4.2. Setup of MIDAS on Inactive Cluster Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  60

6.5. Server Startup and Shutdown in a High-Availability Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  60

6.6. Server Settings in a High-Availability Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  60

7. Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  61

7.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  61

7.2. Downgrading MIDAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  61

7.3. Removing MIDAS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  61

8. Updating or Upgrading MIDAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  65

8.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  65

8.2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  65

8.3. Updating MIDAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  65

8.3.1. Backing up Old Installer Inventory Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  66

8.3.2. Preserving Customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  66

8.3.3. Running the MIDAS 4.12 Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  66

8.4. Upgrading MIDAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  68

8.5. Updating/Upgrading MIDAS in a HA Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  69

9. Post Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  71

9.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  71

9.2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  71

9.3. Installing MIDAS Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  71

9.4. Setting an XML Database Administrator Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  71

9.5. Java Memory Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  73

9.6. Oracle RAC Cluster Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  74

9.7. Disabling the MIDAS Web Application’s HTTP Port (9662) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  75

10. MIDAS Versioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  78

10.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  78

10.2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  78

10.3. Download Locations For CVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  78

10.4. CVS Binary Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  79

10.4.1. Using Standard CVS on HP-UX, Solaris or Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  79

10.5. Configuring MIDAS Versioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  79

10.5.1. Enabling/Disabling VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  79

10.5.2. Alternative CVS Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  80

Using a Non-Standard Local CVS Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  80

Using a Remote CVS Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  80

10.5.3. Time and Date Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  81

10.5.4. Backend Mapping Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  82

All Backend Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  82

Group Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  83

10.5.5. Author Tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  84

11. Using HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  86

11.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  86

11.2. Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  86

11.3. HTTPS Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  87

Page 5: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

12. Using SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  89

12.1. SSH in MIDAS - Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  89

12.2. Common SSH set-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  89

12.2.1. Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  89

12.2.2. Configuring SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  90

Initial Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  90

Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  90

12.3. Embedded SSH Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  90

12.4. External SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  91

12.5. Custom SSH keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  93

13. Using External Authentication Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  94

13.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  94

13.2. Authentication Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  94

13.3. PAM integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  94

13.3.1. Authentication Service: UNIX passwd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  95

13.4. LDAP Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  96

13.4.1. The ldap.properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  97

13.4.2. Using LDAP Mode BIND_WITH_DN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  97

13.4.3. Using LDAP Mode USER_SEARCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  98

Example: OpenLDAP with USER_SEARCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  98

Example: Microsoft ADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  99

13.4.4. Secure LDAP (LDAPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  99

Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  100

Software Included . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  100

Page 6: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

1. Information Road MapIn addition to the online help available in the Web browser during a MIDAS session, the MIDAS Product Familyincludes the following core user information:

MIDAS Installation Guide

Information concerning the installation process and initial setup tasks

MIDAS Administration & Configuration Guide

Information concerning advanced configuration, maintenance or troubleshooting

MIDAS User Guide

Information and instructions to help you use the MIDAS software

MIDAS Release Notes

Information about all the new features included with the current version of the MIDAS software and, in addition,a list of known problems that have been fixed

Information is also available for the following Add-on products that enable you to extend the features andfunctionality of the MIDAS Product Family:

API Toolkit

Extends access to APIs beyond the native HPOM capabilities by supporting various additional programminglanguages.

MIDAS Debugger

Reduces the number of tools and actions required for testing policy changes.

MIDAS Inventory

Enables the rapid identification of new or changed systems to ensure up-to-date infrastructure information.

MIDAS Outage Manager

Simplifies the usage and management of outages with HPOM.

MIDAS Service Builder

Provides an easy-to-use graphical interface for creating new services trees and modifying and exporting existingservice trees.

MIDAS Synchronizer

Provides ready-to-use functionality that enables you to replicate changes across multiple HPOM servers.

boom

Monitors your entire enterprise environment with platform-independent technology.

For more information about which Add-on products are available and the features and functionality they include,see the Worldline Germany Web site in Useful Links & Contact Information.

As a result of regular program updates, some information in the printed manuals may differ from that found in theonline help. For the same reason, there may be minor differences in the presentation of the program’s interface.Most screenshots in this manual have been taken during development and may not reflect final content.

The information in this manual applies to MIDAS for HP OMU, HP OMS and HP OML and anyreference throughout this manual to HPOM includes all three versions. System specificspecialties are highlighted accordingly. For a general overview of the features provided with HPOMU, HP OMS and HP OML, refer to the HP Operations Manager Concepts Guide, which isavailable in PDF format on the HP product manual Web site (see below).

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 1 of 103

Page 7: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

1.1. Useful Links & Contact InformationCheck our home page (downloads section) for the latest version of the MIDAS manuals, whitepapers, documents,and software:

http://www.bes-worldline.com

HPOM patches and documentation can be downloaded from the following Web site:

http://support.openview.hp.com/selfsolve/manualshttp://support.openview.hp.com/patches/patch_index.jsp

1.1.1. Contacting Customer Support

You can contact the support team from Worldline via:

• e-mail: [email protected]

• phone: ( +49 | 0 ) 211-399-415-30Support Times: Mo.-Fr. from 9.00-17.00 CET (except German public holidays)

MIDAS 4.12Installation Guide

2 of 103 © Copyright 2018, Worldline Germany GmbH

Page 8: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

2. Installing MIDASThis chapter describes the installation of MIDAS, guides you through all the installation steps, and shows you how toaccess and verify the installation of MIDAS.

2.1. OverviewBefore you start the installation process, make sure that all installation requirements are met. It is recommended touse the Installation Checklist. In the event of problems during (or after) an installation, for example when launchingthe MIDAS GUI, see Installation Troubleshooting.

Before installing MIDAS, review the following sections:

• MIDAS Architecture

• Installer Technology

• Technical Requirements

• Installation Prerequisites

• Installation Steps - Overview

• Starting the MIDAS Installer

• GUI based Installation of the Software

• Installation of the Software without a GUI (console-based installer)

2.2. MIDAS ArchitectureBefore starting the actual MIDAS installation, consider the different architectural options described in the followingsections.

2.2.1. MIDAS Products and Add-Ons

MIDAS consists of a set of software products and add-ons each representing a certain set of features and functions.The MIDAS installer contains multiple such products/add-ons and the installing user may choose which of them toactually install. Independently from the selected add-ons, always the base product MIDAS Configurator will beinstalled. Currently the following add-ons can be selected during the installation process:

MIDAS Administrator

Provides desired state and package release management for structured and well-defined release processes.

MIDAS Debugger

Assists in developing and debugging HPOM policies.

MIDAS Synchronizer

Two or more MIDAS Backend servers or two MIDAS Web Application servers can be synchronized in almost real-time.

MIDAS Outage Manager

Simplifies the usage and management of outages within HPOM. Application and service owners can create andmanage outages for their applications without major HPOM know-how.

MIDAS Inventory

Integrates the MIDAS Inventory server into the MIDAS Web Application GUI.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 3 of 103

Page 9: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

2.2.2. MIDAS Server Tiers

A Server Tier defines the role of the local MIDAS server system. Currently the following Server Tier roles areavailable:

HPOM Backend Server

The MIDAS Backend Server module has to be installed on the HPOM management server system. It connects tothe HPOM database and the HPOM API.

HPOM Agent Driver

The HPOM Agent Driver module controls a real HPOM Agent for example by replaying test events. This ServerTier is only available with the add-on MIDAS Debugger.

Web Application

This modules transforms internal XML data into HTML to be displayed in the MIDAS GUI. No user data is storedwithin this component.

Web Application Server

This module maintains the MIDAS Web Application functions and data like MIDAS users, user roles, search index,versioning, and so on

With MIDAS 4.x the MIDAS Web Application has been split into two sub-components MIDAS WebApplication and MIDAS Web Application Server. Technically these two sub-components can beinstalled on separate systems. However, this scenario is currently not supported. So, please onlyselect both sub-components together!

Considering these Server Tier roles (ignoring the specific HPOM Agent Driver), MIDAS environments can bestructured as either of the following main scenarios:

• Full installationBoth the MIDAS Web Application and MIDAS Backend on the same host

• Split installationMIDAS Web Application and MIDAS Backend(s) on different hosts

• A combination of both full and split installations, for example, consisting of a full installation with additionalMIDAS Backend(s)

The following diagrams show typical MIDAS installation scenarios. Each diagram shows (next to each server) whichMIDAS Server Tier component has to be installed and where the corresponding add-ons have to be installed.

Full MIDAS Installation on HPOM Server shows scenario (A) representing a full installation. The MIDAS WebApplication component is installed together with the MIDAS Backend component on the HPOM Management Server.The MIDAS add-on administrator could also be installed on the same machine.

Figure 1. Full MIDAS Installation on HPOM Server

Full MIDAS Installation on HPOM server with HPOM Test Agent shows scenario (B) where an additional HPOM testagent system has been added; the additional system will be used for policy debugging with MIDAS Debugger.

MIDAS 4.12Installation Guide

4 of 103 © Copyright 2018, Worldline Germany GmbH

Page 10: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Figure 2. Full MIDAS Installation on HPOM server with HPOM Test Agent

In scenario © illustrated in Split MIDAS installation, the MIDAS Web Application has been installed on a dedicatedmachine. Two HPOM Backend servers exist (representing a split installation) plus one HPOM test agent and a MIDASInventory server.

In this example, MIDAS Synchronizer is used to synchronize the HPOM Backend servers 1 and 2 (controlled by theMIDAS Web Application). This scenario requires that the MIDAS Synchronizer add-on be installed on all threemachines.In addition, in this example the MIDAS Inventory add-on must be installed on the MIDAS Web Applicationintegrating the separate MIDAS Inventory server.

Figure 3. Split MIDAS installation

2.2.3. Choosing the Right MIDAS Architecture

The matrix illustrated in Product and Add-on Selection Matrix shows the possible combinations of Server Tiers andMIDAS add-ons.

• The symbol "+" indicates that the add-on must be installed on all listed Server Tiers.For example, MIDAS Administrator will not be functional if it is not installed on both the MIDAS Web Applicationand the MIDAS Backend server.

• The symbol "-" indicates that the add-on does not allow an installation (see Product and Add-on SelectionMatrix).For example, there is no component belonging to MIDAS Administrator that can be installed on a system actingas HPOM Agent Driver.

Table 1. Product and Add-on Selection Matrix

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 5 of 103

Page 11: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Server Tiers

Server Tier Add-OnProducts

HPOM BackendServer

HPOM Test Agent Webapp/WebappServer

Administrator

+ - + Debugger +

+ + Outage Manager - -

+ Synchronizer - - +

Which installation scenario to choose depends on the set of desired MIDAS products and the following factors:

• The number of MIDAS Backends.This equals the number of HPOM servers.

• Size of the environment in terms of number of MIDAS users, number of managed objects and their size (forexample number of conditions within HPOM policies).The higher these numbers, the more system load can be expected.

• Usage of MIDAS in terms of whether resource-intensive MIDAS features (for example document generation) areto be used.The more often such functions are used, the higher the resulting system load.

• Use pattern of the MIDAS environment - for testing, development of production, with the assumption that in testor development environments the number of users or objects is lower than in production environments.Considering these aspects, the following guidelines apply:

◦ MIDAS full installations are suitable for smaller environments with lower system load (as caused by the usecases described above)

◦ If there are multiple MIDAS Backends (for example, with multiple HPOM servers), controlling all of themthrough the same MIDAS Web Application offers the following significant benefits:

▪ Single central access point to the entire MIDAS environment

▪ Simplified administration of MIDAS users (only once on central MIDAS Web Application)

▪ The use of all MIDAS multi-server functions such as: transfers, compare, search, and so on…

◦ Using a split installation (separated MIDAS Web Application and MIDAS Backend) moves significant systemload from the MIDAS Backend system to the MIDAS Web Application. This may be particularly important forHPOM Backends to minimize the impact of the MIDAS Backend component on the HPOM server.

In addition, various special factors are covered in the following sections, like for example installing MIDAS in HAclusters.

2.3. Installer TechnologyAll MIDAS installers are built using the InstallAnywhere technology and are self-extracting executables. For eachtarget OS platform a dedicated installer program exists - make sure to download and use the installer binarymatching the target platform.Generally there is one common MIDAS installer containing all MIDAS products and Add-ons (see MIDASArchitecture), however in addition there are stand-alone MIDAS products with individual installers that are notcovered in this document. Please see the following website for more details: https://bes-worldline.com/products/midas-product-family/overview/.

To actually install MIDAS, the MIDAS installer must unpack itself and needs a certain amount of temporary diskspace. With the current product version this amount calculates itself as 3 times the size of the installer image plus250MB, which makes up about 2000MB in a temporary location (see Hardware).

MIDAS 4.12Installation Guide

6 of 103 © Copyright 2018, Worldline Germany GmbH

Page 12: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

2.3.1. MIDAS Installer Preview

The MIDAS installer Product Selection screen illustrated in Product Selection presents two blocks matching the twomain dimensions of the MIDAS architecture as described in Choosing the Right MIDAS Architecture. The actualinstaller context is described in more detail in chapter Product Selection on page 38. The two dimensions are:

Server Tiers

Define the role of the local server (MIDAS Web Application system, HPOM server, Agent Driver). For example, ifinstalling MIDAS on the HPOM server, select the HPOM Backend server component. If none of the additional add-ons is selected the base product MIDAS Configurator will be installed.

Server Tiers Add-on Products

Add-ons extend the functionality of MIDAS Configurator.The example (see Product Selection) represents a full MIDAS installation consisting of MIDAS Configurator plusthe Add-on MIDAS Administrator.

2.3.2. Graphical, Silent and Console installation

To keep it simple the name for the installation binary is always install.bin in the followingchapters. Dependent on your platform this stands for Linux64:MIDAS_Cfg_install_4.12.0_linux64.bin, Solaris: MIDAS_Cfg_install_4.12.0_linux64.bin and HPUX:MIDAS_Cfg_install_4.12.0_hpux_ia64.bin

1. To use the default GUI-based MIDAS installer, it must be possible to display its application windows correctly. OnUNIX systems the standard X Window system GUI technology is used, and you must ensure that X applicationscan be displayed properly. For more details about X-redirection, see X Server Redirection. The same rules applyto the MIDAS de-installation program (see Uninstallation).

2. In addition to that the installer can be called with the "console" option:

# ./install.bin -i console

This installation procedure does not require any X application and is explained in more detail in Installation ofthe Software without a GUI (console-based installer).

3. Alternatively, you can perform a non-graphical („silent") installation. However, in this case, you must supply thesilent installer with a prepared input file containing the values that are required by the installer; these valueswould be entered manually in installation dialogs and text boxes during the GUI installation.The input file for the silent installation can be created for you by the MIDAS support team using a speciallyprepared template. The MIDAS silent-installation feature greatly simplifies the installation of multiple MIDASinstances with the added bonus that the input file serves as documentation for the supplied installationparameters.To start the MIDAS silent installation process, use the following command:

# ./install.bin -f <silent_install_properties_file>

For more information about installation methods, contact the MIDAS support team.

2.3.3. Installer Inventory File

The MIDAS installer maintains an inventory file; the inventory file is used to store information about the currentinstallation such as parameters supplied during product installation. The inventory file is namedmidas412.properties and resides in the following location:

UNIX systems

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 7 of 103

Page 13: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

/var/opt/midas/midas412.properties

The inventory properties file is required in particular for product-update (and product-upgrade) scenarios or whenyou want to remove an installed MIDAS product. In addition, the global InstallAnywhere inventory file exists. Thereis normally no need to touch or modify this file:

UNIX systems/var/.com.zerog.registry.xml

Do not manually modify or removed these installer inventory files.

2.4. Technical RequirementsThis section describes the technical requirements for the MIDAS servers on which you install MIDAS. Unlessotherwise indicated, the statements in this section apply to both MIDAS Web Application and MIDAS Backendservers (collectively referred to as MIDAS servers), no matter whether running in a full or split installation (seeMIDAS Architecture). All statements apply independently of whether the target system is a physical computer or avirtual machine.

2.4.1. Hardware

The minimum hardware requirements of a server system for running a MIDAS server are listed below Disk- andMemory Requirements. The amount of RAM listed is not the total amount of memory of the target machine; it is theamount of RAM that must be exclusively available to MIDAS.

Table 2. Disk- and Memory Requirements

Memory MIDAS

Disk 1500MB in target installation directory /opt/midas

Disk ~2000MB temporary disk space in /tmp or some other location (neededtemporarily during the installation of MIDAS only). The temporarydiskspace needed is 4x the size of the installer binary.

RAM 1024MB minimum, Recommendation for the Webapp: 4096MB

The actual demand on system resources depends on the size and scale of the MIDAS environment.

2.4.2. Operating System

MIDAS Backend Servers

The list of hardware platforms, operating systems, and high-availability software supported with the current MIDASrelease is shown in Operating System Support.

Table 3. Operating System Support

Operating System HPOM 9

HP-UX Itanium on HP Integrity 11.31 (11iv3) base_pagesize=4 must be set and cannot bechanged (default setting)! Other settings will not besupported by MIDAS.

Solaris SPARC 10

RHEL Linux 64bit 5.x - 7.3

ServiceGuard for HP-UX 11.20.10 and later

RHEL Cluster Suite 5, 6

MIDAS 4.12Installation Guide

8 of 103 © Copyright 2018, Worldline Germany GmbH

Page 14: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Operating System HPOM 9

Veritas Cluster for HP-UX 5.1 and later

Veritas Cluster for Solaris 5.1 and later

Currently, all HPOM 9.x releases are supported by MIDAS in conjunction with Oracle version 11.x and 12.x assupported by HP for each HPOM release. Since HPOM 9.2x and MIDAS 4.9.0 the Postgres Database is also supported.Generally, Oracle’s Real Application Cluster (RAC) is also supported by MIDAS. To use MIDAS Backends with OracleRAC, some post installation configuration adjustments have to be performed as described in section Oracle RACCluster Support. For a current and up-to-date description of HPOM versions, their supported hardware, softwareand HA cluster versions, review the current {HPOM-support-matrix} (SUMA).

MIDAS Web Application Servers

In addition to the platforms listed in MIDAS Backend Servers, the MIDAS Web Application module can also beinstalled on servers running:

• Linux (64bit)

In a standard set-up the MIDAS versioning functions require that the CVS software is installed on the MIDAS WebApplication server as described in chapter MIDAS Versioning.

2.4.3. Operating System Patches

For MIDAS Backend servers make sure that the system which is intended as installation target meets all hardwareand software requirements of HPOM as described in the HPOM documentation. On all MIDAS servers (MIDAS WebApplication or MIDAS Backend) the latest operating system patches should be present.

On HPOM servers, make sure that the following UTF-8 locale is installed on the target system:en_US.UTF-8

2.4.4. Software on User Workstations

The following software details should be observed regarding the user’s workstation, i.e. from where the MIDASinstallation is initiated or MIDAS will be used eventually.

2.4.5. Web Browser Support

In theory, the MIDAS GUI as a Web application can be used in any standard web browser from the user’sworkstation. However, only the following web browsers have been tested and are supported:

• Mozilla Firefox 45 and higher

• Microsoft Internet Explorer 11

• Google Chrome 54 and higher

Internet Explorer on CITRIX and older browser versions than stated above have technicallimitations and are not supported.

• Newer browser versions may work but have not been tested and are not supported officially.

• Other browser implementations like Opera, Safari have not been tested and are not supported officially.

Cookies must be enabled in the web browser and some MIDAS functions require that pop-up windows are enabled.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 9 of 103

Page 15: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

2.4.6. X Server Redirection

By default, MIDAS installers are GUI-based (see GUI based Installation of the Software). Therefore, during the MIDASinstallation session onto UNIX systems it should be possible to display X-Applications running on the system whereMIDAS is to be installed.

If this is not possible at all, the console mode is now available for fresh installation and also updates and upgrades.Please refer to Graphical, Silent and Console installation for further information.

The prerequisite of displaying the MIDAS installer GUI can be tested quickly by executing any X-Application, forexample:

# xclock

The corresponding window must appear on the workstation of the installing user. If this does not work, theMIDAS installation will fail as well. To set up such X-based access, the following prerequisites must be met:

• An X-Server must be running on the workstation of the installing user

• X-connectivity must be allowed using either of the following methods:

◦ SSHAn SSH connection with X-display tunnel to the system where MIDAS is to be installed exists (using ssh orputty), for example:

# ssh -Y <targetsystem>

When using putty on Windows workstations, enable the appropriate setting in the connection properties (seeDisplay Problems). This method is generally simpler since nothing has to be done with DISPLAY variables andso on.

◦ User logonLog on the the target system using whatever method and export the DISPLAY variable correctly. Possiblyaccess on the workstation of the installing user must be allowed (for example, using the xhost + command).

As of product release the following Windows-based X Servers are supported with the MIDAS installer:

• Xming

• Exceed

• Reflection X

Other X Servers have not been tested and may or may not work properly.For UNIX-based workstations the same rules apply with regards to displaying remote X-Applications. In the event ofproblems related to the graphical installer, refer to Display Problems.MIDAS also supports a non-GUI installation which requires a prepared input file containing all variable values thatwould have been asked by the installer GUI. For details and an example, refer to the product support team.An X-Server on the user‘s workstation is only needed during installation of MIDAS. During runtime all MIDASfunctions run within the web browser and no X-Server will be needed with one exception: MIDAS supports aninteractive installation of HPOM agents. If this feature is desired, the following prerequisites must be fulfilled:

• When logging on to the MIDAS Web Application, specify the DISPLAY variable representing the user‘sworkstation

• The MIDAS Backend server, which eventually performs the HPOM agent installation must be able to perform thefollowing actions:

◦ Launch an xterm console (the needed software packages must be installed on the MIDAS Backend server)

MIDAS 4.12Installation Guide

10 of 103 © Copyright 2018, Worldline Germany GmbH

Page 16: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

◦ Open the DISPLAY specified, which includes all prerequisites like a running X-Server, permissions for remoteX-application, general network connectivity between the MIDAS Backend server and the user workstation

2.5. Installation PrerequisitesThis section explains the checks to be performed to ensure that MIDAS can be installed successfully. Theinformation in this section applies to all types of MIDAS installations.

Before you start the installation process, consider the following important points:

• To install MIDAS on a system that is configured in a high-availability (HA) environment, review chapterInstalling in a HA Cluster before starting the installation.

• Before installing a MIDAS Backend, make sure that the HPOM server processes are up and running on the HPOMManagement server.

• Make sure that X-Applications like the MIDAS installer can open the X-Display.See section X Server Redirection for details.

• To install MIDAS in parallel with other MIDAS instances on the same system, review Chapter Multiple parallelMIDAS installations.

The information in this section covers the following topics:

• HPOM Passwords

• Create Local OS User for MIDAS

• HPOM Database Settings

2.5.1. HPOM Passwords

Before starting to install MIDAS Backend servers, make sure to obtain the following passwords as they will bequeried by the MIDAS installer:

HPOM database user

The MIDAS Backend accesses the HPOM database directly using SQL which in turn requires name and passwordof a database user.The MIDAS installer suggests by default the user name opc_op. Alternatively choose the user opc_report. Anydatabase user with read-only access to the HPOM database objects can be used.Both the opc_op and opc_report users which are created during the HPOM server installation fulfill thisrequirement. The user opc_op even has write capabilities, which are actually not needed for MIDAS.

Make sure that the password of the configured database user is not subject to expiration policies.If the password expires, neither the HPOM processes nor MIDAS will be able to connect to theHPOM database.

If a required password cannot be obtained, see chapter Wrong or Unknown HPOM Passwords forinformation about how to determine, verify or if necessary how to change it.

2.5.2. Create Local OS User for MIDAS

A local operating-system (OS) user named midas is required on both MIDAS Backend and MIDAS Web Applicationservers for version control software CVS and for secure-data transfer using SSH (if enabled). If either of the systems(MIDAS Backend or MIDAS Web Application) is configured in a high-availability environment, the user midas mustbe configured on each physical cluster node where MIDAS may run. The home directory of the OS user midas mustbe set to the MIDAS installation directory. Unless changed during installation, the default this installation directoryis: /opt/midas.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 11 of 103

Page 17: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

MIDAS itself does not require/use a password for the OS user midas. However, the SSH-basedtransfer functions may not work correctly if no password is set. Therefore it is recommended toset a password for the OS user midas.

To add the user midas on a UNIX-based system, please execute the following command:

# useradd -c „MIDAS user" -d /opt/midas midas

The password-expiration option ensures that the account does not require any later maintenance.

If using external user authentication mechanisms like LDAP, NIS or Microsoft ADS, create a useraccount named midas with the correct home directory in that authentication system.

2.5.3. HPOM Database Settings

During MIDAS Backend server installation correct access parameters to the HPOM database must be provided, suchas the (virtual) hostname and port of the database server, database instance name, and so on. Also, check whethersecure Oracle communication is used or not. The MIDAS installer determines the database-related settings from theHPOM configuration, particularly the following two entities:

• The file /etc/opt/OV/share/conf/ovdbconf contains the database access parameters as used by the HPOM Serverprocesses

• The database SQL*Net alias (default value ov_net) used by HPOM that is set as XPL config variable and which canbe displayed using the following command:

# ovconfget -ovrg server opc DATABASE

If the HPOM Server processes run normally, these settings can be assumed to be correct.

To verify the Oracle parameters of the HPOM management server, use the following two commands (make surethat the $ORACLE_HOME environment variable is set correctly). The first command tnsping must be executed onthe HPOM Management Server system:

$ $ORACLE_HOME/bin/tnsping <SQL*Net alias>

For example:

MIDAS 4.12Installation Guide

12 of 103 © Copyright 2018, Worldline Germany GmbH

Page 18: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

$ tnsping ov_net[...](DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=lanzarote.bes-intern.com))(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.123.123)(PORT=1521)))On the Oracle database server itself (which may be a different system than the HPOM management serverin case of a remote database), the command lsnrctl status should produce an output like in thefollowing example:bash-3.1# $ORACLE_HOME/bin/lsnrctl statusAlias LISTENERVersion TNSLSNR for HPUX: Version 11.1.0.7.0 - ProductionStart Date 17-APR-2009 20:36:26Uptime 9 days 2 hr. 17 min. 32 secTrace Level offSecurity ON: Local OS AuthenticationSNMP OFFListener Parameter File /opt/oracle/product/11.1.0.6/network/admin/listener.oraListener Log File /opt/oracle/diag/tnslsnr/lanzarote/listener/alert/log.xmlListening Endpoints Summary...(DESCRIPTION=(ADDRESS=(PROTOCO=ipc)(KEY=openview)))(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=lanzarote.bes-intern.com)(PORT=1521)))

2.6. Installation Steps - OverviewThe MIDAS installation comprises the following high-level steps, which are explained in detail in the subsequentsections:

1. Login as administrative user (root on Unix systems) and mount the product media or copy the installer image tothe target system. Have enough temporary disk space available for unpacking the installation software (seeInstallation Prerequisites).

2. If installing MIDAS on a remote system, make sure that X-Applications can be displayed correctly (see X ServerRedirection) or use the console installer (Installation of the Software without a GUI (console-based installer))

3. If the default temporary directory does not provide sufficient space, determine a temporary directory to whichthe installer can be extracted (see Technical Requirements).

4. Start the MIDAS installer program that matches the operating system on the target system.

5. Supply parameters queried by the MIDAS installer (as preparation, see Installation Checklist)

6. Review the preinstallation summary of port numbers, server names, disk space and so on

7. Initiate the automatic installation of the MIDAS software.The MIDAS installer will attempt to determine most parameters by itself and, in most cases, it should besufficient to confirm the provided default values. However, please review the parameters to make sure that theyare correct.

The configuration parameters queried by the installer are the basis for the initial MIDASenvironment. All parameters can be modified at any time after a completed MIDAS installation.

2.6.1. Installation Checklist

The following installation checklist can be used both as a preparation to collect required information before actuallystart the MIDAS installation as well as an installation protocol. If multiple MIDAS servers are to be installed, obtainthe required information for each MIDAS server.

• HA Cluster: Is HPOM and/or Oracle running in a HA cluster ( ) YES ( ) NO

• Installation Directory (min. 1500mb needed):HA Cluster: Installation directory must reside on a shared file system which is part of the same HARG as the

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 13 of 103

Page 19: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

MIDAS software.

• Older versions of MIDAS will be detected. The installer will offer to update this version (old data will beimported) or to install a new version in parallel without importing any old data.

• Product Selection (Note: if no add-ons are selected, MIDAS Configurator will be installed)Server Tiers are the MIDAS core components defining the role of this MIDAS server. Depending on the server upto four components can be installed (see also Product and Add-on Selection Matrix):

◦ HPOM Backend Server (requires a HPOM server; will connect to HPOM)

◦ HPOM Agent Driver is part of the MIDAS Debugger product (Do NOT install this on the HPOM managementserver); requires MIDAS Debugger add-on.

◦ MIDAS Web Application system (unless advised by support DO NOT install the MIDAS Web Application andMIDAS Web Application Server on different systems!)

• User Check:Make sure the OS user midas exists on the system. The home directory of that user must match the MIDASinstallation directory.HA Cluster: User midas must exist on all physical machines.

• Server Settings:Server Hostname:(FQDN recommended. HA Cluster: Use virtual hostname of HARG hosting the MIDAS server!)Local Server Identifier:Example: <hostname>_server, or generic name "production_server"Server Description (optional):Password (to protect port 9661):

• Port Settings:Server port (MIDAS Webapp connects to a MIDAS Backend by default via port 9661):JMX port (default 9660 - used locally only):JMS port (default 9665 - used locally only):[ ] Use HTTPS (on server port 9661):This requires a separate certificate exchange between a separate MIDAS Webapps and MIDAS Backend(s)!

• Port Settings Derby (for the embedded audit database):Derby port (default 9664):

• Oracle for HPOM Settings (MIDAS Backend only)Suggested values are read from the HPOM configuration. Review all settings. Caution: Especially review if aremote Oracle (e.g. HA clustered) database is used.Oracle home path:Oracle hostname:HA Cluster: Use virtual hostname of Oracle (remote) database.Oracle listener port (default 1521):[ ] Secure Oracle connection.

• Oracle for HPOM Access Settings (MIDAS Backend only)Oracle DB name (default ov_net):OpenView DB instance name (default openview):Specify an Oracle user and password. (Tip: use opc_op or opc_report. Read-only access is required.)Oracle DB username (default opc_op):Oracle DB password:

• HPOM user opc_adm password (required for HPOM 8.29 and below, MIDAS Backend only):

• Self Monitoring Settings (MIDAS Backend servers only, if MIDAS Web Application has not been selected):Web Application Host:Web Application HTTP Port:

• Document Paper Format (MIDAS Web Application only):[ ] A4 or

MIDAS 4.12Installation Guide

14 of 103 © Copyright 2018, Worldline Germany GmbH

Page 20: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

[ ] US Legal

• CVS Settings (for version control, MIDAS Web Application only):[ ] Enable CVS FeatureCVS Binary:Repository path:

• Web Application Server Settings (MIDAS Web Application only)Web application ports to which the user will connect with his web browser:HTTP (default 9662):HTTPS (default 9663):

• FTP/SSH Transfer Method:[ ] Enable FTP for file transferFTP Port (default 10021):FTP Data Port (default 10020):[ ] Enable SCP for file transferSSH Port (default 10022):SSH Command Port (default 10023):

• Automatic System Startup:[ ] Start as ovc managed process (ovcd - HPOM 9.x only)[ ] Start on system startup (OS system boot integration)[ ] Start manually

• Pre-Installation summaryShows a summary of the parameters set. After that the actual MIDAS installation will start. After the MIDASinstallation has completed an installation summary will be shown.

2.7. Starting the MIDAS InstallerThe installation of the MIDAS software has to be performed as administrative user (on UNIX-Systems as user root,the installer checks whether root privileges are available). Remember to verify the installation prerequisites,particularly regarding disk space (see Hardware) and X-Server (see X Server Redirection).

To start the installer just run

• GUI based MIDAS installer:

# ./install.bin

• Console installer:

# ./install.bin -i console

• Silent installer:

# ./install.bin -f <silent_install_properties_file>

2.7.1. Update/Upgrade a previous version

If an older version of MIDAS is already installed on the target system, observe the following point:

• The MIDAS 4.11 installer allows to update an existing older version of MIDAS.To import existing data from the older version, do not stop the existing MIDAS server. See Updating or UpgradingMIDAS.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 15 of 103

Page 21: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

2.7.2. New installation

On target systems where MIDAS < 4.11 is already installed or no migration of the existing data is desired, theprocesses of the older version has to be stopped first. There must be no processes such as wrapper or java running,that belong to the older MIDAS version. Verify this by executing the following command:

# ps -ef | grep -i midas

If there are still MIDAS processes running, the command output looks like the following example:

root 3343 1 0 Aug11 ? 00:12:32 /opt/midas/jre/bin/java -classpath/opt/midas/conf:/opt/midas/lib/classworlds-1.0.1.jar -Xms64m -Xmx512m -server -DbesId=midas412_server-Dmidas.instance=. -Dclassworlds.conf=/opt/midas/conf/servicemix/servicemix.conf-Dservicemix.home=/opt/midas -Djava.endorsed.dirs=/opt/midas/lib/endorsed -Dexist.home=/opt/midas-Dartifactory.home=/opt/midas -Djavacvs.multiple_commands_warning=false -DEnv-CVS_EXE=[cvspath]-Dorg.mortbay.jetty.Request.maxFormContentSize=10000000-Dorg.apache.cocoon.settings=/opt/midas/conf/cocoon.properties -Dcom.bes.servicemix.shutdown.timeout=500-Dsun.net.inetaddr.ttl=0 -Djava.util.logging.manager=com.bes.itm.util.JCLLogManager-XX:+PrintCommandLineFlags -Djava.net.preferIPv4Stack=false -Dnet.sf.ehcache.skipUpdateCheck=true-Dorg.terracotta.quartz.skipUpdateCheck=true -Dom.home=/opt/OV -Djava.security.egd=file:/dev/./urandom-Dbiz.red_soft.olap.resource_catalog=/opt/midas/conf/olap/resources -Djava.awt.headless=true-XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -Xdebug -Xnoagent -Djava.compiler=NONE-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005 -XX:MaxPermSize=512m-Djava.library.path=/opt/midas/bin:/opt/midas/lib/ovo:/opt/midas/lib/midas:/opt/OV/lib/hpux32:/opt/OV/lib64:/opt/OV/lib:/opt/oracle/product/11.2.0/lib:/opt/oracle/product/11.2.0/lib32:/opt/OV/www/htdocs/classesorg.codehaus.classworlds.Launcherroot 3344 1 0 Aug11 ? 00:01:56 /bin/sh /opt/midas/bin/watchdog.sh -p 3343 -c/opt/midas/midas.shroot 24234 24160 0 12:31 pts/1 00:00:00 grep -i midas

• To stop the older version of MIDAS, execute the following commands (the base directory depends on the actualproduct version):

# /opt/midas/midas.sh stop

• Make sure that the product media is mounted (e.g. on UNIX systems to /mnt) or the installer image has beencopied to a temporary location.

• Make sure there is enough disk space (~2000MB) in the standard temporary directory or in some other directory.Start the MIDAS installer matching the target OS platform, for example:

# ./install.bin

If there is not enough free disk space in the current directory for temporary files nor in the root file system, thefollowing message will appear and the installation aborts:

MIDAS 4.12Installation Guide

16 of 103 © Copyright 2018, Worldline Germany GmbH

Page 22: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

# ./install.bin Preparing to install...WARNING: /tmp does not have enough disk space!Attempting to use / for install base and tmp dir.WARNING! The amount of / disk space required to perform this installation is greater than what isavailable. Please free up at least 512262 kilobytes in / and attempt this installation again. You mayalso set the IATEMPDIR environment variable to a directory on a disk partition with enough free diskspace. To set the variable enter one of the following commands at the UNIX command line prompt beforerunning this installer again:- for Bourne shell (sh), ksh, bash and zsh:$ IATEMPDIR=/your/free/space/directory$ export IATEMPDIR- for C shell (csh) and tcsh:$ setenv IATEMPDIR /your/free/space/directory

If this message appears, set the IATEMPDIR variable to a location with enough disk space for the time of theinstallation and restart the installer, for example:

# IATEMPDIR=/directory/with/enough/space ./install.bin

The MIDAS installer will unpack itself into the directory defined by IATEMPDIR. After a few moments the actualMIDAS installer GUI should appear. This startup process can take some time. Please be patient and do notinterrupt the execution. The MIDAS installer will guide you through the various installation steps, which aredescribed in the following sections.

2.8. GUI based Installation of the SoftwareThe actual MIDAS installation consists of three phases:

• Determine installation parameters by either analyzing the local system or querying the user

• Installing the MIDAS software files

• Configuring the MIDAS software by applying the previously determined parameters

The MIDAS installer will try to gather as much as possible information to complete the initial phase.During this phase, a number of screens appear which require the user to either confirm the suggested configurationor supply new values.The sequence of the installation steps in the example presented throughout the following sections represents a fullMIDAS installation (see MIDAS Architecture) with the MIDAS Web Application and MIDAS Backend module installedonto an HPOM server. For pure MIDAS Web Application or MIDAS Backend installations, the non-applicableinstaller panels will not appear.The following steps are performed by the MIDAS installer in this order:

• License Agreement

• Context Help

• Cluster Support

• Product Selection

• Server Settings

• Common Port Settings

• Port Settings Derby

• HPOM Configuration

• Self Monitoring Settings

• Document Paper Format

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 17 of 103

Page 23: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

• CVS Settings

• Configuration of MIDAS Web Application Ports

• Transfer Method

• Automatic System Startup

• Pre-Installation Summary

• Starting the Software Installation

• Post-Installation Summary

2.8.1. License Agreement

After starting the MIDAS installer please review and accept the MIDAS License Agreement (see License Agreement),otherwise you cannot continue the installation. The GUI element to confirm the license agreement is only enabledafter scrolling down the license text to the very bottom.

Figure 4. License Agreement

2.8.2. Context Help

On most installer panels, the MIDAS installer offers a context sensitive Help button (otherwise the Help button isgrayed out). The installer screen shown in the example below (see Context Help) informs about this installer feature.

Figure 5. Context Help

MIDAS 4.12Installation Guide

18 of 103 © Copyright 2018, Worldline Germany GmbH

Page 24: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

2.8.3. Cluster Support

On the next panel, the MIDAS installer asks whether HPOM and/or Oracle is running as a HA cluster application (seeCluster Support). This section applies only when installing MIDAS Backend servers. In case of an upgradeinstallation (see Upgrading MIDAS), i.e. to add components to an already existing MIDAS installation, this panel doesnot appear.

Figure 6. Cluster Support

2.8.4. Installation Path

Choose Installation Path illustrates how to set the installation directory. The default, location for a MIDASinstallation is /opt/midas on UNIX-Systems. If this location is not suitable, click Choose to browse to an alternativetarget directory for the installation. That installation directory you choose must reside in a file system withsufficient free space.For more information about installation prerequisites see Hardware.In HA cluster enviroments, make sure that the installation directory is located on a shared filesystem as described inchapter Installing in a HA Cluster.For upgrade installations (described in Upgrading MIDAS), where you want to add components to an alreadyexisting MIDAS installation, this panel does not appear, and the installation path of the existing MIDAS applies.For new installations or update installations (described in Updating MIDAS), the selected target directory must notalready contain a MIDAS installation.

Figure 7. Choose Installation Path

If the MIDAS installer detects an existing MIDAS installation, you can choose to overwrite the existing installation or

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 19 of 103

Page 25: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

specifiy an alternative location for the new installation. The default location for MIDAS is /opt/midas.

If an existing version of MIDAS is detected, you can choose to overwrite the existing installation,you can create a backup of the installed version before continuing with the installation or updateprocess. For more information about backup features as well as more general details aboutupdating and upgrading MIDAS, see Updating or Upgrading MIDAS.

2.8.5. Update/Upgrade Options

The MIDAS installer checks for the presence of a previous installation of MIDAS by evaluating inventory files asdescribed in Installer Inventory File. If a previous installation of MIDAS is detected, the following possibilities exist:

• If the installed version of MIDAS is older and not supported for update installations, an error dialog appears. Inthis case, you must install a new MIDAS instance and, if desired, migrate data manually.

• If the installed version of MIDAS is older than the current MIDAS version and an update installation issupported, the MIDAS installer offers to perform an update, as described in Updating MIDAS.

• If the MIDAS installer detects an existing MIDAS 4.12 installation with some (but not all) components installed,you can choose to upgrade the current installation, as described in Upgrading MIDAS.

For more information about updating and upgrading MIDAS, see Updating or Upgrading MIDAS.

2.8.6. Product Selection

The Product Selection screen provides the possibility to select the desired MIDAS components on the local MIDASserver. Review chapter MIDAS Architecture to understand the terminology, the individual MIDAS components andMIDAS server roles. In the following example the MIDAS Administrator add-on has been selected for a full MIDASinstallation (see Product Selection).

Figure 8. Product Selection

If the MIDAS add-on product MIDAS Synchronizer has been selected an additional CAUTION message will bedisplayed with the following text:

MIDAS 4.12Installation Guide

20 of 103 © Copyright 2018, Worldline Germany GmbH

Page 26: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

MIDAS Synchronizer allows you to perform a full synchronization between an HPOM (defined as MASTER) withone or more HPOM (defined as SLAVES) servers.Please note, that during this full synchronization all HPOM configuration entries on the SLAVE server(s)will be removed (!) and replaced by the HPOM configuration (incl. HPOM files and the MIDAS setup) from theserver which is defined as MASTER.Therefore, please be aware of the consequences the full synchronization script has for the target HPOMservers! It is strongly recommended to have up-to-date backups of all of your HPOM servers, before you arestarting to setup and use MIDAS Synchronizer.MIDAS Synchronizer is an extremly powerful tool, but it can also lead to serious consequences if it isincorrectly used. Therefore, it is absolutely necessary to follow exactly the MIDAS Synchronizerconfiguration and best practices instructions (see the dedicated manual).Generally, it is recommended to use MIDAS Synchronizer within a dedicated project or after properconsultation.Worldline Germany GmbH cannot be held responsible in any way for loss of data any other problems anddamages which might occur due to incorrect operation or setup of MIDAS Synchronizer.

2.8.7. User Check

The installer verifies whether a local OS user named midas exists on the local system. If this is not the case, theMIDAS installer displays a panel explaining this situation and how to create this user account.Figure User Check Unix shows the panel for an installation on a Unix system.For details about the midas user account, please review chapter Create Local OS User for MIDAS.If the user account midas does not exist, the MIDAS installation may be continued and the user account can becreated later if needed (if neither CVS nor SSH will be used on the local MIDAS server, the midas user account is notneeded at all and the error can be ignored).

Figure 9. User Check Unix

2.8.8. Server Settings

In this step of the installation procedure confirm the name of the system hosting the MIDAS server (see ServerSettings).

• Server Hostname: This is the local server hostname. Specify a name or IP address which can be resolved andreached from all involved systems. Default value is the output of the system command "hostname", for example

# hostnamemeggy

HA CLUSTER: To install MIDAS as HA cluster application, enter the virtual host name that represents the HARGrunning the MIDAS server.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 21 of 103

Page 27: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

If you install the HPOM Backend component of MIDAS Synchronizer, you must enter the serverhostname of the HPOM server exactly as it is configured in the HPOM NodeBank.To determine this name, perform the following command, for example with the node namemeggy:

# opcnode -list_nodes node_list=meggy.bes-intern.com===============Name = meggy.bes-intern.comLabel = ......

If this command does not print any output similar to the example above, the node name does not match.

• Local Server Identifier: This value is used within MIDAS to identify individual instances of MIDAS servers. Thisidentifier must not contain any spaces nor special characters.

The recommended naming schema for the Local Server Identifier is to use either the hostnameor some generic name extended by _server, for example meggy_server.

• Server Description: Optional field in which to enter some short description, for example: "OM9 Fullinstallation".

• Server Password: The password specified here will be required when registering the MIDAS Backend serverbeing installed on a remote MIDAS Web Application server (see Registering MIDAS Backend). This passwordprovides some basic authentication to avoid unauthorized access to the MIDAS server.

• Click the Help button for further context sensitive help information.

Figure 10. Server Settings

2.8.9. Common Port Settings

Every MIDAS server (MIDAS Backend or MIDAS Web Application) uses a few ports for internal communication.Either confirm the default port numbers or specify new values (see Common Server Ports).The ports to define in this step are:

• The Server Port (default 9661) is used for the main HTTP(S) communication between MIDAS Web Applicationand MIDAS Backend systems.

• The JMX Port (default 9660) is used for troubleshooting purposes only.It is not referenced by any remote MIDAS components (No firewall opening is required).

MIDAS 4.12Installation Guide

22 of 103 © Copyright 2018, Worldline Germany GmbH

Page 28: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

• The JMS Port (default 9665) is used for internal communication purposes only.It is not referenced by any remote MIDAS components (No firewall opening is required).

• For HTTPS communication between MIDAS servers enable secure communication (HTTPS). Enabling thischeckbox will affect:

◦ The registration of a MIDAS Backend on a MIDAS Web Application (see Registering MIDAS Backend). Thisapplies to all MIDAS Web Application connecting to this MIDAS Backend.

◦ Local communication using the midas.sh command. No extra configuration is necessary for this purpose.

If HTTPS is enabled, HTTPS certificates have to be exchanged between all involved MIDAS servers. This is not anautomatic process and you must perform the post-installation steps described in Using HTTPS.

Figure 11. Common Server Ports

The MIDAS installer will test whether any of the specified ports is already occupied and will display an errormessage in that case (see Port in use detected). To proceed, you must supply a port number which is currently notbeing used.

Figure 12. Port in use detected

Ports being used by other applications that are not running at the time of the MIDAS installationcannot be detected and may cause errors during runtime.

If there is a firewall between MIDAS servers communicating with each other, make sure that the appropriatefirewall rules are configured correctly. See chapter "Architecture and References" in the MIDAS Administration andConfiguration Guide for details.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 23 of 103

Page 29: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

2.8.10. Port Settings Derby

The MIDAS server contains an embedded Derby Database (http://db.apache.org/derby) which is used to storepersistent data from multiple MIDAS components, for example for the advanced auditing feature.

Derby Server Port

The default port suggested is 9664.The MIDAS installer will test whether the specified port is already occupied and will display an error message inthat case as described in Common Port Settings.The Derby DB port is only used locally. Therefore, no firewallopening will be necessary.

Figure 13. Derby DB Port Settings

2.8.11. HPOM Configuration

On the next installer panels define the HPOM database connection settings. This chapter covers two configurationitems:

• Oracle Settings for the Backend Server

• Oracle Access for the Backend Server

This section applies only when installing MIDAS Backend servers.

Oracle Settings for the Backend Server

HPOM uses an Oracle instance to store its configuration data. MIDAS retrieves the HPOM configuration data (forexample nodes, policies) directly from this database using SQL. The HPOM database will be accessed by MIDASpurely in read-only mode.The MIDAS installer attempts to detect most database settings by examining the file/etc/opt/OV/share/conf/ovdbconf. The file ovdbconf is part of the main HPOM server configuration and contains mostdatabase access parameters used by the HPOM server. See HPOM Database Settings for details about the requesteddatabase parameters.

Oracle RAC environments: The MIDAS configuration must be adapted after the MIDAS installation has completed.Please see chapter Oracle RAC Cluster Support. The HPOM database settings requested in this installer screen are(see Oracle for HPOM Location Settings):

• Oracle home path: This must match the ORACLE_HOME environment variable of the HPOM database instanceon the HPOM server.

• Oracle hostname: This value must be the hostname of the system where the HPOM database runs (specificallythe Oracle listener). By default (assuming a local database), the suggested hostname is the HPOM serverhostname which was entered in the previous screen (Server Settings). The hostname must be resolvable on the

MIDAS 4.12Installation Guide

24 of 103 © Copyright 2018, Worldline Germany GmbH

Page 30: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

HPOM server.

HA CLUSTER: If the HPOM database instance is running as a HA cluster application, specify the virtual hostname ofthat HARG.

• Oracle port: Since the MIDAS installer cannot automatically determine the Oracle listener port, the standardvalue 1521 is suggested as default. Please double-check if this is correct.

• Secure Oracle connection: Enable the checkbox if a secure Oracle communication is being used.Click on the Help button to receive more context sensitive help information.

Figure 14. Oracle for HPOM Location Settings

Oracle Access for the Backend Server

The subsequent screen (see Oracle for HPOM Access Settings) queries additional database parameters like instancename, username and password required to access the correct Oracle database instance.Make sure that the Oracle DB name and HPOM DB instance name are correct. These values are extracted from/etc/opt/OV/share/conf/ovdbconf and the HPOM XPL configuration and should be correct if the HPOM server runsnormally.The user name and password of the database user which will be used to connect to the HPOM database must bespecified. By default, it is assumed that the database user opc_op will be used; alternatively, the database useropc_report (who has read-only rights) can be used as well.Generally, any database user can be specified as long as that database user has sufficient privileges to read allrelevant HPOM database objects.

The passwords for the both database users (opc_op or opc_report) are defined during theinstallation of the HPOM server. In the MIDAS installer screen supply exactly this password. SeeWrong or Unknown HPOM Passwords if they are unknown.

Do not confuse the database user opc_op with the accounts of the same user name in HPOM andthe UNIX operating system itself. All three exist and are completely different accounts.

The installer will verify the entered password. If that test fails, the following warning (see opc_op Connection Error)will be displayed:

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 25 of 103

Page 31: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Figure 15. opc_op Connection Error

If you ignore this warning and proceed anyway, the MIDAS Backend server will fail to connect to the HPOMdatabase and most MIDAS functionality will be unavailable. Though not recommended, it is possible to finish theinstallation first and re-configure the DB access with the correct information afterwards. In that case refer to theMIDAS Administration and Configuration Guide for instructions how to change database access parameters at alater time.

Figure 16. Oracle for HPOM Access Settings

2.8.12. Self Monitoring Settings

When installing a standalone MIDAS Backend, the host name and port of an initial MIDAS Web Application has to bespecified.

This section applies only when installing pure MIDAS Backend servers, i.e. without the MIDASWeb Application.

If choosing the Full-Installation option, the self-monitoring screen will not appear. The local system runs a MIDASWeb Application, which will be used for this purpose. The MIDAS installer contains something like a HPOM SMARTPlug-in providing some self management capabilities. It consists of HPOM policies, policy groups, node groups,profiles, tools, and so on.

This set of HPOM configuration objects will be automatically uploaded into the HPOM database during a MIDASBackend installation. The hostname and port of the MIDAS Web Application (same as used for working with theregular MIDAS GUI) will be used to construct URL Tools in HPOM, so the MIDAS GUI can be started from operator’sApplication Desktop.To make these tools work immediately, specify the required parameters (see Self Monitoring Settings). If unsure,leave these values unchanged and update the HPOM Tools manually later.

• Web Application Host: Enter here the host name of the system where the MIDAS Web Application is installed.Specify a host name which is resolvable and reachable from all systems, where such an HPOM Tool will belaunched by an HPOM user.

MIDAS 4.12Installation Guide

26 of 103 © Copyright 2018, Worldline Germany GmbH

Page 32: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

• Web Application HTTP Port: The port where the MIDAS Web Application to be used is listening. Default port is9662.

Figure 17. Self Monitoring Settings

2.8.13. Document Paper Format

On the next installer panel, choose the default paper format used by the MIDAS document generation subsystem.

This section applies only when installing MIDAS Web Application servers.

Choose between the paper formats A4 or US letter (see Document Paper Format).

Figure 18. Document Paper Format

2.8.14. CVS Settings

The MIDAS Web Application contains the MIDAS version control subsystem (VCS). During MIDAS installation youcan choose whether to use this feature at all and supply some basic parameters.

This section applies only when installing MIDAS Web Application servers.

The current MIDAS version supports only CVS as actual implementation of the versioning capability. However, theMIDAS installer does NOT contain the actual CVS software itself. During MIDAS installation an empty CVS repositorywill be created.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 27 of 103

Page 33: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

The CVS software itself must be installed by the user separately (due to licensing restrictions). Forsimplicity it is recommended to install the CVS software before installing MIDAS. For all detailson the installation and configuration of CVS, please refer to MIDAS Versioning.

During the MIDAS installation specify the following parameters:

• [X] enable CVS Feature

• CVS Binary: Enter the path to the CVS executable (e.g. /usr/bin/cvs).

• Repository path: The CVS repository will be created here. Default location is the directory data/repositoryrelative within the MIDAS installation directory, for example /opt/midas/data/repository. If needed, configureany other location intended for this purpose. For non-default repositories or other CVS configuration optionsplease see MIDAS Versioning.

Figure 19. CVS Settings

2.8.15. Configuration of MIDAS Web Application Ports

The MIDAS installer queries the ports on which the MIDAS Web Application can be reached using your web browser(see MIDAS Web Application Server Settings).

MIDAS installer will check whether the specified ports are available. If any of the ports is occupied, a warningmessage will be displayed and you will be asked to change the port before proceeding. The default ports are:

• HTTP Port number: 9662

• HTTPS Port number: 9663

If you enter a non-default port number, you also have to specify that alternate port number in the URL, which isused to invoke the MIDAS Web Application from the web browser. With the default ports, this is:

http://midas-webapp:9662/https://midas-webapp:9663/

After the installation of the MIDAS Web Application has completed, the HTTP port may be blocked by restricting it tolocal access only. For further details refer to Disabling the MIDAS Web Application’s HTTP Port (9662).

MIDAS 4.12Installation Guide

28 of 103 © Copyright 2018, Worldline Germany GmbH

Page 34: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Figure 20. MIDAS Web Application Server Settings

In case of a full installation, the port numbers supplied here are also inserted into a set of HPOMtools (formerly „HPOM Applications") as explained in Self Monitoring Settings. These HPOM toolswill be uploaded into the HPOM database during the MIDAS installation.

For details on the HPOM Java GUI integration, please refer to the MIDAS Administration and Configuration Guide.

2.8.16. Transfer Method

To transfer large amounts of HPOM data between MIDAS servers (MIDAS Web Applications and/or MIDAS Backends)originating for example from policy or node group downloads, MIDAS offers three options:

• FTP using an embedded FTP server

• embedded SCP/SSH using an embedded SSH server

• external SSH using a standard external SSH server

During MIDAS installation you may choose whether to enable FTP or SSH transfers at all and which server ports touse (see Transfer Method Configuration). FTP requires no further configuration but is considered as insecure. To useeither SSH method, further post-installation steps are necessary as explained in SSH in MIDAS - Overview. In eithercase, enable SSH transfer on the MIDAS installer panel shown below.

[X] Enable FTP for file transferFTP Port: 10021FTP Data Port: 10020

Enable SCP even if you plan to use a standard external SSH server (port 22) and leave the portnumbers in the MIDAS installer unchanged. After the MIDAS installation has completedsuccessfully, refer to section SSH in MIDAS - Overview.

For SCP/SSH-based transfer (both external and embedded) the public keys must be exchangedbetween the involved MIDAS servers. Refer to section SSH in MIDAS - Overview for details.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 29 of 103

Page 35: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Figure 21. Transfer Method Configuration

2.8.17. Automatic System Startup

In this step the start up method of the local MIDAS server has to be defined. Select between:

HPOM 9

Start with ovc startup integration:The MIDAS server can be integrated into ovc -start and ovc -stop. This option is only available where HPOM 9.x isinstalled (see Automatic System Startup).

Start on system startup

On UNIX systems standard OS boot scripts (typically in /etc/init.d) will be created.

Figure 22. Automatic System Startup

2.8.18. Pre-Installation Summary

All previous MIDAS installer panels have collected configuration information used to generate an initialconfiguration after the actual MIDAS software has been installed. At this point the actual installation of MIDAS hasnot yet taken place. Before the actual software installation process starts, the installation wizard displays asummary screen (see Pre-Installation Summary).Review the details supplied, in particular the installation folder and disk space requirements.Click Install to start the actual installation; click Previous to return to any dialog to check or change the installationparameters.

MIDAS 4.12Installation Guide

30 of 103 © Copyright 2018, Worldline Germany GmbH

Page 36: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Figure 23. Pre-Installation Summary

2.8.19. Starting the Software Installation

After clicking on Install, the MIDAS installation starts and displays the progress. During the installation some pop-upwindows will appear when the different internal modules are configured and started. The installation procedureconsists of two phases:

• Installation of the MIDAS software itself (binaries, configuration files, documentation, and so on).

• Configuration of the MIDAS components based on the parameters provided by the user during the installationsession.

The configuration phase of the installation includes the execution of various scripts and commands. During theinstallation of a MIDAS Web Application on slow systems or machines with a high workload the Derby databasestartup may fail resulting in a Derby database initialization error (see Derby database initialization Error).If this error message appears, select "Retry". Generally this fixes the problem.

Figure 24. Derby database initialization Error

If the Retry operation was not successful or if logging into the MIDAS web interface doesn‘t work after theinstallation has completed, refer to section MIDAS GUI - No Login.

2.8.20. Post-Installation Summary

After the MIDAS installation has completed, an installation summary will be displayed consisting of two screens:first a panel showing MIDAS server information as needed to register this MIDAS server at another MIDAS Web

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 31 of 103

Page 37: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Application (see Server Identification), second a summary of ports used by this MIDAS instance (see Portssummary).

Figure 25. Server Identification

Print or save this information, though it is possible to view this information at any time after the installation byrunning the following command:

# /opt/midas/midas.sh backend[...][echo] Server lanzarote_server: OM Development System EMEA[echo] Server Identifier: lanzarote_server[echo] Hostname: lanzarote.bes-intern.com[echo] Protocol: http[echo] Port: 9661[echo] Secure Communication: false[echo] Platform: unix[echo] Install Directory: <MIDAS_HOME>[echo] Services:[echo] file[...]BUILD SUCCESSFUL

A summary about the allocated ports is shown on the subsequent panel (see Ports summary).

Figure 26. Ports summary

MIDAS 4.12Installation Guide

32 of 103 © Copyright 2018, Worldline Germany GmbH

Page 38: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Installation Errors and Warnings

In the event of non-fatal errors and warnings during the MIDAS installation process, the message illustrated inInstallation Error appears. The stated installation log file will be created in the following location:/opt/midas/MIDAS_Product_Family_Install_<Timestamp>.log

For steps possibly necessary after the MIDAS installation has completed, see Post Installation Tasks. However the logfile does not exist until you close the MIDAS installer. Click Done to close the installer.

Figure 27. Installation Error

2.9. Installation of the Software without a GUI (console-basedinstaller)The console installer exactly queries the same parameters as the GUI based installer does. It is the same thing inconsole mode only. The following screens are presented in case an upgrade of an existing MIDAS ConfiguratorBackend installation to MIDAS Administrator with Synchronizer is done.

1. Launch the installer

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 33 of 103

Page 39: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

[root@meggy ~]# /tmp/install.bin -i consolePreparing to install...Extracting the JRE from the installer archive...Unpacking the JRE...Extracting the installation resources from the installer archive...Configuring the installer for this system's environment...

Launching installer...

===============================================================================MIDAS Product Family (created with InstallAnywhere)-------------------------------------------------------------------------------

Preparing CONSOLE Mode Installation...

===============================================================================Introduction------------

It is strongly recommended that you close any other running programs beforecontinuing with this installation.To proceed to the next step, click Next. If you want make changes to dataentered in a previous step, click the Previous button.

PRESS <ENTER> TO CONTINUE:===============================================================================

2. The next screens show the License Agreement etc.. Read it and confirm each step with <Enter>.

===============================================================================License Agreement-----------------

Installation and use of MIDAS Product Family requires acceptance of thefollowing license agreement:

Software License Terms and Conditions

.....

.....

DO YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENT? (Y/N):

3. Context Help - confirm with <Enter>

===============================================================================Context Help------------

Help is available for the choices you have to make in the more complexinstallation screens.Click the Help button, where available, to display more information.

PRESS <ENTER> TO CONTINUE:

MIDAS 4.12Installation Guide

34 of 103 © Copyright 2018, Worldline Germany GmbH

Page 40: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

4. Upgrade mode

===============================================================================Already installed components found----------------------------------

The installer has detected, that some MIDAS Product Family components from thesame version are already installed on this system.

Please select "Upgrade" to add components to your existing MIDAS Product Familyproduct or "Exit" to abort the installation.

  ->1- Upgrade  2- Exit

ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT THE  DEFAULT:

5. Cluster Support

===============================================================================Cluster support---------------

Please indicate if either HPOM and/or Oracle is running in a high-availabilitycluster.

  1- YES  ->2- NO

ENTER THE NUMBER FOR YOUR CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT::

6. Product Selection - in this example the existing MIDAS Configurator installation will be upgraded to MIDASAdministrator with Synchronizer

===============================================================================Product Selector----------------

  1- HP OM Backend Server  2- HP OM Agent Driver  3- Web Application Server  4- Web Application  5- MIDAS Administrator  6- MIDAS Synchronizer  7- MIDAS Debugger  8- MIDAS Outage Manager  9- MIDAS Inventory

  -> = Default Values  Choose Products for installation e.g. 3,4,5,6,7 : 5,6

7. Server Settings - keeping the defaults

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 35 of 103

Page 41: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

===============================================================================Server Settings: Server Hostname--------------------------------

Enter the name of the host on which you are installing MIDAS Product Family,

Server Hostname (DEFAULT: meggy):

===============================================================================Server Settings: Server Identifier----------------------------------

Enter the name of the local identifier that is required for internal use.

Local Server Identifier (DEFAULT: meggy_server):

===============================================================================Server Settings: Server Description-----------------------------------

Enter the server description.

Server Description (DEFAULT: ):

===============================================================================Server Settings: Password-------------------------

Enter the password for the server.

Please Enter the Password:===============================================================================

8. Ports Settings - keeping the defaults

MIDAS 4.12Installation Guide

36 of 103 © Copyright 2018, Worldline Germany GmbH

Page 42: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Port Settings-------------

MIDAS Product Family requires several ports for internal communication. If youare using a firewall, please ensure that the specified ports are open andavailable. The installer checks the availability of the ports you enter here.

Server Port (DEFAULT: 9661):

===============================================================================Port Settings-------------

MIDAS Product Family requires several ports for internal communication. If youare using a firewall, please ensure that the specified ports are open andavailable. The installer checks the availability of the ports you enter here.

JMX Port (DEFAULT: 9660):

===============================================================================Port Settings-------------

MIDAS Product Family requires several ports for internal communication. If youare using a firewall, please ensure that the specified ports are open andavailable. The installer checks the availability of the ports you enter here.

JMS Port (DEFAULT: 9665):

===============================================================================Port Settings-------------

Enable secure communication (https)

  ->1- No  2- Yes

ENTER THE NUMBER FOR YOUR CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT::===============================================================================

9. System Startup Method

Automatic System Startup------------------------

Specify how and when you want MIDAS Product Family components to start, forexample, when the system hosting MIDAS Product Family boots.

  ->1- Start on system boot  2- Do not start on system boot

ENTER THE NUMBER FOR YOUR CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT::===============================================================================

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 37 of 103

Page 43: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

10. Installation Summary

Pre-Installation Summary------------------------

Please Review the Following Before Continuing:

Product Name:  MIDAS Product Family

Install Folder:  /opt/midas

Disk Space Information (for Installation Target):  Required: 610,831,791 Bytes  Available: 19,604,709,376 Bytes

PRESS <ENTER> TO CONTINUE:

11. Installation Progress

===============================================================================Installing...-------------

 [==================|==================|==================|==================] [------------------|------------------

 ----

 . Installation Completion + ---- ===============================================================================Installation Complete---------------------

Congratulations! MIDAS Product Family has been successfully installed in:

  /opt/midas

PRESS <ENTER> TO EXIT THE INSTALLER:

MIDAS 4.12Installation Guide

38 of 103 © Copyright 2018, Worldline Germany GmbH

Page 44: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

3. Multiple parallel MIDAS installationsThis chapter covers the installation of multiple, parallel MIDAS instances

3.1. OverviewThe information provided in this section covers the following areas:

• Example Scenarios

• Parallel Operation

• Alternative Operation

• Installing Parallel MIDAS Instances

• Configuring the MIDAS Startup Mode

• Configuring the MIDAS OS User

• Switching Between MIDAS Instances

3.2. Example ScenariosMIDAS supports multiple instances on the same system, either with the same or different product versions or HPOM AdminUI (all collectively referred to as MIDAS unless stated otherwise). Parallel installations can be used in thefollowing scenarios:

• For evaluation purposes or testing

• For update installations (see Updating or Upgrading MIDAS)

In either case, two scenarios exist:

• Multiple MIDAS instances should run at the same time. For details see Parallel Operation

• Only one MIDAS instance is active at any given time and the same port numbers are used by all instances. Fordetails review Alternative Operation

Generally, the following rules apply:

• Each MIDAS instance MUST be installed separately in different base directories, even if having the same productversion. Currently it is NOT supported to start multiple MIDAS instances from the same installation like forexample /opt/midas unless assisted by MIDAS product support.

• If multiple MIDAS instances shall run concurrently, they must use different ports. It is not possible on OS-levelthat multiple processes share the same port.

• Depending on the usage scenario, the start-up mode of each MIDAS instance may be different. For example, oneMIDAS instance shall start automatically while another manually.

Details are presented in the following sections. Before installing MIDAS, review the architecture options (see MIDASArchitecture).

HP OM AdminUI always installs into /opt/OV/OMU/adminUI. It is not possible to change thislocation.HP OM AdminUI always consists of a full installation as defined in MIDAS Architecture.

3.3. Parallel OperationIf multiple MIDAS instances shall be running on the same system and at the same time, those instances MUST usedifferent ports. Perform regular product installations as described in Installing MIDAS considering:

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 39 of 103

Page 45: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

• You MUST install each instance separately and into different installation directories.

• Do not choose the same MIDAS Backend ID (see Server Settings) for different instances.

• For all ports queried by the MIDAS installer, specify unique values for each instance. A typical guideline is to usethe default ports (9660 and so on) for one and, for example, 10660 for another. The MIDAS installer will verifyand report ports occupied during installation but cannot detect port conflicts with processes that are notrunning at installation time.

• Depending on the start-up mode, either choose the appropriate mode while installing MIDAS or subsequentlyupdate the MIDAS configuration. See Configuring the MIDAS Startup Mode for details.

3.4. Alternative OperationThis scenario represents a situation that at any time only one MIDAS instance may be active. In that case, eachMIDAS instance may use the same port numbers. This has the advantage that MIDAS users don’t need to rememberdifferent port numbers (in case of MIDAS Web Applications) but rather just use always the same port and connect tothe MIDAS instance which is currently active. Make sure that at most one MIDAS instance starts up automaticallyand all others are configured for manual start-up. Perform regular product installations as described in InstallingMIDAS considering:

• You MUST install each instance separately and into different installation directories.

• You may choose the same MIDAS Backend ID (see Server Settings) for different instances (then, also use the sameMIDAS Backend password). For MIDAS Backend servers this may even have the advantage that a MIDAS WebApplication transparently refers to the currently active instance.However, make sure that MIDAS Backend and MIDAS Web Application have compatible product versions.

• Depending on the start-up mode, either choose the appropriate mode while installing MIDAS or subsequentlyupdate the MIDAS configuration. See Configuring the MIDAS Startup Mode for details.

3.5. Installing Parallel MIDAS InstancesTo actually install multiple parallel MIDAS on the same system, depending on the involved product versions,different steps have to be performed:

• To install a MIDAS instance of a higher version than already installed, perform an update installation (with orwithout migrating data) as described in Updating MIDAS

• To install a MIDAS instance of the same or a lower version than already installed, perform the following steps:

◦ Temporarily move away the installer inventory file matching the existing MIDAS instance (see InstallerInventory File). Otherwise, the MIDAS installer will offer an Upgrade installation

◦ Perform a standard MIDAS installation as described in Installing MIDAS

◦ Restore the saved installer inventory file unless it has the same name. Backup all involved inventory files andmake sure the correct inventory file is in place when removing a MIDAS instance

3.6. Configuring the MIDAS Startup ModeDuring MIDAS installation you choose the start-up mode of the MIDAS instance (see Automatic System Startup).Depending on the desired scenario, configure the start-up mode as desired, however consider:

• for MIDAS instances to be started manually, simply select the corresponding start-up mode in the MIDASinstaller. No additional steps are necessary. Switch between the instances as described in Switching BetweenMIDAS Instances

• for MIDAS instances to be started automatically, select the corresponding start-up mode in the MIDAS installer.Subsequent steps depend on the start-up mode as explained in the following sections

MIDAS 4.12Installation Guide

40 of 103 © Copyright 2018, Worldline Germany GmbH

Page 46: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

HP OM AdminUI always registers with ovcd.So, there is no chance, to select the startup methodfor this product.

In all cases verify (and modify, if needed) that the file /opt/midas/conf/config.groovy contains the right MODEsetting matching the desired start-up mode, for example:

midasGroovy {  startUpMode = "[startup]"  ovc = '/opt/OV/bin/ovc'  ovstart = '/opt/OV/bin/ovstart'  ovstop = '/opt/OV/bin/ovstop'  ovcProg = "midas4120"  ovstartProg = "midas4120"

The following MODE values exist:

• Value ovc represents an ovcd integration

• Value ovstart represents an ovstart integration

• Parameter [startup] either represents an OS init integration or a manual start-up

3.6.1. HPOM 9.x ovcd Integration

An ovcd integration (HPOM 9.x) creates a registration file in the directory /var/opt/OV/conf/ctrl, for example namedmidas4120.xml.If multiple MIDAS instances with or without the same product version exist, all may use the same file name and mayreplace each other during installation. This will result in a situation that effectively only one registration exists.To fix this situation, change the file /opt/midas/conf/ovo/midas.xml of each MIDAS instance by editing the XML filesand assigning individual registration IDs, for example change the lines

<ovc:Component><ovc:Name>midas4120</ovc:Name><ovc:Label><ovc:String>MIDAS Server</ovc:String></ovc:Label>

into:

<ovc:Component><ovc:Name>midas4100_1</ovc:Name><ovc:Label><ovc:String>MIDAS_Inst_1</ovc:String></ovc:Label>

Then, run the command:

# /opt/OV/bin/ovcreg -add /opt/midas/conf/ovo/midas.xml

Verify the directory /var/opt/OV/conf/ctrl as described above whether the registration is now correct. Ultimately,the command:

# /opt/OV/bin/ovc

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 41 of 103

Page 47: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

must display all instances. To unregister a MIDAS instance from the ovcd start-up integration, determine theregistration ID by running the ovc command, for example:

# /opt/OV/bin/ovc...midas4100_1 MIDAS Inst 1 SERVER,OPC,UI 34222 Running...

Then unregister the desired instance, for example using the following command:

# /opt/OV/bin/ovcreg -del midas4100_1

3.6.2. OS init Integration

On UNIX systems, an OS init integration creates a set of scripts and symbolic links in directories like /etc/init.d orsimilar (may be different depending on the actual OS, see below). If multiple MIDAS instances with or without thesame product version exist, all may use the same file names and may replace each other during installation. Thiswill result in a situation that effectively only one registration exists.Depending on the OS, the following set of files and symbolic links will be created.

/etc/init.d/midas412_server (Linux)

The MIDAS startup scripts support the standard parameters start_msg, stop_msg, start and stop. Additionally, run-level links are created referring to the midas_server script. Depending on the platform the start-up link are locatedin:

/etc/rc.d/rc3.d (RH Linux 6 and later)/etc/init.d/rc3.d (other Linux)

The shutdown links are located in:

/etc/rc.d/rc2.d (RH Linux 6 and later)/etc/init.d/rc2.d (other Linux)

Default numbers are 1 for startup links and 99 for shutdown links.To make multiple MIDAS instances start and stop, duplicate the entire init structure while assigning new names (forexample, name the init script of a new instance midas4120_server) and sequence numbers.Inside of the actual init script update the MIDAS installation path appropriately.To unregister a MIDAS instance from the OS start-up, remove the corresponding start-up and shutdown links. Theactual scripts may or may not be retained.

3.7. Configuring the MIDAS OS UserThe OS user midas is used by a MIDAS server for the MIDAS versioning subsystem (specifically for executing CVScommands) and SSH-based transfer operations. The HOME directory of the OS user midas must match theinstallation directory of the currently active MIDAS instance.Since there can be only one OS user with the same name and a user account cannot have multiple HOMEdirectories, the following options exist to solve this dilemma:

• MIDAS Backend servers can be ignored with regards to MIDAS versioning (MIDAS versioning happens only onMIDAS Web Application servers)

• HP OM AdminUI instances can be ignored entirely as HP OM AdminUI neither supports MIDAS VCS nor MIDAStransfers

• Consider not using MIDAS VCS nor MIDAS transfers for MIDAS where this functionality is not needed

• Consider sharing the base directory of SSH-based transfers among MIDAS instances, for example:

MIDAS 4.12Installation Guide

42 of 103 © Copyright 2018, Worldline Germany GmbH

Page 48: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

◦ The HOME directory of the OS user matches the directory /opt/midas

◦ An additional MIDAS instance exists in /opt/midas4100_1

◦ Perform the following steps essentially establishing a symbolic link that shares the MIDAS download andtransfer data directory between both instances:

# cd /opt/midas4100_1/data# mv clipboard clipboard-orig# ln -s <MIDAS_HOME>/data/clipboard .

◦ If multiple involved MIDAS instances use a standard external SSH server for data transfers, the SSH keys ofthe midas user must be cloned between the MIDAS instances.

• Similarly to sharing the transfer data directory described above, share the VCS data repository (MIDAS WebApplication servers only) located by default in /opt/midas/data/repository.

3.8. Switching Between MIDAS InstancesIn an alternate usage scenario, you can switch between different MIDAS instances by stopping one instance andstarting the other instance, as illustrated iin the following example:

• Stop the running MIDAS instance, for example:

# /opt/midas/midas.sh stop

• Start the alternative instance, for example an HP OM AdminUI:

# /opt/OV/OMU/adminUI/adminui start

You cannot run multiple MIDAS instances at the same time, if they are using the same set of portnumbers; the instance starting last will fail to allocate the already occupied ports.

If an ovcd (HPOM 9.x) integration has been configured, alternatively the command ovstart/ovstop or ovc can be usedto start/stop a MIDAS instance which effectively yields the same result since the command midas.sh just callsovstart/ovstop or ovc.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 43 of 103

Page 49: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

4. Testing and Verifying the MIDAS InstallationThis chapter covers the steps to test and verify a completed MIDAS installation

4.1. OverviewThe information provided in this section covers the following areas:

• Accessing the MIDAS Web Interface

• Accessing the MIDAS Backend

4.2. Accessing the MIDAS Web InterfaceTo access the MIDAS web interface for the first time perform the following steps:

1. In your web browser, open the URL referring to the address where the MIDAS Web Application is installed.Default ports are 9662 (HTTP) and 9663 (HTTPS) unless different values have been specified during installationof the MIDAS Web Application:

◦ Unsecured access using HTTP: http://midas-webapp:9662

◦ Secure access using HTTPS: https://midas-webapp:9663

The MIDAS user interface should appear in the web browser as illustrated in MIDAS Web User Interface.

2. Log in using the default user name admin and password secret.

Logging in and opening pages within the MIDAS GUI the very first time will take more time thanlater because the web browser must load all GUI components once - later many files will bestored in the web browser‘s cache.

Figure 28. MIDAS Web User Interface

When logging into the MIDAS web interface as user admin for the first time or whenever the MIDAS WebApplication determines that the user admin has the default password secret set. It is required to change the defaultpassword for security reasons. After logging on to the MIDAS GUI and setting a new password for the user admin

MIDAS 4.12Installation Guide

44 of 103 © Copyright 2018, Worldline Germany GmbH

Page 50: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

the next step depends on the architecture of your MIDAS environment as explained in section Accessing the MIDASBackend.

4.3. Accessing the MIDAS BackendLogging on to the MIDAS Web Application provides access to various MIDAS functions but not yet to objectsmanaged by a MIDAS Backend such as HPOM data like policies and so on. To perform this kind of activity, first selectthe desired MIDAS Backend and choose the corresponding MIDAS context as described in the following sections.Depending on the architecture of your MIDAS installation, MIDAS Backends must be registered first. This will benecessary if the following conditions are true:

• The MIDAS Web Application has not been installed on the same system as the MIDAS Backend

• Multiple MIDAS Backends will be accessed In either case, the MIDAS Backend to be accessed must be registeredat the MIDAS Web Application as described in Split MIDAS Web Application and MIDAS Backend Installation.

Otherwise, if both MIDAS Backend and MIDAS Web Application reside on the same system, continue as described inFull MIDAS Installation on the HPOM Server.

MIDAS supports working with multiple MIDAS Backends at the same time, for example inmultiple web browser tabs. Always make sure that the current MIDAS GUI page is connected tothe intended MIDAS Backend when performing modifications. See section Backend Coloringabout how to reduce the risk of using a wrong MIDAS Backend.

MIDAS does NOT support working as multiple users at the same time within the same GUIsession. After logging off and logging on again as a different user within the same web browsersession, other MIDAS pages in the same web browser may still show the previous user name.Either reload or close and re-open such pages.

4.3.1. Full MIDAS Installation on the HPOM Server

After logging on to the MIDAS Web Application and changing the password of the user admin the MIDAS welcomescreen appears (see MIDAS Welcome Screen).

Figure 29. MIDAS Welcome Screen

This MIDAS welcome screen is also the MIDAS Home context.On all pages of the MIDAS GUI, the top right corner of the GUI displays the MIDAS user as who you are currentlylogged into MIDAS and (directly below) the MIDAS Backend connected on the current page.In the scenario described in this section we assume a so-called „Full installation“ with both the MIDAS Backend andMIDAS Web Application on the same system - in that case the local MIDAS Backend is connected by default.After logging on, select the desired MIDAS context, for example click the OM icon to choose the HPOM context andaccess all HPOM configuration objects. Then, the MIDAS GUI will present the set of available HPOM configurationobjects (see HPOM Objects Main Page).

If the OM icon is not visible, make sure that the correct MIDAS Backend is selected.

The MIDAS GUI field labelled „Comment“ can be used to enter a global comment. This comment (stored as GUIsession cookie) will be logged in the MIDAS auditing subsystem for all subsequent GUI operations.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 45 of 103

Page 51: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

This feature can be used for example to record work order details of a change request.After completing all operations in MIDAS that belong to that activity, either clear the global comment or enter a newone for another work order.

Figure 30. HPOM Objects Main Page

Displaying the main page of a HPOM context is still served by the MIDAS Web Application and may be functionaleven if the connected MIDAS Backend does not work correctly.To verify the correct function of the MIDAS Backend component select any of the contained objects, for examplefollow the link titled “Policy Bank”. This step will trigger a request to the MIDAS Backend which in turn loads datafrom the HPOM database.If this operation completes successfully, the resulting screen looks like in the following example (see HPOM PolicyBank) and proves a successful communication between MIDAS Web Application and MIDAS Backend component:

Figure 31. HPOM Policy Bank

4.3.2. Split MIDAS Web Application and MIDAS Backend Installation

Separating the MIDAS Web Application and MIDAS Backend components onto different computers offers thefollowing main benefits (also see Choosing the Right MIDAS Architecture):

• single central access point (MIDAS Web Application) for all MIDAS-related functions with concurrent access to allregistered MIDAS Backends

• one common MIDAS user configuration covering all MIDAS Backends

• distribution of system load between both involved systems

If your MIDAS environment consists of such a separate MIDAS Web Application server and (possibly multiple)MIDAS Backend server(s), use the MIDAS Web Application as single central access point (for example using the URLhttp://midas-webapp:9662) and switch between the MIDAS Backends within the MIDAS GUI session.To implement this scenario, all non-local MIDAS Backends must be registered with the MIDAS Web Application asdescribed in the following section.If the MIDAS Web Application is not part of full installation, after logging on to the MIDAS Web Application, noMIDAS Backend will be automatically selected and the Welcome screen appears as in the following example afterchanging the password of the MIDAS user admin (see MIDAS Web Application Only Installation).Note the missing OM icon in the context bar.

MIDAS 4.12Installation Guide

46 of 103 © Copyright 2018, Worldline Germany GmbH

Page 52: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Figure 32. MIDAS Web Application Only Installation

To display an overview about all registered MIDAS servers (inluding the local Web Application server), use the "ListAll" menu item within the Servers main menu, as shown in the following example (see List Servers).The green or red indicator shows the status of the corresponding MIDAS server.

Figure 33. List Servers

If there are already registered MIDAS Backend servers, select one in the Servers main menu and proceed usingHPOM by performing the same steps as described in Full MIDAS Installation on the HPOM Server.

4.3.3. Registering MIDAS Backend

To register an additional MIDAS Backend select from the footer drop-down menu: Choose an action → "Add Server"(see Register Server)

Figure 34. Register Server

In the next window enter the correct information for the MIDAS Backend to be registered as in the followingexample (see Register New MIDAS Backend). Specify the information which you provided during the installation ofthat MIDAS Backend.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 47 of 103

Page 53: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Figure 35. Register New MIDAS Backend

To determine the configuration settings specified during installation of the MIDAS Backend, run the followingcommand on the MIDAS Backend server:

# /opt/midas/midas.sh backend[...]Server mrslave_server  Hostname: mrslave  Protocol: http  Secure communication: false  Port number: 9661  Description:

Exactly enter the information displayed by the command midas.sh backend into the GUI screen to register thatMIDAS Backend. Leave the menu Backend Type with the value Standard Backend. The requested value for the fieldPassword must be equal to the value specified for the Server Password during the installation of the MIDAS Backend(see Server Settings).

Make sure that the choice of using HTTP or HTTPS communication between MIDAS WebApplication and MIDAS Backend is identical on both sides (see also Using HTTPS). If the output ofthe command midas.sh backend says "Secure Communication: true", the GUI field SSL must beenabled.

After entering all information and saving, the newly registered MIDAS Backend should show up with a greenindicator (see Successful MIDAS Backend Registration).

Figure 36. Successful MIDAS Backend Registration

After a new MIDAS Backend has been registered, test communication by clicking on the hyperlink representing thenew MIDAS Backend (in the example marge_server).The MIDAS Web Application will connect to this MIDAS Backend and the OM context icon appears in the top menu(assuming the new MIDAS Backend contains HPOM functions).At the same time the name and HPOM version of the selected MIDAS Backend are shown (see Selected HPOMBackend).

MIDAS 4.12Installation Guide

48 of 103 © Copyright 2018, Worldline Germany GmbH

Page 54: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Figure 37. Selected HPOM Backend

4.3.4. Backend Coloring

To reduce the risk of accidentally performing some operation on the wrong Backend, MIDAS allows to configure thepage heading layout per Backend.Compared with the standard page heading layout illustrated in Selected HPOM Backend, the example illustrated inCustom Highlighting in the MIDAS Page Header shows how you could highlight the productive HPOM Backend towarn users not to perform changes.

Figure 38. Custom Highlighting in the MIDAS Page Header

To configure such a Backend-specific layout, perform the following steps:

• On the MIDAS Web Application system, edit the file /opt/midas/conf/midas_backend_banners.xml

• Per MIDAS Backend to configure, create a section like

<!-- marge_coloring -->

<serverbannerconfig> <serverid>marge_server</serverid>  <banner>  <when>backendSelected</when>  <background-color>#FFF000</background-color>  <background-orientation>vertical</background-orientation>  <message-text>ATTENTION - Production System</message-text>  <text-color>#366BAC</text-color>  </banner></serverbannerconfig>

• Make sure the matching server name is registered in the <serverid> tag, in the example above marge_server

• The file midas_backend_banners.xml included in a standard MIDAS Webapp contains various examples andcomments explaining the different configurable parameters

No restart of any MIDAS components is needed, just reload the current page in the GUI.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 49 of 103

Page 55: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

5. Installation TroubleshootingThis section provides basic troubleshooting information concerning the most common problems that occur duringor after a MIDAS installation.

5.1. OverviewThe information in ths section covers the following topics:

• Display Problems

• Wrong or Unknown HPOM Passwords

• MIDAS GUI - No Login

• Installation Log Files

5.2. Display Problems

5.2.1. X Server Problems

If you experience problems with the X server or X redirection in general, have a look at the information in thefollowing section:

• Display Access

Display Access

During the installation process, the MIDAS installer attempts to open a GUI. On UNIX systems, the GUI sessionrequires the correct setting of the DISPLAY environment variable and, in addition, permission to access the X Serveron the workstation where the installation is initiated. On Windows systems, the MIDAS installer always runs locallyand can be displayed remotely using software like VNC, Windows Remote Desktop, and so on.

The troubleshooting information regarding X-Server problems apply only to MIDAS installationsonto UNIX systems.

If the MIDAS installer cannot display the GUI, the following output will appear in the console where the installationhas been started:

MIDAS 4.12Installation Guide

50 of 103 © Copyright 2018, Worldline Germany GmbH

Page 56: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

[root@meggy ~]# /tmp/install.binPreparing to install...Extracting the JRE from the installer archive...Unpacking the JRE...Extracting the installation resources from the installer archive...Configuring the installer for this system's environment...

Launching installer...

Xlib: connection to "localhost:10.0" refused by serverXlib: MobaXterm X11 proxy: unable to connect to forwarded X server: Network error: Connection refused

Graphical installers are not supported by the VM. The console mode will be used instead...

===============================================================================MIDAS Product Family (created with InstallAnywhere)-------------------------------------------------------------------------------

Preparing CONSOLE Mode Installation...

===============================================================================Introduction------------

It is strongly recommended that you close any other running programs beforecontinuing with this installation.To proceed to the next step, click Next. If you want make changes to dataentered in a previous step, click the Previous button.

PRESS <ENTER> TO CONTINUE:

You will now have the possibility to use the Installation of the Software without a GUI (console-based installer) forinstallation or skip it completely.

The easiest way to establish a redirection of the X-Display as a prerequisite for a normal MIDAS installation is toperform the following steps:

• Make sure that an X-Server is running on your workstation

• Connect to the target server, where the actual MIDAS installation is to be performed using ssh with enabled X-forwarding, for example:

# ssh -Y root@midas-srv

• When using a Windows workstation, use putty or similar tools. In that case, X-forwarding must be enabled in theconnection settings. In addition, you must have a local X-Server running on your Windows system.

• After logging on, X-applications should appear on your workstation without any further steps. Test this using forexample the application xclock:

root@midas-srv # xclock

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 51 of 103

Page 57: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Alternatively, the X DISPLAY variable can be set manually as shown in the following example (the example assumesthat MIDAS is to be installed on the HPOM Management Server midas-srv whereas the user is working on the systemworkstation, i.e. the display must be redirected from midas-srv to workstation):

# [root@midas-srv]> DISPLAY=workstation:0 /tmp/install.bin

If needed, allow access on the target workstation workstation by executing this command:

# [user@workstation]> xhost +

To test general X connectivity, execute any X application. For example, open a clock using the command xclock:

# [root@midas-srv]> DISPLAY=workstation:0 xclock

If this test using xclock works correctly, also the MIDAS installer will be able to open the display properly.

5.2.2. Wrong or Unknown HPOM Passwords

During the installation of a MIDAS Backend for HPOM the access parameters to the HPOM database will berequested.Since that information has been entered only once during the installation of HPOM server, often users forget it soonafterwards.The examples in the following section use Oracle as HPOM database implementation. In case of other databasesoftware being used please adapt the information provided correspondingly.Also, review the HPOM server installation log file /var/opt/OV/log/OpC/mgmt_sv/installation.log.verbose (HPOM >=9.x only). Locate the section containing the phrase „ORACLE_PW_OPC_OP …“_ for the password specified during theHPOM server installation.If you cannot remember the password of the database user opc_op, the following tests may help to determine it.

Testing Passwords of Database Users

First determine the related database parameters on the HPOM Management Server by executing the followingcommand:

MIDAS 4.12Installation Guide

52 of 103 © Copyright 2018, Worldline Germany GmbH

Page 58: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

# cat /etc/opt/OV/share/conf/ovdbconfDB_VENDOR OracleDB_NAME openviewDB_RELEASE 11.2.0DB_TIME_STAMP "Thu Aug 2 17:22:55 CEST 2012"DB_USER ovdbORACLE_SID openviewORACLE_HOME /opt/oracle/product/11.2.0ORACLE_BASE /opt/oracleDBA_USER oracleDATA_DIR /opt/oradataCREATE_DIR /opt/oracle/admin/openview/createINDEX_DIR /opt/oradataADMIN_DIR /opt/oracleDIAG_DIR /opt/oracleOS_AUTHENT_PREFIXCHARACTER_SET AL32UTF8BASE_DATA_TS_SIZE 25BASE_INDEX_TS_SIZE 5DATA_TS_SIZE 25INDEX_TS_SIZETEMP_TS_SIZE 2DATA_TS_EXTENT_SIZE 2DATA_TS_MAX_SIZE 500INDEX_TS_EXTENT_SIZEECHO_CMD /bin/echo -ePROMPT FALSEDBA_PROGRAM sqlplusChapter 5: Installation Troubleshooting 77OV_USER ovdbDBA_LOGFILE /var/opt/OV/share/log/sqlplus_logORACLE_BASE_REV 11ORACLE_SECOND_REV 2DB_CREATED TRUENLS_LANG american_america.AL32UTF8ITO_DATADIR /opt/oradataITO_INDEXDIR /opt/oradataSQLNET_ALIAS ov_net

Log on to the HPOM Management Server (or use the su command) as user oracle and try to connect to the databaseusing the user-password combination to be tested as shown in the example below.After logging on as user oracle, make sure that the environment variables ORACLE_SID and ORACLE_HOME matchthe entries in ovdbconf. Next use the sqlplus command as shown in the example below:

# su oracle$oracle> export ORACLE_HOME=/opt/oracle/product/11.2.0$oracle> export ORACLE_SID=openview$oracle> /opt/oracle/product/11.2.0/bin/sqlplusSQL*Plus: Release 11.2.0.1.0 Production on Thu Dec 18 14:31:30 2014Copyright (c) 1982, 2009, Oracle. All rights reserved.Enter user-name: opc_opEnter password:[...]Connected to:Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit ProductionWith the Partitioning, OLAP, Data Mining and Real Application Testing optionsSQL> exit

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 53 of 103

Page 59: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

If the sqlplus command displays the response „Connected“, the tested user name and password are correct; if not,try again.

Do not use the sqlplus command to login like this (or similar): Enter user-name: opc_op as sysdbaIn this case any password can be entered (even a wrong one) and login is still possible, so this isno real check.

The sqlplus command as described in the example above should work with all Oracle versions supported by HPOMand MIDAS.

Updating the Password of the Database User opc_op

If it is not possible to find out the password of the required database user, the password has to be changed to a newknown value.

Change the password of the database user opc_op only if it is absolutely necessary. For moreinformation about changing this password, also see the HPOM man page about the opcdbpwdcommand.

To change the password of the database user opc_op within the HPOM database, use the HPOM command opcdbpwdby performing the following steps:

• First, create a backup of this file: /etc/opt/OV/share/conf/OpC/mgmt_sv/.opcdbpwd.sec

• Then change the password of the database user opc_op using the command:

# /opt/OV/bin/OpC/opcdbpwd -set

Using the opcdbpwd command is the only supported way to change the password of the HPOMdatabase user. Do NOT use SQL commands like alter user. The command opcdbpwd also updatesHPOM’s internal security file opcdbpwd.sec with the new authentication values, which is essentialfor HPOM to continue to work properly after the password change.

After the database password has been changed, make sure to update the MIDAS configuration. Run the followingcommand on the MIDAS Backend server:

# /opt/midas/midas.sh password -u ovodb -a -p <new_password>

The same password as in the opcdbpwd command has to be used as „<new_password>“. After the password changewith the MIDAS configuration restart the MIDAS server using the following command:

# /opt/midas/midas.sh clean# /opt/midas/midas.sh start

The password of the database user opc_report cannot be changed using the command opcdbpwd, instead use theappropriate sqlplus commands, for example:

SQL> alter user opc_report identified by {new password};SQL> commit;

Since the database user opc_report is not used by the HPOM server, there is no need to update the password inHPOM.If the database user opc_report has been configured in MIDAS, the corresponding password must be updated in

MIDAS 4.12Installation Guide

54 of 103 © Copyright 2018, Worldline Germany GmbH

Page 60: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

MIDAS as well using the same midas.sh password command as explained above.

5.2.3. MIDAS GUI - No Login

After a completed installation of the MIDAS Web Application, it must be possible to login to MIDAS using the defaultusername (admin) and password (secret). If this fails with an error message (see MIDAS GUI log-in error) check thefollowing possible reasons.

Note, that the situation of such a log-on error immediately after an installation slightly differs from similarproblems at a later time after MIDAS has been used for a while (for example wrong password, empty user role) - seethe troubleshooting section of the MIDAS Administration and Configuration Guide.

If the MIDAS GUI does not load at all possibly your MIDAS Web Application server hasn’t fully started yet. Pleasewait for another 30-60sec. There should be no more activity in the log file #/opt/midas/logs/servicemix.log

If the MIDAS GUI loads into your web browser but you cannot log on, check the following:

• try to restart the MIDAS Web Application by executing the following command on the MIDAS Web Applicationserver:

# /opt/midas/midas.sh clean# /opt/midas/midas.sh start

This command will restart the MIDAS Web Application after performing a cleanup of all log and run-time files,forcing the application to unpack again all necessary run-time files. The output „BUILD SUCCESSFUL“ should beprinted at the end of the command midas.sh clean.Again, wait until the MIDAS Web Application has started completely and there is no more activity in the log file/opt/midas/logs/servicemix.log.

• If the embedded XML database which stores the MIDAS user database wasn’t successfully initialized during theinstallation of the MIDAS Web Application (see Derby database initialization Error), all initial user data may bemissing. Therefore, any login attempt will fail.In this case perform a complete reset of the XML database.

Resetting the MIDAS XML database is only recommended after a fresh installation of theMIDAS software and if logging in is not possible at all. Performing this activity at a later timewill reset the whole user management and backend configuration to the initial state!

To re-initialize the MIDAS XML database the MIDAS Web Application server must be running, i.e. after accessingthe MIDAS URL, a logon screen must appear (see MIDAS GUI log-in error).Perform the following command to reset the MIDAS XML database:

# /opt/midas/midas.sh init force

There is no need to restart MIDAS server processes. The message „BUILD SUCCESSFUL“ should be printed at the end.Afterwards, logging in as the user "admin" with the password "secret" should be possible.

• If the string Not enough licenses left appears in the servicemix.log file on the MIDAS Web Application server, novalid licenses for the MIDAS Webapp are present. Possibly the licenses have expired - however, this should nothappen during the evaluation period (60d) since this period begins with the completed MIDAS installation.Always review the log file /opt/midas/logs/servicemix.logContact the product support team to obtain new licenses.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 55 of 103

Page 61: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Figure 39. MIDAS GUI log-in error

Finally, if none of these solutions helps, contact the product support team.

5.2.4. Installation Log Files

The MIDAS installation procedure logs all activities into the log file MIDAS_Product_Family_Install_<Timestamp>.log inthe installation root directory /opt/midas.This log file will contain information about installation steps and the values of variables used during installation. Inaddition, any output created by the various scripts called during the installation process will be logged into this file,for example, to determine the Oracle installation directory or to create configuration elements.To redirect the MIDAS Installer debug output to the console on a UNIX operating system set the environmentvariable LAX_DEBUG to true, before starting the installer, for example:

# LAX_DEBUG=true /tmp/install.bin

In this example, the variable setting LAX_DEBUG=true will be applied to the MIDAS Installer binary /tmp/install.bin.

If you redirect the output to the screen by setting the LAX_DEBUG variable, the MIDAS installer willnot create the log file MIDAS_Product_Family_Install_<Timestamp>.log.

If there is a persistent problem with the MIDAS installation, send the installation log file and the support.zip to theproduct support team.The support.zip contains all important logfiles and configuration data of the MIDAS application.To create the support.zip execute the following command:

# /opt/midas/midas.sh support

The command midas.sh only exists if at least the MIDAS software installation phase wassuccessful.

MIDAS 4.12Installation Guide

56 of 103 © Copyright 2018, Worldline Germany GmbH

Page 62: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

6. Installing in a HA ClusterThis chapter provides additional information about installing MIDAS as a high-availability (HA) cluster application.

6.1. OverviewBoth MIDAS Backend servers and MIDAS Web Application servers can be installed as a HA cluster application. Theinformation in this section applies to both MIDAS Backend servers and MIDAS Web Application servers as well as„full installations“ (where MIDAS Web Application and MIDAS Backend are on the same system) with specialconsiderations highlighted where applicable.The following topics are covered:

• Cluster Prerequisites

• Installation in a High-Availability Cluster

• Installation Locations in a High-Availability Cluster

• Server Startup and Shutdown in a High-Availability Cluster

• Server Settings

6.2. Cluster PrerequisitesThe set of HA cluster software and their versions supported by MIDAS are described in chapter Installing MIDAS.The term “HA resource group” (referred to as „HARG“ in the following text) used within this section equals the term“HA package” defined with HP MC ServiceGuard. Independently from the actual HA set-up the following generalguidelines apply:

• MIDAS can be installed into an existing HARG, for example on MIDAS Backend servers for HPOM into the HARGrunning the HPOM server. Alternatively, MIDAS can be installed into it‘s own HARG.

The configuration of the actual HARG is not covered in this MIDAS manual. Please refer to yourIT administrator and/or the HA software documentation.

• MIDAS must be installed into a shared filesystem that has to be present on the active physical node of the HARG.The installation of the MIDAS server must be performed on the HARG’s active physical node. Since MIDASresides on a shared file system, there is no need to install MIDAS on subsequent physical nodes.However, some configuration steps are required as described below.

• The virtual name and IP address of the HA resource group containing a MIDAS server must be resolvable withthe name service (DNS, /etc/hosts, …) at all locations where needed, e.g. by end-users accessing the MIDAS webinterface.

• The virtual host name of the HA resource group must be specified during installation of MIDAS and whenlogging into MIDAS with a web browser.

• If the MIDAS Web Application and/or MIDAS Backend modules are installed as HA cluster application and eitherthe MIDAS VCS subsystem or SSH-based transfer from/to the MIDAS server is desired, the OS user midas must becreated on all physical nodes where the MIDAS HARG may run.The home directory of the OS user midas must be configured as the MIDAS installation directory, just as in a non-cluster MIDAS installation.For details regarding creating the OS user midas see Create Local OS User for MIDAS.

6.3. Installation in a High-Availability ClusterDepending on the actual MIDAS architecture, the effective set-up may differ, but the following two scenarios can beused as examples.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 57 of 103

Page 63: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

6.3.1. MIDAS Full Installation

A MIDAS full installation contains both the MIDAS Web Application and MIDAS Backend component on the samesystem. In conjunction with HPOM and using the already existing HPOM HARG, the resulting MIDAS may look as inthe following example:

Figure 40. Full Installation

MIDAS is installed into to a dedicated filesystem mounted to /opt/midas . This file system is defined as resourcebelonging to the HARG ov-server, i.e.the MIDAS server is configured as application resource into the same HARG ov-server as the HPOM Management Server itself.

The names of the physical nodes in the example are: “oahu” and “maui”. Currently the HARG is active on “maui”. Incase of a fail-over the entire HARG including the HPOM Server and the MIDAS server moves to “oahu”. The virtualhost name of the HARG is “hawaii”. The virtual IP address of hawaii must be resolvable (using DNS or whatevername service is in place).

In case of a failover this name and address moves along with the HARG from “maui” to “oahu”. The MIDAS WebApplication HTTP port (default 9662) is allocated by the running MIDAS Web Application module. MIDAS GUIsessions always connect to the MIDAS Web Application using the URL http://hawaii:9662.This way, the physical node, on which the MIDAS Web Application is actually running, is completely transparent tothe user.

6.3.2. MIDAS Pure Backend

Similarly to the scenario described in section MIDAS Full Installation, MIDAS Backend servers can be installedindividually into a HARG. For simplicity, again the existing HARG as already used by the HPOM Management Server.However, in the following example scenario, the MIDAS Web Application is installed on a separate node fiji:

MIDAS 4.12Installation Guide

58 of 103 © Copyright 2018, Worldline Germany GmbH

Page 64: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Figure 41. Pure MIDAS Backend installation

In this scenario, MIDAS users connect to the MIDAS Web Application on the physical node fiji. When registering theMIDAS Backend hawaii, the virtual hostname hawaii of the HARG running both the HPOM Management Server andthe MIDAS Backend must be configured.

6.3.3. Other Scenarios

Besides the two example scenarios presented above, the following other scenarios are conceivable:

• MIDAS Backend and HPOM Management Server run in a separate HARGs.In this case the configuration of the MIDAS HARG must contain a dependency on the HPOM HARG to guaranteethat the MIDAS HARG switches along with the HPOM HARG. The MIDAS Backend must run on the same physicalnode as the HPOM Server processes.

• HPOM database runs in a separate HARG or remotely anywhere else.Since both HPOM and the MIDAS Backend connect to the database using network access, only the databaseconnection must be configured correctly by referring to the virtual hostname of the HARG running the databaseand no further impact on the MIDAS installation exists.

• Run a separate MIDAS Web Application as HARG.In this scenario, an individual HARG must be configured. All other statements regarding the use of MIDAS as aHARG apply.

6.4. Installation Locations in a High-Availability ClusterMIDAS must be installed only once per HA cluster into a shared filesystem. The MIDAS software has to be installedon the currently active physical node.Make sure that the shared filesystem is available on the active physical node of the HARG. All MIDAS binary anddata files are stored in that shared file system and only a few extra steps are necessary on the other physical nodesforming the MIDAS HARG as described below.

6.4.1. Installing MIDAS on the Active Cluster Node

To actually install MIDAS on the active cluster node of the target HARG, perform a regular installation as describedin Installing MIDAS. Make sure that the prerequisites as described in Cluster Prerequisites are fulfilled.During the installation of MIDAS as a HA cluster application, it is crucial to specify the virtual host name of theHARG representing the virtual host where MIDAS runs.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 59 of 103

Page 65: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

If the name of the virtual host is e.g. “hawaii” enter “hawaii” in the Server Hostname field.

6.4.2. Setup of MIDAS on Inactive Cluster Nodes

Although MIDAS does not need any installation on inactive physical nodes, it is necessary to perform the followingsteps on each subsequent physical node on which the MIDAS high-availability resource group (HARG) might run, forexample, in the event of a failover:

• Configure the MIDAS to automatically start and stop whenever the MIDAS HARG starts or stops on a physicalnode. This topic is covered in section Server Startup and Shutdown in a High-Availability Cluster.Create the OS user midas unless neither VCS nor SSH are used on the MIDAS server. For details see Create LocalOS User for MIDAS.

• Copy the MIDAS installation inventory files as described in Installer Inventory File from the active physical nodeto all other physical nodes.

6.5. Server Startup and Shutdown in a High-Availability ClusterNormally, during a HA cluster failover (switch), the MIDAS server shuts down and starts along with the MIDASHARG itself. The configuration of this behavior depends on the HA set-up and the possibly existing HPOM version asdescribed in the following section:

• If the MIDAS server is installed as separate HARG, i.e. does not share a HARG with the HPOM Server, integratethe standard MIDAS start/stop script midas.sh into the HARG start/stop script.

• If the MIDAS server is installed into a HARG used by a HPOM Server version 9.x the ovc -start and ovc -stopintegration can be used and no manual configuration for start-up and shut-down is necessary.

Register MIDAS using ovcreg so that it is started after a cluster switch together with the HPOM Server processes byperforming the following steps on each inactive physical node:

• Copy the file /opt/midas/conf/ovo/midas.xml from the active node to the inactive node, for example into /tmp.

• Then, on the inactive node, run the following command:

# /opt/OV/bin/ovcreg -add /tmp/midas.xml

• If the MIDAS server is installed into a HARG used by a HPOM Server version 8.x the ovstart and ovstopintegration can be used and no manual configuration for start-up and shut-down is necessary.Register MIDAS using ovaddobj so it is started after a cluster switch together with the HPOM Server processes byperforming the following steps on each inactive physical node:

◦ Copy the file /opt/midas/conf/ovo/midas_ovo.lrf from the active node to the inactive node, for example into/tmp.

◦ Then, on the inactive node, run the following command:

# /opt/OV/bin/ovaddobj /tmp/midas_ovo.lrf

6.6. Server Settings in a High-Availability ClusterTo log into a MIDAS GUI with the MIDAS Web Application running within a high-availability resource group (HARG),enter the name of the virtual host in the URL.

MIDAS 4.12Installation Guide

60 of 103 © Copyright 2018, Worldline Germany GmbH

Page 66: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

7. UninstallationThis chapter covers the removal of MIDAS.

7.1. OverviewThe information provided covers the following areas:

• Downgrading MIDAS

• Removing MIDAS

7.2. Downgrading MIDASGenerally, downgrading MIDAS installations using the MIDAS uninstallation program is not supported. This coversboth the scenario of removing product components (for example, converting a full installation to a pure MIDASBackend by removing the MIDAS Web Application) as well as attempting to convert a MIDAS Administrator server toa MIDAS Configurator.To perform any downgrade, for example as described above, perform a side-by-side installation as described inMultiple parallel MIDAS installations, then remove the original installation if desired.

7.3. Removing MIDASBefore starting the Uninstaller, stop the MIDAS server processes:

# /opt/midas/midas.sh stop

Make sure that no MIDAS-related processes are running before starting the removal process. If necessary, stop orkill these processes. Check the running processes by:

# ps -ef | grep -i midas

If MIDAS is still running the output of the ps command (showing two processes) looks like in the following example:

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 61 of 103

Page 67: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

root 21720 21645 0 08:32 pts/1 00:00:00 grep -i midas

root 5465 1 5 09:51 pts/0 00:00:09 /opt/midas/jre/bin/java -classpath root 25296 1 0Sep09 ? 00:12:23 /opt/midas/jre/bin/java -classpath /opt/midas/conf:/opt/midas/lib/classworlds-1.0.1.jar -Xms64m -Xmx512m -server -DbesId=midas411_server -Dmidas.instance=.-Dclassworlds.conf=/opt/midas/conf/servicemix/servicemix.conf -Dservicemix.home=/opt/midas-Djava.endorsed.dirs=/opt/midas/lib/endorsed -Dexist.home=/opt/midas -Dartifactory.home=/opt/midas-Djavacvs.multiple_commands_warning=false -DEnv-CVS_EXE=[cvspath]-Dorg.mortbay.jetty.Request.maxFormContentSize=10000000-Dorg.apache.cocoon.settings=/opt/midas/conf/cocoon.properties -Dcom.bes.servicemix.shutdown.timeout=500-Dsun.net.inetaddr.ttl=0 -Djava.util.logging.manager=com.bes.itm.util.JCLLogManager-XX:+PrintCommandLineFlags -Djava.net.preferIPv4Stack=false -Dnet.sf.ehcache.skipUpdateCheck=true-Dorg.terracotta.quartz.skipUpdateCheck=true -Dom.home=/opt/OV -Djava.security.egd=file:/dev/./urandom-Dbiz.red_soft.olap.resource_catalog=/opt/midas/conf/olap/resources -Djava.awt.headless=true-XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -Xdebug -Xnoagent -Djava.compiler=NONE-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005 -XX:MaxPermSize=512m-Djava.library.path=/opt/midas/bin:/opt/midas/lib/ovo:/opt/midas/lib/midas:/opt/OV/lib/hpux32:/opt/OV/lib64:/opt/OV/lib:/opt/oracle/product/11.2.0/lib:/opt/oracle/product/11.2.0/lib32:/opt/OV/www/htdocs/classesorg.codehaus.classworlds.Launcherroot 25297 1 0 Sep09 ? 00:01:54 /bin/sh /opt/midas/bin/watchdog.sh -p 25296 -c/opt/midas/midas.sh

The uninstallation program to remove MIDAS is located in the MIDAS home directory. This utility is present as GUIbased uninstallation or console based one. All explanations regarding X connectivity as in Display Problems applyfor the GUi based procedure as well.Start the Uninstaller using the following command:

# /opt/midas/Uninstall_MIDAS/uninstall.bin

After a few moments the GUI of the Uninstaller should appear (see Uninstallation Welcome Screen).

Figure 42. Uninstallation Welcome Screen

Even though the MIDAS uninstallation GUI offers both the options of a complete and partial de-installation (seeUninstallation modes) only complete uninstallations are supported (an partial de-installation effectivelyrepresenting a downgrade of the current MIDAS instance).

MIDAS 4.12Installation Guide

62 of 103 © Copyright 2018, Worldline Germany GmbH

Page 68: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Figure 43. Uninstallation modes

Attempting to perform a partial uninstallation will result in an error dialog which cannot be ignored (see Partial de-installations not supported).

Figure 44. Partial de-installations not supported

Click Uninstall to start the uninstallation procedure.

Figure 45. Uninstallation Completion

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 63 of 103

Page 69: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

After finishing the uninstallation there will be some files and folders left in the /opt/midas directory:

[root@meggy midas]# ls -l /opt/midastotal 6332drwxrwxr-x 6 root root 4096 Aug 17 10:01 confdrwxrwxr-x 6 root root 4096 Aug 17 10:01 data-rw-rw-r-- 1 root root 5 Aug 17 09:51 midas411_server_..pid.WD-rwxrwxr-x 1 root root 1059 Aug 16 14:32 midas_env.sh-rwxr-xr-x 1 root root 6453771 Aug 17 10:01 MIDAS_Product_Family_Uninstall_08_17_2017_10_01_48.log

Review the remaining files and carefully remove the installation directory /opt/midas including all contentsmanually.

Generally, it is not recommended to remove the MIDAS installation in any other way than usingthe MIDAS uninstallation program as described above. If MIDAS has been removed without usingthe Uninstaller, it is recommended to also remove the installation inventory file as described inInstaller Inventory File.

MIDAS 4.12Installation Guide

64 of 103 © Copyright 2018, Worldline Germany GmbH

Page 70: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

8. Updating or Upgrading MIDASThis chapter covers the scenarios of updating and upgrading MIDAS.

8.1. OverviewThe information provided in this section covers the following areas:

• Updating MIDAS

• Upgrading MIDAS

• Updating/Upgrading MIDAS in a HA Cluster

Note the following definitions:

Update

You want to install a more recent version of the product.Updating MIDAS describes a situation where you are already using MIDAS with a lower product version than theproduct version that you intend to install.

Upgrade

You want to add product components to an existing MIDAS installation of the same version.

Always perform a MIDAS backup of the existing MIDAS instance before performing any updateor upgrade installation. You can perform the backup automatically as part of the update/upgradeprocess or manually, for example, using the following command:

# /opt/midas/midas.sh backup

Remember to copy the resulting backup file to a save location.

8.2. IntroductionThis section describes the different scenarios for updating or upgrading your MIDAS installation. MIDAS 4.12supports direct update installations from MIDAS ≥4.9.

8.3. Updating MIDASIf you are running MIDAS 4.10.0 or later, you can update to the latest version of MIDAS automatically. For example,you can update a MIDAS 4.10.0 installation to the latest version of MIDAS by performing the steps described in thissection.

When updating to MIDAS 4.12, new license files must be requested from the Worldline Germanysupport team. Older licenses will stop working 60 days after the update!

An update installation replaces the old installation with the current installation. However, theold configuration settings are preserved and migrated, if necessary.

For update installations, the following data is automatically migrated:

• The XML database of MIDAS Web Application serversThe migrated data contains the following components:

◦ MIDAS user model

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 65 of 103

Page 71: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

◦ registered MIDAS Backend servers

◦ MIDAS package data (MIDAS Administrator only)

• The MIDAS Derby database (all MIDAS servers)The migrated data contains the following components:

◦ Auditing data

◦ Outage data (MIDAS Outage Manager only)

• The MIDAS data directory /opt/midas/data

• The MIDAS configuration directory /opt/midas/confThe migrated data contains the following components:

◦ MIDAS Licenses

◦ HTTPS certificates and keystores

◦ SSH keys

◦ Jobs

◦ Task definitions

• The MIDAS update installation does NOT migrate non-standard MIDAS customizations such as the followingcomponents:

◦ Custom Web assemblies and service assemblies

◦ Custom skins (files are backed up though)

◦ Customizations in groovy scripts, for example needed for MIDAS Synchronizer

◦ Any modifications made to properties files located in /opt/midas/conf

◦ /opt/midas/data/query are ignored

◦ Custom service assemblies and data assemblies are ignored

You must manually migrate customized items after a completed update installation. In case of questions contact theMIDAS support team.

Make sure that only the installer inventory file midas*.properties exists that matches thecurrently installed MIDAS version. See Installer Inventory File for details.

8.3.1. Backing up Old Installer Inventory Files

It is recommend to backup the MIDAS installer inventory files described in Installer Inventory File. These files maybe necessary to downgrade back to the existing version.

8.3.2. Preserving Customizations

During an update the MIDAS installer automatically detects any customizations, displays them in a list in a popupdialog, and on confirmation, stores them in a separate folder for future use. You can restore them at a later date, ifrequired.The updated MIDAS instance consists of standard MIDAS software installation, and you must migrate anycustomizations made to the original MIDAS instance manually to the updated/upgrades installation.

8.3.3. Running the MIDAS 4.12 Installer

This section describes the steps to perform during an update installation to MIDAS 4.12. To update MIDAS from anearlier supported version (see Introduction) to the current MIDAS version 4.12, you perform the following high-levelsteps:

• Perform a regular MIDAS installation as described in Installing MIDAS.The MIDAS 4.12 installer will detect an already existing MIDAS installation by checking the installation inventory

MIDAS 4.12Installation Guide

66 of 103 © Copyright 2018, Worldline Germany GmbH

Page 72: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

files as described in Installer Inventory File. If an existing MIDAS 4.x installation is detected, for example, MIDAS4.11, two options exist, as illustrated in Existing Installation detected (update possible): "Update or "Install".

If the Update function is not displayed on a MIDAS system running a MIDAS version supported for updating or theinstallation inventory files are missing. This may happen under the following circumstances:

• MIDAS was installed on systems configured in a high-availability (HA) cluster while the MIDAS High AvailabilityResource Group (HARG) was running on another physical node.

• The installation inventory files have been removed.

In either case, try to recover the missing files from a backup (in the HA cluster, the missing inventory files may existon another cluster node - see also Updating/Upgrading MIDAS in a HA Cluster. If the installation inventory files canbe recovered, you must cancel and re-start the MIDAS 4.12 installation.Otherwise a MIDAS update installation will not be possible. In this case, you must perform a standard MIDASinstallation from scratch as described in Installing MIDAS and manually migrate data. If an existing MIDASinstallation is detected, the MIDAS installer displays the available options, as illustrated in Existing Installationdetected (update possible), and prompts you to choose how to continue.

Figure 46. Existing Installation detected (update possible)

• To update an existing MIDAS installation, click the „Update“ button as described in the following sections (the„Install“ function will perform a standard MIDAS installation without any data migration).

• The installer asks if you want to perform a backup as part of the update process, as illustrated in Choose theBackup Mode.

Figure 47. Choose the Backup Mode

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 67 of 103

Page 73: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

If you choose the “Backup now” option illustrated in Choose the Backup Mode, the automatic backup creates thefollowing files in the target directory you specify:Data file Backup_MIDAS<VERSION>_<TIMESTAMP>.<EXT>- <VERSION> - A number indicating the currently installed version of MIDAS, for example, MIDAS 4.12- <TIMESTAMP> - The date and time at which the backup archive was created, for example, 2018_08_17_031732(03:17:33 on the 17th of August 2018)- <EXT> - A platform specific file extension for the backup data archive, for example .tar.gz (Linux/Solaris), .zip(Windows).

• Log file log_Backup_MIDAS<VERSION>_<TIMESTAMP>.log

As soon as the automatic backup has been finished, the following screen will be displayed (Automatic Backup). Justconfirm with "OK" and trigger the update.

Figure 48. Automatic Backup

If you want to restore a MIDAS installation from the backup file, you must replace the folder ofthe existing MIDAS installation with the contents of the backup file. The name of the MIDASinstallation directory must be identical before and after the restore operation. You must notchange the name of the MIDAS installation folder during a restore operation.

8.4. Upgrading MIDASUpgrading is the process of installing additional MIDAS components to an existing MIDAS installation. For example,if MIDAS is already installed you can upgrade it by adding MIDAS Synchronizer, MIDAS Debugger, MIDAS OutageManager or MIDAS Administrator.

For upgrade installations you must use the MIDAS installer version that matches the currentlyinstalled MIDAS version unless you want to perform an update installation at the same time. Inthat case you must install into a different installation directory.

To upgrade an existing MIDAS system (for example, to install missing MIDAS Server Tiers or Add-ons, perform thefollowing steps.Launch the MIDAS 4.12 installer (i.e. the MIDAS installer version that matches the currently installed version).During that installation session, perform the following steps:

• The first installer screens are identical to a standard installation (see Installing MIDAS).

• The installer panels "Querying the installation path" and "HA cluster information" do not appear - thisinformation will be adopted from the existing MIDAS instance.

• The MIDAS installer will detect that MIDAS is already installed on the system and will offer to either perform an

MIDAS 4.12Installation Guide

68 of 103 © Copyright 2018, Worldline Germany GmbH

Page 74: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

"Upgrade" or "Exit" the installer, as illustrated in Upgrade: Exit Selector. To install missing MIDAS Server Tiers oradd-ons click "Upgrade".

Figure 49. Upgrade: Exit Selector

• Choose the MIDAS product options/add-ons to be added as explained in Product Selection. The installer informsyou that it is in upgrade mode. Already installed components are marked and greyed out; components not yetinstalled can be selected as desired, as illustrated in Upgrade: Exit Selector.

Figure 50. Product selection in upgrade mode

• During the subsequent installer steps only those screens will be displayed that match the missing MIDAScomponents. To find out about all options in the Product Selection window, refer to the main installation chapterstarting with Product Selection.

8.5. Updating/Upgrading MIDAS in a HA ClusterTo update or upgrade MIDAS instances installed as a high-availability (HA) cluster generally works the same way asfor non-clustered MIDAS instances with the following exceptions:

• MIDAS installation inventory filesThe MIDAS installer must be able to locate the installer inventory files as described in Installer Inventory File.These files will be created during an installation. However, since MIDAS installs only once per HA cluster into ashared file system, normally the installer inventory files exist only on that physical cluster node where MIDAShas been installed originally.To make the MIDAS update find the installer inventory file you must either

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 69 of 103

Page 75: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

◦ Switch MIDAS to the physical cluster node where the installer inventory files are already present

◦ Copy the installer inventory files to the physical cluster node where MIDAS currently runs

• MIDAS start-upThe MIDAS start-up mechanism must be adapted on ALL physical cluster nodes where the MIDAS instance mayrun. Note that the startup method can no longer be changed as part of the update/upgrade process.

MIDAS 4.12Installation Guide

70 of 103 © Copyright 2018, Worldline Germany GmbH

Page 76: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

9. Post Installation TasksThis chapter covers the post installation tasks that we recommend you perform.

9.1. OverviewThe information in this section covers the following areas:

• Installing MIDAS Licenses

• Setting an XML Database Administrator Password

• Java Memory Parameters

• Oracle RAC Cluster Support

• Disabling the MIDAS Web Application’s HTTP Port (9662)

• MIDAS Versioning

• Using HTTPS

• Using SSH

• Using External Authentication Software

9.2. IntroductionAfter a completed MIDAS installation, a couple of subsequent steps may be needed to improve the operation of yourMIDAS environment. The following section lists such potential enhancements:

• It is strongly recommended to set a password for the user admin within the MIDAS XML database:Setting an XML Database Administrator Password

• The MIDAS performance may be improved by tune some Java JRE parameters:Java Memory Parameters

• To use MIDAS within an Oracle RAC cluster environment:Oracle RAC Cluster Support

• Enforcing secure HTTPS access to the MIDAS Web Application and disable HTTP:Disabling the MIDAS Web Application’s HTTP Port (9662)

• To use the MIDAS versioning capabilities:MIDAS Versioning

• Using secure HTTPS communication between a MIDAS Web Application and a MIDAS Backend:Using HTTPS

• To perform secure SCP/SSH file transfers between MIDAS servers:Using SSH

9.3. Installing MIDAS LicensesDuring a MIDAS installation, evaluation licenses for all installed MIDAS components will be generated. Theselicenses are valid for 60 days starting from the time of the installation. To install productive licenses after acompleted MIDAS installation, obtain licenses by containing MIDAS product support and install them as described inthe MIDAS Administration and Configuration Guide.

9.4. Setting an XML Database Administrator PasswordThe MIDAS Web Application contains an embedded XML database used to store MIDAS user configuration andvarious other information. This XML database is implemented using the eXist technology (http://exist.db.org) as

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 71 of 103

Page 77: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

dedicated Web Application with an own web-based user interface.This UI can be accessed after logging on with a user name/password.The installation of the MIDAS Web Applicationperforms all configuration of the XML database automatically with the exception that it is not possible to protect thedefault user admin with a password.To fix this potential security issue, manually set this password as described in the following section.

The XML database exists only on the MIDAS Web Application server. All steps described in thischapter have to applied on the system acting in this role.

• Open the following URL in a web browser (midas-webapp stands for the hostname of your MIDAS WebApplication server): http://midas-webapp:9662/exist

• On the left hand side of the eXist UI, click the entry "Administration" → "Admin".

• Log in using:— Username: admin— Password: default is „admin" (see XML Database Login Screen)

Figure 51. XML Database Login Screen

• After logging in, select "User Management" from the left column. Enable the checkbox for the user admin andpress "Edit" (Edit User "admin").

Figure 52. Edit User "admin"

• Enter a new password for the user "admin". Confirm by pressing the "Change" button Setting the Password.Leave all other fields untouched.

MIDAS 4.12Installation Guide

72 of 103 © Copyright 2018, Worldline Germany GmbH

Page 78: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Figure 53. Setting the Password

• Leave the eXist UI by selecting "Logout".

After setting the password in the XML DB itself, configure this password in encrypted form in in the MIDAS WebApplication by performing the following steps:

• Update the password in the MIDAS configuration using the following command:

# /opt/midas/midas.sh password -u xmldbadm -a -p [new password]

• Restart the MIDAS Web Application:

# /opt/midas/midas.sh clean# /opt/midas/midas.sh start

9.5. Java Memory ParametersTo improve performance of your MIDAS installation, it is highly recommended to tune the Java JRE memoryparameters used by MIDAS. If the system‘s hardware is sufficiently powerful and has enough RAM, it isrecommended to increase the maximum memory setting to maxmemory = 1024MB or higher (for the MIDASBackend the maxmemory is 512MB by default).

Tuning the JRE memory parameters applies to all MIDAS servers - both MIDAS Web Applicationand MIDAS Backend servers. Most important though is the MIDAS Web Application because ofmemory-consuming operations like for example building search indexes or generatingdocumentation.

To change the configuration setting limiting the RAM utilization of the JRE running MIDAS edit the file:/opt/midas/conf/servicemix/wrapper.conf

and configure the property maxmemory, for example:

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 73 of 103

Page 79: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

# Maximum Java Heap Size (in MB)# alternative for wrapper.java.additional.<n>=-Xmxmaxmemory=2048

Restart the MIDAS server to activate the new parameters:

# /opt/midas/midas.sh restart -clean

Do NOT decrease the value below the initial setting – this will negatively impact performanceand MIDAS may not function properly anymore.

9.6. Oracle RAC Cluster SupportThe MIDAS Backend Server for HPOM directly reads data from the HPOM SQL database. If HPOM is configured touse a database in an Oracle RAC cluster, the MIDAS must be updated after the MIDAS installation has completed.

The MIDAS Web Application does not access the HPOM database. The configuration described inthis section is only needed on MIDAS Backend Servers for HPOM.

Contact your Oracle database administrator for the correct virtual hostnames, port and SID. Then, configure theMIDAS database access as in the following example.In this section we use an example assuming that the Oracle RAC cluster consists of the following servers andsettings:

• physical hostname: ora1phys

• virtual hostname: ora1virt

• physical hostname: ora2phys

• virtual hostname: ora2virt

• Listener Port: 1521

• HPOM database instance SID: openview

The following MIDAS configuration files must be updated with the correct Oracle RAC JDBC connection string:

/opt/midas/conf/opccfg.properties

/opt/midas/conf/ovoappl.properties

/opt/midas/conf/ovoconfig.properties

/opt/midas/conf/ovoinstall.properties

/opt/midas/conf/ovodistrib.properties

/opt/midas/conf/ovonode.properties

Depending on the set of installed MIDAS products, possibly not all of these configuration filesexist.

Each of these configuration files contains a JDBC connection string which looks like in the following non-RACexample:

ovodb.url=jdbc:oracle:thin:@(DESCRIPTION=(FAILOVER=ON)(ADDRESS_LIST=(LOAD_BALANCE=ON)(ADDRESS=(PROTOCOL=TCP)(HOST=virtual-hostname1)(PORT=xxxx))(ADDRESS=(PROTOCOL=TCP)(HOST=virtual-hostname2)(PORT=xxxx)))(CONNECT_DATA=(SERVICE_NAME=SID)))

With our example the JDBC connection string in each configuration file must look like this:

MIDAS 4.12Installation Guide

74 of 103 © Copyright 2018, Worldline Germany GmbH

Page 80: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

ovodb.url=jdbc:oracle:thin:@(DESCRIPTION=(FAILOVER=ON)(ADDRESS_LIST=(LOAD_BALANCE=ON)(ADDRESS=(PROTOCOL=TCP)(HOST=ora1virt)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=ora2virt)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=openview)))

Enter the host names, port and SID matching your environment. You MUST specify the virtualhost names.

Restart the MIDAS server to activate the changes:

# /opt/midas/midas.sh clean# /opt/midas/midas.sh start

9.7. Disabling the MIDAS Web Application’s HTTP Port (9662)To access the MIDAS GUI in a web-browser, two options exist:

• unencrypted access http://midas-webapp:9662

• encrypted access https://midas-webapp:9663

with „midas-webapp" standing for the MIDAS Web Application and assuming that during installation of the MIDASWeb Application the default ports 9662 and 9663 have been confirmed.If custom MIDAS Web Application ports have been specified, use these in the following instructions.

To enforce the usage of HTTPS when accessing the MIDAS Web Application, the HTTP port 9662 can be disabledcompletely by binding port 9662 to localhost (IP 127.0.0.1).Precisely, HTTP access to port 9662 is still possible, but not from any other system than the local MIDAS WebApplication server.

The instructions described in this chapter only apply to the MIDAS Web Application server.

To implement this change the following steps have to be applied on the MIDAS Web Application system while theMIDAS Web Application is up and running:

• Edit the file /opt/midas/conf/jetty.xml

In this file locate the following block:

<!-- default http connector -->

In this block, remove the comments around the host property (for example) and specify localhost as value:

<!--<property name="host" value="192.168.123.159"/>-->

so the resulting line looks like this:

<property name="host" value="localhost"/>

If this line is missing, please add it. The resulting block must look like this:

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 75 of 103

Page 81: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

<!-- default http connector --><bean class="org.mortbay.jetty.nio.SelectChannelConnector"><property name="host" value="localhost"/><property name="port" value="9662"/><property name="headerBufferSize" value="12000"/>

• Edit the file /opt/midas/conf/config.properties

Change the property hostname to localhost, so the resulting configuration block looks like this:

....vendor = Worldline Germany GmbHbackend = todd_serverhostname = localhostserver.port = 9661

Depending on the set of installed MIDAS products, further configuration files have to be modified. If the statedconfiguration files are present, replace the originally configured host name of the MIDAS Web Application withthe value localhost as shown in the following examples:

• Edit the file /opt/midas/conf/association.properties

Change the property xmldb.dbUrl as in the following example:

xmldb.dbUrl=xmldb:exist://localhost:9662/exist/xmlrpc/db/

• Edit the file /opt/midas/conf/backend.properties

Change the property xmldb.dbUrl as in the following example:

xmldb.dbUrl=xmldb:exist://localhost:9662/exist/xmlrpc/db/

• Edit the file /opt/midas/conf/package.properties

Change the properties xmldb1.dbUrl and xmldb2.dbUrl as in the following example:

xmldb1.dbUrl=xmldb:exist://localhost:9662/exist/xmlrpc/db/xmldb2.dbUrl=xmldb:exist://localhost:9662/exist/xmlrpc/db/

• Edit the file /opt/midas/conf/pkgdef.properties

Change the property xmldb.dbUrl as in the following example:

xmldb.dbUrl=xmldb:exist://localhost:9662/exist/xmlrpc/db/

• Edit the file /opt/midas/conf/search.properties

Change the properties xmldb.dbUrl and search.url as in the following example:

xmldb.dbUrl=xmldb:exist://localhost:9662/exist/xmlrpc/db/search.url=http://localhost:9662/solr/

• Edit the file /opt/midas/conf/usermgmt.properties

MIDAS 4.12Installation Guide

76 of 103 © Copyright 2018, Worldline Germany GmbH

Page 82: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Change the property xmldb.dbUrl as in the following example:

xmldb.dbUrl=xmldb:exist://localhost:9662/exist/xmlrpc/db/

• Please exactly follow the procedure described below:

◦ Edit the file /opt/midas/conf/backend_local.xml

At the beginning of the configuration file check line 4 with the XML tag <hostname> as in the followingexample:

<?xml version="1.0" encoding="UTF-8"?><backend xmlns:do="http://www.openadaptor.org/" do:type="backend"><name do:type="String" xml:space="preserve">todd_server</name><hostname do:type="String" xml:space="preserve">todd</hostname>

Write down the original hostname. Replace the hostname (here "todd") with "localhost" so the resulting linelooks like this:

<hostname do:type="String" xml:space="preserve">localhost</hostname>

If there are registered MIDAS Backends, those will be listed also in the file backend_local.xml. DoNOT modify the hostname property there. Only edit line 4 as described above.

• Immediately after this modification run the following command:

# /opt/midas/midas.sh ant -f run.xml intern.solr_http

This command should terminate with a message "BUILD SUCCESSFULLY".

◦ Important: Re-edit the file /opt/midas/conf/backend_local.xml

Now change back line 4 from "localhost" to the original hostname.

<?xml version="1.0" encoding="UTF-8"?><backend xmlns:do="http://www.openadaptor.org/" do:type="backend"><name do:type="String" xml:space="preserve">todd_server</name><hostname do:type="String" xml:space="preserve">todd</hostname>

◦ Restart the MIDAS Web Application to activate the changes:

# /opt/midas/midas.sh clean# /opt/midas/midas.sh start

◦ Verify locally on MIDAS Web Application server, that the HTTP port (default 9662) is bound to localhost(127.0.0.1), for example on Linux:

# netstat -an | grep 9662tcp 0 0 *127.0.0.1*:9662 0.0.0.0:* LISTEN

◦ Test all MIDAS functions

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 77 of 103

Page 83: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

10. MIDAS VersioningThis section covers the installation and configuration of the version-control system that MIDAS uses to manageversions of your configuration objects.

10.1. OverviewMIDAS supports creating and maintaining a version history of all configuration objects managed using MIDAS.The product component implementing this capability is referred to as "Version Control System" (VCS) and isdesigned as a layer capable of different actual revision management software tools.Examples for such tools are CVS (Concurrent Versioning System), SVN (Subversion) or Clearcase.

MIDAS only supports CVS as a Version Control System!

Using MIDAS VCS is entirely optional. During MIDAS installation (see Installing MIDAS) the installing user mayenable or disable VCS globally. If enabled, the actual CVS software must be present. For licensing reasons, the CVSsoftware itself is not part of the MIDAS product but must be rather downloaded and installed by the end user.

This chapter covers all issues related to installing and configuring the MIDAS VCS subsystem and the CVS software:

• Introduction

• Download Locations For CVS

• CVS Binary Installation

• Configuring MIDAS Versioning

10.2. IntroductionCVS (Concurrent Versioning System) is a widely distributed, popular software to maintain a revision history ofsource data. Usually this applies to programming source code but can be used for any other data as well.Within the MIDAS context, CVS will be used to maintain a revision history of configuration objects managed usingMIDAS, such as HPOM configuration data.MIDAS already contains all related functionality, but the CVS software itself must be installed manually.

Within MIDAS, all VCS-related functions are performed on the MIDAS Web Application server.Therefore, all statements made in this chapter apply to the MIDAS Web Application server only. Itis not necessary to install CVS on pure MIDAS Backend systems.

CVS stores data in a "Repository". MIDAS supports local or remote CVS repositories, by default, a local CVS repositorywill be created during installation of a MIDAS Web Application server. In this scenario, also the CVS software itselfmust be present on the MIDAS Web Application server (in case of a remote CVS repository this is not necessary).For simplicity, it is recommended to install the CVS software before MIDAS and specify the location of the CVSexecutable correctly when installing the MIDAS Web Application.Alternatively, the configuration of MIDAS needs to be updated later.

10.3. Download Locations For CVSFor UNIX platforms, most open-source software can be downloaded as pre-compiled installable packages from someporting center or is available with a standard OS media kit. Observe run-time dependencies, which have to bedownloaded and installed before. The following table lists download locations where the CVS software may beobtained for the corresponding platforms:

Table 4. Download Locations

MIDAS 4.12Installation Guide

78 of 103 © Copyright 2018, Worldline Germany GmbH

Page 84: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

OS Download Location Installation Method

HP-UX http://hpux.connect.org.uk/ swinstall

Solaris http://www.sunfreeware.com pkgadd

Linux Typically included in the Linuxdistribution

rpm

The general home page of the CVS project is http://www.nongnu.org/cvs. Please review this page for documentation,examples and all other kinds of resources.

10.4. CVS Binary InstallationThis section explains particular installation hints for the CVS software on the different operating systems. Theinformation covers the following topics:

• Using Standard CVS on HP-UX, Solaris or Linux

10.4.1. Using Standard CVS on HP-UX, Solaris or Linux

Download the CVS software from the location stated in Download Locations and use the native installation methodto install CVS on the target system. The listed download locations provide a standard CVS implementation. No extraconfiguration steps are necessary.

10.5. Configuring MIDAS VersioningThis section describes how to configure the MIDAS VCS subsystem. This ranges from enabling/disabling versioningin MIDAS, changing the time/date format to defining single or common version repositories, and so on.

Only CVS is supported as an implementation of the VCS subsystem. All VCS related configurationhas to be done on the MIDAS Web Application system.

The information covers the following areas:

• Enabling/Disabling VCS

• Alternative CVS Repositories

• Time and Date Formats

• Backend Mapping Mode

10.5.1. Enabling/Disabling VCS

The MIDAS versioning subsystem can be disabled completely by setting the property cvs.enabled to false in the file/opt/midas/conf/vcs.properties:

cvs.enabled=false

After changing this setting, the MIDAS Web Application needs to be restarted:

# /opt/midas/midas.sh restart

If disabled, all VCS-related operations in the MIDAS GUI will fail with a corresponding error reporting that VCS hasbeen disabled.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 79 of 103

Page 85: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

10.5.2. Alternative CVS Repositories

By default, MIDAS uses a local CVS repository created during installation of the MIDAS Web Application. This defaultrepository is located in data/repository relative to the installation directory,i.e. for example /opt/midas/data/repository.The following options are supported:

• Using a Non-Standard Local CVS Repository

• Using a Remote CVS Repository

Using a Non-Standard Local CVS Repository

During installation of the MIDAS Web Application the location of the VCS data repository can be specified. Bydefault, this is /opt/midas/data/repository, or on Windows systems, C:\midas\data\repository. Choose any otherlocation if desired.Alternatively, to move the VCS data repository to a different location at any time after a completed MIDASinstallation, perform the following steps:

1. Edit the file /opt/midas/conf/vcs.properties

Update the line defining the CVS repository, for example:

cvs.cvsRoot=:local:/data/vcsrepo

2. Edit/Check the file /opt/midas/conf/config.properties

Make sure that the setting for cvs.repository matches the new location, for example:

cvs.repository = /data/vcsrepo

3. If needed, copy the existing MIDAS VCS data repository directory (and all sub-directories) to the new location.

4. Restart the MIDAS Web Application

# /opt/midas/midas.sh clean# /opt/midas/midas.sh start

Using a Remote CVS Repository

MIDAS supports remote CVS repositories using the connection methods pserver and ssh. The referred remote CVSserver must be configured to allow the desired access. Both methods can be used without installing CVS softwarelocally on the MIDAS Web Application system.To use a remote CVS repository perform the following steps:

1. Edit the file /opt/midas/conf/vcs.properties

Update the setting cvs.cvsRoot to the appropriate value as explained below. Also, refer to the CVS documentationabout the syntax and possible values.For the connection methods SSH and pserver a user name and password for accessing the remote repository arerequired. These two parameters have to be configured in the vcs.properties file as shown in the followingexample. Encrypt the password using the command:

# /opt/midas/midas.sh password -u <username> -p <password_to_encrypt>

as described in the main MIDAS Administration and Configuration Guide in section "Changing Passwords".

MIDAS 4.12Installation Guide

80 of 103 © Copyright 2018, Worldline Germany GmbH

Page 86: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

For example, if the the user name is igo and the encrypted password is B52ABA9B198F9DCDA422C3BCA1B896BA,configure the following settings:

cvs.user=igocvs.password=B52ABA9B198F9DCDA422C3BCA1B896BA

2. Restart the MIDAS Web Application

/opt/midas/midas.sh clean/opt/midas/midas.sh start

Remote CVS Using the pserver Method

To use a remote CVS server with the connection method pserver, configure the setting cvs.cvsRoot in the filevcs.properties like in the following example:

cvs.cvsRoot=:pserver:midas@malta:/repo/midas

The MIDAS Web Application contains an embedded CVS client which implements a standard CVS protocol.Therefore, besides of a correct cvsRoot and a user/password setting, no further configuration on the MIDAS WebApplication is needed.

Remote CVS Using the ssh Method

The MIDAS VCS subsystem supports remote CVS access using SSH. For example, using the built-in SSH protocol withthe repository path /repo/midas on host malta the resulting CVSROOT string is

cvs.cvsRoot=:ext:malta:/repo/midas.

The same embedded SSH client as described in chapter SSH in MIDAS - Overview is used when accessing a remoteCVS repository using SSH. Make sure that the user configured as cvs.user in vcs.properties is able to access theremote server using SSH. Remotely the command configured in conf/servicemix/wrapper.conf will be executed inserver mode, for example

java_additional="${java_additional} -DEnv-CVS_EXE=${MIDAS_HOME}/bin/cvs"

results in /usr/bin/cvs server being executed remotely using SSH.

10.5.3. Time and Date Formats

The date format used in the MIDAS GUI to display the time stamps in the VCS revision history can be customized.The default date format is yyyy-MM-dd HH:mm:ss resulting in an output like in the following example Date Format:

Figure 54. Date Format

To change the date format, add the property cvs.dateFormat in the vcs.properties file, for example:

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 81 of 103

Page 87: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

# vi /opt/midas/conf/vcs.propertiescvs.dateFormat=dd.MM.yyyy HH:mm:ss

For details about the possible formatting variables (like HH for the hour), refer tohttp://docs.oracle.com/javase/8/docs/api/java/text/SimpleDateFormat.html.

10.5.4. Backend Mapping Mode

By default, separate directories exist in the VCS data repository on the MIDAS Web Application for the differentHPOM Backends. That means that configuration items with the same name are versioned in different locations anddo not share a version history.

In some cases, e.g. when a test and production server share the same configuration, it might be desirable to have acommon version history between all or some MIDAS Backend servers. The Backend mode setting can help achievingthis. The list below shows all available mapping modes:

Table 5. Backend Mapping Mode

Mode Description Additional Parameters

separate default mode, all Backends are versioned separately none

all all Backends are versioned into one directory, its defaultname is "all"; configurable

allBackend

group a group of Backends is versioned into a commondirectory, whereas others can be separate or in othergroups

BackendGroupResource

By default, in mode separate, configuration items are stored in different locations (nothing has to be configured inthis case) and the CVS repository structure looks like this:

/opt/midas/data/repository/config/<server_identifier>/ovo/…

All Backend Mode

In order to map all configuration items of all Backends into a common directory (one version history) use the allBackend mode:

# vi /opt/midas/conf/vcs.propertiesvcs.BackendMode = all

Within the CVS repository, the shared backend can be assigned a name, for example "production". Configure thisname in the vcs.properties file, for example:

# vi /opt/midas/conf/vcs.propertiesvcs.allBackend = production

Then, in the CVS repository the created directory structure will look like this:

# /opt/midas/data/repository/config/production/ovo/policy/...

The MIDAS Web Application must be restarted to activate the modification:

MIDAS 4.12Installation Guide

82 of 103 © Copyright 2018, Worldline Germany GmbH

Page 88: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

# /opt/midas/midas.sh clean# /opt/midas/midas.sh start

Group Mode

To group multiple MIDAS Backends (for example, test and production) into a common group for versioning use thegroup mode. To configure this mode, edit the file vcs.properties as shown in the following example :

# vi /opt/midas/conf/vcs.propertiesvcs.BackendMode = groupvcs.BackendGroupResource=file:conf/vcs.xml

The actual MIDAS Backend groups can be defined in the MIDAS GUI as described in the following example:

• Select "Servers" → "All Server Groups", Select all Server Groups.

Figure 55. Select all Server Groups

• From the dropdown menu at the bottom of the server list select "Add Server Group"

• Enter a group name and description for the VCS Server group Add Server Group name and description. Makesure to enable the checkbox labelled [X] Is VCS Group

Figure 56. Add Server Group name and description

• Assign the servers which should be put into the newly created VCS Server Group Assign to Server Group

Figure 57. Assign to Server Group

• Select the desired MIDAS servers to be assigned in the selector box and press OK.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 83 of 103

Page 89: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Figure 58. Select servers to be assigned

• Again select menu "Servers" → "All Servers (Grouped)". Deploy this MIDAS Backend group configuration using"Deploy Server Group Configuration", Deploy server group configuration

Figure 59. Deploy server group configuration

This procedure groups the MIDAS Backends "beslin03.bes-intern.com_server" and "marge_server" into the group"VCS Servers". In the CVS repository the resulting directory structure looks like in the following example:/opt/midas>/data/repository/config/VCS Servers/ovo/… Subsequently in this example, all VCS operations on MIDASBackend "beslin03.bes-intern.com_server" and "margee_server" will share this CVS repository.

10.5.5. Author Tagging

To list and track the name of each MIDAS user who has checked in an object into MIDAS version control. Authortagging can be enabled or disabled in the configuration file (default is enabled): /opt/midas/conf/vcs.properties byconfiguring the setting vcs.authortagging, for example:

vcs.authortagging=true

If enabled, the MIDAS user who performed the check-in operation will be listed in the column "Author", AuthorTagging. If disabled, the name midas will be listed in the "Author" column no matter which actual MIDAS user hascreated a VCS revision.The MIDAS Web Application must be restarted to activate this modification:

# /opt/midas/midas.sh clean# /opt/midas/midas.sh start

MIDAS 4.12Installation Guide

84 of 103 © Copyright 2018, Worldline Germany GmbH

Page 90: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Figure 60. Author Tagging

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 85 of 103

Page 91: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

11. Using HTTPSThis section covers the steps required to configure MIDAS to use secure HTTP (HTTPS). Within MIDAS, HTTPS can beused to secure communication in the following scenarios:

• Between the MIDAS Web Application and a Web browser

• Between the MIDAS Web Application and the MIDAS Backend, unless both instances exist in the same process onthe same system (the so-called"Full installation")

This chapter covers the internal MIDAS communication between MIDAS Web Application and MIDAS Backend only.For information regarding HTTPS in relation to web browsers, please see the MIDAS Administration andConfiguration Guide.

11.1. OverviewBy default, communication between the MIDAS Web Application and MIDAS Backend servers uses HTTP. Since HTTPis not secure, it is possible to use encrypted communication using HTTPS, HTTPS Communication. To enable securecommunication using HTTPS between the MIDAS Web Application and one or more MIDAS Backends HTTPScertificates need to be exchanged and imported on each involved MIDAS server.

Figure 61. HTTPS Communication

The following instructions define how to configure HTTPS communication between the MIDAS Web Application andone or more MIDAS Backends.The information in this section covers the following areas:

• Prerequisites

• HTTPS Setup

11.2. PrerequisitesCommunication between MIDAS Web Application and MIDAS Backends uses either HTTP or HTTPS - never both inparallel. In either case, the server port of the MIDAS Backend server is the same (configurable, default 9661). Thesame setting (either HTTP or HTTPS) must be selected on both sides of the communication relationship. Normallythis happens:

• for the MIDAS Backend (i.e. the MIDAS server acting as HTTP server) during MIDAS installation (see CommonPort Settings).This setting can be verified by reviewing the file /opt/midas/conf/backend_local.xml which contains a setting:

<secure do:type="Boolean">true</secure>

+ A value of true represents HTTPS enabled.

• for the MIDAS Web Application (i.e. the MIDAS server acting as HTTP client) while adding/modifying MIDASBackend(s) in question (see Registering MIDAS Backend).

MIDAS 4.12Installation Guide

86 of 103 © Copyright 2018, Worldline Germany GmbH

Page 92: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Make sure, both settings configure equally HTTP or HTTPS. To use HTTPS, in addition HTTPS certificates must beexchanged as described in the following section.

11.3. HTTPS SetupThe HTTPS certificates used in MIDAS are standard X.509 certificates. For convenience, during MIDAS installation,on each MIDAS server a self-signed HTTPS certificate will be generated that can be used for MIDAS HTTPScommunication. Alternatively, any other custom HTTPS certificates can be used as well (see the MIDASAdministration Guide). The following section explains the certificate exchange using the default MIDAS certificatesand an example with two systems:

MIDAS Web Application server: toddMIDAS Backend HPOM server: meggy

To exchange the MIDAS HTTPS certificates, perform the following steps:

• The certificate file of the local MIDAS server already exists in /opt/midas/conf/<ServerID>.cer (in this examplethe file name would be todd_server.cer and meggy_server.cer).If that certificate file is not present for whatever reason, it can be manually exported as presented in thefollowing example:

root@todd> # keytool -export -keystore {MIDAS_HOME}/conf/servicemix/truststore_endpoint.jks -aliasmeggy_server -file /tmp/meggy_server.cer

The -alias option always requires the MIDAS server identifier as a value as shown in the exampleabove.

• Transfer the certificate file /opt/midas/conf/meggy_server.cer to the target MIDAS server todd, e.g. into thedirectory /tmp (using scp, ftp, and so on). Do not modify the contents of this certificate in any way.

• On todd import the meggy CA certificate (since the default MIDAS certificates are self-signed, they are at thesame time CA certificates) into the MIDAS truststore using the following command (type as one single line):

root@todd # /opt/midas/jre/bin/keytool -import -alias meggy_server -keystore/opt/midas/conf/servicemix/truststore_endpoint.jks -file /tmp/meggy_server.cer

Enter keystore password: .....Owner: CN=meggy_serverIssuer: CN=meggy_server[...]Trust this certificate? [no]: yesCertificate was added to keystore

Answer the question whether to trust the certificate with yes.

When asked for the password to access the truststore, the default password is: password

• Restart MIDAS on todd:

todd # /opt/midas/midas.sh cleantodd # /opt/midas/midas.sh start

• Now perform the same steps on the MIDAS Web Application server todd.

• Transfer the file /opt/midas/conf/todd_server.cer from todd to meggy into /tmp.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 87 of 103

Page 93: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

• On meggy import the todd CA certificate into meggy’s truststore. Answer the question whether to trust thecertificate with yes.Please note, that the command needs to be one single line:

meggy # /opt/midas/jre/bin/keytool -import -alias todd_server -keystore/opt/midas/conf/servicemix/truststore_endpoint.jks -file /tmp/todd_server.cer

Enter keystore password: .....Owner: CN=todd_serverIssuer: CN=todd_server[...]Trust this certificate? [no]: yesCertificate was added to keystore

• Restart MIDAS on meggy:

meggy # /opt/midas/midas.sh cleanmeggy # /opt/midas/midas.sh start

MIDAS 4.12Installation Guide

88 of 103 © Copyright 2018, Worldline Germany GmbH

Page 94: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

12. Using SSHThis section covers the configuration and enablement of communication in MIDAS using the Secure Shell (SSH).

12.1. SSH in MIDAS - OverviewMIDAS provides the capability to conveniently transfer data between MIDAS servers (e.g. MIDAS Web Applicationand MIDAS Backend systems). MIDAS supports the following low-level mechanisms for this data transfer:

• embedded FTP

• embedded SSH

• external SSH

FTP requires no setup/configuration at all but is considered as insecure, whereas SSH is secure but both SSH-variants require some manual configuration steps which are described in this chapter.To use SSH, the communicating MIDAS servers must be configured in a way that the SSH client can connect to theSSH server without any user interaction. This is accomplished by using public-key authentication.Every MIDAS server contains an SSH client and SSH server component based on the open-source technologies jsch(http://www.jcraft.com/jsch) and j2ssh (http://sourceforge.net/projects/sshtools). This embedded SSH client willalways be used independently from the chosen SSH server method (embedded or external).From a security perspective, both SSH server variants are equally secure.Using an external SSH server is favorable, if SSH is already in place as established communication mechanism - inthis case no additional communication ports must be opened. If there is no SSH server present on the MIDASserver(s), the embedded SSH server requires less configuration effort.

Independently from the SSH server method, the roles "SSH client" and "SSH server" describe only the direction inwhich a connection will be established during runtime in the MIDAS GUI, the direction of the actual data flow willbe controlled by the GUI user by choosing either the "Push" or "Pull" transfer method.It is not mandatory to set up a bidirectional SSH-trust between two MIDAS servers, rather the SSH setup must matchthe GUI usage during runtime. For example, if a GUI user transfers data from MIDAS server "A" to "B" in "Push"mode and initiates this operation on MIDAS server "A", then server "A" will act as SSH client whereas "B" as SSHserver (in "Pull" mode the SSH communication channel will be opened in the reverse direction, i.e. "A" is SSH server,while the effective data flow will be the same). The distinction between "Pull" and "Push" model as described aboveis intended to support data transfers through firewalls between MIDAS servers.

The two SSH-Server possibilities supported by MIDAS, along with common information applying to both models, areexplained below:

• Common SSH set-up

• Embedded SSH Server

• External SSH

• Custom SSH keys

12.2. Common SSH set-upThis chapter describes the set-up applicable to both the embedded SSH server and the external SSH server as usedin MIDAS.

12.2.1. Prerequisites

The following conditions must be fulfilled:

• The OS user midas must exist on all MIDAS servers where a transfer is performed. The home directory of thatuser midas must be set to the MIDAS installation directory (default /opt/midas).

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 89 of 103

Page 95: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

• The OS user midas must have a password. Otherwise, SSH file transfers will fail. That password will not actuallybe used by MIDAS but rather SSH requires that the user has a password.

• SSH-based transfer must be enabled on all involved MIDAS servers as explained in chapter Transfer Methodusing either of the following methods:

◦ during MIDAS installation

◦ by performing the SSH-related steps that are normally done during the MIDAS installation. You can enableSSH-based transfer with the following command:

# /opt/midas/midas.sh ant -f conf/ant/admin.xml change_ssh -Denabled=true

12.2.2. Configuring SSH

The main task of configuring an embedded SSH server for MIDAS is to enable public-key-based authentication,which basically requires an exchange of public keys.

Initial Setup

During the MIDAS installation default key pairs are automatically generated (if the installing user has enabled SSHtransfer) which have to be exchanged to allow a non-interactive connection. The generated key files are located in/opt/midas/conf/sshd (/opt/midas must be the $HOME directory of the local OS user midas) with the name id_dsa forthe private key and id_dsa.pub for the public key. DSA is used as default encryption method. Goal of theconfiguration described below is to register the public key of one MIDAS server (acting as SSH client) as authorizedon another MIDAS server (acting as SSH server).

Verification

The following command can be used to verify SSH connectivity (also at any time later), for example with MIDASserver todd acting as SSH client and MIDAS server meggy acting as SSH server:

# root@todd> ssh -i /opt/midas/conf/sshd/id_dsa -p 10022 midas@meggy

Option -p <port> specifies a non-standard SSH port and is only necessary with an embedded SSH server on meggy(with an external SSH server on meggy just omit this option).The embedded MIDAS SSH-server uses by default 10022 unless a different value has been supplied duringinstallation.If successful, the ssh comand must not request a password

The very first time you use the ssh command as shown in the example above, you will be askedwhether to accept the host key of the target SSH server (you must confirm this), for example:

# root@todd> ssh -i /opt/midas/conf/sshd/id_dsa -p 10022 midas@meggyThe authenticity of host ‚meggy‘ (...) can‘t be established.RSA key fingerprint is ...Are you sure you want to continue connecting (yes/no)?

12.3. Embedded SSH ServerEvery MIDAS server contains an embedded SSH server component that implements the standard SSH2 protocol. Toenable and use this embedded SSH server, perform the steps described below. However, first see the commoninformation in Common SSH set-up. The following example describes the setup required for an SSH-based transferusing an embedded SSH server on the target MIDAS server:

MIDAS 4.12Installation Guide

90 of 103 © Copyright 2018, Worldline Germany GmbH

Page 96: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

MIDAS Web Application server: todd (acting as SSH client)MIDAS Backend server: meggy (acting as SSH server)

todd meggy

/opt/midas/conf/sshd/ /opt/midas/conf/sshd/

id_dsa id_dsa

id_dsa.pub id_dsa_todd.pub

authorization.xml authorization.xml

• Copy the file id_dsa.pub from todd to meggy (after renaming it!).

Do not overwrite the original file id_dsa.pub on the target system!

• Add a reference to the copied public key file id_dsa_todd.pub to the file authorization.xml on meggy (the MIDASserver acting as SSH server):

# root@meggy> vi /opt/midas/conf/sshd/authorization.xml

• Add the bold line:

<?xml version="1.0" encoding="UTF-8"?><!-- Sshtools User Authorization File --><AuthorizedKeys><!-- Enter authorized public key elements here --><Key>/opt/midas/conf/sshd/id_dsa.pub</Key>*<Key>/opt/midas/conf/sshd/id_dsa_todd.pub</Key>*</AuthorizedKeys>

• No restart of MIDAS is necessary.

These steps will enable a SSH-based transfer initiated from todd to meggy, but not vice versa. To also configure SSHin the reverse direction, repeat the same series of steps, just exchange the roles of both systems. Repeat the sameprocedure with any further MIDAS servers as needed.

12.4. External SSHIf a standard SSH solution is already in use, the existing SSH set-up can be adopted by MIDAS. To use an existingexternal SSH server with MIDAS, perform the following steps on the system acting as SSH server.

The SSH functionality must be enabled during the installation of MIDAS as explained in TransferMethod. Otherwise no SSH keys will be generated.

• Disable the embedded MIDAS SSH server (both the embedded SSH server and an external SSH server can not beused in parallel) by setting the property of sshd.enabled to false:

# vi /opt/midas/conf/transfer.properties[...]sshd.enabled=false

• Remove the # in front of the two lines, so the transfer.properties reads the following:

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 91 of 103

Page 97: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

# vi /opt/midas/conf/transfer.properties

[...]transfer.externalSshPort=22[...]transfer.externalSshEnabled=true

◦ SSH transfers are always performed with the target OS user midas. Therefore, that OS user "midas" mustexist on all involved MIDAS servers as described in Common SSH set-up.

• Create the directory .ssh inside /opt/midas

# mkdir /opt/midas/.ssh

• Copy the (already existing) MIDAS Backend’s own public key to .ssh:

# cd /opt/midas# cp conf/sshd/id_dsa* .ssh/

First import the id_dsa.pub file of the local MIDAS server itself into the file authorized_keys:

# cp .ssh/id_dsa.pub .ssh/authorized_keys

• Copy the public key files id_dsa.pub from all MIDAS server acting as SSH client to the local system acting as SSHserver while renaming the file (for example, the public key file from MIDAS server todd should be namedid_dsa_todd.pub). Import all these external public keys likewise, for example from the MIDAS server todd:

# cat /tmp/id_dsa_todd.pub >> .ssh/authorized_keys

Repeat this procedure for each required MIDAS server acting as SSH client.

• Subsequently, set the correct file and directory ownership by executing the following commands:

# chown -R midas:sys /opt/midas

◦ Set the file access rights like in the following example:

# chmod 750 /opt/midas# chmod 700 /opt/midas/.ssh# chmod 640 /opt/midas/.ssh/authorized_keys# chmod 640 /opt/midas/.ssh/id_dsa.pub# chmod 600 /opt/midas/.ssh/id_dsa

• Restart MIDAS by executing:

# /opt/midas/midas.sh clean# /opt/midas/midas.sh start

MIDAS 4.12Installation Guide

92 of 103 © Copyright 2018, Worldline Germany GmbH

Page 98: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

If the procedure described above has been performed on a MIDAS Backend server, which is notat the same time MIDAS Web Application, the MIDAS Backend configuration needs to bereloaded. In the MIDAS GUI open the menu Menu → Servers → List all and choose "Force Reloadof Backends" in the displayed server list.

12.5. Custom SSH keysOn systems acting as SSH client, always an embedded SSH client will be used independently of whether the targetSSH server is embedded or not. The generated keys from /opt/midas/conf/sshd will always be used. If SSH wasenabled during MIDAS installation, no additional setup is required. If desired, custom keys can be used instead ofthe default keys. To use custom SSH keys, copy the custom DSA key files to /opt/midas/conf/sshd on the MIDASservers acting as SSH clients. Register the same custom keys at the target SSH servers as described in External SSH.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 93 of 103

Page 99: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

13. Using External Authentication SoftwareThis section describes additional, external authentication software products that can be integrated in MIDAS anddescribes how to configure the software to suit the demands of your environment.

13.1. OverviewThe information in this section covers the following area:

• PAM integration

• LDAP Integration

13.2. Authentication SoftwareAuthentication of MIDAS users happens inside the MIDAS Web Application server part, to which the user’s webbrowser connects. With the current product version, MIDAS supports authentication using LDAP, LDAPS, ActiveDirectory Server or any authentication service which can be integrated into PAM.

Authentication covers only the process of validating the user account with a password. It doesnot include any authorization control (user’s capabilities). Authorization is implementedexclusively in MIDAS by defining MIDAS user roles.

Therefore, whenever setting up a new MIDAS user, make sure that the account exists in both MIDAS and theexternal authentication system. Furthermore, make sure that the MIDAS user is member of at least one MIDASgroup which has at least one MIDAS user role assigned.To use an external authentication software like LDAP or PAM in MIDAS additional software (for example, the LDAPclient) may be required on the MIDAS Web Application. Install and configure this software as needed. More detailsare presented below. LDAP authentication can be used in two variants - directly or via PAM. On UNIX systems,where PAM is normally available by default, PAM offers two advantages over direct LDAP:

• the same set-up can be used for MIDAS and the OM Java GUI (both just refer to the same PAM set-up, just withdifferent service names) and possibly even OS-level authentication - therefore this configuration has to be doneonly once

• the configuration within MIDAS is simpler

In case of problems with either method, please review the troubleshooting sections in the MIDAS Administration andConfiguration Guide.

MIDAS authentication always happens on the MIDAS Web Application server. All steps describedin this chapter have to applied on the MIDAS system acting in this role.

13.3. PAM integrationTo authenticate midas users through PAM (Pluggable Authentication Modules), no extra software is needed. MIDASalready includes the open-source module jpam (see http://jpam.sourceforge.net for details). However, PAM is just aninterface linking software providing authentication services (like LDAP, Kerberos, UNIX passwd) to consumerapplications like MIDAS. Therefore, possibly software modules (for example, an LDAP client) implementing theactual authentication service may be needed.

To configure MIDAS to use PAM as authentication interface, perform the following steps:

1. Decide, which authentication method to use. If needed, install required software modules and configure them.Test the authentication service standalone, i.e. outside of the MIDAS context, for example using command linetools.

MIDAS 4.12Installation Guide

94 of 103 © Copyright 2018, Worldline Germany GmbH

Page 100: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

2. Configure all MIDAS user accounts in the authentication service.

3. Configure PAM to route MIDAS authentication requests to the desired authentication service. The PAM servicename is midas.

4. Activate the external authentication service in the conf/auth.properties file:

# vi /opt/midas/conf/auth.properties# configuration properties for authentication and authorization components#auth-filter.enabled=falseusermodel-router.authResource=file:conf/auth.xml# eof

5. Switch MIDAS to PAM authentication by configuring the property in the conf/auth.xml file. The file has to looklike this:

# vi /opt/midas/conf/auth.xml<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd"><beans><bean id="targetServices" class="java.util.ArrayList"><constructor-arg><list><value>pam</value><value>usermgmt</value></list></constructor-arg></bean></beans>

6. Deploy the midas-wapam-sa.zip service assembly (command must be typed in one single line):

# cp /opt/midas/assemblies/midas-wapam-sa.zip /opt/midas/deploy

7. Restart the MIDAS Web Application:

# /opt/midas/midas.sh restart

Configuring the actual authentication software depends on this software itself and the OS the MIDAS WebApplication is running on. In the following example, the default authentication mechanism on a Linux system isused.

13.3.1. Authentication Service: UNIX passwd

By default, the default authentication mechanism on Linux is UNIX passwd, which in turn is always available(normally) and there is no need to install and configure anything. If not existing yet, create a user account and setthe password, for example the user igo:

# useradd igo# passwd igoChanging password for igo.New Password: *******Reenter New Password: *******Password changed.

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 95 of 103

Page 101: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Other UNIX-related parameters like home directory or shell are not needed for MIDAS. Configure PAM to routeMIDAS authentication requests to UNIX passwd by configuring the following in /etc/pam.conf (example applies toHP-UX):

[...]midas auth required libpam_unix.so.1midas account required libpam_unix.so.1[...]

For further details like advanced PAM capabilities (for example using multiple and/or optional authenticationservices) refer to the OS-specific PAM documentation.

13.4. LDAP IntegrationMIDAS supports user authentication through direct LDAP (Lightweight Directory Access Protocol). MIDAS uses theopen-source component “Acegi Security System for Spring Project” (see ACEGI_URL) as embedded LDAP client. PAMis not being used in this scenario.

Microsoft Active Directory Server (ADS) also implements LDAP and can be used with MIDAS aswell. All statements below apply unless specifically marked.

Currently, only basic authentication of user accounts is supported. Additional LDAP features like group membershipand so on are not used by MIDAS. To configure LDAP authentication in MIDAS, perform the following steps:

1. Configure all MIDAS user accounts on the LDAP/Active Directory Server.

2. Configure access to the desired LDAP server in the properties file /opt/midas/conf/ldap.properties as explainedbelow.

3. Activate the external authentication service in the conf/auth.properties file:

# vi /opt/midas/conf/auth.properties# configuration properties for authentication and authorization components#auth-filter.enabled=falseusermodel-router.authResource=file:conf/auth.xml

4. Switch MIDAS to LDAP authentication by configuring conf/auth.xml:

# vi /opt/midas/conf/auth.xml<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd"><beans><bean id="targetServices" class="java.util.ArrayList"><constructor-arg><list><value>ldap</value><value>usermgmt</value></list></constructor-arg></bean></beans>

No matter whether LDAP, LDAPS or an Active Directory Server is used, always set the value to “ldap”.

5. Deploy the midas-waldap-sa.zip service assembly:

MIDAS 4.12Installation Guide

96 of 103 © Copyright 2018, Worldline Germany GmbH

Page 102: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

# cp /opt/midas/assemblies/midas-waldap-sa.zip /opt/midas/deploy

6. Restart MIDAS Web Application:

# /opt/midas/midas.sh clean# /opt/midas/midas.sh start

13.4.1. The ldap.properties File

The file ldap.properties contains all configuration for direct LDAP access within MIDAS. First, configure an URLpointing to your LDAP server, for example:

# The LDAP URL# Format: ldap://<host>:<port>/<base dn>ldap.url=ldap://ldap-test:389/dc=bes-intern,dc=com#ldap.url=ldaps://ldap-test:636/dc=bes-intern,dc=com#ldap.url=ldaps://winsrv2008ad:636/dc=worldline-test,dc=org

Both standard-LDAP and ADS can be accessed using secure LDAP (based on SSL). If secure LDAP is desired configureldaps as protocol in the LDAP server URL, for example:

ldap.url=ldaps://ldap-server:636/dc=bes-intern,dc=com

For both secure or unsecure LDAP access, in the next block enter the login credentials, which determine as whoMIDAS makes LDAP queries during runtime:

# Manager DN for loginldap.managerDn=cn=Manager,dc=bes-intern,dc=com#ldap.managerDn=cn=administrator,cn=users,dc=worldline-test,dc=org# Manager password - must be in plain textldap.managerPassword=******

LDAP authentication within MIDAS supports two main modes: BIND_WITH_DN or USER_SEARCH. Choose theappropriate mode depending on your LDAP server set-up and configure the related parameters as described in thefollowing paragraphs.

Standard LDAP and OpenLDAP generally support both modes whereas with ADS the mode USER_SEARCH must beused.

13.4.2. Using LDAP Mode BIND_WITH_DN

With the default mode ldap.authenticationMode=BIND_WITH_DN normally no further configuration changes arenecessary. Leave everything else commented out as shown in the following example:

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 97 of 103

Page 103: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

# The mode which is used for the authentication# Allowed values are:# BIND_WITH_DN:Use the authenticationDnPatterns for identifying a user# USER_SEARCH : Use the authenticationSearchBase and# authenticationSearchFilter for identifying a userldap.authenticationMode=BIND_WITH_DN# The search base for searching users for authentication# This property is used in combination with the ldap.authenticationSearchFilter# and is used e.g. for a Active Directory search#ldap.authenticationSearchBase=CN=Users# The filter for searching users for authentication# This property is used in combination with the ldap.authenticationSearchBase# and is used e.g. for a Active Directory search#ldap.authenticationSearchFilter=(sAMAccountName={0})

13.4.3. Using LDAP Mode USER_SEARCH

To use the USER_SEARCH mode, at least the search base and search filter properties must be set as shown in thefollowing example:

# The mode which is used for the authentication# Allowed values are:# BIND_WITH_DN : Use the authenticationDnPatterns for identifying a user# USER_SEARCH : Use the authenticationSearchBase and# authenticationSearchFilter for identifying a userldap.authenticationMode=USER_SEARCH# The search base for searching users for authentication# This property is used in combination with the ldap.authenticationSearchFilter# and is used e.g. for a Active Directory searchldap.authenticationSearchBase=ou=people# The filter for searching users for authentication# This property is used in combination with the ldap.authenticationSearchBase# and is used e.g. for a Active Directory searchldap.authenticationSearchFilter=(uid={0})

To enable recursive user search set the following configuration parameter:

#searchSubtreeldap.searchSubtree=true

The Overall, the necessary configuration values heavily depend on the actual LDAP server set-up - please consultyour LDAP administrator.

Example: OpenLDAP with USER_SEARCH

The example given earlier for the USER_SEARCH mode at the same time reflects the standard configuration neededfor OpenLDAP:

ldap.authenticationMode=USER_SEARCHldap.authenticationSearchBase=ou=peopleldap.authenticationSearchFilter=(uid={0})

Always doublecheck with your LDAP administrator whether this configuration matches your LDAP server.

MIDAS 4.12Installation Guide

98 of 103 © Copyright 2018, Worldline Germany GmbH

Page 104: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Example: Microsoft ADS

To use an Active Directory Server set ldap.authenticationMode to USER_SEARCH. Depending on the Active DirectoryServer configuration, the login name field also needs to be defined. In our example the search filter attribute iscalled sAMAccountName.

# The mode which is used for the authentication# Allowed values are:# BIND_WITH_DN : Use the authenticationDnPatterns for identifying a user# USER_SEARCH : Use the authenticationSearchBase and# authenticationSearchFilter for identifying a userldap.authenticationMode=USER_SEARCH# The search base for searching users for authentication# This property is used in combination with the ldap.authenticationSearchFilter# and is used e.g. for a Active Directory searchldap.authenticationSearchBase=CN=Users# The filter for searching users for authentication# This property is used in combination with the ldap.authenticationSearchBase# and is used e.g. for a Active Directory searchldap.authenticationSearchFilter=(sAMAccountName={0})

For ADS, secure LDAP configuration is required as described above. Always doublecheck with your LDAPadministrator whether this configuration matches your LDAP server.

13.4.4. Secure LDAP (LDAPS)

Secure LDAP is based on SSL and requires that the LDAP client trusts the LDAP server. To verify the certificatepresented by the LDAP server (and by doing so being certain that the LDAP server can be trusted) the LDAP clientmust access the CA root certificate of the CA that has signed the LDAP server certificate. If that CA root certificateoriginates from a well-known third-party certification authority (like Verisign) and is already included in a standardJRE, no further steps should be necessary (however, this scenario has not been tested). If the CA root certificate isnot part of the JRE, it is necessary to import the CA root certificate into the truststore accessed by the LDAP clientwithin MIDAS. Configure the path to the truststore file and the truststore password as in the following example (inthis example the global MIDAS truststore file is used, alternatively create and use a separate dedicated trustore):

# The path to the truststore for trusted certificates for secure LDAPldap.truststore=conf/servicemix/truststore.jks

# The truststore password for secure LDAPldap.trustPassword=password

Then import the CA root certificate of the LDAP server (in .cer format) using the following command:

# /opt/midas/jre/bin/keytool -import -alias ldapserver_a -keystore/opt/midas/conf/servicemix/truststore.jks -file /tmp/ldap_server.cerEnter keystore password: *******[...]Trust this certificate? [no]: yesCertificate was added to keystore

The default password for the MIDAS truststore is: password

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 99 of 103

Page 105: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Appendix

Software IncludedMIDAS includes software developed by various open-source projects and organizations as listed below. Thecorresponding files and components are copyright to the corresponding organization or vendor and all rightsreserved. The software files and components distributed under the open-source licenses are distributed on an "ASIS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the license of the correspondingproject for specific rights and limitations under the license. Depending on the license, any product derived from theproducts may not be called with the name of the project nor may the name of the project appear in their name,without prior written permission. For written permission, please contact the corresponding project owner byvisiting the corresponding project home page as listed below. We greatly appreciate the work of those projects andtry to contribute as much as possible to some of those projects in order to compensate their contributions.

All license files can be found in the installation directory (./docs/licenses). Furthermore, a full overview of allexternal dependencies and license conditions is also accessible via the Web interface: HELP button → About menu→ External Dependencies. This includes links to all projects.

Project Description URL License

ActiveMQ JMS bus http://www.activemq.org Apache SoftwareLicense 2.0

Ant Java build tool http://ant.apache.org Apache SoftwareLicense 2.0

Ant-Contrib additional optional Ant tasks http://ant-contrib.sourceforge.net Apache SoftwareLicense 1.1

Antlr Java parser generator http://www.antlr2.org BSD-style License

Baekmuk Korean Truetype fonts http://kldp.net/projects/baekmuk BSD-style License

BCEL Apache Jakarta Byte CodeEngineering Library

http://jakarta.apache.org/bcel Apache SoftwareLicense 2.0

BSF Bean Scripting Framework forapplication scripting support

http://jakarta.apache.org/bsf Apache SoftwareLicense 1.1

Cocoon XML-based web publishingframework

http://cocoon.apache.org Apache SoftwareLicense 2.0

Commons reusable Java components (logging,collections, cli, …)

http://jakarta.apache.org/commons Apache SoftwareLicense 2.0

Derby Java embedded database http://db.apache.org/derby Apache SoftwareLicense 2.0

dnsjava Java DNS library http://www.dnsjava.org BSD-style License

Docbook Docbook document format and XSLstylesheets

http://www.docbook.org Docbook License

dom4j Java XML parser http://dom4j.org BSD-style License

Drools Java rules engine http://drools.codehaus.org Drools License

dsmltools DSML LDAP access http://www.dsmltools.org Mozilla Public License

EditArea Javascript web editor http://www.cdolivet.com/editarea Apache SoftwareLicense 2.0

MIDAS 4.12Installation Guide

100 of 103 © Copyright 2018, Worldline Germany GmbH

Page 106: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Project Description URL License

Ehcache Caching library http://ehcache.org Apache SoftwareLicense 2.0

Excalibur Avalon utility libraries http://avalon.apache.org/excalibur Apache SoftwareLicense 2.0

Exist XML database http://www.exist-db.org GNU Library GeneralPublic License 3.0

Fins Cocoon Charting http://cocoondev.org/main/117-cd/29-cd.html

BSD License

Fireflysung Chinese Truetype fonts http://www.study-area.org/apt/firefly-font

Arphic Public License

FOP Java PDF renderer http://xml.apache.org/fop Apache SoftwareLicense 2.0

Forrest XML-based documentationframework

http://xml.apache.org/forrest Apache SoftwareLicense 2.0

FTPServer Java FTP server http://mina.apache.org/ftpserver Apache SoftwareLicense 2.0

FugueIcons

Icon library http://pinvoke.com Fugue Icons License

Gradle Groovy-based build system http://www.gradle.org Apache SoftwareLicense 2.0

Groovy Java-based script language http://groovy.codehaus.org Apache SoftwareLicense 2.0

GWT Web-based GUI framework http://code.google.com/webtoolkit Apache SoftwareLicense 2.0

H2 Embedded single-File Database http://www.h2database.com H2 License 1.0

ICU4C International Components forUnicode

http://www.ibm.com/software/globalization/icu

X.org License

ICU4J International Components forUnicode

http://www.ibm.com/software/globalization/icu

X.org License

j2ssh Java SSH client library http://sourceforge.net/projects/sshtools

GNU Library GeneralPublic License 2.0

Janino Java compiler http://www.janino.net New BSD License

Jasper Tomcat JSP compiler http://tomcat.apache.org Apache SoftwareLicense 2.0

Jasypt Java Simplified Encryption http://http://www.jasypt.org/ Apache SoftwareLicense, Version 2.0

Jaxen XPath library http://jaxen.org Jaxen License (BSD-style)

Jaxup XUpdate library http://klomp.org/jaxup Jaxup License (BSD-style)

JDOM Java XML parser http://www.jdom.org JDOM License

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 101 of 103

Page 107: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Project Description URL License

Jencks Java JCA container http://jencks.codehaus.org Apache SoftwareLicense 2.0

Jetty Java servlet web container http://jetty.mortbay.org/jetty Apache SoftwareLicense 2.0

JFreeChart Java Charting http://www.jfree.org/jfreechart GNU Lesser GeneralPublic License 2.1

JPam Java PAM wrapping library http://jpam.sourceforge.net Apache SoftwareLicense 2.0

mimeutil Java mime-type library http://sourceforge.net/projects/mime-util/

Apache SoftwareLicense 2.0

jRegistryKey

Java Windows registry library http://sourceforge.net/projects/jregistrykey

Open Software License

Jsch Java SSH client library http://www.jcraft.com/jsch Jsch License (BSD-style)

Jsdifflib A Javascript Visual Diff Tool &Library

http://snowtide.com/jsdifflib Jsdifflib License (BSD-style)

Jython Java python interpreter http://www.jython.org Jython License (BSD-style)

Log4j Java logging toolkit http://logging.apache.org/log4j Apache SoftwareLicense 2.0

Lucene Java search engine http://jakarta.apache.org/lucene Apache SoftwareLicense 2.0

MX4J JMX toolkit http://mx4j.sourceforge.net License (BSD-style)

Netbeans CVS Netbeans CVS client library http://javacvs.netbeans.org/library Sun Public License

openadaptor

Java EAI framework http://www.openadaptor.org OpenAdaptor License

opencsv Java CSV library http://opencsv.sourceforge.net Apache SoftwareLicense 2.0

OracleJDBCDriver

JDBC Oracle database access http://www.oracle.com Oracle License

ORO Java regular expression library http://jakarta.apache.org/oro Apache SoftwareLicense 2.0

POI Microsoft document format accesslibrary

http://jakarta.apache.org/poi Apache SoftwareLicense 2.0

Prefuse Java visualization library http://prefuse.org BSD-style license

Quartz Java scheduling library http://www.opensymphony.com/quartz

Apache SoftwareLicense 2.0

Rhino Javascript interpreter http://www.mozilla.org/rhino Mozilla Public License1.1

Sazanami Japanese Truetype fonts http://sourceforge.jp/projects/efont BSD-style License

ServiceMix ESB server http://servicemix.apache.org Apache SoftwareLicense 2.0

MIDAS 4.12Installation Guide

102 of 103 © Copyright 2018, Worldline Germany GmbH

Page 108: MIDAS 4.12: Installation Guide - bes-worldline.com · the HPOM database and the HPOM API. HPOM Agent Driver The HPOM Agent Driver module controls a real HPOM Agent for example by

Project Description URL License

ServingXml XML pipeline library http://servingxml.sourceforge.net Apache SoftwareLicense 2.0

Snmp4j SNMP library http://www.snmp4j.org/ Apache SoftwareLicense 2.0

Smart-GWT Dynamic Web GUI library http://www.smartclient.com/smartgwt

GNU Library GeneralPublic License 3.0

Solr Java search server http://lucene.apache.org/solr Apache SoftwareLicense 2.0

Spring Java application framework http://www.springframework.org Apache SoftwareLicense 2.0

SpringSecurity

Java authentication security library http://projects.spring.io/spring-security/

Apache SoftwareLicense 2.0

StaX Java XML pull parser https://sjsxp.dev.java.net Binary Code LicenseAgreement

TM4J Java topicmap engine http://www.tm4j.org TM4J License

Tuscany Simple data object http://tuscany.apache.org Apache SoftwareLicense 2.0

util.concurrent

concurrency and threading library http://gee.cs.oswego.edu/dl/classes/EDU/oswego/cs/dl/util/concurrent/intro.html

No license

Velocity Template engine http://velocity.apache.org Apache SoftwareLicense 2.0

VMTools XML diff library http://www.vmsystems.net/vmtools VMTools License (BSD-Style)

Xalan Java stylesheet processor http://xml.apache.org/xalan-j Apache SoftwareLicense 2.0

XBean Customized spring XMLconfiguration library

http://xbean.org/ Apache SoftwareLicense 2.0

Xerces Java XML parser http://xml.apache.org/xerces2-j Apache SoftwareLicense 2.0

XIA Ant Xinclude task http://www.jeckle.de/freeStuff/xia GNU Library GeneralLicense 3.0

XML RPC Java XML RPC library http://ws.apache.org/xmlrpc Apache SoftwareLicense 2.0

XML-Security

Java XML security library http://santuario.apache.org/Java/index.html

Apache SoftwareLicense 2.0

XML AntTask

XML manipulation ant task http://www.oopsconsultancy.com/software/xmltask

Apache SoftwareLicense 1.1

MIDAS 4.12Installation Guide

© Copyright 2018, Worldline Germany GmbH 103 of 103