Sterling Integrator Client Components – What Are They?

Having worked in EDI for over 18 years, you get to see the same architecture over and over.  One particular architecture I have become very familiar with is the Sterling Integrator client components.

Protocols such as FTP, SFTP, HTTP, C:D are all divided into suite adapters that can be used to create a client that then connects to the trading partner and transfer the document,enforcing any security specifications from the business process.

Client components for B2B in GIS include FTP, SFTP, HTTP, JMS, MQ, SMTP, POP3, SOAP, C:D, C:E.

Scenarios in which GIS can act as a client,by using any of above mentioned protocols looks like as follows:

si-diagram

Sterling Integrator server components

Server components for B2B in GIS are FTP, SFTP, HTTP, WS – HTTP over SOAP, C:D Server Adapters

FTP Server Adapter in GIS/SI

  • FTP Server is tightly integrated with the Application mailbox system. An FTP client can only access the mailbox that is assigned to its user account.
  • This adapter receives and processes requests from external trading partners that are submitted using the FTP protocol. This adapter is used with a Application Perimeter server.
  • Use this adapter to put files into a Application mailbox or get files from a Application mailbox.
  • mailbox activities can trigger routing rules

SFTP Server Adapter in GIS/SI

  • Uses Mailbox subsystem as its repository (virtual roots)
  • Receives and processes requests from external trading partners that are submitted through the SFTP protocol or SCP protocol
  • Use this adapter to enable external SFTP clients or SCP clients to put files into a Application Mailbox or get files from a Application Mailbox.
  • Routing rules for items placed in Mailbox can be used to trigger a business process

CD Server Adapter

  • This adapter receives and processes requests from remote Connect:Direct nodes.
  • Mediate requests originating from a business process and going to an external trading partner using a (non-application) Connect:Direct node or another Connect:Direct Server adapter.
  • Accept requests from a Connect:Direct node (or another Connect:Direct Server adapter) to copy to or from a mailbox or business process
  • Forward requests from one remote Connect:Direct node to another

HTTP Server Adapter

  • Use this adapter to send documents to and receive documents from a trading partner using HTTP
  • Uses Perimeter services
  • Uses the same Jetty HTTP server engine as the GIS ASI console
  • Able to run both WARs and BPML applications
  • Runs application code inside the Application JVM for access to all Application resources
  • Handles SOAP requests as well

Scenarios in which GIS can act as a server, by using any of above mentioned protocols looks like as follows:

si-diagram-2

Leave Comment

Your email address will not be published. Required fields are marked *