If you are installingSterling B2B Integratorby using the IBM Installation Manager, you must consider additional system requirements.
- IBM Installation Manager
- Java Requirements
- Virtualization support
IBM Installation Manager
Installation Manager is used to installSterling B2B Integrator.
IBM Installation Manager V1.8.8 is included with Sterling B2B Integrator.
For information about how the Installation Manager is used to install Sterling B2B Integrator, see the installation documentation atThe IBM Installation Manager (IIM).
For more information about the Installation Manager, seehttps://www.ibm.com/support/knowledgecenter/SSDV2W/im_family_welcome.html.
Minimum hardware requirement on IIM
The minimum hardware size published onSoftware Product Compatibility Reportsis based on the defined use case for AS2 Inbound/Outbound file transfer with 10KB and 5MB payload sizes. For 10KB payload size the target throughput is 600 docs/min and for 5MB payload size the target throughput is 50 docs/min.
In case of AS2 Inbound, the transferred payload is already encrypted, compressed and signed. Once the payload reaches the B2Bi server, it gets decrypted, verified, de-compressed and the MDN gets triggered back to the sender.
In case of AS2 Outbound, the payload gets encrypted, compressed, and signed and then it is transferred to the receiver. Once the payload reaches the receiver, it gets decrypted, verified, de-compressed and the MDN gets triggered back to the sender.
Java requirements
Java software required for installingIBM® Sterling B2B Integratoris included with the download or media.
Java (All platforms)
Consider the following points for the Java software that is required.
- The required 64-bit JDK files for Windows, AIX®, and Linux® platforms are provided with the product download or media.
- Determine the correct JDK or JRE for your installation ofSterling B2B Integratorbased on the detailed system requirements.
- For other IBM Java software, refer toIBM developerWorks®.
JCE requirements (All platforms)
The IBM Unrestricted SDK JCE policy files are required for all platforms supported bySterling B2B Integrator.
The IBM Unrestricted SDK JCE policy files can be downloaded athttp://www.ibm.com/marketing/iwm/iwm/web/preLogin.do?source=jcesdk.
Map Editor Java requirements
To ensure the Map Editor runs properly on your Windows client system, be sure your system meets the Java requirements.
- The IBM JDK and JRE for Windows are available only as part of an IBM product. The 32-bit java files can be obtained fromFix Central.
- To save your source map as an XML file (.mxlfile extension) using the Map Editor, you must have Microsoft XML Core Services (MSXML) 4.0 installed on the same computer as Map Editor. If you do not have Microsoft XML Core Services (MSXML) 4.0 installed, you cannot save source maps as .mxlfiles and must use the .mapextension.
Virtualization support
Sterling B2B Integratorsupports Virtualization on many systems.
Performance Considerations for RISC and x86/x64 architectures
While employing virtualization is common in environments, for performance reasons, it is expected in sizing practices provided by IBM or otherwise that the architecture utilizes dedicated resources for CPU, memory and I/O devices such as disks, network, and so on.
This ensures thatSterling B2B Integratorreceives consistent access to the resources required to run the application. Those resources should not be shared (or over-shared) in a VM environment.
Virtualization support for RISC-based systems
Operating system native clustering, partitioning, or virtualization are supported for all RISC-based platforms thatSterling B2B Integratorsupports.
| Platform | Details |
|---|---|
| AIX® on P5 and above |
|
Virtualization support for x86/x64-based systems
IBM cannot maintain all possible combinations of virtualized platforms. However, IBM generally supports all enterprise class virtualization mechanisms, such as VMware ESX, VMware ESXi, VMware vSphere, Citrix Xen Hypervisor, KVM (Kernel-based virtual machine), and Microsoft Hyper-V Server.
Additional Considerations for RISC and x86/x64 architectures
IBM investigates and troubleshoots a problem until it is determined that the problem is due to virtualization. The following guidelines apply:
- If we suspect that a specific issue is happening because the system is virtualized and we cannot reproduce the problem in our non-virtualized environment, we will request that you demonstrate the issue to us in a live meeting session. IBM may also require that further troubleshooting be done jointly on your test environment, as we do not have all types and versions of VM software installed in-house.
- If we are unable to reproduce the issue in-house in a non-virtualized environment and troubleshooting together on your environment indicates that the issue is with the VM software itself, we will request that you open a Support ticket with the VM software provider. IBM can meet with the provider and you to share any information we have which would help the provider further troubleshoot the issue on your behalf.
- If you choose to use virtualization, you must balance the virtualization benefits against its performance impacts. IBM does not provide advice regarding configuring, administering, or tuning virtualization platforms.
