The Bolero WebGateway is an extension of the Bolero hosted service which is designed to ensure ease of integration and interoperability between a bank’s (or corporate’s) back office systems and Bolero. It is entirely configurable to ensure that this can be mapped onto specific needs for each customer. In addition each customer may utilise multiple configuration of the gateway for different aspects of use of Bolero and for different geographies or divisions, providing maximum flexibility to interoperate at local and channel levels.
The principal objectives of the Bolero WebGateway are:
- Standardised Interface environment to enable plug and play with minimal effort
- Enable full automation between Bank back office and Bolero
- Configurable at lowest level of use (division/channel/geography)
- Automatic Mapping from Industry Standards (SWIFT, DTA), Bolero Standards (BoleroXML, SWIFT++) and easily configurable for automated mapping to other structured (application of customer specific) formats.
- Provide robust message control and administration capabilities for audit, replay, monitoring etc.
- Preserve Auditability, Security, Non-repudiation and Compliance
The Bolero Gateway Components
The Bolero WebGateway is a fully packaged service designed to be configured by the user (user layer) and Bolero (service layer). At the service layer Bolero can configure the use of the Gateway to meet the requirements of each user (company, department, end user) including the configuration of the Bolero Connectors (Translators), packaging of messages, and transport (communications) options.
Core Components of the Bolero WebGateway:
- Bolero Connectors – provide automatic translation to and from any specified standard or proprietary structured message format into BoleroXML.
- Monitor tools allow views of all messages sent and received through the WebGateway, together with administration and control functions to manage Pending Activities, Repair Queue and Recovery.
- Security – Management of keys, certificates and user accounts.
- Packaging – determines and packages the message into specified packaging format (e.g. zip)
- Communications Layer – provides access to secure FTP servers, dedicated service capabilities determined by some individual banks and local disc storage for simple upload and download.