2.2.6 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‒11: 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^#

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
(2) In UNIX

(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‒12: 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‒13: 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

#: Back up the transmission information file as needed.

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‒14: 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‒15: 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

#: Back up the transmission information file as needed.

To Page Top