1.1 Maintain Message Media Control

This topic explains systematic instructions to maintain message media control.

  1. On Homescreen, type MSDMGMCS in the text box, and click Next.
    The Message Media Control Maintenance screen displays.

    Figure 1-1 Message Media Control Maintenance


    Description of Figure 1-1 follows
    Description of "Figure 1-1 Message Media Control Maintenance"

  2. Click New to maintain details of a new media control system.
    The Message Media Control Maintenance screen displays.
  3. On the Message Media Control Maintenance screen, specify the fields.

    Note:

    The fields, which are marked with an asterisk, are mandatory.

    For more information on fields, refer to the field description table.

    Table 1-1 Message Media Control Maintenance - Field Description

    Field Description
    Node Click Search and specify the Node from the list of values. A node is the database instance on which Oracle FLEXCUBE Universal Banking is installed. On assigning a code to an MCS, specify the node or server at which the MCS is located. A branch’s database is located in a node and an MCS is also installed in a node. Thus, while defining an MCS, specify the node at which it has been installed.
    Media Control System Click Search and specify the Media Control System from the list of values. In Oracle FLEXCUBE Universal Banking, each media control system is identified by a 15- character code called an MCS code. If required, follow own convention for devising this code. The code that is assigned an MCS should be unique as it is used to identify the external source.
    Media Click Search and specify the Media from the list of values. Specify the media for which the bank is using the MCS. For example, if an MCS is set as MCSSWIFT and the media type is set as SWIFT, it indicates that Oracle FLEXCUBE Universal Banking can receive and transmit SWIFT messages through the media control system MCSSWIFT.
    Status Select the status of an MCS from the drop-down list:
    • Active
    • Passive
    It is only when an MCS is Active that messages will be directed to it. For example, If an MCS located at the node in which the branch operates malfunctions, indicate that the MCS is Passive. In this case, Oracle FLEXCUBE Universal Banking will not write into or read from the directories on the node. No message will be routed through a passive MCS.
    Delivery Type Select the delivery type from the Folder and Queue options. Depending on the selection, specify the details in the corresponding fields as follows:
    • Folder - If the Folder option is selected as the Delivery Type, specify the In Directory and the Out Directory. Further, after selecting Folder, if the Unix Swift Server option is checked for a UNIX SWIFT server, then specify the Unix In-Directory and the Unix Out-Directory. For a Windows Server, the In Directory and Out Directory must be maintained.
    • Queue - If the Queue option is selected as the Delivery Type, specify In Queue, Out Queue, and the type of queue i.e. Microsoft Message Queue or WebSphere Messaging Queue.
    In Directory and Out Directory If the Delivery Type is selected as Folder, and the SWIFT server is a Windows server then specify the full path of the directories from which Oracle FLEXCUBE Universal Banking should read and write incoming and outgoing messages respectively instead of specifying the node on which an MCS is located.
    File Prefix For the Media Control System, identify the outgoing message files generated in a different media with unique prefixes. Enter the unique identifier in this field.
    In Queue If the Delivery Type is Queue, then enter the full path of the queue in the node or server into which the MCS should store the incoming message hand-off file. Oracle FLEXCUBE Universal Banking by default pickup up and read all incoming messages transmitted through the specified media from this queue.
    Out Queue Enter the full path of the queue in the node or server into which the message hand-off file from Oracle FLEXCUBE Universal Banking for the specified media should be stored. The MCS which is located on the same node, will by default store the outgoing messages in this queue.
    Unix Swift Server Check this box if the SWIFT server is on UNIX at the bank. In this screen, specify the default In and Out Directories for the SWIFT message hand-off files. To continue with the normal banking operations, connect to another node and indicate the directory on that node from which Oracle FLEXCUBE Universal Banking should read from and write into.
    SWIFT Server on UNIX - In the Message Media Control Maintenance screen, indicate if the SWIFT server at the bank is on UNIX. Subsequently, specify the default In and Out Directories for the SWIFT message hand-off files.

    Table 1-2 SWIFT Server on UNIX - Field Description

    Field Description
    UNIX In-Directory Specify the full path of the directory on the SWIFT server where would like to store incoming SWIFT message files. Oracle FLEXCUBE Universal Banking pickups and process all incoming SWIFT message files from this directory.
    UNIX Out-Directory Specify the directory on the SWIFT server where would like to store outgoing SWIFT message hand-off files.
    The following process flow explains about MCS setup:

    Figure 1-2 MCS setup


    Description of Figure 1-2 follows
    Description of "Figure 1-2 MCS setup"

    Table 1-3 MX Preference - Field Description

    Field Description
    Data PDU Required Check this box, if the data PDU is required.
    XMLv2 Revision Select the XMLv2 revision from the drop-down list:
    • Revision 11
    • Revision 10
    Swift LAU Required Check this box, if the Swift LAU is required.
    LAU Type Select LAU type from the drop-down list:
    • HMAC
    • GCM
    Delivery Notification Required Check this box to get the delivery notification.
    File Type Select the required file extension from the drop-down list:
    • .ia
    • .xml

    Table 1-4 LAU Key Outgoing - Field Description

    Field Description
    Key First Part Specify LAU outgoing key first part.
    Key Second Part Specify LAU outgoing key second part.

    Table 1-5 LAU Key Incoming - Field Description

    Field Description
    Key First Part Specify LAU incoming key first part.
    Key Second Part Specify LAU incoming key second part.
  4. After making mandatory entries, save the record.
    For the MCS, identify outgoing message files generated in the media with unique prefixes. Oracle FLEXCUBE will automatically prefix outgoing message hand-off files for the MCS with the prefix that is specified. An MCS record that has been created should be authorized by a user, bearing a different Login ID, before the End of Day process (EOD) runs.
  5. Click Exit to end the transaction.

Parent topic: EMS Maintenance