3.7 Process Media Control Systems Detail

This topic provides the systematic instructions to maintain Media Control Systems (MCS).

The messages that are sent from and delivered to your bank are transmitted and received over sources that are external to FCIS. We shall call these external sources Media Control Systems (MCS).

In a distributed environment, the database of a branch is located in a node or server. The MCS of the messages are also installed in a node. Thus, while defining an MCS, you also need to indicate the node in which it is installed.

An MCS can handle only one media, hence you need to set up several media control systems for the various media types maintained for your bank. Apart from indicating the media type for an MCS, you can also indicate separate directories from which FCIS should read and write incoming and outgoing messages, for a given media.

  1. On Home screen, type UTDMCS in the text box, and click Next.
    The Media Control Systems Detail screen is displayed.

    Figure 3-7 Media Control Systems Detail


    Description of Figure 3-7 follows
    Description of "Figure 3-7 Media Control Systems Detail"

  2. On Media Control Systems Detail screen, click New to enter the details.
    For more information on fields, refer to the field description table.

    Table 3-4 Media Control Systems Detail - Field Description

    Field Description
    Node

    Alphanumeric; 420 Characters; Mandatory

    Specify a node or server at which the MCS is located, from the adjoining option list. A node is the Database instance on which FCIS is installed. A branch’s database is located in a node and an MCS is also installed in a node.
    Media Control System

    Alphanumeric; 60 Characters; Mandatory

    Specify a unique code for MCS to identify the external source. You can follow your own convention for devising this code.
    Media

    Alphanumeric; 60 Characters; Mandatory

    Specify the media for which your bank is using the MCS, from the adjoining option list. The option-list displays the media codes maintained at the Message Media Detail level.

    Status

    Optional

    Select a valid status of an MCS from the adjoining drop-down list. This list displays the following values:
    • Active – Select if you want to direct the messages through MCS.
    • Passive – Select if you do not want to direct any message to through MCS. If the status of MCS is passive, then FCIS will not write into or read from the directories on the node.
    Delivery Type

    Optional

    Select a valid type of delivery from the options. The following options are available for selection:
    • Folder – If you select this option, you must specify the In Directory and Out Directory for Windows Server. Further, after selecting this option, if you check the option Unix Swift Server for a UNIX SWIFT server, then you must specify the Unix In-Directory and the Unix Out-Directory.
    • Queue – If you select this option, you must specify In Queue, Out Queue and select a valid type of queue from the options. The following options are available for selection:
      • Microsoft Message Queue – Select if you want to maintain Microsoft message queue.
      • WebSphere Messaging – Select if you want to maintain WebSphere message queue.
    In Directory

    Alphanumeric; 512 Characters; Optional

    Specify the full path of the directory from which FCIS should read and write incoming message, if you have maintained the Delivery Type as Folder and the SWIFT server as Windows server.

    Out Directory

    Alphanumeric; 512 Characters; Optional

    Specify the full path of the directory from which FCIS should read and write outgoing message, if you have maintained the Delivery Type as Folder and the SWIFT server as Windows server.

    File Prefix

    Alphanumeric; 1 Character; Optional

    Specify a unique identifier for the specified MCS to identify the outgoing message files generated in a different media.
    Unix-In-Directory

    Alphanumeric; 512 Characters; Optional

    Specify the full path of the directory on the SWIFT server where you would like to store incoming SWIFT message hand-off files. The system will pickup and process all incoming SWIFT message files from this directory.
    Unix-Out-Directory

    Alphanumeric; 512 Characters; Optional

    Specify the full path of the directory on the SWIFT server where you would like to store outgoing SWIFT message hand-off files.
    In Queue

    Alphanumeric; 1020 Characters; Optional

    Specify the full path of the queue in the node or server into which the MCS should store the incoming message hand-off file, if the Delivery type is Queue. The system will pickup and read all incoming messages transmitted through the specified media from this queue, by default.

    Out Queue

    Alphanumeric; 1020 Characters; Optional

    Specify the full path of the queue in the node or server into which the message hand-off file from the system, for the specified media, should be stored. The MCS, which is also located on the same node, will store the outgoing messages in this queue by default.
    Unix Swift Server

    Optional

    Check this box if the SWIFT server at your Bank is on UNIX.
    Microsoft Message Queue

    Optional

    Check this option to select Microsoft message queue.
    WebSphere Messaging

    Optional

    Check this option to select WebSphere messaging.

Parent topic: External System Maintenance