What tasks can WebPublisher Studio perform? |
| WebPublisher Studio is designed as a Client-Server 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). Consequently it is possible to use WebPublisher Studio to operate in many different configurations - serving "Thin" HTML pages, remote data processing as a "Thick" client, Peer to Peer data transfer (eg. Client Server database consolidation and batching), Bulk Email dispatching, eCommerce etc. In fact there isn't anything that we haven't been able to do using WebPublisher Studio. |
How difficult is WebPublisher Studio to use? |
Anyone familiar with writing applications in Omnis Studio can immediately write systems using WebPublisher Studio.
In fact it is often easier writing web-enabled solutions than writing traditional LAN based multi user systems.
If you have libraries containing code to manage application business rules then all of this code is available for use by WebPublisher Studio. The WebPublisher Studio toolkit allows you to easily leverage your existing code base for use on the internet and existing applications can be written to take advantage of the Thick Client API so they work on the LAN and/or the internet. |
How would I use WebPublisher Studio to Web enable applications? |
| Typically development work takes place in a staging environment - you aren't going to test/debug your code using a live system are you? To develop in WebPublisher Studio you need a development copy of Omnis Studio to write code for your Plug-ins using the WebPublisher Studio Client, and a runtime copy to run the WebPublisher Studio Server. You write your application using the WebPublisher Studio tools then, when ready to deploy, you migrate your Plug-ins to the production server and switch it on. That's it. Once the system is deployed you use the WebPublisher Studio Client to manage the server - take Plug-ins off line, add mail servers, reallocate server 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 Applets, Flash objects and other forms of media. The main qualification here is that WebPublisher Studio is primarily designed to service CGI style requests (ie. Named Pair Value - NPV) and not static content. Although WebPublisher Studio can process static pages using the "PUBLIC" subdirectory, it is less efficient than processing these requests via 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. The main advantage of WebPublisher Studio is that it is an Omnis Studio application and is therefore a Rapid Application Development environment suitable for prototyping online systems. 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 code in a foreign environment. Flexible, scaleable and a low total cost of ownership plus the reliability of Omnis Studio. |
What 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 ODBC, SQLServer, EDP, DB2, Oracle, Sybase, MySQL, OpenBase and OmnisSQL. |
Does Corporate Windows undertake custom work in WebPublisher Studio? |
| Certainly. 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. |
Home
