The Development Environment
The WebPublisher Studio development system comprises two separate applications for authoring and publishing web-enabled applications - the Database Server (WebPublisher Studio Server) and the Development Client (WebPublisher Studio Client).

WebPublisher Studio Server is booted using an Omnis Studio Runtime whilst the Development Client is started using an Omnis Studio development (IDE) copy. Application development work is usually done in a staging area on a single machine or across a Local Area Network. The final Plug-in resource libraries and data file are then copied into the production area and put on-line. The WebPublisher Studio Client includes comprehensive administration tools for remotely managing server resources (eg. taking resources offline, adding/removing server ports etc).

Server Folder Contents

Production Environment
The production environment requires a WebPublisher Studio Runtime Serial Number to unlock the evaluation restrictions in the server. The contents of the WebPublisher Studio Server folder are a mirror of the development environment (except you may wish to lock your development Plug-ins before deploying). To migrate your application to production, simply copy the contents of your Plug-in folders (and any Public resources) to the production environment and restart WebPublisher Studio Server.

Multiple Instance Clusters
WebPublisher Studio can be deployed to run multiple instances of the Server.
An instance is a running copy of WebPublisher Studio Server paired with an Omnis Runtime kit. The result is a multi-threaded server cluster with each instance delivering a single execution thread. The number of instances permitted is determined by (1) the number of Omnis Runtimes installed and (2) the WebPublisher Studio Multiple Instance License for the number of instances. Configuration simply requires all of the Omnis Runtime Folders to be stored in a common directory in the applications folder. The WebPublisher Studio Serial number controls the boot cycle and loads each instance using a separate Omnis Runtime. Typical uses of multiple instances include load balancing and dedicating functions/services (eg. dedicated Thick Client data entry, Web Forms and HTTP, Server Task Handling, SMTP outbound processing etc.).

Internet Protocol (IP) Address
The development environment requires a single, static IP address for registration of the server, and a single port allocation for the Administration Port. The WebPublisher Studio Client uses this address and port number for communicating with the WebPublisher Studio Server to manage resources and undertake development. Typically the server is set up with two ports - one for administration (eg. 9999) and one for the web service (eg. Port 80).

Port Forwarding and Firewalls
Because WebPublisher Studio is an Omnis Studio application it must be registered in the firewall to allow port flow-through of requests on any listening ports that have been assigned. Failing to do this means that your application may not be visible outside of the local network. You should enable any firewalls to allow WebPublisher Studio to be globally accessible and to enable port forwarding on the designated ports to prevent requests from being blocked. Consult your documentation for the make and model of any routers or firewall software you have installed on your production network.