Online documentation - WebsydianExpress v3.0 |
This description describes the steps necessary for deploying a developed business process for test purposes.
This guide shows how to make the the business process available by pressing a menu item.
For a more complete description of how you can add the business process to a site, read the two administrator guides:
The simplest way of deploying the objects is to let the library/folder you compile you objects to be part of the library list/path defined for the application service jobs.
For iSeries, this is defined in the job description EXPRESS. For Windows, this is defined in the settings.cmd file under the folder "Application Service"
If the templates has been defined using the PageModeler (RPG Developer and 2E Developer) the templates are already deployed. Otherwise you will have to move the templates to one of the folders defined in the administration interface.
For iSeries, you must restart the jobs servicing the application (use the start/stop) command if any program objects has been changed.
Follow these steps in order to define a new Business Process:
Follow these steps to attach a business process to a menu element as a menu item:
Whenever a new event (typically buttons or links on pages) is called the first time, the WebsydianExpress runtime makes a registration of the event as a valid event.
To ensure that only the correct events are registered - a number of preconditions must be in place:
The Site Settings can be found in the Sites -> Site Settings in the administration interface.
If any of these preconditions are not satisfied, an general error will be shown to the user, and a diagnostic error message will be written to the message log.
If an error occurs when trying to run the application, there are a couple of places to look for diagnostic information:
The message log is found in the administration interface. Utilities -> Message Log.
The message log contains error messages and diagnostic information from the WebsydianExpress runtime.
When using the iSeries, the joblog for the EXPRESSAS jobs submitted by the START command can contain all of the usual information concerning missing objects etc.
In Windows installations, the EXPRESS.log file found in the installed folder "Application Service" can contain error and diagnostic message.