Virtual Broker - Move Applications Off the Desktop

OpenSpan Virtual Broker enables you to deploy solutions as services in a server environment instead of across enterprise desktops. This enables you to very rapidly service-enable legacy applications and move them off of users' desktops altogether.

Virtual Broker:

• Uses an application fabric that supports large grids
• Manages service requests to multiple OpenSpan Integrator instances
• Supports leading Java EE and .NET Platforms

How Virtual Broker works

Each Virtual Broker runtime agent is called a Worker Instance. Worker Instances are grouped in Service Groups, and each Service Group is exposed to a proxy client. If enabled, OpenSpan Studio can produce proxy clients in addition to the normal deployment packages; user desktops communicate with proxy clients and use different queuing schemes to access the virtual instances.

Compatibility

Virtual Broker is compatible with most industry-standard server architectures, including those listed below.

Middleware

Virtual Broker can integrate with virtually any middleware architecture. Proxy Objects can be generated as either .NET or Java classes and installed in any of the application servers listed above, including IBM WebSphere, BEA WebLogic, Oracle AS, JBoss AS, SAP NetWeaver, Microsoft IIS, etc. Developers can also easily extend these environments to integrate with existing ESBs, messaging or other middleware environments.

Read a Virtual Broker data sheet, and to learn more about OpenSpan products and access related information, please see the content menus on the right side of the screen, or Contact Us.