Synchronizing Process Runtime Settings with webMethods Monitor

In both cases, any changes to the stage runtime settings in a process model are saved to the Process Audit database. The saved changes overwrite the existing setting details in the database. As a best practice, you should ensure that your runtime settings are always synchronized between the two locations.

When you open a process in Designer, it retrieves the runtime settings saved with the model in the local workspace.

When you click the Synchronize button on the Stages page in the Properties view, or in the Runtime Editable Properties section of the Runtime page in the Properties view, Designer retrieves the runtime settings from the database and applies them to the process model. Saving the process model saves the settings to the local workspace.If you want your process model in Designer to display the current database runtime stage settings, you must click the Synchronize button on the Stages page of the Properties view.

When you build and upload a process in Designer, the runtime settings in the model are saved in the Process Audit database, overwriting the settings stored in the database and applying the updated settings to the runtime environment. In addition, a warning message is recorded in the build and upload report. If you want your process model runtime settings in Designer to be written to the database, build and upload the process model. This overwrites the settings are stored in the database, and the setting are applied to the runtime environment.

To ensure that you work with the latest settings, click the appropriate Synchronize button immediately before you modify and save these settings.

Important:

Deleting a step that is contained in a process stage without first synchronizing the stage settings with the database can lead to the process being out of sync with edits done in Monitor. Always click the stage settings Synchronize button immediately before you delete any steps in Designer that are contained in a stage.