Home | Websydian Documentation
Search | Print

Moving process to production - Win/iSeries

Overview

As a developer often won't be authorized to move processes from the test environment to the production environment, this task will often be done as a collaboration between the developer responsible for the process and an administrator who is responsible for the setup of the production site.

Moving a process from test to production can in some cases also mean that the objects have to be moved between different physical servers - in some cases this will have to be done by an operator.

All of this means that it is very important to be aware of which steps it is necessary to do to move a process, who is responsible for each step, and how the person responsible for the step can obtain the necessary information from the other persons involved in the move.

Move new/changed database files

The developer responsible for the process must keep track of which physical and logical files it is necessary to move for each process.

Any new files must be added to the library containing the production files.

It is important that the library is not the one containing the database used by the Websydian Express runtime - otherwise you might experience problems when upgrading Websydian Express.

Move program objects

The developer responsible for the process must keep track of which objects it is necessary to move for each process.

As for the files, we recommend that the Websydian Express runtime program objects is kept separate from the application objects.

For the WinC objects (webserver objects) it is important to remember the .pnl objects (and remember that even internal functions can use .pnl files).

Move templates

In addition to the program objects and files, it is necessary to move the templates to the folders used by the production environment. This means that it is also necessary for the developer to keep track of the templates used by the process. If designers/administrators have made new versions of the templates it is of course necessary to keep track of which version it is necessary to move.

Specify process and presentation

To make the business process available in the production environment it is necessary to define the process and one or more presentations - as well as adding a site element to the site structure specifying where the new process is to be available in the production site.

To be able to define the process, it is necessary to know the Program ID (implementation name of the ProcessEntryPoint function). This information must be supplied by the developer. Use the menu item "Content Loaders -> Business Processes" to create the process.

To be able to define the correct presentations it is necessary to know the templates used by the process. If only the original templates are used (without any suffix), the easiest way to define the necessary presentation is to use the "Use default presentation" check box in the Insert function of the "Content Loaders -> Business Processes" function.

Otherwise the administrator must be informed about the presentations it is necessary to use - and the corresponding template suffix used. The presentations is specified by pressing "Presentations" for the new process on the grid page of the "Content Loaders -> Business Processes" function.

Special information needed for framesets

In the cases where a new frameset process is to be moved from test to production, it is important that the administrator is informed about which frames the frameset defines - as he must use this information to specify the site structure.

In some cases it will be enough to inform the administrator about the names of the templates that defines the frameset (the name of the frames can be found in the template).

In some cases you might want to make a list or maybe a graphical  representation of the way the frameset will split the page - and what the name of each frame is.

The administrator can use the "Frames" menu item to make the frames known to the system - after this he can add the functions he wants to populate the frames to the site structure (as children of the frameset site element).

Menuservice (alias)

In some cases you will use menu services to make a link from one process to another (outside the menus). If this is the case, the administrator must also be informed about any menu services used (which site elements the refer and the alias used). He can the use the "Site Structure -> Maintain Alias" function to define the alias - and the "Menu Service" button on the "Site Structure -> Site Structure" function to specify which menu item the menu service refers to.