Environment Architecture
The following diagram illustrates the use and interaction of custom access modules within the WorldServer environment.
Standard clients interact with WorldServer services via the WorldServer UI. However, with the addition of the SDK, the options for interacting with WorldServer have increased. In addition to using the standard WorldServer hosted Web application UI, customers can interact within the WorldServer environment via custom servlets, standard and custom Web services, and external custom access modules.
Note that all external modules must run on the same server as the WorldServer environment. External modules depend on the WorldServer installation. Running on a separate physical server is possible, but it requires an additional installation of WorldServer and an additional license. Client-server interaction between WorldServer and an application or client on a separate server can be facilitated via custom servlets and Web services. While these servlets are uploadable components, they do provide a means for externally accessing WorldServer services and data remotely via HTTP.
Customers can create and upload custom components to extend WorldServer options within the standard WorldServer UI application. Access to core WorldServer services is provided through the SDK API level within the WorldServer environment.