WebPublisher Studio Product Information: Developing

Home Product Tools Case Studies Telework Support
FAQ Purchasing Technical Videos About Us Developer Site
New release Developing Software
Overview Developing Thin Clients Thick Clients SMTP Mail Server Tasks

Developing With WebPublisher Studio

The development of WebPublisher Studio applications takes place on a single computer or over a TCP/IP enabled network.

All resources are authored and tested using the development toolkit in the WebPublisher Studio Client then deployed to a production environment using the built in File Transfer tools.

WebPublisher Studio uses TCP/IP as the communications layer for developing, deploying and serving web-enabled databases.

The basic steps involved in writing applications are:

1. Create Your Plugin Application Library

  • Run WebPublisher Server and login using WebPublisher Client.
  • Create your Plugin (automatically saved in the developer folder)
    (This folder contains all your WebPublisher Studio and Omnis code)
  • Use the Resource Editors to create and edit Plugin resources
  • Use the Omnis IDE to write any Omnis code you want to use.
  • Save any changes you make.
Environment Folder Contents

2. Test Your Application

  • WebPublisher Plugins are staged using WebPublisher Server to test all published resources.
  • Upload WebPublisher Studio resources and Omnis libraries from the developer folder to the server.
    (Resource uploads to the server are managed with the upload tools in the Development Client)
  • The Server automatically recompiles and activates refreshed resources.
  • Test out your Plugin (ie. using a web browser or your custom application as appropriate).
  • WebPublisher logs any errors to enable you to debug the development code.
  • If you need to make changes, use the Resource Editors and repeat the testing process.


Plugin Manager

3. Move Your Application to Production

  • When your Plugin is ready for deployment, move it to the Production Server using the Remote Installer.
  • You can transfer Plugins, Files and other resources based upon server access privileges.
  • Uploads to Production uses the Development Server to relay transmission.
  • Uploads are performed securely over TCP/IP and Production Server status is restored.
  • Transmission errors during uploads are recorded to log files.
  • Fatal errors will cause the system to rollback to previous installation.
  • Developer access privileges are controlled by the Production Server Administrator.
  • Upgrades to Plugin applications can be performed offsite and uploaded into production from anywhere without the need for Production Administrator intervention.

Remote Installer Tool

WebPublisher Studio is designed to integrate with the following environments...

Any SQL compliant server supported by the Omnis Studio DAMs including ODBC (eg. DB2, Sybase, Oracle, SQLServer, MySQL etc.). FTP Servers using the Omnis Studio WebEnabler API to store, retrieve and manage documents over FTP .
SMTP email in batches or individually using our SMTP Mail tools in conjunction with any SMTP mail server. Custom Java applications (.jar) acting as server or client.
The Omnis NDF for caching WPS Server data or web enabling enterprise Omnis NDF content. Two (or more) WebPublisher Studio Server clusters to provide a communications bridge across discontiguous networks.
The WPS Thick Client delivering the Omnis programming interface to anywhere using our WebPublisher Studio .WPX API. The WebPublisher Studio Development toolkit HTTP Active Web Page generator supporting web browsers and other thin technologies.