Friday, February 24, 2017

SWIFTNet Profiles


SWIFTNet Profiles


SWIFTNet Profiles
Field
Description
Filtering criteria
Ex
Indicates if the emission or reception profile is in an exceptional state

Type
The type of SWIFTNet profile

Name
The emission profile or reception profile name

Status
The status of the profile
These are the possible values:
·         Enabled
·         Disabled
Mode
Indicates the mode in which the emission profile or the reception profile is. In Alliance, there are two modes in which an emission profile or a reception profile can operate. The two modes of operation are Manual and Automatic. The automatic mode allows you to schedule operations. When the emission profile or the reception profile is operating in manual mode, none of the scheduled operations are activated.

Session Status
The session status of the emission profile or reception profile.
These are the possible values:
·         Active: The profile has been activated and the session for this profile is in progress.
·         Inactive: The profile has been deactivated and the session is inactive.
·         Activating: The profile was inactive, the profile is in the process of being "activated".
·         Deactivating: The profile was active, but the session has been interrupted and the profile is in the process of being "deactivated".
·         Interrupted: The profile was active, but the session has been interrupted. The system attempts to resume the session automatically.
Number of Messages
The number of messages received or sent
These are the possible values:
·         Received Messages > 0
·         Sent Messages > 0
Urgent
The number of urgent messages queued

Normal
The number of normal messages queued

Sent
The number of messages successfully sent in the current session

Received
The number of messages successfully received in the current session

Connection
The name of the current connection used for emission or reception

Thursday, February 23, 2017

Deleting an Authorisation

This procedure provides instructions for deleting authorisations. You delete an authorisation by deleting an Authorisation to Send. On your correspondent's system, this action is recorded as the rejection of an authorisation.

Users and permissions

You can delete authorisations when the Delete Auth function is assigned to you in the Relationship Mgmt application.
The following permissions restrict the business relationships that you can access:
  • Allowed/Prohibited Destination(s)
  • Allowed/Prohibited Service(s)

Before you begin

Before deleting a Test and Training Authorisation to Send, ensure that the Signing BICs are defined in the authorisation. The Relationship Management application displays a warning message if the Signing BICs are empty. For more information about specifying the Signing BICs for a Test and Training authorisation,

To delete an Authorisation to Send:

  1. Select an authorisation that has the status "Enabled" or "Deleted".
    You can select the authorisation in the following windows:
    • Authorisation - Relationship Management
    • Authorisations
  2. From the Authorisation menu, select Delete.
    The Delete Authorisation to Send window appears.
    The Deletion Code is always xrma.003.4 - Record deleted.
  3. In the Reason for deletion field, explain why you are deleting the authorisation.
    Note
    If you are deleting an authorisation that has the status "Deleted", then the previous reason for deletion appears. You cannot edit the reason.
  4. If you need another user to approve the Delete action, then select the Needs delete approval option box.
    Note
    The Needs delete approval option box is selected and unavailable when you have the Bypass Approval permission set to "No" for the Delete Auth function.
  5. To delete the Authorisation to Send, click Delete.
    If the Needs delete approval option box is clear, then the Relationship Management application stores the authorisation with the status "Deleted". If you selected the Needs delete approval option box, then the Relationship Management application saves the authorisation with the status "Pending Delete Approval".
    Note
    After you delete the authorisation, the text in the Reason for Deletion field is no longer available for editing. However, the Delete button changes to the Resend Delete button and it remains available to allow you to re-send the Delete message in cases where a previous Delete message failed to reach your correspondent. This does not apply to an imported authorisation with the status "Deleted"
  6. Do you want to delete this Authorisation to Send?
    If yes, then click Delete.
    If the Needs delete approval option box is clear, then the Relationship Management application stores the authorisation with the status "Deleted". If you selected the Needs delete approval option box, then the Relationship Management application saves the authorisation with the status "Pending Delete Approval".
    If no, then click Cancel.
Clicking Cancel leaves the Authorisation to Send unchanged, closes the Delete Authorisation to Send window, and displays either the Relationship Management window or Authorisations window.

Rejecting an Authorisation

Purpose

This procedure provides instructions for rejecting an authorisation. You reject an authorisation by rejecting an Authorisation to Send.
When your system receives an Authorisation to Send, the Relationship Management application determines whether it relates to an existing one. If it relates to an existing Authorisation to Send, then it assigns the status "Pending Accept" to it but does not change its external status. Keeping the same external status ensures that the existing authorisation stays active until an RMA operator accepts the modified authorisation, or rejects it. If it is a new Authorisation to Send, then the Relationship Management application assigns the status "Pending Accept" but leaves the external status empty.

Users and permissions

You can reject authorisations when the Reject Auth function is assigned to you in the Relationship Mgmt application.
The following permissions restrict the business relationships that you can access:
  • Allowed/Prohibited Destination(s)
  • Allowed/Prohibited Service(s)

To reject an Authorisation to Send:

  1. Select an authorisation that has the status "Pending Accept".
    You can select the authorisation in the following windows:
    • Pending Action - Relationship Management
    • Authorisation - Relationship Management
    • Authorisations
  2. From the Pending Action or Authorisation menu, select Reject.
    The Reject Authorisation to Send window appears.
    When the authorisation relates to an existing Authorisation to Send, the window shows an additional sentence, which starts with "This new authorisation replaces an existing authorisation".
  3. Select one of the following rejection codes:
    • xrma.003.1 - no business relation exists
    • xrma.003.3 - Unexpected permissions
    • xrma.003.5 - Insufficient
    • xrma.003.7 - Duplicate value in permissions
    • xrma.003.99 - Undefined
    Note
    If you are rejecting an authorisation that has the status "Rejected", then the window shows the previous rejection code. You cannot edit this code or the rejection reason, but you can re-send the rejection.
  4. If you entered the rejection code, xrma.003.99 - Undefined, then explain your reason for rejecting the authorisation in the Reject Reason field.
    If you select one of the other rejection codes, then the rejection reason is optional.
  5. If you need another user to approve the Reject action, then select the Needs reject approval option box.
    Note
    The Needs reject approval option box is selected and unavailable when you have the Bypass Approval permission set to "No" for the Reject Auth function.
  6. To reject the Authorisation to Send, click Reject.
    If the Needs reject approval option box is clear, then the Relationship Management application stores the authorisation with the status "Rejected". If you selected the Needs reject approval option box, then the Relationship Management application saves the authorisation with the status "Pending Reject Approval".
    Note
    After you reject the authorisation, the text in the Reject Reason field is no longer available for editing. However, the Reject button changes to the Resend Reject button and it remains available to allow you to re-send the Reject message in cases where a previous Reject message failed to reach your correspondent. This does not apply to an imported authorisation with the status "Rejected".
Clicking Cancel leaves the Authorisation to Send unchanged, closes the Reject Authorisation to Send window, and displays either the Relationship Management window or the Authorisations window.

Accepting an Authorisation

Purpose

This procedure provides instructions for accepting an authorisation. You accept an authorisation by accepting an Authorisation to Send.
When your system receives an Authorisation to Send, the Relationship Management application determines whether it relates to an existing one. If it relates to an existing Authorisation to Send, then it assigns the status "Pending Accept" to it but does not change its external status. Keeping the same external status ensures that the existing authorisation stays active until an RMA operator accepts the modified authorisation, or rejects it. If it is a new Authorisation to Send, then the Relationship Management application assigns the status "Pending Accept" but leaves the external status empty.

Users and permissions

You can accept authorisations when the Accept Auth function is assigned to you in the Relationship Mgmt application.
The following permissions restrict the business relationships that you can access:
  • Allowed/Prohibited Destination(s)
  • Allowed/Prohibited Service(s)

To accept Authorisations to Send:

  1. Select an authorisation that has the status "Pending Accept".
    You can select the authorisation in the following windows:
    • Pending Action - Relationship Management
    • Authorisation - Relationship Management
    • Authorisations
  2. From the Pending Action or Authorisation menu, select Accept.
    The Accept Authorisation to Send window appears.
    When the authorisation relates to an existing Authorisation to Send, the window shows an additional sentence, which starts with "This new authorisation replaces an existing authorisation"
  3. If you need another user to approve the Accept action, then select the Needs accept approval option box.
    Note
    The Needs accept approval option box is selected and unavailable when you have the Bypass Approval permission set to "No" for the Accept Auth function.
  4. Do you want to accept this Authorisation to Send?
    If yes, click Accept.
    If the Needs accept approval option box is clear, then the Relationship Management application stores the authorisation with the status "Enabled". If you selected the Needs accept approval option box, then the Relationship Management application saves the authorisation with the status "Pending Accept Approval".
    If no, then click Cancel.
    The Relationship Management application leaves the Authorisation to Send unchanged. It closes the Accept Authorisation to Send window and displays either the Relationship Management window or the Authorisations window.

Modifying an Authorisation

This procedure provides instructions for modifying the details of an authorisation in the Authorisations window.
Tip
You can modify multiple authorisations simultaneously using the procedure for creating Authorisations to Receive.
When you are creating new Authorisations to Receive, you can modify existing authorisations if you define the same service, Correspondent BIC, and list of Own BICs in the new authorisation as are defined in the existing authorisations. The Relationship Management application applies the same details to each of the selected authorisations.
For more information about what happens to the authorisation after you have modified it. The same process occurs for modifying an active authorisation as for creating an authorisation.

Scope of modifications

In the Authorisations window, you can modify an Authorisation to Receive but you can only view or edit the comments of an Authorisation to Send.
You cannot modify the following details of an authorisation:
  • service
  • Own BIC
  • Correspondent BICs
  • status

Users and permissions

You can modify authorisations when the Modify Auth function is assigned to you in the Relationship Mgmt application.
The following permissions restrict the business relationships that you can access:
  • Allowed/Prohibited Destination(s)
  • Allowed/Prohibited Service(s)

Before you begin

This procedure assumes that you are familiar with the layout and the information displayed in the Authorisations window.
If you close the Authorisations window by clicking the Close icon, Icon, then a warning appears. Select the appropriate action. The buttons in the warning dialog box have the following functions:
  • OK closes the window without saving the changes that you made.
  • Cancel returns to the Authorisations window and displays the changes that you made.
  • Help displays help about the task.

To modify authorisation details:

  1. Select an authorisation in the Authorisation - Relationship Management window.
  2. Select Open from the Authorisation menu.
    The Authorisations window appears.
  3. To modify the Signing BICs for Test and Training authorisations.
  4. To add or edit comments, click Open comments window in the main window and add the comments for the authorisation.
  5. Select the Authorisation to Receive tab, and then edit the authorisation details in the New Authorisation pane.
    Note
    The New Authorisation pane does not show message or request types that the relevant standard no longer supports.
  6. From the Authorisation menu, select Modify to save the changes.
    If you are modifying a Test and Training authorisation and a Signing BIC for Test and Training is not defined, then a warning message appears. Define the Signing BIC for Test and Training a
    The Modify Authorisation to Receive dialog box appears.
  7. To save the authorisation for future editing
    Select Draft
    The Relationship Management application saves the authorisation with the preparation status "Draft".
    If the authorisation is already active, then it stays active, and gains the preparation status "Draft" in addition to its external status.
    To activate the new version of the authorisation to make it the Current version
    Select Enabled
    This option is available if your user profile has Bypass Approval set to "Yes" for the Modify Auth function.
    The Relationship Management application saves the authorisation with external status, "Enabled", and activates it so that it becomes the Current authorisation.
    To have another user approve the new version of the authorisation
    Select Pending Approval
    The Relationship Management application saves the authorisation with the preparation status, "Pending Approval", which requires another user to approve it.
    If the authorisation is already active, then it stays active, and gains the preparation status "Pending Approval" in addition to its external status.
  8. Click OK.

Revoking an Authorisation

This procedure provides instructions for revoking authorisations. You revoke an authorisation by revoking an Authorisation to Receive.
For more information about what happens to the authorisation after you have revoked it.

Users and permissions

You can revoke authorisations when the Revoke Auth function is assigned to you in the Relationship Mgmt application.
The following permissions restrict the business relationships that you can access:
  • Allowed/Prohibited Destination(s)
  • Allowed/Prohibited Service(s)

To revoke Authorisations to Receive:

  1. Select the authorisation that you want to revoke.
    You can select the authorisation in the following windows:
    • Authorisation - Relationship Management
    • Authorisations
  2. From the Authorisation menu, select Revoke.
    The Revoke Authorisation to Receive window appears.
    If a Signing BIC for Test and Training is not defined, then a warning message appears. Define the Signing BIC for Test and Training.
  3. If you need another user to approve the Revoke action, then select the Needs revocation approval option box.
  4. Click Revoke.
    If the Needs revocation approval option box is clear, then the Relationship Management application stores the authorisation with the status "Revoked". If you selected the Needs revocation approval option box, then the Relationship Management application stores the authorisation with the status "Pending Revoke Approval".
    Your correspondent must acknowledge the revocation action.

Tuesday, February 21, 2017

RMA : Creating an Authorisation

Purpose

The procedure explains how to create an authorisation by creating an Authorisation to Receive, and to create authorisations using an existing authorisation. An Authorisation to Receive is the authorisation that you (Own BIC) send to a correspondent (Correspondent BIC) to enable that correspondent to send messages to you.
If you create an authorisation using an existing one, then the Relationship Management application uses the values of the existing authorisation as default values for the new authorisation. You can keep those values or modify them if necessary.
RMA Plus enables you to define a granular authorisation which specifies the types of messages within a service that a correspondent can send you. This capability is defined by the service and the available granularity levels for a service are defined in the application service profile. A non-granular authorisation covers all types of messages.
For more information about what happens to the authorisation after you have created it,
For more information about creating an authorisation for Test and Training,

Using an existing authorisation

When you base a new authorisation on an existing one, the New Authorisation to Receive Details window shows the same details as in the existing one. You can use those details, or modify them if necessary.
The comments from the existing authorisation are not included, so you can enter new comments for the new authorisation.

Users and permissions

You can create authorisations when the Create Auth function is assigned to you in the Relationship Mgmt application.
The following permissions restrict the business relationships that you can access:
  • Allowed/Prohibited Destination(s)
  • Allowed/Prohibited Service(s)

Before you begin

When you are creating a granular authorisation for RMA Plus, ensure that Own BICs are approved as candidates for granular authorisations.

To create an Authorisation to Receive:

  1. To create an authorisation without basing it on an existing one, select New or New (granular) from the Authorisation menu.
    To create an authorisation based on an existing authorisation, open an authorisation and view its details in the Authorisations window. Then, select New As or New As (granular) from the Authorisation menu.
    If the existing authorisation has a preparation status, then the new authorisation is based on the authorisation in preparation rather than the active authorisation. Also, if you view an Authorisation to Send or an Authorisation to Receive, then the new authorisation is based on the authorisation that is being viewed.
    The New Authorisation to Receive window appears.
    The Available list displays the BICs for which you have permission to create an authorisation.
    For granular authorisations, the list shows only the BICs that are approved as candidates for granular authorisations, and for which you have permission to create an authorisation.
  2. Select the service to which the authorisation will apply.
    The list of services contains the live services (including the associated Test and Training !p service) that require authorisations and which are specified in the application service profile. You can select another service by selecting the Other option from the Services list and then, selecting the service name and optionally, entering an environment identifier.
    Authorisations that are based on an existing one show the same service as the existing authorisation.
  3. Select the licensed BIC8s for which you want to create authorisations.
    Tip
    Selecting several BICs in this field generates an Authorisation to Receive for each BIC8. Each authorisation has the same validity period and comments, if any are specified.
  4. Type the BIC8 of the Correspondent BIC.
    This gives permission to the Correspondent BIC to send messages to the Own BICs in the Selected list.
    If the BIC and Bank file is already installed, then the first 35 characters of the Correspondent's BIC expansion appear automatically beside the Correspondent BIC.
  5. Click Continue.
  6. If an authorisation exists for the business relationship, then the New Authorisation to Receive window appears.
    In this case, select an action by clicking one of the following buttons:
    • Modify - Apply the authorisation details to all the selected Own BICs.
      (This action modifies the authorisation details of those BICs.)
    • Skip - Leave the existing authorisations for the selected BICs unchanged, and create new authorisations for the remaining BICs.
    • Cancel - Display the New Authorisation to Receive window, where you can change the list of Selected Own BICs, or cancel the task.
    If no authorisation exists for the service, Correspondent BIC, and Own BICs that you selected, then the New Authorisation to Receive Details window appears.
    Note
    When you base a new authorisation on an existing one, the New Authorisation to Receive Details window shows the same details as in the existing one. You can use those details, or modify them if necessary.
    The comments from the existing authorisation are not included, so you can enter new comments for the new authorisation.
  7. To specify a validity period for the authorisation after it becomes active, select the option box Timebound Authorisation In the New Authorisation to Receive Details window. Then, specify the date range in the Valid from and Valid until fields.
    Valid dates are between 01 January 2006 and 31 December 2037, inclusive.
    The dates are stored in Greenwich Mean Time (GMT), with their times set to 00:00:01 and 23:59:59. The format of the date is defined by the Date configuration parameter in the System Management application.
  8. For a granular authorisation, specify the types of messages that may be transmitted between both parties. The available granularity levels for a service are defined in the application service profile.
  9. Enter comments about the authorisation (optional).
  10. From the Authorisation menu, select Add.
    The Add Authorisation to Receive dialog box appears.
    Assign one of the following statuses to the authorisation:
    • Draft - Save the authorisation for future editing.
      The Relationship Management application saves the authorisation with the preparation status "Draft". If the authorisation exists and is active, then it stays active and gains the preparation status "Draft" in addition to its external status.
    • Enabled - Activate the new version of the authorisation to make it the Current version.
      This option is available if your user profile has Bypass Approval set to "Yes" for the Create Auth function.
      The Relationship Management application saves the authorisation with external status, "Enabled", and activates it so that it becomes the Current authorisation. The date on which the authorisation becomes active is the Issued Date, and it is stored and displayed in GMT.
    • Pending Approval - Request approval for the new version of the authorisation.
      The Relationship Management application saves the authorisation with the preparation status, "Pending Approval", which requires another user to approve it. If the authorisation exists and is active, then it stays active and gains the preparation status "Pending Approval" in addition to its external status.
  11. Click OK.

Monday, February 20, 2017

Alliance Relationship Management

Alliance Access provides the Alliance Relationship Management to help you manage business
relationships with counterparties through authorisations that are sent as XML messages over
the RMA service.

You can use the Alliance Relationship Management to help you manage the authorisations for
exchanging FIN, InterAct, and FileAct messages.

While the SWIFTNet Public Key Infrastructure (PKI) authenticates messages, the RMA service
is essential to ensure that the exchange of authenticated messages complies with the
agreements of established business relationships.

Manage authorisations

You can create, modify, delete, revoke, accept, and reject the authorisations for exchanging
FIN, InterAct, and FileAct messages. It also possible to implement the 4-eyes principle for
managing authorisations, which dictates that at least two users must witness a certain action, or
the outcome of that action.

It is possible to create an authorisation for multiple BIC8s in a single operation.
You can easily search for authorisations using search criteria, including authorisations with
"anomalies" (unilateral relationships). You can also search for authorisations that have actions
pending on them.

You can view a current and new authorisation side-by-side in the Alliance Relationship
Management, which allows you to compare easily two versions of an authorisation to identify
the differences. In addition, you can add comments to an authorisation for your benefit. These
comments are stored locally, and are not exchanged with your correspondent.
RMA Plus licensed option

RMA Plus (61:RMA PLUS) is a licensed option that extends the basic application by providing
the ability to create authorisations with additional granularity for message types. Therefore, it
provides you with more control over the types of messages that a correspondent can send to
your organisation.

The application service profile of the service specifies the available granularity levels for the FIN
services and for all other InterAct and FileAct services. For the FIN service, you can authorise
the sending of messages by message type. For the other services, you can authorise the
sending of messages by request type patterns.

Exchange queries and answers with correspondents
You can send and receive a query and answer about a business relationship with the
counterparty in that relationship.
You can search for queries and answers easily using search criteria.

Administer authorisations
You can export and import all authorisations (for FIN, InterAct, and FileAct) automatically or
manually, and also generate of a report that provides details about the results. You can also
export automatically only the authorisations that have been changed.

Saturday, February 18, 2017

SWIFT File transfer licences

SWIFT File transfer licences
File transfer interface provides two distinct licences, FT-Adapter and FT-Integrated, which are represented as licence options:
• The file transfer adapter licence option 61:FTA enables the automatic transfer and reception of files.
• The file transfer integrated licence option 60:FTI enables the transfer and reception of files triggered by application-generated commands.

Tuesday, February 14, 2017

About Alliance Gateway

Alliance Gateway is a modular software package that is installed on top of the SWIFTNet Link
software, and is designed to enable application-to-application communication. Using the
SWIFTNet interactive services InterAct and FileAct, messages and files are typically exchanged
between a customer application (client) and a central application (server) over the Secure IP
Network.


Monday, February 6, 2017

Queues and Routing

A queue is where Alliance Access stores message instances.
A routing point is where message transformation takes place in Alliance Access.
Routing points consist of these elements:

• a queue where messages are stored
• a message processing function
• a set of routing rules.

An exit point is a special routing point that Alliance Access uses to route message instances to
external applications (message partners). The system configures generic exit points to allow
default processing of all kinds of messages by default, but operators can define their own exit
point for specific routing purposes. In addition to these exit points, operators can also create
user-defined queues for other needs.

Additional queues are sometimes also available while installing the ADK component. Those
queues are considered as ADK queues.

Messages are routed and processed in Alliance Access until they reach their final destination.
The processing of messages takes place at "routing points" where the messages are stored in
queues. These can be divided into system queues and user-defined queues and exit points.
Associated with a routing point is a Message Processing Function (MPF) which typically
fetches, processes and then routes (according to the routing rules associated with the routing
point) the messages in the queue at the routing point.

Each routing point queue can be controlled by holding or releasing it to stop and start the flow of
messages. Queue thresholds can be set to generate warnings when the number of messages
in a queue reaches a specified level. Also, if a message is older than the maximum message
age limit that is set, then the queue is put in an exceptional state and an event (by default
configured as an alarm) is logged.

FIN Logical Terminals

What is a logical terminal?

A logical terminal is a logical entity through which users send and receive FIN messages.
Each logical terminal is identified by a unique 8-character BIC (that is a destination), plus a 1-
character terminal code. When you first install Alliance Access or when you purchase additional
destinations, you must configure the logical terminals using Alliance Access Configuration.
Operators can then manage the connection of logical terminals to the SWIFT network from both
Alliance Access Configuration and Alliance Access Monitoring.

You can work with live or FIN test and training logical terminals.

To deal with traffic volumes of between 10,000 and 20,000 messages per day, it is
recommended to have two logical terminals on two different destinations. Both logical terminals
must be configured for Login and Select in input/output mode.


Sunday, February 5, 2017

Connection Methods in SWIFT Alliance

A connection method is part of a message partner profile. It specifies the type of communication.
back-office application or external product. The location of the message or parameter files for
transmission are specified as a connection point, which is associated with a connection method.
The Application Interface application supports several connection methods. This section
provides basic descriptions of these connection methods after the summary table.

To exchange FileAct messages between Alliance Access and a message partner, the following
connection methods are available:
• Direct FileAct
• File Transfer
• WebSphere MQ

Direct FileAct
The Direct FileAct connection method enables the transfer of a payload file between Alliance
Access and a back-office application. A payload file contains the data that is to be transferred.
The FileAct transmission parameters are always deducted from the message partner profile. No
XML version 2 message or parameter file with FileAct settings is required with the payload file.
Dedicated Direct FileAct input and output file directories are accessible to both Alliance Access
Alliance Access 7.0
244 System Management Guide
and the back-office application or operator. The back-office application or operator use these
directories to simply drop the payload files to send over SWIFTNet or get the payload files
received from SWIFTNet.

Direct FileAct also enables back-office applications to benefit from simplified reporting of
network acknowledgements and of reconciled delivery notifications.
A message partner profile with the Direct FileAct connection method must exist for each
correspondent that will use Direct FileAct to transmit files between each other.

The Direct FileAct connection method requires the licence package 22: DIRECT FILEACT.
The file-transfer session can be started automatically or manually. For example, if a back-office
application stores a payload file in a pre-configured input directory, then the presence of the file
in the directory can automatically start a file-transfer session.
You can define a message partner profile for Direct FileAct only through the Alliance
Configuration package on Alliance Web Platform. You can also view a message partner profile
for Direct FileAct through the Alliance Monitoring package on Alliance Web Platform.

File Transfer
The File Transfer method enables the transfer of batch files containing multiple FIN, FileAct, or
InterAct messages between Alliance Access and a back-office application. For FileAct
messages, in addition to transferring a payload file, Alliance Access or a back-office application
also transfers an XML version 2 message containing the FileAct settings which control the file
transfer, and an optional parameter file. The file-transfer session can be started automatically or
manually.

Note For FileAct messages, the body of the XML version 2 message does not contain
the payload of the message to be transmitted. Instead, the body of the message
points to the location of the payload file.
To exchange FileAct messages, XML version 2 with revision 2 or 3 is required.
For each message format, the communication media are file system directories. Alliance Access
can read or write a batch message file from or to a directory in a local or remote file system.
The File Transfer connection method supports the following message file data formats:



Message Flow in the Application Interface

Message Processing Functions (MPF) control the exchange of messages between the
Application Interface (AI) and the message partners, as follows:

• The first MPF controls the flow of messages from message partners (input session) to the
inbound queue of the Application Interface. This queue is identified internally as
AI_from_APPLI. This queue is used to route all incoming messages from all message
partners using the connection methods, File Transfer, Interactive, WebSphere MQ, or SOAP.

• A second MPF controls the flow of messages from exit points to message partners (output
session). When more than one exit point is assigned to a message partner during an output
session, a polling mechanism services each exit point queue in turn.
Bidirectional message exchange (to and from Alliance Access to a message partner) during the
same session is possible with the following connection methods:
• Interactive
Message flow in an input session


Message Partners and Message Partner Profiles

A message partner is an external application, such as, a back-office application, a printer, or a
mainframe connection.

The Application Interface manages the transfer of files and messages between Alliance Access
and a message partner using the profile that is defined for that message partner.
Profile of a message partner

A message partner profile specifies the parameters necessary to transfer message and files
between Alliance Access and a message partner. The most important of these parameters is
the connection method, which defines the type of connection protocol and the data format to be
used for the transfer.

Every application that communicates with Alliance Access must have a message partner profile
defined in the Application Interface.
You can view message partner


SWIFT Application Interface

The Application Interface controls the transfer of messages and files between Alliance Access
and back-office applications, printers, or any other system that communicates with Alliance
Access. Suitable messages for transferring include SWIFT FIN, MX, FileAct, and system
messages. Suitable files include payload files, or files that contain several messages (such as
for Bulk Payments).

Within the Application Interface, a message partner represents the external application or
product that communicates with Alliance Access. A message partner profile specifies how each
message partner communicates with Alliance Access, and allows you to control and monitor the
communication sessions.

Alliance Access transfers a message to a message partner through an exit point, which holds
the message in a queue before transferring it to the message partner. Each exit point is
associated with a particular message partner.

The Application Interface allows you to:
• create, modify, or remove exit points and message partner profiles
• assign an exit point to a message partner
• control and monitor communication sessions between Alliance Access and a message
partner.

What are the functions of the CIPS (Phase I)?

The main functions of the CIPS (Phase I) are to facilitate processing of cross-border RMB business and to support settlement of cross-border trade in goods and services, cross-border direct investment, cross-border financing and cross-border individual remittance.

The CIPS (Phase I) has main features as follows: First, the CIPS (Phase I) processes remittance of individual customers and financial institutions on a real-time basis and in full amount. 

Second, through one-point access, direct participants can enjoy centralized clearing service, shortened clearing path and more efficient clearing.

Third, the CIPS adopts the internationally accepted ISO20022 message standard and uniform Chinese four-corner codes; transmission in Chinese and English is supported; settings of fields such as name, address, charging etc. better facilitate the automatic processing of RMB business.

In terms of message design, CIPS takes full considerations of the conversion requirements with the current SWFIT MT messages and thus, facilitates STP (straight through processing) of cross-border business and supports future business development. Fourth, running hours of the CIPS covers all major time zones in Asia, Europe, Africa and Oceania. Fifth, direct participants in Mainland China are connected to the system via special lines.

Saturday, February 4, 2017

Alliance Access Monitoring Main Page

Overview
Depending on the configuration of the Alliance Web Platform installed on your system, you have the possibility to monitor multiple Alliance server instances. The instances that can be monitored are the instances that belong to the Alliance instance group associated to the Monitoring application group. 

Once you are logged on, the monitoring details for the selected instance are displayed in the monitoring tree view. The list of entities displayed in the tree view for a given instance depends on the type of server and on the operation mode (operational or housekeeping). The permissions of the operator who is logged on also determine which entities are available. The list of entities is automatically refreshed according to the refresh rate set. 

If there are other instances in the Alliance instance group, they appear in the tree view but without any details. To monitor another instance, you have to select it in the tree view and log on.

The Alliance Access Monitoring sessions never expire.
The details of the exceptional events for a given instance are displayed in the Exceptions tab.
In the Monitoring Scope tab, it is possible to define scope restrictions for FIN logical terminals, SWIFTNet profiles, message partners, and queues. The scope defined then applies to all the screens of Alliance Access Monitoring.
For objects that are not included in the monitoring scope, the following applies:
  • The object is not displayed in the list of entries of the entities
  • Exceptions raised for this object are not reported in the list of exceptions
At least one object per category is selected by default.
The monitoring scope that you define for a specific server instance is stored as a user preference in Alliance Access. Each time that you connect to this specific server instance, the monitoring scope defined is applied.

Display


Colour conventions for exceptions
Tree view
The following conventions are used for the nodes of the tree view:
·         Red: used for monitored entities which are in exceptional state
·         Green: used for monitored entities which are not in exceptional state
·         Yellow: used when the status is unknown
·         Grey: used for entities which are not monitored
Lists
The following conventions are used for the entries of each entity:
Red: used for monitored entities which are in exceptional state
Notification mechanism and exception counters
Notifications
When an exception occurs, the instance node is highlighted in orange and flashes during a few seconds.
Exception counters
Counters displaying the number of elements in exceptional state are available for the exception node and for the following sub-nodes:
·         FIN Logical Terminals
·         SWIFTNet Profiles
·         Message Partners
·         Queues
·         Disk Space
Dashboard
The Dashboard is the initial page displayed when clicking on a specific Alliance Access instance node in the Monitoring tree.
In this Dashboard, you can customise your summary view by adding, updating, moving, removing and resizing the following portlet types; Logical Terminals, SWIFTNet Profiles, Message Partners, Queues, Queue Trend, Components, Processes, Operator Sessions, File Transfers, Event Log, Disk Space.
Important:
The Dashboard is not available in housekeeping mode.
You can add up to eight portlets to your dashboard view. When adding a portlet, you can choose your own title.The portlets added are organised in two columns, with a standard height. You can minimise the portlets present in their custom summary view, which causes the portlet to be reduced in height to its title. You can also can resize vertically each portlet; other portlets in the same column are resized vertically in accordance. Portlets can also be moved between columns.
The colour of portlets changes to red, and flashes, as soon as there is an exception on at least one item displayed in the portlet.
Every portlet has a dedicated refresh rate available via the settings button. The exception counters displayed in each portlet is refreshed according to the global refresh setting and not to the individual portlet setting. The date and time of the last refresh is displayed in each portlet.
Note:
Dashboard views are defined per operator and are remembered across the sessions of each operator. Initially, the dashboard view of an operator who has not yet defined one does not contain any portlet.
The actions on monitored objects, when executed from portlets, remain subject to the same permission(s) as when executed from the corresponding GUI applications from the monitoring tree of Alliance Access instances.
Clicking on an entity in a list displayed in a portlet opens the details of that entity in a pop-up window.
Portlet descriptions and defaults
Portlet name
Filtering criteria
Columns displayed
Action menu bar
Settings
FIN Logical Terminals
None
Ex, Destination, Code, Status, Session Status
Change view button and actions possible on LTs.
Apply filtering criteria, respectively amongst all the columns and filtering criteria that exist in the 'Logical Terminals' GUI available in the monitoring tree under the Alliance Access instance node.
SWIFTNet Profiles
None
Ex, Type, Name, Status, Session Status
Change view button and actions possible on SWIFTNet Profiles.
Apply filtering criteria, respectively amongst all the columns and filtering criteria that exist in the 'SWIFTNet Profiles' GUI available in the monitoring tree under the Alliance Access instance node.
Message Partners
None
Ex, Name, Direction, Connection Method, Status, Session Status
Change view button and actions possible on MPs.
Apply filtering criteria, respectively amongst all the columns and filtering criteria that exist in the 'Message Partners' GUI available in the monitoring tree under the Alliance Access instance node.
Queues
None
Ex, Name, Type, Threshold, Inst/Threshold %, Status
Change view button and actions possible on queues.
Add/use/remove filtering criteria , respectively amongst all the columns (plus a Trend column) and filtering criteria that exist in the 'Queues' GUI available in the monitoring tree under the Alliance Access instance node.
Queue Trend
None
The name and the graph showing the history of the number of message instances versus threshold ratio values over the last 10 minutes
-
Change the queue whose trend is displayed in the portlet. Only one queue at a time can be displayed in a Queue Trends portlet instance.
Components
None
Name, Description, Status
Change view button and actions possible on Components.
Apply filtering criteria, respectively amongst all the columns and filtering criteria that exist in the 'System/Components' sub-GUI available in the monitoring tree under the Alliance Access instance node.
Processes
None
Component, Description, Status
Change view button and actions possible on Processes.
Apply filtering criteria, respectively amongst all the columns and filtering criteria that exist in the 'System/Processes' sub-GUI available in the monitoring tree under the Alliance Access instance node.
Operator Sessions
None
Name, Type, Expiration, Session Type
Change view button and actions possible on Operator sessions.
Apply filtering criteria, respectively amongst all the columns and filtering criteria that exist in the 'Operator Sessions' GUI available in the monitoring tree under the Alliance Access instance node.
File Transfers
None
I/O, Transfer Reference, User Reference, Status, Progress, Service Name, Request Type, File Name
Change view button and actions possible on File Transfers.
Apply filtering criteria, respectively amongst all the columns and filtering criteria that exist in the 'File Transfers' GUI available in the monitoring tree under the Alliance Access instance node.
Event Log
None
Date and time, Severity, Description
Change view button and actions possible on Events.
Add/use/remove filtering criteria , respectively amongst all the columns and filtering criteria that exist in the 'Event Log' GUI available in the monitoring tree under the Alliance Access instance node.
Disk Space
None
Ex, Component and Location, Free Disk Space
Change view button and actions possible on Disk Space.
There is no filtering criteria available in the 'Disk Space'.

Exceptions Tab
Content
The Exceptions tab contains these elements:
Display





Exceptions
Exceptions
Field
Description
Filtering criteria
Entities
These check boxes allow you to select the elements that you want to display in the list
These are the possible values:
  • Logical Terminal
  • SWIFTNet Profile
  • Message Partner
  • Queue
  • Disk Space
When no filtering criteria are selected, no filtering applies. All the exceptions are displayed.
When filtering criteria are selected, the list is restricted to the exceptions raised for the entities selected.
Ex
Indicates if entities are in an exceptional state

Date
The date and time when the exceptional state occurred

Type
The type of exception
These are the possible values:
  • Message Partner
  • Logical Terminal
  • Emission Profile
  • Reception Profile
  • Queue
  • Disk Space

Description
The description of the exception


Monitoring Scope Tab
Content
The Monitoring Scope tab contains these elements:
  • Details of the monitoring scope
See Details
  • Functions that allow you to manage the monitoring scope
Display



Details
Column
Description
Monitoring Scope
For certain entities, you can select the elements which will be monitored.
These are the entities for which you can define a monitoring scope:
  • FIN Logical Terminals
  • SWIFTNet Profiles
  • Message Partners
  • Queues
Functions
Function
Description
Reset to Default
Enables you to reset the monitoring scope to its default value

Alliance Instance Page

Description
The Alliance Instance page allows you to log on to an instance and start monitoring it.
Display


Fields
User Name
The user name that corresponds to your operator definition.
Password
The password that corresponds to your operator definition.
Alliance Server Instance
The name of the instance. Read-only.

Define the Monitoring Scope
This procedure enables you to define a monitoring scope.
Before you begin
To be able to define a monitoring scope, your operator profile must have this entity:
  • Monitoring
Security officers can also define a monitoring scope.
Procedure
  1. In the tree view, select the instance node.
  2. Click the Monitoring Scope tab.
  3. In the FIN Logical Terminals, SWIFTNet Profiles, Message Partners, and Queues selection lists, select the objects that you want to monitor.
  4. Click Save.
A status popup message appears.
The scope defined applies to all the screens of Alliance Access Monitoring.
Results
Note:
Click Reset to Default and then Save to restore the default settings.
Start Monitoring an Instance
This procedure enables you to start monitoring an instance.
You cannot monitor instances which are in a disabled state.
Procedure
  1. In the tree view, select the node of the instance that you want to monitor.
The Alliance Instance page opens.
  1. Click the Start monitoring <instance name> link.
A login window opens.
  1. Enter your User Name and Password. Both are case sensitive.
  2. Click Login.
Results
The details of the instance are displayed in the tree view.
The Exceptions tab is not available in the following cases:
  • when the instance is in housekeeping mode
  • if you do not have the Monitoring entity in your operator profile
Stop Monitoring an Instance
This procedure enables you to stop monitoring an instance.
Procedure
  1. In the tree view, select the node of the instance from which you want to log off.
  2. Click Logout in the top right corner of the browser window.
The Confirmation Message window opens.
  1. In the Instance drop-down list, select the instance from which you want to log off.
  2. Click OK.
The Confirmation Message window closes and the Alliance Instance page is displayed.