When you execute the Scale Out scenario, a scenario for adding a new OpenTP1 node and a scenario for updating the domain configuration are executed.

(a) When the domain configuration management node is used

The following figure shows the operating model for executing Scale Out when the domain configuration management node is used.

Figure 3-34 Operating model for Scale Out (when the domain configuration management node is used)

To execute Scale Out using the domain configuration management node, carry out the following procedure:

1. Execute scenario (a) for adding a new node and create OpenTP1-C.
2. Execute scenario (b) for updating the domain configuration at OpenTP1-N (domain configuration management node) and add OpenTP1-C to the domain configuration.

(b) When the domain configuration management node is not used

The following figure shows the operating model for executing Scale Out when the domain configuration management node is not used.

Figure 3-35 Operating model for Scale Out (when the domain configuration management node is not used)

In this operating model, nodes manage the domain configuration in the system by configuring one another. When a new OpenTP1 node is created, the domain configuration set at other nodes is updated so that those nodes can recognize the new node.

To execute Scale Out without using the domain configuration management node, carry out the following procedure:

1. Execute scenario (a) for adding a new node and create OpenTP1-D.
2. Execute scenario (b) for updating the domain configuration in OpenTP1-A, B, and C, and add OpenTP1-D to the domain configuration.
3. Execute scenario (b) for updating the domain configuration in OpenTP1-D and add other nodes in the system (OpenTP1-A, B, C) to the domain configuration.

When the Scale Out scenario provided by OpenTP1 is executed, OpenTP1 executes a scenario for adding a new OpenTP1 node and then a scenario for updating the domain configuration.

See the following for details about each scenario.

(a) Scenario for adding a new OpenTP1 node

The following figure shows the sequence of the scenario templates executed by the scenario for adding a new OpenTP1 node.

Figure 3-36 Sequence of scenario templates executed by the scenario for adding a new OpenTP1 node

See the following table for an explanation of each scenario template.

Table 3-35 Scenario templates in the scenario for adding a new OpenTP1 node

No.	Scenario template name	Description
1	OpenTP1_MakeTP1Dir#1	Creates an OpenTP1 directory.
2	OpenTP1_SetConfig#1	Sets the OpenTP1 environment.
3	OpenTP1_ChangeNodeID#2	Sets a node ID.
4	OpenTP1_Deploy#2	Registers OpenTP1.
5	OpenTP1_MakeFileSystem#1	Creates OpenTP1 file systems.
6	OpenTP1_Start#2	Starts OpenTP1.
7	OpenTP1_StartUAP#2	Starts a UAP.

#1

Created by the user. For details about the samples provided by OpenTP1, see 3.15.6 Using sample scenario templates.

#2

This scenario template is provided by OpenTP1. For details, see M. Details About Scenario Templates.

(b) Scenario for updating the domain configuration

The prerequisites for updating the domain configuration are as follows:

• Y is specified in the name_domain_file_use operand in the system common definition.
• The node where you update the domain configuration is online.

The following figure shows the sequence of the scenario templates executed by the scenario for updating the domain configuration.

Figure 3-37 Sequence of scenario templates executed by the scenario for updating the domain configuration

See the following table for an explanation of each scenario template.

Table 3-36 Scenario templates in the scenario for updating the domain configuration

No.	Scenario template name	Description
1	OpenTP1_AddNode	Adds a node to the domain definition file.
2	OpenTP1_UpdateDomain	Updates the domain configuration.

Both of these scenario templates are provided by OpenTP1. For details, see M. Details About Scenario Templates.

By executing Scale Out, you can partially automate the procedure for setting the OpenTP1 environment. This subsection describes the procedure for setting the environment in which Scale Out and the disk copy facility of DPM are used. The superuser must perform steps 1 to 8. Perform steps 1 to 5 on the master computer of the OpenTP1 system (disk copy source), step 6 on the computer where DPM is installed, and steps 7 to 9 on the new OpenTP1 node (disk copy destination) to be added.

1. In the /etc/hosts file, register the host name used by the OpenTP1 system.
2. Register the OpenTP1 system administrator.
   For details, see 1.2.1 Cataloging of OpenTP1 administrator.
   
3. Set an OpenTP1 group.
   For details, see 1.2.2 Definition of OpenTP1 group.
   
4. Install the OpenTP1 program product.
   You must create the OpenTP1 program product on the same disk (master disk) that contains the OS.
   
5. Create a file for setting the OpenTP1 environment, that will be used by Scale Out.
   For details, see 3.15.6(3) Customizing a sample scenario template.
   
6. Using the disk copy facility of DPM, restore the contents of the disk backed up from the master computer of the OpenTP1 system to the node of the new OpenTP1.
   As the network type of the disk copy destination, specify fixed IP, not DHCP. For details about how to use DPM, see the manual JP1/ServerConductor/Deployment Manager.
   
7. Set up JP1/AJS2 - Agent.
   For details about how to set up JP1/AJS2 - Agent, see the manual Job Management Partner 1/Automatic Job Management System 2 Setup Guide.
   
8. Allocate a raw device as the OpenTP1 file system.
   To run the OpenTP1 file system by using a character type special file, allocate a raw device on the OpenTP1 file system to automate the initialization of the OpenTP1 file system by Scale Out.
   
9. Execute Scale Out.
   When Scale Out is executed, a scenario for adding a new OpenTP1 node is executed. When this scenario is executed, the following processing is performed automatically:
   1. Creation of the OpenTP1 directory
   2. Creation of the system definition
   3. Registration of OpenTP1 in the OS
   4. Initialization of the OpenTP1 file system
   5. Creation of the OpenTP1 file