What tasks can WebPublisher Studio perform?
WebPublisher Studio is as a Client-Server Offsite development environment using TCP/IP as the underlying communications layer.
This means that WebPublisher Studio can "talk" to any other device that uses TCP/IP (including other installations of WebPublisher Studio).
This allows WebPublisher Studio to operate in various configurations - serving "Thin" Offsite HTML pages, remote data processing as a "Thick" Offsite client, Peer to Peer data transfer (eg. Client Server database consolidation and batching), Bulk Email dispatching, eCommerce etc.
In fact there really isn't anything that we haven't been able to do using WebPublisher Studio.
Why should I develop in WebPublisher Studio?

WebPublisher Studio provides a comprehensive TCP/IP application development framework that extends Omnis to allow rapid prototyping of dynamic web services and complete desktop applications. Using WebPublisher Studio you can develop and deploy applications to your production systems from anywhere - our remote upgrade tools are industrial strength and allow you maximum flexibility to support your customers - even when you're on vacation. And did we mention unlimited users and unlimited sessions? No restrictions supporting multiple connections with WebPublisher Studio.

What value does WebPublisher Studio add?

WebPublisher Studio integrates a suite of Client Server development tools with the Omnis Studio IDE to streamline application development.
You don't get all of this stuff straight out of the box in Omnis. We know - we had to write it for ourselves.
For more than 15 years we've done the hard yards developing and testing WebPublisher Studio and have numerous production systems installed that run flawlessly, day after day. Delivering that sort of reliability is why we choose to develop in Omnis. Omnis provides a rich toolkit for writing Client Server and web enabled applications - great if you want to roll your own server. We did and what we've written is a genuine value-add to Omnis.
Try it and judge for yourself.

How difficult is WebPublisher Studio to use?
Anyone familiar with writing applications in Omnis Studio can immediately write systems using WebPublisher Studio.
In fact, we've found it is often easier writing web-enabled solutions than writing traditional LAN based multi user systems.
If you have libraries containing code to manage the business application rules then all of this code is available for use in WebPublisher Studio.
The WebPublisher Studio Developer toolkit allows you to easily leverage your existing code base for use on the internet.
Existing applications can be rewritten to take advantage of the Thick Client API so they work on the LAN and over the internet.
How do I use WebPublisher Studio to develop applications?
Typically development work takes place in a sandbox environment on your computer or deployed across your network over TCP/IP.
To develop in WebPublisher Studio you need a development copy of Omnis Studio to write code for your Plugins using the WebPublisher Studio Client, and a runtime copy to run the WebPublisher Studio Server. You write your application using the WebPublisher Studio development tools then, when ready to deploy, you migrate your Plugins to the production server and switch it on. That's it. Once the system is deployed you use the WebPublisher Studio Client Administration tools to manage the server - take Plugins off line, assign SMTP mail servers, add or reallocate service ports etc. - all these tasks can be performed remotely.
Is WebPublisher Studio a complete web server?
Yes and no. WebPublisher Studio can service any type of HTTP request provided suitable resources (eg. Macros) have been created to handle the request.
This includes Java, HTML, graphics and other forms of static media. The qualification here is that WebPublisher Studio is designed primarily to service dynamic and not static content. Although WebPublisher Studio supports serving static pages using the "PUBLIC" subdirectory, it is much more efficient to offload these requests to a dedicated HTTP server such as IIS or Apache.
How does WebPublisher Studio compare with other database server environments (eg. PHP, ColdFusion)?
Certainly PHP, ColdFusion and WebPublisher Studio are performing similar tasks running thin applications.
The main advantage of WebPublisher Studio is that it is an Omnis application and is therefore a Rapid Application Development environment suitable for prototyping online systems. It can do what these other IDEs do and more including FTP, SMTP and Thick Client.
We believe that the WebPublisher Studio tools allow you to author comprehensive online systems in a fraction of the time it would take using PHP, ASP/NET, Perl or Java. And if you're already an Omnis Developer you preserve all of your code assets and don't need to learn to program in some foreign environment.
Flexible, scalable and a low total cost of ownership plus the reliability of Omnis Studio.
Which backend databases does WebPublisher Studio support?
WebPublisher Studio systems can access data from any of the databases supported by the Data Access Managers (DAMs) supplied with Omnis Studio.
This includes MySQL, PostgreSQL, Oracle, Sybase, DB2, ODBC, JDBC, OmnisSQL and others.
Does Corporate Windows undertake custom work in WebPublisher Studio?
Yes - we frequently perform custom work configuring WebPublisher Studio systems for clients.
If customers wish to do their own work using WebPublisher Studio we are happy to do the foundation work and supply open source libraries to seed development. This allows an exchange of knowledge that will permit custom development to be transferred, completed and maintained in-house.
I've got a specific question about WebPublisher Studio - how can I get an answer?
Just contact us using the submission form on the Support page and we'll get back to you.