Environments

Environments are available in Professional Edition or higher. Contact your Dell Boomi Sales Representative for more information.

Before managing environments, you should be familiar with general process development, and process deployment.

Overview of Environments

The activation of Environments allows you to support dedicated and separate deployment setups for different phases of the development lifecycle. More importantly, it gives you greater control over change management and supports different connection configurations with the use of Extensions. Integrations can be built, tested and promoted between Environments with a full audit trail of what was deployed, and by whom. Environments help to ease the management of larger implementation projects that require the use of multiple application setups, on-premise resources and a distributed architecture.

All Processes can still be tested in Test Mode, but Environments allow you to deploy specific Processes for testing scheduled executions, larger document batches and real-time integration scenarios. Multiple Atoms can be attached to an Environment, while multiple Processes can be attached to multiple Environments. Basically, you can fully test deployed Processes from end-to-end, avoiding Test Mode restrictions, without affecting Processes currently running in Production.

Environments and Licensing Impact

It is important to understand that deploying Connections across different Atoms and Environments will affect your License count. Connections are still deployed at the Atom level. If you utilize extensions, you can re-use the same connection components and supply different configuration information at "deploy-time".

Use Cases for Environments

• Distinguish Test and Production: Many applications offer the ability for users to manage production and sandbox accounts. Processes that need to be thoroughly tested may require the storage of alternate configuration information when compared to a Production setup.

• Classify On-Premise Resources: Database setups or network directories may require unique connection information. Managing these resources in different environments helps to ensure data integrity and prevents documents from reaching the wrong destination.

• Manage Client-specific Projects: A full implementation for a specific client may require a series of Processes. Distributing the process workload across different atom environments per each client can help you to more easily deploy Process updates.

Processes must contain Extensions for Connection information, along with other global variables, to be controlled at the Environment level. Review how Environment-level Extensions can be enabled here.