Using Runtime Configurations

Runtime configurations can be used to quickly change the runtime configuration of a project that has already been deployed and used. For example, you can change the theme or path of your Web App, disable scheduling or profiling of your project, or correct the value for a process parameter.

X4 BPMS uses runtime configurations for the following files:

• .schedule

• .profiling

• .param

• .wac

• .theme

You can find the runtime configurations (.runtime files) under <server_directory>/deployments/<repository> . The name of the .runtime file corresponds to the name of the project in which you made the change. The .runtime file stores all changes to the runtime configuration of the project in the form of a password-encrypted file.

Note:

.runtime files have priority over the original configuration file.

Example:

You change the scheduling for your project using an endpoint. The generated .runtime file is then used, not the .schedule file. If you make changes to the .schedule file, they will not be applied because the .runtime file will not be overwritten.

If you want to use the configuration from the .schedule file again in the project, you have two options:

1. Delete the .runtime file.

2. Update the .runtime file with the available endpoints/adapters.

The following table provides an overview of which adapters and REST endpoints can use and create runtime files.