Integration with external systems

IBM allows the integration of Sterling™ Order Management System with external systems.

Sterling Order Management System does not support non-secure communication protocols like FTP, SMTP, and the usage of components in the Service Definition Framework that use them. The components within Sterling Order Management System use secure communication. Therefore, the external systems should also set up communication over SSL. For example, the communication between Sterling Order Management System and WebsSphere MQ is over SSL.

Sterling Order Management System does not support the usage of SFTP as an integration utility for file-based integration between applications. IBM supports only a specialized usage of SFTP for inbound transfer of deployment packages, or outbound transfers of output documents from the data extract utility.

Sterling Order Management System does not expose its APIs or Services as Web Services. External systems can invoke the RESTful APIs exposed in Sterling Order Management System. The RESTful API technology is a recommended method of integration and SOAP-based integration is not permitted by IBM.

Sterling Order Management System cannot communicate with external systems by default. An SI must raise a ticket to enable the external IP and expose the required ports so that Sterling Order Management System can communicate with the external system. For more information about requesting for enabling IP addresses, see Information for network firewall policy.

Further, the custom implementation to integrate with an external system should be introduced into Sterling Order Management System through the customization route.

If you want to open certain connections for egress on the firewall, you must create a firewall policy in Self Service. For more information, see Managing firewall policies.