MSIF command service (DNF_O_CMD)
The MSIF command service controls the MSIF transfer services and
message or file transfers. This service:
- Automatically detects scenario timeouts (that is, when an attempt to transfer a message or file to or from an SAG is not completed within its timeout period)
- Automatically detects expired scenarios and modifies their transfer state (see Scenario expiration)
- Can automatically clean up information pertaining to completed transfers
By means of issuing CLI commands, users with different roles use
this service to control different aspects of file and message transfers:
- MSIF operator
- A user with this role uses DNF_O_CMD to operate the MSIF transfer services. For example, the user can start or stop the MSIF transfer services for an OU, or manually clean up information pertaining to completed transfers in all OUs.
- MSIF SWIFT operator
- A user with this role uses DNF_O_CMD to operate SAGs and SnF sessions. For example, the user can open or close an SnF output channel to initiate SWIFT to push to the local MSIF transfer services messages or files queued up in an SnF queue at SWIFT.
- MSIF administrator
- A user with this role uses DNF_O_CMD to administer message-transfer or file-transfer scenarios. For example, the user can list information about a message-transfer or file-transfer scenario, cancel a message-transfer or file-transfer scenario, or recover a scenario that encountered a recoverable error.
- MSIF SWIFT administrator
- A user with this role uses DNF_O_CMD to create and delete SnF channels.
The MSIF command service is implemented as message broker message flow
with two input queues:
- prefix.DNF_O_CMD
- When a user issues a command by means of the CLI, the CLI puts a message to this queue.
- prefix.DNF_O_CMDCTRL
- When the MSIF command service processes commands in batches, it puts a message in this queue to trigger the next batch in a new transaction.
