Protocol adapters are external interfaces that connect users to applications. Each protocol adapter functions as a Windows service that appears in the services control panel applet. Each protocol adapter can exist outside of the application and can be started and stopped independently of the rest of the system.

The server side consists of your application and the protocol adaptors. Each specific protocol adapter transforms a particular protocol according to the requirements of the business segment class. The actions of the application do not affect the functionality of protocol adapters.

The following protocol adapters are available:

SOAP over HTTP (Web Services)

Simple Object Access Protocol (SOAP) is an area in XML development. It has a major role to play in the next generation of Microsoft Visual Studio, and it is the basis of the .NET strategy.

SOAP over MSMQ

Since SOAP is XML and there is already a protocol adapter that talks SOAP, the obvious solution was to have another protocol adapter that talks SOAP over Microsoft Message Queuing (MSMQ).

HUB

HUB is a proprietary protocol that allows AB Suite systems to talk to each other.

NOF/OFF/USER/GLI

All of these are proprietary protocols that you can use to migrate applications from mainframe hosts (where these protocols were used more heavily) to Windows operating system hosts.

RATL over TCP/IP

This protocol is used by earlier versions of Enterprise Application Component Enabler.

RATL over MSMQ

This is a feature of Enterprise Application Component Enabler.