The next step is to deploy an instance of BundleWorks. Typically, there will be only one instance of BundleWorks per machine, but multiple instances are possible. Each instance uses its own 'work' directory for runtime files.

A BundleWorks installation can be shared across multiple machines (for example, /opt/bundles may be on a shared drive), but a deployed BundleWorks instance is machine-specific. (If you need to deploy BundleWorks instances on a shared drive, you must create a directory per host to keep each instance separate.)

Deploying an instance is simply a matter of running the 'deploy.sh' script from the root directory of the extracted BundleWorks archive. After you accept the license agreement, the script will ask you for the following:

A directory named 'bundleworks' is created within the chosen deployment directory. Inside this directory, a 'work' directory is created, inside which other runtime directories are created (e.g. data, logs).

Note that you can run the deploy.sh without user interaction by setting environment variables before running deploy.sh. See the script for details. This can be useful for scripting installation to multiple machines.