SoftLink's technologies provide a centralized solution for interfacing with external clients, file distribution and automatic forwarding. SoftLink’s customizable solution allows banks to deploy unique file transfer and processing scenarios on a wide range of platforms, using any type of transfer method. SoftLink's robust FEST technology combined with FASTCopy’s superior file transfer protocol, provides an unrivalled solution for banking transfer needs.
The basic goals and requirements of the bank are illustrated by the following distribution scenarios.
Scenario 1: Salary Upload from Client.
Scenario 2: Distribution of Mainframe Oriented Files.
Scenario 3: Internal Distribution of Common Rates/Tables.
Scenario 4: Distribution to External Partners/Entities.
Platforms involved:
§ Mainframe at the bank's headquarters
§ SUN servers at the bank's headquarters
§ HP-UX servers used by the bank clients
§ Linux workstations used by the bank clients
§ Windows NT/2000 servers (300 at the branches and 100 at the Bank's IT center, excluding the bank's clients)
§ Windows NT/2000 workstations at 5,500 tellers and workstations
Security requirements:
§ All files must be verified for appropriate digital signature prior to distribution
§ All files must be encrypted during broadcast
§ All connections must be authenticated
File transfer Protocols used:
§ FASTCopy
§ Standard
§ SFTP
§ SSH
§ Resident proprietary protocols (besides FASTCopy)
FEST Central Server installed on:
1. The bank's DMZ server
2. The bank's internal LAN
3. Branch servers
FEST SAT Plus installed on:
1. All of the bank's workstations
2. FEST Central Servers
§ Stage 1: An external client sends salary payment instructions to the bank.
§ Stage 2: The bank sends an acknowledgment to the client that it has received the instructions.
§ Stage 3: The files are delivered to the bank's mainframe for processing.
The bank's client uploads files to a pre-configured "hot" directory residing on the bank's FEST Central server, which is located in the DMZ. FASTCopy Server may, on request, be installed on the bank's FEST Central server, providing easy to use, secure and guaranteed upload (FASTCopy Server provides unlimited free clients).
1. After delivery to the "hot" directory, the files are saved locally in a temporary directory that is inaccessible to the clients.
2. Simultaneously, after the file is successfully uploaded, the following acknowledgements are sent:
o An acknowledgement is sent to the client.
o A notification is sent to the system administrator informing him/her of the file's temporary location.
1. The system administrator pulls the files into a "hot" directory on the FEST Central server located on the LAN. If the security policy permits, the DMZ FEST may push the files to the LAN FEST Server.
2. After delivery to the "hot" directory, the files are processed for preparation or converted to meet the mainframe's requirements.
3. When local processing is concluded, the file is pushed to the mainframe. The delivery method of the file may be by FTP, FASTCopy or any existing file transfer protocol used by the bank.
Processed products from the mainframe are converted to a suitable format and distributed to all branches.
Files are uploaded from the mainframe to a "hot" directory on the FEST Central Server. The files are uploaded using FEST Super SAT, Standard FTP or any other file transfer protocol. If the files arrive with CRC, FEST verifies their integrity.
1. After verification, the files are moved to a temporary directory and converted to the proper format, using a converter that must reside on the same machine.
2. When conversion is complete, the files are copied to a different "hot" directory.
1. After delivery to the "hot" directory, the files are verified again to make sure that the conversion was successful and that other pre-configured parameters were verified.
2. After verification, the files are distributed to the branches.
|
Note: |
A Large organization can set up a distribution tree wherein FEST is installed at the IT department and at each of the organization’s branches. In such a setup, FEST Satellites are installed at the final target nodes (i.e. the tellers). This way, the files would be automatically cascaded from the IT department to the end-nodes (the tellers, etc.). |
§ Stage 1: The National bank distributes updated interest rate sheets to banks across the country.
§ Stage 2: The interest rate sheets are converted to each bank’s particular format and distributed to all the tellers at that bank.
§ Stage 3: The updated interest sheets only become available (for download) after they have been received by all the banks on the National bank’s distribution list.
1. The National bank uploads interest rates files to a "hot" directory residing on the recipient bank’s FEST server.
2. Upon verification and qualification, the files are copied to a "hot" directory residing on the recipient bank’s internal FEST Server.
3. Optionally:
i. Files can be uploaded using FEST Super SAT.
ii. Install FASTCopy Server on the recipient bank’s FEST Server machine, thus providing any organization with the ability to securely transfer files to the bank using FASTCopy free client. FASTCopy Server may be used as a general external solution.
1. After arriving to the "hot" directory, the files are copied to a temporary processing folder.
2. A local process is activated on the files changing the interest rate sheet into a format suitable for that specific bank.
3. After processing, the files are placed in a distribution "hot" directory.
¨ Files placed in the distribution "hot" directory are distributed to all relevant nodes.
§ Stage 1: Files containing foreign exchange transactions are distributed to partner banks.
§ Stage 2: An e-mail notification is sent to the administrator in each of the recipient partner banks.
1. Files containing end-of-day foreign exchange transactions in US dollars are copied to a FEST "hot" directory.
2.
Upon arrival of a trigger file or by a certain time, FEST Server in
the DMZ distributes the files in order of priority to the relevant partner bank
in the
|
Note: |
FEST Satellite should be installed on the receiving node. |
¨ If the file transfer is successful, an e-mail notification is sent to the partner bank administrator, informing him/her of the new transaction arrival and its location. Optionally, an e-mail notification is also sent to the main bank’s administrator.