Release 7.6
Alliance and SwiftNet Release 7.6 – Reaching end of life
Release 7.6
Overview
Alliance and SwiftNet Release 7.6 was a mandatory pre-requirement for using the Alliance product stack together with CBPR+. Release 7.6 is now in the migration phase and will reach end-of-support on 31 March 2025 for RHEL and Windows and 30 June 2025 for AIX.
It is necessary for to upgrade to release 7.7 or 7.8, to remain compliant with the Customer Security Control Framework and to successfully reach the end of the CBPR+ migration end November 2025.
To help you plan for CBPR+, you can find more details in the dedicated Swift Smart FINplus, CBPR+ and Multi-Format MX messages in Alliance Access/Entry curriculum, and in the product documentation on the User Handbook Online.
To help you transition to Release 7.7 or 7.8, Swift also provides a range of service offerings that includes Consultancy, Training and Operational services. For more information on these offerings, please consult the Services section or contact your Swift Account Manager.
Hardware reference for release 7.6
This information presents the hardware reference needed to use Swift applications efficiently and achieve the required performance. If you are running third-party applications (Application Monitoring tools, Antivirus, IBM MQ server, etc.) on the same server, we advise you to monitor actual CPU load and memory consumption to confirm that your systems are still adequately sized. Recently acquired systems on which you installed Release 7.5 release are most likely still adequate.
For the disk space requirements, please refer to the Installation guide of the product.
NOTE 1
The hardware reference does not indicate the minimum level of hardware required to run Release 7.6. An equivalent system based on older architecture can be used as long as it meets the minimum OS baseline requirement.
NOTE 2
A “core” represents a single physical core of a multi-core CPU. When virtualizing, one Virtual Processor should be seen as the equivalent of one physical core.
System
Running Alliance Access on a dedicated system
If you are running Alliance Access on a dedicated system, then use the following system configuration as a reference.
| Up to 40 TPS | IBM Power System | Intel Xeon or Core, AMD Epyc or Ryzen (Linux) | Intel Xeon or Core, AMD Epyc or Ryzen (Windows) |
| Processor type | POWER 10 | Intel Xeon E5 family or more recent | Intel Xeon E5 family or more recent |
| Number of Core(s) | 8 | 16 | 16 |
| RAM | 16 GB | 16 GB | 16 GB |
| Up to 20 TPS | IBM Power System | Intel Xeon or Core, AMD Epyc or Ryzen (Linux) | Intel Xeon or Core, AMD Epyc or Ryzen (Windows) |
| Processor type | POWER 10 | Intel Xeon E5 family or more recent | Intel Xeon E5 family or more recent |
| Number of Core(s) | 8 | 16 | 16 |
| RAM | 16 GB | 16 GB | 16 GB |
| Up to 10 TPS | IBM Power System | Intel Xeon or Core, AMD Epyc or Ryzen (Linux) |
Intel Xeon or Core, AMD Epyc or Ryzen (Windows) |
| Processor type | POWER 10 | Intel Xeon E5 family or more recent | Intel Xeon E5 family or more recent |
| Number of Core(s) | 4 | 8 | 8 |
| RAM | 16 GB | 16 GB | 16 GB |
| Up to 5 TPS | IBM Power System | Intel Xeon or Core, AMD Epyc or Ryzen (Linux) |
Intel Xeon or Core, AMD Epyc or Ryzen (Windows) |
| Processor type | POWER 10 | Intel Xeon E5 family or more recent | Intel Xeon E5 family or more recent |
| Number of Core(s) | 4 | 8 | 8 |
| RAM | 16 GB | 16 GB | 16 GB |
Important notes:
The Above specifications are independent of the actual type of messages processed (MT vs MX vs multi-format MX)
The above specifications for 40 TPS and 20 TPS are a good indication for what is considered as a system used in "pipe" mode (that is, limited event logging, simple routing, etc.) and tuned for high performance. Your Alliance Access system will require more resources, for example, when you have very complex routing, hundreds of operators, many simultaneous message searches, reporting activities, or are intensively using the Integration Platform.
Indications for 10 TPS and 5 TPS are given for an untuned system, using a default system configuration.
For higher throughput configurations (for example, more than 40 TPS or more than 1 million messages per day), we recommend that you contact Swift for a review of your system capacity. Contact your account manager for more information.
Running SwiftNet Link and Alliance Gateway on a dedicated system
If you are running SwiftNet Link and Alliance Gateway on a dedicated system, then use the following system configuration as a reference.
| Up to 40 TPS | IBM Power System | Intel Xeon or Core, AMD Epyc or Ryzen (Linux) |
Intel Xeon or Core, AMD Epyc or Ryzen (Windows) |
| Processor type | POWER 10 | Intel Xeon E5 family or more recent | Intel Xeon E5 family or more recent |
| Number of Core(s) | 4 | 4 | 4 |
| RAM | 16 GB | 16 GB | 16 GB |
| Up to 5 TPS | IBM Power System | Intel Xeon or Core, AMD Epyc or Ryzen (Linux) |
Intel Xeon or Core, AMD Epyc or Ryzen (Windows) |
| Processor type | POWER 10 | Intel Xeon E5 family or more recent | Intel Xeon E5 family or more recent |
| Number of Core(s) | 2 | 2 | 2 |
| RAM | 16 GB | 16 GB | 16 GB |
| Up to 1 TPS | IBM Power System | Intel Xeon or Core, AMD Epyc or Ryzen (Linux) |
Intel Xeon or Core, AMD Epyc or Ryzen (Windows) |
| Processor type | POWER 10 | Intel Xeon E5 family or more recent | Intel Xeon E5 family or more recent |
| Number of Core(s) | 2 | 2 | 2 |
| RAM | 16 GB | 16 GB | 16 GB |
Important notes:
Contact Swift if you plan to do more than 40 TPS.
Running Alliance Web Platform on a dedicated system
If you are running Alliance Web Platform on a dedicated system, then the following minimum recommendations apply.
| Up to 250 concurrent users | IBM Power System | Intel Xeon or Core, AMD Epyc or Ryzen (Linux) |
Intel Xeon or Core, AMD Epyc or Ryzen (Windows) |
| Processor type | POWER 10 | Intel Xeon E5 family or more recent | Intel Xeon E5 family or more recent |
| Number of Core(s) | 3 | 4 | 4 |
| RAM | 16 GB | 16 GB | 16 GB |
| Up to 100 concurrent users | IBM Power System | Intel Xeon or Core, AMD Epyc or Ryzen (Linux) |
Intel Xeon or Core, AMD Epyc or Ryzen (Windows) |
| Processor type | POWER 10 | Intel Xeon E5 family or more recent | Intel Xeon E5 family or more recent |
| Number of Core(s) | 2 | 4 | 4 |
| RAM | 16 GB | 16 GB | 16 GB |
Important notes:
A four core system should be sufficient to operate Alliance Web Platform with 250 operators connected. However, the overall performance might depend on the nature of the operations made simultaneously by those operators, as certain operations are more CPU intensive than others. It is therefore highly recommended to test the configuration under typically business conditions before deploying the solution in the production environment.
Running multiple Alliance software on the same system
If you plan to have software for two or more Alliance products running on the same system with less than 5 TPS and less than 100 concurrent users, then use the following system configuration as a reference.
Note: running SNL/Gateway and Access or Entry on the same systems will require specific configuration to meet the CSCF control criteria.
| Up to 5 TPS and up to 100 concurrent users |
IBM Power System | Intel Xeon or Core, AMD Epyc or Ryzen (Linux) |
Intel Xeon or Core, AMD Epyc or Ryzen (Windows) |
| Processor type | POWER 10 | Intel Xeon E5 family or more recent | Intel Xeon E5 family or more recent |
| Number of Core(s) | 6 | 12 | 12 |
| RAM | 32 GB | 32 GB | 32 GB |