| IBM® Sterling
Standards Database for SWIFT |
- Provides all validation for field tags and structures
for SWIFT messages.
- References a SWIFT extended rule library that is
automatically checked in so you can use it with your maps.
- SWIFT_FINMessageTypes code list, supplied as part
of the install, which contains a list of valid SWIFT message types.
- If you purchase a Financial Services license, you
have access to XML standards once you download them.
|
- Populate the external codes lists: SWIFT_Addresses,
SWIFT_BaseAddresses (only needs to be populated when address verification
is enabled), SWIFT_Currencies, SWIFT_Countries, IBAN_Formats, SWIFT_BICPlusIBAN,
and SEPARouting.
- If you want to use BIC+ Validation, you must also
populate the BICPlusIBAN code list.
See SWIFT Envelopes.
- Install the Sterling Standards Database for SWIFT.
Note: The data dictionary is optionally installed
from the Deployment > Standards page. The SWIFT rule libraries
for 2008 and forward are installed by installing the Sterling Standards Database for SWIFT.
|
| SWIFT Market Practices |
The following two market practices are available in the Sterling B2B Integrator:
- Germany: MT515: Trade Confirmation (Broker to Asset
Manager)
- United States: MT536: ISITC-IOA: Statement of Transactions
You can create a new message type by customizing
a standard SWIFT message type map according to the specifications
of the Market Practice. The customized map can be imported into the
SWIFT Market Practices data dictionary through the SWIFTRuleImporter
utility.
|
- Install the Sterling Standards Database for SWIFT.
The data dictionary is optionally installed
from the Deployment > Standards page. The SWIFT rule libraries
for 2008 and forward are installed by installing the Sterling Standards Database for SWIFT.
- You can create a new message type by implementing
the additional restrictions related to the desired Market Practice.
|
| Services |
- Generic Envelope service envelopes SWIFT messages.
Note: The Generic envelope service assumes that
SWIFT expects a starting CRLF (carriage return/line feed) but not
an ending CRLF.
- Generic Deenvelope service deenvelopes SWIFT messages.
Note: The Generic Deenvelope service assumes
that SWIFT expects a starting CRLF (carriage return/line feed) but
not an ending CRLF.
- EDI Deenvelope service accepts SWIFT messages.
- SWIFTNet Server Adapter (for SWIFT version 6.x
only).
- SWIFTNet Client Service (for SWIFT version 6.x
only).
- SWIFTNet Reconciliation Service.
- SWIFTNet HTTP Server Adapter ((preconfigured instance
for SWIFT version 6.x only)
- SWIFTNet7 Adapter (for SWIFTNet 7 only).
- SWIFTNet7 Adapter Scheduler (for SWIFTNet 7 only).
- SWIFTNet7 Client Service (for SWIFTNet 7 only).
- SWIFTNet7 Server Service (for SWIFTNet 7 only).
- SWIFTNet 7 RMA Service (for SWIFTNet 7 only).
- SWIFTNet7 ASP Service (for SWIFTNet 7 only).
- SWIFTNet7 HTTP Server Adapter (preconfigured instance for SWIFTNet
7).
- SWIFTNet7 HTTP Client Adapter (preconfigured instance for SWIFTNet
7).
- SWIFTNet7 File System Adapter (preconfigured instance for SWIFTNet
7).
- An application, SWIFTNet MEFG Server, supports FileAct and InterAct
processing for SWIFT version 6.x, as well as failover processing.
- An application, SWIFTNet7 MEFG Server, supports FileAct and InterAct
processing for SWIFT version 7, as well as failover processing.
|
- Install the SWIFTNet MEFG Server on a machine running
either the Sun Solaris 5.10, Windows Server
2003 (Standard or Enterprise Edition), or AIX® 5.3 operating system.
- For SWIFT version 7, install the MEFGCommServer7 and MEFGSWIFTNetServer7
on a machine running either the Sun Solaris 10, Windows 2008, or AIX 6.1operating system.
- For SWIFT version 6.x, configure the SWIFTNet Client Service.
- Configure the SWIFTNet Server adapter (for SWIFT version 6.x),
or the SWIFTNet7 Adapter and SWIFTNet Adapter Scheduler (for SWIFT
version 7).
|
| Envelopes |
- Inbound SWIFT envelope wizard to implement inbound
SWIFT messages.
- Outbound SWIFT envelope wizard to implement outbound
SWIFT messages.
- The SWIFT_FINMessageTypes code list is automatically
installed with the Sterling B2B Integrator. This
code list contains a list of valid message types.
- Deenvelope functionality supports SWIFT system
messages and user-to-user messages.
|
- Create the appropriate SWIFT envelopes for each
message type you are sending and receiving.
- You need to populate four code lists to use in
conjunction with the SWIFT_FINMessageTypes code list to perform SWIFT
validations.
- Configure the EDI Encoder service for use with
the outbound SWIFT messages.
|
| Predefined business processes |
- SWIFTDeenvelope business process
- SWIFTEnvelope business process
- SWIFTNetClient business process
- SWIFTNetClientFA business process
- handleSWIFTNetServerSnFRequest
- handleSWIFTNetInboundCorrelation
- handleSWIFTNetOutboundCorrelation
- handleSWIFTNetServerFADelNotif
- handleSWIFTNetServerFAEvent
- handleSWIFTNetServerFARequest
- handleSWIFTNetServerFASnFDelNotif
- handleSWIFTNetServerFASnFRequest
- handleSWIFTNetServerRequest
- handleSWIFTNetServerSnFDelNotif
- handleSWIFTNetServerFASnFEvent
- handleSWIFTNetSnFInboundCorrelation
- handleSWIFTNetSnFOutboundCorrelation
- SWIFTMessageEntryOutbound
- handleSWIFTNetOpenInputChannel
- SWIFTNetOpenInputChannel
- SWIFTMessageEntryOutbound
- SWIFTNet3rdPartyClientForceRefusal
- SWIFTNet3rdPartyClientNotification
- SWIFTNetClientRenewSecContext
- SWIFTNetClientResend
- SWIFTNetCloseInputChannel
- SWIFTNetCreateInputChannel
- SWIFTNetDeleteInputChannel
- SWIFTNet7WaitRequest
- SWIFTNet7CloseInputChannel
- SWIFTNet7CloseOutputChannel
- SWIFTNet7CreateInputChannel
- SWIFTNet7CreateOutputChannel
- SWIFTNet7DeleteInputChannel
- SWIFTNet7DeleteOutputChannel
- SWIFTNet7FileActFetch
- SWIFTNet7FileActNotification
- SWIFTNet7ImportASP
- SWIFTNet7ImportRMA
- SWIFTNet7OpenInputChannel
- SWIFTNet7OpenOutputChannel
- SWIFTNet7QueryReplication
- SWIFTNet7RenewSecContext
- SWIFTNet7ThirdPartyForceRefusal
- handleSWIFTNet7ContextReport
- handleSWIFTNet7Events
- handleSWIFTNet7FileActDelNotif
- handleSWIFTNet7FileActEvent
- handleSWIFTNet7FileActRequest
- handleSWIFTNet7FileActSnFRequest
- handleSWIFTNet7InterActRequest
- handleSWIFTNet7InterActSnFRequest
- handleSWIFTNet7OpenChannels
- handleSWIFTNet7ResponseInfo
- handleSWIFTNet7SnFDelNotif
- Schedule_SWIFTNet7AdapterScheduler
- SWIFTNet7AbortTransfer
- SWIFTNet7Client
- SWIFTNet7ClientResend
|
The business processes that are related to the SWIFTNet workflow
must have the Document Tracking option enabled when you check in or
edit the business process. Additionally, you need to configure other
parameters in the SWIFTNetClient or SWIFTNet7Client business process
to support SWIFTNet. |
| Sterling B2B Integrator
Map Editor |
- Sterling B2B Integrator
Map Editor wizard
enables you to generate a file layout using the MT or MX message that
you select. Included in the SWIFT map are groups, records, composites,
and fields that are defined by SWIFT.
- Properties dialog boxes that enable you to define
and modify SWIFT map components.
- Autolink function automatically creates links between
input and output fields that have the same name or business name.
This function can be used with any data format.
- Extended Rules Library function (used with SWIFT
and any other data format) contains a list of rules in a separate
file outside of the Sterling B2B Integrator
Map Editor source. Sterling B2B Integrator
Map Editor stores
the name of the library in its source file, so when you load a map
the library is also loaded and compiled. This enables you to create
a library of extended rules and then add it to any other map, so you
do not have to recreate those extended rules after the first time.
- Extended rules are used to validate SWIFT messages.
- SWIFT MX validations are performed and generated
maps define the parameters used to look up validations that are defined
in a properties file.
|
- Download Sterling B2B Integrator
Map Editor.
- Create a map or maps to translate your SWIFT messages.
- Place custom extended rule code inside a validation
block.
|
| Extended Rule Libraries |
The extended rule libraries that are loaded automatically when
you download SWIFT and SWIFTNet Financial Services XML standards are:
- SWIFT_2002.erl
- SWIFT_2005.erl
- SWIFT_2006.erl
- SWIFT_2007.erl
- SWIFT_2008.erl
- SWIFT_2009.erl
- SWIFT_2010.erl
- SWIFTMX_ v1-0.erl
- SWIFTMX_BulkPayments_v2-0.erl
- SWIFTMX_CashManagement_v4-0.erl
- SWIFTMX_CashReporting_v1-0.erl
- SWIFTMX_CashReporting_v3-0.erl
- SWIFTMX_CashReporting_v3-1.erl
- SWIFTMX_CashReporting_v3-2.erl
- SWIFTMX_CashReporting_v4-0.erl
- SWIFTMX_CashReporting_v5-0.erl
- SWIFTMX_EI_v1-0.erl
- SWIFTMX_EI_v1-1.erl
- SWIFTMX_EI_v1-2.erl
- SWIFTMX_e-Mandate_v1-0.erl
- SWIFTMX_FpML_v1-0.erl
- SWIFTMX_Funds_v2-0.erl
- SWIFTMX_Funds_v2-1.erl
- SWIFTMX_Funds_v2-2.erl
- SWIFTMX_Funds_v3-0.erl
- SWIFTMX_Funds_v3-1.erl
- SWIFTMX_Funds_v4-0.erl
- SWIFTMX_Funds_v4-1.erl
- SWIFTMX_Funds_v4-2.erl
- SWIFTMX_ProxyVoting_v1-0.erl
- SWIFTMX_ProxyVoting_v1-1.erl
- SWIFTMX_ProxyVoting_v1-2.erl
- SWIFTMX_SCORE_v2-0.erl
- SWIFTMX_TradeServices_v1-0.erl
- SWIFTMX_TradeServices_v2-0.erl
- SWIFTMX_TransactionReporting_v1-0.erl
|
None |
| SWIFTNet Correlations |
- Enables you to search for SWIFTNet messages using
specific criteria.
|
- Run inbound and outbound data and then use the
search interface to search for messages.
- If you are upgrading from a previous version to
the IBM Sterling
Standards Library Version
5.3, you must run the SwnetCorrMigrate.cmd script to migrate
correlation detail records to new database tables.
|
| Document Tracking |
- Support for monitoring SWIFTNet data flows.
- Support for tracking SWIFTNet messages within the Sterling B2B Integrator. The tracking
and correlation functionality automatically tracks the SWIFTNet messages
the same manner as the other standards are tracked.
- Support for document repair and resend.
|
- Use the data flow interface to track inbound and
outbound SWIFTNet processes.
- All the business processes that are related to
the SWIFTNet workflow (SWIFTNetClient, handleSWIFTNetServerRequest,
and handleSWIFTNetServerSnfRequest) must have the Document Tracking
option enabled when you check in or edit the business processes.
- Access messages with Ready To Edit status, repair,
and resend them.
|
| SWIFTNet Routing Rule |
- Interface to support creation, modification, and
deletion of SWIFTNet routing rules for SWIFT version 6.x and 7.
- The criteria specified in the SWIFTNet Routing
Rule enables a user to set a specific business process to process
the incoming request from SWIFTNet (for version 6.x). For SWIFTNet
version 7, it allows you to select the action associated with the
routing rule (including specifying a business process, store it into
the mailbox, or store it into the file system).
- You can also use wildcards in the SWIFTNet routing
rule.
|
- Create a business process or modify the SWIFTNetClient
or SWIFTNet7Client business process.
- Create a SWIFTNet routing rule that is linked to
the business process you created.
|
| SWIFTNet Service Profile |
For SWIFTNet version 6.x, enables you to associate SWIFTNet
Request Type with a Schema for Header Validation.
Note: With
the introduction of the Application Service Profile (ASP) in SWIFTNet
7.0, this feature is no longer required.
|
- For SWIFTNet version 6.x, create a new SWIFTNet
Service Profile (not needed for SWIFTNet version 7.0).
|
| SWIFTNet Copy Service Profile |
Enables you, as a third party, to specify the relationship
between a Service Name and Copy Mode (T or Y Copy).
Note: If
the useASP flag is set to TRUE, this feature is not used.
|
- For SWIFTNet version 6.x, create a SWIFTNet Copy
Service Profile if you are using T or Y Copy.
|
| SWIFTNet Client Profile |
SWIFTNet Client Profile Enables you, as a
requestor, to send a request using an ASP-driven wizard. This minimizes
the occurrence of unnecessary errors when sending a request.
|
Create a SWIFTNet Client Profile if you are
using SWIFT version 7.
|
| SWIFT Message Editor |
- Interface to enable a user to correct a SWIFT MT
or MX message that was returned due to an error either in transmission
or translation.
- Support for validating messages.
|
- Assign permissions for two different roles: the
Editor and the Reviewer and give appropriate permission sets to each
role.
- Correct appropriate messages and notify the appropriate
user that activity is required.
- Review change history for messages.
|
| SWIFT Message Entry Workstation |
Interface to enable manual message entry using a structured
message editor. |
- Assign permissions for the three different roles
(Creator, Verifier, Tracker).
- Create, verify, view (read-only), and track new
SWIFT messages created through this interface.
|
| Input Channel |
The SWIFTNet 6.1 release introduces the concept of an input
channel. Currently, the Sterling B2B Integrator only supports
the use of input channel for InterAct messages in store-and-forward
(SnF) mode. An input channel can be used by the messaging interface
to establish an input session with SWIFT. The input session starts
when the messaging interface opens the input channel and ends when
the messaging interface closes the input channel. The input channel
also supports sender-to-receiver first-in-first-out (FIFO), which
means that each message is delivered only one time and minimizes the
number of possible duplicates. |
You must configure the following three application components
to use the input channel:
- SWIFTNet Server Adapter or SWIFTNet7 Adapter
- Resend Scheduler (SWIFT 6.x only)
- SWIFTNet Client Service or SWIFTNet7 Client Service
(including configuring a predefined business process to create a new
input channel)
|
| Output Channel |
The SWIFTNet 7.0 release introduces output
channels and queue sharing. In previous versions, a queue could not
be shared by different messaging interfaces at the same time because
SWIFT only allowed one queue session to be opened at one time.
By
introducing the output channel in version 7.0, SWIFT allows queue
sharing by enabling a queue to use different output channels and the
interface to open several output channels on the same queue at the
same time.
|
You must configure the following application
components to use the input channel:
|
| SWIFTNet Monitor |
Displays the status of the SWIFTNet queues and channels, including
the input channel. |
View the SWIFTNet Monitor. |