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.
- 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.
|
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.
|
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.
(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.
|
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
|
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.