Installing interactively with a new DB2 Express database on an existing installation of WebSphere Application Server

Using the custom installation option, you can install DB2 Express and IBM® Business Process Manager on an existing installation of WebSphere® Application Server, on Linux on Intel systems. If you are installing on Linux for z, Linux on Power, or Linux on Power LE, use the instructions for installing onto and configuring an existing database.

Before you begin

If you are installing from downloaded images from Passport Advantage, ensure that you downloaded all required images (three disk images for Linux systems on Intel; two disk images for other Linux systems). If you are installing from the DVD images, obtain the compressed files from the DVDs. In both cases, extract all of the files from the compressed files to the same location on your hard disk. Overwrite directories, if prompted.

Restriction: Extract the installation files to a directory that does not contain spaces or special characters. The launchpad cannot be started from a directory path that contains spaces or special characters.

When you install the product, also install any available cumulative fixes or fix packs. If you are using the launchpad to install and you have Internet access, you can include available fixes from the live repository during installation. Otherwise, you must install the upgrades from a local directory as described in Step 2 in the steps that follow. For example, you could add fixpack.BPM_CF=local_repository_path to the bpm_updates.properties file to include a cumulative fix.

About this task

Only one IBM Installation Manager is required to install multiple instances of IBM Business Process Manager.

Procedure

Go to the directory into which you extracted the images and enter the following command to start the launchpad:
```
extract_directory/launchpad.sh
```
You can run only one launchpad at a time.
Optional: If you are prompted to update the launchpad, click Update. The updates are installed and your launchpad is restarted automatically.
If you do not have access to the Internet and want updates to the launchpad to be installed from a local directory, you can modify a properties file with the appropriate launchpad prefix as described in step 1 to direct Installation Manager to the updates to install. Create the following file:
- /user_home_directory/bpm_updates.properties
Note: Ensure that you have read/write access to the folders that are specified in the bpm_updates.properties file.
The file uses a launchpad prefix, followed by a period. The name after the prefix and the period can be anything you want, which enables you to point to multiple locations for launchpad upgrades. The locations can be either local directories or URLs. The following code is an example of the prefixes and names in the properties file:
```
launchpad.1=/launchpad_updates
```
On the Welcome page, click Custom installation.
Click Installation on an existing WebSphere Application Server.
Select Install as administrative user to install the product as an administrative user. If you are a root user, you can install the product as an administrative user. If you are not a root user, or if you want to install to your own user name without root privileges, clear this option.
Optional: Click Update to update WebSphere Application Server Network Deployment. When Installation Manager opens, click Update to install available updates. On the Update Packages page, select Show all to display available updates.
Note: WebSphere Application Server Network Deployment must be updated only if it is not already at the fix pack level that IBM Business Process Manager Advanced - Process Server requires. IBM Business Process Manager can be installed only on top of the supported version of WebSphere Application Server Network Deployment. See system requirements for more information
Click Install.
On the Install Packages page, WebSphere Application Server Network Deployment, IBM WebSphere SDK Java Technology Edition (Optional) (Java™ 7), IBM Business Process Manager Advanced - Process Server, and IBM DB2 Express are selected by default. Clear the WebSphere Application Server Network Deploymentoption.
Note: For the existing WebSphere Application Server, the Java version used is Java 6 by default, except on Linux on Power LE, where Java 7.1 is used (and the other options are not available). If you clear the Java 7 package option, Java 6 will be used. If you install Java 7 but find that you still need to use Java 6, you can switch before you create profiles by using the managesdk command. For more information, see Switching the edition of Java used in IBM BPM.
You can also optionally install IBM WebSphere SDK Java Technology Edition 7.1 (Java 7.1) to use instead of Java 6 or Java 7. If you install Java 7.1, you must also follow the instructions for switching Java versions in the topic Switching the edition of Java used in IBM BPM.
If you are connected to the Internet and want to check for the latest fix pack or refresh pack and recommended interim fixes for WebSphere Application Server and IBM Business Process Manager, click Check for other Versions, Fixes, and Extensions, and then click Next. You might be prompted to provide your IBM ID and password to connect to the IBM service repositories.
You can obtain an IBM ID and password can by registering at http://www.ibm.com.

If there are fix packs or interim fixes available, they are shown after you select the fix pack or refresh pack levels that you want to install.

To continue installing the product without downloading the required fixes, click Cancel.
On the Licenses page, read the license agreement. If you agree to the terms of the license agreement, click I accept the terms in the license agreements, and then click Next.
On the Location page, the Use the existing package group is selected by default. Make sure that the path points to the installation directory where WebSphere Application Server is installed, and then click Next.
On the Features page, expand the plus symbol to select the package features that you want to install. Installation Manager automatically enforces dependencies with other features and shows the updated download size and disk space requirements for the installation.
1. Select the translations to install. Under Translations Supported by All Packages, English is selected by default for the English version. To install other language versions, select the appropriate language under Translations Supported by Only Some Packages.
2. Optional: To see the dependency relationships between features, select Show Dependencies.
3. Optional: Click a feature to view its brief description under Details.
4. Select one of the following features to install.
  - IBM Process Center License
  - IBM Process Server Production License to use the server in production
  - IBM Process Server Non-production License to use the server only for development, test, or staging.
  Your selection is recorded in the product tag for inventory purposes, so select the license feature that matches the license you have purchased and want to use. There are no functional differences.
  Restriction: Do not mix production and non-production servers in the same cell.
  
  Optionally, select the Basic Case Management License feature if you are licensed to install basic case management capabilities, which enable knowledge workers to drive business outcomes by using a combination of structured workflows, ad-hoc tasks, and document processing.
When you are finished selecting features, click Next.
On the Common Configurations page, specify the DB2® administrative user names and passwords.
- DB2 instance user
- DB2 fenced user. The fenced user is used to run user defined functions (UDFs) and stored procedures outside of the address space used by the DB2 database. The default user is db2fenc1 and the default group is db2fadm1.
- DB2 administration server (DAS) user. The user ID for the DB2 administration server user is used to run the DB2 administration server (DAS) on your system. The default user is dasusr1 and the default group is dasadm1. This user ID is also used by the DB2 GUI tools to perform administration tasks against the local server database instances and databases.
If the fenced user or administration (DAS) server user name exists, clear the New User option.
To confirm that your choices are correct, click Re-Validate.

Restriction: User names must not contain National Language Strings (NLS).
On the Summary page, review your choices before installing the IBM Business Process Manager Advanced - Process Server package. When you are satisfied with your installation choices, click Install. A progress indicator shows the percentage of the installation completed.
When the installation process is complete, a message confirms the success of the process.
1. Optional: To open the installation log file for the current session in a new window, click View Log File. To continue, close the Installation Log window.
2. If you plan to use the BPMConfig command-line utility to create your Deployment Environment, select None to complete the installation.
3. Click Finish.

What to do next

After you install IBM BPM, you must configure the product by creating profiles, setting up database tables, and configuring the network deployment environment. To do these configuration tasks in one step, use the BPMConfig command. Alternatively, you can do each configuration step separately using the Profile Management Tool, if it is supported on your operating system, and the Deployment Environment wizard.

Important: If you are migrating business data and applications from a previous version, use the configuration instructions in the Migrating to IBM Business Process Manager section.