Windows Runtime consists of the following components:
Runtime
Protocol Adapters
Database Server (Remote DB Server)
GUI Server
Client Container
Administration Tool
Windows Runtime supports deployment of components developed in Agile Business Suite and other tools and enables optimum, flexible, and rapid development of runtime solutions.
Windows Runtime runs on .NET Framework Enterprise Services environment and includes a Microsoft Management Console (MMC) snap-in to administer the Runtime. The Administration Tool snap-in to MMC enables you to configure the Runtime environment. Using the Administration Tool, you can deploy systems and perform administration tasks required for deployed systems.
You can use the Runtime Administration Tool to create a test database to test your application using Debugger before you deploy it to a runtime host. It also enables you to configure and manage the runtime environment and deployed AB Suite applications for the Windows operating system.
You can use the Runtime Administration Tool to perform the following:
Add a Runtime Database Server
Add a Database Server Registration
Add a New Database
Prepare an Existing Database
Agile Business Suite Windows runtime supports different protocols and transport layers as follows:
SOAP over HTTP (Web Services)
Simple Object Access Protocol (SOAP) is a protocol that has a predominant role in XML development and Web Services.
SOAP over MSMQ
This protocol adapter provides SOAP over Microsoft Message Queuing (MSMQ).
HUB
HUB is a proprietary protocol that allows Agile Business Suite systems to talk to each other.
NOF/OFF/USER/GLI
All of these are proprietary protocols that are mainly used to migrate applications from mainframe hosts (where these protocols were used more heavily) to Windows operating system hosts.
RATL over TCP/IP
A protocol that is used by Component Enabler.
RATL over MSMQ
A feature of Component Enabler.