IBM BPM, V8.0.1, All platforms > Install IBM BPM > Plan for IBM BPM > Plan the database configuration

Non-administrative user considerations

If installing IBM BPM as a non-administrative or non-root user and you want to create a test profile during installation, you must have the DB2 server installed before you begin the installation. Remember the database details so that you can enter them during the installation.

Tip: The Interactive Installation and Configuration Guide is a tool in this information center that you can use to generate a set of installation and configuration topics customized to your precise installation needs. You can save the generated output, print it, take it with you when install on another computer, or share it with someone else on your team. Each time you need to install with other options, return to the form and generate a new guide, or use it to see what the installation and configuration process looks when you choose different options.

The considerations described in this topic apply to any install scenario where you choose to install using the Typical install option. Profiles are created automatically when install using the Typical option.

Test profiles apply only for use with an IBM BPM Advanced configuration.

To install as a non-administrative user, you have the following choices:

Alternatively, instead of creating a test profile, you can create a profile after installation (this is the case for any install using the Custom install option). Use these steps:

  1. Install the product without creating a profile. When install as a non-administrative user, on the Install Packages page, you must clear the check box for DB2 Express. On Windows, if you have the option to install IBM Cognos Business Intelligence, you must clear that check box as well.

  2. On the Features page, expand the servers and make sure that none of the test profiles are selected.

  3. Use pmt.sh to create a stand-alone profile, or to create the dmgr and the custom profiles. If you do not have a database installed, use the Advanced path for all. Do not use the Typical path. Select the option to delay the execution of the database scripts during profile creation.

  4. If the databases were not created in advance, have the database administrator create the databases and tables after profile creation or augmentation.

  5. For an ND:
    1. Federate the custom profiles to the dmgr.

    2. Using the administrative console, create the required deployment environment

Plan the database configuration