Process Server provides
one business process management runtime environment that can support
a range of business processes for development, test, staging, or production.
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.
About this task
Using
the typical installation option, you can install DB2 Express on Linux
on Intel systems, and configure the required databases for IBM® Business Process Manager. Select
typical installation only if you are installing on Linux on Intel,
have administrative privileges (are a root user), and do not have
an existing DB2 database server on the system. 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.
From the product launchpad,
the typical installation process installs the software, configures
the deployment manager and managed-node profiles, and configures a
single-cluster deployment environment that consists of one node and
one server. It also installs IBM WebSphere SDK Java Technology Edition
7 (Java 7) and the profiles use it, except on Linux on Power LE where
it installs Java 7.1. On supported operating systems, you can optionally
switch the profiles to a different version of Java. For more information,
see Switching the edition of Java used in IBM BPM.
Only
one IBM Installation Manager is required to install multiple instances
of IBM Business Process Manager.
Procedure
- Optional: If you are connected
to the Internet, the typical installation process automatically upgrades
your product to the latest fix pack or refresh pack level and recommended
interim fixes. If you want these upgrades to be installed from a local
directory instead, or if you want to specify the fix level, you can
modify a properties file to direct Installation Manager to the upgrades
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 three prefixes:
ifix,
fixpack,
and
launchpad. Each prefix must be 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 interim
fixes, fix packs, and 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:
ifix.1=/bpmUpdates
fixpack.2=http://test/rep
launchpad.1=/launchpad_updates
fixpack.WAS_REP=/WAS_updates
fixpack.BPM_REP=/BPM_updates
- 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 the updates
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.
- On the Welcome page,
click Typical installation.
- Select Install Process Server and
click Next.
- Specify Process Server information:
Select Use this server offline if this Process Server will
not be connected to a Process Center. Offline
servers can still be used when deploying snapshots of process applications,
but the method for deploying process applications to an offline process
server differs from the method for deploying process applications
to an online process server.
If you did not select
Use
this server offline, provide the following information
for the
Process Center that
this server should connect to:
- Host name: Enter the host or virtual host
that this Process Server will
use to communicate with Process Center. Use
a fully qualified host name. In an environment with a load balancer
or proxy server between the Process Server and
the Process Center services,
make sure that what you designate here matches the URL that is used
to access the Process Center.
- Port: Enter the port number of the Process Center. In
an environment with a load balancer or proxy server between the Process Server and
the Process Center,
make sure that what you designate here matches the URL that is used
to access the Process Center.
- User name: Enter the name of a Process Center user. Process Server will
connect to Process Center as
this user.
- Password: Enter the password for the Process Center user.
You can click Test Connection to check
the connection to the Process Center. The
connection attempt can fail if the user name and password combination
is wrong, or if a custom context root has been set for the Process Center. If
the custom context root has been set, you must use a custom install
path instead of typical.
- Click Next.
- Select No. I need one installed
for me. to install DB2 Express.
- Specify the following 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. Restriction: - User names must not contain National Language Strings (NLS)
- User names must be maximum eight characters long
- Click Next to continue.
You are prompted to provide your IBM ID and password to connect to
the IBM service repositories.
Note: If you are using a
local properties file, you do not need to provide your IBM ID and
password.
A connection to the service repositories is required
to download and install fix packs and required interim fixes from
the Internet, including fixes for WebSphere Application
Server and IBM Business Process Manager. You
can obtain an IBM ID and password by registering at http://www.ibm.com.
To continue
installing without downloading the required fixes, click Cancel or
clear the Use your support account to include updates
with the installation option on the Installation
summary page.
After successfully installing the product,
you can use Installation Manager to install the required fixes.
- On the Installation summary page,
verify that the installation options and read the license agreements.
If you agree to the terms of the license agreements, click I
have read and accepted the license agreement and notices.
- Click Install Software.
Results
After a successful installation, the Quick Start console
starts automatically. If the security certificates failed to import
for the connection between Process Center and Process Server, you
must configure the SSL communication manually.
What to do next
To learn about security for
the environment and applications, see Creating a secure environment.