12.2.1 Preparations for recovery from a failure in a JP1/AJS3 system that connects to an external database

This subsection describes the preparations for recovery from a failure in a JP1/AJS3 system that connects to an external database, and provides cautionary notes on recovery. The required preparation tasks are as follows:

Create a backup of a JP1/AJS3 system set up to use the external database
Check the environment information of the manager host

Organization of this subsection

(1) Creating a backup of a JP1/AJS3 system set up to use an external database
(2) Checking the environment information of the manager host
(3) Cautionary note

(1) Creating a backup of a JP1/AJS3 system set up to use an external database

After you have completed setting up a JP1/AJS3 system to use an external database, you must create a backup of the JP1/AJS3 system by using snapshots or other methods. When you create a backup, make sure that the JP1/AJS3 service is not running.

For details about setting up JP1/AJS3, see 24. Performing setup for using an external database in a cloud environment in the JP1/Automatic Job Management System 3 Configuration Guide.

To Page Top

(2) Checking the environment information of the manager host

If a failure occurs on a manager host, to perform job processing on the manager host again, you must restore the same operating environment that was used by the manager host before the failure occurred. When you restore the operating environment, if the settings of the manager host have been changed after the backup of the JP1/AJS3 system was created, you must also change the settings accordingly. The following table shows the settings that are required to restore the same operating environment.

Table 12‒3: Settings required to restore the same operating environment
No.	Type of information	Item	Required settings
1	System settings	Host name	Host name of the manager host
2		IP address	IP address of the manager host
3		Language environment	Language environment of the manager host
4		Port number	Set the port number in the `services` file.
5		Firewall settings	Set up a firewall for the port.
6	General	Trace log file size	Set the sizes of the following trace log files: JP1/AJS3 trace log file Trace log file for the JP1/AJS3 Check Manager service or the JP1/AJS3 Check Agent service
7		Environment setting parameters	Set the environment setting parameters for physical hosts.
8		Shell	Shell customization
9		AJS administrator	Designating the AJS administrator
10		JP1/AJS3 connection source restriction	The following settings files: connection permission configuration file manager connection permission configuration file `permitted_host_manager.conf` agent connection permission configuration file `permitted_host_agent.conf`
11		Execution agent information^#	Information about the execution agents and information about addition, deletion, and modification of execution agent groups
12	Scheduler	Adding or deleting a scheduler service	The names of the following directories that were specified when they were added: The name of the database directory Temporary directory name Job information directory name Job information directory name
13		Adding or deleting a scheduler service	Use the following command to obtain the environment setting parameter: jbsgetcnf -c JP1AJSMANAGER -n `scheduler-service-name`
14		Local date and time for the JP1/AJS3 scheduler service	Use the `ajslocaldate` command to change the local date and time for the JP1/AJS3 scheduler service.
15	Events and actions	Destination host for the JP1 event-sending job	Set up communication when the JP1 event-sending job is used to send JP1 events to another host.
16	Events and actions	Linkage with mail systems	Set up the mail system linkage function.
17	Definition pre-check	Definition pre-check function	Either set up or remove the setup of the definition pre-check function.
18	Prerequisite products, related products, and linkage products	Transfer destination host for the JP1 event service	Specify the settings when you use the JP1 event reception monitoring job to monitor JP1 events transferred from other hosts.
19	System management	Process definition	Settings in the following startup process definition files: `jp1ajs_dbmd.conf` `jp1ajs_hstd.conf` `jp1ajs_agtd.conf` `jp1ajs_schd.conf` `jp1ajs_spmd.conf`
20		Process definition	Settings in the following extended startup process definition files: `jp1ajs_dbmd_0700.conf` `jp1ajs_hstd_0700.conf` `jp1ajs_agtd_0700.conf` `jp1ajs_schd_0700.conf` `jp1ajs_service_0700.conf`
21		Process startup settings	Settings in the JP1/AJS3 environment definition file (`jp1ajs_env.conf`)
22	Operation profile	Unit-attribute profile	Settings in the unit-attribute profile
23	Operation profile	Execution agent profile	Settings in the execution agent profile
24	JP1/AJS3 - View settings	Customization of windows and dialog boxes	Common user profile (under `/etc/opt/jp1ajs2/conf/profiles`)
25			Customization of the customization file (`jajsDisableMenu`) that disables the menus of JP1/AJS3 - View windows displayed in JP1/AJS3 - Manager
26			Customization of the executable-command settings file (`jajsExecutableCommand`)
27			Customization of the View customization settings file (`jajsCustomizeView`)
28	User assets	ODBC file data source	ODBC file data source specified during setup of the scheduler service for the external database
29		User application	User applications executed as jobs
30		Data and files required by user applications	The environment variable file, standard input file, file to transfer, end judgment file, and other files
31		Execution environment for user applications	OS user name, user mapping settings in JP1/Base, and other settings

#: If the agent management database is restored with insufficient settings, this information is required to restore the same operating environment that existed before a failure occurred. After you have restored the agent management database, you must complete the necessary settings based on this information.

To Page Top

(3) Cautionary note

The following types of information cannot be taken over to the restored environment. However, if the failed environment can be referenced from the restored environment, the relevant log files can be referenced.

Log files cannot be taken over to the restored environment. If log files are necessary, you must back them up before a failure occurs.
JP1 events cannot be taken over to the restored environment. Therefore, even if you use the JP1 event reception monitoring job, you cannot search for events that were generated before the failure occurred.

To Page Top