2.2.7 Backing up other information

You must also back up other information required to run JP1.

The following table lists the tasks required to back up the information necessary for running JP1.

Table 2‒12: Tasks for backing up the information necessary for running JP1
Task	Windows	UNIX
Setting up a service account	Y	N/A
Backing up login scripts	N/A	Y
Backing up the adjustment values of kernel parameters	N/A	Y
Backing up the tool that collects troubleshooting data	Y	Y
Backing up the cluster-capable tools (only if required by the cluster system)	Y	Y
Backing up the user-created tools for linking with a mail system	N/A	Y
Backing up the files used by HTTP connection jobs	Y	Y^#
Backing up the file used by service linkage jobs and service linkage monitoring jobs	Y	Y
Backing up the aggregation results of the number of job executions	Y	Y
Backing up the aggregation results of the operating status of execution agent	Y	Y

Legend:

Y: Required

N/A: Not applicable

#

This task is required for Linux only.

The procedure for backing up the information required to run JP1 is different for Windows and UNIX. The following subsections describe these procedures.

Note that only the procedures for major items are described. Other items you will need to back up include the OS, network, and cluster software settings. For details, see the documentation for the OS and the cluster software.

Organization of this subsection

(1) In Windows

(a) Setting up a service account

If you have switched a JP1/AJS3 service to a user account, record this change.

(b) Backing up the tool that collects troubleshooting data (_04.bat)

If you collect data by using the data collection tool (_04.bat) you customized, back up the tool after customization.

(c) Backing up the cluster-capable tools (only if required by the cluster system)

To control JP1 from cluster software, back up the cluster-capable tools created for a logical host. This procedure is unnecessary for cluster software that does not need cluster-capable tools.

The following table lists the file you need to back up.

Table 2‒13: File to be backed up
File name	Description
`any-file-name`	Cluster-capable tool

(d) Backing up the files used by HTTP connection jobs

Back up the files used by HTTP connection jobs.

The following table describes the files to be backed up.

Table 2‒14: Files that are used by HTTP connection jobs and are to be backed up
File name	Description
Connection configuration file	File used to set information about HTTP connections
Transmission information file^#	File used to store information about requests sent to APIs
Transmission information file (URL parameter)^#	File used to store the URL parameter for accessing information about requests sent to APIs
Transmission information file (message body)^#	File used to store the message body for accessing information about requests sent to APIs

#

Of the transmission information file, transmission information file (URL parameter), and transmission information file (message body), which files are to be used depends on whether extended mode is used in JP1/AJS3 12-50 or later. Back up these files according to your needs.

For details about extended mode, see 2.4.12 Linking with a business system on the web (example of defining a jobnet that uses HTTP connection jobs) in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

(e) Backing up the file used by service linkage jobs and service linkage monitoring jobs

Back up the file used by service linkage jobs and service linkage monitoring jobs.

The following table describes the file to be backed up.

Table 2‒15: File that is used by service linkage jobs and service linkage monitoring jobs and is to be backed up
File name	Description
Connection configuration file^#	File for setting the information about connection to the JP1/AJS3 for Cloud Service Applications server

#: For details about the file, see JP1/Automatic Job Management System 3 for Cloud Service Applications.

(f) Backing up the aggregation results of the number of job executions

If automatic aggregation of the number of job executions is enabled in the management portal execution environment, back up the aggregation results of the number of job executions. For details about aggregation of the number of job executions in the management portal execution environment, see 4.6.3 Considering the Management Portal execution environment in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

The following table shows the folders to be backed up.

Table 2‒16: Folders that store the aggregation results of the number of job executions
Folder	Description
For a physical host `Mgr_Data_Path`^#\sys\jobagg For a logical host `shared_disk_name`\jp1ajs2\sys\jobagg	Aggregation results of the number of job executions

#

Mgr_Data_Path differs depending on the JP1/AJS3 installation folder.

If the installation folder is the default installation folder or is in a folder protected by the system

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2

A folder protected by the system is a folder under any of the following:

system-drive\Windows
system-drive\Program Files
system-drive\Program Files (x86)

The default value for %ALLUSERSPROFILE% is system-drive\ProgramData.

If the installation folder is other than the above

JP1/AJS3-Manager-installation-folder

(g) Backing up the aggregation results of the operating status of execution agent

If automatic aggregation of the operating status of execution agent is enabled in the management portal execution environment, back up the aggregation results of the operating status of execution agent. For details about aggregation of the operating status of execution agent in the management portal execution environment, see 4.6.3 Considering the Management Portal execution environment in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

The following table shows the folders to be backed up.

Table 2‒17: Folders that store the aggregation results of the operating status of execution agent
Folder	Description
For a physical host `Mgr_Data_Path`^#\sys\agtagg For a logical host `shared_folder_name`\jp1ajs2\sys\agtagg	Aggregation results of the operating status of execution agent

#

Mgr_Data_Path differs depending on the JP1/AJS3 installation folder.

If the installation folder is the default installation folder or is in a folder protected by the system

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2

A folder protected by the system is a folder under any of the following:

system-drive\Windows
system-drive\Program Files
system-drive\Program Files (x86)

The default value for %ALLUSERSPROFILE% is system-drive\ProgramData.

If the installation folder is other than the above

JP1/AJS3-Manager-installation-folder

When you back up the aggregation results of execution agent performance data, back up the execution agent information at the same time. For details about backing up the execution agent information, see 2.2.3(2) Backing up the execution agent information. The backed-up aggregation results cannot be used if there are inconsistencies between the aggregation results execution agent performance data and the execution agent information.

To Page Top

(2) In UNIX

(a) Backing up login scripts

When you have changed the user environment to a JP1 environment, you must also back up the login scripts.

(b) Backing up the adjustment values of kernel parameters

Record the values of kernel parameters provided for JP1.

(c) Backing up the tool that collects troubleshooting data (_04)

If you collect data by using the data collection tool (_04) you customized, back up the tool after customization.

(d) Backing up the cluster-capable tools (only if required by the cluster system)

To control JP1 from cluster software, back up the cluster-capable tools created for a logical host. The following table lists the tool you need to back up.

Table 2‒18: Cluster-capable tool to be backed up
File name	Description
`any-file-name`	Cluster-capable tools

(e) Backing up the user-created tools for linking with a mail system

Back up user-created tools for linkage with a mail system, if any.

(f) Backing up the files used by HTTP connection jobs

Back up the files used by HTTP connection jobs.

The following table describes the files to be backed up

Table 2‒19: Files that are used by HTTP connection jobs and are to be backed up
File name	Description
Connection configuration file	File used to set information about HTTP connections
Transmission information file^#	File used to store information about requests sent to APIs
Transmission information file (URL parameter)^#	File used to store the URL parameter for accessing information about requests sent to APIs
Transmission information file (message body)^#	File used to store the message body for accessing information about requests sent to APIs

#

(g) Backing up the file used by service linkage jobs and service linkage monitoring jobs

Back up the file used by service linkage jobs and service linkage monitoring jobs.

The following table describes the file to be backed up.

Table 2‒20: File that is used by service linkage jobs and service linkage monitoring jobs and is to be backed up
File name	Description
Connection configuration file^#	File for setting the information about connection to the JP1/AJS3 for Cloud Service Applications server

#: For details about the file, see JP1/Automatic Job Management System 3 for Cloud Service Applications.

(h) Backing up the aggregation results of the number of job executions

The following table shows the directories to be backed up.

Table 2‒21: Directories that store the aggregation results of the number of job executions
Directory	Description
For a physical host /var/opt/jp1ajs2/sys/jobagg For a logical host `shared_disk_name`/jp1ajs2/sys/jobagg	Aggregation results of the number of job executions

(i) Backing up the aggregation results of the operating status of execution agent

The following table shows the directories to be backed up.

Table 2‒22: Directories that store the aggregation results of the operating status of execution agent
Directory	Description
For a physical host /var/opt/jp1ajs2/sys/agtagg For a logical host `shared_directory_name`/jp1ajs2/sys/agtagg	Aggregation results of the operating status of execution agent

To Page Top