Customization placeholders

A customization placeholder is a string in a resource file that, during customization definition, before the resource file is executed, is replaced with a value. The replacement is usually done automatically by the CDP during customization definition, but a placeholder for which a value is not mandatory and for which no value was specified during customization definition must be replaced manually before customization deployment.

Placeholders are set by specifying a value in the corresponding statement in the CDD. For example, the statement DNIvSGRP="dnisecgr" sets the value of the placeholder DNIvSGRP to dnisecgr.

To help you keep track of the settings used by your installation, write the values you use in the margin next to the rightmost column of each of the following tables.

Notes:
  1. In the domain descriptions, the values in square brackets indicate allowable characters, and the values in braces indicate the minimum and maximum number of characters. For example, [A-Z0-9] {1,8} indicates that the value must be between one and eight characters long, and can contain only digits and uppercase letters. A definition {1,} specifies a value which has a minimum length of one no maximum length.
  2. A checkmark in the Mandatory column indicates that a placeholder is mandatory; otherwise, it is optional:
    mandatory
    You must specify a value for the placeholder before issuing the import command.
    optional
    You can elect not to specify a value for the placeholder before issuing the import command. When the resulting customization definition is prepared, the resulting resource files contain the placeholder itself, rather than a replacement value. Before these resource files can be run, a file editor must be used to replace the placeholder with the appropriate value.
  3. The number in the Category column indicates to which of the following categories a placeholder belongs:
    1
    If the customizer changes the value of a placeholder of this type in a CDD and prepares new deployment data, the CDP generates new resource files that:
    • Deletes resources that use the old value
    • Creates resources that use the new value
    The deployment instructions instruct the customizer to run the new resource files to delete the old resources and to create the new ones.
    2
    Changing the value of this placeholder results in changes to the runtime environment for which the CDP is unable to generate deployment vehicles that implement them. If those changes are related to Db2® or IBM MQ resources, they must be implemented manually following the instructions given by the corresponding product. If the changes are related to FTM SWIFT resources, please contact your IBM service representative to receive further instructions on which manual steps need to be taken to reflect the new placeholder values. If the current preparation step generated any deployment vehicles, it is important that those changes are made before any of the generated deployment vehicles are run. After the changes were made, and after the generated deployment vehicles (if any) were run, issue the implement CDP command to indicate that the current CDD conforms to the actual runtime environment.
    3
    If the customizer changes the value of a placeholder of this type in a CDD and prepares new deployment data, the CDP does not generate new resource files. This is because the changes affect only the deployment vehicles, but not the deployed resources. The resources that are currently running are not affected by such changes.
    4
    If the customizer changes the value of a placeholder of this type in a CDD and prepares new deployment data, the CDP generates a description of how to modify the affected subsystem.
Table 1. FTM SWIFT placeholders (general)
Placeholder Description
DNIvINST The name of the instance.
Example:
INST1
Domain:
[A-Za-z0-9] {1,8}
DNIvOU The name of the business organizational unit.
Example:
BANKA
Domain:
[A-Za-z0-9] {1,8}
DNIvSRV The FTM SWIFT server name. This can be the name of a broker server, a WebSphere® application server, or a SAG.
Example:
SERV1
Domain:
[A-Za-z0-9] {1,8}
DNIvSVB The name of the service bundle.
Example:
DNIOU
Domain:
[A-Z0-9]{1,40}
Table 2. FTM SWIFT placeholders
Placeholder Description Scope Category Mandatory
DNIvMBRK The name of the broker to which the BAR files are deployed.
Example:
MQM1BRK
Domain:
[A-Za-z0-9_\./]{1,48}
server 1
DNIvPATH Installation directory of FTM SWIFT.
Example:
/opt/IBM/ftm/swift/v324
Domain:
[A-Za-z0-9_\./] {1,}
instance 2
DNIvSA1 The user ID of first system configuration administrator*
Example:
sa1
Domain:
[A-Za-z0-9#$@] {1,8}
instance 2
DNIvSA2 The user ID of second system configuration administrator*
Example:
sa2
Domain:
[A-Za-z0-9#$@] {1,8}
instance 2
DNIvUA1 The user ID of first security administrator of SYSOU*
Example:
ua1
Domain:
[A-Za-z0-9#$@] {1,8}
instance 2
DNIvUA2 The user ID of second security administrator of SYSOU*
Example:
ua2
Domain:
[A-Za-z0-9#$@] {1,8}
instance 2
* The user IDs of all security and configuration administrators for an FTM SWIFT instance must be unique.
Table 3. IBM MQ placeholders
Placeholder Description Scope Category Mandatory
DNFvLQCLUS The name of the input queue of an SAG cluster, without the queue prefix. The complete name, including the queue prefix, must not exceed 48 characters.
Example:
LQCLUS1
Domain:
[A-Za-z0-9_\./] {1,46}
server 1
DNFvQTHFT Internal queue thread threshold on queue DNF_O_FT used when CIN processes MSIF transfers.
Default value:
0
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNFvQTHFT1 Internal queue thread threshold on queue DNF_O_FT1 used when CIN processes MSIF transfers.
Default value:
0
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNFvQTHFT2 Internal queue thread threshold on queue DNF_O_FT2 used when CIN processes MSIF transfers.
Default value:
0
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNFvQTHFT3 Internal queue thread threshold on queue DNF_O_FT3 used when CIN processes MSIF transfers.
Default value:
0
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNFvQTHIO Internal queue thread threshold on queue DNF_O_FTIO used when CIN processes MSIF transfers.
Default value:
1
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNFvQTHIO1 Internal queue thread threshold on queue DNF_O_FTIO1 used when CIN processes MSIF transfers.
Default value:
1
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNFvQTHIO2 Internal queue thread threshold on queue DNF_O_FTIO2 used when CIN processes MSIF transfers.
Default value:
1
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNFvQTHIO3 Internal queue thread threshold on queue DNF_O_FTIO3 used when CIN processes MSIF transfers.
Default value:
1
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNFvQTHTMH Internal queue thread threshold on queue DNF_O_FTTMH used when CIN processes MSIF transfers.
Default value:
0
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNFvQTHTMH1 Internal queue thread threshold on queue DNF_O_FTTMH1 used when CIN processes MSIF transfers.
Default value:
0
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNFvQTHTMH2 Internal queue thread threshold on queue DNF_O_FTTMH2 used when CIN processes MSIF transfers.
Default value:
0
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNFvQTHTMH3 Internal queue thread threshold on queue DNF_O_FTTMH3 used when CIN processes MSIF transfers.
Default value:
0
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNFvQTHTML Internal queue thread threshold on queue DNF_O_FTTML used when CIN processes MSIF transfers.
Default value:
0
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNFvQTHTML1 Internal queue thread threshold on queue DNF_O_FTTML1 used when CIN processes MSIF transfers.
Default value:
0
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNFvQTHTML2 Internal queue thread threshold on queue DNF_O_FTTML2 used when CIN processes MSIF transfers.
Default value:
0
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNFvQTHTML3 Internal queue thread threshold on queue DNF_O_FTTML3 used when CIN processes MSIF transfers.
Default value:
0
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNFvQTHUMH Internal queue thread threshold on queue DNF_O_FTUMH used when CIN processes MSIF transfers.
Default value:
0
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNFvQTHUMH1 Internal queue thread threshold on queue DNF_O_FTUMH1 used when CIN processes MSIF transfers.
Default value:
0
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNFvQTHUMH2 Internal queue thread threshold on queue DNF_O_FTUMH2 used when CIN processes MSIF transfers.
Default value:
0
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNFvQTHUMH3 Internal queue thread threshold on queue DNF_O_FTUMH3 used when CIN processes MSIF transfers.
Default value:
0
Domain:
[0-9] {1,1}

Change this value only if asked to do so by your IBM service representative.

instance 1
DNIvCLUS The name of the IBM MQ cluster. If you do not have an IBM MQ cluster, specify blank as the value.
Example:
DNIMQCLS
Domain:
[A-Za-z0-9_\./] {1,48}
instance 2
DNIvMQCHL The name of the IBM MQ channel used to connect to the queue manager used by an FTM SWIFT server.
Example:
SYSTEM.DEF.SVRCONN
Domain:
[A-Za-z0-9_\./%]{1,20}
server 4  
DNIvMQHOST The host name of the system on which the queue manager used by an FTM SWIFT server runs.
Example:
host1.yourcompany.com
Domain:
Not checked
server 4  
DNIvMQPORT The port used to connect to the system on which the queue manager used by an FTM SWIFT server runs.
Example:
1414
Domain:
[0-9] {1,5}
server 4  
DNIvMQMN The name of the queue manager used by an FTM SWIFT server.
Example:
MQM1
Domain:
[A-Za-z0-9_\./] {1,48}
server 1
DNIvMQTRANS The transport type to use for connections to the queue manager from an application server running on an FTM SWIFT server.
Domain:
CLIENT | BINDINGS
server 4  
DNIvQPFX The prefix of the input-queue names of the FTM SWIFT services of this instance.
Example:
DNI
Domain:
[A-Za-z0-9_\./] {1,17}
instance 2
DNIvTPFX The prefix of the topic names of the FTM SWIFT services of this instance.
Example:
DNI
Domain:
[A-Za-z0-9_\./] {1,17}
instance 2
Table 4. Security-related placeholders
Placeholder Description Scope Category Mandatory
DNFvAGRP The group used to restrict access to the queues used by a particular SAG Add-On. For example, access to the queue HLQ.SNCCREQUEST.SAG2, from which the SAG Add-On of SAG2 receives operating commands, would be restricted to members of this group. The SAG owner must be a member of this group.
Example:
dnfagrp
Domain:
[A-Za-z0-9#$@] {1,8}
server 1  
DNFvAGRPS The group used to restrict access to the queues shared by all the SAG Add-Ons of all the SAG servers of an instance. For example, access to the queue INST1.DNFSYSOU. DNFSAGOP_RE, into which each SAG Add-On associated with instance INST1 puts its responses to operating commands, would be restricted to members of this group. The owner each of the SAGs associated with the instance must be a member of this group.
Example:
dnfagrps
Domain:
[A-Za-z0-9#$@] {1,8}
server 1  
DNFvCUSR The group used to restrict access to the interface queues into which FIN messages that are to be processed are placed.
Example:
dnfcusr
Domain:
[A-Za-z0-9#$@]{1,8}
server 1  
DNFvMGRP The group used to restrict access to the queues used by the MQHA of a particular SAG, or the SAGs that form a local queue cluster. For example, access to the queue HLQ.LQCLUS1, from which the SAGs of the local queue cluster named LQCLUS1 retrieve messages to be passed to the SIPN, would be restricted to members of this group. The SAG owner must be a member of this group.
Example:
dnfmgrp
Domain:
[A-Za-z0-9#$@] {1,8}
server 1  
DNFvMGRPS The group used to restrict access to the queues shared by all the MQHAs of all the SAG servers of this instance. For example, access to the queue INST1.DNF_FSM_SLS.LT3, into which all SAGs place inbound OSN messages destined for LT3, would be restricted to members of this group. The owner of each of the SAGs associated with the instance must be a member of this group.
Example:
dnfmgrps
Domain:
[A-Za-z0-9#$@] {1,8}
server 1  
DNIvOGRP The group used to restrict access to interface queues that are defined in each OU.
Example:
dniogrp
Domain:
[a-z0-9$@] {1,8}
ou 1  
DNIvRGRP The group used to restrict write access to reference data database tables and views on the runtime system.
Example:
dnirefgr
Domain:
[a-z0-9#$@] {1,8}
instance 1
DNIvSGRP The group used to restrict access to input queues and database tables on the runtime system.
Example:
dnisecgr
Domain:
[a-z0-9#$@] {1,8}
instance 1  
DNIvUGRP The group used to restrict access on the application server to the database tables for service bundles DNFRMA, DNFRMR, DNPAO and DNQER.
Example:
dniugwas
Domain:
[a-z0-9#$@] {1,8}
instance 1  
DNIvDAGRP The user group providing access permissions required by data integrity administrators.
Example:
dnidagrp
Domain:
[a-z0-9#$@] {1,8}
instance 1  
DNIvDBGRP The user group providing access permissions required by data integrity operators.
Example:
dnidbgrp
Domain:
[a-z0-9#$@] {1,8}
instance 1  
DNIvDCGRP The user group providing access permissions required by data integrity validators.
Example:
dnidcgrp
Domain:
[a-z0-9#$@] {1,8}
instance 1  
DNIvDDGRP The user group providing access permissions required by data integrity disposers.
Example:
dniddgrp
Domain:
[a-z0-9#$@] {1,8}
instance 1  
DNIvYGRP The group used to restrict access to interface queues that are defined in SYSOU and DNFSYSOU.
Example:
dnisysou
Domain:
[a-z0-9#$@] {1,8}
instance 1  
DNIvWGRP The group used to restrict access to the web application response queue of the application servers.
Example:
dniwgrp
Domain:
[A-Za-z0-9#$@] {1,8}
server 1  
Table 5. Db2 placeholders
Placeholder Description Scope Category Mandatory
DNFvCOLLID The collection ID of the SIPN FIN services.
Example:
INST1CID
Domain:
[A-Z0-9_] {1,18}
instance 2  
DNFvFCA Name of table space for FIN Copy messages.
Example:
DNFFCA01
Domain:
[A-Za-z0-9] {1,8}
ou 2
DNFvMWF Name of table space used by the SIPN FIN service to store additional data related to FIN messages in the message warehouse.
Example:
DNFMWF01
Domain:
[A-Z0-9] {1,8}
ou 2  
DNFvMWM Name of table space used by the MSIF services to store additional data related to InterAct messages in the Message Warehouse.
Example:
DNFMWM01
Domain:
[A-Z0-9] {1,8}
ou 2  
DNFvMWOF Name of table space used by the MSIF services to store additional data related to FileAct file transfers in the message warehouse.
Example:
DNFMWO01
Domain:
[A-Z0-9] {1,8}
ou 2  
DNFvMWX Name of table space used by the MM services to store additional data related to Exceptions and Investigations messages in the message warehouse.
Example:
DNFMWX01
Domain:
[A-Za-z0-9] {1,8}
ou 1  
DNIvAUM The name of the table space* for the message-audit table.
Example:
DNIAUM
Domain:
[A-Za-z0-9] {1,8}
ou 2  
DNIvAUU The name of the table space* for the user-audit table.
Example:
DNIAUU
Domain:
[A-Za-z0-9] {1,8}
ou 2  
DNIvBP4K Name of default buffer pool for table spaces with a 4 KB page size.
Example:
FTMSWIFTBP4K
Domain:
[A-Za-z0-9] {1,30}
instance 2
DNIvBP16K Name of default buffer pool for table spaces with a 16 KB page size.
Example:
FTMSWIFTBP16K
Domain:
[A-Za-z0-9] {1,30}
instance 2
DNIvBP32K Name of default buffer pool for table spaces with a 32 KB page size.
Example:
FTMSWIFTBP32K
Domain:
[A-Za-z0-9] {1,30}
instance 2
DNIvDB01 The name of the FTM SWIFT runtime database.
Example:
DNIDBRUN
Domain:
[A-Za-z0-9] {1,8}
instance 2  
DNIvDBHOST The host name of the server on which the FTM SWIFT runtime database for the current instance is located.
Example:
host1.yourcompany.com
Domain:
Not checked
instance 2
DNIvDBPORT The port number used to connect to the FTM SWIFT runtime database for the current instance.
Example:
58888
Domain:
[0-9] {1,5}
instance 2
DNIvDSN The data source name of the FTM SWIFT runtime database. This is the same as the name of the database, which was specified for the placeholder DNIvDB01.
Example:
DNIDBRUN
Domain:
[A-Za-z0-9_] {1,16}
instance 2
DNIvMWH The name of the table space* for the Message Warehouse table.
Example:
DNIMWH01
Domain:
[A-Za-z0-9] {1,8}
ou 2  
DNIvRDSN The ODBC data source name of the FTM SWIFT runtime database that contains the reference data tables:
  • If the current instance has its own reference data tables, the values of its DNIvRDSN and DNIvDSN placeholders are identical.
  • If the current instance uses the reference data of another instance, set the value of DNIvRDSN for the current instance to the value of DNIvDSN for that other instance.
Example:
dsn2
Domain:
[A-Za-z0-9_] {1,16}
instance 4
DNIvRDBHOST The host name of the server on which the FTM SWIFT runtime database that contains the reference data tables is located:
  • If the current instance has its own reference data tables, the values of its DNIvRDBHOST and DNIvDBHOST placeholders are identical.
  • If the current instance uses the reference data of another instance, set the value of DNIvRDBHOST for the current instance to the value of DNIvDBHOST for that other instance.
Example:
host1.yourcompany.com
Domain:
Not checked
instance 4
DNIvRDBPORT The port number used to connect to the FTM SWIFT runtime database that contains the reference data tables:
  • If the current instance has its own reference data tables, the values of its DNIvRDBPORT and DNIvDBPORT placeholders are identical.
  • If the current instance uses the reference data of another instance, set the value of DNIvRDBPORT for the current instance to the value of DNIvDBPORT for that other instance.
Example:
58889
Domain:
[0-9] {1,5}
instance 4
DNIvRSN The schema name of the FTM SWIFT runtime database that contains the reference data tables:
  • If the current instance has its own reference data tables, the values of its DNIvRSN and DNIvSN placeholders are identical.
  • If the current instance uses the reference data of another instance, set the value of DNIvRSN for the current instance to the value of DNIvSN for that other instance.
Example:
udb2adm2
Domain:
[A-Za-z0-9] {1,8}
instance 4
DNIvSN The schema name of the tables in the FTM SWIFT runtime database for the current instance.
Example:
DNI
Domain:
[A-Z0-9] {1,8}
instance 2
* Table space names must be unique within a single database. Keep this in mind when creating a new table space.
Table 6. WebSphere Application Server placeholders
Placeholder Description Scope Category Mandatory
DNFvRMACONTROOT The context root of the RMA enterprise application. This can be any string of URL-safe characters, preceded and followed by a forward slash.
Default:
/rma/
instance 1  
DNFvWCLUSRMA The name of the application server cluster to which the FTM SWIFT RMA J2EE enterprise application is to be deployed. If this placeholder is not specified, the placeholders DNFvWSRVRMA and DNFvWNODERMA must be specified.
Example:
ftmswift_cluster
instance 1  
DNFvWSRVRMA The name of the application server to which the FTM SWIFT RMA J2EE enterprise application is to be deployed. If this placeholder is not specified, the placeholder DNFvWCLUSRMA must be specified.
Example:
ftmswift_server
instance 1  
DNFvWNODERMA The name of the application server node to which the FTM SWIFT RMA J2EE enterprise application is to be deployed. If DNFvWSRVRMA is specified, this placeholder must also be specified.
Example:
node1
instance 1  
DNIvLOGINCASE This placeholder determines if the user name entered during login to one of the enterprise applications of FTM SWIFT is translated. It can be translated to uppercase or lowercase. It is not translated if Mixed or an empty string is specified.
Default:
empty string
Domain:
(UPPER|lower|Mixed)
instance 4  
DNIvLOGOUTURL The URL to be invoked when logging out from one of the enterprise applications of FTM SWIFT. Leave this value empty to use the built-in logout logic of WebSphere Application Server. If you are using an authentication proxy with single sign-off capability, set the value to the single sign-off URL of the authentication proxy.
Default:
empty string
instance 4  
DNIvWCLUS The name of the cluster within the application server cell. Specify this value to deploy the resources contained in service bundle DNIWAS in the scope of this cluster. If you do not provide a value, the resources are deployed with scope node or server as specified using DNIvWSRV and DNIvWNODE.
Example:
ftmswift_cluster
server 1  
DNIvWSRV The name of the server within the application server cell. Specify this value to deploy the resources contained in service bundle DNIWAS in the scope of this server. If you do not provide a value, the resources are deployed with scope cluster or node as specified using DNIvWCLUS and DNIvWNODE.
Example:
ftmswift_server
server 1  
DNIvWNODE The name of the node within the application server cell. Specify this value to deploy the resources contained in service bundle DNIWAS in the scope of this node. If you do not provide a value, the resources are deployed with scope cluster as specified using DNIvWCLUS.
Example:
node1
server 1  
DNIvWSRVHOME The name of the application server to which the FTM SWIFT WebHome enterprise application is to be deployed. If this placeholder is not specified, the placeholder DNIvWCLUSHOME must be specified.
Example:
ftmswift_server
instance 1  
DNIvWCLUSHOME The name of the application server cluster to which the FTM SWIFT WebHome enterprise application is to be deployed. If this placeholder is not specified, the placeholders DNIvWSRVHOME and DNIvWNODEHOME must both be specified.
Example:
ftmswift_cluster
instance 1  
DNIvWNODEHOME The name of the application server node to which the FTM SWIFT WebHome enterprise application is to be deployed. If the placeholder DNIvWSRVHOME is specified, this placeholder must also be specified.
Example:
node1
instance 1  
DNQvWCLUSMER The name of the application server cluster to which the FTM SWIFT MER J2EE enterprise application is to be deployed. If this placeholder is not specified, the placeholders DNQvWSRVMER and DNQvWNODEMER must be specified.
Example:
ftmswift_cluster
instance 1  
DNQvWSRVMER The name of the application server to which the FTM SWIFT MER J2EE enterprise application is to be deployed. If this placeholder is not specified, the placeholder DNQvWCLUSMER must be specified.
Example:
ftmswift_server
instance 1  
DNQvWNODEMER The name of the application server node to which the FTM SWIFT MER J2EE enterprise application is to be deployed. If the placeholder DNQvWSRVMER is specified, this placeholder must also be specified.
Example:
node1
instance 1  
DNPvAOCONTROOT The context root of the AO enterprise application. This can be any string of URL-safe characters, preceded and followed by a forward slash.
Default:
/ao/
instance 1  
DNPvWCLUSAO The name of the application server cluster to which the FTM SWIFT AO enterprise application is to be deployed. If this placeholder is not specified, the placeholders DNPvWSRVAO and DNPvWNODEAO must be specified.
Example:
ftmswift_cluster
instance 1  
DNPvWSRVAO The name of the application server to which the FTM SWIFT AO enterprise application is to be deployed. If this placeholder is not specified, the placeholder DNPvWCLUSAO must be specified.
Example:
ftmswift_server
instance 1  
DNPvWNODEAO The name of the application server node to which the FTM SWIFT AO enterprise application is to be deployed. If the placeholder DNPvWSRVAO is specified, this placeholder must also be specified.
Example:
node1
instance 1