Deployment Platforms

ActiveVOS Designer User’s Guide

Deployment Platforms

During the creation of the Process Deployment Descriptor file, you can select one of the following deployment platforms:

ActiveVOS Enterprise Server. Select this option to deploy to the ActiveVOS server. The ActiveVOS server is included with Designer.
ActiveBPEL Engine. Select this option for the open source engine. The engine is not full-featured, and some options in the PDD Editor are not available.

Platform-Specific Deployment Options

You can select platform-specific deployment options for new and running versions. If you do not change any settings, the server uses the defaults.

Process Logging

By default the ActiveVOS does not generate an execution log for running processes. Logging is turned off to enhance engine performance. You can enable this setting to override the engine default, and then view or download an execution log for a running or completed process. An execution log provides start/end times for activity execution and other details, and helps you troubleshoot faulted processes. The logging levels are:

System Default. Setting that is enabled in the server Administration Console that applies to all processes without a Process Logging override. The server is set to None by default.
None. No logging occurs as processes run.
Full. All execution statements are logged, including the Will Not Execute statements for deadpath activities. For example, all fault handling statements that are not executed are logged.
Execution. All execution statements are logged, except for Will Not Execute statements. Using this setting instead of Full can greatly decrease the size of the log file.
Execution with Data. All execution statements are logged, except for Will Not Execute statements, including variable, expression, and partner link data. Using this setting can greatly increase the size of the log file.

Process Persistence

Persistence refers to storage of active processes deployed to a server. When a process runs on the ActiveVOS server, all state information is stored in the server database. If you have a version of open source ActiveVOS Engine that is configured for persistent storage, the default is also to store all state information.

You can make persistence setting selections as follows:

Full	The default setting. For each process instance, all state information is stored for a running, faulted, and completed process.
None	No process information is stored in the server database when a process terminates. The process instance is not listed in the Administration Console’s Active Processes page.

Process Group

You can assign a process group name to one or more processes. The Group Name is a selection filter for viewing a list of deployed or active processes in the ActiveVOS server Administration Console. The Group Name is also useful for deploying a group of BPEL processes containing a People Activity. Refer to the ActiveVOS BPEL for People documentation for more information.

Suspend on Uncaught Fault

According to the WS-BPEL 2.0 specification, a process with an uncaught fault must exit. However, you can suspend this process on an uncaught fault to perform process exception management, if desired.

You can make selections as follows:

System Default	The current engine setting for all processes. The default engine setting is to disable suspension on uncaught fault.
False	Do not allow this process to suspend on an uncaught fault. The process will terminate abnormally. This setting overrides the engine setting.
True	Suspend this process on an uncaught fault to put it in a suspended-faulting state. You can then perform process exception management on the faulting process, followed by retrying or completing the faulting activity or scope. This setting overrides the engine setting. For details, see Process Exception Management.

Suspend on Invoke Recovery

For invoke activities which do not complete due to the node failure, you can suspend the process upon recovery. The process is suspended at the pending invoke, and you can perform process exception management, is desired.

You can make selections as follows:

System Default	The current engine setting for all processes. The default engine setting is to disable suspension upon process recovery when there is a pending invoke.
False	Do not allow this process to suspend at a pending invoke after process recovery. The process will terminate abnormally.
True	Suspend this process on recovery when there is a pending invoke to put it in a suspended state. You can then perform process exception management on the process, followed by retrying or completing the invoke. This setting overrides the engine setting.

Process Instance Retention Days

Once you deploy a process to the ActiveVOS server, and begin to execute it, the completed and faulted process instances are stored in the ActiveVOS database. ActiveVOS administrators can delete old processes from the database on an automatic schedule, based on the number of days you want to retain old processes before deleting them.

You can specify how many days to retain a completed or faulted process in the ActiveVOS database by adding a number of retention days in the PDD. This number can be modified for the process in the ActiveVOS server Administration Console.

If you don’t specify a value for retention days, the default engine value is applied to the process. This value is relevant only if automated database maintenance is enabled.

Versioning

Note that only one version of a process can create new process instances.

Process Version	By default, the ActiveVOS server auto-increments the version number for new versions. Auto-incrementing is based dropping the minor version number and incrementing the major version number by one. For example, 1.5 becomes 2.0. To define your own version number for this process, type in a number, such as 1.5.
Effective Date	If the effective date is blank or in the past, then the process immediately becomes the current version. The current version for a given process is the one capable of creating new process instances. If the date is in the future, the server makes this version the current version when the effective date arrives. If you intend to deploy your process to a server in a different time zone, be sure to edit the deployment descriptor file to include a time zone expression. For details, see What is Process Versioning?.
Expiration Date	If the expiration date is blank, then the process will not expire. Providing an expiration date is useful if you want the process to run for a limited period of time. An expired process version cannot create new process instances, but running process instances complete normally. You can specify an expiration date. If you intend to deploy your process to a server in a different time zone, be sure to edit the deployment descriptor file to include a time zone expression. For details, see What is Process Versioning?.
Running Process Disposition	By default, the all process instances are maintained. The default value of Maintain Version allows process instances created under previous versions to run to completion when this version becomes effective. You can select Migrate Version to convert process instances running against an earlier version to use the new version. This is useful if you have made only a small change to the BPEL process and want to apply the change to process instances already running. The only permitted changes are expressions. Select Terminate to terminate processes running under previous versions on the effective date of the new version, regardless of whether or not the process instances are complete. For details, see What is Process Versioning?

If you do not change the defaults, the .pdd file does not include any version details. To add or change version details, see Using the PDD Editor Source View.