Adding a login warning banner for the Ops Center Portal

Ops Center Quick Start Guide

Version
11.0.x
Audience
anonymous
Part Number
MK-99OPS006-07
ft:lastEdition
2026-03-16
You can add a warning banner to display information about system access on the portal login page.
  1. Log in to the Ops Center portal as sysadmin or a user with opscenter-administrators membership.
  2. Click the Settings icon and select Warning banner.
  3. You can customize the default message or compose a new one. Click Submit when the changes are complete.

Maintain Hitachi Ops Center

The Hitachi Ops Center system administrator performs various system operation and maintenance tasks such as starting or stopping a service, backing up and restoring user data, and modifying URLs.

Checking the status of Ops Center services

Product Command
Ops Center Common Services

systemctl status csportal

Ops Center Analyzer

Common-Component-installation-destination/bin/hcmds64srv -status

Ops Center Analyzer detail view

Analyzer probe server

/usr/local/megha/bin/megha-jetty.sh status

Ops Center Analyzer RAID Agent

/opt/jp1pc/htnm/bin/htmsrv status -all

Ops Center Analyzer viewpoint

systemctl status analyzer- viewpoint.target

Ops Center Administrator

systemctl status rainier

Ops Center Automator Windows:

Common-Component-installation-destination\bin\hcmds64srv /status

Linux:

Common-Component-installation-destination/bin/hcmds64srv -status

Ops Center Protector -
Ops Center API Configuration Manager Windows:

REST-API-installation-destination\status.bat

Linux:

REST-API-installation-destination/status.sh

hcmds64srv

Use this command to start or stop Analyzer server services. The command also displays the Analyzer server service status or changes the service start method.

Format

To start, stop, or display only the status of a specific service:
hcmds64srv
     {-start | -stop | -check | -status}
     [-server service-name]
To display the status of services of Analyzer server and products that use Common component:
hcmds64srv
        -statusall
To change the start method of a service:
hcmds64srv
        -starttype {auto | manual}
        {-server service-name | -all}

Options

start

Starts the service and database you specified in the server option.

stop

Stops the service and database you specified in the server option.

status

Displays the status of the server and database you specified in the server option.

server service-name

To start, stop, or display the status of Analyzer server product services only, specify AnalyticsWebService as the service name. By running this command by specifying AnalyticsWebService in the server option, you can start, stop, or display the status of the following services:

Service display name and process

Start

Stop

Status display

HAnalytics Engine Web Service

 Y 

 Y 

 Y 

HBase 64 Storage Mgmt Web Service

 Y 

 N 

 N 

HBase 64 Storage Mgmt Web SSO Service

 Y 

 N 

 N 

Database process*

 Y 

 N 

 N 

Legend:

Y: Processed

N: Not processed

* An Analyzer server internal process corresponding to the service HiRDB/EmbeddedEdition _HD1

If you omit the server option, the next service is started, stopped, or the status of the next service displays.

Service display name and process

Start

Stop

Status display

HAnalytics Engine Web Service

 Y 

 Y 

 Y 

HBase 64 Storage Mgmt SSO Service

 Y 

 Y 

 Y 

HBase 64 Storage Mgmt Web Service

 Y 

 Y 

 Y 

HBase 64 Storage Mgmt Web SSO Service

 Y 

 Y 

 Y 

Database process*

 Y 

 Y 

 Y 

Service of products that use Common component

 Y 

 Y 

 Y 

Legend:

Y: Processed

* An Analyzer server internal process corresponding to the service HiRDB/EmbeddedEdition _HD1

statusall

Displays the service and data statuses, and the status of the products registered in Common component. If you omit the server option, this argument is used.

starttype {auto | manual}

Specify the start type of the service with the server option. Specify auto for an automatic start. Specify manual for a manual start.

all

If you specify this option, the command runs for all services of Analyzer server and other products that use Common component.

Execution Permission

root permission

Location

In Windows

Common-component-installation-folder\bin

In Linux

Common-component-installation-directory/bin

Notes

  • If you start or stop Analyzer server services as a daily operation, omit the server option to start or stop all the services. To start only Analyzer server services by specifying the server option, specify AnalyticsWebService for the server option to start Common component service.
  • If you run the command with the stop option and the termination processing does not end within three minutes, an error occurs and a message is displayed to indicate a time-out. In this case, wait a while, and then rerun the command with the stop option.
  • If you start or stop a service with the start or stop option, the command might end while the service does not start or stop completely. To confirm that the service has completely started or stopped, use either of the following operations:
    • Confirm that either of the following messages has been output to a disclosed log or the event logsyslog:
      At startup
      KNAQ10086-I Application is running.
      When stopped
      KNAQ10089-I Application is stopped.
    • Specify the statusall option to check the status of the service.

Return values

The following table shows the return values of the command with start option or stop option:

Return value

Description

0

The command ran normally.

1

With start option

The service was already started.

With stop option

The service was already stopped.

255

The command failed.

The following table shows the return values of the command with the check, status, or statusall option:

Return value

Description

0

The service has not started.

1

The service has started.

255

The command failed.

The following table shows the return values of the command with the starttype option:

Return value

Description

0

The command ran normally.

255

The command failed.

Examples

To start all services:
hcmds64srv -start
To stop all services:
hcmds64srv -stop
To check the status of all services:
hcmds64srv -status
To start the services of only Analyzer server products:
hcmds64srv -start -server AnalyticsWebService

Checking the status of the REST API service

The following describes how to check the status of the REST API service:

Log in to the management server as any one of the following user types:

  • A user with Administrator permissions (in Windows)
  • Root user (if the REST API was installed by the root user in Linux)
  • A non-root user who installed the REST API
Perform the following operations.

In a Windows OS:

Check the services in one of the following ways:

  • Select Start, All Programs, Hitachi Ops Center, Configuration Manager, and then Status - CONFIG_MGR.
  • From the Start window, open the application list window, select Hitachi Ops Center, and then Status - CONFIG_MGR.
  • Run the following command:

    REST-API-installation-destination\status.bat

In a Linux OS:

Run the following command:

REST-API-installation-destination/status.sh

Starting and stopping Ops Center services

Product Command
Ops Center Common Services

To stop the service:

systemctl stop csportal

To start the service:

systemctl start csportal

or

systemctl restart csportal

Ops Center Analyzer

To stop the service:

Common-Component-installation-destination/bin/hcmds64srv -stop

To start the service:

Common-Component-installation-destination/bin/hcmds64srv -start

Ops Center Analyzer detail view

To stop the service:

/usr/local/megha/bin/megha-jetty.sh stop

To start the service:

/usr/local/megha/bin/megha-jetty.sh start

Analyzer probe server
Ops Center Analyzer RAID Agent

Windows:

To stop the service:

RAID-Agent-installation-destination\jp1pc\htnm\bin\htmsrv stop -all

To start the service:

RAID-Agent-installation-destination\jp1pc\htnm\bin\htmsrv start -all

Linux:

To stop the service:

/opt/jp1pc/htnm/bin/htmsrv stop -all

To start the service:

/opt/jp1pc/htnm/bin/htmsrv start -all

Ops Center Analyzer viewpoint

To stop the service:

systemctl stop analyzer-viewpoint.target

To start the service:

systemctl restart analyzer-viewpoint.target

Ops Center Administrator

To stop the service:

systemctl stop rainier

To start the service:

systemctl start rainier

Ops Center Automator

Windows:

To stop the service:

Common-Component-installation-destination\bin\hcmds64srv /stop

To start the service:

Common-Component-installation-destination\bin\hcmds64srv /start

Linux:

To stop the service:

Common-Component-installation-destination/bin/hcmds64srv -stop

To start the service:

Common-Component-installation-destination/bin/hcmds64srv -start

Ops Center Protector

To stop all services:

/bin/diagdata --stop hub

To start all services:

/bin/diagdata --start all

Ops Center API Configuration Manager

Windows:

To stop the service:

REST-API-installation-destination\stop.bat

To start the service:

REST-API-installation-destination\start.bat

Linux:

To stop the service:

REST-API-installation-destination/stop.sh

To start the service:

REST-API-installation-destination/start.sh

Starting or stopping the Common Services service

To start or stop the Common Services service, use the systemctl command.
  1. Log in to the management server as the root user.
    If you log in as an ordinary user, use the sudo command to complete the following procedure as the root user.
  2. Run the systemctl command.
    To start the service:
    systemctl start csportal
    To stop the service:
    systemctl stop csportal
    To restart the service:
    systemctl restart csportal

Starting the REST API services

You can start the REST API services.

Log in to the management server as any one of the following user types:

  • A user with Administrator permissions (in Windows)
  • Root user (if the REST API was installed by the root user in Linux)
  • A non-root user who installed the REST API
Note:

If the installation path of the REST API includes a space and a file whose path matches the installation path up to the first space, an attempt to start the REST API services might end in an error. For example, if the installation destination is C:\Program Files\hitachi\ConfManager and C:\ contains a file called Program, installation might end in an error. In such cases, change the file name, or move or delete the file.

Perform the following operations.

In a Windows OS:

Start the services in one of the following ways:

  • Select Start, All Programs, Hitachi Ops Center, Configuration Manager, and then Start - CONFIG_MGR.
  • From the Start window, open the application list window, select Hitachi Ops Center, and then Start - CONFIG_MGR.
  • Run the following command:

    REST-API-installation-destination\start.bat

In a Linux OS:

Run the following command:

REST-API-installation-destination/start.sh

Stopping the REST API services

You can stop the REST API services.

Log in to the management server as any one of the following user types:

  • A user with Administrator permissions (in Windows)
  • Root user (if the REST API was installed by the root user in Linux)
  • A non-root user who installed the REST API
Note:

If the installation path of the REST API includes a space and a file whose path matches the installation path up to the first space, an attempt to stop the REST API services might end in an error. For example, if the installation destination is C:\Program Files\hitachi\ConfManager and C:\ contains a file called Program, installation might end in an error. In such cases, change the file name, or move or delete the file.

Perform the following operations.

In a Windows OS:

Stop the services in one of the following ways:

  • Select Start, All Programs, Hitachi Ops Center, Configuration Manager, and then Stop - CONFIG_MGR.
  • From the Start window, open the application list window, select Hitachi Ops Center, and then Stop - CONFIG_MGR.
  • Run the following command:

    REST-API-installation-destination\stop.bat

In a Linux OS:

Run the following command:

REST-API-installation-destination/stop.sh

Gathering diagnostic information with diagdata

diagdata is a CLI tool that is used to aid diagnostic testing of Ops Center Protector. It provides the following functions:

  • Stopping and starting of Ops Center Protector services
  • Resetting the Ops Center Protector system state
  • Raising and lowering of trace level for diagnostics
  • Collection of Ops Center Protector state information to aid investigation of issues

Command line options

Table. General options
Abbreviated argument Full argument Description
-h --help Display help.
Table. Service options
Abbreviated argument Full argument Description
-r arg --restart arg Auto restart active services yes | no
--start arg

Starts the hub service.

Options are none, all, hub.

‘none’ means no argument is required.

--stop arg

Stops the hub service.

Options are none, all, hub.

‘none’ means no argument is required.

Table. Protector
Abbreviated argument Full argument Description
-d arg --trace-dir arg Set the trace directory.
-T arg --temp-dir arg Set the temp directory.
--reset

Resets the state of the Ops Center Protector node and flushes cache and logs. Can only be run if Ops Center Protector services are stopped (see --stop).

Table. Dump options
Abbreviated argument Full argument Description
-f --full Produce a full dump of the Ops Center Protector configuration on the system, including all trace files. Results are placed in a ZIP file named:

diag_node name_YYYYMMDDhhmm.zip

in the directory: Data-Instance-Director-install\runtime

This ZIP file can be requested by Hitachi Vantara support when investigating complex end user issues.

Can be combined with --spilt

-m --mini Similar to –f but only saves a recent portion of all trace files.

Can be combined with --spilt

-c arg --collect arg arg specifies which data must be collected. Use all to collect all components. For additional component names use -c help.

Can be combined with --spilt

-o arg --output-dir arg arg specifies an optional output directory. Default is Protector\runtime
-n arg --tracename arg arg specifies a filter mask which uses wildcards to target only specific trace files e.g. diagdata -f --tracename repos*.

Multiple filters can be used seperated by ';' e.g. hub*;node*;repo*. For Linux use "hub*;node*;repo*").

-a arg --traceage arg arg specifies an age, in days, to target only trace files modified in that time frame.
-z --nosnapshots Prevents diagdata from creating snapshots before a dump (this may result in some files not being added to the diagnostic dump).
-Z --withsnapshots Attempt diagdata snapshots regardless of configuration. The default mode of operation.

For linux , snapshots will only be taken for LVM filesystems

--no-md5 Disable MD5 checksum on created zip files.
Table. Trace options
Abbreviated argument Full argument Description
-t arg --trace arg

Sets the trace level of the node. Valid arguments are:

TraceAlways –

TraceTesting, TraceNormal, TraceVerbose TraceDebug

Trace files are placed in the directory:

[Install-Dir]\runtime\trace

-p --deltrace Delete inactive trace files. Any trace files currently in use by the Protector system will not be deleted.

Deletes the contents of [Install-Dir]\runtime\trace

-x --delalltrace Stop Protector services, delete all trace and then restart them.
-i --info Get information about this node and current trace status.
Table. Windows crash dump file options
Abbreviated argument Full argument Description
-l arg --dumplevel arg Not available on Linux. Sets Protector crash dump level full | default.
--test-dump Not available on Linux. Generates a Windows dump file for test purposes.
Table. Archive options
Abbreviated argument Full argument Description
-S arg --split-file arg Split an existing zip file (path specified by arg) into multiple chunks (configurable, 1GB default). Intended to be used if the file is too big to be uploaded to a file service.
-C arg --concatenate arg File name for the concatenated file. That must be followed by the list of the files to be concatenated. Example: --concatenate diag.zip part.000 part.001 part.002
--split Split the zip in multiple chunks (configurable, 1GB default), this is used with the --full, --mini and --collect options. Intended to be used if the file is too big to be uploaded to a file service.

Usage Examples:

Stopping the Ops Center Protector services on any node:

diagdata --stop

Setting the trace level of the Ops Center Protector services on any node:

diagdata --trace TraceAlways

Collect a mini dianostic log from a node:

diagdata --mini

Collect a full diagnostic log from a node:

diagdata --full

Starting and stopping the Ops Center Analyzer services

Start and stop the Ops Center Analyzer services with the hcmds64srv command.

Starting the Analyzer server services

To start the Analyzer server services, run the hcmds64srv command.

You must have Administrator permission (Windows) or root permission (Linux).

Run the following command:

For Windows:

Common-component-installation-folder\bin\hcmds64srv /start

For Linux:

Common-component-installation-directory/bin/hcmds64srv -start

For details on the command, see hcmds64srv.

Note:
  • For Windows, do not use Service Control Manager to start the services.
  • To stop or start only the Analyzer server services when the Common component services are running, specify -server AnalyticsWebService.
  • When you restart the Analyzer server services, the status of monitored resources can be delayed for 5 minutes or longer. During this time, the status displays as Unknown.
Stopping the Analyzer server services

To stop the services, run the hcmds64srv command.

You must have Administrator permission (Windows) or root permission (Linux).
Run the following command:

For Windows:

Common-component-installation-folder\bin\hcmds64srv /stop /server server-name

For Linux:

Common-component-installation-directory/bin/hcmds64srv -stop -server server-name

For details on the command, see hcmds64srv.

Note:
  • For Windows, do not use Service Control Manager to stop the service. Doing so might cause the process to fail
  • To stop or start only the Analyzer server services when the Common component service is running, specify -server AnalyticsWebService.
  • When you restart the Analyzer server services, the status of monitored resources can be delayed for 5 minutes or longer. During this time, the status displays as Unknown.
Starting the Analyzer detail view server or Analyzer probe server services

Start the Analyzer detail view server or Analyzer probe server services by editing crontab.

  • Make sure that the following disk space is available:
    • Analyzer probe server:
      • Installation directory: More than 5 GB or 5% available of the total disk space
      • /etc: 100 MB (Available)
      Note: The Analyzer probe server retrieves the partition details where the directories are mounted and checks the free disk space. Make sure that the required disk space is available on partition in case multiple directories are mounted on it.
    • Analyzer detail view server:
      • Installation directory: More than 5 GB or 5% of the total disk space
  • Log on to the Analyzer detail view server or Analyzer probe server as the megha user.
  1. Run the crontab -e command.
  2. Delete the hash marks (#) from the beginning of each line as shown in this example:
    */5 * * * * F=/usr/local/megha/cron.5min; test -f $F && sudo $F
    */5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (sudo $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\%d`.log; chown -R megha:megha /usr/local/megha/logs/sys)
    
  3. Start the megha service using the command:
    sudo /usr/local/megha/bin/megha-jetty.sh start
  4. Confirm the megha service has started:
    /usr/local/megha/bin/megha-jetty.sh status
Stopping the Analyzer detail view server or Analyzer probe server services

Stop the Analyzer detail view server or Analyzer probe server services by editing crontab.

Log on to the Analyzer detail view server or Analyzer probe server as the megha user.

  1. Run the crontab -e command.
  2. At the beginning of each line add a hash mark (#) to comment out a line as shown in this example:
    # */5 * * * * F=/usr/local/megha/cron.5min; test -f $F && sudo $F
    # */5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (sudo $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\%d`.log; chown -R megha:megha /usr/local/megha/logs/sys)
    
  3. Stop all services using the command:
    sudo /usr/local/megha/bin/stop-all-services.sh
  4. Confirm the megha service has stopped:
    /usr/local/megha/bin/megha-jetty.sh status
Starting the RAID Agent services
Start the RAID Agent services when creating or deleting an instance environment for RAID Agent.
  • Log on as root permission (Linux) or Administrator permission (Windows) to the host where RAID Agent is installed.
  • For RAID Agent (Windows), run commands from the administrator console. For details, see Command usage guidelines.

Procedure

To start services manually:
  1. Run the following command.
    In Linux
    /opt/jp1pc/htnm/bin/htmsrv start -all
    In Windows
    RAID-Agent-installation-folder\raid_agent\jp1pc\htnm\bin\htmsrv start -all
  2. If you are starting the services after performing a restore operation, check the RAID Agent log file htmRestDbEngineMessage<number>.log to make sure that the KATR13248-E message is not logged before the KATR13244-I message is generated.

    Note that it might take about one hour from when the RAID Agent service starts until the KATR13244-I message is generated.

    If the KATR13248-E message is logged, RAID Agent restoration might have failed. Check whether the prerequisites for restoration are met. If there is a problem, restore the entire RAID Agent system again.

    The htmRestDbEngineMessage<number>.log file is stored in the following location.

    In Linux

    /opt/jp1pc/htnm/logs

    In Windows

    RAID-Agent-installation-folder\raid_agent\jp1pc\htnm\logs

To start services automatically (Linux only):
When setting RAID Agent to automatically start in Linux, use the following procedure as reference.

Setting automatic starting and stopping of the RAID Agent services (Linux)

Note: For RAID Agent (Windows), automatic service start is enabled by default.
To disable automatic service start (Windows only):
  1. From the Windows Start menu, select Administrative Tools > Services.
  2. Select the windows service whose settings you want to change. To disable automatic service start, you must change the following service settings:
    • Ops Center Analyzer RAID Agent - Status Server
    • Ops Center Analyzer RAID Agent - Action Handler
    • Ops Center Analyzer RAID Agent - Agent REST Web Service
    • Ops Center Analyzer RAID Agent - Agent REST Application Service
    • Ops Center Analyzer RAID Agent instance-name*
    • Ops Center Analyzer RAID Agent Store instance-name*

    * Displayed only when you created an instance.

  3. Select the startup type. To cancel automatic startup, select Manual.
Note: Do not change the service account settings. If you do, the service might not operate properly.
Stopping the RAID Agent services
You can stop the RAID Agent services manually or automatically.
  • Log on as root permission (Linux) or Administrator permission (Windows) to the host where RAID Agent is installed.
  • For RAID Agent (Windows), run commands from the administrator console. For details, see Command usage guidelines.

Procedure

To stop services manually:
Run the following command.

In Linux

/opt/jp1pc/htnm/bin/htmsrv stop -all

In Windows

RAID-Agent-installation-folder\raid_agent\jp1pc\htnm\bin\htmsrv stop -all
To stop services automatically:
When setting RAID Agent to automatically stop in Linux, use the following procedure as reference.

Setting automatic starting and stopping of the RAID Agent services (Linux)

Note: For RAID Agent (Windows), automatic service stop is enabled by default.
Setting automatic starting and stopping of the RAID Agent services (Linux)
Use the following procedure to enable or disable automatic starting and stopping of the RAID Agent services.

If you enable automatic stopping of the services, you must also enable automatic starting. Also, if you enable automatic starting of the services, you must also enable automatic stopping.

Log on as root permission (Linux) to the host where RAID Agent is installed.

Procedure

To enable automatic starting and stopping:
  1. Run the following command to stop the RAID Agent services:
    /opt/jp1pc/htnm/bin/htmsrv stop -all
  2. Run the following command and verify that the services have stopped.
    /opt/jp1pc/htnm/bin/htmsrv status -all
  3. Set up the service automatic start script file (jpc_start) for the RAID Agent by copying the .model file (jpc_start.model) of the service automatic start script and adding execute permission as follows:
    cp -a /opt/jp1pc/jpc_start.model /opt/jp1pc/jpc_start
    chmod 500 /opt/jp1pc/jpc_start
  4. Set up the service automatic stop script file (jpc_stop) for the RAID Agent by copying the .model file (jpc_stop.model) of the service automatic stop script and adding execute permission as follows:
    cp -a /opt/jp1pc/jpc_stop.model /opt/jp1pc/jpc_stop
    chmod 500 /opt/jp1pc/jpc_stop
  5. Run the following command to enable automatic starting and stopping of the RAID Agent REST Application Service and the RAID Agent REST Web Service.
    /opt/jp1pc/htnm/bin/htmsrv starttype auto -webservice
  6. Run the following command to stop the RAID Agent services:
    systemctl stop jp1_pc.service
    /opt/jp1pc/htnm/bin/htmsrv stop -webservice
  7. Run the following command to start the RAID Agent services:
    systemctl start jp1_pc.service
    /opt/jp1pc/htnm/bin/htmsrv start -webservice
To disable automatic starting and stopping:
  1. Run the following command to stop the RAID Agent services:
    systemctl stop jp1_pc.service
    /opt/jp1pc/htnm/bin/htmsrv stop -all
  2. Run the following command and verify that the services have stopped.
    /opt/jp1pc/htnm/bin/htmsrv status -all
  3. Run the following command to disable automatic starting and stopping the following services:
    • Agent Collector, Agent Store, Status Server, Action Handler
    /bin/rm /opt/jp1pc/jpc_start
    /bin/rm /opt/jp1pc/jpc_stop
  4. Run the following command to disable automatic starting and stopping of RAID Agent REST Application Service and RAID Agent REST Web Service.
    /opt/jp1pc/htnm/bin/htmsrv starttype manual -webservice
  5. Run the following command to start the RAID Agent services:
    /opt/jp1pc/htnm/bin/htmsrv start -webservice
Starting the Virtual Storage Software Agent services

To start the Virtual Storage Software Agent services:

  1. Log on as root on the host where Virtual Storage Software Agent is installed.
  2. Run the following command:
    systemctl start virtualstoragesoftware-agent.service
Stopping the Virtual Storage Software Agent services

To stop the Virtual Storage Software Agent services:

  1. Log on as root on the host where Virtual Storage Software Agent is installed.
  2. Run the following command:
    systemctl stop virtualstoragesoftware-agent.service
Starting the On-demand real time monitoring module services

You can start the On-demand real time monitoring services.

You must have root permission (Linux) or Administrator permission (Windows).
  1. Log on to the host where the RAID Agent is installed.
  2. Start the On-demand real time monitoring module services.

    In Linux

    systemctl start analyzer-granular-data-collection-api

    In Windows

    1. Open the Windows Services window.
    2. Right-click On-demand real time monitoring module and then select Start.
Stopping the On-demand real time monitoring module services

To stop the On-demand real time monitoring services:

You must have root permission (Linux) or Administrator permission (Windows).
  1. Log on to the host where the RAID Agent is installed.
  2. Stop the On-demand real time monitoring module services:

    In Linux

    systemctl stop analyzer-granular-data-collection-api

    In Windows

    1. Open the Windows Services window.
    2. Right-click On-demand real time monitoring module and then select Stop.

Starting the Analyzer Windows probe service

Start the probe service from the Status tab in the Analyzer Windows probe console.

  1. On the Analyzer Windows probe console, click the Status tab.
    The Status tab list the details of the upload information and service information.
  2. Verify the upload and service information, and click Start.
    Note: When you change the time zone of the Windows machine on which the Analyzer Windows probe is installed, restart the Analyzer Windows probe console to update the Analyzer Windows probe with this new time zone.

Checking the validity period of a certificate in the truststore

You can check whether the validity period of a certificate in the truststore has expired.
Run the following command and provide the keystore password when prompted:
installation-directory-of-Common-Services/jdk/bin/keytool -list -v -keystore /var/installation-directory-of-Common-Services/tls/cacerts

Checking the validity period of the server certificate

You can check whether the validity period of the server certificate for the management server has expired.
Note: If the certificate has expired, you must renew it. Follow the procedure in Creating a private key and a certificate signing request (SSL Setup tool) to request a new certificate and overwrite the existing one. You must also reconfigure the SSL server settings and SSL client settings.
Run the following command:
installation-directory-of-Common-Services/jdk/bin/keytool -printcert -file path-of-server-certificate

Checking the revocation status of the server certificate

You can check the revocation status of the server certificate for a Hitachi Ops Center product by using the Online Certificate Status Protocol (OCSP).
Note: If the certificate has been revoked, you must renew it. Follow the procedure in Creating a private key and a certificate signing request (SSL Setup tool) to request a new certificate and overwrite the existing one. You must also reconfigure the SSL server settings and SSL client settings.

Verify that the following settings are configured on the management server:

  • The OCSP responder is functioning. If you are unsure whether it is functioning, contact the certificate authority.
  • The server certificate has the Authority Information Access (AIA) record that includes the correct address of the OCSP responder.
  • The management server can access the OCSP responder and access is not blocked by a proxy.

To check whether the AIA record includes the correct address of the OCSP responder, you can use the openssl command. Check the address of the OCSP-URI field of the AIA record. If no address is set, contact the certificate authority that signed the server certificate. The following is the command syntax and an example of the command:

Command syntax:

echo "Q" | installation-directory-of-Common-Services/openssl/bin/openssl s_client -connect host-name-or-ip-address-of-product-URL:port-number-of-product-URL 2> /dev/null | openssl x509 -noout -text

Command example:

echo "Q" | /opt/hitachi/CommonService/openssl/bin/openssl s_client -connect example.com:443 2> /dev/null | openssl x509 -noout -text

You can check the revocation status of the server certificate in one of the following ways:

Checking the revocation status of the server certificate by using a web browser

You can use the OCSP check function of your web browser to check the revocation status of the server certificate. For details on how to check the status, see the documentation for your browser.

For Firefox, you can check the status by using the following procedure.

  1. In the settings window of Firefox, select Privacy & Security, and then select the Query OCSP responder servers to confirm the current validity of certificates check box.
  2. Use Firefox to access the URL for the target product, and then check whether an error appears.
    If the server certificate has expired, the SEC_ERROR_REVOKED_CERTIFICATE error appears.
    Note: For API Configuration Manager and other products that do not have a web GUI, you cannot use a web browser to check the revocation status. In such cases, see Checking the revocation status of the server certificate by using a command.

Checking the revocation status of the server certificate by using a command

You can check the revocation status of the server certificate by using the OCSP check function of the openssl command. For more details, see the openssl documentation.

  1. On the management server, run the following openssl command.

    Command syntax:

    installation-directory-of-Common-Services/openssl/bin/openssl ocsp -no_nonce -issuer issuer-certificate -cert server-certificate -url OCSP-Responder-URI -text

    The issuer certificate is either the root certificate or, if there is an intermediate certificate, specify the PEM-format certificate that combines the root and intermediate certificates.

    Command example:

    /opt/hitachi/CommonService/openssl/bin/openssl ocsp -no_nonce -issuer cacert.cer -cert httpsd.cer -url http://ad.example.com/ocsp -text
  2. Check whether the value of Cert Status is good. If the value is revoked, the server certificate has expired.

Checking the revocation status of the server certificate on a regular basis

On the management server where Hitachi Ops Center products are installed, use cron to check the revocation status of the server certificate on a regular basis. The revocation status check results can be output to a file or to syslog.
Sending the revocation status check results to a file
Send the revocation status of a server certificate to a file as follows. Register a command in cron and send the check results to a file.
  1. Log in to the management server as the root user.
    If you log in as an ordinary user, use the sudo command to complete the following procedure as the root user.
  2. Modify the crontab file. Run the following command.
    For details on the command, see the crontab documentation.
    crontab -u root -e
  3. Add a command to the crontab file for each product for which you want to check revocation status.
    The command you set differs depending on how the server certificate of the product is referenced.
    If you check by downloading the certificate file from the URL of the Hitachi Ops Center product:

    Specify the time to download, the command to download the server certificate, and the command to query the OCSP responder in the following format.

    * * * * * command-to-download-the-server-certificate;command-to-query-the-OCSP-responder
    • Command syntax for downloading the server certificate:
      installation-directory-of-Common-Services/openssl/bin/openssl s_client -connect host-name-or-ip-address-of-product-URL:port-number-of-product-URL [-sigalgs Signature-Algorithm-list] < /dev/null 2> path-of-the-standard-error-output-file | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' > path-of-download-destination-of-server-certificate
      

      For products that use both RSA and ECDSA server certificates, you must specify the command for RSA and again for ECDSA. For the -sigalgs option, specify the following signature algorithm list:

      For RSA: RSA+SHA256:RSA+SHA384:RSA+SHA512:RSA-PSS+SHA256:RSA-PSS+SHA384:RSA-PSS+SHA512

      For ECDSA: ECDSA+SHA256:ECDSA+SHA384:ECDSA+SHA512

    • Command syntax for querying the OCSP responder:
      installation-directory-of-Common-Services/openssl/bin/openssl ocsp -no_nonce -issuer issuer-certificate -cert path-of-server-certificate -url OCSP-Responder-URI [ -proxy [http[s]://][userinfo-of-proxy@]host-name-or-IP-address-of-proxy[:port-number-of-proxy] [/path-of-proxy] ] [-CAfile root-certificate-of-the-OCSP-responder-server] -text -out path-of-the-file-to-which-the-results-are-output 2>> path-of-the-standard-error-output-file
    If you check by referencing the certificate file set for the Hitachi Ops Center product:

    Specify the execution time and the command to query the OCSP responder in the following format.

    * * * * * command-to-query-the-OCSP-responder
    • Command syntax for querying the OCSP responder:
      installation-directory-of-Common-Services/openssl/bin/openssl ocsp -no_nonce -issuer issuer-certificate -cert path-of-server-certificate -url OCSP-Responder-URI [ -proxy [http[s]://][userinfo-of-proxy@]host-name-or-IP-address-of-proxy[:port-number-of-proxy] [/path-of-proxy] ] [-CAfile root-certificate-of-the-OCSP-responder-server] -text -out path-of-the-file-to-which-the-results-are-output 2> path-of-the-standard-error-output-file
    Note:
    • Specify the time to run each command. Specify a value for "* * * * *". If you want to run the command every day at 4:00 a.m., specify "0 4 * * *". For details, see the crontab documentation.
    • Specify different paths for path-of-the-file-to-which-the-results-are-output and path-of-the-standard-error-output-file for each command.
    • For the issuer-certificate for the command that queries the OCSP responder, either specify the root certificate or, if there is an intermediate certificate, specify the PEM-format certificate that combines the root and intermediate certificates.
    • To use a proxy for the command that queries the OCSP responder, specify the -proxy option.
    • If the Response Verify Failure error is output to standard-error-output-file, specify the -CAfile option.
    • For details on the openssl command, see the openssl documentation.
  4. Add a command for each product, specifying each command as described in step 3.

    Example settings:

    10 4 * * * command-for-product-1
    20 4 * * * command-for-product-2
    30 4 * * * command-for-product-3
    …
  5. After you finish specifying the commands, save the crontab file.
  6. Run the following command to enable crond.service.
    systemctl enable crond.service
  7. Restart the service to apply the crond settings. Run the following command.
    systemctl restart crond
  • At the specified time, a file is output to the directory specified in path-of-the-file-to-which-the-results-are-output. Check the value of Cert Status in the output file.
    • If the value is good: The server certificate is valid.
    • If the value is revoked: The server certificate has been revoked.
    • If the value is unknown: The status is unknown.
  • If the output file does not include the Cert Status line, an error might have occurred. For details about the error, check the file output to the directory specified in path-of-the-standard-error-output-file.
Outputting the revocation status check results to syslog
Output the revocation status of the server certificate to syslog as follows.
  1. Register a command in cron for each product whose revocation status you want to check.
    For details on how to specify the command, see Sending the revocation status check results to a file. To output the results to syslog, you do not need to specify the -out option.
  2. Change the crond settings. Open crond in a text editor such as vi editor and add -s to the CRONDARGS value.
    If you use the default value, the check results will be output to /var/log/cron.
    CRONDARGS=-s
  3. Restart the service to apply the crond settings. Run the following command.
    systemctl restart crond

At the specified time, the results are output to syslog. Search the syslog file for Cert Status. The result will be good, revoked, or unknown.

Changing the management server host name, IP address, or port number

If you change the management server host name or IP address or the port number used by Common Services, run the cschgconnect command to change the URL for accessing the Hitachi Ops Center Portal.

In order to change IP address of the server where Administrator is installed, setting Administrator is necessary before changing the IP address. Refer to "Modifying the Ops Center Administrator server's IP address" in Hitachi Ops Center Administrator Getting Started Guide to change Administrator configuration and then change the IP address.

  1. Log in to the management server as the root user.
    If you log in as an ordinary user, use the sudo command to complete the following procedure as the root user.
  2. Run the cschgconnect command.
    Command location
    installation-directory-of-Common-Services/utility/bin/cschgconnect.sh
    Format
    cschgconnect.sh [-h host-name-or-IP-address] [-p port-number] | -enableip {true|false} | -list
    Options
    -h host-name-or-IP-address

    Specify the host name (or FQDN) or IP address used to access the Hitachi Ops Center Portal. If you specify a host name (or FQDN), specify a value using no more than 128 characters. For the host name (or FQDN), you cannot specify uppercase characters. If you do, they are converted to lowercase characters and then registered.

    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.

    -p port-number
    Specify the port number used by Common Services.
    Note: If you change the port number, you must also change the firewall setting.
    -enableip {true|false}

    Specify whether an IP address can be used when the host name or FQDN is used in the URL for the Hitachi Ops Center Portal. To specify that the portal can be accessed by using an IP address, specify true. To specify that the portal cannot be accessed by using an IP address, specify false. The IP address for accessing the portal is automatically acquired from the system.

    This option and other options cannot be specified at the same time.

    -list

    Displays the current settings. This option and other options cannot be specified at the same time.

    If you change the settings by using the -h, -p, or -enableip option, the settings displayed when you specify the -list option are not applied to the system until the Common Services service is restarted.

    Note: If you use this command to change the host name or IP address to one that differs from the value set for CN or subjectAltName when the SSL server certificate was created, you must issue a new server certificate.
  3. Restart the Common Services service.
  4. Run the following command to check the result of the change.
    cschgconnect.sh -list
  5. Make sure that you can use a web browser to access the login window at the following URL:

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

  6. For each product registered in Common Services, run the setupcommonservice command for registering the product in Common Services again.
    For details, see the documentation for each product.

Changing the port number used for internal communications

You can change the port number that Common Services uses for internal communications.
  1. Log in to the management server as the root user.
    If you log in as an ordinary user, use the sudo command to complete the following procedure as the root user.
  2. Change the port number.
    The procedure differs depending on the port number.
    Port number Change procedure
    20951
    1. In the following property file, specify the port number after the change, and then save the file.

      Property file location
      /var/installation-directory-of-Common-Services/userconf/config_user.properties
      Settings
      CS_PORTAL_PORT=port-number-after-change
      CS_GW_PORTAL_PORT=port-number-after-change
    2. Restart the Common Services service.
    20952
    1. In the following property file, specify the port number after the change, and then save the file.

      Property file location
      /var/installation-directory-of-Common-Services/userconf/config_user.properties
      Settings
      CS_PORTAL_IDP_PORT=port-number-after-change
      CS_IDP_OP_HTTP_PORT=port-number-after-change
      CS_GW_IDP_PORT=port-number-after-change
    2. Restart the Common Services service.
    20954
    1. In the following property file, specify the port number after the change, and then save the file.

      Property file location
      /var/installation-directory-of-Common-Services/userconf/config_user.properties
      Setting
      CS_PORTAL_IDP_POSTGRESQL_PORT=port-number-after-change
    2. In the following configuration definitions file, specify the port number after the change, and then save the file.

      Definitions file location
      /var/installation-directory-of-Common-Services/pgdata/csidp/data/postgresql.conf
      Setting
      port = port-number-after-change # (change requires restart)
    3. Stop the Common Services service.
    4. Run the systemctl command to restart postgresql-15@csidp.
    5. Start the Common Services service.
    20955
    1. In the following property file, specify the port number after the change, and then save the file.

      Property file location
      /var/installation-directory-of-Common-Services/userconf/config_user.properties
      Setting
      CS_PORTAL_POSTGRESQL_PORT=port-number-after-change
    2. In the following configuration definitions file, specify the port number after the change, and then save the file.

      Definitions file location
      /var/installation-directory-of-Common-Services/pgdata/csportal/data/postgresql.conf
      Setting
      port = port-number-after-change # (change requires restart)
    3. Stop the Common Services service.
    4. Run the systemctl command to restart postgresql-15@csportal.
    5. Start the Common Services service.
    20956
    1. In the following property file, specify the port number after the change, and then save the file.

      Property file location
      /var/installation-directory-of-Common-Services/userconf/config_user.properties
      Setting
      CS_PORTAL_MANAGEMENT_PORT=port-number-after-change
    2. Restart the Common Services service.

Backing up and recovering Hitachi Ops Center applications

This sections provides information on backing up and recovering your Hitachi Ops Center applications. You can backup and recover automatically using Protector or manually as described in the following sections:

Backing up and restoring Hitachi Ops Center applications using Protector

You can schedule automatic backups for Hitachi Ops Center applications by using Protector. You can then restore your backups to recover each application.

You create backups by running Protector and selecting one or more Ops Center product components.

The restoration process consists of two stages, restore and recovery:

  1. Restoring backup archives to the proper node using Protector.
  2. Recovering each application by manually extracting the archive and running the required commands to bring it back online.
Note: Analyzer detail view and Analyzer probe server are automatically recovered as part of the restore process, so no manual recovery is necessary. All other applications require the two-stage restore and recovery.
CAUTION:
Prerequisites and cautions for backing up Hitachi Ops Center applications
There are specific and prerequisites for creating backups as described in the following table.
Application Precautions
All
  • Each server to be backed up must have a Protector client installed and configured. (If a Hitachi Ops Center application is installed on the same server as the Protector master, no client is necessary.)
  • Protector stores backup files in a repository. Prepare a Protector repository that includes the total size of backup files for each product.
Administrator

Before backing up Administrator, verify the following:

  • Administrator service is running.
  • No backup or restore jobs are running.
  • The Virtual Appliance Manager log level is set to INFO (DEBUG or TRACE might cause the backup to fail).
Analyzer During a backup, the Analyzer server stops Common Component, so other products that are using Common Component also stop.
Analyzer RAID Agent RAID Agent backups only include settings information. If you also want to back up the performance data used by the API requests that access RAID Agent, see the section explaining RAID Agent backups in the Hitachi Ops Center Analyzer Installation and Configuration Guide, and run the htmhsbackup command.
Analyzer probe Instances of the Windows probes are not backed up when using Protector.
Analyzer On-demand real time monitoring module The on-demand real time monitoring module installed on a Windows host is not backed up when using Protector.
Analyzer Adapter Analyzer Adapter is not backed up when using Protector.
Automator
  • Automator running on Windows is not backed up when using Protector. Only Linux is supported.
  • During a backup, the Automator server stops Common Component, so other products that are using Common Component also stop.
  • Make sure that no tasks are currently being processed in the Automator "Status" column of the Tasks tab with a status of "In Progress", "Waiting for Input", "In Progress (with Error)", "Long Running", or "In Progress (Terminating)".
API Configuration Manager
  • When API Configuration Manager is installed by a non-root Linux user, you cannot back up by using Protector.
  • When backing up, API Configuration Manager cannot be used because necessary services are temporarily stopped.
Common Services If the server certificate and private key are stored in a location other than the following directory, manually back up the server certificate and private key:

/var/Common-Services-installation-directory/tls/

Prerequisites and cautions for recovering Hitachi Ops Center applications
Depending on the Hitachi Ops Center application, there are restrictions on how you can recover an application. For example, you cannot recover all applications when using a different IP address, host name, or Hitachi Ops Center version. For details, see the following table.
Application Move data to different host name Move data to different IP address Move data to different Hitachi Ops Center version
Administrator Supported Supported Supported
Automator Not supported Not supported Not supported
Common Services Supported1 Supported1 Not supported
Analyzer Supported Supported Not supported
Analyzer viewpoint Not supported Not supported Not supported
API Configuration Manager Not supported Not supported Not supported
Protector Supported2 Supported Not supported
Notes:
  1. The Installation path must be the same as the original.
  2. The original Master Node name appears in the GUI and cannot be changed.
Note: By default, the recovery process uses /tmp for temporary storage. You can change this location by using the system environment variable (UBI_BACKUP_TMP_DIR). The location must be an absolute path (no symbolic links). You can set UBI_BACKUP_TMP_DIR as follows:
  1. Open the /etc/systemd/system.conf file and add the following:
    DefaultEnvironment="UBI_BACKUP_TMP_DIR=directory"
  2. Restart the OS.
Backing up Ops Center applications using Protector
You can create scheduled or immediate backups of Ops Center applications using Protector. This procedure applies to all Ops Center product components.
  • If you are not planning to use an existing repository node, you must configure a new one before proceeding.
  • You can only restore one application at a time.
  1. Log in to the Protector UI.
  2. In the Policies window, click the plus (+) icon near the top of the screen, enter a name (example: MasterBackup), and click Next.
  3. Click Next to skip Allocate Policy to Access Control Resource Group.
  4. In the Add one or more Classifications window, click on the plus (+) icon, click Application, select Ops Center, and click Next.
  5. In the Specify Ops Center Applications window, choose the master node as a source, and then choose whether you want to Include all Ops Center Applications, or select individual products by clicking Add. (You can also exclude products.) Click Apply.
  6. In the Add one or more Operations window, click the plus (+) icon, select Backup, and click Next.
  7. In the Specify Backup operation attributes window, you can set the schedule and retention for your backups. Click Apply to return to the Add one or more Operations window and click Finish.
  8. Select Data Flows, click the plus (+) icon, enter a name (example: MasterBackup) and click Next.
  9. Click Next to skip Allocate Policy to Access Control Resource Group.
  10. In the Create Data Flows window, drag the master node from the Nodes tab into the workspace, then drag the repository you want to use to store the backup.
  11. Click the master node and select MasterBackup from the Policies list.
  12. Click the repository and select MasterBackup from the Policies list.
  13. Click Finish.
  14. In Data Flows, select MasterBackup from the list, and click the play icon in the toolbar.
  15. In Activate Data Flows, click Activate.
  16. In the Monitor window, you can start the backup immediately by selecting MasterBackup and clicking the trigger (lightning) icon. (Otherwise, the backup occurs according to the schedule.)
  17. Select the operation and click Run Now. You can check the overall progress in the Jobs window or the details in the Log window.
To recover an Ops Center application, you must first restore the backup archive as described in Restoring Ops Center application archives using Protector.
Restoring Ops Center application archives using Protector
You can use Ops Center Protector to restore a backup archive to the server where you plan to perform the recovery of the application.

Analyzer detail view and Analyzer probe server are automatically recovered as part of the restore process described here, so no manual recovery is necessary. You must manually recover all other applications after the backup archive is restored using this procedure.

  1. In the Restore window, select the backup from the list and click the restore icon.
  2. In Select restore options, choose the Destination Node to which you want the backup archive exported.
  3. Click Finish.
  4. You can check the overall progress in the Jobs window or the details in the Log window.
Recovering Hitachi Ops Center applications from a backup archive
After the backup archive has been restored (copied to the proper node), you can recover your Hitachi Ops Center application. You must follow the recovery procedure for each product and any related agents by extracting each archive and supplying the path to the backup file required by the command line for each product and agent.

Recovering Administrator

To recover Administrator from a backup archive, complete the following steps:
  1. Access the Virtual Appliance Manager by opening a browser and entering the following URL.
    https://ip-address:port/vam

    where:

    • ip-address is the IP address of the Administrator server.
    • port is the port number of the Administrator server. The default port number is 443 or 20961. The default login credentials are sysadmin/sysadmin.

  2. Click Restore and either drag and drop the backup file or click the plus sign (+) to browse.
  3. Click Submit. The restore procedure can take up to an hour, after which Administrator restarts.
  4. Remove and reregister Administrator in Common Services.
    1. Remove Administrator from Common Services by going to the Hitachi Ops Center Portal and deleting it.
    2. Run the setupcommonservice command to register with Common Services.
    3. If necessary, change permissions for user groups.

Recovering Analyzer

To recover Analyzer from a backup archive, complete the following steps:
  1. Run the tar command to extract the backup archive file.

    tar xf backup-archive-file -C destination-directory

  2. Run the following restoresystem command.

    Analyzer-installation-directory/Analytics/bin/restoresystem -dir destination-directory -type all

For details, see the description of the restoresystem command in the Hitachi Ops Center Analyzer Installation and Configuration Guide.
Note: Private key files and server certificate files created or obtained by the user are not backed up. Depending on the location, the files might be included in the backup data; however, as a general rule, manually relocate the files when you recover.

Recovering Analyzer RAID Agent

<For Linux>

Before recovering Analyzer RAID Agent, verify the following:
  • If instances with the same names as those on the backup source do not exist in the restore destination, manually create RAID Agent instances using the same instance names as those on the backup source.
  • Verify that the following items are the same between the backup source host and the restore destination host:
    • OS (Linux)
    • Version number of the RAID Agent
    • Instance name
    • Hybrid Store storage destination
  • Stop all RAID Agent services on the restore destination host.
  • Verify that the restore destination has free space equal to or greater than the size of the data to be restored.
To recover Analyzer RAID Agent from a backup archive, complete the following steps:
  1. Confirm that the same name instance exists as when the backup was taken, and if it does not exist, create it.
  2. Copy the backup archive file to a working directory and extract it:

    tar xf backup-archive-file

  3. Run the following command to restore the performance data and configuration information files:

    /opt/jp1pc/htnm/bin/htmhsrestore -dir extracted-data-directory

  4. Run the jpctdchkinst command to check whether the instance is monitoring the targets correctly. If it is not, run the jpcinssetup command to change the settings, and then run the jpctdchkinst command again to check the monitoring status.

For details, see the Hitachi Ops Center Analyzer Installation and Configuration Guide.

Note:
  • Private key files and server certificate files created or obtained by the user are not backed up. Depending on the location, the files might be included in the backup data; however, as a general rule, manually relocate the files when you recover.
  • You cannot restore the following by using the htmhsrestore command and must make any required changes manually:
    • If you changed the port numbers or SSL communication settings in the backup source environment, you must also change them in the restore destination by editing the following file.

      /opt/jp1pc/htnm/Rest/config/htnm_httpsd.conf

    • If you changed the port numbers specified in the following files in the backup source environment, you must also change them in the restore destination.

      /opt/jp1pc/htnm/Rest/config/htnm_httpsd.conf

      /opt/jp1pc/htnm/HBasePSB/CC/server/usrconf/ejb/AgentRESTService/usrconf.properties

<For Windows>

Before recovering Analyzer RAID Agent, verify the following:
  • If instances with the same names as those on the backup source do not exist in the restore destination, manually create RAID Agent instances using the same instance names as those on the backup source.
  • Verify that the following items are the same between the backup source host and the restore destination host:
    • OS (Windows)
    • Version number of the RAID Agent
    • Instance name
    • Hybrid Store storage destination
  • Stop all RAID Agent services on the restore destination host.
  • Verify that the restore destination has free space equal to or greater than the size of the data to be restored.
To recover Analyzer RAID Agent from a backup archive, complete the following steps:
  1. Confirm that same name instance exists as when the backup was taken, and if it does not exist, create it.
  2. Copy the backup archive file to a working folder and extract it:

    tar xf backup-archive-file

  3. Run the following command to restore the performance data and configuration information files:

    Analyzer-RAID-Agent-Installation-folder\htnm\bin\htmhsrestore -dir extracted-data-folder

  4. Run the jpctdchkinst command to check whether the instance is monitoring the targets correctly. If it is not, run the jpcinssetup command to change the settings, and then run the jpctdchkinst command again to check the monitoring status.

For details, see the Hitachi Ops Center Analyzer Installation and Configuration Guide.

Note:
  • Private key files and server certificate files created or obtained by the user are not backed up. Depending on the location, the files might be included in the backup data; however, as a general rule, manually relocate the files when you recover.
  • You cannot restore the following settings by using the htmhsrestore command and must make any required changes manually:
    • If you changed the port numbers or SSL communication settings in the backup source environment, you must also change them in the restore destination by editing the following file.

      Analyzer-RAID-Agent-Installation-folder\htnm\Rest\config\htnm_httpsd.conf

    • If you changed the port numbers specified in the following files in the backup source environment, you must also change them in the restore destination.

      Analyzer-RAID-Agent-Installation-folder\htnm\Rest\config\htnm_httpsd.conf

      Analyzer-RAID-Agent-Installation-folder\htnm\HBasePSB\CC\server\usrconf\ejb\AgentRESTService\usrconf.properties

Recovering Analyzer detail view

To recover Analyzer detail view from a backup archive, see the Hitachi Ops Center Analyzer Installation and Configuration Guide.
Note: Private key files and server certificate files created or obtained by the user are not backed up. Depending on the location, the files might be included in the backup data; however, as a general rule, manually relocate the files when you recover.

Recovering Analyzer probe

To recover Analyzer probe from a backup archive, see the Hitachi Ops Center Analyzer Installation and Configuration Guide.

Note: Private key files and server certificate files created or obtained by the user are not backed up. Depending on the location, the files might be included in the backup data; however, as a general rule, manually relocate the files when you recover.

Recovering Analyzer viewpoint

To recover Analyzer viewpoint from a backup archive, run the following command:
  1. Run the following restore command.

    /opt/hitachi/analyzer_viewpoint/bin/restore --file {backup-archive-file-path}

For details, see the Hitachi Ops Center Analyzer Installation and Configuration Guide.

Note: Private key files and server certificate files created or obtained by the user are not backed up. Depending on the location, the files might be included in the backup data; however, as a general rule, manually relocate the files when you recover.

Recovering Analyzer Virtual Storage Software Agent

To recover Analyzer Virtual Storage Software Agent from a backup archive, complete the following steps:
  1. Extract the archive file. For the specific file path, see the Protector GUI.
  2. Copy the contents to the following directories:

    /var/{installation-directory}/system/access-points.yaml

    /var/{installation-directory}/config/userconfig-setting.yaml

For details, see the Hitachi Ops Center Analyzer Installation and Configuration Guide.

Note: Private key files and server certificate files created or obtained by the user are not backed up. Depending on the location, the files might be included in the backup data; however, as a general rule, manually relocate the files when you recover.

Recovering Analyzer On-demand real time monitoring module (Linux only)

To recover the Analyzer On-demand real time monitoring module for Linux from a backup archive, complete the following steps:
  1. Extract the archive file. For the specific file path, see the Protector GUI.
  2. Copy the contents to the following directories:

    /opt/hitachi/Analytics/granular-data-collection-api/conf/user-granular-data-collection-api.conf

    /opt/hitachi/Analytics/granular-data-collection-api/conf/system-granular-data-collection-api.conf

For details, see the Hitachi Ops Center Analyzer Installation and Configuration Guide.

Note: Private key files and server certificate files created or obtained by the user are not backed up. Depending on the location, the files might be included in the backup data; however, as a general rule, manually relocate the files when you recover.

Recovering Automator

  • Verify the following settings are the same between the backup source host and the restore destination host:
    • Host name and IP address
    • Account of the OS user used by Automator
    • Hitachi Ops Center product environment (configuration, version, and revision)
    • Installation path of Automator
    • System locale and character set
  • Verify that no tasks are currently being processed in the Automator "Status" column of the Tasks tab with a status of "In Progress", "Waiting for Input", "In Progress (with Error)", "Long Running", or "In Progress (Terminating)".
To recover Automator from a backup archive, complete the following steps:
  1. Run the tar command to extract the backup archive file:

    tar xvf backup-archive-file -C destination-file-path

  2. Run the restoresystem command:

    Automator-installation-directory/bin/restoresystem -dir destination-file-path -auto

For details about restoresystem command, see the Hitachi Ops Center Automator Installation and Configuration Guide.

Recovering API Configuration Manager

To recover API Configuration Manager from a backup archive, complete the following steps:
  1. Run the jar command to extract the backup archive file:
    Windows:
    Configuration-Manager-installation-directory\base\jdk\bin\jar xf backup-archive-file ConfManager
    Linux:
    Configuration-Manager-installation-directory/base/jdk/bin/jar xf backup-archive-file ConfManager
  2. Restore the extracted files. For details, see "Restoring the REST API database and environment settings file" in the Hitachi Ops Center API Configuration Manager REST API Reference Guide.
Note: Private key files and server certificate files created or obtained by the user are not backed up. Depending on the location, the files might be included in the backup data; however, as a general rule, manually relocate the files when you recover.

Recovering Common Services

Verify the installation path and version number of Common Services are the same between the backup source host and the restore destination host.
To recover Common Services from a backup archive, run the following csrestore command for the applicable data.

Common-Services-installation-directory/utility/bin/csrestore.sh -file backup-archive-file

For details, see Restoring Common Services.

Recovering Protector

To restore Protector from a backup archive, see the Hitachi Ops Center Protector User Guide.

Backing up and restoring Ops Center applications manually

You can back up and restore Ops Center applications manually.

You can also schedule backups using Ops Center Protector as described in Backing up and restoring Hitachi Ops Center applications using Protector.

Product Command Procedure
Ops Center Common Services
  1. Log in to the management server as the root user.
  2. Stop the Common Services service.
  3. Run the csbackup or csrestore command.

See Starting or stopping the Common Services service.

See Backing up Common Services.

See Restoring Common Services.

Ops Center Analyzer
  1. Stop each service in the following order and back up the setting information:
    • Analyzer viewpoint server
    • Analyzer server
    • Analyzer detail view server
    • Analyzer probe server
    • RAID Agent
  2. Back up and restore each of the Ops Center Analyzer components.
For details on backing up, see the Hitachi Ops Center Analyzer Installation and Configuration Guide.
Ops Center Administrator To back up:

Log in to Virtual Appliance Manager and click Backup to download a tar.gz file containing the system settings.

To restore:
  1. Log in to Virtual Appliance Manager and click Restore and either drag and drop the backup file or click the plus sign.
  2. Click Submit.
For details, see the Hitachi Ops Center Administrator User Guide.
Ops Center Automator To back up or restore the system configuration for Automator, use the backupsystem and restoresystem commands. For details, see the Hitachi Ops Center Automator Installation and Configuration Guide.
Ops Center Protector Use the mastersettings command to back up and restore the configuration settings of the master node. For details, see the Hitachi Ops Center Protector Installation and Configuration Guide.
Hitachi Ops Center API Configuration Manager

You must manually back up and restore the REST API files.

For details on backing up, see the Hitachi Ops Center API Configuration Manager Reference Guide.
Backing up and restoring Common Services
You can back up and restore Common Services system information.
Backing up Common Services
To back up data in Common Services, run the csbackup command. You can restore the backup data to an instance of Common Services in an environment that has the same installation configuration and version.
  1. As necessary, back up each product registered in Common Services.
    For details on how to back up each product, see the documentation for each product.
  2. Log in to the management server as the root user.
    If you log in as an ordinary user, use the sudo command to complete the following procedure as the root user.
  3. Stop the Common Services service.
  4. Run the csbackup command.
    Command location
    installation-directory-of-Common-Services/utility/bin/csbackup.sh
    Format
    csbackup.sh -dir backup-destination-directory
    Option
    -dir backup-destination-directory
    Specify the path to the directory that stores the backup data. A relative path can be specified. A backup file, with the following file name, is output to the specified directory.
    csbackup_YYYY-MM-DD-hh-mm-ss_VVRRSS.tar.gz

    VVRRSS indicates the version of Common Services.

    Example:
    If the version is 11.0.0-01, VVRRSS is 110001.
    Note: Each time data is backed up, the number of backup files increases. For this reason, if data is backed up regularly over a long period of time, the backup files might take up a large amount of disk space. Delete backup files that are no longer necessary.
  5. If the server certificate and secret key are stored in a location other than the following directory, manually back up the server certificate and secret key.
    /var/installation-directory-of-Common-Services/tls/
    Note: If SSL communication was set up by using the cssslsetup command, the secret key of the server certificate is stored in the location specified when the command was run.
  6. Start the Common Services service.
Restoring Common Services
To restore the Common Services backup data, run the csrestore command.
Make sure that the installation configuration and version of Common Services on the restoration-destination system are the same as those on the system where the backup was taken. You cannot restore backup data to a system that has a different installation configuration and version.
  1. Log in to the management server as the root user.
    If you log in as an ordinary user, use the sudo command to complete the following procedure as the root user.
  2. Stop the Common Services service.
  3. Run the csrestore command.
    Command location
    installation-directory-of-Common-Services/utility/bin/csrestore.sh
    Format
    csrestore.sh -file path-to-backup-file
    Option
    -file path-to-backup-file
    Specify the path to the backup file to be restored. A relative path can be specified.
  4. If the server certificate and secret key were stored in a location other than the following directory and backed up manually, store the server certificate and secret key in the same location that was used for backup:

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

    Note: If you set up SSL communication by using the cssslsetup command prior to performing backup, store the server certificate and the secret key in the location you specified.
  5. If the host name, IP address, or port number of Common Services at the restoration destination is changed, run the cschgconnect command to change the settings.
    For details on the cschgconnect command, see Changing the management server host name, IP address, or port number.
  6. Start the Common Services service.
  7. As necessary, restore the backup data for each product registered in Common Services.
    For details on the restoration method and the prerequisites for restoring backup data, see the documentation for each product.
  8. If any products are registered in Common Services, delete each product in the Hitachi Ops Center Portal, and then register the products in Common Services again.
    To re-register the products in Common Services, run the setupcommonservice command for each product. For details on the setupcommonservice command, see the documentation for each product.

Configuring key-based authentication for the Analyzer detail view server

You can configure the key-based authentication to download data on the Analyzer detail view server when data is directly uploaded to the Analyzer detail view server (without an intermediate FTP server).

Note: For best results:
  • Use unique SSH host keys for every host that is using SSH.
  • Implement an SSH key management solution.

If the SFTP server subsystem setting is configured as sftp internal-sftp in the /etc/ssh/sshd_config file, make sure that the following entry is also present in this file:

Match User meghadata
        ForceCommand internal-sftp -u 2
  1. Log on to the Analyzer detail view server through an SSH client (like putty) as a root user.
  2. Switch to the megha user:
    su - megha
  3. Generate a key for the megha user:
    ssh-keygen -t rsa -b key_length
    Note: Key length can be 2048 or 4096.
  4. Press Enter to save the key in the folllowing directory under the installation directory (default: /data):
    /Installation_directory/megha/.ssh/id_rsa
    For example:
    /data/megha/.ssh/id_rsa
  5. (Optional) Enter a passphrase and confirm it.
    Note:
    • You cannot use quotation marks or spaces at the beginning or end of a passphrase, nor can you use contiguous multiple spaces within a passphrase.
    • If you decide to use a passphrase, make sure you note it. You will need it when updating the data download settings.
    • If you do not want to enter passphrase, press Enter and confirm it. A blank value is set.
  6. Copy the public key:
    ssh-copy-id meghadata@localhost
  7. When prompted for the password, enter the meghadata user password.
  8. Switch to the root user:
    su - root
  9. Configure the SELinux security context in the /etc/selinux/targeted/contexts/files/file_contexts.local file for the following directories available under the Analyzer detail view server installation directory (default: /data).
    • /Installation_directory/meghadata/.ssh directory:
      For example:
      semanage fcontext -a -t ssh_home_t /data/meghadata/.ssh
    • /Installation_directory/meghadata/.ssh/authorized_keys file:

      For example:

      semanage fcontext -a -t ssh_home_t /data/meghadata/.ssh/authorized_keys
  10. Use the restorecon command to change file type to ssh_home_t for the following directories available under the Analyzer detail view server installation directory (default: /data):
    • /Installation_directory/meghadata/.ssh directory:
      For example:
      restorecon -R -v /data/meghadata/.ssh
    • /Installation_directory/meghadata/.ssh/authorized_keys file:

      For example:

      restorecon -R -v /data/meghadata/.ssh/authorized_keys
    • Verify the type has been changed to ssh_home_t:
      ls -Z -a /Installation_directory/meghadata/.ssh
      For example:
      ls -Z -a /data/meghadata/.ssh
  11. Restart the sshd service:
    service sshd restart
By default, password-based authentication is configured for downloading data to the Analyzer detail view server. If you want to switch to key-based authentication, see Updating the downloader on the Analyzer detail view server.

Configuring key-based authentication to transfer data directly from Analyzer probe server to Analyzer detail view server

Key-based authentication helps you to transfer data directly (without an intermediate FTP or FTPS server) from the Analyzer probe server to the Analyzer detail view server using the SFTP protocol with the meghadata user.
Note: For best results:
  • Use unique SSH host keys for every host that is using SSH.
  • Implement a SSH key management solution.

Follow these procedures to configure key-based authentication:

  1. Configure the Analyzer probe server
  2. Configure the Analyzer detail view server

Configure the Analyzer Probe server

Follow these steps:

  1. Log on to the Analyzer probe server through an SSH client (like putty) as a root user.
  2. Change ownership and permission of the .ssh directory available under the Analyzer probe server installation directory.
    chown megha:megha /Installation_directory/megha/.ssh
    
    chmod 700 /Installation_directory/megha/.ssh
    For example:
    chown megha:megha /home/megha/.ssh
    
    chmod 700 /home/megha/.ssh
  3. Switch to the megha user:
    su - megha
  4. Generate a key for the megha user using one of the following algorithms:
    • RSA:
      ssh-keygen -t rsa -b key_length
      Note: Key length can be 2048 or 4096.
      For example:
      ssh-keygen -t rsa -b 2048
    • ECDSA:
      ssh-keygen -t ecdsa -b 256
  5. Press Enter to save the key in the folllowing location:
    • RSA:
      /Installation_directory/megha/.ssh/id_rsa
      For example:
      /home/megha/.ssh/id_rsa
    • ECDSA:
      /Installation_directory/megha/.ssh/id_ecdsa
      For example:
      /home/megha/.ssh/id_ecdsa
  6. (Optional) Enter a passphrase and confirm it.
    Note: If you decide to use a passphrase, make sure you note it. You will need this when configuring the following settings on the Analyzer probe server to transfer data:
    • Configuring data transfer settings when setting up the Analyzer probe server
    • Adding a secondary Analyzer detail view server
    • Editing an Analyzer detail view server (primary and secondary)
  7. Copy the public key to the Analyzer detail view server:
    ssh-copy-id meghadata@Analyzer_detail_view_server_IP_address_or_hostname
    For example:
    ssh-copy-id meghadata@192.168.35.31
  8. When prompted for the password, enter the meghadata user password.
  9. (If you are using the ECDSA algorithm), do the following:
    1. Stop the crond service using the command:
      service crond stop
    2. Stop the Analyzer probe server using the command:
      /usr/local/megha/bin/megha-jetty.sh stop
    3. Verify that the services (including crond) are stopped using the commands:
      service crond status
      /usr/local/megha/bin/megha-jetty.sh status
    4. Add the ssh.private.key.file property in the custom.properties file:
      ssh.private.key.file=/Installation_directory/megha/.ssh/id_ecdsa
      For example:
      ssh.private.key.file=/usr/local/megha/.ssh/id_ecdsa
    5. Start the crond service using the command:
      service crond start
    6. Start the Analyzer probe server using the command:
      /usr/local/megha/bin/megha-jetty.sh start
    7. Verify that the services (including crond) are started using the commands:
      service crond status
      /usr/local/megha/bin/megha-jetty.sh status
    Note: If you want to switch from the ECDSA algorithm to RSA algorithm in the future, add a comment symbol (#) at the beginning of the following line in the custom.properties file:
    ssh.private.key.file=/usr/local/megha/.ssh/id_ecdsa

Configure the Analyzer detail view server

Follow these steps on the Analyzer detail view server:

  1. Log on to the Analyzer detail view server through an SSH client (like putty) as a root user.
  2. Configure the SELinux security context in the /etc/selinux/targeted/contexts/files/file_contexts.local file for the following directories available under the Analyzer detail view server installation directory (default: /data).
    1. /Installation_directory/meghadata/.ssh directory:
      For example:
      semanage fcontext -a -t ssh_home_t /data/meghadata/.ssh
    2. /Installation_directory/meghadata/.ssh/authorized_keys file:

      For example:

      semanage fcontext -a -t ssh_home_t /data/meghadata/.ssh/authorized_keys
  3. Change file type to ssh_home_t for the following directories available under the Analyzer detail view server installation directory (default: /data):
    1. /Installation_directory/meghadata/.ssh directory:
      For example:
      restorecon -R -v /data/meghadata/.ssh
    2. /Installation_directory/meghadata/.ssh/authorized_keys file:

      For example:

      restorecon -R -v /data/meghadata/.ssh/authorized_keys
    3. Verify if the type has been changed to ssh_home_t:
      ls -Z -a /Installation_directory/meghadata/.ssh

Make sure that you switch to the key-based authentication and SFTP protocol in the Analyzer probe UI (select Reconfigure > Analyzer detail view server > Server Details).

Registering Analyzer detail view server with Common Services

If you want to use Common Services installed on a different host, or you installed Analyzer detail view server using the installer, you must register Analyzer detail view server with Common Services.

Verify the following:
  • The host name of Common Services is resolvable from the Analyzer detail view server.
  • The Analyzer detail view server and Common Services are running.
  • SSL is configured for the Analyzer detail view server and Common Services.
  • A user account exists with Common Services that has Administrator permissions.
  1. Log on to the Analyzer detail view server through an SSH client (like putty) as a root user.
  2. Navigate to the following directory:
    /usr/local/megha/bin
  3. Run the setupcommonservice command to register the Analyzer detail view server with Common Services.
    /usr/local/megha/bin/setupcommonservice -csUri Common-Services-URL -csUsername Common-Services-user-name -appHostname Analyzer-detail-view-server-host-name-or-IP-address -appPort Analyzer-detail-view-server-port -appName product-name-to-display-in-the-portal -appDescription description-todisplay-in-the-portal
    

    Use the -help option for command usage information.

    The following is an example to register a new instance of Analyzer detail view server in Common Services:
    /usr/local/megha/bin/setupcommonservice -csUri https://myopscenter.com:443/portal -
    csUsername sysadmin -appHostname mydetailview.com -appPort 8443 -
    appName detailview_B -appDescription "detail view B"
    Note:
    • The Common-Services-user-name must not contain greater than and less than signs (< >), Square brackets ([ ]), spaces, double quotation mark ("), colon (:), or ampersand (&).
    • The Analyzer-detail-view-server-host-name-or-IP-address must contain the correct host name or IP address.
  4. Enter the password of the Common Services user.

Analyzer detail view server is shown in the Common Services.

Note: You cannot unregister a Hitachi Ops Center product using the setupcommonservice command. To delete products, use the Ops Center Portal.

Registering Analyzer probe server with Common Services

If you want to use Common Services installed on a different host, or you installed Analyzer probe server using the installer, you must register Analyzer probe server with Common Services.

Verify the following:
  • The host name of Common Services is resolvable from the Analyzer probe server.
  • The Analyzer probe server and Common Services are running.
  • SSL is configured for the Analyzer probe server and Common Services.
  • A user account exists with Common Services that has Administrator permissions.
  1. Log on to the Analyzer probe server through an SSH client (like putty) as a root user.
  2. Navigate to the following directory:
    /usr/local/megha/bin
  3. Run the setupcommonservice command to register Analyzer probe server with Common Services.
    /usr/local/megha/bin/setupcommonservice -csUri Common-Services-URL -csUsername Common-Services-user-name -appHostname Analyzer-probe-server-host-name-or-IP-address -appPort Analyzer-probe-server-port -appName product-name-to-display-in-the-portal -appDescription description-todisplay-in-the-portal
    

    Use the -help option for command usage information.

    The following is an example to register a new instance of Analyzer probe server in Common Services:
    /usr/local/megha/bin/setupcommonservice -csUri https://myopscenter.com:443/portal -
    csUsername sysadmin -appHostname myprobe.com -appPort 8443 -appName
    probe_B -appDescription "probe B"
    Note:
    • The Common-Services-user-name must not contain greater than and less than signs (< >), Square brackets ([ ]), spaces, double quotation mark ("), colon (:), and ampersand (&).
    • The Analyzer-detail-view-server-host-name-or-IP-address must contain the correct host name or IP address.
  4. Enter the password of the Common Services user.

Analyzer probe server is shown in the Common Services.

Note: You cannot unregister a Hitachi Ops Center product using the setupcommonservice command. To delete products, use the Ops Center Portal.

Updating the downloader on the Analyzer detail view server

You must update the downloader details on the Analyzer detail view server if any of the following conditions apply:

  • You are currently downloading the data from an intermediate FTP server and you need to update the connection details for the Analyzer detail view server or intermediate FTP server.
  • You are directly uploading data to the Analyzer detail view server (without an intermediate FTP server) and you want to switch between password-based authentication and key-based authentication.
Note: If you do not want to stop the crond service, you can stop specific processes of the Analyzer detail view server and Analyzer probe server by using the crontab -e command as described in Stopping the Analyzer detail view server or Analyzer probe server services and Starting the Analyzer detail view server or Analyzer probe server services
  1. Log on to the Analyzer detail view server through an SSH client (like putty) as a root user.
  2. Stop the crond service and verify the status with these commands:
    service crond stop
    service crond status
  3. Stop the megha service and verify the status with these commands:
    /usr/local/megha/bin/megha-jetty.sh stop
    /usr/local/megha/bin/megha-jetty.sh status
  4. Run the update FTP configuration script to update the FTP server details:
    • If you are downloading the data from an intermediate FTP server using the password-based authentication and you want to update its connection details:
      • To download data of all the Analyzer probe server appliances:
        sh /usr/local/megha/bin/createOrUpdateFTPConfiguration.sh --update --authType Password-Based --ftpServer FTP-server-hostname-or-IP-address --ftpMethod FTP-method-(FTP/FTPS/SFTP) --ftpPort FTP-port --ftpUsername FTP-username --ftpPassword

        For example:

        sh /usr/local/megha/bin/createOrUpdateFTPConfiguration.sh --update --authType Password-Based --ftpServer 192.168.1.2 --ftpMethod SFTP --ftpPort 22 --ftpUsername abc --ftpPassword
        Note:
        • The authType, ftpServer, and ftpUsername parameters are mandatory.
        • You cannot update the value of the ftpServer and ftpUsername parameters.
        • The value for the authType parameter must be Password-Based to download the data from an intermediate FTP server.
        • You can update the FTP server password, port, and FTP method. You can update all or one of these details. For example, if you want to update only the FTP method, enter only the ftpMethod parameter and its value.
        • You should use the ftpPassword parameter if you are downloading the data from an intermediate FTP server. To change the password, enter only the ftpPassword parameter. Do not enter any value for it. You can define the password in the next step.
      • To download the data of the specific Analyzer probe server appliance:
        sh /usr/local/megha/bin/createOrUpdateFTPConfiguration.sh --update --authType Password-Based --ftpServer FTP-server --ftpMethod FTP-method-(FTP/FTPS/SFTP) --ftpPort FTP-port --ftpUsername FTP-username --ftpPassword --applianceidOption ApplianceIds --applianceidList Appliance-ID-list-separated-by-comma

        For example:

        sh /usr/local/megha/bin/createOrUpdateFTPConfiguration.sh --update --authType Password-Based --ftpServer 192.168.1.2 --ftpMethod SFTP --ftpPort 22 --ftpUsername abc --ftpPassword --applianceidOption ApplianceIds --applianceidList 1c5fbdd9-8ed3-43fe-8973-e9cba6d103c6,39cfcb01-11b2-46b4-8fce-b4d84ea5acda
        
        Note:
        • The authType, ftpServer, and ftpUsername parameters are mandatory.
        • You cannot update the value of the ftpServer and ftpUsername parameters.
        • The value for the authType parameter must be Password-Based to download the data from an intermediate FTP server.
        • You can add new appliance IDs or you can remove the existing appliance IDs.
        • You can update the FTP server password, port, and FTP method. You can update all or one of these details. For example, if you want to update only the FTP method, enter only the ftpMethod parameter and its value.
        • You should use the ftpPassword parameter if you are downloading the data from an intermediate FTP server. To change the password, enter only the ftpPassword parameter. Do not enter any value for it. You can define the password in the next step.
    • To switch between password-based authentication and key-based authentication:
      • Switching to key-based authentication:
        sh /usr/local/megha/bin/createOrUpdateFTPConfiguration.sh --update --authType Key-Based --ftpServer localhost --ftpMethod SFTP --ftpPort FTP-Port --ftpUsername meghadata --keyPassphrase
        For example:
        sh /usr/local/megha/bin/createOrUpdateFTPConfiguration.sh --update --authType Key-Based --ftpServer localhost --ftpMethod SFTP --ftpPort 22 --ftpUsername meghadata --keyPassphrase
      • Switching to password-based authentication:
        sh /usr/local/megha/bin/createOrUpdateFTPConfiguration.sh --update --authType Password-Based --ftpServer localhost --ftpMethod FTP-method-(FTP/FTPS/SFTP) --ftpPort FTP-Port --ftpUsername meghadata --ftpPassword
        For example:
        sh /usr/local/megha/bin/createOrUpdateFTPConfiguration.sh --update --authType Password-Based --ftpServer localhost --ftpMethod SFTP --ftpPort 22 --ftpUsername meghadata --ftpPassword
      Note:
      • The authType, ftpServer and ftpUsername parameters are mandatory.
      • You cannot update the value of the ftpServer, ftpUsername, and ftpPassword parameters. If you want to change the ftpPassword of the meghadata user, use the changePassword.sh command. See Changing the megha and meghadata passwords for more information.
      • Key-based authentication only supports the SFTP method
      • You must enter the keyPassphrase parameter when switching to key-based authentication for the first time. When configuring key-based authentication to download data to Analyzer detail view server:
  5. Enter the passphrase or blank value if you have provided the keyPassphrase parameter or enter the meghadata user password if you have provided the ftpPassword parameter. For an intermediate FTP server, the passwords can contain uppercase and lowercase letters, numbers, and the following special characters: @, !, ~, #, $, `, %, ^, &, *, (, ), -, _, =, +, {, }, <, >, [, ], \
  6. Start the megha service and verify the status with these commands:
    /usr/local/megha/bin/megha-jetty.sh start
    /usr/local/megha/bin/megha-jetty.sh status
  7. Start the crond service and verify the status with these commands:
    service crond start
    service crond status
    

Changing the megha and meghadata passwords

You should change the megha and meghadata user passwords to enhance the security. The megha user exists on both the Analyzer detail view server and the Analyzer probe server. The Analyzer probe server does not have a meghadata account.

Note: You can also use this procedure if the current megha or meghadata user password has expired.

If a security policy for the maximum number of login attempts is enabled in your environment, you must disable it before changing the megha and meghadata passwords. After completing the procedure, you can re-enable the setting.

Note: If you do not want to stop the crond service, you can stop specific processes of the Analyzer detail view server and Analyzer probe server by using the crontab -e command as described in Stopping the Analyzer detail view server or Analyzer probe server services and Starting the Analyzer detail view server or Analyzer probe server services
  1. Log on to the Analyzer detail view server or Analyzer probe server through an SSH client (like putty) as a root user.
  2. Stop the crond service and verify the status with these commands:
    service crond stop
    service crond status
  3. Stop the megha service and verify the status with these commands:
    /usr/local/megha/bin/megha-jetty.sh stop
    /usr/local/megha/bin/megha-jetty.sh status
  4. Run the change password script:
    /usr/local/megha/bin/changePassword.sh --user
  5. Choose the account you want to change.
  6. Type the user password and confirm it.
    Note: Passwords can contain uppercase and lowercase letters, numbers, and the following special characters:

    @, !, ~, #, $, `, %, ^, &, *, (, ), -, _, =, +, {, }, <, >, [, ], \

  7. Start the megha service and verify the status with these commands:
    /usr/local/megha/bin/megha-jetty.sh start
    /usr/local/megha/bin/megha-jetty.sh status
  8. Start the crond service and verify the status with these commands:
    service crond start
    service crond status
    

If the Analyzer probe server is uploading the data directly to an Analyzer detail view server for which you have changed the meghadata user password, you must also update the meghadata user password on the Analyzer probe server. To change the password, log on to the Analyzer probe server and then go to the Home > Reconfigure > Analyzer detail view Server tab.

Stopping unnecessary product services

After deploying the Ops Center OVA, you can stop the services of products that you do not use, and specify not to start the services when the OS starts.

After the OVA is deployed, as a best practice, we recommend that you remove any products that are not being used. If you decide not to remove them, you can use the opsvmservicectl command to stop multiple product services at the same time. You can also use the command to change the setting so that the services do not start when the OS starts.

Note: The opsvmservicectl command is installed with version 10.1.0 or a later of the Ops Center OVA. If the individual installer or a version of the OVA earlier than 10.1.0 was used, uninstall any unnecessary products.

After you deploy the OVA and finish the configuration using the setup tool (opsvmsetup).

  1. From a VMware vSphere client, log in to the guest OS as the root user.
  2. Run the opsvmservicectl command to stop the services for the products that are not needed.
    Format
    opsvmservicectl {disable|enable} product-name [product-name ...]
    Options
    disable
    Stops the services for the specified products and prevents them from starting automatically when the OS starts. After you stop the services, the products remain registered in Common Services.
    enable
    Starts the services for the specified products and changes the setting so that the services automatically start when the OS starts.
    product-name

    Specify the target products by specifying the following values. To specify multiple products, use spaces to separate the products.

    Product name

    Value to specify

    Automator

    Automator

    Analyzer

    Analyzer

    Analyzer detail view

    AnalyzerDetailView

    API Configuration Manager

    APIConfigurationManager

    Protector

    Protector

    Administrator

    Administrator

    Common Services

    CommonServices
    Note: Do not perform an upgrade installation of a product that is disabled by using the opsvmservicectl command, because the product might not operate correctly.
  3. Check the results by running the following command:
    opsvmservicectl status
  4. To delete the products, log in to the Hitachi Ops Center Portal and remove them.

Resetting the trust relationship with each product

If unauthorized access to Common Services occurs or unauthorized operations are performed on the Common Services settings, information such as tokens exchanged between Common Services and each product might be leaked. In this case, reset and disable the information that might have been compromised.
  1. Log in to the management server as the root user.
    If you log in as an ordinary user, use the sudo command to complete the following procedure as the root user.
  2. Run the csresettrustrelationship command.
    Command location
    installation-directory-of-Common-Services/utility/bin/csresettrustrelationship.sh
    Format
    csresettrustrelationship.sh -f
    Option
    -f
    Specify this option if you run this command. If you omit this option, the command usage is displayed.
    Output file

    The results of running the command are output to the following file:

    /var/log/hitachi/CommonService/utility/result_reset_secert.json

    Note:
    • If you run this command, logged-in users might be forcibly logged out.
    • This command runs for a period from several minutes to several tens of minutes, depending on the system configuration.
    • When the command finishes running, Common Services restarts.
  3. Check the content of the output file.

    Make sure that the value of the status key is SUCCESS for both the resetSecretResult object and the resetKeyResult object.

    If the value is ERROR, restart Common Services, and then rerun the command. If this does not resolve the problem, collect the failure information, and contact customer support.

  4. If you are linking with the identity provider by using the SAML protocol, update the metadata for Common Services in identity provider.

    This step is required because when you reset the trust relationship, the authentication key of Common Services is forcibly updated.

    For details of the procedure, see one of the following topics, based on the linked identity provider:

  5. Run the csreregisterapp command or run the setupcommonservice command to re-register each product registered in Common Services.
    You can use the csreregisterapp command to re-register multiple products at once. For details, see Re-registering each product in Common Services.
  6. Restart the service of each product registered in Common Services.

Re-registering each product in Common Services

If you reset the trust relationships with each product, you must re-register each product registered in Common Services. If you use the csreregisterapp command, you can re-register each of the products in Common Services at once.

  • Run the csreregisterapp command on the management server where the product you want to re-register is installed. To run the command on a management server and Analyzer probe server where Common Services is not installed, obtain the csreregisterapp command in advance. You can obtain the csreregisterapp command by getting utility.tar from the following directories on the installation media and extracting the files:
    • root-directory-of-the-Common-Services-installation-media
    • root-directory-of-the-Server-Express-installer-media/COMMONSERVICES
    • root-directory-of-the-Client-Express-installer-media/COMMONSERVICES
  • To run the csreregisterapp command, the expect package must be installed. (The expect package is installed on management servers where Common Services version 11.0.4 or later is installed.)
  1. Log in to the management server as the root user.
    If you log in as an ordinary user, use the sudo command to complete the following procedure as the root user.
  2. Run the csreregisterapp command.
    Command location
    If Common Services is installed on the management server:
    installation-directory-of-Common-Services/utility/bin
    If Common Services is not installed on the management server:
    directory-where-utility.tar-is-extracted/utility/bin
    Format
    csreregisterapp.sh [-cshost host-name-or-IP-address-of-Common-Services] [-csport port-number-of-Common-Services] [-apphost host-name-or-IP-address-of-Product]
    Options
    -cshost host-name-or-IP-address-of-Common-Services
    Specify the host name (FQDN) or IP address for the URL to access Common Services. If you omit this option, the host name of the server on which the command was run will be specified. Specify this option if either of the following applies:
    • If you are specifying the host name in FQDN format or IP address for the URL to access Common Services
    • If the products to be re-registered and Common Services are installed on separate management servers
    -csport port-number-of-Common-Services
    Specify the port number for the URL to access Common Services. If you omit this option, 443 will be specified.
    -apphost host-name-or-IP-address-of-Product
    Specify the host name (FQDN) or IP address for the URL to access the product to be re-registered in Common Services. If you omit this option, the host name of the server on which the command was run will be specified. Specify this option if you specified a host name in FQDN format or IP address for the URL to access the product you want to re-register.
  3. Specify the user and password for Common Services.
    Specify a user who belongs to the opscenter-administrators group.
  4. When re-registering Administrator, specify whether to verify the SSL certificate for communications with Common Services. To perform verification, specify y, and then specify the root certificate of the certificate authority that signed the Common Services server certificate by using the absolute path.
  5. When you have finished running the command, the results will be displayed. Products for which failed is displayed could not be re-registered. Check the cause by referring to the log files in the following locations, and then rerun the command.
    If Common Services is installed on the management server:
    /var/log/hitachi/CommonService/utility/csreregisterapp_YYYY-MM-DD-hh-mm-ss.log
    If Common Services is not installed on the management server:
    /tmp/csreregisterapp_YYYY-MM-DD-hh-mm-ss.log
    Note: Products with warning displayed in the command execution results are successfully re-registered. However, the product names or product descriptions displayed on the Hitachi Ops Center Portal could not be carried over. In this case, the following information will be displayed in the Products window for items that are not carried over for the re-registered product:
    • Product name: The host name or IP address of the management server on which the re-registered product is installed will be displayed.
    • Product description: The content before re-registration will be deleted, leaving it in a not configured state.

    To reset the product name and product description, in the Products window on the Hitachi Ops Center Portal, click the Edit icon for the relevant product, and then manually specify the settings. For details about items that were set before re-registration, see the log file of the csreregisterapp command.

Configuring the settings for session idle timeout

After you log in to the Hitachi Ops Center Portal by using the single sign-on functionality of Common Services, if a specific amount of time elapses with no activity in the window, the session times out.

For the idle timeout settings, you can configure the following settings:

  • Idle timeout

    Specify the amount of time that can elapse with no activity in the window before a timeout occurs. The default is 20 minutes.

  • Auto refresh

    Specify whether a timeout occurs if the idle timeout time elapses with no operation performed for a window that automatically refreshes. By default, a timeout does not occur.

    These settings apply to the following products: Automator, Analyzer, and Analyzer viewpoint.

You can configure the idle timeout settings by using the Hitachi Ops Center Portal. The settings will apply to each Hitachi Ops Center product within a few minutes.

Note:
  • The idle timeout settings apply to Common Services and each Hitachi Ops Center product whose version is 10.9.0 or later (7.6.0 or later in the case of Protector). For Hitachi Ops Center products of a version earlier than 10.9.0 (earlier than 7.6.0 in the case of Protector), timeouts might not occur.
  • Actual session timeouts might differ by a few minutes from the configured idle timeout time.

Changing the scale of the resources managed by an individual product

On the management server where Common Services is installed, you can change the memory size to match the scale of the resources managed by a Hitachi Ops Center product. The target products are as follows:
  • Analyzer
  • Analyzer detail view
  • Analyzer viewpoint
  • Analyzer probe server
  1. Log in to the management server as the root user.
    If you log in as an ordinary user, use the sudo command to complete the following procedure as the root user.
  2. Run the cschgscale command.

    Run this command on the management server where the product that changes the scale of the resources is installed. For a management server where Common Services is not installed or the Analyzer probe server, obtain the command from the installation media. The locations of the command are as follows:

    • If Common Services is installed on the management server:

      installation-directory-of-Common-Services/utility/bin/cschgscale.sh

    • If Common Services is not installed on the management server:

      Expand utility.tar from the installation media.

      The utility.tar is located in the following directory:

      • root-directory-of-the-Common-Services-installation-media
      • root-directory-of-the-Server-Express-installer-media/COMMONSERVICES
      • root-directory-of-the-Client-Express-installer-media/COMMONSERVICES

      The cschgscale command is stored in the following directory after the files are extracted from utility.tar:

      directory-where-utility.tar-is-extracted/utility/bin

    Format
    cschgscale.sh {-scale scale-of-resources [-target Product-name] [-restart] | -h}
    Options
    -scale scale-of-resources

    Specify the scale of the resources. The memory size are changed according to the specified value. Specify one of the following values. The values are not case sensitive.

    • S: Small-scale configuration
    • M: Medium-scale configuration
    • L: Large-scale configuration
    Note:
    • You can check a detailed descriptions of the scales by using the -h option.
    • For details on the system requirements for each product according to the scale, see Hitachi Ops Center System Requirements.
    -target Product-name
    If you omit the -target option, all products targeted by the cschgscale command installed on the management server are changed. If you want to run the command for an individual product, specify the value as follows:
    • analyzer: Analyzer
    • detailview: Analyzer detail view
    • viewpoint: Analyzer viewpoint
    • probe: Analyzer probe server
    Note: The versions on which you can use the cschgscale command differ depending on the product. You can use this command on the following versions:
    • Analyzer, Analyzer viewpoint: 10.9.1 or later
    • Analyzer detail view, Analyzer probe server: 11.0.4 or later
    -restart
    Specify this option when you are changing the product settings and want to apply the changes immediately. If you specify this option, the product service is restarted after the command is run, and the changes are applied. For Analyzer viewpoint, the changes are applied immediately, so you do not need to specify -restart.
    -h

    Displays usage information. This option displays a description of the options, the names of installed products for which the command can be used, and details of the -scale option.

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-15/bin
  • installation-directory-of-Common-Services/nginx/temp
  • /var/installation-directory-of-Common-Services
For details on the directories of other Hitachi Ops Center products to exclude from the scanning targets, see the manual for each product.

Applying Linux security updates using yum

You can collectively (or selectively) apply OS security updates using the yum command. First, you must configure your server to access the RPM packages from the Linux OS media or the distribution website.

Accessing the RPM packages using the Linux OS media

  1. Mount the Linux OS media and obtain the RPM packages:
    mkdir /media/OSImage
    mount /dev/cdrom /media/OSImage
  2. Configure the yum repository.
    touch /etc/yum.repos.d/OSImage.repo
    echo [dvd-baseos]>>/etc/yum.repos.d/OSImage.repo
    echo name=dvd-baseos>>/etc/yum.repos.d/OSImage.repo
    echo baseurl=file:///media/OSImage/BaseOS/>>/etc/yum.repos.d/OSImage.repo
    echo gpgcheck=0>>/etc/yum.repos.d/OSImage.repo
    echo enabled=1>>/etc/yum.repos.d/OSImage.repo
    echo >>/etc/yum.repos.d/OSImage.repo
    echo [dvd-appstream]>>/etc/yum.repos.d/OSImage.repo
    echo name=dvd-appstream>>/etc/yum.repos.d/OSImage.repo
    echo baseurl=file:///media/OSImage/AppStream/>>/etc/yum.repos.d/OSImage.repo
    echo gpgcheck=0>>/etc/yum.repos.d/OSImage.repo
    echo enabled=1>>/etc/yum.repos.d/OSImage.repo

Accessing the RPM packages using the distribution website

  1. Specify the repository to which the yum command will connect.
  2. If you are using a proxy, specify the proxy for the yum command:
    1. Add the following information to the /etc/yum.conf file:
      proxy=http://host-name:port-number
      proxy_username=user-name
      proxy_password=password
    2. Clear the cache for the yum command.
      yum clean all

Using the yum command

To update all packages for which security-related errata are available (including packages with bug fixes or new features without security errata):

yum --security --exclude kernel* --exclude *podman* --exclude *containers-common* upgrade

To update all packages for which security-related errata are available (ignoring any newer packages without security errata):

yum --security --exclude kernel* --exclude *podman* --exclude *containers-common* upgrade-minimal

To update all kernel and podman packages to the latest supported versions that contain security errata, follow these examples.

For Red Hat kernel (must specify supported kernel version):

yum --security upgrade-minimal kernel-4.18.0-305.*

For Unbreakable Enterprise kernel (must specify supported uek kernel version):

yum --security upgrade-minimal kernel-uek-5.4.17-2102.*

For podman (must specify supported podman version):

yum --security upgrade-minimal podman-3.3.*

You can also update only those packages that correspond to a CVE or erratum, as in the following examples:

yum --cve CVE-2021-37576 upgrade-minimal

For Red Hat Enterprise Linux:

yum --advisory RHSA-2021:4056 upgrade-minimal

For Oracle Linux:

yum --advisory ELSA-2021-9474 upgrade-minimal

Replacing Command Control Interface

You can replace an individually installed instance of Command Control Interface with an instance of Command Control Interface installed by the Express installer, or replace an instance of Command Control Interface installed by the Express installer with an individually installed instance of Command Control Interface.

Switching to an instance of Command Control Interface installed by the Express installer

You can replace an individually installed instance of Command Control Interface with that installed by the Express installer.
  1. If API Configuration Manager or Protector is installed, stop the service.
    For details on how to stop the service, see the manual for the relevant product.
  2. Run the ps command to check for Command Control Interface processes that are running.
    ps aux
    From the list that appears, look for items in the format horcmd_number. (There might be more than one such item.)
  3. If any processes are running, run the following command to stop the Command Control Interface service:
    In the following, number consists of the fixed value 0 and instance-number. If there are multiple items in the format horcmd_number, specify each of instance-number separated by a space.
    horcmshutdown.sh instance-number
  4. Run the following command to uninstall Command Control Interface:
    /HORCM/horcmuninstall.sh
  5. Run the following command to delete the Command Control Interface installation directory:
    rm -rf $(readlink /HORCM)
  6. Run the following command to delete the Command Control Interface symbolic link:
    rm /HORCM
  7. Use the Express installer to install Command Control Interface. Select API Configuration Manager or Protector as the product to be installed and then perform the installation.

Switching to an individually installed instance of Command Control Interface

You can replace an instance of Command Control Interface installed by the Express installer with an individually installed instance.
  1. If API Configuration Manager or Protector is installed, stop the service.
    For details on how to stop the service, see the manual for the relevant product.
  2. Run the ps command to check for Command Control Interface processes that are running.
    ps aux
    From the list that appears, look for items in the format horcmd_number. (There might be more than one such item.)
  3. If any processes are running, run the following command to stop the Command Control Interface service:
    In the following, number consists of the fixed value 0 and instance-number. If there are multiple items in the format horcmd_number, specify each of instance-number separated by a space.
    horcmshutdown.sh instance-number
  4. Run the following command to uninstall Command Control Interface:
    /HORCM/horcmuninstall.sh
  5. Run the following command to delete the Command Control Interface installation directory:
    rm -rf $(readlink /HORCM)
  6. Run the following command to delete the Command Control Interface symbolic link:
    rm /HORCM
  7. Install Command Control Interface.
    For details on the installation method, see the Command Control Interface manual.
  8. Start the service of API Configuration Manager or Protector.
    For details on how to start the service, see the manual for the relevant product.

Upgrading Amazon Corretto 21

If a vulnerability is found in Amazon Corretto 21, upgrade Amazon Corretto 21.
  1. Log in to the management server as the root user.
    If you log in as an ordinary user, use the sudo command to complete the following procedure as the root user.
  2. Download Amazon Corretto 21, and store it on the management server where Common Services is installed.
    For details on the versions of Amazon Corretto 21 that are supported by Common Services, see the Hitachi Ops Center Release Notes.
  3. Stop the Common Services service.
    Note: If products that use Amazon Corretto 21 are installed on the management server, stop the services of those products as needed.
  4. Run the rpm command with the --nopost option specified to upgrade Amazon Corretto 21.
  5. Start the Common Services service.
    Note: If products that use Amazon Corretto 21 are installed on the management server, start the services of those products as needed.

Upgrading PostgreSQL 15

If a vulnerability is found in PostgreSQL 15, upgrade PostgreSQL 15.
  1. Log in to the management server as the root user.
    If you log in as an ordinary user, use the sudo command to complete the following procedure as the root user.
  2. Download PostgreSQL 15, and store it on the management server where Common Services is installed.
    For details on the versions of PostgreSQL 15 that are supported by Common Services, see the Hitachi Ops Center Release Notes.
  3. Stop the Common Services service.
  4. Run the following command to stop the Common Services database:
    systemctl stop postgresql-15@csportal.service postgresql-15@csidp.service
  5. Run the rpm command to upgrade the RPM package for PostgreSQL 15.
    rpm -Uv PostgreSQL-15-package-name postgresql15-libs-package-name postgresql15-server-package-name
  6. Run the following command to start the Common Services database:
    systemctl start postgresql-15@csportal.service postgresql-15@csidp.service
  7. Start the Common Services service.

Troubleshooting

Check the messages or log files to determine the cause of the error and take action. If you cannot determine the cause or resolve the error, collect the maintenance information about the management server and Common Services, and then contact support personnel.

Collecting failure information

If a failure occurs while using Hitachi Ops Center, collect the failure information required to analyze the cause.
  1. Log in to the management server as the root user.
    If you log in as an ordinary user, use the sudo command to complete the following procedure as the root user.
  2. To collect the failure information of Common Services, run the csgetras command.
    Command location
    installation-directory-of-Common-Services/utility/bin/csgetras.sh
    Format
    csgetras.sh -dir path-to-output-destination-directory
    Option
    -dir path-to-output-destination-directory

    Specify the path to the directory to which the collected failure information is output. A relative path can be specified.

    If you run the command, a file that compresses and archives the collected information is created.

  3. As necessary, collect the failure information of each product registered in Common Services and the Server Express installer.
    For details on how to collect failure information, see the documentation for each product.

    For failure information for the Server Express installer, manually save the following log files.

    Log file

    Location

    Description

    ExpressInstaller_version.hv_yyyymmdd-hhmmss.log

    /tmp

    The log file of the Server Express installer.

    ExpressInstaller_version.product-name_yyyymmdd-hhmmss.log

    /tmp

    The log files for the standard output displayed during the installation of products selected in the Server Express installer.

    For product-name, one of the following strings is output:

    • commonservices: Common Services
    • administrator: Administrator
    • ConfManager: API Configuration Manager
    • protector: Protector
    • automator: Automator
    • analyzer: Analyzer
    • detailview: Analyzer detail view
    • viewpoint: Analyzer viewpoint
    • CCI: Command Control Interface

    ExpressInstaller_version.command-name_yyyymmdd-hhmmss.log

    /tmp

    The log file output when a command is run by the Server Express installer.

    For command-name, the following string is output:
    • cschgscale: Output when a product is newly installed and resources have been configured.

    COMSERV_Report.txt

    /var/log/hitachi/CommonService/inst

    Installation report file that is output if Common Services is installed.

  4. To collect the following failure information for work performed on a server where Common Services is not installed, log in to the server:
    • Client Express installer
    • SSL Setup tool (Use the cssslsetup command in utility.tar.)
    • csreregisterapp command (Use the command in utility.tar.)
    • cschgscale command (Use the command in utility.tar.)
    Manually save the following log files.

    Log file

    Location

    Description

    ClientExpressInstaller_version.hv_yyyymmdd-hhmmss.log

    /tmp

    The log file of the Client Express installer.

    ClientExpressInstaller_version.product-name_yyyymmdd-hhmmss.log /tmp

    The log files for the standard output displayed during the installation of products selected in the Client Express installer.

    For product-name, one of the following strings is output:

    • probe: Analyzer probe server
    • ConfManager: API Configuration Manager
    • protector: Protector Client
    • CCI: Command Control Interface

    ClientExpressInstaller_version.command-name_yyyymmdd-hhmmss.log

    /tmp

    The log file output when a command is run by the Client Express installer.

    For command-name, the following string is output:

    • cschgscale: Output when a product is newly installed and resources have been configured.

    command-name_YYYY-MM-DD-hh-mm-ss.log

    /tmp This is the log file that is output when a command is run.

    For command-name, the following string is output:

    • cssslsetup
    • csreregisterapp
    • cschgscale

Collecting Ops Center log files

The following table provides the commands for collecting log files from Ops Center component products.

Product Command
Ops Center Common Services installation-directory-of-Common-Services/utility/bin/csgetras.sh -dir output-directory-path
Ops Center Analyzer Common-component-installation-destination-directory/bin/hcmds64getlogs -dir output-directory-path
Ops Center Analyzer viewpoint /opt/hitachi/analyzer_viewpoint/bin/diag
Ops Center Analyzer detail view

Analyzer probe server

Obtain the log files from the UI.
Ops Center Analyzer RAID Agent /opt/jp1pc/tools/jpcras output-directory-path-all all
Ops Center Administrator

/opt/rainier/bin/rainier-getlogs -dir [output-directory]

Check the location of collected log file (rainier-logs.tar.gz).

Ops Center Automator

Windows:

Common-component-installation-destination-directory\bin\hcmds64getlogs /dir output-directory-path

Linux:

Common-component-installation-destination-directory/bin/hcmds64getlogs -dir output-directory-path
Ops Center Protector

Collect a mini diagnostic log from a node:

diagdata --mini

Collect a full diagnostic log from a node:

diagdata --full

Ops Center API Configuration Manager

Windows:

REST-API-installation-destination\SupportTools\CollectTool\RestTI.bat -dir omaintenance-information-storage-destination

Linux:

REST-API-installation-destination/SupportTools/CollectTool/RestTI.sh -dir omaintenance-information-storage-destination

Common Services logs

In Common Services, log files are output and can be used to analyze the causes of failures that occur.

Three types of log files are output for Common Services.

Output-destination directory
/var/log/hitachi/CommonService
Log files

Log file

Description

error.log

The Common Services error log is output to this file. Check the contents of this file as needed.

debug.log

This log file is necessary for customer support to analyze the cause of a failure when, for example, you cannot identify the cause or cannot perform recovery.

server.log

This log file is necessary for customer support to analyze the cause of a failure when, for example, you cannot identify the cause or cannot perform recovery.

The following items are output to error.log.

Item

Description

Date and time

The date and time when the log was output

Level

The log level

Thread name

The name of the internal processing of Common Services

Message ID

The message ID in the following format.

KAOPnnnnn-Z

In the above, nnnnn is the message number.

Z is the message type.
  • E: Error message
  • W: Warning message
  • I: Information

Message

The message corresponding to the message ID

Exception

Information about the exception that occurred

Changing the properties of logs
You can change the properties of Common Services logs to change how the logs are output.
  1. Log in to the management server as the root user.
    If you log in as an ordinary user, use the sudo command to complete the following procedure as the root user.
  2. Edit the following properties file.

    /var/installation-directory-of-Common-Services/userconf/config_user.properties

    The properties of logs are as follows:

    Property

    Description

    CS_PORTAL_LOG_LEVEL_DEBUG

    Specify the level for which the debug log is to be output.

    You can specify one of the following values (listed in descending order of detail level): TRACE, DEBUG, and INFO.

    Default value: DEBUG

    CS_PORTAL_LOG_MAX_FILESIZE

    Specify the maximum size of each log file.

    When the size of a log file exceeds the specified size, a new log file is created.

    The value of this property must be specified in the form of an integer and a unit.

    You can specify KB, MB, or GB for the unit. KB, MB, and GB correspond to KiB, MiB, and GiB, respectively. If you do not specify a unit, the unit is assumed to be bytes.

    Default value: 20MB

    CS_PORTAL_LOG_MAX_INDEX_ERROR

    Specify the maximum number of error log backups to keep.

    When the error log file reaches the maximum size specified for the CS_PORTAL_LOG_MAX_FILESIZE property, a backup of the file is created, where the name of the backup file is the original file name with a number appended to the end. Each time the log file reaches the maximum size, a new backup file is created until the number of backup files reaches the number specified for this property. After this number of backup files is reached, each time a new backup file is created, the oldest backup file is deleted.

    You can specify a value in the range from 1 to 21.

    Default value: 10

    CS_PORTAL_LOG_MAX_INDEX_DEBUG

    Specify the maximum number of debug log backups to keep.

    When the debug log file reaches the maximum size specified for the CS_PORTAL_LOG_MAX_FILESIZE property, a backup of the file is created, where the name of the backup file is the original file name with a number appended to the end. Each time the log file reaches the maximum size, a new backup file is created until the number of backup files reaches the number specified for this property. After this number of backup files is reached, each time a new backup file is created, the oldest backup file is deleted.

    You can specify a value in the range from 1 to 21.

    Default value: 20

    CS_PORTAL_LOG_MAX_INDEX_APPLOG

    Specify the maximum number of server log backups to keep.

    When the server log file reaches the maximum size specified for the CS_PORTAL_LOG_MAX_FILESIZE property, a backup of the file is created, where the name of the backup file is the original file name with a number appended to the end. Each time the log file reaches the maximum size, a new backup file is created until the number of backup files reaches the number specified for this property. After this number of backup files is reached, each time a new backup file is created, the oldest backup file is deleted.

    You can specify a value in the range from 1 to 21.

    Default value: 20

  3. Restart the Common Services service.

Common Services audit log

Common Services can output audit log information about who performed which operation and when. By default, the audit log output is disabled, but you can enable it and change the properties as needed.

Output destination

The audit log is output to the syslog.

Output items

The following items are output to the audit log.

Location

Item

Description

Example

PRI

Priority

A number that indicates the priority level.

This number is converted from the facility value and the log level. The facility value is converted based on the value set for the CS_PORTAL_AUDIT_FACILITY property.

<11>

HEADER

Date and time

The date and time when the auditing event occurred

Sep 2 13:15:04

Host name

The name of the host for which the auditing event occurred

WIN-00ABCD11EFG

MSG

Process ID

The process ID

5828

Thread ID

The thread ID

http-nio-8081-exec-2

Log level

The log level, such as ERROR or DEBUG

ERROR

Date and time

The date and time when the audit log was output

2019-09-02T13:15:04.362+0900

Message ID

The message ID

KAOP91111-E

Type of auditing event

The auditing event type, such as StartStop or Authentication

Authentication

Result of the auditing event

The result of the event, such as whether the event was successful or not

Success

Subject-identifying information

Information such as the user ID or a URI

User ID=system,URI=/portal

Message

The message

KAOP91111-E Audit Log.

The auditing event types that are output and their corresponding severity levels are as follows. You can change the properties of the audit log to narrow down the severity levels that are output.

Type of auditing event

Description

Corresponding severity level

Authentication

Indicates an auditing event that is related to login or authentication

If the event is successful: 6

If the event fails: 4

ConfigurationAccess

Indicates an auditing event that is related to the creation, referencing, modification, or deletion of a user account or user group

If the event is successful: 6

If the event fails: 3

Auditing events output to the audit log

Common Services outputs the following types of auditing events to the audit log. A message to be output consists of a message ID and message text.

The following shows the message ID format:

prefixNNNNN-x

A message ID consists of the following elements:

prefix
Indicates the component from which the message is output. The prefix of audit log messages is KAOP.
NNNNN

Indicates the serial number of the message. The serial number differs depending on the type.

  • KAOP9800N: Authentication message
  • KAOP90NNN: ConfigurationAccess message
x

Indicates the message type. The following shows the message types and their meanings:

  • E (Error): Message that notifies users of an error that prevents processing from continuing
  • I (Information): Message that notifies users of information

If the auditing event type is Authentication:

Detailed type

Auditing event

Message

User authentication

Successful login

KAOP98001-I,Authentication,Success,type=LOGIN

Login error

KAOP98002-E,Authentication,Failed,type=LOGIN_ERROR

Successful logout

KAOP98001-I,Authentication,Success,type=LOGOUT

Logout error

KAOP98002-E,Authentication,Failed,type=LOGOUT_ERROR

Profile

Successful account editing

KAOP98001-I,Authentication,Success,type=UPDATE_PROFILE

Account editing error

KAOP98002-E,Authentication,Failed,type=UPDATE_PROFILE_ERROR

Successful password change

KAOP98001-I,Authentication,Success,type=UPDATE_PASSWORD

Password change error

KAOP98002-E,Authentication,Failed,type=UPDATE_PASSWORD_ERROR

  • For the audit log, message IDs other than those listed in this table are also output from the internal processing of Common Services.
  • Based on the message ID and the type value, determine each event in the auditing log.

If the auditing event type is ConfigurationAccess:

Detailed type

Auditing event

Message

User

Successful user creation

KAOP90001-I

User creation error

KAOP90002-E

Successful acquisition of a user list

KAOP90003-I

Error obtaining a user list

KAOP90004-E

Successful acquisition of information about a specific user

KAOP90005-I

Error obtaining information about a specific user

KAOP90006-E

Successful update of information about a specific user

KAOP90007-I

Error updating information about a specific user

KAOP90008-E

Successful user deletion

KAOP90009-I

User deletion error

KAOP90010-E

Successful acquisition of a list of user groups to which a specific user belongs

KAOP90011-I

Error obtaining a list of user groups to which a specific user belongs

KAOP90012-E

User group

Successful addition of users to a user group

KAOP90013-I

Error adding users to a user group

KAOP90014-E

Successful deletion of users from a user group

KAOP90015-I

Error deleting users from a user group

KAOP90016-E

Successful reset of a user password

KAOP90017-I

Error resetting a user password

KAOP90018-E

Successful registration of a user group

KAOP90019-I

Error registering a user group

KAOP90020-E

Successful acquisition of a user group list

KAOP90021-I

Error obtaining a user group list

KAOP90022-E

Successful update of registered information of a user group

KAOP90023-I

Error updating registered information of a user group

KAOP90024-E

Successful acquisition of information about a specific user group

KAOP90025-I

Error obtaining information about a specific user group

KAOP90026-E

Successful deletion of a user group

KAOP90027-I

Error deleting a user group

KAOP90028-E

Successful acquisition of a list of users who belong to a specific user group

KAOP90029-I

Error obtaining a list of users who belong to a specific user group

KAOP90030-E

Successful acquisition of a list of roles assigned to a specific user group

KAOP90031-I

Error obtaining a list of roles assigned to a specific user group

KAOP90032-E

Successful assignment of roles to a user group

KAOP90033-I

Error assigning roles to a user group

KAOP90034-E

Successful deletion of roles assigned to a user group

KAOP90035-I

Error deleting roles assigned to a user group

KAOP90036-E

Successful acquisition of a list of roles that can be assigned to a specific user group

KAOP90037-I

Error obtaining a list of roles that can be assigned to a specific user group

KAOP90038-E

User directory

Successful registration of an Active Directory or LDAP server

KAOP90039-I

Error registering an Active Directory or LDAP server

KAOP90040-E

Successful acquisition of an Active Directory or LDAP server list

KAOP90041-I

Error obtaining an Active Directory or LDAP server list

KAOP90042-E

Successful acquisition of information about a specific Active Directory or LDAP server

KAOP90043-I

Error obtaining information about a specific Active Directory or LDAP server

KAOP90044-E

Successful update of information about an Active Directory or LDAP server

KAOP90045-I

Error updating information about an Active Directory or LDAP server

KAOP90046-E

Successful deletion of information about an Active Directory or LDAP server

KAOP90047-I

Error deleting information about an Active Directory or LDAP server

KAOP90048-E

Successful synchronization of user groups

KAOP90049-I

Error synchronizing user groups

KAOP90050-E

Successful implementation of the connection and authentication tests of an Active Directory server

KAOP90051-I

Error implementing the connection and authentication tests of an Active Directory server

KAOP90052-E

setupcommonservice command of each product

Successful registration of a product

KAOP90053-I

Error registering a product

KAOP90054-E

Product

Successful acquisition of a list of products registered in Common Services

KAOP90055-I

Error obtaining a list of products registered in Common Services

KAOP90056-E

Successful acquisition of information about a specific product registered in Common Services

KAOP90057-I

Error obtaining information about a specific product registered in Common Services

KAOP90058-E

Successful update of registered information of a product

KAOP90059-I

Error updating registered information of a product

KAOP90060-E

Successful deletion of a product

KAOP90061-I

Error deleting a product

KAOP90062-E

Successful acquisition of configuration information of a specific product registered in Common Services

KAOP90063-I

Error obtaining configuration information of a specific product registered in Common Services

KAOP90064-E

Successful acquisition of version information of a specific product registered in Common Services

KAOP90065-I

Error obtaining version information of a specific product registered in Common Services

KAOP90066-E

Successful acquisition of status information of a specific product registered in Common Services

KAOP90067-I

Error obtaining status information of a specific product registered in Common Services

KAOP90068-E

Successful acquisition of license information of a specific product registered in Common Services

KAOP90069-I

Error obtaining license information of a specific product registered in Common Services

KAOP90070-E

Data Center

Successful registration of a data center

KAOP90071-I

Error registering a data center

KAOP90072-E

Successful acquisition of a data center list

KAOP90073-I

Error obtaining a data center list

KAOP90074-E

Successful acquisition of information about a specific data center

KAOP90075-I

Error obtaining information about a specific data center

KAOP90076-E

Successful update of registered information of a data center

KAOP90077-I

Error updating registered information of a data center

KAOP90078-E

Successful deletion of a data center

KAOP90079-I

Error deleting a data center

KAOP90080-E

Successful acquisition of a list of products registered in a specific data center

KAOP90081-I

Error obtaining a list of products registered in a specific data center

KAOP90082-E

Successful registration of products registered in Common Services to a data center

KAOP90083-I

Error registering products registered in Common Services to a data center

KAOP90084-E

Successful deletion of products registered in Common Services from a data center

KAOP90085-I

Error deleting products registered in Common Services from a data center

KAOP90086-E

Password policy

Successful acquisition of the password policy

KAOP90087-I

Error obtaining the password policy

KAOP90088-E

Successful update of the password policy

KAOP90089-I

Error updating the password policy

KAOP90090-E

Warning banner

Successful acquisition of the banner

KAOP90091-I

Error obtaining the banner

KAOP90092-E

Successful update of the banner

KAOP90093-I

Error updating the banner

KAOP90094-E

Successful preview of the banner

KAOP90095-I

Error previewing the banner

KAOP90096-E

Successful acquisition of the banner tag

KAOP90097-I

Error obtaining the banner tag

KAOP90098-E

Version information

Successful acquisition of version information of Common Services

KAOP90099-I

Error obtaining version information of Common Services

KAOP90100-E

Access token

Successful acquisition of the access token

KAOP90103-I

Error obtaining the access token

KAOP90104-E

Successful acquisition of information about the user who obtained the access token

KAOP90105-I

Error obtaining information about the user who obtained the access token

KAOP90106-E

Periodic running by a registered product

Successful notification of the status of a linked product

KAOP90109-I

Error reporting the status of a linked product

KAOP90110-E

Login

Successful acquisition of the logged-in user's profile

KAOP90111-I

Error obtaining the logged-in user's profile

KAOP90112-E

Login banner

Successful acquisition of the login banner

KAOP90113-I

Error obtaining the login banner

KAOP90114-E

Checking the session and token status during use of the GUI

Successful acquisition of the logged-in user status

KAOP90115-I

Error obtaining the logged-in user status

KAOP90116-E

Product deletion

Error notifying a product of deletion

KAOP90125-W

Kerberos connection settings

Successful acquisition of information about the Kerberos authentication connection

KAOP90126-I

Error obtaining information about the Kerberos authentication connection

KAOP90127-E

Successful update of the Kerberos connection settings

KAOP90128-I

Error updating the Kerberos connection settings

KAOP90129-E

Successful creation of a Kerberos realm

KAOP90130-I

Error creating a Kerberos realm

KAOP90131-E

Successful deletion of a Kerberos realm

KAOP90132-I

Error deleting a Kerberos realm

KAOP90133-E

Successful acquisition of information about a specific realm for Kerberos authentication

KAOP90134-I

Error obtaining information about a specific realm for Kerberos authentication

KAOP90135-E

Successful acquisition of a list of information about Kerberos authentication realms

KAOP90136-I

Error obtaining a list of information about Kerberos authentication realms

KAOP90137-E

Successful update of Kerberos realm information

KAOP90138-I

Error updating Kerberos realm information

KAOP90139-E

Identity provider

Successful import of metadata

KAOP90172-I

Error importing metadata

KAOP90173-E

Successful registration of an identity provider

KAOP90174-I

Error registering an identity provider

KAOP90175-E

Successful export of metadata

KAOP90176-I

Error exporting metadata

KAOP90177-E

Successful acquisition of an identity provider list

KAOP90178-I

Error obtaining an identity provider list

KAOP90179-E

Successful acquisition of information about a specific identity provider

KAOP90180-I

Error obtaining information about a specific identity provider

KAOP90181-E

Successful update of registered information of an identity provider

KAOP90182-I

Error updating registered information of an identity provider

KAOP90183-E

Successful deletion of an identity provider

KAOP90184-I

Error deleting an identity provider

KAOP90185-E

Authentication key

Successful acquisition of the authentication key settings

KAOP90186-I

Error obtaining the authentication key settings

KAOP90187-E

Successful update of the update interval of the authentication key

KAOP90188-I

Error updating the update interval of the authentication key

KAOP90189-E

Successful update of the authentication key

KAOP90190-I

Error updating the authentication key

KAOP90191-E

User directory

Successful synchronization of all users of an external authentication server

KAOP90192-I

Error synchronizing all users of an external authentication server

KAOP90193-E

Successful check of the number of users obtained from an Active Directory or LDAP server

KAOP90196-I

Error checking the number of users obtained from an Active Directory or LDAP server

KAOP90197-E

Product

Successful acquisition of session information of the product

KAOP90198-I

Error obtaining session information of the product

KAOP90199-E

Session control

Successful acquisition of information about the session settings

KAOP90200-I

Error obtaining information about the session settings

KAOP90201-E

Successful update of information about the session settings

KAOP90202-I

Error updating information about the session settings

KAOP90203-E

Changing the audit log properties
You can change the Common Services audit log properties to change the output.
  1. Log in to the management server as the root user.
    If you log in as an ordinary user, use the sudo command to complete the following procedure as the root user.
  2. Edit the following properties file.

    /var/installation-directory-of-Common-Services/userconf/config_user.properties

    The properties of the audit log are as follows:

    Property

    Description

    CS_PORTAL_AUDIT_ENABLE

    Specify one of the following values to indicate whether to generate the audit log.

    • true: Generate the audit log.
    • false: Do not generate the audit log.

    Default value: false

    CS_PORTAL_AUDIT_SYSLOGHOST

    If you want audit logs output to a server other than the management server on which Common Services is installed, specify the host name or IP address of that server.

    Default value: localhost

    CS_PORTAL_AUDIT_PORT

    Specify the port number of the syslog server.

    Communication with the syslog server is over UDP. TCP is not supported.

    Default value: 514

    CS_PORTAL_AUDIT_FACILITY

    Specify the information needed to identify the sender of a message.

    You can specify the following values:

    • KERN
    • USER
    • MAIL
    • DAEMON
    • AUTH
    • SYSLOG
    • LPR
    • NEWS
    • UUCP
    • CRON
    • AUTHPRIV
    • FTP
    • NTP
    • AUDIT
    • ALERT
    • CLOCK
    • LOCAL0
    • LOCAL1
    • LOCAL2
    • LOCAL3
    • LOCAL4
    • LOCAL5
    • LOCAL6
    • LOCAL7

    Default value: USER

    CS_PORTAL_AUDIT_LEVEL

    Specify the severity levels to include in the audit log output.

    You can specify the following values.

    • DEBUG: Output the audit log for severity levels 0 to 7.
    • INFO: Output the audit log for severity levels 0 to 6.
    • WARN: Output the audit log for severity levels 0 to 4.
    • ERROR: Output the audit log for severity levels 0 to 3.

    Default value: INFO

  3. Restart the Common Services service.

Collecting the log file for the Analyzer server

Run the hcmds64getlogs command to collect the log file for the Analyzer server.

  1. Log on to the host where the Analyzer server is installed as a user with Administrator permission (Windows) or root permission (Linux).
  2. Run the hcmds64getlogs command to collect the log file for the Analyzer server.

    In Windows

    Common-component-installation-folder\bin\hcmds64getlogs /dir output-folder-path

    In Linux

    Common-component-installation-directory/bin/hcmds64getlogs -dir output-directory-path
    An archive file is output to the specified output destination.

    For details about the hcmds64getlogs command, see the command reference in the Appendix.

Collecting the log file for the Analyzer detail view server and the Analyzer probe server

You can download the log files for the Analyzer detail view server and the Analyzer probe server by using a web browser.

  1. In the web browser, type the Analyzer detail view server or the Analyzer probe server URL:
    https://server-IP-address:Port-Number

    The Logon window appears.

  2. Log on to the desired server as the admin user and make the appropriate selection:
    • Analyzer detail view server In the application bar, click the Manage icon ().
    • Analyzer probe server Click the Manage link.
  3. In the Manage window, click the Download Diagnostic Data link.
  4. In the Download Diagnostic Data window, click the Download button.

Collecting the log file for the RAID Agent

Run the jpcras command to collect the log file for the RAID Agent.

For RAID Agent (Windows), run commands from the administrator console. For details, see Command usage guidelines.
  1. Log on to the host where RAID Agent is installed, as a user with root permission (Linux) or Administrator permission (Windows).
  2. Run the jpcras command to collect the log file for the RAID Agent.
    In Linux
    /opt/jp1pc/tools/jpcras output-directory-path all all
    An archive file named jpcrasYYMMDD.tar.gz or jpcrasYYMMDD.tar.Z is output to the specified output destination.

    In Windows

    RAID-Agent-installation-folder\raid_agent\jp1pc\tools\jpcras output-folder-path all all
    The agtd.agtras and localhost folder stored in the log files are output to the specified output destination.
    Note: When sending log files, send them in compressed format.
For RAID Agent (Windows), you must also collect the following information.
Dump information
To collect dump information, perform the following procedure:
  1. Open the Task Manager.
  2. Choose the Process tab.
  3. Right-click the name of the process for which dump information is to be collected, and then choose Create dump file.

    The generated dump files are stored in the following folder:

    %SystemDrive%\Users\user-name\AppData\Local\Temp

    If an environment variable has been changed to output dump files to a folder other than that shown in step 3, collect dump files from that folder.

Other information
Collect the following additional information:
Collecting the installation logs for RAID Agent (Windows)

Collect the following logs and registry information for the RAID Agent installer.

  1. Log on to the host where RAID Agent is installed, as a user with Administrator permission.
  2. Run cmd.exe as Administrator.
  3. Run the following commands to collect the registry information for RAID Agent.
    reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hitachi" /s > 01_reg_Hitachi.txt
    reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\On-demand real time monitoring module" /s > 02_reg_on-demand.txt
    reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PH" /s > 03_reg_JP1PCMGR_PH.txt
    reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\JP1PCMGR_PT" /s > 04_reg_JP1PCMGR_PT.txt
    reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AgentRESTService" /s > 05_reg_AgentREST.txt
  4. Exit cmd.exe and collect the files:
    • 01_reg_Hitachi.txt
    • 02_reg_on-demand.txt
    • 03_reg_JP1PCMGR_PH.txt
    • 04_reg_JP1PCMGR_PT.txt
    • 05_reg_AgentREST.txt
  5. Collect the following log files for the RAID Agent installer in %SystemDrive% folder. If there are multiple files, collect all of them:
    • AnalyzerRAIDAgent_Inst_mm-dd-yyyy.log
    • HTM_INST_LOG_AGTD_n.log1
    • HTM_INST_LOG_AGTREST_n.log1
    • HTM_WORK_LOG_AGTD_n.log1, 2
    • htmsilent.rtn
    Note:

    If uninstallation was performed, the following files are also output.

    • AnalyzerRAIDAgent_Uninst_mm-dd-yyyy.log
    • HTM_UNINST_LOG_AGTD_n.log1
    • HTM_UNINST_LOG_AGTD_MSI_n.log1
    • HTM_UNINST_LOG_AGTP_MSI_n.log1
    • HTM_UNINST_LOG_AGTREST_n.log1

    1. n is a serial number.

    2. This file might not exist because it is a temporary file.

  6. If the installation of RAID Agent failed and the following folders of RAID Agent installer exist, collect the folders by compressing them into ZIP or another format. This file might not exist at the time of collection because it is usually deleted:
    • %SystemDrive%\work_winraidagent
  7. Archive the files collected in Step 4 to Step 6 into ZIP or another format.

Collecting Analyzer viewpoint log files

You must have root privilege.
To collect log files, use the following command:
/opt/hitachi/analyzer_viewpoint/bin/diag
The collected log files are output to the current directory.

Command usage guidelines

You must consider the following when using commands.

In Linux

  • You must have root permission.
  • To interrupt a running command, press Ctrl C and make sure that you read any messages and check for problems. If necessary, repeat the command. If you interrupt a command, the return value might be undefined.
  • If the maximum output size of the core file is set to 0, core dumps are effectively disabled. To output a core dump when a failure occurs, run the ulimit command before running each command, and set the maximum output size to unlimited.

In Windows

Note the following when using commands with RAID Agent on a Windows host:

  • You must have Administrator permission.
  • Run the commands in the administrator console.
    1. From the desktop, display the Start window.
    2. In the Analyzer RAID Agent folder, select Ops Center Analyzer Administrator Console.
      Note: The display might vary depending on the OS version.
  • If you enable Quick Edit Mode in the command prompt and then click the mouse in the window, the window output stops until Quick Edit Mode is canceled. For best results, do not use Quick Edit Mode.

Downloading maintenance information

You can download the Ops Center Administrator maintenance information by using the CLI.

  1. Either open an SSH connection to the VM or open the VMware console and press Alt+F2 to reach the console.
  2. Log in as a root user or a normal user. If you log in as a normal user, use the sudo command to complete the following procedure as the root user.
  3. In the terminal, enter the command: /opt/rainier/bin/rainier-getlogs -dir [output-directory].
  4. Verify the location of collected log file (rainier-logs.tar.gz) in the specified output folder, and copy the file to your client computer as required.

hcmds64getlogs command

The hcmds64getlogs command acquires maintenance information on the management server.

The syntax is:

hcmds64getlogs /dir folder-name [/types Automation] [/arc archive-file-name] [/logtypes log-file-type[ log-file-type ...]] 

where:

  • /dir specifies the absolute path to the folder on a local disk that contains collected maintenance information. If the folder has already been created, empty the folder.

    The maximum length of a path name that can be specified is 100 bytes. You can specify any printable ASCII character excluding certain special characters. You cannot specify the following characters:

    \ / : , ; * ? " < > | $ % & ' `

    However, you can specify backslashes (\), colons (:), and forward slashes (/) in Windows, or forward slashes (/) in Linux as a path delimiter. Do not specify a path delimiter at the end of a path name.

    In Windows, to specify a space character in a path name, enclose the path name in double quotation marks ("). In Linux, you cannot specify a space character in a path name.

  • /types Automation specify Automation if the maintenance information for only Ops Center Automator can be collected. When specifying this option, also specify the log file type log for the /logtypes option. If this option is not specified, the Ops Center Automator server and all products using Common Component installed on the same management server is collected.
  • /arc specifies the name of the archive files to be created. If you do not specify this option, the default file name is HiCommand_log_64.

    For the file name, you can specify any printable ASCII character excluding certain special characters. You cannot specify the following characters:

    \ / : , ; * ? " < > | $ % & ' `

    In Linux, you cannot specify a space character in a file name.

  • /logtypes specifies the types of log files to acquire when log files of a particular type cannot be collected due to a failure.
    • log: Specify this to acquire .jar files and .hdb.jar files only.
    • db: Specify this to acquire .db.jar files only.
    • csv: Specify this to acquire .csv.jar files only.

    To specify multiple types, separate them by a space.

    If you omit this option, all log files will be acquired.

Tip: When this command is run, the KAPM05318-I or KAPM05319-E message is output. In addition, maintenance information (log file and database file) is acquired and four archive files (.jar, .hdb.jar, .db.jar, and .csv.jar) are output in the folder specified in the /dir option.

Remarks

  • Do not interrupt this command while it is running.
  • If the hcmds64getlogs command is interrupted, this command has ended before this command completed due to insufficient free space in the folder specified in the /dir option. In this case, make sure that the folder has enough free space, and then execute this command again.
  • Do not run more than one hcmds64getlogs command at the same time.
  • When Ops Center Automator is running in a cluster configuration, execute this command on both the active host and standby host. You can run this command even if the Ops Center Automator server is not running. Therefore, even if an error occurs in a cluster configuration, you can collect log information without switching nodes. However, if the database is not running, you cannot obtain the database information.
  • If the same option is specified more than one time, only the first option is effective.

Common Services REST API

You can use the Common Services REST API to perform user authentication for product that uses the Common Services single-sign on function.

Overview of the Common Services REST API

The following provides an overview and common specifications of the Common Services REST API.

Specifying resources

In the REST API, the target resource is specified as a URL. In Common Services, the target resource is specified as a continuation of the following base URL:

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

Specify the host name or IP address of a host that can access Common Services.

For the port number, specify the port number used for Common Services. The default port number is 443.

Note: The Common Services REST API does not support Cross-Origin Resource Sharing (CORS).

Using a session to perform authentication

To run a Common Services REST API request or a request from a REST API provided by a product linking with Common Services, you must first acquire an access token to use the Common Services user authentication. An access token is authentication information that is returned when a session is generated. This authentication information determines whether a request is issued from an authenticated user.

The operational flow for running a REST API request is as follows:

  1. Run the Common Services REST API request to acquire an access token.
  2. In the Authorization header of the request header, specify the access token in the following format, and run a Common Services REST API request or a request from a REST API provided by another product.
    Authorization: Bearer access-token

    Example of specifying an Authorization header:

    Authorization: Bearer eyJhbxxx
Note:
  • The validity period of an access token expires five minutes.
  • An identify provider user cannot obtain an access token, so they cannot execute a Common Services REST API request.

Response headers

This section describes the response headers returned by the REST API server.

Header

Description

Default

Content-Type

Indicates the media type of the response data.

application/json;charset=UTF-8

Content-Length

Indicates the size of the response data.

If the size of the response data is large, instead of this header, Transfer-Encoding: chunked is returned, indicating that the response data has been divided and then transferred.

None

Transfer-Encoding

Indicates the encoding format used when the response data was transferred.

When a large amount of response data is divided and then transferred, chunked is returned.

None

Location

When an object is registered, this header indicates the URL of the registered object.

None

Status codes

The REST API uses the following standard HTTP status codes to indicate the processing results.

HTTP status codes

Description

200

Success

This indicates that the request was properly processed.

201

Created

This indicates that the request was properly processed and a new resource was successfully created.

204

No content

This indicates that the request was accepted but there was no information to return.

400

Bad request

This indicates that the specification of the request header, the query parameters, or the request body was invalid.

401

Unauthorized

This indicates that the request header did not include the Authorization header or that authentication by using the information specified in the Authorization header failed.

403

Forbidden

This indicates that you do not have permission to perform the operation.

404

Not found

This indicates that the resource specified in the URL could not be found or that you do not have permission to read the resource.

409

Conflict

This indicates that the request could not be completed because of a conflict with the current state of the resource.

500

Unexpected error

This indicates that an unexpected error occurred.

503

Service Unavailable

This indicates that you cannot access the service because of a temporary problem with the server. If you wait a while and then retry the operation, you might be able to access the service.

Request and response formats

Use the JSON format to specify attribute values when creating or changing a resource. Also, use the JSON format for the results of resource information acquisition.

When creating or adding a resource by using the POST method, or when changing or editing a resource by using the PUT method, specify resource attributes in JSON format. The supported character encoding is UTF-8.

When you use the GET method to collect resource information, responses are returned in JSON format. For API requests that get a list of resources, the response body is an array.

Response when an error occurs

If the processing of a request is not successful, the following error information is returned as a response.

Attribute

Type

Description

errorMessage

string

Error message

additionalInfo

string

Additional information about the error message

Output example
{
    "errorMessage" : "KAOP20012-E Not Found.",
    "additionalInfo" : "{\"error\":\"Could not find group by id\"}"
}

REST API of Common Services

The following describes the API provided by Common Services.

Getting access tokens

The following describes the API requests for getting an access token to use for REST API authentication.
Getting an access token
You can get an access token to use for REST API authentication.

If you are an identity provider user, you cannot use this API to obtain an access token.

Execution permission

None.

Request line

POST base-URL/auth/v1/providers/builtin/token

Request message

Object ID
None.
Query parameters
None.
Body
{
  "username" : "TestUser",
  "password" : "password"
}

Attribute

Type

Description

username

string

(Required) Username of the user who wants to acquire an access token

password

string

(Required) Password of the user who wants to acquire an access token

Response message

Body
{
  "access_token" : "access token",
  "expires_in" : 300,
  "token_type" : "bearer"
}

Attribute

Type

Description

access_token

string

Character string that serves as the access token

expires_in

int

Period of validity (in seconds) of the access token

token_type

string

Access token type

A fixed string (bearer) is returned.

Coding example

curl -v -X POST -H "Content-Type:application/json" -s "https://example.com:443/portal/auth/v1/providers/builtin/token" -d @./request.json
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Getting information about users who obtained an access token
The following request gets information about users who obtained an access token.

Execution permission

None.

Request line

GET base-URL/auth/v1/providers/builtin/userinfo

Request message

Object ID
None.
Query parameters
None.
Body
None.

Response message

Body
{
    "sub": "63583645-fc6f-416d-94a1-1e0719247f4d",
    "name": "john smith",
    "given_name": "john",
    "family_name": "smith",
    "preferred_username": "john_smith",
    "email": "john_smith@example.com",
    "email_verified": false,
    "https://opscenter/user_groups": [
        "92d2677b-a3a2-4643-a908-49ade439e0d4"
    ],
    "https://opscenter/user_is_enabled": true,
    "https://opscenter/roles": [
        "opscenter-user",
        "offline_access",
        "uma_authorization"
    ]
}

Attribute

Type

Description

sub

string

Object ID of the user

name

string

Full name of the user

given_name

string

First name of the user

family_name

string

Last name of the user

preferred_username

string

Username

email

string

Email address

email_verified

boolean

Whether or not the email address is verified

  • true: Verified
  • false: Not verified

https://opscenter/user_groups

string[]

ID of the user group that the user belongs to

https://opscenter/user_is_enabled

boolean

Whether the user account is enabled

  • true: The user account is enabled.
  • false: The user account is disabled.

https://opscenter/roles

string[]

ID of the role that was assigned to the user

Coding example

curl -v -X GET -s "https://example.com:443/portal/auth/v1/providers/builtin/userinfo" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)

Managing external authentication

The following describes the API requests for managing external authentication.
Performing connection and authentication tests for the Active Directory server
The following request performs connection and authentication tests for the Active Directory server.

Execution permission

You must be a system administrator or a security administrator.

Request line

POST base-URL/security/v1/external-user-storage-test-connection

Request message

Object ID
None.
Query parameters
None.
Body
To perform only a connection test:
{
    "action": "testConnection",
    "connectionUrl": "ldaps://example.com"
}
To perform both a connection test and an authentication test:
{
    "action": "testAuthentication",
    "connectionUrl": "ldaps://example.com",
    "bindDn": "admin@example.com",
    "bindCredential": "password"
}

Attribute

Type

Description

action

string

(Required) Type of test

Specify either of the following:

  • testConnection:

    Specify this attribute to test whether the connection destination specified by the connectionUrl attribute is accessible.

  • testAuthentication:

    Specify this attribute to test whether the connection destination specified by the connectionUrl attribute is accessible and whether authentication can be performed by using the authentication information specified by the bindDn and bindCredential attributes.

connectionUrl

string

(Required) URL of the connection-destination Active Directory server

Specify a URL that starts with ldaps:// or ldap://.

bindDn

string

(Optional) Bind DN

If you specified testAuthentication for the action attribute, you must specify this attribute.

bindCredential

string

(Optional) Password for the bind DN

If you specified testAuthentication is specified for the action attribute, you must specify this attribute.

Response message

Body
None.

Coding example

curl -v -X POST -H "Content-Type:application/json" -s "https://example.com:443/portal/security/v1/external-user-storage-test-connection" -d @./request.json  -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Getting a list of Active Directory or LDAP servers
The following request gets a list of Active Directory or LDAP servers registered in Common Services.

Execution permission

You must be a system administrator or a security administrator.

Request line

GET base-URL/security/v1/external-user-storage

Request message

Object ID
None.
Query parameters
None.
Body
None.

Response message

Body
For Active Directory servers
[
    {
        "id": "1022c8b2-934e-4097-8112-64b0274a3653",
        "name": "ldap-srv2",
        "priority": 1,
        "userAuthenticationProtocol": "LDAP",
        "vendor": "ACTIVE_DIRECTORY",
        "connectionUrl": "ldaps://vm.ldap-srv2.soft.example.co.jp",
        "baseDn": "CN=Users,DC=ldap-srv2,DC=soft,DC=example,DC=co,DC=jp",
        "bindDn": "admin@ldap-srv2.soft.example.co.jp",
        "bindPassword": null,
        "groupBaseDn": "CN=Users,DC=ldap-srv2,DC=soft,DC=example,DC=co,DC=jp",
        "groupEntryDnList": [
            "CN=admins,CN=Users,DC=ldap-srv2,DC=soft,DC=example,DC=co,DC=jp",
            "CN=users,CN=Users,DC=ldap-srv2,DC=soft,DC=example,DC=co,DC=jp"
        ],
        "kerberosRealm": null,
        "enabled": true,
        "defaultGroupMappingEnabled": false,
        "config": {
            "customUserSearchFilter": "(ou=Ops Center*)"
        }
    }
]
For LDAP servers
[
    {
        "id": "1022c8b2-934e-4097-8112-64b0274a3653",
        "name": "ldap-srv2",
        "priority": 1,
        "userAuthenticationProtocol": "LDAP",
        "vendor": "GENERAL",
        "connectionUrl": "ldaps://vm.ldap-srv2.soft.example.co.jp",
        "baseDn": "CN=Users,DC=ldap-srv2,DC=soft,DC=example,DC=co,DC=jp",
        "bindDn": "admin@ldap-srv2.soft.example.co.jp",
        "bindPassword": null,
        "groupEntryDnList": null,
        "kerberosRealm": null,
        "enabled": true,
        "defaultGroupMappingEnabled": true,
        "config": {
            "usernameLDAPAttribute": "userPrincipalName",
            "rdnLDAPAttribute": "cn",
            "customUserSearchFilter": "(ou=Ops Center*)",
            "lastNameLDAPAttribute": "sn",
            "emailLDAPAttribute": "mail",
            "fullNameLDAPAttribute": "cn",
            "searchScope": "2",
            "uuidLDAPAttribute": "objectGUID",
            "userObjectClasses": "person, organizationalPerson"
        }
    }
]

Attribute

Type

Description

id

string

Object ID

name

string

Server name

priority

int

Priority

userAuthenticationProtocol

string

Authentication method

  • LDAP
  • Kerberos

vendor

string

Type of directory service

  • ACTIVE_DIRECTORY: Active Directory
  • GENERAL: Not Active Directory

connectionUrl

string

URL of the connection-destination Active Directory or LDAP server

baseDn

string

User base DN

bindDn

string

Bind DN

bindPassword

string

Password for the bind DN

groupBaseDn

string

Group base DN

When the vendor attribute is ACTIVE_DIRECTORY, this attribute is displayed.

groupEntryDnList

string[]

List of DNs of the groups to be synchronized

If the value of the vendor attribute is GENERAL, the value null is always returned.

kerberosRealm

string

Realm name for Kerberos authentication

If the value of the userAuthenticationProtocol attribute is LDAP, the value null is always returned.

enabled

boolean

Whether the server setting is enabled

  • true: Enabled
  • false: Disabled

defaultGroupMappingEnabled

boolean

Whether all the users under the User base DN of the Active Directory or LDAP server are allocated to the opscenter-users group

  • true: The users are allocated to the group.
  • false: The users are not allocated to the group.

config

object

Configuration information of the Active Directory or LDAP server

When the vendor attribute is ACTIVE_DIRECTORY, the following configuration information of the Active Directory server is displayed.

  • customUserSearchFilter (string)

    The search filter for narrowing down the users to be displayed in the Users window of the Hitachi Ops Center Portal

When the vendor attribute is GENERAL, the following configuration information of the LDAP server is displayed.

  • usernameLDAPAttribute (string)

    The LDAP attribute allocated to the user ID

  • emailLDAPAttribute (string)

    The LDAP attribute allocated to the email address of the user account

  • lastNameLDAPAttribute (string)

    The LDAP attribute allocated to the last name of the user account

  • fullNameLDAPAttribute (string)

    The LDAP attribute allocated to the full name of the user account

    When information is set for the firstNameLDAPAttribute attribute, this attribute is not displayed.

  • firstNameLDAPAttribute (string)

    The LDAP attribute allocated to the first name of the user account

    When information is set for the fullNameLDAPAttribute attribute, this attribute is not displayed.

  • rdnLDAPAttribute (string)

    The LDAP attribute used as the RDN

  • uuidLDAPAttribute (string)

    The LDAP attribute used as the UUID

  • userObjectClasses (string)

    The object class of the users to be imported

  • searchScope (string)

    The range of hierarchy levels in which to search for the users to be imported

    • 1: One level

    • 2: Subtree

  • customUserSearchFilter (string)

    The search filter for narrowing down the users to be imported

Coding example

curl -v -X GET -s "https://example.com:443/portal/security/v1/external-user-storage" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Getting information about a specific Active Directory or LDAP server
The following request gets information about a specific Active Directory or LDAP server registered in Common Services.

Execution permission

You must be a system administrator or a security administrator.

Request line

GET base-URL/security/v1/external-user-storage/object-ID-of-the-server

Request message

Object ID of the server

Specify the value of id acquired by using the request for getting a list of Active Directory or LDAP servers.

Attribute

Type

Description

id

string

(Required) Object ID of the Active Directory or LDAP server

Query parameters
None.
Body
None.

Response message

Body
For an Active Directory server
{
    "id": "1022c8b2-934e-4097-8112-64b0274a3653",
    "name": "ldap-srv2",
    "priority": 1,
    "userAuthenticationProtocol": "LDAP",
    "vendor": "ACTIVE_DIRECTORY",
    "connectionUrl": "ldaps://vm.ldap-srv2.soft.example.co.jp",
    "baseDn": "CN=Users,DC=ldap-srv2,DC=soft,DC=example,DC=co,DC=jp",
    "bindDn": "admin@ldap-srv2.soft.example.co.jp",
    "bindPassword": null,
    "groupBaseDn": "CN=Users,DC=ldap-srv2,DC=soft,DC=example,DC=co,DC=jp",
    "groupEntryDnList": [
        "CN=admins,CN=Users,DC=ldap-srv2,DC=soft,DC=example,DC=co,DC=jp",
        "CN=users,CN=Users,DC=ldap-srv2,DC=soft,DC=example,DC=co,DC=jp"
    ],
    "kerberosRealm": null,
    "enabled": true,
    "defaultGroupMappingEnabled": false,
    "config": {
            "customUserSearchFilter": "(ou=Ops Center*)"
        }
}
For an LDAP server
{
    "id": "1022c8b2-934e-4097-8112-64b0274a3653",
    "name": "ldap-srv2",
    "priority": 1,
    "userAuthenticationProtocol": "LDAP",
    "vendor": "GENERAL",
    "connectionUrl": "ldaps://vm.ldap-srv2.soft.example.co.jp",
    "baseDn": "CN=Users,DC=ldap-srv2,DC=soft,DC=example,DC=co,DC=jp",
    "bindDn": "admin@ldap-srv2.soft.example.co.jp",
    "bindPassword": null,
    "groupEntryDnList": null,
    "kerberosRealm": null,
    "enabled": true,
    "defaultGroupMappingEnabled": true,
    "config": {
        "usernameLDAPAttribute": "userPrincipalName",
        "rdnLDAPAttribute": "cn",
        "customUserSearchFilter": "(ou=Ops Center*)",
        "lastNameLDAPAttribute": "sn",
        "emailLDAPAttribute": "mail",
        "fullNameLDAPAttribute": "cn",
        "searchScope": "2",
        "uuidLDAPAttribute": "objectGUID",
        "userObjectClasses": "person, organizationalPerson"
    }
}

Attribute

Type

Description

id

string

Object ID of the Active Directory or LDAP server

name

string

Server name

priority

int

Priority

userAuthenticationProtocol

string

Authentication method

  • LDAP
  • Kerberos

vendor

string

Type of directory service

  • ACTIVE_DIRECTORY: Active Directory
  • GENERAL: Not Active Directory

connectionUrl

string

URL of the connection-destination Active Directory or LDAP server

baseDn

string

User base DN

bindDn

string

Bind DN

bindPassword

string

Password for the bind DN

groupBaseDn

string

Group base DN

When the vendor attribute is ACTIVE_DIRECTORY, this attribute is displayed.

groupEntryDnList

string[]

List of DNs of the groups to be synchronized

If the value of the vendor attribute is GENERAL, the value null is always returned.

kerberosRealm

string

Realm name for Kerberos authentication

If the value of the userAuthenticationProtocol attribute is LDAP, the value null is always returned.

enabled

boolean

Whether the server setting is enabled

  • true: Enabled
  • false: Disabled

defaultGroupMappingEnabled

boolean

Whether all the users under the User base DN of the Active Directory or LDAP server are allocated to the opscenter-users group

  • true: The users are allocated to the group.
  • false: The users are not allocated to the group.

config

object

Configuration information of the Active Directory or LDAP server

When the vendor attribute is ACTIVE_DIRECTORY, the following configuration information of the Active Directory server is displayed.

  • customUserSearchFilter (string)

    The search filter for narrowing down the users to be displayed in the Users window of the Hitachi Ops Center Portal

When the vendor attribute is GENERAL, the following configuration information of the LDAP server is displayed.

  • usernameLDAPAttribute (string)

    The LDAP attribute allocated to the user ID

  • emailLDAPAttribute (string)

    The LDAP attribute allocated to the email address of the user account

  • lastNameLDAPAttribute (string)

    The LDAP attribute allocated to the last name of the user account

  • fullNameLDAPAttribute (string)

    The LDAP attribute allocated to the full name of the user account

    When information is set for the firstNameLDAPAttribute attribute, this attribute is not displayed.

  • firstNameLDAPAttribute (string)

    The LDAP attribute allocated to allocated to the first name of the user account

    When information is set for the fullNameLDAPAttribute attribute, this attribute is not displayed.

  • rdnLDAPAttribute (string)

    The LDAP attribute used as the RDN

  • uuidLDAPAttribute (string)

    The LDAP attribute used as the UUID

  • userObjectClasses (string)

    The object class of the users to be imported

  • searchScope (string)

    The range of hierarchy levels in which to search for users to be imported

    • 1: One level

    • 2: Subtree

  • customUserSearchFilter (string)

    The search filter for narrowing down the users to be imported

Coding example

curl -v -X GET -s "https://example.com:443/portal/security/v1/external-user-storage/1022c8b2-934e-4097-8112-64b0274a3653" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Getting a list of realms for Kerberos authentication
The following request gets a list of realms for Kerberos authentication registered in Common Services.

Execution permission

You must be a system administrator or a security administrator.

Request line

GET base-URL/security/v1/kerberos-realm

Request message

Object ID
None.
Query parameters
None.
Body
None.

Response message

Body
[
    {
        "id": "8a44f59a6f87e5d4016f880c544c0000",
        "realm": "LDAP-SRV2.SOFT.EXAMPLE.CO.JP",
        "kdcs": [
            "vm.ldap-srv2.soft.example.co.jp"
        ]
    }
]

Attribute

Type

Description

id

string

Object ID of the realm

realm

string

Realm name

kdcs

string[]

List of KDC servers

Coding example

curl -v -X GET -s "https://example.com:443/portal/security/v1/kerberos-realm" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Getting information about a specific realm for Kerberos authentication
The following request gets information about a specific realm for Kerberos authentication registered in Common Services.

Execution permission

You must be a system administrator or a security administrator.

Request line

GET base-URL/security/v1/kerberos-realm/object-ID-of-the-realm

Request message

Object ID of the realm

Specify the value of id acquired by using the request for getting information about a list of realms for Kerberos authentication.

Attribute

Type

Description

id

string

(Required) Object ID of the realm

Query parameters
None.
Body
None.

Response message

Body
{
    "id": "8a44f59a6f87e5d4016f880c544c0000",
    "realm": "LDAP-SRV2.SOFT.EXAMPLE.CO.JP",
    "kdcs": [
        "vm.ldap-srv2.soft.example.co.jp"
    ]
}

Attribute

Type

Description

id

string

Object ID of the realm

realm

string

Realm name

kdcs

string[]

List of KDC servers

Coding example

curl -v -X GET -s "https://example.com:443/portal/security/v1/kerberos-realm/4028b8816e4ad3ee016e5d76637c0000" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Getting Kerberos authentication connection information
The following request gets Kerberos authentication connection information registered in Common Services.

Execution permission

You must be a system administrator or a security administrator.

Request line

GET base-URL/security/v1/kerberos-connection-settings

Request message

Object ID
None.
Query parameters
None.
Body
None.

Response message

Body
{
    "clockskew" : 0,
    "dnsLookupKdc" : true
}

Attribute

Type

Description

clockskew

int

Allowable time difference between Common Services and the Kerberos server (in seconds)

dnsLookupKdc

boolean

Whether to query the DNS server for KDC information

  • true: Queries the server.
  • false: Does not query the server.

Coding example

curl -v -X GET -s "https://example.com:443/portal/security/v1/kerberos-connection-settings" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Checking the number of users to be acquired from an Active Directory or LDAP server
Check the number of users to be acquired from an Active Directory or LDAP server. This number is the number of users to be displayed in the Users window of the Hitachi Ops Center Portal.

Execution permission

You must be a system administrator or a security administrator.

Request line

POST base-URL/security/v1/external-user-storage-test-search-limit-exceeded

Request message

Object ID
None.
Query parameters
None.
Body
{
    "connectionUrl": "ldaps://example.com",
    "bindDn": "cn=Directory Manager",
    "bindPassword": "password",
    "baseDn": "OU=Subtree,DC=example,DC=com",
    "objectClasses": "person, organizationalPerson",
    "searchScope": "1",
    "customUserSearchFilter": "(ou=Ops Center*)",
    "usernameLDAPAttribute": "uid"
}

Attribute

Type

Description

connectionUrl

string

(Required) URL of the connection-destination Active Directory or LDAP server

bindDn

string

(Required) Bind DN

bindPassword

string

(Required) Password for the bind DN

baseDn

string

(Required) User base DN

objectClasses

string

(Required)

For an Active Directory server

Specify person,organizationalPerson,user.

For an LDAP server

The object class of the users to be acquired

To specify multiple values, separate the values by using commas.

searchScope

string

(Required)

For an Active Directory server

Specify 2.

For an LDAP server

The range of hierarchy levels in which to search for users to be acquired

Specify either of the following.

  • 1: One level
  • 2: Subtree

customUserSearchFilter

string

(Optional) The search filter for narrowing down the users to be acquired

The syntax of the search filter conforms to RFC 2254.

usernameLDAPAttribute

string

(Required)

For an Active Directory server

Specify sAMAccountName.

For an LDAP server

LDAP attribute that uniquely identifies the user to be acquired

Response message

Body
{
    "count" : 5,
    "maxValue" : 100
}

Attribute

Type

Description

count

int

The number of users acquired from the Active Directory or LDAP server

If the number of users is greater than the value of the maxValue attribute, -1 is returned.

maxValue

int

The maximum number of users that can be displayed in the Users window of the Hitachi Ops Center Portal

Coding example

curl -v -X POST -H "Content-Type:application/json" -s "https://example.com:443/portal/security/v1/external-user-storage-test-search-limit-exceeded" -d @./request.json -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)

Managing identity providers

This section describes the API requests related to the management of identity providers.
Getting a list of identity providers
The following request gets a list of identity providers registered in Common Services.

Execution permission

You must be a system administrator or a security administrator.

Request line

GET base-URL/idp/v1/external-identity-provider

Request message

Object ID
None.
Query parameters
None.
Body
None.

Response message

Body
When the federation protocol is OIDC
[
    {
        "providerType": "ADFS",
        "protocol": "oidc",
        "alias": "ad5oidc",
        "displayName": "AD5OIDC",
        "fromUrl": "https://adfs.example.com/adfs/.well-known/openid-configuration",
        "enabled": true,
        "guiOrder": 1,
        "defaultGroupList": [
            {
                "localGroupId": "a39f9e45-5e2e-446b-89d3-93f9e9ec4c31",
                "localGroupName": "opscenter-users"
            }
        ],
        "customGroupList": [
            {
                "idpGroupName": "opscenter-ad5\\opscenter_admins",
                "localGroupId": "9fd2ef28-5077-4816-ade8-526204f4d2ac",
                "localGroupName": "opscenter-administrators"
            }
        ],
        "clientId": "a49d4539-c080-4436-8bcb-113271b5152a",
        "clientSecret": "**********",
        "config": {
            "userInfoUrl": "https://adfs.example.com/adfs/userinfo",
            "validateSignature": "true",
            "redirectURI": "https://example.com:8443/auth/realms/opscenter/broker/ad5oidc/endpoint",
            "clientId": "a49d4539-c080-4436-8bcb-113271b5152a",
            "tokenUrl": "https://adfs.example.com/adfs/oauth2/token/",
            "jwksUrl": "https://adfs.example.com/adfs/discovery/keys",
            "issuer": "https://adfs.example.com/adfs",
            "useJwksUrl": "true",
            "authorizationUrl": "https://adfs.example.com/adfs/oauth2/authorize/",
            "clientAuthMethod": "client_secret_post",
            "disableUserInfo": "true",
            "fromUrl": "https://adfs.example.com/adfs/.well-known/openid-configuration",
            "logoutUrl": "https://adfs.example.com/adfs/oauth2/logout",
            "syncMode": "FORCE",
            "clientSecret": "**********",
            "allowedClockSkew": "300",
            "defaultScope": "https://example.com/openid https://example.com/allatclaims"
        }
    }
]
When the federation protocol is SAML
[
    {
        "providerType": "ADFS",
        "protocol": "saml",
        "alias": "ad5saml",
        "displayName": "AD5SAML",
        "fromUrl": "https://adfs.example.com/FederationMetadata/2007-06/FederationMetadata.xml",
        "enabled": true,
        "guiOrder": 1,
        "defaultGroupList": [
            {
                "localGroupId": "a39f9e45-5e2e-446b-89d3-93f9e9ec4c31",
                "localGroupName": "opscenter-users"
            }
        ],
        "customGroupList": [
            {
                "idpGroupName": "opscenter-ad5\\opscenter_admins",
                "localGroupId": "9fd2ef28-5077-4816-ade8-526204f4d2ac",
                "localGroupName": "opscenter-administrators"
            }
        ],
        "clientId": null,
        "clientSecret": null,
        "config": {
            "redirectURI": "https://example.com:8443/auth/realms/opscenter/broker/ad5saml/endpoint",
            "samlXmlKeyNameTranformer": "KEY_ID",
            "postBindingLogout": "true",
            "postBindingResponse": "true",
            "singleLogoutServiceUrl": "https://adfs.example.com/adfs/ls/",
            "claimEmail": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress",
            "claimFirstname": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname",
            "claimGroup": "http://schemas.xmlsoap.org/claims/Group",
            "claimLastname": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname",
            "xmlSigKeyInfoKeyNameTransformer": "CERT_SUBJECT",
            "metadataEndpoint": "https://example.com:8443/auth/realms/opscenter/broker/ad5saml/endpoint/descriptor",
            "syncMode": "FORCE",
            "singleSignOnServiceUrl": "https://adfs.example.com/adfs/ls/",
            "wantAuthnRequestsSigned": "true",
            "allowedClockSkew": "300",
            "encryptionPublicKey": "MIIDDDCCAfSgAwIBAgIQPniaLjBZQolPp9AouqTIATANBgkqhkiG9w0BAQsFADBCMUAwPgYDVQQDEzdBREZTIEVuY3J5cHRpb24gLSB2bTIzNzA1My5vcmlvbi1hZDIuc29mdC5oaXRhY2hpLmNvLmpwMB4XDTIxMDMyMzA0MTI0MVoXDTI0MDMyMjA0MTI0MVowQjFAMD4GA1UEAxM3QURGUyBFbmNyeXB0aW9uIC0gdm0yMzcwNTMub3Jpb24tYWQyLnNvZnQuaGl0YWNoaS5jby5qcDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMpfyp7lB7YdRjnKir4RlRgJIshm1x9ZmjPZYXu+VZ0o7m+r6a+CwuH3zsFJlhu8/QYhjAthL6iHwyrLdv3YETOrURRzd23BY3q0d9aZ50efaAfh1NfcZOltoMkFhOvz39TGjtHL6FlayPkJKRP+AwONZ8VOWkAJIHlmMF3wX8myFHs6Y2cSR5ClbWGZ+eRLfQP4gjLlribfcZMRCulBHk7FrOe9k4hZd2/IaqMVZQKEUofqv1r8fpSu99e01pR59hvoJUQE6xl2mgmKmQygMceit+mCEldw5N31lxq8vj3Uab12OeuadSDYbOJDAuNUwFhx360VJMo6vmZqSpnJlcECAwEAATANBgkqhkiG9w0BAQsFAAOCAQEAAo7wvasuKX7NtGd8YcHzwZ/v/2klT0jx1tmuWS0TezKAnZSofYmJn7HAYugJa/VUal8nehvBAPjajjRvArDLsZBAxOzYsn2U4m3XuEzHrtS+40/dBS/vYGldIfTfupVjCRJZvV35ONFL7sqnXnnxk0PiVTC0r3jY3oIqB8uRELFYEmLgDEEdB3YizH0NdtzWHdWIcHyWTYdZBe3zfizl3UEIOfbZIeMolgXjZquiNcOO/EZKLuJWgbupc17B7RQOhX1ZeKY2OGcL2opqnaBRcib2bTyg6R0E+ZGm6yOy6pC8pYdbvvKv9uBoys7BB/JgbSnLWXz9nB7c6o/yU6WdCA==",
            "validateSignature": "true",
            "signingCertificate": "MIIDBjCCAe6gAwIBAgIQMCWzE1wV4b9Kq4X13T/i3DANBgkqhkiG9w0BAQsFADA/MT0wOwYDVQQDEzRBREZTIFNpZ25pbmcgLSB2bTIzNzA1My5vcmlvbi1hZDIuc29mdC5oaXRhY2hpLmNvLmpwMB4XDTIxMDMyMzA0MTI0NVoXDTI0MDMyMjA0MTI0NVowPzE9MDsGA1UEAxM0QURGUyBTaWduaW5nIC0gdm0yMzcwNTMub3Jpb24tYWQyLnNvZnQuaGl0YWNoaS5jby5qcDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAIwQWHRYEJ1MglckuKBBStb+ClBz3QlrzDlcXAPv1/QQjOpWa20fB0YlL2RmKTjtVE3AuUNEtJXkYfMWoYqVaDcudPj5I6zRve+ZYE46KgyjDkDSBE2o2saENe74KvZ23G9J+1beKt/hcmPdXKH6oOQ8c1C40fEXfxoiV2Uw5K3ltOYfa7lSeQ6ywYdso/DYtUrJqK4juq2kVk7+hHsrQ7hNndKpAKhouq89KZ1opbzxvG/cdQqWR110NZx2CFtZrYXtVu5P4VzloBoA+GVvu7CBQoFlZ2dbWruI0oEPj7/ebV+84HFZYG1NrSMn3D5Da+6LwReljZEoDwJkNKz3m6cCAwEAATANBgkqhkiG9w0BAQsFAAOCAQEAIelrzirZug21oHupUezWbaeP7wAYfS8LBIKpbyR+xrtoaJhcdcEUUGwpadT283Yq3AXzRAVJ7rXPVhAGYCOuw+1kq3WaT+glaTbQJPPAy57WhrhNLRRY3AowohOdCZi5fznTTMbREK4E0hJ1xh4r7Hst+JlR9hLfMK1l5DNPKrBMZuiYXa566WIw6F708VLJxRQcTVG9P/MqecOOuch6f9lH4zDyNFPrjDmbssdGVCBX2RnVqHhUKJXPVCTTTLDNOqqUZ4Z/wWzuEAhis0/eyUBs0w3XlBVXYuHaEMIESpGDUSBrBY+Uqv6oR7q0i4Ge+YmfqqwpaxKAUrAN0m2ckA==",
            "nameIDPolicyFormat": "urn:oasis:names:tc:SAML:1.1:nameid-format:WindowsDomainQualifiedName",
            "signatureAlgorithm": "RSA_SHA256",
            "wantAssertionsEncrypted": "true",
            "useJwksUrl": "true",
            "wantAssertionsSigned": "true",
            "fromUrl": "https://adfs.example.com/FederationMetadata/2007-06/FederationMetadata.xml",
            "postBindingAuthnRequest": "true",
            "forceAuthn": "true",
            "addExtensionsElementWithKeyInfo": "false",
            "principalType": "SUBJECT"
        }
    }
]

Attribute

Type

Description

providerType

string

Provider type

A fixed string (ADFS) is returned.

protocol

string

Federation protocol

  • oidc
  • saml

alias

string

Alias name

displayName

string

Display name

fromUrl

string

OpenID Connect discovery endpoint or metadata endpoint of the identity provider

enabled

boolean

Whether the server setting is enabled

  • true: Enabled

  • false: Disabled

guiOrder

int

Server display sequence in the Identity Provider window

A fixed value (1) is returned.

defaultGroupList

object

Settings of default group mappers
  • localGroupId (string)

    Object ID of the local user group

  • localGroupName (string)

    Local user group name

customGroupList

object

Settings of custom group mappers
  • idpGroupName (string)

    Group name of the identity provider

  • localGroupId (string)

    Object ID of the local user group

  • localGroupName (string)

    Local user group name

clientId

string

Client ID of the identity provider

If the value of the protocol attribute is saml, the value null is always returned.

clientSecret

string

Client secret of the identity provider

If the value of the protocol attribute is oidc, the value ********** is always returned.

If the value of the protocol attribute is saml, the value null is always returned.

config

object

Configuration information of the identity provider

Coding example

curl -v -X GET -s "https://example.com:443/portal/idp/v1/external-identity-provider" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Getting information about a specific identity provider
The following request gets information about a specific identity provider registered in Common Services.

Execution permission

You must be a system administrator or a security administrator.

Request line

GET base-URL/idp/v1/external-identity-provider/alias-name

Request message

Alias name

Specify the value of alias acquired by using the request for getting a list of identity providers.

Attribute

Type

Description

alias

string

(Required) Alias name of the identity provider

Query parameters
None.
Body
None.

Response message

Body
When the federation protocol is OIDC
{
    "providerType": "ADFS",
    "protocol": "oidc",
    "alias": "ad5oidc",
    "displayName": "AD5OIDC",
    "fromUrl": "https://adfs.example.com/adfs/.well-known/openid-configuration",
    "enabled": true,
    "guiOrder": 1,
    "defaultGroupList": [
        {
            "localGroupId": "a39f9e45-5e2e-446b-89d3-93f9e9ec4c31",
            "localGroupName": "opscenter-users"
        }
    ],
    "customGroupList": [
        {
            "idpGroupName": "opscenter-ad5\\opscenter_admins",
            "localGroupId": "9fd2ef28-5077-4816-ade8-526204f4d2ac",
            "localGroupName": "opscenter-administrators"
        }
    ],
    "clientId": "a49d4539-c080-4436-8bcb-113271b5152a",
    "clientSecret": "**********",
    "config": {
        "userInfoUrl": "https://adfs.example.com/adfs/userinfo",
        "validateSignature": "true",
        "redirectURI": "https://example.com:8443/auth/realms/opscenter/broker/ad5oidc/endpoint",
        "clientId": "a49d4539-c080-4436-8bcb-113271b5152a",
        "tokenUrl": "https://adfs.example.com/adfs/oauth2/token/",
        "jwksUrl": "https://adfs.example.com/adfs/discovery/keys",
        "issuer": "https://adfs.example.com/adfs",
        "useJwksUrl": "true",
        "authorizationUrl": "https://adfs.example.com/adfs/oauth2/authorize/",
        "clientAuthMethod": "client_secret_post",
        "disableUserInfo": "true",
        "fromUrl": "https://adfs.example.com/adfs/.well-known/openid-configuration",
        "logoutUrl": "https://adfs.example.com/adfs/oauth2/logout",
        "syncMode": "FORCE",
        "clientSecret": "**********",
        "allowedClockSkew": "300",
        "defaultScope": "https://example.com/openid https://example.com/allatclaims"
    }
}
When the federation protocol is SAML
{
    "providerType": "ADFS",
    "protocol": "saml",
    "alias": "ad5saml",
    "displayName": "AD5SAML",
    "fromUrl": "https://adfs.example.com/FederationMetadata/2007-06/FederationMetadata.xml",
    "enabled": true,
    "guiOrder": 1,
    "defaultGroupList": [
        {
            "localGroupId": "a39f9e45-5e2e-446b-89d3-93f9e9ec4c31",
            "localGroupName": "opscenter-users"
        }
    ],
    "customGroupList": [
        {
            "idpGroupName": "opscenter-ad5\\opscenter_admins",
            "localGroupId": "9fd2ef28-5077-4816-ade8-526204f4d2ac",
            "localGroupName": "opscenter-administrators"
        }
    ],
    "clientId": null,
    "clientSecret": null,
    "config": {
        "redirectURI": "https://example.com:8443/auth/realms/opscenter/broker/ad5saml/endpoint",
        "samlXmlKeyNameTranformer": "KEY_ID",
        "postBindingLogout": "true",
        "postBindingResponse": "true",
        "singleLogoutServiceUrl": "https://adfs.example.com/adfs/ls/",
        "claimEmail": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress",
        "claimFirstname": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname",
        "claimGroup": "http://schemas.xmlsoap.org/claims/Group",
        "claimLastname": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname",
        "xmlSigKeyInfoKeyNameTransformer": "CERT_SUBJECT",
        "metadataEndpoint": "https://example.com:8443/auth/realms/opscenter/broker/ad5saml/endpoint/descriptor",
        "syncMode": "FORCE",
        "singleSignOnServiceUrl": "https://adfs.example.com/adfs/ls/",
        "wantAuthnRequestsSigned": "true",
        "allowedClockSkew": "300",
        "encryptionPublicKey": "MIIDDDCCAfSgAwIBAgIQPniaLjBZQolPp9AouqTIATANBgkqhkiG9w0BAQsFADBCMUAwPgYDVQQDEzdBREZTIEVuY3J5cHRpb24gLSB2bTIzNzA1My5vcmlvbi1hZDIuc29mdC5oaXRhY2hpLmNvLmpwMB4XDTIxMDMyMzA0MTI0MVoXDTI0MDMyMjA0MTI0MVowQjFAMD4GA1UEAxM3QURGUyBFbmNyeXB0aW9uIC0gdm0yMzcwNTMub3Jpb24tYWQyLnNvZnQuaGl0YWNoaS5jby5qcDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMpfyp7lB7YdRjnKir4RlRgJIshm1x9ZmjPZYXu+VZ0o7m+r6a+CwuH3zsFJlhu8/QYhjAthL6iHwyrLdv3YETOrURRzd23BY3q0d9aZ50efaAfh1NfcZOltoMkFhOvz39TGjtHL6FlayPkJKRP+AwONZ8VOWkAJIHlmMF3wX8myFHs6Y2cSR5ClbWGZ+eRLfQP4gjLlribfcZMRCulBHk7FrOe9k4hZd2/IaqMVZQKEUofqv1r8fpSu99e01pR59hvoJUQE6xl2mgmKmQygMceit+mCEldw5N31lxq8vj3Uab12OeuadSDYbOJDAuNUwFhx360VJMo6vmZqSpnJlcECAwEAATANBgkqhkiG9w0BAQsFAAOCAQEAAo7wvasuKX7NtGd8YcHzwZ/v/2klT0jx1tmuWS0TezKAnZSofYmJn7HAYugJa/VUal8nehvBAPjajjRvArDLsZBAxOzYsn2U4m3XuEzHrtS+40/dBS/vYGldIfTfupVjCRJZvV35ONFL7sqnXnnxk0PiVTC0r3jY3oIqB8uRELFYEmLgDEEdB3YizH0NdtzWHdWIcHyWTYdZBe3zfizl3UEIOfbZIeMolgXjZquiNcOO/EZKLuJWgbupc17B7RQOhX1ZeKY2OGcL2opqnaBRcib2bTyg6R0E+ZGm6yOy6pC8pYdbvvKv9uBoys7BB/JgbSnLWXz9nB7c6o/yU6WdCA==",
        "validateSignature": "true",
        "signingCertificate": "MIIDBjCCAe6gAwIBAgIQMCWzE1wV4b9Kq4X13T/i3DANBgkqhkiG9w0BAQsFADA/MT0wOwYDVQQDEzRBREZTIFNpZ25pbmcgLSB2bTIzNzA1My5vcmlvbi1hZDIuc29mdC5oaXRhY2hpLmNvLmpwMB4XDTIxMDMyMzA0MTI0NVoXDTI0MDMyMjA0MTI0NVowPzE9MDsGA1UEAxM0QURGUyBTaWduaW5nIC0gdm0yMzcwNTMub3Jpb24tYWQyLnNvZnQuaGl0YWNoaS5jby5qcDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAIwQWHRYEJ1MglckuKBBStb+ClBz3QlrzDlcXAPv1/QQjOpWa20fB0YlL2RmKTjtVE3AuUNEtJXkYfMWoYqVaDcudPj5I6zRve+ZYE46KgyjDkDSBE2o2saENe74KvZ23G9J+1beKt/hcmPdXKH6oOQ8c1C40fEXfxoiV2Uw5K3ltOYfa7lSeQ6ywYdso/DYtUrJqK4juq2kVk7+hHsrQ7hNndKpAKhouq89KZ1opbzxvG/cdQqWR110NZx2CFtZrYXtVu5P4VzloBoA+GVvu7CBQoFlZ2dbWruI0oEPj7/ebV+84HFZYG1NrSMn3D5Da+6LwReljZEoDwJkNKz3m6cCAwEAATANBgkqhkiG9w0BAQsFAAOCAQEAIelrzirZug21oHupUezWbaeP7wAYfS8LBIKpbyR+xrtoaJhcdcEUUGwpadT283Yq3AXzRAVJ7rXPVhAGYCOuw+1kq3WaT+glaTbQJPPAy57WhrhNLRRY3AowohOdCZi5fznTTMbREK4E0hJ1xh4r7Hst+JlR9hLfMK1l5DNPKrBMZuiYXa566WIw6F708VLJxRQcTVG9P/MqecOOuch6f9lH4zDyNFPrjDmbssdGVCBX2RnVqHhUKJXPVCTTTLDNOqqUZ4Z/wWzuEAhis0/eyUBs0w3XlBVXYuHaEMIESpGDUSBrBY+Uqv6oR7q0i4Ge+YmfqqwpaxKAUrAN0m2ckA==",
        "nameIDPolicyFormat": "urn:oasis:names:tc:SAML:1.1:nameid-format:WindowsDomainQualifiedName",
        "signatureAlgorithm": "RSA_SHA256",
        "wantAssertionsEncrypted": "true",
        "useJwksUrl": "true",
        "wantAssertionsSigned": "true",
        "fromUrl": "https://adfs.example.com/FederationMetadata/2007-06/FederationMetadata.xml",
        "postBindingAuthnRequest": "true",
        "forceAuthn": "true",
        "addExtensionsElementWithKeyInfo": "false",
        "principalType": "SUBJECT"
    }
}

Attribute

Type

Description

providerType

string

Provider type

A fixed string (ADFS) is returned.

protocol

string

Federation protocol

  • oidc
  • saml

alias

string

Alias name

displayName

string

Display name

fromUrl

string

OpenID Connect discovery endpoint or metadata endpoint of the identify provider

enabled

boolean

Whether the server setting is enabled

  • true: Enabled

  • false: Disabled

guiOrder

int

Server display sequence in the Identify Providers window

A fixed value (1) is returned.

defaultGroupList

object

Configuration of default group mappers
  • localGroupId (string)

    Object ID of the local user group

  • localGroupName (string)

    Local user group name

customGroupList

object

Settings of custom group mappers
  • idpGroupName (string)

    Group name of the identity provider

  • localGroupId (string)

    Object ID of the local user group

  • localGroupName (string)

    Local user group name

clientId

string

Client ID of the identify provider

If the value of the protocol attribute is saml, the value null is always returned.

clientSecret

string

Client secret of the identity provider

If the value of the protocol attribute is oidc, the value ********** is always returned.

If the value of the protocol attribute is saml, the value null is always returned.

config

object

Configuration information of the identity provider

Coding example

curl -v -X GET -s "https://example.com:443/portal/idp/v1/external-identity-provider/ad5oidc" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)

Managing users

The following describes the API requests for managing users.
Getting a list of users
The following request gets a list of users.

Execution permission

You must be a system administrator or a security administrator.

Request line

GET base-URL/security/v1/users

Request message

Object ID
None.
Query parameters

Parameter

Type

Filter condition

search

string

String that must be included in the username, first name, last name, or email address of the user.

Body
None.

Response message

Body
[
    {
        "id": "a010279b-ae66-4c1d-b066-c45d50c9f75a",
        "username": "sysadmin",
        "firstName": "firstName",
        "lastName": null,
        "email": "sysadmin@example.com",
        "dn": null,
        "description": "Built-in user",
        "enabled": true,
        "builtin": true,
        "federatedIdentities": null
    },
    {
        "id": "82576381-e765-4645-a697-782111f8f5b5",
        "username": "user_1",
        "firstName": "1",
        "lastName": "user",
        "email": "user_1@example.com",
        "dn": null,
        "description": "description user_1",
        "enabled": true,
        "builtin": false,
        "federatedIdentities": [
            {
                "alias": "dummy_alias",
                "displayName": "DUMMY DISPLAY NAME"
            }
        ]
    }
]

Attribute

Type

Description

id

string

Object ID of the user

username

string

Username

firstName

string

First name of the user

lastName

string

Last name of the user

email

string

Email address

dn

string

Distinguished Name

If the user is not a user acquired from an Active Directory or LDAP server, the value null is always returned.

description

string

Description of the user account

enabled

boolean

Whether the user account is enabled

  • true: The user account is enabled.
  • false: The user account is disabled.

builtin

boolean

Whether the user is a built-in user

  • true: The user is a built-in user.
  • false: The user is not a built-in user.

federatedIdentities

object

Identity provider information

If the user is not an identity provider user, null is always returned.

alias

string

Alias name that identifies the identity provider

This is displayed when the user is an identity provider user.

displayName

string

Display name of the identity provider

This is displayed when the user is an identify provider user.

Coding example

When no query parameter is specified:

curl -v -X GET -s "https://example.com:443/portal/security/v1/users" -H "Authorization:Bearer eyJhbxxx"

When a query parameter is specified:

curl -v -X GET -s "https://example.com:443/portal/security/v1/users?search=smith" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Getting information about a specific user
The following request gets information about a specific user.

Execution permission

You must be a system administrator or a security administrator.

Request line

GET base-URL/security/v1/users/object-ID-of-the-user

Request message

Object ID of the user

Specify the value of id acquired by using the request for getting information about a list of users.

Attribute

Type

Description

id

string

(Required) Object ID of the user

Query parameters
None.
Body
None.

Response message

Body
{
    "id": "a010279b-ae66-4c1d-b066-c45d50c9f75a",
    "username": "sysadmin",
    "firstName": "firstName",
    "lastName": null,
    "email": "sysadmin@example.com",
    "dn": null,
    "description": "Built-in user",
    "enabled": true,
    "builtin": true,
    "federatedIdentities": [
        {
            "alias": "dummy_alias",
            "displayName": "DUMMY DISPLAY NAME"
        }
    ]
}

Attribute

Type

Description

id

string

Object ID of the user

username

string

Username

firstName

string

First name of the user

lastName

string

Last name of the user

email

string

Email address

dn

string

Distinguished Name

If the user is not a user acquired from an Active Directory or LDAP server, the value null is always returned.

description

string

Description of the user account

enabled

boolean

Whether the user account is enabled

  • true: The user account is enabled.
  • false: The user account is disabled.

builtin

boolean

Whether the user is a built-in user

  • true: The user is a built-in user.
  • false: The user is not a built-in user.

federatedIdentities

object

Identity provider information

If the user is not an identity provider user, null is always returned.

alias

string

Alias name that identifies the identity provider

This is displayed when the user is an identity provider user.

displayName

string

Display name of the identity provider

This is displayed when the user is an identify provider user.

Coding example

curl -v -X GET -s "https://example.com:443/portal/security/v1/users/a010279b-ae66-4c1d-b066-c45d50c9f75a" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Getting a list of the user groups to which a specific user belongs
The following request gets a list of the user groups to which a specific user belongs.

Execution permission

You must be a system administrator or a security administrator.

Request line

GET base-URL/security/v1/users/object-ID-of-the-user/user-groups

Request message

Object ID of the user

Specify the value of id acquired by using the request for getting information about a list of users.

Attribute

Type

Description

id

string

(Required) Object ID of the user

Query parameters
None.
Body
None.

Response message

Body
[
    {
        "id": "4760d4c0-c593-42fe-b44a-553da4793882",
        "name": "opscenter-administrators",
        "path": "/opscenter-administrators",
        "dn": null,
        "description": null,
        "builtin": true,
        "essential": false,
        "external": false
    },
    {
        "id": "7a773ca8-49cf-4ee2-9456-eb4853b4c6c1",
        "name": "opscenter-users",
        "path": "/opscenter-users",
        "dn": null,
        "description": null,
        "builtin": true,
        "essential": true,
        "external": false
    }
]

Attribute

Type

Description

id

string

Object ID of the user group

name

string

User group name

path

string

Path

dn

string

Distinguished Name

If the group is not a group acquired from an Active Directory or LDAP server, the value null is always returned.

description

string

Description of the user group

builtin

boolean

Whether the user group is a built-in user group

  • true: The user group is a built-in user group.
  • false: The user group is not a built-in user group.

essential

boolean

Whether the user group is an essential user group (opscenter-users)

  • true: The user group is an essential user group.
  • false: The user group is not an essential user group.

external

boolean

Whether the user group was acquired from an external source

  • true: The user group was acquired from an external source.
  • false: The user group was not acquired from an external source.

Coding example

curl -v -X GET -s "https://example.com:443/portal/security/v1/users/a010279b-ae66-4c1d-b066-c45d50c9f75a/user-groups" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Registering a user
The following request registers a user.

Execution permission

You must be a system administrator or a security administrator.

Request line

POST base-URL/security/v1/users

Request message

Object ID
None.
Query parameters
None.
Body
{
    "username": "John_Smith",
    "firstName": "John",
    "lastName": "Smith",
    "email": "john_smith@example.com",
    "description": "John's account",
    "enabled": true
}

Attribute

Type

Description

username

string

(Required) Username

Specify a character string that is no more than 255 characters.

You can use the following characters:

0-9 A-Z a-z ! # $ % & ' ( ) * + - . = @ ^ _ | $

firstName

string

(Optional) First name of the user

Specify a character string that is no more than 64 characters.

lastName

string

(Optional) Last name of the user

Specify a character string that is no more than 64 characters.

email

string

(Optional) Email address

Specify a character string that is no more than 254 characters.

description

string

(Optional) Description of the user account

Specify a character string that is no more than 128 characters.

enabled

boolean

(Required) Whether to enable the user account

  • true: Enables the user account.
  • false: Disables the user account.

Response message

Body
None.

Coding example

curl -v -X POST -H "Content-Type:application/json" -s "https://example.com:443/portal/security/v1/users" -d @./request.json  -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Adding a user to a user group
The following request adds a user to a user group.

Execution permission

You must be a system administrator or a security administrator.

Request line

PUT base-URL/security/v1/users/object-ID-of-the-user/user-groups/object-ID-of-the-user-group

Request message

Object ID of the user

Specify the value of id acquired by using the request for getting information about a list of users.

Attribute

Type

Description

id

string

(Required) Object ID of the user

Object ID of the user group

Specify the value of id acquired by using the request for getting information about a list of user groups.

Attribute

Type

Description

userGroupId

string

(Required) Object ID of the user group

Query parameters
None.
Body
None.

Response message

Body
None.

Coding example

curl -v -X PUT -s "https://example.com:443/portal/security/v1/users/8b39869a-a778-4a08-a2ff-bf967946e836/user-groups/4760d4c0-c593-42fe-b44a-553da4793882" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Updating the registered information for a user
The following request updates the registered information for a user.

The registration information of an identity provider user cannot be updated.

Execution permission

You must be a system administrator or a security administrator.

Request line

PUT base-URL/security/v1/users/object-ID-of-the-user

Request message

Object ID of the user

Specify the value of id acquired by using the request for getting information about a list of users.

Attribute

Type

Description

id

string

(Required) Object ID of the user

Query parameters
None.
Body
{
    "id": "8b39869a-a778-4a08-a2ff-bf967946e836",
    "username": "user_1",
    "firstName": "1",
    "lastName": "user",
    "email": "user_1@email.com",
    "description": "description user_1",
    "enabled": true
}

Attribute

Type

Description

id

string

(Required) Object ID of the user

Specify the value of id acquired by using the request for getting information about a list of users.

username

string

(Required) Username

Specify the username that corresponds to the object ID of the user. You cannot change the username.

firstName

string

(Optional) First name of the user

Specify a character string that is no more than 64 characters.

lastName

string

(Optional) Last name of the user

Specify a character string that is no more than 64 characters.

email

string

(Optional) Email address

Specify a character string that is no more than 254 characters.

description

string

(Optional) Description of the user account

Specify a character string that is no more than 128 characters.

enabled

boolean

(Optional) Whether to enable the user account

  • true: Enables the user account.
  • false: Disables the user account.

Response message

Body
None.

Coding example

curl -v -X PUT -H "Content-Type:application/json" -s "https://example.com:443/portal/security/v1/users/8b39869a-a778-4a08-a2ff-bf967946e836" -d @./request.json  -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Resetting a user's password
The following request resets the password for a user.

The password of an identity provider user cannot be reset.

Execution permission

You must be a system administrator or a security administrator.

Request line

PUT base-URL/security/v1/users/object-ID-of-the-user/reset-password

Request message

Object ID of the user

Specify the value of id acquired by using the request for getting information about a list of users.

Attribute

Type

Description

id

string

(Required) Object ID of the user

Query parameters
None.
Body
{
    "type": "password",
    "value": "P@ssw0rd"
}

Attribute

Type

Description

type

string

(Required) Type of the auth6entication information to be reset

You must specify password for this attribute.

value

string

(Required) New password

Specify a character string that is no more than 256 characters.

Response message

Body
None.

Coding example

curl -v -X PUT -H "Content-Type:application/json" -s "https://example.com:443/portal/security/v1/users/8b39869a-a778-4a08-a2ff-bf967946e836/reset-password" -d @./request.json  -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Deleting a user from a user group
The following request deletes a user registered in a user group.

Execution permission

You must be a system administrator or a security administrator.

Request line

DELETE base-URL/security/v1/users/object-ID-of-the-user/user-groups/object-ID-of-the-user-group

Request message

Object ID of the user

Specify the value of id acquired by using the request for getting information about a list of users.

Attribute

Type

Description

id

string

(Required) Object ID of the user

Object ID of the user group

Specify the value of id acquired by using the request for getting information about a list of user groups.

However, you cannot specify a user group for which essential is set to true.

Attribute

Type

Description

userGroupId

string

(Required) Object ID of the user group

Query parameters
None.
Body
None.

Response message

Body
None.

Coding example

curl -v -X DELETE -s "https://example.com:443/portal/security/v1/users/8b39869a-a778-4a08-a2ff-bf967946e836/user-groups/4760d4c0-c593-42fe-b44a-553da4793882" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Deleting a user
The following request deletes a user.

Execution permission

You must be a system administrator or a security administrator.

Request line

DELETE base-URL/security/v1/users/object-ID-of-the-user

Request message

Object ID of the user

Specify the value of id acquired by using the request for getting information about a list of users.

However, you cannot specify a user for which builtin is set to true.

Attribute

Type

Description

id

string

(Required) Object ID of the user

Query parameters
None.
Body
None.

Response message

Body
None.

Coding example

curl -v -X DELETE -s "https://example.com:443/portal/security/v1/users/8b39869a-a778-4a08-a2ff-bf967946e836" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)

Managing the password policy

The following describes the API requests for managing the password policy.
Getting the password policy
The following request gets the password policy for Common Services.

Execution permission

You must be a system administrator or a security administrator.

Request line

GET base-URL/security/v1/password-policy

Request message

Object ID
None.
Query parameters
None.
Body
None.

Response message

Body
{
    "length": 8,
    "upperCase": 1,
    "lowerCase": 1,
    "digits": 1,
    "specialChars": 1,
    "bruteForceProtected": true,
    "failureFactor": 5
}

Attribute

Type

Description

length

int

Minimum number of characters required for a password

upperCase

int

Minimum number of uppercase characters required in a password

lowerCase

int

Minimum number of lowercase characters required in a password

digits

int

Minimum number of numeric characters required in a password

specialChars

int

Minimum number of symbols required in a password

bruteForceProtected

boolean

Whether to lock a user account after a certain number of unsuccessful login attempts

  • true: Locks the account.
  • false: Does not lock the account.

failureFactor

int

Number of unsuccessful login attempts allowed before a user account is locked

Coding example

curl -v -X GET -s "https://example.com:443/portal/security/v1/password-policy" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Updating the password policy
The following request updates the password policy for Common Services.

Execution permission

You must be a system administrator or a security administrator.

Request line

PUT base-URL/security/v1/password-policy

Request message

Object ID
None.
Query parameters
None.
Body
{
    "length": 8,
    "upperCase": 1,
    "lowerCase": 1,
    "digits": 1,
    "specialChars": 1,
    "bruteForceProtected": true,
    "failureFactor": 5
}

Attribute

Type

Description

length

int

(Required) Minimum number of characters required for a password

Specify a value in the range from 1 to 256.

upperCase

int

(Required) Minimum number of uppercase characters required in a password

Specify a value in the range from 0 to 256. If you do not want to set a minimum for the number of uppercase characters, specify 0.

lowerCase

int

(Required) Minimum number of lowercase characters required in a password

Specify a value in the range from 0 to 256. If you do not want to set a minimum for the number of lowercase characters, specify 0.

digits

int

(Required) Minimum number of numeric characters required in a password

Specify a value in the range from 0 to 256. If you do not want to set a minimum for the number of numeric characters, specify 0.

specialChars

int

(Required) Minimum number of symbols required in a password

Specify a value in the range from 0 to 256. If you do not want to set a minimum for the number of symbols, specify 0.

bruteForceProtected

boolean

(Required) Whether to lock a user account after a certain number of unsuccessful login attempts

  • true: Locks the account.
  • false: Does not lock the account.

failureFactor

int

(Optional) Number of unsuccessful login attempts allowed before a user account is locked

Specify a value in the range from 1 to 256. If you specified true for the bruteForceProtected attribute, you must specify this attribute.

Response message

Body
None.

Coding example

curl -v -X PUT -H "Content-Type:application/json" -s "https://example.com:443/portal/security/v1/password-policy" -d @./request.json  -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)

Managing user groups

The following describes the API requests for managing user groups.
Getting a list of user groups
You can get a list of user groups.

Execution permission

You must be a system administrator or a security administrator.

Request line

GET base-URL/security/v1/user-groups

Request message

Object ID
None.
Query parameters

Parameter

Type

Filter condition

search

string

String that must be included in the name of the user group

Body
None.

Response message

Body
[
    {
        "id": "caf4dd60-5213-430a-907c-17c98c3dca5e",
        "name": "opscenter-administrators",
        "path": "/opscenter-administrators",
        "dn": null,
        "description": null,
        "builtin": true,
        "essential": false,
        "external": false
    }
]

Attribute

Type

Description

id

string

Object ID of the user group

name

string

User group name

path

string

Path

dn

string

Distinguished Name

If the group is not a group acquired from an Active Directory or LDAP server, the value null is always returned.

description

string

Description of the user group

builtin

boolean

Whether the user group is a built-in user group

  • true: The user group is a built-in user group.
  • false: The user group is not a built-in user group.

essential

boolean

Whether the user group is an essential user group (opscenter-users)

  • true: The user group is an essential user group.
  • false: The user group is not an essential user group.

external

boolean

Whether the user group was acquired from an external source

  • true: The user group was acquired from an external source.
  • false: The user group was not acquired from an external source.

Coding example

When no query parameter is specified:

curl -v -X GET -s "https://example.com:443/portal/security/v1/user-groups" -H "Authorization:Bearer eyJhbxxx"

When a query parameter is specified:

curl -v -X GET -s "https://example.com:443/portal/security/v1/user-groups?search=smith" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Getting information about a specific user group
You can get information about a specific user group.

Execution permission

You must be a system administrator or a security administrator.

Request line

GET base-URL/security/v1/user-groups/object-ID-of-the-user-group

Request message

Object ID of the user group

Specify the value of id acquired by using the request for getting information about a list of user groups.

Attribute

Type

Description

id

string

(Required) Object ID of the user group

Query parameters
None.
Body
None.

Response message

Body
{
    "id": "caf4dd60-5213-430a-907c-17c98c3dca5e",
    "name": "opscenter-administrators",
    "path": "/opscenter-administrators",
    "dn": null,
    "description": null,
    "builtin": true,
    "essential": false,
    "external": false
}

Attribute

Type

Description

id

string

Object ID of the user group

name

string

User group name

path

string

Path

dn

string

Distinguished Name

If the group is not a group acquired from an Active Directory or LDAP server, the value null is always returned.

description

string

Description of the user group

builtin

boolean

Whether the user group is a built-in user group

  • true: The user group is a built-in user group.
  • false: The user group is not a built-in user group.

essential

boolean

Whether the user group is an essential user group (opscenter-users)

  • true: The user group is an essential user group.
  • false: The user group is not an essential user group.

external

boolean

Whether the user group was acquired from an external source

  • true: The user group was acquired from an external source.
  • false: The user group was not acquired from an external source.

Coding example

curl -v -X GET -s "https://example.com:443/portal/security/v1/user-groups/caf4dd60-5213-430a-907c-17c98c3dca5e" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Getting a list of users who belong to a specific user group
The following request gets a list of users who belong to a specific user group.

Execution permission

You must be a system administrator or a security administrator.

Request line

GET base-URL/security/v1/user-groups/object-ID-of-the-user-group/users

Request message

Object ID of the user group

Specify the value of id acquired by using the request for getting information about a list of user groups.

Attribute

Type

Description

id

string

(Required) Object ID of the user group

Query parameters
None.
Body
None.

Response message

Body
[
    {
        "id": "a010279b-ae66-4c1d-b066-c45d50c9f75a",
        "username": "sysadmin",
        "firstName": "firstName",
        "lastName": null,
        "email": "sysadmin@example.com",
        "dn": null,
        "description": "Built-in user",
        "enabled": true,
        "builtin": true
    }
]

Attribute

Type

Description

id

string

Object ID of the user

username

string

Username

firstName

string

First name of the user

lastName

string

Last name of the user

email

string

Email address

dn

string

Distinguished Name

If the user is not a user acquired from an Active Directory or LDAP server, the value null is always returned.

description

string

Description of the user account

enabled

boolean

Whether the user account is enabled

  • true: The user account is enabled.
  • false: The user account is disabled.

builtin

boolean

Whether the user is a built-in user

  • true: The user is a built-in user.
  • false: The user is not a built-in user.

Coding example

curl -v -X GET -s "https://example.com:443/portal/security/v1/user-groups/4760d4c0-c593-42fe-b44a-553da4793882/users" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Getting a list of roles that can be assigned to a specific user group
The following request gets a list of roles that can be assigned to a specific user group.

Execution permission

You must be a system administrator or a security administrator.

Request line

GET base-URL/security/v1/user-groups/object-ID-of-the-user-group/role-mappings/portal/available

Request message

Object ID of the user group

Specify the value of id acquired by using the request for getting information about a list of user groups.

Attribute

Type

Description

id

string

(Required) Object ID of the user group

Query parameters
None.
Body
None.

Response message

Body
[
    {
        "id": "e219126f-c858-4fc6-8ad9-9622cc8bddf7",
        "name": "opscenter-security-administrator",
        "description": null,
        "builtin": true,
        "essential": false
    },
    {
        "id": "6eb98bb9-43cc-4062-a25c-185e78afa438",
        "name": "opscenter-system-administrator",
        "description": null,
        "builtin": true,
        "essential": false
    }
]

Attribute

Type

Description

id

string

Object ID of the role

name

string

Role name

description

string

Description of the role

builtin

boolean

Whether the role is a built-in role

  • true: The role is a built-in role.
  • false: The role is not a built-in role.

essential

boolean

Whether the role is an essential role (opscenter-user)

  • true: The role is an essential role.
  • false: The role is not an essential role.

Coding example

curl -v -X GET -s "https://example.com:443/portal/security/v1/user-groups/7a773ca8-49cf-4ee2-9456-eb4853b4c6c1/role-mappings/portal/available" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Getting a list of roles assigned to a specific user group
The following request gets a list of roles assigned to a specific user group.

Execution permission

You must be a system administrator or a security administrator.

Request line

GET base-URL/security/v1/user-groups/object-ID-of-the-user-group/role-mappings/portal

Request message

Object ID of the user group

Specify the value of id acquired by using the request for getting information about a list of user groups.

Attribute

Type

Description

id

string

(Required) Object ID of the user group

Query parameters
None.
Body
None.

Response message

Body
[
    {
        "id": "6eb98bb9-43cc-4062-a25c-185e78afa438",
        "name": "opscenter-system-administrator",
        "description": null,
        "builtin": true,
        "essential": false
    },
    {
        "id": "8c9db2e1-9abb-4f9a-a6a0-d0486faa75c1",
        "name": "opscenter-user",
        "description": null,
        "builtin": true,
        "essential": true
    }
]

Attribute

Type

Description

id

string

Object ID of the role

name

string

Role name

description

string

Description of the role

builtin

boolean

Whether the role is a built-in role

  • true: The role is a built-in role.
  • false: The role is not a built-in role.

essential

boolean

Whether the role is an essential role (opscenter-user)

  • true: The role is an essential role.
  • false: The role is not an essential role.

Coding example

curl -v -X GET -s "https://example.com:443/portal/security/v1/user-groups/4760d4c0-c593-42fe-b44a-553da4793882/role-mappings/portal" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Registering a user group
The following request registers a user group.

Execution permission

You must be a system administrator or a security administrator.

Request line

POST base-URL/security/v1/user-groups

Request message

Object ID
None.
Query parameters
None.
Body
{
    "name": "group_1",
    "description": "description group_1"
}

Attribute

Type

Description

name

string

(Required) Name of the user group

Specify a character string that is no more than 255 characters.

You can use the following characters:

0-9 A-Z a-z ! # $ & ' ( ) + - . = @ [ ] ^ _ ` { } ~ $ space character

You cannot specify space character at the start or end.

description

string

(Optional) Description of the user group

Specify a character string that is no more than 255 characters.

Response message

Body
None.

Coding example

curl -v -X POST -H "Content-Type:application/json" -s "https://example.com:443/portal/security/v1/user-groups" -d @./request.json  -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Assigning a role to a user group
The following request assigns a role to a user group.

Execution permission

You must be a system administrator or a security administrator.

Request line

POST base-URL/security/v1/user-groups/object-ID-of-the-user-group/role-mappings/portal/role-name

Request message

Object ID of the user group

Specify the value of id acquired by using the request for getting information about a list of user groups.

Attribute

Type

Description

id

string

(Required) Object ID of the user group

Role name

Specify the value of name acquired by using the request for getting information about a list of roles that can be assigned to a specific user group.

Attribute

Type

Description

roleName

string

(Required) Role name

Query parameters
None.
Body
None.

Response message

Body
None.

Coding example

curl -v -X POST -s "https://example.com:443/portal/security/v1/user-groups/baf760bc-c789-4cb9-a9cb-662b0b2e4be1/role-mappings/portal/opscenter-security-administrator" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Updating the registered information for a user group
The following request updates the registered information for a user group.

Execution permission

You must be a system administrator or a security administrator.

Request line

PUT base-URL/security/v1/user-groups/object-ID-of-the-user-group

Request message

Object ID of the user group

Specify the value of id acquired by using the request for getting information about a list of user groups.

Attribute

Type

Description

id

string

(Required) Object ID of the user group

Query parameters
None.
Body
{
    "id": "baf760bc-c789-4cb9-a9cb-662b0b2e4be1",
    "name": "name",
    "description": "description"
}

Attribute

Type

Description

id

string

(Required) Object ID of the user group

Specify the value of id acquired by using the request for getting information about a list of user groups.

name

string

(Optional) User group name

Specify a character string that is no more than 255 characters.

You can use the following characters:

0-9 A-Z a-z ! # $ & ' ( ) + - . = @ [ ] ^ _ ` { } ~ $ space character

You cannot specify space character at the start or end.

description

string

(Optional) Description of the user group

Specify a character string that is no more than 255 characters.

Response message

Body
None.

Coding example

curl -v -X PUT -H "Content-Type:application/json" -s "https://example.com:443/portal/security/v1/user-groups/baf760bc-c789-4cb9-a9cb-662b0b2e4be1" -d @./request.json  -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Deleting the role assigned to a user group
The following request deletes the role assigned to a user group.

Execution permission

You must be a system administrator or a security administrator.

Request line

DELETE base-URL/security/v1/user-groups/object-ID-of-the-user-group/role-mappings/portal/role-name

Request message

Object ID of the user group

Specify the value of id acquired by using the request for getting information about a list of user groups.

Attribute

Type

Description

id

string

(Required) Object ID of the user group

Role name

Specify the value of name acquired by using the request for getting information about a list of roles that can be assigned to a specific user group.

However, you cannot specify the opscenter-user role.

Attribute

Type

Description

roleName

string

(Required) Role name

Query parameters
None.
Body
None.

Response message

Body
None.

Coding example

curl -v -X DELETE -s "https://example.com:443/portal/security/v1/user-groups/baf760bc-c789-4cb9-a9cb-662b0b2e4be1/role-mappings/portal/opscenter-security-administrator" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Deleting a user group
The following request deletes a user group.

Execution permission

You must be a system administrator or a security administrator.

Request line

DELETE base-URL/security/v1/user-groups/object-ID-of-the-user-group

Request message

Object ID of the user group

Specify the value of id acquired by using the request for getting information about a list of user groups.

However, you cannot specify a user group for which builtin is set to true.

Attribute

Type

Description

id

string

(Required) Object ID of the user group

Query parameters
None.
Body
None.

Response message

Body
None.

Coding example

curl -v -X DELETE -s "https://example.com:443/portal/security/v1/user-groups/baf760bc-c789-4cb9-a9cb-662b0b2e4be1" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)

Managing linked products

The following describes the API requests for managing products linked with Common Services.
Getting a list of products linked with Common Services
The following request gets a list of products linked with Common Services.

Execution permission

None.

Request line

GET base-URL/app/v1/application-services

Request message

Object ID
None.
Query parameters
None.
Body
None.

Response message

Body
[
    {
        "id": "8a11b0f56d3cf1ac016d3d1aa6a80001",
        "type": "Analyzer",
        "displayType": "Hitachi Ops Center Analyzer",
        "abbreviatedDisplayType": "Analyzer",
        "name": "example.com",
        "description": "",
        "scheme": "https",
        "hostname": "example.com",
        "port": 22016,
        "baseUri": "https://example.com:22016/Analytics",
        "loginScreenUri": "https://example.com:22016/Analytics/oidc_login",
        "licenseRegistrationScreenUri": "https://example.com:22016/Analytics/license.htm",
        "authorizationManagementScreenUri": "https://example.com:22016/Analytics/main.htm?module=administration&param[navi]=ad-sso-usergroup-mgmt",
        "clientConfigurationUri": "https://example.com:22016/Analytics/v1/orionConfig",
        "oidcEnabled": true,
        "oidcRedirectUris": [
            "https://example.com:22016/Analytics/oidc_verify"
        ],
        "internalVersion": 1,
        "statusCheckDisabled": false
    },
    {
        "id": "8a11a1bf6d7012db016dd878c5e50001",
        "type": "AUTOMATOR",
        "displayType": "Hitachi Ops Center Automator",
        "abbreviatedDisplayType": "Automator",
        "name": "example.com",
        "description": "",
        "scheme": "https",
        "hostname": "example.com",
        "port": 22016,
        "baseUri": "https://example.com:22016/Automation",
        "loginScreenUri": "https://example.com:22016/Automation/login",
        "licenseRegistrationScreenUri": "https://example.com:22016/Automation/license.htm",
        "authorizationManagementScreenUri": "https://example.com:22016/Automation/main.htm?module=administrations",
        "clientConfigurationUri": "https://example.com:22016/Automation/v1/application/ClientConfigurations",
        "oidcEnabled": true,
        "oidcRedirectUris": [
            "https://example.com:22016/Automation/callback"
        ],
        "internalVersion": 1,
        "statusCheckDisabled": false
    }
]

Attribute

Type

Description

id

string

Object ID of the product

type

string

Product type

displayType

string

Display type

abbreviatedDisplayType

string

Product abbreviation

name

string

Product name

description

string

Description of the product

scheme

string

Communication protocol

  • http
  • https

hostname

string

Host name of the server running the product

port

int

Port number of the product

baseUri

string

Base URI of the product

loginScreenUri

string

URI of the login screen for the product

licenseRegistrationScreenUri

string

URI of the license registration screen for the product

authorizationManagementScreenUri

string

URI of the authorization management screen for the product

clientConfigurationUri

string

URI of the configuration screen for the product

oidcEnabled

boolean

Whether single sign-on can be used

  • true: Can be used.
  • false: Cannot be used.

oidcRedirectUris

string[]

Redirect URI

internalVersion

int

Internal version of the product

statusCheckDisabled

boolean

Whether to use Common Services to check the product's heartbeat

  • true: Do not check the product's heartbeat.
  • false: Check the product's heartbeat.

Coding example

curl -v -X GET -s "https://example.com:443/portal/app/v1/application-services" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Getting information about a specific product linked with Common Services
The following request gets information about a specific product linked with Common Services.

Execution permission

None.

Request line

GET base-URL/app/v1/application-services/object-ID-of-the-product

Request message

Object ID of the product

Specify the value of id acquired by using the request for getting information about the products linked with Common Services.

Attribute

Type

Description

id

string

(Required) Object ID of the product

Query parameters
None.
Body
None.

Response message

Body
{
    "id": "8a11a1bf6d7012db016dd878c5e50001",
    "type": "AUTOMATOR",
    "displayType": "Hitachi Ops Center Automator",
    "abbreviatedDisplayType": "Automator",
    "name": "example.com",
    "description": "",
    "scheme": "https",
    "hostname": "example.com",
    "port": 22016,
    "baseUri": "https://example.com:22016/Automation",
    "loginScreenUri": "https://example.com:22016/Automation/login",
    "licenseRegistrationScreenUri": "https://example.com:22016/Automation/license.htm",
    "authorizationManagementScreenUri": "https://example.com:22016/Automation/main.htm?module=administrations",
    "clientConfigurationUri": "https://example.com:22016/Automation/v1/application/ClientConfigurations",
    "oidcEnabled": true,
    "oidcRedirectUris": [
        "https://example.com:22016/Automation/callback"
    ],
    "internalVersion": 1,
    "statusCheckDisabled": false
}

Attribute

Type

Description

id

string

Object ID of the product

type

string

Product type

displayType

string

Display type

abbreviatedDisplayType

string

Product abbreviation

name

string

Product name

description

string

Description of the product

scheme

string

Communication protocol

  • http
  • https

hostname

string

Host name of the server running the product

port

int

Port number of the product

baseUri

string

Base URI of the product

loginScreenUri

string

URI of the login screen for the product

licenseRegistrationScreenUri

string

URI of the license registration screen for the product

authorizationManagementScreenUri

string

URI of the authorization management screen for the product

clientConfigurationUri

string

URI of the configuration screen for the product

oidcEnabled

boolean

Whether single sign-on can be used

  • true: Can be used.
  • false: Cannot be used.

oidcRedirectUris

string[]

Redirect URI

internalVersion

int

Internal version of the product

statusCheckDisabled

boolean

Whether to use Common Services to check the product's heartbeat

  • true: Do not check the product's heartbeat.
  • false: Check the product's heartbeat.

Coding example

curl -v -X GET -s "https://example.com:443/portal/app/v1/application-services/8a11a1bf6d7012db016dd878c5e50001" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Getting license information for a specific product linked with Common Services
The following request gets license information for a specific product linked with Common Services.

Execution permission

None.

Request line

GET base-URL/app/v1/application-services/object-ID-of-the-product/license

Request message

Object ID of the product

Specify the value of id acquired by using the request for getting information about the products linked with Common Services.

Attribute

Type

Description

id

string

(Required) Object ID of the product

Query parameters
None.
Body
None.

Response message

Body
{
    "status" : "NOT_ACTIVATED"
}

Attribute

Type

Description

status

string

Status of the license

  • NOT_ACTIVATED: A license is not set up.
  • ACTIVATED: A license has been set up.
  • ACTIVATED_WITH_ISSUES: There is a problem with the license that was set. (Possible reasons include the license being expired or the license capacity being exceeded.)
  • UNKNOWN: The license status is unknown.

Coding example

curl -v -X GET -s "https://example.com:443/portal/app/v1/application-services/8a11a1bf6d7012db016dd878c5e50001/license" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Getting status information for a specific product linked with Common Services
The following request gets status information for a specific product linked with Common Services.

Execution permission

None.

Request line

GET base-URL/app/v1/application-services/object-ID-of-the-product/status

Request message

Object ID of the product

Specify the value of id acquired by using the request for getting information about the products linked with Common Services.

Attribute

Type

Description

id

string

(Required) Object ID of the product

Query parameters
None.
Body
None.

Response message

Body
{
    "connectionStatus" : "ONLINE",
    "trustRelationshipStatus" : "ESTABLISHED"
}

Attribute

Type

Description

connectionStatus

string

Status of connection with Common Services

  • ONLINE: Connected
  • OFFLINE: Not connected

trustRelationshipStatus

string

Single sign-on status

  • ESTABLISHED: Single sign-on is possible.
  • NOT_ESTABLISHED: Single sign-on is not possible.
  • NOT_SUPPORTED: The single sign-on function is not supported.
  • UNKNOWN: The status of the single sign-on setting is unknown.

Coding example

curl -v -X GET -s "https://example.com:443/portal/app/v1/application-services/8a11a1bf6d7012db016dd878c5e50001/status" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Getting version information for a specific product linked with Common Services
The following request gets version information for a specific product linked with Common Services.

Execution permission

None.

Request line

GET base-URL/app/v1/application-services/object-ID-of-the-product/version

Request message

Object ID of the product

Specify the value of id acquired by using the request for getting information about the products linked with Common Services.

Attribute

Type

Description

id

string

(Required) Object ID of the product

Query parameters
None.
Body
None.

Response message

Body
{
    "displayVersion" : "10.0.1-01",
    "internalVersion" : 1
}

Attribute

Type

Description

displayVersion

string

Displayed version

internalVersion

int

Internal version

Coding example

curl -v -X GET -s "https://example.com:443/portal/app/v1/application-services/8a44f59a6f785e31016f78651c820000/version" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)

Managing data centers

The following describes the API requests for managing data centers.
Getting a list of data centers
The following request gets a list of data centers.

Execution permission

None.

Request line

GET base-URL/app/v1/datacenters

Request message

Object ID
None.
Query parameters
None.
Body
None.

Response message

Body
[
    {
        "id": "8a11a1bf6d4378d9016d67206ee70005",
        "name": "Bangkok",
        "description": "",
        "attributes": {
            "city": "Bangkok (Krung Thep Maha Nakhon, Thailand)",
            "latitude": "13.7500",
            "longitude": "100.5166"
        }
    },
    {
        "id": "8a11a1bf6d4378d9016d6723704e000a",
        "name": "Tokyo Data Center",
        "description": "",
        "attributes": {
            "city": "Hachioji (Tokyo, Japan)",
            "latitude": "35.6577",
            "longitude": "139.3261"
        }
    }
]

Attribute

Type

Description

id

string

Object ID of the data center

name

string

Data center name

description

string

Description

attributes

object

Information about the attributes of the data center

Information defined by the user when registering or updating the data center is returned.

Coding example

curl -v -X GET -s "https://example.com:443/portal/app/v1/datacenters" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Getting information about a specific data center
The following request gets information about a specific data center.

Execution permission

None.

Request line

GET base-URL/app/v1/datacenters/object-ID-of-the-data-center

Request message

Object ID of the data center

Specify the value of id acquired by using the request for getting information about a list of data centers.

Attribute

Type

Description

id

string

(Required) Object ID of the data center

Query parameters
None.
Body
None.

Response message

Body
{
    "id": "8a11a1bf6d4378d9016d6723704e000a",
    "name": "Tokyo Data Center",
    "description": "",
    "attributes": {
        "city": "Hachioji (Tokyo, Japan)",
        "latitude": "35.6577",
        "longitude": "139.3261"
    }
}

Attribute

Type

Description

id

string

Object ID of the data center

name

string

Data center name

description

string

Description

attributes

object

Information about the attributes of the data center

Information defined by the user when registering or updating the data center is returned.

Coding example

curl -v -X GET -s "https://example.com:443/portal/app/v1/datacenters/8a11a1bf6d4378d9016d6723704e000a" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Getting a list of products registered in a specific data center
The following request gets a list of products registered in a specific data center.

Execution permission

None.

Request line

GET base-URL/app/v1/datacenters/object-ID-of-the-data-center/application-services

Request message

Object ID of the data center

Specify the value of id acquired by using the request for getting information about a list of data centers.

Attribute

Type

Description

id

string

(Required) Object ID of the data center

Query parameters
None.
Body
None.

Response message

Body
[
    {
        "id": "8a11b0f56d3cf1ac016d3d1aa6a80001",
        "type": "Analyzer",
        "displayType": "Hitachi Ops Center Analyzer",
        "abbreviatedDisplayType": "Analyzer",
        "name": "example.com",
        "description": "",
        "scheme": "https",
        "hostname": "example.com",
        "port": 22016,
        "baseUri": "https://example.com:22016/Analytics",
        "loginScreenUri": "https://example.com:22016/Analytics/oidc_login",
        "licenseRegistrationScreenUri": "https://example.com:22016/Analytics/license.htm",
        "authorizationManagementScreenUri": "https://example.com:22016/Analytics/main.htm?module=administration&param[navi]=ad-sso-usergroup-mgmt",
        "clientConfigurationUri": "https://example.com:22016/Analytics/v1/orionConfig",
        "oidcEnabled": true,
        "oidcRedirectUris": [
            "https://example.com:22016/Analytics/oidc_verify"
        ],
        "internalVersion": 1,
        "statusCheckDisabled": false
    },
    {
        "id": "8a11a1bf6d7012db016dd878c5e50001",
        "type": "AUTOMATOR",
        "displayType": "Hitachi Ops Center Automator",
        "abbreviatedDisplayType": "Automator",
        "name": "example.com",
        "description": "",
        "scheme": "https",
        "hostname": "example.com",
        "port": 22016,
        "baseUri": "https://example.com:22016/Automation",
        "loginScreenUri": "https://example.com:22016/Automation/login",
        "licenseRegistrationScreenUri": "https://example.com:22016/Automation/license.htm",
        "authorizationManagementScreenUri": "https://example.com:22016/Automation/main.htm?module=administrations",
        "clientConfigurationUri": "https://example.com:22016/Automation/v1/application/ClientConfigurations",
        "oidcEnabled": true,
        "oidcRedirectUris": [
            "https://example.com:22016/Automation/callback"
        ],
        "internalVersion": 1,
        "statusCheckDisabled": false
    }
]

Attribute

Type

Description

id

string

Object ID of the product

type

string

Product type

displayType

string

Display type

abbreviatedDisplayType

string

Product abbreviation

name

string

Product name

description

string

Description of the product

scheme

string

Communication protocol

  • http
  • https

hostname

string

Host name of the server running the product

port

int

Port number of the product

baseUri

string

Base URI of the product

loginScreenUri

string

URI of the login screen for the product

licenseRegistrationScreenUri

string

URI of the license registration screen for the product

authorizationManagementScreenUri

string

URI of the authorization management screen for the product

clientConfigurationUri

string

URI of the configuration screen for the product

oidcEnabled

boolean

Whether single sign-on can be used

  • true: Can be used.
  • false: Cannot be used.

oidcRedirectUris

string[]

Redirect URI

internalVersion

int

Internal version of the product

statusCheckDisabled

boolean

Whether to use Common Services to check the product's heartbeat

  • true: Do not check the product's heartbeat.
  • false: Check the product's heartbeat.

Coding example

curl -v -X GET -s "https://example.com:443/portal/app/v1/datacenters/8a11a1bf6d4378d9016d67206ee70005/application-services" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Registering a data center
The following request registers a data center.

Execution permission

You must be a system administrator or a security administrator.

Request line

POST base-URL/app/v1/datacenters

Request message

Object ID
None.
Query parameters
None.
Body
{
    "name": "Yokohama",
    "description": "Data center of Yokohama city",
    "attributes": {
        "city": "Yokohama (Kanagawa, Japan)",
        "latitude": "35.3200",
        "longitude": "139.5800"
    }
}

Parameter

Type

Description

name

string

(Required) Data center name

You cannot use the following characters:

/ \ ^ $ . * + ? ( ) [ ] { } |

You cannot specify space character at the start or end.

description

string

(Optional) Description

attributes

object

(Optional) Information about the attributes of the data center

You can define a pair of any key and any value as a map.

Response message

Body
None.

Coding example

curl -v -X POST -H "Content-Type:application/json" -s "https://example.com:443/portal/app/v1/datacenters" -d @./request.json  -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Updating the registered information for a data center
The following request updates the registered information for a data center.

Execution permission

You must be a system administrator or a security administrator.

Request line

PUT base-URL/app/v1/datacenters/object-ID-of-the-data-center

Request message

Object ID of the data center

Specify the value of id acquired by using the request for getting information about a list of data centers.

Attribute

Type

Description

id

string

(Required) Object ID of the data center

Query parameters
None.
Body
{
    "id": "8a11a1bf6f1c0a95016f8d41c4d7000a",
    "name": "Yokohama",
    "description": "Data center of Yokohama city",
    "attributes": {
        "city": "Yokohama (Kanagawa, Japan)",
        "latitude": "35.3200",
        "longitude": "139.5800"
    }
}

Parameter

Type

Description

id

string

(Required) Object ID of the data center

Specify the value of id acquired by using the request for getting information about a list of data centers.

name

string

(Optional) Data center name

You cannot use the following characters:

/ \ ^ $ . * + ? ( ) [ ] { } |

You cannot specify space character at the start or end.

description

string

(Optional) Description

attributes

object

(Optional) Information about the attributes of the data center

You can define a pair of any key and any value as a map.

Response message

Body
None.

Coding example

curl -v -X PUT -H "Content-Type:application/json" -s "https://example.com:443/portal/app/v1/datacenters/8a11a1bf6f1c0a95016f8d41c4d7000a" -d @./request.json  -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Registering a product linked with Common Services in a data center
The following request registers a product linked with Common Services in a data center.

Execution permission

You must be a system administrator or a security administrator.

Request line

PUT base-URL/app/v1/datacenters/object-ID-of-the-data-center/application-services/application-service-ID

Request message

Object ID of the data center

Specify the value of id acquired by using the request for getting information about a list of data centers.

Attribute

Type

Description

id

string

(Required) Object ID of the data center

Application service ID

Specify the value of id acquired by using the request for getting information about a list of products linked with Common Services.

Attribute

Type

Description

application-service-id

string

(Required) Object ID of the product

Query parameters
None.
Body
None.

Response message

Body
None.

Coding example

curl -v -X PUT -s "https://example.com:443/portal/app/v1/datacenters/8a44f59a6f785e31016f7957f7db0005/application-services/8a44f59a6f785e31016f78651c820000" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Deleting a product linked with Common Services from a data center
The following request deletes a product linked with Common Services from a data center.

Execution permission

You must be a system administrator or a security administrator.

Request line

DELETE base-URL/app/v1/datacenters/object-ID-of-the-data-center/application-services/application-service-ID

Request message

Object ID of the data center

Specify the value of id acquired by using the request for getting information about a list of data centers.

Attribute

Type

Description

id

string

(Required) Object ID of the data center

Application service ID

Specify the value of id acquired by using the request for getting information about a list of products linked with Common Services.

Attribute

Type

Description

application-service-id

string

(Required) Object ID of the product

Query parameters
None.
Body
None.

Response message

Body
None.

Coding example

curl -v -X DELETE -s "https://example.com:443/portal/app/v1/datacenters/8a44f59a6f785e31016f7957f7db0005/application-services/8a44f59a6f785e31016f78651c820000" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)
Deleting a data center
The following request deletes a registered data center.

Execution permission

You must be a system administrator or a security administrator.

Request line

DELETE base-URL/app/v1/datacenters/object-ID-of-the-data-center

Request message

Object ID of the data center

Specify the value of id acquired by using the request for getting information about a list of data centers.

Attribute

Type

Description

id

string

(Required) Object ID of the data center

Query parameters
None.
Body
None.

Response message

Body
None.

Coding example

curl -v -X DELETE -s "https://example.com:443/portal/app/v1/datacenters/8a44f59a6f7d6b59016f7ee8cc210001" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)

Managing the Common Services system information

The following describes the API requests for managing the Common Services system information.
Getting the Common Services version information
The following requests gets information about the Common Services version.

Execution permission

None.

Request line

GET base-URL/system/v1/version

Request message

Object ID
None.
Query parameters
None.
Body
None.

Response message

Body
{
    "version" : "10.1.0",
    "build" : "20191218163524"
}

Attribute

Type

Description

version

string

Product version

build

string

Build version

Coding example

curl -v -X GET -s "https://example.com:443/portal/system/v1/version" -H "Authorization:Bearer eyJhbxxx"
Tip: Because this request uses SSL communication, you must either run the curl command with the root certificate of the Common Services server certificate specified for the --cacert option, or run the command with the -k option specified. (The -k option runs the command by ignoring SSL errors.)

Moving the Analyzer probe server to the Ops Center Protector ISM client VM

If you have the Analyzer probe server and Protector ISM client running on different VMs, you can consolidate them by migrating the Analyzer probe server to the ISM client VM.

Verify that you are running the following versions:

  • ISM server is running version 10.5.0 or later.
  • Analyzer probe server is running version 10.5.0 or later.
  1. Back up the Analyzer probe server.
  2. Back up the RAID Agent.
  3. Verify that the ISM server has sufficient resources to install the Analyzer probe.
  4. Download the Analyzer probe v10.5.0 installer ISO.
    1. Log in to the Support site.
    2. Click DOWNLOAD PRODUCTS AND UPDATES.
    3. Scroll down and select Ops Center Installation Media.
    4. Verify that 10.5.0 is selected, then select Analyzer probe Add-On and click Download.
  5. On the ISM server machine, install the Analyzer probe server using the installer ISO.
  6. Using the backup you created, restore the Analyzer probe on the ISM server.
  7. Restore the RAID Agent.
  8. If the host name or the IP address differs from the backup source host and the restore destination host, complete all of the following procedures that apply:
  9. Set up SSL communication and user passwords as needed. (The Analyzer probe server backup does not include these settings.)
  10. Verify that the Analyzer probe server is functioning correctly.

Backing up the Analyzer probe server

You can back up the settings information of the Analyzer probe server. Information such as user passwords and SSL settings is not backed up. You must reset this information after a restore.

  • Stop all Analyzer probe server services.
  • Make sure that the location where the backup files are to be stored has sufficient space.

  • The properties that are required for this utility are backed up by default. The backup of the optional properties is controlled by the /usr/local/megha/conf/backup.properties file.

    Note the following when editing the file backup.properties:

    • Comment out lines corresponding to information that does not need to be backed up. To comment out a line, enter a hash mark (#) at the beginning of the line.
    • The parameter RAW_BACKUP_DATA is used to back up raw data (data normally transferred to Analyzer detail view server). It is commented out by default. To back up raw data, delete the hash mark (#) at the beginning of the line containing this parameter.
  1. Log on to the Analyzer probe server through an SSH client (like putty) as a root user.
  2. (Optional) Edit the file backup.properties. Delete hash marks (#) from lines that are commented out, as needed.
  3. Run the following command to perform backup.
    sh /usr/local/megha/bin/backupAndRestore.sh -o backup -z zip_file_path
    • zip_file_path

      Specify the name of the directory in which the backed-up data (a ZIP file) is to be saved.

    Example:
    sh /usr/local/megha/bin/backupAndRestore.sh -o backup -z /root/probe_backup
  4. The following settings information is not backed up by backupAndRestore.sh. Write down this information (or record it by other means) because, after the restore, the settings must be manually revised.
    • OS settings (hosts file, passwords of the megha user and meghadata user, and so on)
    • SSL communication settings
    • External user authentication settings (Connection with Active Directory)

Backing up the RAID Agent (Linux)

You can back up the configuration information files and the performance data of the RAID Agent.

Stop all RAID Agent services.
  1. Run the following command to back up the configuration information files.
    /opt/jp1pc/htnm/bin/htmhsbackup -dir output-directory -pdonly
    Note: If you want to collectively back up the configuration information files and the performance data used by API functions that access RAID Agent, run the following command:
    /opt/jp1pc/htnm/bin/htmhsbackup -dir output-directory

    Make sure that the output directory has sufficient free space. Use the size of the following directory as an indication of the estimated amount of required free space:

    Analyzer-probe-server-installation-directory/RAIDAgent

  2. The following files for HTTPS connections are not backed up. If necessary, back them up manually:
    • Server certificate
    • Private key

Installing Analyzer probe server (Linux OS)

To install the Analyzer probe server, run the installer (dcaprobe_install.sh) and follow the prompts.

The installer starts and stops the crond service. Do not run any operations that use the crond service when the installer is running.

Review the following:
  • Review the Analyzer probe server requirements (hardware and software). The Analyzer probe server cannot be installed on a host where the JP1/Performance Management is installed.
  • Install the Analyzer detail view server first. The Analyzer detail view server IP address is required for setting up the Analyzer probe server.
  • Make sure that the ports you specify are available for communication. The default port is 8443. (The default port for SSH is 22.)
  • Verify that you have root permission to run the installer and the precheck tool.
  • Group and other users must have read and execute permissions (755) for the installation path directories.
  • During installation, when prompted to specify the installation directory for the Analyzer probe server, follow these rules:
    • Specify an absolute path.
    • Do not include any symbolic links.
    • Do not specify a directory under /opt/jplpc.
    • Use the following characters only:

      A-Z a-z 0-9 + [ ] , ~ ! # @ { } _ . -

    • Do not use spaces.
  • Check the kernel and system limits on the number of open files and processes. Refer to Increasing the maximum number of open files (Linux OS) for more information.
  • Do not set the COLUMNS environment variable.
  • If firewalld is enabled during installation, settings will be changed for all active zones. If necessary, revise the settings after the installation finishes.
  • Make sure that the time on the Analyzer probe server machine is synchronized with the UTC time. For example, when the time in UTC is 23:00, then time in the Analyzer probe server machine in the PST time zone must be 15:00.
  • When you install the Analyzer probe server, the RAID Agent is installed automatically. Review the RAID Agent requirements before you begin installation:
    • The installation directory is fixed (/opt/jp1pc) and cannot be changed. Make sure that the directory is empty. Do not include any symbolic links in the installation path.
    • You cannot install other components or products in /opt/jp1pc.
    • Make sure that the following directories are not mounted with the noexec option:
      • /tmp
      • /var
      Note: After a successful installation, do not add the noexec option to the /tmp directory. (It might prevent the service from running properly.)
    • When you install the RAID Agent, a temporary work directory jp1pc_AGT is created in the /opt or /opt/jp1pc directory. (This directory is automatically deleted after the installation is successful.)

      If an error occurs during installation, delete it manually if necessary.

    • The IP address must be resolvable from the host name of the host where RAID Agent is installed. Check the hosts file or the domain name system (DNS) server configuration of the host where RAID Agent is installed.
    • The RAID Agent cannot run on hosts that use DHCP to assign IP addresses. You must specify a fixed IP address for Analyzer probe server.
    • The Analyzer probe server can be used in a DNS environment, but does not support FQDN. You must exclude the domain name.
    • Before setting up the RAID Agent, you must specify C for the LANG environment variable on the Analyzer probe server host.

      At startup, RAID Agent is subject to the system LANG environment variable. If the LC_ALL environment variable differs from the LANG environment variable, either unset LC_ALL or change its value to match the LANG value. The following example is an example that sets C for the LANG value and unsets the LC_ALL value.

      Example settings:
      ## Set Environment-variables
      PATH=/sbin:/bin:/usr/bin:/opt/jp1pc/bin
      SHLIB_PATH=/opt/hitachi/common/lib
      LD_LIBRARY_PATH=/opt/hitachi/common/lib
      LIBPATH=/opt/hitachi/common/lib
      HCCLIBCNF=/opt/jp1/hcclibcnf
      LANG=C
      export PATH SHLIB_PATH LD_LIBRARY_PATH LIBPATH HCCLIBCNF LANG
      unset LC_ALL
  • If needed, you can install Virtual Storage Software Agent when you install the Analyzer probe server.
    • If firewalld is enabled, the settings will be changed for the default zone. If required, revise the settings after the installation finishes.
    • For the installation path:
      • Specify an absolute path.
      • Do not include any symbolic links.
      • Do not specify a path of a directory under /opt/jp1pc.
  1. Stop any security monitoring software, antivirus software, and process monitoring software.
  2. Mount the Hitachi Ops Center installation media and copy the directories and files in the DCAPROBE directory on the installation media to a directory on the Linux host.
    Note:
    • You must use only the following characters in the directory path to which the installer is copied: A-Z a-z 0-9 - . _
    • Do not use spaces.
    In the following example, if the /root/DCAPROBE directory already exists, create a new directory, and then perform the subsequent steps in the new directory.
    mkdir /media/OpsImage
    mount /dev/cdrom /media/OpsImage
    cp -rT /media/OpsImage/DCAPROBE /root/DCAPROBE
    
  3. Move to the /root/DCAPROBE directory.
    cd /root/DCAPROBE
  4. Run the precheck tool as a root user to check whether the Analyzer probe server can be installed:
    sh ./dcaprobe_precheck.sh

    If OK is displayed in [ Check results ], you can start the installation. If NG is displayed, make sure the system requirements have been met.

    Output example when the Ops Center Analyzer version is 10.0.0:

    ============================================================
     Ops Center Analyzer probe Precheck          ver. 10.0.0-00
    ============================================================
    
    [ Check results ]
    Ops Center Analyzer probe server [10.0.0-00]            [OK]
    
    [ Details ]
    Check resolved hostname. [host-name (IP-address)]       [OK]
    Check premise OS version.                               [OK]
    Note:
    • When you run the precheck tool, it checks the static information of the system environment.
    • If the -v option is specified, information such as the OS name is also displayed.
  5. Run the following command as root to start the installation:
    sh ./dcaprobe_install.sh NEW

    Do not change the size of the device window while the command is running. If you change the size of the window, the installation fails.

  6. Specify a directory for installing the Analyzer probe server:
    Tip: The prompt displays the default value. To use the default value, simply press the Enter key.
    Specify the path of the directory in which to store application data. [/home]:
    
  7. Specify y to configure the firewall settings. At this time, the firewall rules that are currently applied are saved.
    Do you want to configure the firewall to accept connections from the Ops Center Analyzer probe servers? (y/n) [y]: y 
    
  8. Specify the secure communication information to use for the Analyzer probe server.
    To apply the default settings, press the Enter key in each prompt window.
    [Keytool parameter  ]
    ------------------------------------------------------------
    [INFO] This setting is for SSL configuration.
    What is the name of your organizational unit? [Unknown]: organizational-unit
    What is the name of your organization? [Unknown]: organization
    What is the name of your City or Locality? [Unknown]: city-or-locality
    What is the name of your State or Province? [Unknown]: state-or-province
    What is the two-letter country code for this unit? [Unknown]: two-letter-country-code-for-unit
  9. Specify the password for the megha user.
    [Password for megha user]
    ------------------------------------------------------------
    New password: password-for-megha-user
    Retype new password: password-for-megha-user
    ------------------------------------------------------------
    
  10. Verify the settings that you specified:

    The number of CPAN libraries to be installed varies depending on the environment.

    [Confirmation]
    ------------------------------------------------------------
    Data directory (for the RAID Agent)             : /home/RAIDAgent
    Data directory (for the Ops Center Analyzer probe server): /home
    Port number (for the Ops Center Analyzer probe server): 8443,24221
    Firewall accept rule to be added                :
      Protocol Source IP        Destination IP   Destination PORT
      -------- ---------------- ---------------- ----------------
      ALL      0.0.0.0          0.0.0.0          ALL <RELATED,ESTABLISHED>
      TCP      0.0.0.0          0.0.0.0          24221
      TCP      0.0.0.0          0.0.0.0          8443
      TCP      10.197.195.109   10.197.195.109   ALL
      TCP      127.0.0.1        127.0.0.1        ALL
    Required CPAN libraries                         : Module::Build YAML IO::Pty Date::Calc Net::OpenSSH DateTime DateTime::Format::Strptime Date::Gregorian Log::Log4perl Log::Dispatch::FileRotate Sys::RunAlone LWP::Protocol::https
    Distinguished Name for keytool                  : CN=host-name, OU=organizational-unit, O=organization, L=city-or-locality, ST=state-or-province, C=two-letter-country-code-for-unit
    
    ------------------------------------------------------------
  11. Check the CAUTION message.
                           ** CAUTION **
    
    * This installation will change firewall settings. (Listing above)
    
    * Installation of the required CPAN libraries may take more than 12 minutes.
  12. Unless the CAUTION message includes a problem that requires your attention, enter y.
    Do you want to continue the installation? (y/n) [n]: y 
    Note:
    • Installation of the CPAN library Net::OpenSSH package might display the following prompt:
      root@localhost's password:
      You can ignore this prompt and the installation process will resume in approximately ten seconds.
    • If a warning message appears indicating that an attempt to update the password for the megha user failed, follow the instructions in the message to update the password. The Analyzer probe server will not run properly until the password is updated successfully.
  13. If you want to monitor VSP One SDS Block systems, you must install the required agent.
    Do you want to install the Virtual Storage Software Agent server? (y/n) [n]: y
  14. Specify the directory in which to install the Virtual Storage Software Agent server.
    Tip: The prompt displays the default value. To use the default value, simply press the Enter key.
    Specify the directory to store application data. [/opt/hitachi]:
  15. When prompted, enter y to configure the firewall settings. Specify the IP address of the Analyzer server. You can also accept the default value 0.0.0.0 and configure the IP addresses later. When you enter y, the firewall rules that are currently applied are saved.
    [Firewall parameter ]
    ------------------------------------------------------------
    Do you want to configure the firewall to accept connections from the Ops Center Analyzer server? (y/n) [y]: y
    
    Specify the IP address of the Ops Center Analyzer server,
    so that this IP address will be added in the configuration of firewall,
    and the connection from this server can be accepted.(port 24081/tcp)
    You can also use 0.0.0.0 and change it later.
    [0.0.0.0]:
  16. If your settings are complete, enter y.
    Do you want to continue the installation? (y/n) [n]: y

    When the process is complete, the following message is displayed:

    [INFO] Installation of the Ops Center Analyzer probe servers finished successfully.
    Note: The Analyzer probe server uses the crond service. If the crond service is disabled or stopped, enable and start it.

    As a best practice, you should set the crond service to start automatically when the OS starts.

Restoring the Analyzer probe server

You can restore the settings information of the Analyzer probe server.

  • Stop all Analyzer probe server services on the restore destination host.
  • Make sure that the restore destination directory has sufficient free space.
  • To restore the data, you must have a new setup with settings matching the original, including the following:
    • Version: The base version of the Analyzer detail view server must be same.
    • Deployment Model: The deployment model must be the same. To verify the deployment model, navigate to Manage > Status > License Information.
    • Machine: The machine time zone must be the same, and the machine locale must be English.
  1. Log on to the Analyzer probe server through an SSH client (like putty) as a root user.
  2. Copy the backed-up data to any directory on the restore destination host.
  3. Run the following command on the restore destination host to restore the data.
    sh /usr/local/megha/bin/backupAndRestore.sh -o restore -z zip_file_path
    • zip_file_path

      Specify the path of the backed-up data (a ZIP file) to be restored.

    Example:
    sh /usr/local/megha/bin/backupAndRestore.sh -o restore -z /root/probe_backup/backup-hdca-probe-9.0.0-01_18041109_201806150907.zip
  4. If necessary, reset the following information based on the notes you made during the backup procedure.
    • OS settings
      • The hosts file

        Add connection destination hosts if the backup source host and the restore destination host are different, or if settings were reset when the host OS was reinstalled.

      • Passwords of the megha user and the meghadata user
      • Any other OS settings that were changed
    • SSL communication settings
    • External user authentication settings (Connection with Active Directory)
  5. If you were performing monitoring by using a Linux probe and the IP addresses of the backup source host and restore destination host are different, after performing a restore, delete the Linux probe and then add it back to the Analyzer probe server.
  6. If the Analyzer probe server on the backup source host was using Common Services, run the setupcommonservice command to update the connection settings.
  7. If you are using key-based authentication to transfer data, make sure that you re-configure it. Refer to Configuring key-based authentication to transfer data directly from Analyzer probe server to Analyzer detail view server for more information. When re-configuring the key-based authentication, if you provide a new passphrase, make sure you update the passphrase in the Analyzer probe server UI for primary (and secondary, if applicable) Analyzer detail view server.
  8. If you are using the Common Services, make sure that you re-register the Analyzer probe server with Common Services. Refer to Registering Analyzer probe server with Common Services for more information.

Restoring RAID Agent (Linux)

You can restore the configuration information files and the performance data of RAID Agent.

  • If instances with the same names as those on the backup source do not exist in the restore destination, manually create RAID Agent instances using the same instance names as those on the backup source.
  • Verify that the following items are the same between the backup source host and the restore destination host:
    • OS (Linux or Windows)
    • Version number of the RAID Agent
    • Instance name
    • Hybrid Store storage destination
  • Stop all RAID Agent services on the restore destination host.
  • Verify that the restore destination has free space equal to or greater than the size of the data to be restored.
When transferring backup data to another host, make sure of the following:
  • Binary mode must be used to transfer backup data using FTP.
  • When the backup data is transferred, the data sizes at the source and destinations must match.
  1. Run the following command to restore the backed-up configuration information files:
    /opt/jp1pc/htnm/bin/htmhsrestore -dir storage-directory-of-the-backed-up-data
    Note: If you also backed up performance data, the configuration information files and the performance data are restored.
  2. Run the jpctdchkinst command to check whether the instance is monitoring the targets correctly.
  3. If the instance is not properly monitoring the targets, run the jpcinssetup command to change the settings, and then run the jpctdchkinst command again to check the monitoring status.
  4. The following items cannot be restored by using the htmhsrestore command and must be changed manually:
    • If you changed the port numbers or SSL communication settings in the backup source environment, you must also change them in the restore destination environment by editing the following file.

      /opt/jp1pc/htnm/Rest/config/htnm_httpsd.conf

    • If you changed the port numbers specified in the following files in the backup source environment, you must also change them in the restore destination environment.
      • /opt/jp1pc/htnm/Rest/config/htnm_httpsd.conf
      • /opt/jp1pc/htnm/HBasePSB/CC/server/usrconf/ejb/AgentRESTService/usrconf.properties

Changing the system information of the Analyzer probe server

Use these procedures to change system information such as the host name of the Analyzer probe server, the IP address of the Analyzer probe server, the port number used by the RAID Agent, or the port number used by the RAID Agent REST Web Service.

Changing the IP address of the Analyzer probe server when not monitoring Hitachi Enterprise Storage systems on the host

Change the IP address by performing the following procedure if the Hitachi Enterprise Storage probe is not added.

  1. Perform the following steps to stop the Analyzer probe server services:
    1. Run the following command:
      crontab -e
    2. At the beginning of each line in the standard schedule that was output for the Analyzer probe server, add a hash mark (#) to comment out each line:
      # */5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F
      # */5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\%d`.log; chown -R megha:megha /usr/local/megha/logs/sys)
    3. Run the following command to stop the services:
      /usr/local/megha/bin/megha-jetty.sh stop
  2. Change the IP address of the host on which Analyzer probe server is installed.
  3. If Analyzer probe server is registered with Common Services by using an IP address, run the setupcommonservice command to update the IP address.
    setupcommonservice -appHostname new-IP-address -addPort Port Number
  4. Perform the following steps to start the Analyzer probe server services:
    1. Run the following command:
      crontab -e
    2. Delete the hash marks (#) from the beginning of each line in the standard schedule that generates output for the Analyzer probe server:
      */5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F
      */5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\%d`.log; chown -R megha:megha /usr/local/megha/logs/sys)
    3. Run the following command:
      /usr/local/megha/bin/megha-jetty.sh start
  5. Log on to Analyzer detail view server, and then verify that data is collected.
    1. Log on to Analyzer detail view server.
    2. Click the Server Status icon.
    3. Verify that the probe appears in Last Configuration Import Time and Last Performance Import Time of Data Import Status, and that data is collected.
      Note: It might take some time before the probe appears in the Analyzer detail view server GUI.
  6. Log on to Analyzer server, and then verify that the resources are ready to be analyzed.
    1. Log on to Analyzer server.
    2. In the Administration tab, select Resource Management.
    3. Verify that the resources collected by the probe appear and are ready to be analyzed by Analyzer server.
      Note: It might take some time before the resources collected by the probe appear in the Analyzer server GUI.

Changing the IP address of the Analyzer probe server when monitoring Hitachi Enterprise Storage systems on the host

Change the IP address of the host where the Analyzer probe server is installed. Because RAID Agent and Analyzer Adapter is also installed on the host where the Analyzer probe server is installed, change the IP address by performing the following procedure if the Hitachi Enterprise Storage probe is added.

  1. Perform the following steps to stop the Analyzer probe server services:
    1. Run the following command:
      crontab -e
    2. At the beginning of each line in the standard schedule that was output for the Analyzer probe server, add a hash mark (#) to comment out each line:
      # */5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F
      # */5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\%d`.log; chown -R megha:megha /usr/local/megha/logs/sys)
    3. Run the following command to stop the services:
      /usr/local/megha/bin/megha-jetty.sh stop
  2. Run the following command to stop the Analyzer Adapter services:
    /opt/hitachi/analyzer_adapter/change-etl-config --disable
  3. Run the following command to stop the RAID Agent services.
    /opt/jp1pc/htnm/bin/htmsrv stop -all
  4. Change the IP address of the host on which Analyzer probe server is installed.
  5. Verify that the IP address can be resolved from the host name of the host on which Analyzer probe server is installed.
  6. When Granular Data Collection is enabled, change the IP address of the RAID Agent host defined in the storage_agent_map.txt file to the new IP address.
  7. If the servers that can access RAID Agent are limited (the access source restriction function is configured), change the IP address of the Analyzer probe server defined in the htnm_httpsd.conf file to the new IP address.
  8. If Analyzer probe server is registered with Common Services by using an IP address, run the setupcommonservice command to update the IP address.
    setupcommonservice -appHostname new-IP-address -addPort port-number
  9. Run the following command to start the RAID Agent services.
    /opt/jp1pc/htnm/bin/htmsrv start -all
  10. Run the following command to start the Analyzer Adapter services:
    /opt/hitachi/analyzer_adapter/change-etl-config --enable
  11. Perform the following steps to start the Analyzer probe server services:
    1. Run the following command:
      crontab -e
    2. Delete the hash marks (#) from the beginning of each line in the standard schedule that generates output for the Analyzer probe server:
      */5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F
      */5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\%d`.log; chown -R megha:megha /usr/local/megha/logs/sys)
    3. Run the following command:
      /usr/local/megha/bin/megha-jetty.sh start
  12. Change the settings of Hitachi Enterprise Storage probe as follows:
    1. On the Analyzer probe server home page, stop the target probe and click Edit.
    2. In the Edit Hitachi Enterprise Storage Probe section, enter the IP address of the machine on which the RAID Agent is installed in the RAID Agent IP address field. Then, click Next.
    3. In the Validating Hitachi Enterprise Storage Probe details window, click Next, and then click OK
    4. In the Status window, in ACTION, click Start to start collecting data.
  13. Log on to Analyzer detail view server, and then verify that data is collected.
    1. Log on to Analyzer detail view server.
    2. Click the Server Status icon.
    3. Verify that the probe appears in Last Configuration Import Time and Last Performance Import Time of Data Import Status, and that data is collected.
      Note: It might take some time before the probe appears in the Analyzer detail view server GUI.
  14. Log on to Analyzer server, and then verify that the resources are ready to be analyzed.
    1. Log on to Analyzer server.
    2. In the Administration tab, select Resource Management.
    3. Verify that the resources collected by the probe appear and are ready to be analyzed by Analyzer server.
      Note: It might take some time before the resources collected by the probe appear in the Analyzer server GUI.

Changing the host name of the Analyzer probe server when not monitoring Hitachi Enterprise Storage systems on the host

Use this procedure only if the probe is not added.

  1. Perform the following steps to stop the Analyzer probe server services:
    1. Run the following command:
      crontab -e
    2. At the beginning of each line in the standard schedule that was output for the Analyzer probe server, add a hash mark (#) to comment out each line:
      # */5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F
      # */5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\%d`.log; chown -R megha:megha /usr/local/megha/logs/sys)
    3. Run the following command to stop the services:
      /usr/local/megha/bin/megha-jetty.sh stop
  2. Change the physical host name of the host on which Analyzer probe server is installed.
  3. (Optional) In preparation for adding the Hitachi Enterprise Storage probe, perform the procedures in this step for best results:
    1. Change the monitoring host name of the RAID Agent. The monitoring host name refers to the unique host name that is used to identify internal RAID Agent services.

      Run the jpcconf host hostname  command to change the monitoring host name.

      The following example of the command changes the physical host name to host02:

      /opt/jp1pc/tools/jpcconf host hostname -newhost host02 -d /root/backup
      Do not run any other commands while running the jpcconf host hostname  command.
      Tip: If the command fails, the RAID Agent configuration file is stored in the directory specified for the -d option of the jpcconf host hostname  command. Collect all of the stored configuration files, and then contact the system administrator or aHitachi Vantara Support.
    2. Edit the htnm_httpsd.conf file to specify the new host name of the Analyzer probe server for the ServerName directive in the first line and the ServerName directive in the VirtualHost tag. Make sure that you specify the same name (case sensitive) for the physical host.

      The htnm_httpsd.conffile is stored in the following location:

      /opt/jp1pc/htnm/Rest/config/htnm_httpsd.conf

  4. If Analyzer probe server is registered with Common Services by using a host name, run the setupcommonservice command to update the host name:
    setupcommonservice -appHostname new-host-name -appPort port-number
  5. Perform the following steps to start the Analyzer probe server services:
    1. Run the following command:
      crontab -e
    2. Delete the hash marks (#) from the beginning of each line in the standard schedule that generates output for the Analyzer probe server:
      */5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F
      */5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\%d`.log; chown -R megha:megha /usr/local/megha/logs/sys)
    3. Run the following command:
      Note: If the service automatic startup script is configured, when you restart the OS after changing the host name, the services will start automatically.
      /usr/local/megha/bin/megha-jetty.sh start
  6. Log on to Analyzer detail view server, and then verify that data is collected.
    1. Log on to Analyzer detail view server.
    2. Click the Server Status icon.
    3. Verify that the probe appears in Last Configuration Import Time and Last Performance Import Time of Data Import Status, and that data is collected.
      Note: It might take some time before the probe appears in the Analyzer detail view server GUI.
  7. Log on to Analyzer server, and then verify that the resources are ready to be analyzed.
    1. Log on to Analyzer server.
    2. In the Administration tab, select Resource Management.
    3. Verify that the resources collected by the probe appear and are ready to be analyzed by Analyzer server.
      Note: It might take some time before the resources collected by the probe appear in the Analyzer server GUI.

Changing the host name of the Analyzer probe server when monitoring Hitachi Enterprise Storage systems on the host

Change the host name of the host where the Analyzer probe server is installed. Because RAID Agent and Analyzer Adapter is also installed on the host where the Analyzer probe server is installed, you must also change the host name by performing the following procedure if the Hitachi Enterprise Storage probe is added.

  1. Perform the following steps to stop the Analyzer probe server services:
    1. Run the following command:
      crontab -e
    2. At the beginning of each line in the standard schedule that was output for the Analyzer probe server, add a hash mark (#) to comment out each line:
      # */5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F
      # */5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\%d`.log; chown -R megha:megha /usr/local/megha/logs/sys)
    3. Run the following command to stop the services:
      /usr/local/megha/bin/megha-jetty.sh stop
  2. Run the following command to stop the Analyzer Adapter services:
    /opt/hitachi/analyzer_adapter/change-etl-config --disable
  3. Run the following command to stop the RAID Agent services.
    /opt/jp1pc/htnm/bin/htmsrv stop -all
  4. Change the monitoring host name of the RAID Agent. The monitoring host name refers to the unique host name that is used to identify internal RAID Agent services.

    Run the jpcconf host hostname command to change the monitoring host name.

    The following example of the command changes the physical host name to host02:

    /opt/jp1pc/tools/jpcconf host hostname -newhost host02 -d /root/backup

    Do not run any other commands while running the jpcconf host hostname command.

    Tip: If the command fails, the RAID Agent configuration file is stored in the directory specified for the -d option of the jpcconf host hostname command. Collect all of the stored configuration files, and then contact the system administrator or Hitachi Vantara Support.
  5. Edit the htnm_httpsd.conf file to specify the new host name of the Analyzer probe server for the ServerName directive in the first line and the ServerName directive in the VirtualHost tag. Make sure that you specify the same name (case sensitive) for the physical host.

    The htnm_httpsd.conf file is stored in the following location:

    /opt/jp1pc/htnm/Rest/config/htnm_httpsd.conf
  6. If the servers that can access RAID Agent are limited (the access source restriction function is configured), change the host name of the Analyzer probe server defined in the htnm_httpsd.conf file to the new host name.
  7. Change the physical host name of the host on which Analyzer probe server is installed.
  8. The IP address must be able to be resolved from the host name of the host on which Analyzer probe server is installed. After changing the physical host name, check the hosts file or the domain name system (DNS) server configuration of the host on which Analyzer probe server is installed.
  9. If Analyzer probe server is registered with Common Services by using a host name, run the setupcommonservice command to update the host name:
    setupcommonservice -appHostname new-host-name -appPort port-number
  10. Run the following command to start the RAID Agent services.
    Note: If the service automatic startup script is configured, when you restart the OS after changing the host name, the services will start automatically.
    /opt/jp1pc/htnm/bin/htmsrv start -all
  11. Run the following command to start the Analyzer Adapter services:
    /opt/hitachi/analyzer_adapter/change-etl-config --enable
  12. Perform the following steps to start the Analyzer probe server services:
    1. Run the following command:
      crontab -e
    2. Delete the hash marks (#) from the beginning of each line in the standard schedule that generates output for the Analyzer probe server:
      */5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F
      */5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\%d`.log; chown -R megha:megha /usr/local/megha/logs/sys)
    3. Run the following command:
      Note: If the service automatic startup script is configured, when you restart the OS after changing the host name, the services will start automatically.
      /usr/local/megha/bin/megha-jetty.sh start
  13. Change the settings of Hitachi Enterprise Storage probe as follows:
    1. On the Analyzer probe server home page, stop the target probe and click Edit.
    2. In the Edit Hitachi Enterprise Storage Probe section, enter the host name of the machine on which the RAID Agent is installed in the RAID Agent Hostname field. Then, click Next.
    3. In the Validating Hitachi Enterprise Storage Probe details window, click Next, and then click OK
    4. In the Status window, in ACTION, click Start to start collecting data.
  14. To use the API functions that access RAID Agent, manually refresh the Agent list from the API client. For details, see the Hitachi Ops Center Analyzer REST API Reference Guide.
  15. Log on to Analyzer detail view server, and then verify that data is collected.
    1. Log on to Analyzer detail view server.
    2. Click the Server Status icon.
    3. Verify that the probe appears in Last Configuration Import Time and Last Performance Import Time of Data Import Status, and that data is collected.
      Note: It might take some time before the probe appears in the Analyzer detail view server GUI.
  16. Log on to Analyzer server, and then verify that the resources are ready to be analyzed.
    1. Log on to Analyzer server.
    2. In the Administration tab, select Resource Management.
    3. Verify that the resources collected by the probe appear and are ready to be analyzed by Analyzer server.
      Note: It might take some time before the resources collected by the probe appear in the Analyzer server GUI.

Removing an Ops Center product

To remove an Ops Center product, use the product uninstaller.

Removing Common Services

Remove Common Services by performing the following procedure.
Note: If you remove Common Services, Amazon Corretto 21 and PostgreSQL 15 are not removed. If Common Services was upgraded from an earlier version, Amazon Corretto 8 (version 10.6.0 and earlier), Amazon Corretto 11 (versions 10.6.1 to 10.9.1), Amazon Corretto 17 (versions 10.9.2 to 11.0.2), and PostgreSQL 11 (version 10.9.2 and earlier) might be installed on the management server. If you do not need these programs, remove them by using the rpm command. If you cannot remove the programs by using this command, use the rpm command with the --nopreun option specified.

The package name of each program is as follows:

  • Amazon Corretto 21: java-21-amazon-corretto-devel
  • Amazon Corretto 17: java-17-amazon-corretto-devel
  • Amazon Corretto 11: java-11-amazon-corretto-devel
  • Amazon Corretto 8: java-1.8.0-amazon-corretto-devel
  • PostgreSQL 15: postgresql15, postgresql15-server, postgresql15-libs
  • PostgreSQL 11: postgresql11, postgresql11-server, postgresql11-libs
Before removing Common Services, complete the following:
  • If necessary, back up the data.
  • If any products are registered in Common Services, log in to the Hitachi Ops Center Portal, and delete all products.
  1. Log in to the management server as the root user.
    If you log in as an ordinary user, use the sudo command to complete the following procedure as the root user.
  2. Move to the root directory.
  3. Run the following command:
    installation-directory-of-Common-Services/inst/uninstall.sh

Removing Ops Center Analyzer components

You can remove an Analyzer server, Analyzer detail view server, or Analyzer probe server.

Removing Ops Center Analyzer and Analyzer detail view servers from a Linux host

You can remove Analyzer server and Analyzer detail view server individually or together.

  1. Log on to the Analyzer server or Analyzer detail view server by using a user account with root permission.
  2. Stop any security monitoring software, antivirus software, and process monitoring software.
  3. If you are using the functionality for connecting with Ops Center Automator in the Analyzer server, reset the settings of the Common component.
    If you are removing the Analyzer detail view server only, this step is not required.
  4. Run the following commands:
    cd /opt/hitachi/Analytics/installer
    sh ./analytics_uninstall.sh SYS
  5. When prompted, select the components you want to remove, and then complete the removal process.
    Note:
    • The Analyzer detail view server uninstaller stops the crond service. If you are using the crond service with other programs, start the crond service.
    • Amazon Corretto 17 is not automatically removed even if it was installed during the installation of Analyzer detail view server.

Removing Analyzer probe server

Remove Analyzer probe server using the dcaprobe_uninstall.sh command.

  1. Log on to the Analyzer probe server by using a user account with root permission.
  2. Stop any security monitoring software, antivirus software, and process monitoring software.
  3. Run the following commands:
    cd /opt/hitachi/Analytics/installer
    sh ./dcaprobe_uninstall.sh SYS
    Note: If you leave the Virtual Storage Software Agent and later want to uninstall it, refer to Removing Virtual Storage Software Agent
  4. If there is no problem with uninstalling the probe server, enter y.
    Do you want to continue the uninstallation? (y/n) [n]: y
  5. If Virtual Storage Software Agent is installed, check whether the directory needs to be deleted.
    Do you want to delete the data and log directory? (y/n) [n]:
  6. If there is no problem with uninstalling Virtual Storage Software Agent, enter y.
    Do you want to continue the uninstallation? (y/n) [n]: y
    Note:
    • The Analyzer probe server uninstaller stops the crond service. If you are using the crond service with other programs, start the crond service.
    • Amazon Corretto 17 is not automatically removed even if it was installed during the installation of Analyzer probe server.

Removing Analyzer viewpoint

Use the viewpoint_uninstall.sh command to remove the instance of Analyzer viewpoint.

You must have root privilege.

  1. Log on to the Analyzer viewpoint server.
  2. Stop any security monitoring software, antivirus software, and process monitoring software.
  3. Run the following commands:
    cd /opt/hitachi/analyzer_viewpoint/uninstaller
    bash viewpoint_uninstall.sh SYS
    Do not forcibly stop the host during or immediately after the removal of Analyzer viewpoint. To stop or restart the host, wait until the removal is complete, and then perform the correct procedure (for example, by running an OS command).
  4. Enter the required values according to the prompts, and then complete the removal process.

When you use the viewpoint_uninstall.sh command to remove Analyzer viewpoint, SELinux policy records are not deleted. Delete them as needed. Do not forcibly stop the host immediately after the deletion of the SELinux policy records. Similarly, the following rpm packages will not be removed. Remove them as needed by using the rpm command. If the command fails, run the rpm command with the --nopreun option specified.

  • Amazon Corretto 11
  • PostgreSQL 11*2
  • Kong*1, *2
  • InfluxDB
*1: Before you remove Kong, delete the Lua modules in the following order.
/usr/local/bin/luarocks remove lua-resty-openidc
/usr/local/bin/luarocks remove lua-resty-jwt

*2: This file exists if you upgraded Analyzer viewpoint from a version earlier than 11.0.0.

Removing Virtual Storage Software Agent

To remove Virtual Storage Software Agent:

  1. Log on as root on the host where Virtual Storage Software Agent is installed.
  2. Stop any security monitoring software, antivirus software, and process monitoring software.
  3. Run the following command:
    cd /Virtual-Storage-Software-Agent-installation-directory/VirtualStorageSoftwareAgent/uninstaller
    sh ./uninstall.sh SYS
    Note: Amazon Corretto is not automatically removed even if it was installed during the installation of Virtual Storage Software Agent.

When you use the uninstall.sh command to remove Virtual Storage Software Agent, SELinux policy records that were added for Red Hat Enterprise Linux/Oracle Linux are not deleted. Delete them as needed. Do not forcibly stop the host immediately after the deletion of the SELinux policy records.

Removing Ops Center Administrator

To remove an Ops Center Administrator deployment that was installed with the application installer, you must delete any Ops Center Administrator containers, images, and files. Select one of the following procedures based on your Ops Center Administrator implementation:

Note: Ops Center Administrator uses rdocker:6000 as an image repository.

Removing Ops Center Administrator when using Docker

If your installation uses Docker as the container runtime, remove Ops Center Administrator as follows:

  1. From the command prompt, log in to the OS using the root account.
  2. Stop all containers and services by using the following command:
    docker stop $(docker ps --format "{{.ID}} {{.Image}}" -a | grep "rdocker:6000/" | awk '{ print $1 }')
    systemctl stop rainier-pipe
    systemctl disable rainier-pipe
  3. Remove all containers by using the following command:
    docker rm -fv $(docker ps --format "{{.ID}} {{.Image}}" -a | grep "rdocker:6000/" | awk '{ print $1 }')
  4. Remove all Docker images by using the following command:
    docker rmi $(docker images --format "{{.ID}} {{.Repository}}" | grep "rdocker:6000/" | awk '{ print $1 }')
  5. Remove all Docker volumes by using the following commands:
    docker volume rm nginx-certificates
    docker volume rm nginx-certificates-override
    docker volume rm nginx-confd
    docker volume rm nginx-log
  6. To remove the configuration files, run the following command:
    /opt/rainier/bin/rainier-config-remove
  7. To remove the remaining files, run the following commands:
    rm -rf /opt/rainier
    rm -rf /var/log/rainier-audit-log
    rm -rf /var/logs/rainier-tool
    rm -rf /var/logs/rainier-elastic-store
    rm -rf /var/logs/rainier-logs
    rm -rf /var/logs/rainier-ubi
    rm -rf /var/opt/rainier-ubi
    rm -f /etc/systemd/system/rainier-pipe.service
    

Removing Ops Center Administrator when using Podman

If your installation uses Podman as the container runtime, remove Ops Center Administrator as follows:

  1. From the command prompt, log in to the OS using a root user or a normal user account. If you log in as a normal user, use the sudo command to complete the following procedure as the root user.
  2. Stop all containers and services by using the following commands:
    systemctl stop rainier
    systemctl disable rainier
    systemctl stop rainier-pipe
    systemctl disable rainier-pipe
  3. Remove all containers by using the following command:
    podman rm -fv $(podman ps --format "{{.ID}} {{.Image}}" -a | grep "rdocker:6000/" | awk '{ print $1 }') 2>/dev/null
  4. Remove all Podman images by using the following command:
    podman rmi $(podman images --format "{{.ID}} {{.Repository}}" | grep "rdocker:6000/" | awk '{ print $1 }')
  5. Remove all Podman volumes by using the following commands:
    podman volume rm nginx-certificates
    podman volume rm nginx-certificates-override
    podman volume rm nginx-confd
    podman volume rm nginx-log
  6. To remove the configuration files, run the following command:
    /opt/rainier/bin/rainier-config-remove
  7. To remove the remaining files, run the following commands:
    rm -rf /opt/rainier
    rm -rf /var/log/rainier-audit-log
    rm -rf /var/logs/rainier-tool
    rm -rf /var/logs/rainier-elastic-store
    rm -rf /var/run/host-manager.sock
    rm -rf /var/logs/rainier-logs
    rm -rf /var/logs/rainier-ubi
    rm -rf /var/opt/rainier-ubi
    rm -f /etc/systemd/system/rainier.service
    rm -f /etc/systemd/system/rainier-pipe.service
    rm -f /etc/containers/containers.conf.d/rainier.conf
    
    Note: When using Podman 4.0.x, the SELinux label of the /var/run/podman/podman.sock file is relabeled as container_file_t and the podman.socket service cannot be restarted, which generates an access error. Check whether there is a container_file_t label by running the following command:
    ls -Z /var/run/podman/podman.sock
    For example,
    # ls -Z /var/run/podman/podman.sock
    system_u:object_r:container_file_t:s0 /var/run/podman/podman.sock
    If there is a container_file_t label, restore the original label by running the following command:
    restorecon -F /var/run/podman/podman.sock

Removing Ops Center Automator

This module describes how to remove Ops Center Automator.

Removing Ops Center Automator (Windows OS)

You can remove Ops Center Automator in a Windows environment by completing the steps listed in the following sections.

  • If tasks in the Status column of the Tasks tab of Ops Center Automator are in the Waiting, Waiting for Input, In Progress, Long Running, or In Progress (with Error) state, wait until the tasks stop or finish running.
  • Close all of the service dialog boxes.
  • Close any Windows Services or open command prompts.
  • Disable any security monitoring, virus detection, or process monitoring software on the server.
    CAUTION:
    If other Common Component products are installed in the same host, do not delete the shared folder (\Base64). If you delete this folder, other Common Component products will not work properly.
  1. Log on to Windows OS as a user with Administrator permissions.
  2. Run the following command to stop all services:
    Common-Component-installation-folder\bin\hcmds64srv /stop
  3. Open the Control Panel, and then choose Programs and Features or Uninstall a Program.
  4. Select Hitachi Ops Center Automator, and then click Uninstall, or select the program, right-click, and select Uninstall.
  5. In the Automation Software window, click Next > Remove to start the software removal process.
    The removal process deletes the Ops Center Automator installation folder.
  6. If you use Common Services, delete Ops Center Automator information from Common Services.

Ops Center Automator is removed from the host.

Microsoft Visual C++ 2015-2022 Redistributable (x64) is not automatically removed. Make sure that other programs are not dependent on it, and remove it manually.

Deleting authentication data (Windows OS)

If the KNAE04574-E warning dialog box appears although the removal completes successfully, the deletion of authentication data failed. Delete the data by running the hcmds64intg command on the server that administers user accounts (on the host running the product using Common Component and connected to the server)

To run the hcmds64intg command to delete the authentication data from a Windows host:

  1. Start all installed services of the products using Common Component products by running the following command:
    Common-Component-installation-folder\bin\hcmds64srv /start
  2. Delete the authentication data by running the following command: Common-Component-installation-folder\bin\hcmds64intg /delete /type component-name /user user-id /pass password
    • /type

      Specify the name of the component that you want to delete. Automation can be specified.

    • /user

      Specify the user ID of a user who has the Admin (user management) permission. If you run the command without the user option, you are prompted to specify a user ID.

    • /pass

      Specify the password of a user who has the Admin (user management) permission. If you run the command without the pass option, you are prompted to specify a password.

    Note: If you display a GUI window of another product using Common Component without deleting the authentication data, the following problems might occur, even after removing the Ops Center Automator server:
    • User management information of the Ops Center Automator server displays.

    • The button used to start the Ops Center Automator server is enabled on the dashboard. Clicking the enabled button causes a link error to appear.
    Note: If you use Common Services, see the Hitachi Ops Center online help for the steps to delete a user account.

Removing Ops Center Automator (Linux OS)

You can remove Ops Center Automator in a Linux OS environment as listed in the following procedure.

  1. Run the following command: Directory-specified-when-installing-Automation-software/ADUninstall/uninstall.sh
  2. If you use Common Services, delete Ops Center Automator information from Common Services.
Deleting authentication data (Linux OS)

If the KNAE04574-E warning dialog box appears although the removal completes successfully, the deletion of authentication data failed. Delete the data by running the hcmds64intg command on the server that administers user accounts (on the host running the product using Common Component and connected to the server)

  1. Start all installed services of the products using Common Component product by running the following command:
    Common-Component-installation-directory/bin/hcmds64srv -start
  2. Delete the authentication data by running the following command: Common-Component-installation-directory/bin/hcmds64intg -delete -type component-name -user user-id -pass password
    • -type

      Specify the name of the component that you want to delete. Automation can be specified.

    • -user

      Specify the user ID of a user who has the Admin (user management) permission. If you run the command without the user option, you are prompted to specify a user ID.

    • -pass

      Specify the password of a user who has the Admin (user management) permission. If you run the command without the pass option, you are prompted to specify a password.

    Note: If you display a GUI window of another product using Common Component without deleting the authentication data, the following problems might occur, even after removing the Ops Center Automator server:
    • User management information of the Ops Center Automator server displays.

    • The button used to start the Ops Center Automator server is enabled on the dashboard. Clicking the enabled button causes a link error to appear.
    Note: If you use Common Services, see the Hitachi Ops Center online help for the steps to delete a user account.

Removing Ops Center Automator software in a cluster environment

You can remove the Ops Center Automator software from the server in a cluster environment to migrate to a different server or stop Ops Center Automator processes.

Note: If you remove Ops Center Automator, the properties files, log files, and other product-related files are deleted.
  1. In the cluster management software, move the group in which the Common Component services are registered from the standby node to the active node by right-clicking the group, selecting Move, and then either Select Node or Move this service or application to another node.
  2. Take offline and disable failover for the group in which Common Component services including Ops Center Automator are registered by using the following command:

    Common-Component-installation-directory\ClusterSetup\hcmds64clustersrvstate /soff /r cluster-group-name

    where

    r - specifies the name of the group in which the Common Component product services including Ops Center Automator are registered. If the group name contains spaces, you must enclose the group name in quotation marks ("). For example, if the group name is Automator cluster, specify "Automator cluster".

  3. Delete the Common Component services including Ops Center Automator by using the following command:
    Note: Before deleting the services, delete the "customer script" from the cluster management software.

    Common-Component-installation-directory\ClusterSetup\hcmds64clustersrvupdate /sdel /r cluster-group-name

    where

    r - specifies the name of the group in which the Common Component product services including Ops Center Automator are registered. If the group name contains spaces, you must enclose the group name in quotation marks ("). For example, if the group name is Automator cluster, specify "Automator cluster".

    Note:
    • All Ops Center Automator and Common Component product services that are registered in the group specified by the r option are deleted.
    • If you plan to continue using Common Component products, reregister them after you remove Ops Center Automator. Deleting the Ops Center Automator service does not cause a problem.

      Remember that if you changed the service resource names, all resource names are reinitialized when the services are reregistered. Therefore, you must write down the resource names for the services that you are deleting, and change the names after reregistering those services.

  4. Use the following command to stop the Common Component products:
    Common-Component-installation-folder\bin\hcmds64srv /stop
  5. Remove Hitachi Ops Center Automator from the active node.
  6. On the active node, delete any files and folders that are no longer required (such as those files and folders created during installation in the cluster environment).
  7. In the cluster management software, move the Ops Center Automator service group to the standby node by right-clicking the group, selecting Move, and selecting either Select Node or Move this service or application to another node.
  8. Remove Ops Center Automator from the standby node.
  9. After performing the removal of the cluster installation, delete the Ops Center Automator folder and, if you no longer plan to use any other Common Component services, also delete the Base64 folder from the standby node.
  10. If the following resources are not in use by other applications, use the cluster management software to take them offline, and then delete them:
    • IP address
    • Shared disk
  11. On the standby node, delete any files and folders that are no longer required (such as those files and folders created during installation in the cluster environment).
  12. To continue using other Common Component products, use the following command to register the Common Component services in the cluster management software group:

    Common-Component-installation-folder\ClusterSetup\hcmds64clustersrvupdate /sreg /r cluster-group-name /sd drive-letter-of-shared-disk /ap resource-name-for-client-access-point

    where

    r - specifies the name of the group in which you to plan to register the Common Component product services. If the group name contains spaces, you must enclose the group name in quotation marks ("). For example, if the group name is Automator cluster, specify "Automator cluster".

    sd - specifies the drive letter of the shared disk that is registered to the cluster management software. You cannot specify multiple drive letters for this option. If the database of Common Component products is divided into multiple shared disks, run the hcmds64clustersrvupdate command for each shared disk.

    ap - specifies the name of the resource for the client access point that is registered to the cluster management software.

  13. To continue using other Common Component products, use the following command to bring online and enable failover for the group in which the Common Component services are registered:

    Common-Component-installation-folder\ClusterSetup\hcmds64clustersrvstate /son /r cluster-group-name

    where

    r - specifies the name of the group in which the Common Component product services are registered. If the group name contains spaces, you must enclose the group name in quotation marks ("). For example, if the group name is Automator cluster, specify "Automator cluster".

  14. In the cluster management software, move the group containing the Common Component resources to the active node by right-clicking the group, selecting Move, and then selecting either Select Node or Move this service or application to another node.
  15. If you are using Common Services, delete the Ops Center Automator information from Common Services.

Ops Center Automator is removed from both the active and standby nodes.

Microsoft Visual C++ 2015-2022 Redistributable (x64) is not automatically removed. Make sure that other programs are not dependent on it, and remove it manually.

Remove the software

CAUTION:
  • The Master does not deactivate active rules on Client nodes. To do this, you must deactivate all data flows before uninstalling, or uninstall the Clients individually.
  • Before removing the application, the node (and any nodes proxied from it) must be removed from all dataflows, be unauthorized, and deleted from the UI.

Operating System Specific Behavior:

OS Note
Linux and AIX Completely removing the software from a Linux or AIX machine is straightforward. Enter the following commands and follow the on-screen instructions:

/opt/hitachi/protector/uninstall

rm -rf /opt/hitachi/protector

Windows Completely removing the software from a Windows machine involves significantly more work, due partly to the additional functionality available on Windows nodes. Follow the steps listed below.
  1. Make a note of the path for the install directory and any repositories or ISMs. These will be required later if you wish to completely remove all traces of the installation and do not want to retain backup data stored in the repositories.
  2. From the Start menu run Uninstall Hitachi Ops Center Protector. Alternatively, navigate to the installation directory and execute the command uninstall.exe.
    A dialog will be displayed asking you to confirm that you wish to proceed. Running the command uninstall.exe --mode unattended will cause the uninstall process to proceed without requiring user interaction; although popups may briefly appear before being automatically dismissed.
  3. Click Yes to proceed with the uninstall process (or No to abort the process).
    A Setup dialog is displayed containing an Uninstall Status bar and information about what actions are currently being performed.
  4. At some point during the uninstallation process you may be presented with a Warning dialog telling you that any repositories must be manually deleted. The uninstall process will pause until you click OK.
    Manual removal of repositories is covered later on.
  5. Eventually an Info dialog will be displayed stating that the uninstall process is complete. Click OK.
  6. Delete any repository directories noted down before uninstalling. Ensure that there are no files or windows open at these locations or attempts at deletion may fail.
    The software and its repositories are now uninstalled and you can end the procedure at this point.

    Some artifacts will remain on your machine. These items are left in place either to facilitate easier reinstallation or because they remained after upgrading from an earlier version or from a failed install. If you want to remove these artifacts, then continue with the following steps:

  7. Delete the installation directory tree noted down before uninstalling. Ensure that there are no files or windows open at this location or attempts at deletion may fail.
  8. A hidden directory Protector-RecycleBin may remain in the root directory. This can be removed.
  9. Delete the Bitrock installer log files bitrock_installer.log and bitrock_installer_<nnnn>.log normally located in C:\Users\Administrator\AppData\Local\Temp
  10. Open the Windows Registry Editor from the Start > Run... dialog by entering regedit.exe in the Open: field.
    The Registry Editor window is displayed. Alternatively use the reg delete command from within a Command Prompt.
  11. Carefully delete the following registry keys:
    CAUTION:
    Incorrectly editing the Registry can cause the operating system to become unstable or stop working. Exercise extreme caution when performing this step.
    • HKEY_LOCAL_MACHINE\SOFTWARE\Cofio Software
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cofio Software
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CofioHub
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\dcefltr
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sdrefltr
    • HKEY_LOCAL_MACHINE\SOFTWARE\Hitachi\Hitachi Ops Center Protector
  12. Confirm that the dcefltr and sdrefltr filter drivers are no longer installed on your system by entering the commands sc query dcefltr and sc query sdrefltr.
    You should see the following output in response to both commands:
    The specified service does not exist as an installed service.
Occasionally an uninstallation may fail to complete successfully. In this situation there are a number of things that can be done before retrying:
  • Ensure any files or folders that can block the uninstallation are closed.
  • Reboot the machine to return it to a known, stable state.
  • Reinstall the softeware over the existing partially-uninstalled version. In most cases this will allow an uninstallation to be completed successfully.

Removing the REST API

To discontinue use of the REST API, remove the REST API server.

Use the REST API uninstaller to remove the REST API.

In Linux, if the REST API was installed by a non-root user, the REST API must be removed by the same user.

Note: In the following cases, CCI will remain (it will not be deleted) even after you remove the REST API. Remove CCI if it is no longer needed.
  • If CCI was installed in advance on the management server
  • If the OS of the management server is Linux and CCI was installed after the REST API was installed

    In this case, CCI is installed in the /HORCM directory.

Removing the REST API (in a Windows OS)

Use the Windows menu Programs and Features to remove the REST API.
  • Stop the event log monitoring program.

    If the event log monitoring program is running, the REST API might not be completely removed. In such cases, check the output error message and take action as appropriate.

  • Stop any programs that are using the CCI that was provided with the REST API.

    If CCI files are used in an environment where the CCI provided with the REST API is installed, you will not be able to uninstall the REST API.

Note:

If the installation path of the REST API includes a space and a file whose path matches the installation path up to the first space, an attempt to remove the REST API might end in an error. For example, if the installation destination is C:\Program Files\hitachi\ConfManager and C:\ contains a file called Program, installation might end in an error. In such cases, change the file name, or move or delete the file.

  1. Log on to the management server as a user with Administrator permissions.
  2. If necessary, back up the REST API database and the environment settings file.
  3. To delete a REST API server, which is to be removed, from the configuration-change notification destinations registered in storage systems, delete the storage system information.
  4. Select Control Panel > Programs and Features > Configuration Manager REST API, and then click the Uninstall button.
  5. Perform operations according to the instructions in the uninstallation wizard.
    If the API is successfully removed, the Uninstallation Complete window appears.

Removing the REST API as the root user (in a Linux OS)

Run uninstall.sh to remove the REST API.
Note:

During the removal of the REST API, do not set the noexec option that restricts the execution of programs in the /tmp and /var/tmp directories.

You can check whether the noexec option is set by running the mount command.

After the removal of the REST API finishes, set the option to restrict the execution of programs in those directories as needed.

  • The COLUMNS environment variable must not be set.

    If you perform an uninstallation while the COLUMNS environment variable is set, the uninstallation might not end normally.

  • Stop any programs that are using the CCI that was provided with the REST API.

    If CCI files are used in an environment where the CCI provided with the REST API is installed, you will not be able to uninstall the REST API.

  1. Log in to the management server as the root user.
  2. If necessary, back up the REST API database and the environment settings file.
  3. To delete a REST API server, which is to be removed, from the configuration-change notification destinations registered in storage systems, delete the storage system information.
  4. Move to the root directory.
  5. Run the following command:
    REST-API-installation-destination/inst/uninstall.sh
  6. Perform operations according to the instructions in the message that appears.

    If the API is successfully removed, the following message appears:

    Configuration Manager REST API removal completed successfully.

Removing the REST API in a cluster environment

You can remove the REST API when the REST API is used in a cluster environment.
Run one of the following commands to check the path of the shared directory on the shared disk:
In a Windows OS:
REST-API-installation-destination\bin\configureCluster.bat -get
  1. If necessary, back up the REST API database and the environment settings file.
  2. To delete a REST API server, which is to be removed, from the configuration-change notification destinations registered in storage systems, delete the storage system information.
  3. Use the cluster management application to remove the REST API server script that is registered in the resource group or the service group.
  4. Stop the REST API service on the active node, and then run the following command to clear the cluster environment settings.
    REST-API-installation-destination\bin\configureCluster.bat -local

    Option

    local
    The cluster configuration is removed and the node begins operating in a non-cluster configuration.
  5. Remove the REST API from the active node.
  6. Stop the REST API service on the standby node, and then run the following command to clear the cluster environment settings.
    REST-API-installation-destination\bin\configureCluster.bat -local

    Option

    local
    The cluster configuration is removed and the node begins operating in a non-cluster configuration.
  7. Remove the REST API from the standby node.
  8. Remove the shared directory on the shared disk.