This type of configuration is used for on-line Subscription Services and Electronic Commerce applications where management of enterprise data requires dedicated functionality to be assigned to specific servers. This system supports remote data processing, subscriptions and access to the data over the web, batch processsing of customised emails and system maintenance activities.
How it works
In the configuration shown there are three instances of WebPublisher Studio sharing a single IP with each instance assigned to different ports. Each server instance is allocated to a specific web service such as HTTP, Thick Client, SMTP Batch Processing etc. This use of WebPublisher Studio allows data to be delivered to several classes of end user - remote data entry personnel, web browser clients, and email clients. We use a similar configuration in the Indotender application we developed for a customer.
Description
Each instance delivers an execution thread that can socket connections and process asynchronous requests. Up to 24 instances can be configured in a cluster - each instance requires an Omnis Studio runtime to operate. In this example all instances share cached data in the WebPublisher Studio server data repository.
- Instance 1 (Port 1080) - Processes WebPublisher Studio Thick Client requests entering enterprise data.
- Instance 2 (Port 80) - Handles HTML web requests for login sessions and access to user account data.
- Instance 3 (Port 1081) - Batch processing activities including compiling email reports to users, archiving transactions, updating subscriptions etc.