In the simplest hardware architecture with multiple Runtime Environments, we usually see three different Servers: a Test Environment BPM Server, a Production Environment BPM Server and a SQL Server. On each BPM Server we install: the Workspace Service, pointing to the same Workspace Database on the SQL Server and the Runtime Services: Notification, Process Engine, Task and Scheduling, where, during installation, we select the Runtime Database corresponding to the Server's environment for each of the Runtime Services, e.g. the Test Environment BPM Server's Runtime Services point to the Test Runtime Database.
Within your Solutions, then, you want to ensure that those Processes running in your Test Environment use test Resources and Processes running in your Production environment use production Resources, but you want to ensure that you use the same Processes and the same Resource Solution Items in both environments. So, how do we ensure test Processes connect, for example, to your test SQL instance and production Processes connect to your production SQL instance?
BPM provides you with a couple of different methods for determining the value of a Data Item by environment:
