WebPublisher Studio V5.1 is written in Omnis Studio V4.3 and can be deployed into any environment where Omnis will run. This includes Windows (2003-2008, XP, Vista, Windows 7, Windows 8 etc.), Macintosh (OS X 10.4.11 and later), and Linux (Ubuntu, Red Hat etc.).
The current release supports Omnis Studio from V4.3 up to Omnis Studio 6.
The shipping version can be converted to Omnis Studio 5 or 6 by opening WebPublisher Studio with a development copy of Omnis.
| The WebPublisher Studio development system comprises two separate applications for authoring and publishing web-enabled applications - the Database Server (WebPublisher Server) and the Development Client (WebPublisher Client).
WebPublisher Studio Server is booted using an Omnis Studio Runtime whilst the Development Client is started using an Omnis Studio development 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 uploaded into the production environment 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, uploading Plugins etc).
Server Folder Contents
The production environment requires a WebPublisher Studio Production 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 Plugins before deploying).
- To migrate your application to production, you simply upload the contents of your Plug-in folders (and any Public resources) to the production environment using the deployment tools built into WebPublisher Studio Client.
|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 batch processing etc.).
Cluster - Runtime Folder
|Internet Protocol (IP) Address
The development environment requires a single, static IP address for registration of the host server with one port allocated for Administration and one port allocated for File Transfers. The WebPublisher Studio Client uses this address and port numbers for communicating with the WebPublisher Server to manage resources and develop applications.
- Typically your server would be set up with three ports - one for administration (eg. 9999), one for File Transfer (eg. 9998), and one for your web service (eg. Port 80).
- You can add additional service ports at any time.
|Port Forwarding and Firewalls
Because WebPublisher Studio is an internet application Omnis Studio 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 area network.
You should enable any firewalls to allow WebPublisher Studio listening ports to be globally accessible and 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.
- You can firewall your network with internet-facing service ports for web traffic, and private ports for your LAN, Intranet or Thick Clients.
- You can configure your Macros to route access to URIs based upon request IP and/or port.
- You can Reverse Proxy traffic to your WebPublisher Cluster behind an SSL Certificate to deliver secure web services to thin clients and/or balance load on Multi Instance Clusters.