Creating file-transfer directories

The MSIF transfer service uses the following directories when transferring files:
Name Location Description Option Where option is specified
data directory host Directory that contains the work directory and the transfer directories. This corresponds to the SAG directory on an SAG or RFH workstation. EfaDataDirectory Attribute of the CO DnfEfaParameters (see Setting global parameters and mapping message partners)
work directory host Subdirectory of the data directory that contains temporary files. EfaWorkDirectory
SAG directory SAG or RFH workstation Directory that contains the SAG subdirectory. This corresponds to the data directory on the host. When using MQHA to transfer files to and from the SAG, this corresponds to the MQHA file directory.
Note: If the operating system of the SAG workstation is Microsoft Windows, use Universal Naming Convention (UNC) notation; do not specify a drive letter.
 SagDirectory Attribute of a CO of type DnfEfaSagCommOptionSet (see SAG communication options: SagCommOptions)
SAG subdirectory SAG or RFH workstation Subdirectory of the SAG directory that contains files to be transferred. This corresponds to a transfer directory on the host. SagSubDirectory
transfer directory host Subdirectory of the data directory that contains files to be transferred. This corresponds to an SAG subdirectory on the SAG or RFH workstation. TransferDirectory
target directory host Directory in which a received file is to be stored. TargetDirectory Attribute of a CO of type DnfEfaFileReceiveOptionSet (see File receive options: FileReceiveOptions)
All these directories must be created before they can be used. For example:
Example 1: One SAG or RFH workstation
In this example:
  • One SAG or RFH workstation is used for all file transfers.
  • One target directory is used, and it is a subdirectory of the data directory.
The following directory structure could be used:
On the host:
efadata    [corresponds to efasag on the SAG or RFH]
  efawork  [does not correspond to any directory on the SAG or RFH]
  transfer [corresponds to transfer on the SAG or RFH]
target     [does not correspond to any directory on the SAG or RFH]
On the SAG or RFH workstation:
efasag     [corresponds to efadata on the host]
  transfer [corresponds to transfer on the host]
To create these directory structures:
  • When using MQHA to transfer files to and from the SAG:
    • Issue the following commands for the host: 
      mkdir -p /efadata/efawork
mkdir /efadata/transfer
mkdir /efadata/target
chown -R <broker uid>:<group> /efadata 
chmod -R u=rwx,g=rwx,o= /efadata
    • Issue the following commands for the SAG or RFH: 
      mkdir -p /efasag/transfer
chown -R swnet:swnetg /efasag
chmod -R u=rwx,g=rwx,o= /efasag
  • When using NFS to share files between the host and the SAG or RFH:
    • Issue the following commands for the host: 
      mkdir -p /efadata/efawork
mkdir /efadata/transfer
mkdir /efadata/target
chown -R <broker uid>:<group> /efadata 
chmod -R u=rwx,g=rwx,o= /efadata
    • Export the following directory for the host: 
      /efadata/transfer
    • Issue the following commands for the SAG or RFH: 
      mkdir /efasag
chown -R swnet:swnetg /efasag
chmod -R u=rwx,g=rwx /efasag
mount host:efadata/transfer efasag/transfer
Example 2: Two SAGs and no SAG MP option set switching
In this example:
  • Two SAGs (SAG1 and SAG2) are used for all file transfers.
  • Each SAG subdirectory corresponds a different transfer directory.
  • There is no SAG MP option-set group configured that allows a scenario to switch to another option set in the group.
  • Two target directories are used, and they are both on the same level as the data directory.
The following directory structure can be used:
On the host:
efadata      [corresponds to efasag on the SAG]
  efawork    [does not correspond to any directory on the SAG]
  transfer01 [corresponds to transfer01 on the SAG]
  transfer02 [corresponds to transfer02 on the SAG]
target01     [does not correspond to any directory on the SAG]
target02     [does not correspond to any directory on the SAG]
On SAG1:
efasag       [corresponds to efadata on the host]
  transfer01 [corresponds to transfer01 on the host]
On SAG2:
efasag       [corresponds to efadata on the host]
  transfer02 [corresponds to transfer02 on the host]
To create these directory structures:
  • When using MQHA to transfer files to and from the SAG:
    • Issue the following commands for the host: 
      mkdir -p /efadata/efawork
mkdir /efadata/transfer01
mkdir /efadata/transfer02
mkdir /target01
mkdir /target02
chown -R <broker uid>:<group> /efadata 
chmod -R u=rwx,g=rwx,o= /efadata
    • Issue the following commands for SAG1: 
      mkdir -p /efasag/transfer01
chown -R swnet:swnetg /efasag
chmod -R u=rwx,g=rwx,o= /efasag
    • Issue the following commands for SAG2: 
      mkdir -p /efasag/transfer02
chown -R swnet:swnetg /efasag
chmod -R u=rwx,g=rwx,o= /efasag
  • When using NFS to share files between the host and the SAG or RFH:
    • Issue the following commands for the host: 
      mkdir -p /efadata/efawork
mkdir /efadata/transfer01
mkdir /efadata/transfer02
mkdir /target01
mkdir /target02
chown -R <broker uid>:<group> /efadata 
chmod -R u=rwx,g=rwx,o= /efadata
    • Export the directories /efadata/transfer01 and /efadata/transfer02 for the host.
    • Issue the following commands for SAG1: 
      mkdir -p /efasag
chown -R swnet:swnetg /efasag
chmod -R u=rwx,g=rwx,o= /efasag
mount host:efadata/transfer01 efasag/transfer01
    • Issue the following commands for SAG2: 
      mkdir -p /efasag
chown -R swnet:swnetg /efasag
chmod -R u=rwx,g=rwx,o= /efasag
mount host:efadata/transfer02 efasag/transfer02
Example 3: Two SAGs with SAG MP option set switching
In this example:
  • Two SAGs (SAG1 and SAG2) are used for all file transfers.
  • An SAG MP option-set group is configured that allows a scenario to switch to another option set in the group:
    • The SAG directory (SagDirectory) and SAG subdirectory (SagSubDirectory) must be identical for all of the option sets in the group. This assures that the fully qualified name of the file is the same for all of the SAGs that might be called upon to send it.
    • The transfer directories must be identical for all of the SAGs used by the group. This assures that the file is available to all of the SAGs that might be called upon to send it.
  • One target directory is used, and it is on the same level as the data directory.
The following directory structure can be used:
On the host:
efadata       [corresponds to efasag on either SAG]
  efawork     [does not correspond to any directory on either SAG]
  transfer0x  [corresponds to transfer0x on both SAGs]
target        [does not correspond to any directory on either SAG]
On SAG1:
efasag        [corresponds to efadata on the host]
  transfer0x  [corresponds to transfer0x on the host]
On SAG2:
efasag        [corresponds to efadata on the host]
  transfer0x  [corresponds to transfer0x on the host]
To create these directory structures:
  • When using MQHA to transfer files to and from the SAG:
    • Issue the following commands for the host: 
      mkdir -p /efadata/efawork
mkdir /efadata/transfer0x
mkdir /target
chown -R <broker uid>:<group> /efadata 
chmod -R u=rwx,g=rwx,o= /efadata
    • Issue the following commands for SAG1: 
      mkdir -p /efasag/transfer0x
chown -R swnet:swnetg /efasag
chmod -R u=rwx,g=rwx,o= /efasag
    • Issue the following commands for SAG2: 
      mkdir -p /efasag/transfer0x
chown -R swnet:swnetg /efasag
chmod -R u=rwx,g=rwx,o= /efasag
  • When using NFS to share files between the host and the SAG or RFH:
    • Issue the following commands for the host: 
      mkdir -p /efadata/efawork
mkdir /efadata/transfer0x
mkdir /target
chown -R <broker uid>:<group> /efadata 
chmod -R u=rwx,g=rwx,o= /efadata
    • Export the following directory for the host: 
      /efadata/transfer0x
    • Issue the following commands for SAG1: 
      mkdir -p /efasag
chown -R swnet:swnetg /efasag
chmod -R u=rwx,g=rwx,o= /efasag
mount host:efadata/transfer0x efasag/transfer0x
    • Issue the following commands for SAG2: 
      mkdir -p /efasag
chown -R swnet:swnetg /efasag
chmod -R u=rwx,g=rwx,o= /efasag
mount host:efadata/transfer0x efasag/transfer0x

When using SAG MP option-set groups for a SendFile scenario, the file that is to be sent must be shared by all the SAGs to which the SAG MP option sets in the group refer. For example, the file must be stored centrally in a shared-file system, and all the SAGs must be configured to have identical SAG directory and subdirectory structures. This assures that the fully qualified name of the file is the same for all of the SAGs that might be called upon to send it.