Choosing how to configure profiles and deployment environments

When performing a custom installation and configuration, you can select which tool to use to configure profiles and deployment environments, depending on which product edition you are installing and which operating system you are using.

For IBM® BPM Express, you will use the BPMConfig command to create new stand-alone profiles.

For IBM BPM Standard, IBM BPM Advanced, and IBM BPM Advanced: Process Server, you can choose to configure the profiles and deployment environment all at the same time by using the BPMConfig command, or separately by using the Profile Management Tool (PMT) and the Deployment Environment wizard. Using the BPMConfig command to configure your environment all at once is more straight-forward and easier to do. However, if you want to set up nodes and customize security settings before setting up the topology, choose PMT to create the profiles and the Deployment Environment wizard to configure the deployment environment.

PMT is not supported on Linux on Power LE. If you need to create profiles separately from the deployment environment on Linux on Power LE, you must first create just the profiles using the BPMConfig command.

PMT is not supported on Solaris. If you need to create profiles separately from the deployment environment on Solaris, you must first create just the profiles using the BPMConfig command. The Interactive Installation and Configuration Guide will provide those instructions if you select Solaris as your operating system and PMT as your profile creation method. Although it is possible to use the BPMConfig command to create only profiles on all operating systems, it is not a path suggested through the interactive guide, other than for Solaris.

The interactive guide does not provide information for the path to take if you are augmenting existing profiles because your are installing into an existing WebSphere® Application Server. See help topics about the manageprofiles command for more information on augmenting profiles.

Restriction: When you create profiles using PMT, you must use parameter values that match the values that are specified in the properties file that the BPMConfig command uses for the deployment environment setup. For example, if you set the value of cellName to Cell1, the properties file that BPMConfig uses must also use the Cell1 value. If you omit optional parameter values, PMT creates default values that must also match the required parameter values that are used by BPMConfig. For more information and examples, see The profile management command: manageprofiles.