- Log in to the Ops Center portal as sysadmin or a user with opscenter-administrators membership.
- Click the Settings icon and select Warning banner.
- You can customize the default message or compose a new one. Click Submit when the changes are complete.
Maintain Hitachi Ops Center
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:
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 |
|
|
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
hcmds64srv -start
hcmds64srv -stop
hcmds64srv -status
hcmds64srv -start -server AnalyticsWebService
Checking 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
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
Starting 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
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.
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
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
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.
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
| Abbreviated argument | Full argument | Description |
|---|---|---|
| -h | --help | Display help. |
| 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. |
|
| 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). |
|
| 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. | |
| 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. |
| 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. | |
| 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).
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.
- 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.
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.
- 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
- Analyzer probe server:
- Log on to the Analyzer detail view server or Analyzer probe server as the megha user.
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.
Starting the RAID Agent services
- 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:
-
- Run the following command. In Linux
/opt/jp1pc/htnm/bin/htmsrv start -all
In WindowsRAID-Agent-installation-folder\raid_agent\jp1pc\htnm\bin\htmsrv start -all
- 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
- Run the following command.
- 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):
-
- From the Windows Start menu, select .
- 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.
- 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
- 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)
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.
Procedure
- To enable automatic starting and stopping:
-
- Run the following command to stop the RAID Agent
services:
/opt/jp1pc/htnm/bin/htmsrv stop -all
- Run the following command and verify that the services have stopped.
/opt/jp1pc/htnm/bin/htmsrv status -all
- 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
- 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
- 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
- Run the following command to stop the RAID Agent
services:
systemctl stop jp1_pc.service /opt/jp1pc/htnm/bin/htmsrv stop -webservice
- Run the following command to start the RAID Agent
services:
systemctl start jp1_pc.service /opt/jp1pc/htnm/bin/htmsrv start -webservice
- Run the following command to stop the RAID Agent
services:
- To disable automatic starting and stopping:
-
- Run the following command to stop the RAID Agent
services:
systemctl stop jp1_pc.service /opt/jp1pc/htnm/bin/htmsrv stop -all
- Run the following command and verify that the services have stopped.
/opt/jp1pc/htnm/bin/htmsrv status -all
- 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
- 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
- Run the following command to start the RAID Agent
services:
/opt/jp1pc/htnm/bin/htmsrv start -webservice
- Run the following command to stop the RAID Agent
services:
Starting the Virtual Storage Software Agent services
To start the Virtual Storage Software Agent services:
Stopping the Virtual Storage Software Agent services
To stop the Virtual Storage Software Agent services:
Starting the On-demand real time monitoring module services
You can start the On-demand real time monitoring services.
Stopping the On-demand real time monitoring module services
To stop the On-demand real time monitoring services:
Starting the Analyzer Windows probe service
Start the probe service from the Status tab in the Analyzer Windows probe console.
Checking the validity period of a certificate in the truststore
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
installation-directory-of-Common-Services/jdk/bin/keytool -printcert -file path-of-server-certificate
Checking the revocation status of the server certificate
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:
- Web browser: Checking the revocation status of the server certificate by using a web browser
- openssl command: Checking the revocation status of the server certificate by using a command
- Automatically by using cron: Checking the revocation status of the server certificate on a regular basis
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.
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.
Checking the revocation status of the server certificate on a regular basis
Sending the revocation status check results to a file
- 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
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
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.
Changing the port number used for internal communications
Backing up and recovering Hitachi Ops Center applications
Backing up and restoring Hitachi Ops Center applications using Protector
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:
- Restoring backup archives to the proper node using Protector.
- Recovering each application by manually extracting the archive and running the required commands to bring it back online.
Before starting a backup or recovery, review the following:
Prerequisites and cautions for backing up Hitachi Ops Center applications
| Application | Precautions |
|---|---|
| All |
|
| Administrator |
Before backing up Administrator, verify the following:
|
| 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 |
|
| API Configuration Manager |
|
| 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
| 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:
|
|||
- Open the /etc/systemd/system.conf file and add the
following:
DefaultEnvironment="UBI_BACKUP_TMP_DIR=directory"
- Restart the OS.
Backing up Ops Center applications using Protector
- 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.
- Log in to the Protector UI.
- In the Policies window, click the plus (+) icon near the top of the screen, enter a name (example: MasterBackup), and click Next.
- Click Next to skip Allocate Policy to Access Control Resource Group.
- In the Add one or more Classifications window, click on the plus (+) icon, click Application, select Ops Center, and click Next.
- 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.
- In the Add one or more Operations window, click the plus (+) icon, select Backup, and click Next.
- 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.
- Select Data Flows, click the plus (+) icon, enter a name (example: MasterBackup) and click Next.
- Click Next to skip Allocate Policy to Access Control Resource Group.
- 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.
- Click the master node and select MasterBackup from the Policies list.
- Click the repository and select MasterBackup from the Policies list.
- Click Finish.
- In Data Flows, select MasterBackup from the list, and click the play icon in the toolbar.
- In Activate Data Flows, click Activate.
- 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.)
- Select the operation and click Run Now. You can check the overall progress in the Jobs window or the details in the Log window.
Restoring Ops Center application archives using Protector
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.
- In the Restore window, select the backup from the list and click the restore icon.
- In Select restore options, choose the Destination Node to which you want the backup archive exported.
- Click Finish.
- 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
The recovery process for each product is described in the sections that follow:
Recovering Administrator
- 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.
- Click Restore and either drag and drop the backup file or click the plus sign (+) to browse.
- Click Submit. The restore procedure can take up to an hour, after which Administrator restarts.
- Remove and reregister Administrator in Common Services.
- Remove Administrator from Common Services by going to the Hitachi Ops Center Portal and deleting it.
- Run the setupcommonservice command to register with Common Services.
- If necessary, change permissions for user groups.
Recovering Analyzer
- Run the tar command to extract
the backup archive file.
tar xf backup-archive-file -C destination-directory
- Run the following restoresystem
command.
Analyzer-installation-directory/Analytics/bin/restoresystem -dir destination-directory -type all
Recovering Analyzer RAID Agent
<For Linux>
- 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.
- Confirm that the same name instance exists as when the backup was taken, and if it does not exist, create it.
- Copy the backup archive file to a working directory and extract
it:
tar xf backup-archive-file
- Run the following command to restore the performance data and
configuration information files:
/opt/jp1pc/htnm/bin/htmhsrestore -dir extracted-data-directory
- 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.
- 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
- 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.
<For Windows>
- 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.
- Confirm that same name instance exists as when the backup was taken, and if it does not exist, create it.
- Copy the backup archive file to a working folder and extract
it:
tar xf backup-archive-file
- 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
- 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.
- 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
- 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.
Recovering Analyzer detail view
Recovering Analyzer probe
To recover Analyzer probe from a backup archive, see the Hitachi Ops Center Analyzer Installation and Configuration Guide.
Recovering Analyzer viewpoint
- 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.
Recovering Analyzer Virtual Storage Software Agent
- Extract the archive file. For the specific file path, see the Protector GUI.
- 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.
Recovering Analyzer On-demand real time monitoring module (Linux only)
- Extract the archive file. For the specific file path, see the Protector GUI.
- 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.
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)".
- Run the tar command to extract
the backup archive file:
tar xvf backup-archive-file -C destination-file-path
- 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
- Run the jar command to extract the backup archive file:
- 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.
Recovering Common Services
Common-Services-installation-directory/utility/bin/csrestore.sh -file backup-archive-file
For details, see Restoring Common Services.
Recovering Protector
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 |
|
See Starting or stopping the Common Services service. |
| Ops Center Analyzer |
|
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:
|
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
Backing up Common Services
Restoring Common Services
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).
- 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
Configuring key-based authentication to transfer data directly from Analyzer probe server to Analyzer detail view server
- 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:
Configure the Analyzer Probe server
Follow these steps:
- Log on to the Analyzer probe server through an SSH client (like putty) as a root user.
- 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
- Switch to the megha user:
su - megha
- 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
- RSA:
- 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
- RSA:
- (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)
- 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
- When prompted for the password, enter the meghadata user password.
- (If you are using the ECDSA algorithm), do the following:
- Stop the crond service using the command:
service crond stop
- Stop the Analyzer probe server using the command:
/usr/local/megha/bin/megha-jetty.sh stop
- Verify that the services (including crond) are stopped using the commands:
service crond status
/usr/local/megha/bin/megha-jetty.sh status
- 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
- Start the crond service using the command:
service crond start
- Start the Analyzer probe server using the command:
/usr/local/megha/bin/megha-jetty.sh start
- 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
- Stop the crond service using the command:
Configure the Analyzer detail view server
Follow these steps on the Analyzer detail view server:
- Log on to the Analyzer detail view server through an SSH client (like putty) as a root user.
- 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
- /Installation_directory/meghadata/.ssh
directory:
- 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 if the type has been changed to ssh_home_t:
ls -Z -a /Installation_directory/meghadata/.ssh
- /Installation_directory/meghadata/.ssh directory:
Make sure that you switch to the key-based authentication and SFTP protocol in the Analyzer probe UI (select ).
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.
- 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.
Analyzer detail view server is shown in the Common Services.
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.
- 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.
Analyzer probe server is shown in the Common Services.
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.
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.
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.
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 .
Stopping unnecessary product services
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.
After you deploy the OVA and finish the configuration using the setup tool (opsvmsetup).
Resetting the trust relationship with each product
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.)
Configuring the settings for session idle timeout
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.
- 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
- Analyzer
- Analyzer detail view
- Analyzer viewpoint
- Analyzer probe server
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
Applying Linux security updates using yum
Accessing the RPM packages using the Linux OS media
- Mount the Linux OS media
and obtain the RPM packages:
mkdir /media/OSImage mount /dev/cdrom /media/OSImage
- 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
- Specify the repository to
which the yum command will connect.
- For Red Hat Enterprise Linux, register the system by using Red Hat Subscription Management. For details, see https://access.redhat.com/articles/11258.
- For Oracle Linux, the initial settings are set by default (the file repo is already located in the directory /etc/yum.repos.d). For details, see http://yum.oracle.com/getting-started.html.
- If you are using a proxy,
specify the proxy for the yum command:
- Add the following
information to the /etc/yum.conf file:
proxy=http://host-name:port-number proxy_username=user-name proxy_password=password
- Clear the cache for
the yum command.
yum clean all
- Add the following
information to the /etc/yum.conf file:
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
- To replace an individually installed instance of Command Control Interface with an instance of Command Control Interface installed by the Express installer, perform the procedure described in Switching to an instance of Command Control Interface installed by the Express installer.
- To replace an instance of Command Control Interface installed by the Express installer with an individually installed instance of Command Control Interface, perform the procedure described in Switching to an individually installed instance of Command Control Interface.
Switching to an instance of Command Control Interface installed by the Express installer
Switching to an individually installed instance of Command Control Interface
Upgrading Amazon Corretto 21
Upgrading PostgreSQL 15
Troubleshooting
Collecting failure information
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-pathLinux: 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-destinationLinux: REST-API-installation-destination/SupportTools/CollectTool/RestTI.sh -dir omaintenance-information-storage-destination |
Common Services logs
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.
|
|
Message |
The message corresponding to the message ID |
|
Exception |
Information about the exception that occurred |
Changing the properties of logs
Common Services audit log
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 |
|
|
||
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
Collecting the log file for the Analyzer server
Run the hcmds64getlogs command to collect the log file for the Analyzer server.
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.
Collecting the log file for the RAID Agent
Run the jpcras command to collect the log file for the RAID Agent.
- Dump information
- To collect dump information, perform the following procedure:
- Open the Task Manager.
- Choose the Process tab.
- 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:
- Content of Application, System, and Security in the Windows Event Viewer
- Content displayed by selecting
- You must also collect the log files described in Collecting the installation logs for RAID Agent (Windows).
Collecting the installation logs for RAID Agent (Windows)
Collect the following logs and registry information for the RAID Agent installer.
Collecting Analyzer viewpoint log files
/opt/hitachi/analyzer_viewpoint/bin/diagThe 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.
- From the desktop, display the Start window.
- 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.
- Either open an SSH connection to the VM or open the VMware console and press Alt+F2 to reach the console.
- 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.
- In the terminal, enter the command: /opt/rainier/bin/rainier-getlogs -dir [output-directory].
- 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.
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
Overview of the Common Services REST API
Specifying resources
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.
Using a session to perform authentication
The operational flow for running a REST API request is as follows:
- Run the Common Services REST API request to acquire an access token.
- 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
- 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
|
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
|
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
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
|
Attribute |
Type |
Description |
|---|---|---|
|
errorMessage |
string |
Error message |
|
additionalInfo |
string |
Additional information about the error message |
REST API of Common Services
Getting access tokens
Getting an access token
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
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
Getting information about users who obtained an access token
Execution permission
None.
Request line
GET base-URL/auth/v1/providers/builtin/userinfo
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"
Managing external authentication
Performing 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.
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"
Getting a list of Active Directory or LDAP servers
Execution permission
You must be a system administrator or a security administrator.
Request line
GET base-URL/security/v1/external-user-storage
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"
Getting information about a specific Active Directory or LDAP server
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
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"
Getting a list of realms for Kerberos authentication
Execution permission
You must be a system administrator or a security administrator.
Request line
GET base-URL/security/v1/kerberos-realm
Response message
Coding example
curl -v -X GET -s "https://example.com:443/portal/security/v1/kerberos-realm" -H "Authorization:Bearer eyJhbxxx"
Getting information about a specific realm for Kerberos authentication
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
Response message
Coding example
curl -v -X GET -s "https://example.com:443/portal/security/v1/kerberos-realm/4028b8816e4ad3ee016e5d76637c0000" -H "Authorization:Bearer eyJhbxxx"
Getting Kerberos authentication connection information
Execution permission
You must be a system administrator or a security administrator.
Request line
GET base-URL/security/v1/kerberos-connection-settings
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"
Checking the number of users to be acquired from an Active Directory or LDAP server
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"
Managing identity providers
Getting a list of identity providers
Execution permission
You must be a system administrator or a security administrator.
Request line
GET base-URL/idp/v1/external-identity-provider
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"
Getting information about a specific identity provider
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
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"
Managing users
Getting 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
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"
Getting 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
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"
Getting 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
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"
Registering 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.
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"
Adding 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.
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"
Updating 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.
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"
Resetting a user's password
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.
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"
Deleting a user from 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.
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"
Deleting 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
Coding example
curl -v -X DELETE -s "https://example.com:443/portal/security/v1/users/8b39869a-a778-4a08-a2ff-bf967946e836" -H "Authorization:Bearer eyJhbxxx"
Managing the password policy
Getting the password policy
Execution permission
You must be a system administrator or a security administrator.
Request line
GET base-URL/security/v1/password-policy
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"
Updating the password policy
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.
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"
Managing user groups
Getting 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
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"
Getting 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
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"
Getting 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
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"
Getting 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
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"
Getting 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
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"
Registering 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.
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"
Assigning 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.
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"
Updating 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.
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"
Deleting 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.
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"
Deleting 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.
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"
Managing linked products
Getting a list of products linked with Common Services
Execution permission
None.
Request line
GET base-URL/app/v1/application-services
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¶m[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"
Getting 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
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"
Getting 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
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"
Getting 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
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"
Getting 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
Response message
Coding example
curl -v -X GET -s "https://example.com:443/portal/app/v1/application-services/8a44f59a6f785e31016f78651c820000/version" -H "Authorization:Bearer eyJhbxxx"
Managing data centers
Getting a list of data centers
Execution permission
None.
Request line
GET base-URL/app/v1/datacenters
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"
Getting 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
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"
Getting 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
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¶m[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"
Registering 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.
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"
Updating 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.
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"
Registering 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.
Coding example
curl -v -X PUT -s "https://example.com:443/portal/app/v1/datacenters/8a44f59a6f785e31016f7957f7db0005/application-services/8a44f59a6f785e31016f78651c820000" -H "Authorization:Bearer eyJhbxxx"
Deleting 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.
Coding example
curl -v -X DELETE -s "https://example.com:443/portal/app/v1/datacenters/8a44f59a6f785e31016f7957f7db0005/application-services/8a44f59a6f785e31016f78651c820000" -H "Authorization:Bearer eyJhbxxx"
Deleting 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
Request message
Coding example
curl -v -X DELETE -s "https://example.com:443/portal/app/v1/datacenters/8a44f59a6f7d6b59016f7ee8cc210001" -H "Authorization:Bearer eyJhbxxx"
Managing the Common Services system information
Getting the Common Services version information
Execution permission
None.
Request line
GET base-URL/system/v1/version
Response message
Coding example
curl -v -X GET -s "https://example.com:443/portal/system/v1/version" -H "Authorization:Bearer eyJhbxxx"
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.
- Back up the Analyzer probe server.
- Back up the RAID Agent.
- Verify that the ISM server has sufficient resources to install the Analyzer probe.
-
Download the
Analyzer probe v10.5.0 installer ISO.
- Log in to the Support site.
- Click DOWNLOAD PRODUCTS AND UPDATES.
- Scroll down and select Ops Center Installation Media.
- Verify that 10.5.0 is selected, then select Analyzer probe Add-On and click Download.
- On the ISM server machine, install the Analyzer probe server using the installer ISO.
- Using the backup you created, restore the Analyzer probe on the ISM server.
- Restore the RAID Agent.
-
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:
- Changing the IP address of the Analyzer probe server when not monitoring Hitachi Enterprise Storage systems on the host.
- Changing the IP address of the Analyzer probe server when monitoring Hitachi Enterprise Storage systems on the host.
- Changing the host name of the Analyzer probe server when not monitoring Hitachi Enterprise Storage systems on the host.
- Changing the host name of the Analyzer probe server when monitoring Hitachi Enterprise Storage systems on the host.
- Set up SSL communication and user passwords as needed. (The Analyzer probe server backup does not include these settings.)
- 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.
Backing up the RAID Agent (Linux)
You can back up the configuration information files and the performance data of the RAID Agent.
Installing Analyzer probe server (Linux OS)
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 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.
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 .
- Machine: The machine time zone must be the same, and the machine locale must be English.
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.
- 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.
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.
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.
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.
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.
Removing an Ops Center product
To remove an Ops Center product, use the product uninstaller.
Removing Common Services
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
- 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.
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.
Removing Analyzer probe server
Remove Analyzer probe server using the dcaprobe_uninstall.sh command.
Removing Analyzer viewpoint
Use the viewpoint_uninstall.sh command to remove the instance of Analyzer viewpoint.
You must have root privilege.
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
/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:
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:
- Removing Ops Center Administrator when using Docker
- Removing Ops Center Administrator when using Podman
Removing Ops Center Administrator when using Docker
If your installation uses Docker as the container runtime, remove Ops Center Administrator as follows:
Removing Ops Center Administrator when using Podman
If your installation uses Podman as the container runtime, remove Ops Center Administrator as follows:
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.
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:
Removing Ops Center Automator (Linux OS)
You can remove Ops Center Automator in a Linux OS environment as listed in the following procedure.
- Run the following command: Directory-specified-when-installing-Automation-software/ADUninstall/uninstall.sh
- 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)
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.
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
- 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. |
- 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
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.
- 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)
-
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.
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.
Removing the REST API as the root user (in a Linux OS)
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.