Deployment instructions

The deployment instructions generated by the CDP provide information needed by the administrators who deploy the resources for an instance. Each set of deployment instructions applies to one instance, and contains a separate section for each server. Within the section for a server, there is a separate subsection for each resource class. An excerpt from a typical set of deployment instructions is shown in Figure 1.

Figure 1. Deployment instructions excerpt

       FTM SWIFT Deployment Instructions
       Generated: 2016-07-21 11:09:48
 1 →   *****************************  INST1  ******************************
 2 →   Instance: INST1
       Deployment data directory:
 3 →     '/var/ftmswift_v324/cus/depdata/INST1/2016-07-21-11-09-48/'
       Deployment data sets:
 4 →     'FTMDEP.FTMSW324.INST1.J2021109.*'
 5 →   <<<<<<<<<<<<<<<<<<<<<<<<<<<<   SRV1  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
 6 →   Server: SRV1
       Deployment vehicle directory:
 7 →     '/var/ftmswift_v324/cus/depdata/INST1/2016-07-21-11-09-48/SRV1/'
       Deployment vehicle data set:
 8 →     'FTMDEP.FTMSW324.INST1.J2021109.SRV1'
     
 9 →   :::::::::  Resource Creation, Modification, and Migration  ::::::::::
     
10 →   ==========================   MQ   ==========================
11 →   Resource class: MQ (com.ibm.dni.MQ)
12 →   Resource file directory:
         '/var/ftmswift_v324/cus/depdata/INST1/2016-07-21-11-09-48/SRV1/
       com.ibm.dni.MQ/'
       ----------------------------------------------------------------
13 →   Vehicle #1 IBM MQ statements only:
         FTMDEP.FTMSW324.INST1.J2021109.SRV1(MQ000000)
       Vehicle #2 Job to process IBM MQ statements:
         FTMDEP.FTMSW324.INST1.J2021109.SRV1(MQ000001)
     
14 →     Role: IBM MQ administrator
         
15 →     Deployment instructions:
         
         The deployment vehicles listed above contain statements that
         manipulate IBM MQ resources as required by FTM SWIFT:
        ⋮

1

This is a separator line that indicates the instance to which the deployment instructions apply.

2

This line repeats the name of the instance.

3

The deployment data directory is the directory in which the resource files for the instance are stored. It contains one subdirectory for each server in the instance.

4

The deployment data sets are the partitioned data sets (PDSs) in which the deployment vehicles are stored. Each deployment data set has a name of the form

hlq.DNIvINST.date_code.server

where:

hlq

The high-level qualifier as defined in the customization initialization file (DNIvINST.ini).

DNIvINST

The name of the instance.

date_code

The date in the form ydddhhmm, where:

y: A letter indicating the year (T=2019, U=2020, …, Z=2025, …).
ddd: The day of the year (for example, 365 = 31 December in a non-leap year).
hh: The hour of the day.
mm: The minute of the hour.

server

The name of the server.

Each deployment vehicle is stored in a separate PDS member. The name of each member is eight characters long, and composed of the name of the resource class followed by a serial number, for example, DB000000, ESM00000, or DBGNT000.

5

This is a separator line that indicates the server to which the following portion of the deployment instructions apply.

6

This line repeats the name of the server.

7

This line indicates the subdirectory of the deployment data directory in which the deployment vehicles for the server are stored.

8

The deployment vehicle data set is the PDS in which the deployment vehicles for this server are stored. Each vehicle is stored in a separate PDS member.

9

This is a separator line that marks the beginning of the section containing instructions that result in the creation, modification, or migration of resources for this server. Instructions that result in the removal of resources, if any, are located in a previous section. For each server, removal of resources must take place before creation, modification, or migration of resources.

10

This is a separator line that indicates the resource class to which the following portion of the deployment instructions apply.

11

This line repeats the name of the resource class. The value in parentheses is the full name of the resource class, including a qualifier that uniquely identifies the service bundle set to which the resource class belongs.

12

This line indicates the subdirectory of the deployment vehicle directory in which the resource files for this resource class are stored. These files are required only if the administrator who deploys the corresponding resources elects not to use a deployment vehicle.

Note: This directory is also listed when resource files or deployment vehicles are not needed and so are not created; for example, when the deployment instructions require only that message flows be deleted. In such cases, this directory can be ignored.

13

A deployment vehicle is a job or other executable file that is used to deploy resources. Each vehicle corresponds to a particular resource file. A deployment vehicle contains the same resource definition statements as its corresponding resource file, but might contain additional statements as well, such as job control statements. Sometimes, more than one vehicle might be provided for a single resource file, for example:

One that contains only the statements needed to deploy the resources
One that contains a job that, when run, deploys the resources

An administrator can use any of the provided deployment vehicles to deploy the corresponding resources. If an administrator elects to use a deployment vehicle, the resource files for that class can be ignored.

Alternatively, an administrator can elect to use the statements stored in the corresponding resource files (these are identical to the contents of Vehicle #1). The resource file is located in the indicated resource file directory.

14

This line indicates which administrator is to deploy the resources.

15

This section contains the instructions that apply to this vehicle or resource file.

Each administrator carries out the instructions for all the resource classes for which that administrator is responsible. Table 1 shows which administrator is responsible for each resource class. The access rights required by each administrator are described in Table 1.

To deploy resources, each administrator must carry out the following procedure:

Log on to the appropriate runtime system. For example:
- The Db2® administrator logs on to the system on which the FTM SWIFT database is located
- The message broker application developer logs on to the Windows workstation that hosts the message broker toolkit
Transfer the appropriate deployment vehicles or resource files to the runtime system.
Modify the contents of the deployment vehicles or resource files as required. For example, adapt job cards to local system conventions, or replace, with appropriate values, any placeholders that were not replaced automatically during the prepare step.
Carry out the steps specified in the deployment instructions.