Skip to main content
Close
Hitachi Vantara Knowledge

Install or upgrade Hitachi Ops Center products by using the installer

  1. Last updated
  2. Save as PDF
 

To install, upgrade, or to create a new Hitachi Ops Center system without using the OVA, install the products by using the Common Services installer first and then install one or more products using the product installer.

Child Topics

Workflow for installing and setting up Hitachi Ops Center

 
The general workflow for using the installer for each product is as follows:
Workflow showing the steps for constructing an environment for Hitachi Ops Center products. The steps are: Prepare a management server. Install Common Services and each product. Set up SSL communications. Register the products to Common Services. Log in to the portal. Register a license. Set up Active Directory. Set up a password policy. Finally, set up access controls.

After setting up access control, configure the settings for each product as necessary. For details, see the documentation for each product.

If you are upgrading, the previous settings are preserved. If you upgrade Hitachi Ops Center products that were registered in Common Services, you do not need to configure SSL communication or perform the subsequent steps.

Parent Topic

Preparing the management server

 
Make sure that the management server on which you plan to install Hitachi Ops Center products meets the system requirements.

For the Common Services system requirements, see the Common Services Release Notes. For the system requirements of other Hitachi Ops Center products, see the documentation or Release Notes for each product.

For a complete list of Hitachi Ops Center system requirements, go to the Ops Center documentation site and select Get Started with Ops Center Hitachi Ops Center system requirements.

Note
  • Hitachi Ops Center does not support installing other software products on the management server, but allows for installing software required by corporate policy such as anti-virus programs and third-party monitoring agents. Note that Hitachi Vantara does not take responsibility for or support any interactions between the third-party programs and the Hitachi Ops Center software.
  • When Common Services is installed, the following RPM packages are installed:
    • Amazon Corretto 11
    • PostgreSQL 11

  • Common Services starts the Common Services service by using the postgres user and postgres group created on the management server.

    Configurations where postgres users and postgres groups do not exist on the management server are not supported.

    If the users on the management server are managed by an external authentication server, the Common Services service cannot start when the OS starts.

Make sure there are no conflicts among the following port numbers.

  • Port number used to access Common Services:

    443/tcp (default)

  • Port numbers used for internal communication:

     

    • 20951/tcp
    • 20952/tcp
    • 20953/tcp
    • 20954/tcp
    • 20955/tcp
    • 20956/tcp
    • 20962/tcp
    • 20963/tcp

If necessary, register the port number that is used to access Common Services in the firewall exceptions. For details on how to register firewall exceptions, see the OS documentation.

Parent Topic

Installing or upgrading Common Services

 
To install or upgrade Common Services in an existing environment or to create a Hitachi Ops Center system without using the OVA, install Common Services by using the installer.
Note
  • If you upgrade from version 10.6.0 or earlier to version 10.6.1 or a later, Amazon Corretto 11 will be installed. During the upgrade, Amazon Corretto 8, which was installed with version 10.6.0 and earlier will not be removed. If you no longer need Amazon Corretto 8, remove it by using the rpm command. If you cannot remove the program by using this command, use the rpm command with the --nopreun option specified.

    (Package name of Amazon Corretto 8: java-1.8.0-amazon-corretto-devel)

  • If the Analyzer viewpoint server was deployed by using a version of the OVF earlier than 10.5.1, you cannot use the installer to upgrade Common Services or Analyzer viewpoint on that server. In this case, deploy the newest version of the Analyzer viewpoint OVF to upgrade Analyzer viewpoint and Common Services.

    For details on how to upgrade Analyzer viewpoint, see the Ops Center Analyzer documentation.

Before you begin

Confirm that one of the following settings is configured on the management server installation destination:

  • A DNS server that can be accessed by the management server is set up.
  • The host name is set in the hosts file.

If the system cannot resolve the management server host name, it might take a long time for the Common Services to start.

Procedure

  1. Log in to the management server as the root user.

    If you log on as an ordinary user, use the sudo command to complete the following procedure as the root user.

  2. Run install.sh, which is in the following location in the installation media:

    root-directory-of-installation-media/COMSERV/install.sh

  3. To install Common Services, follow the prompts and specify the required information.

    You must specify the following information during installation:

    • For new installations of Common Services:

       

      • Installation destination for Common Services
        • The default installation destination for Common Services is as follows:

          /opt/hitachi/CommonService

        • User data for Common Services is stored in the following user data directory:

          /var/installation-directory-of-Common-Services

      • Host name (or FQDN) or IP address
        • The host name (or FQDN) or IP address specified in this step is used in the URL for accessing the Hitachi Ops Center Portal. To change the host name (or FQDN) or IP address that is used to access the Hitachi Ops Center Portal, run the cschgconnect command after installation. For details about the cschgconnect command, see Changing the management server host name, IP address, or port number.
        • The management server on which Common Services and other relevant products are installed and the web browser used to access the Hitachi Ops Center Portal must be able to resolve and reach the host name (or FQDN) and IP address.
        • If you specify a host name (or FQDN), specify a value using no more than 128 characters.
        • You cannot specify uppercase characters in the host name (or FQDN). If you do, they are converted to lowercase characters and then registered.
      • Port number of the access URL

        If you install the following products on the same management server, there will be conflicts with the default port number 443. Change the port number so that it does not conflict between the products. If you want to change the port number for Common Services to a number other than 443, we recommend using port number 20950.

        • Hitachi Ops Center Protector (formerly Hitachi Data Instance Director)
        • Hitachi Ops Center Administrator
        • Hitachi Ops Center Analyzer viewpoint
      • Whether access is possible by using an IP address

        Specify whether an IP address can be used to access the Hitachi Ops Center Portal when a host name or FQDN is specified in the access URL.

        • To maintain the default setting of not permitting access by using an IP address, specify y.
        • To permit access by using an IP address, specify n.

          An IP address acquired from the system is automatically set for the access URL.

    • For overwrite or upgrade installations of Common Services:

       

      • Whether to back up the existing Common Services database
      • If yes, the database backup destination
Parent Topic

Installing or upgrading each product

 
You install other products after you install Common Services. For details on the installation procedure, see the documentation for the individual product.

If you complete an upgrade or overwrite installation of an existing product, the installation destination is the same as the current installation destination.

 

NoteIf you upgrade to Hitachi Ops Center Automator or Hitachi Ops Center Analyzer from a version earlier than 10.0, verify that SSL communication is configured.
Parent Topic

Installing OS updates and other products after deployment

 
The following table outlines the installation tasks for an operating system patch or for Hitachi Ops Center products in an environment where the installer is used.

Task

Implementation method

Apply operating system patches

Apply as needed.

Update the operating system

You can update the OS as described in Applying Linux security updates using yum.

Upgrade Hitachi Ops Center products

For an upgrade installation or overwrite installation, use the installation media.

Upgrade of OSS

Python3, Requests, and OpenSSL incorporated in the software is set for the sample code of Hitachi Ops Center API Configuration Manager. If a vulnerability is found in Python3, Requests, and OpenSSL, upgrade all of them. For details, see the Hitachi Ops Center API Configuration Manager Release Notes.

Install additional Hitachi Ops Center products

Confirm the system requirements of the products, install prerequisite packages, and reconfigure kernel parameters as necessary. For details on the product system requirements, see the documentation or Release Notes for each product.
Parent Topic

Configuring SSL communications

 
By default, Common Services uses SSL/TLS communications. Immediately after installation, the system uses SSL communication by using a self-signed certificate. However, you must set up SSL communications to use a valid server certificate before any of the products can communicate with Common Services and the Hitachi Ops Center Portal.

For details on how to configure SSL communications, see Configuring SSL communications.

Parent Topic

Registering products in Common Services

 
To use the functions provided by Common Services, you must register products in Common Services. When you use an individual installer to install each product, run the setupcommonservice command to register each product in Common Services.
NoteThe operation for removing a Hitachi Ops Center product that was registered in Common Services is performed using the Hitachi Ops Center Portal.
 
Parent Topic
Child Topics

Registering Ops Center products with Common Services (setupcommonservice)

 
Use the setupcommonservice command to register Ops Center products with Common Services.

Before you begin

  • Ensure that each product can resolve the host name where Common Services is installed. If you want to use a host name that is not a fully qualified domain name (FQDN), set the IP address and the host name in the /etc/hosts file for name resolution. If you want to use an IP address instead of a host name, log in to the management server where Common Services is installed and run the cschgconnect.sh command.
  • Ensure that the Ops Center product server and the Common Services server are running.
  • Use a Common Services account with the "Application Administrator" role to run setupcommonservice command.
NoteProducts deployed by using the Ops Center OVA are already registered in Common Services.

If you change the Common Services host name, IP address, or server port number changes, you must register each product again.

The setupcommonservice command also sets each Ops Center product as an authentication server that uses Common Services. You can then access the application from the portal using the Ops Center credentials.

Administrator

Default location: /opt/rainier/bin

Command syntax:

 

setupcommonservice --csUri CommonService_URL --applicationPort port_number --applicationHostAddress ip_address --applicationName app_name [--appDescription app_description] [--csUsername CommonService_Username] [--tlsVerify --csUriCACert Certificate_FileName]

Command example:

 

setupcommonservice --csUri https://example.com/portal --csUsername sysadmin --tlsVerify --csUriCACert certificate.cer --applicationPort 443 --applicationHostAddress 192.0.2.11 --applicationName MyAdministrator1
Protector

Default location: /opt/hitachi/protector/bin/

Command syntax:

 

setupcommonservice --cs-uri CommonService_URL [--cs-username CommonService_Username] --app-scheme protocol --app-hostname host_name --app-port port_number

Command example:

setupcommonservice --cs-uri https://example.com/portal --cs-username sysadmin --app-scheme https --app-hostname MyHost --app-port 443
Automator

For Linux:

Default location: /opt/hitachi/Automation/bin/

Command syntax:

setupcommonservice {[-csUri CommonService_URL | -csUri CommonService_URL -csUsername CommonServiceUsername] [-appName app_name] [-appDescription app_description] [-auto] | -help}

Command example:

setupcommonservice -csUri https://example.com/portal -appName MyAutomator1

For Windows:

Default location: Program-Files-folder\hitachi\Automation\bin

Command syntax:

setupcommonservice {[/csUri CommonService_URL | /csUri CommonService_URL /csUsername CommonServiceUsername] [/appName app_name] [/appDescription app_description] [/auto] | /help}

Command example:

setupcommonservice /csUri https://example.com/portal /appName MyAutomator1
Analyzer

Default location: /opt/hitachi/Analytics/bin/

Command syntax:

setupcommonservice -csUri CommonService_URL [-csUsername CommonService_Username] [-appPort port_number] [-appHostname ip_address_or_host_name] [-appName app_name] [-appDescription app_description] [-auto]

Command example:

 

setupcommonservice -csUri https://example.com/portal -appPort 22016 -appHostname 192.0.2.10 -appName MyAnalyzer1
Analyzer detail view

Default location: /usr/local/megha/bin/

Command syntax:

 

setupcommonservice -csUri CommonService_URL -csUsername CommonService_Username -appHostname ip_address_or_host_name -appPort port_number -appName app_name -appDescription app_description

Command example:

 

setupcommonservice -csUri https://example.com/portal -csUsername sysadmin -appHostname MyHost -appPort 8443 -appName MyAnalyzerdetailview1 -appDescription ""
Analyzer probe

Default location: /usr/local/megha/bin/

Command syntax:

 

setupcommonservice -csUri CommonService_URL -csUsername CommonService_Username -appHostname ip_address_or_host_name -appPort port_number -appName app_name -appDescription app_description

Command example:

 

setupcommonservice -csUri https://example.com/portal -csUsername sysadmin -appHostname MyHost -appPort 8443 -appName MyAnalyzerprobe1 -appDescription ""
Analyzer viewpoint

Default location: /opt/hitachi/analyzer_viewpoint/bin/

Command syntax:

 

setupcommonservice --csUri CommonService_URL [--csUsername CommonServiceUsername] [--applicationName app_name]

Command example:

 

setupcommonservice --csUri https://example.com
Parent Topic

Logging in to the Hitachi Ops Center Portal

 
Log in to the Hitachi Ops Center Portal from your browser.

Before you begin

To avoid issues with windows not displaying correctly, configure your browser settings as follows:

  • Accept cookies, or register the portal URL as a trusted site.
  • Enable active scripting in the security settings.

Procedure

  1. In a web browser, access the following URL:

    https://host-name-or-IP-address-of-Portal:port-number/portal/

    When entering the URL to access the portal, enter the host name or IP address and the port number that were specified during installation.

  2. Use the following built-in account to log in:

    User name: sysadmin

    Password: sysadmin

    The Hitachi Ops Center Portal main window opens.

    NoteFor security, be sure to change the password of the built-in account.
Parent Topic

Settings required when using a virus detection program

 
 

If a virus detection program accesses database-related files used by Common Services, an error might occur for reasons such as I/O delays or file locks. To prevent such errors while Common Services is running, exclude the following directories from the targets scanned by the virus detection program:

  • /usr/pgsql-11/bin
  • installation-directory-of-Common-Services/nginx/temp
  • /var/installation-directory-of-Common-Services
For details on the directories of other Ops Center products to exclude from the scanning targets, see the manual for each product.
Parent Topic