How does Automation Broker Work?

OpenSpan Automation Broker leverages the service enablement capabilities of OpenSpan Desktop Automation to expose functionality from existing applications as web services. OpenSpan Automation Broker then allows these applications to be moved off the desktop and managed in a "headless" mode - i.e. without the requirement for a user to interact with the applications. OpenSpan Automation Broker manages the services and assigns work to "Worker Instances". A Worker Instance is a Virtual Machine which includes a copy of:

• A Windows Operating System
• OpenSpan Automation Runtime
• A messaging client (e.g. Microsoft MQ, JMS, MQ-Series)
• Each of the applications to be automated

For scalability, any number of Worker Instances may be employed. Typical deployments leverage virtualization (VMware, Citrix Xen, Microsoft Virtual PC, etc…) and the Worker Instances are managed by the Automation Broker via enterprise messaging (JMS, IBM MQ-Series, Microsoft MQ, etc.).

The required functionality is then exposed to other applications via OpenSpan Proxy Objects, which can be accessed in any Java or .NET Application Server environment, including:

• IBM WebSphere
• Oracle WebLogic
• SAP NetWeaver
• JBoss AS
• Microsoft Application Server

Want to try out service-enabling applications for yourself? Visit the OpenSpan Community Website at http://www.openspan.com/community for details.