Integration Server
Integration Server is a run-time server with a browser-based user interface whose primary function in application integrations is to execute services. Integration Server does the following:
1. Receives requests from client applications and authenticates and authorizes the requesting users.
2. Invokes the appropriate services and passes them input data from the requesting clients.
3. Receives output data from the services and returns it to the clients.
Integration Server supports a wide range of established and emerging standards so you can interact with virtually any business partner that is connected to the Internet.
Integration Server supports... | Such as... |
Transport standards | HTTP, HTTPS, FTP, FTPS, SMTP |
Message formats | MIME, S/MIME |
Data standards | XML and XML Schema, custom flat file formats with delimited fixed- or variable-length records, JSON |
Protocols | JMS, Kerberos, OData, OpenID Connect, SFTP, SOAP, SOCKS, XML RPC |
Specifications | Swagger, Web Service Description Language (WSDL) |
Integration patterns | REST, web services, event-driven, request-reply |
Authorization framework | OAuth |
Integration Server hosts packages that contain services and related files, such as specifications, document types, and DSPs. Integration Server comes with many packages, and developers can create their own packages to hold services they create.
Your Integration Server might sit behind an internal firewall and not be allowed to directly interact with external clients through the DMZ. In this case, you can use Enterprise Gateway to allow the Integration Server to process requests from external clients. In an Enterprise Gateway configuration, you place another Integration Server, called an Enterprise Gateway Server, in your DMZ. The Enterprise Gateway Server acts as an intermediary between external clients and the internal Integration Server, protecting the internal Integration Server and its applications, services, and data from malicious attacks.
Contact Support
|
Community
|
Feedback