Choosing the type of installation

The installation type selection determines how you interact with the installation process to provide information and select the options you want.

A typical installation is the simplest and quickest method for installing and configuring. The installation program uses default values for as many installation options as possible, and you supply values for the remaining options using a graphical interface. This is suitable for a relatively quick proof-of-concept installation and when you are not using an existing WebSphere® Application Server instance.

For IBM® Business Process Manager Express, using the product launchpad, the typical installation installs the software and configures a stand-alone profile. You do not need to create a profile later using the Profile Management Tool or manageprofiles command.

For all other IBM Business Process Manager editions, using the product launchpad, the typical installation installs the software, configures the deployment manager and managed-node profiles, and configures a single cluster deployment environment that consists of a single node and single server.

For IBM BPM Express, the typical installation also installs Process Designer on your machine.

With a custom installation using a graphical interface, you can customize all installation settings.

With a custom installation using a command line, you can run a command that specifies installation settings. This is more suitable if you only require a single installation.

With a custom installation using a response file, you create a file that specifies installation settings, and run an installation command that calls it. Using a response file is a better choice if you know that you need similar installations on several systems in your enterprise.

If you are installing an online Process Server that connects to a Process Center where a customized context root has been set, you must install using one of the custom installation paths. Typical installation does not configure a customized context root environment.

If you are installing IBM Business Process Manager in group mode as a user in the installation group, you must select custom installation using a command line or response file. For more information, see the Installation Manager information center topic Administrator, nonadministrator, and group mode.

For all of the custom options, the generated guide includes information about creating profiles and the deployment environment after installation.

If you are migrating business data and applications from a previous version of IBM Business Process Manager, you must use one of the custom installation types. See the topics in Migrating to IBM Business Process Manager for additional information.

For Windows 7, Windows 8, and Windows 2012, if you want a nonadministrative user ID to be able to administer the deployment environment without elevating its permissions with Run As Administrator, then you must use a custom installation path. Typical installation always configures the deployment environment as an administrator, so later operations such as starting and stopping the environment or modifying profiles must also be done with elevated permissions.