Product Installation and Configuration

Installation of IBPM is very straightforward. An installer application is provided and very few questions are asked. This is known as standard installation. However, despite what I just wrote, experience is showing that Standard installation can be very problematic unless the environment on which the installation is to be performed is about as basic/virgin as it can possibly be. Instead of executing the Standard installation, it is recommended to perform the Advanced installation. In addition to following the instructions for an Advanced install, it is recommended to create a detailed log of the steps followed. This means creating a word processor document (eg. Apache Open Office or Microsoft Word) and logging all the steps performed. Ideally, screen shots of each of the items should also be captured. Any inputs asked for should also have their value recorded. If all goes well, it can be argued that the creation of this document was a waste of time, however, in the event that something goes “south,” this document can become extremely valuable in diagnosing the problems. In addition, if a later review or question comes up over what was entered or selected during installation or configuration, the document will again prove to be a useful guide.

Part Numbers

The part number for the current products as seen on IBM Passport Advantage are:

Business Process Manager

Windows

IBM Business Process Manager Advanced 8.5.7 Windows eAssembly

CRZ94ML

IBM Business Process Manager Advanced 8.5.7 Windows 1 of 3

CN939ML

IBM Business Process Manager Advanced 8.5.7 Windows 2 of 3

CN93AML

IBM Business Process Manager Advanced 8.5.7 Windows 3 of 3

CN93BML

IBM DB2 Server V10.5

CIW3YML

IBM WAS 8.5.5 Supplement 1 of 3

CIK1VML

IBM WAS 8.5.5 Supplement 2 of 3

CIK1WML

IBM WAS 8.5.5 Supplement 3 of 3

CIK1XML

Linux

IBM Business Process Manager Advanced 8.5 Linux eAssembly

CRMM5ML

IBM Business Process Manager Advanced 8.5 Linux 1 of 3

CIL96ML

IBM Business Process Manager Advanced 8.5 Linux 2 of 3

CIL97ML

IBM Business Process Manager Advanced 8.5 Linux 3 of 3

CIL98ML

IBM WAS 8.5.5 Supplement 1 of 3

CIK1VML

IBM WAS 8.5.5 Supplement 2 of 3

CIK1WML

IBM WAS 8.5.5 Supplement 3 of 3

CIK1XML

Integration Designer

|| |IBM Integration Designer 8.0 Multiplatform eAssembly|CRIG4ML| |IBM Integration Designer Version 8.0 Multiplatform Quick Start Guide|CI824ML| |IBM Integration Designer Version 8.0 Windows and Linux 1 of 3|CI825ML| |IBM Integration Designer Version 8.0 Windows and Linux 2 of 3|CI826ML| |IBM Integration Designer Version 8.0 Windows and Linux 3 of 3|CI827ML| |IBM Integration Designer Version 8.0 test environment Windows 1 of 5|CI828ML| |IBM Integration Designer Version 8.0 test environment Windows 2 of 5|CI829ML| |IBM Integration Designer Version 8.0 test environment Windows 3 of 5|CI82AML| |IBM Integration Designer Version 8.0 test environment Windows 4 of 5|CI82BML| |IBM Integration Designer Version 8.0 test environment Windows 5 of 5|CI82CML|

Process Server

Windows

IBM Process Server Advanced 7.5 for Windows eAssembly

CREX6ML

IBM Process Server Advanced 7.5 for Windows 1 of 3

CIOBKML

IBM Process Server Advanced 7.5 for Windows 2 of 3

CIOBLML

IBM Process Server Advanced 7.5 for Windows 3 of 3

CIOBMML

Linux

IBM Process Server Advanced 7.5 for Windows eAssembly

CREX9ML

IBM Process Server Advanced 7.5 for Linux 1 of 3

CI0BSML

IBM Process Server Advanced 7.5 for Linux 2 of 3

CI0BTML

IBM Process Server Advanced 7.5 for Linux 3 of 3

CI0BUML

If you are installing a full DB2, the part numbers for this are:

|| |IBM DB2 9.7 Enterprise Server Edition 32 Bit|CR8NVML| |IBM DB2 9.7 Enterprise Server Edition 64 Bit|CR8NWML|

Prerequisites

The official prerequisites for IBPM 8.5.5 can be found here:

IBM Business Process Manager Advanced detailed system requirements

For DB2, the version must be 10.1.0.1 or better. The version supplied with IBM BPM 8.5.5 is 10.5 ESE. If one installs DB2 manually, it is vital that after it is installed but before installing IBM BPM with a typical settings, that the DB2 license be applied. The license settings can be found using the "db2licm -l" command to see what is currently in effect. To apply an additional license, use the "db2licm -a" command.

Installing Integration Designer

Integration Designer is the development tooling for building SCA, BPEL and related components. It is an Eclipse based set of tools as well as a local copy of a Process Server for performing stand-alone based unit testing.

Experience has shown that there are problems installing ID from a Windows share.

To install Integration Designer and related components, follow these instructions:

Run launchpad64. This brings up an initial wizard.

This then launches and installs the IBM Installation Manager software.

Installing Business Process Manager Advanced in typical mode

The typical install of Business Process Manager installs a WAS server, feature packs and then the Business Process Manager itself. After the mechanical installation has completed, a profile is created that is configured with Process Center. Personally, I prefer to run the custom install as it gives me much more control over the installation process and profile creation. It also allows me to detect problem areas that would otherwise leave a complete installation broken.

The installation is started by running the Launchpad command which asks whether this is a typical or custom install. The typical install runs IBM Installation Manager in silent mode. This means that you don't see what is happening in as much detail during the installation

What follows is an example walk-through for installing IBM BPM 8.5.6:

The installation now progresses with a silent version of Installation Manager.

Performing a custom Install of Process Manager Advanced

When a Custom Install is requested, IBM's Installation manager is launched and used explicitly. I think I like this technique better than one large and silent install. Personally, I prefer to install each component one piece at a time in the following order:

Only when the preceding component has successfully been installed, do I proceed to the next. In principle, I should be able to install all the packages in one shot but I seem to believe that if there is an installation problem with a later package that all the previously installed packages are also rolled back when a clean-up is performed. This is probably the correct semantics as at the end of the failed install, we are back to where we were before the install started but to my mind, this means re-installing those successful packages the next time the install is attempted.

First I install base WebSphere Application Server ND

Following this, WAS ND v8.0.0.5 is now installed. Next it is time to install IBM BPM Advanced:

At the conclusion of the installation we are offered the choice of opening up the Profile Management Tool (PMT). PMT is used to create instances of servers including Process Servers and Process Centers.

Finally, I install IBM DB2 as the Database Provider for my environment.

Using BPMConfig to create servers

Starting from BPM v8.5, a command called "BPMConfig" has been supplied which will perform core BPM configuration functions.

BPMConfig is governed by a properties file. A sample can be found in

<Root>\BPM\samples\config

Always take a copy of this and never work with the master directly.

Within the configuration file, there are a number of entries that you can supply many with defaults already provided. Keep a copy of the file for your records. Also build a table:

|| |Property|Default|Your value| |bpm.de.name|De1|| |bpm.de.authenticationAlias.1.user|dadmin|| |bpm.de.authenticationAlias.1.password|password|| |bpm.de.authenticationAlias.2.user|db2admin|| |bpm.de.authenticationAlias.2.password|password|| |bpm.cell.name|PCCell1|| |bpm.cell.authenticationAlias.1.user|cadmin|| |bpm.cell.authenticationAlias1.password|password|| |bpm.dmgr.installPath|C:/IBM/BPM/v8.5|| |bpm.de.node.1.installPath|C:/IBM/BPM/v8.5|| ||||

Make sure that your DB2 database is already running and ensure that the databases called:


are already created. A sample SQL file called createDatabase.sql can be found in

<ROOT>/BPM/dbscripts/DB2/create

Take three copies of this file (one for each of the databases) and edit the files to reflect the names and userid to be used. Finally, run the scripts to create the databases. The command to run a script is commonly:

db2 -tf <filename>

Alternatively, after running the profiles create command, scripts will be created under the <profile>/dbscripts directory.

<DmgrProfile>/db2scripts/<Cell>/DB2/CMNDB/createDatabase.sh <DmgrProfile>/db2scripts/<Cell_DE1>/DB2/BPMDB/createDatabase.sh

The BPMConfig command to run to create the environment is:

BPMConfig -create -de <properties file>

On Linux, this will be:

/opt/IBM/WebSphere/AppServer/bin/BPMConfig.sh -create -de <properties file>

If an environment already exists, we can create a BPMConfig configuration from the existing environment file using:

BPMConfig -export -profile <dmgr Profile Name> -de <Deployment Environment Name>

An example might be:

BPMConfig -export -profile DmgrProfile -de ProcessCenter

A file will be generated called <Deployment Environment Name>.properties which is a property file used as input to BPMConfig.

Here is an example log of running a -create -de:

Logging to file /opt/IBM/WebSphere/AppServer/logs/config/BPMConfig_20170502-125952.log. Validating the profile registry. [] Configuring the deployment manager. Creating the deployment manager profile. INSTCONFSUCCESS: Success: Profile DmgrProfile now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/DmgrProfile/logs/AboutThisProfile.txt for more information about this profile. Starting deployment manager profile DmgrProfile. CWUPO0001I: Running configuration action detectNewProducts.ant ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServer/profiles/DmgrProfile/logs/dmgr/startServer.log ADMU0128I: Starting tool with the DmgrProfile profile ADMU3100I: Reading configuration for server: dmgr ADMU3200I: Server launched. Waiting for initialization status. ADMU3000I: Server dmgr open for e-business; process id is 31555 Configuring managed node profiles. Creating the managed node Node1 profile. INSTCONFSUCCESS: Success: Profile Node1Profile now exists. Please consult /opt/IBM/WebSphere/AppServer/profiles/Node1Profile/logs/AboutThisProfile.txt for more information about this profile. Adding the node Node1 to the cell PCCell1. ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServer/profiles/Node1Profile/logs/addNode.log ADMU0128I: Starting tool with the Node1Profile profile CWPKI0308I: Adding signer alias "CN=workvm, OU=Root Certificate," to local keystore "ClientDefaultTrustStore" with the following SHA digest: 29:D5:9C:7E:26:D4:D7:18:A9:1F:3F:99:A1:A3:B2:FF:AD:7E:3C:BD CWPKI0309I: All signers from remote keystore already exist in local keystore. ADMU0001I: Begin federation of node Node1 with Deployment Manager at workvm:8879. ADMU0009I: Successfully connected to Deployment Manager Server: workvm:8879 ADMU0507I: No servers found in configuration under: /opt/IBM/WebSphere/AppServer/profiles/Node1Profile/config/cells/PCCell1Node1/nodes/Node1/servers ADMU2010I: Stopping all server processes for node Node1 ADMU0024I: Deleting the old backup directory. ADMU0015I: Backing up the original cell repository. ADMU0012I: Creating Node Agent configuration for node: Node1 ADMU0014I: Adding node Node1 configuration to cell: PCCell1 ADMU0016I: Synchronizing configuration between node and cell. ADMU0300I: The node Node1 was successfully added to the PCCell1 cell. ADMU0306I: Note: ADMU0302I: Any cell-level documents from the standalone PCCell1 configuration have not been migrated to the new cell. ADMU0307I: You might want to: ADMU0303I: Update the configuration on the PCCell1 Deployment Manager with values from the old cell-level documents. ADMU0306I: Note: ADMU0304I: Because -includeapps was not specified, applications installed on the standalone node were not installed on the new cell. ADMU0307I: You might want to: ADMU0305I: Install applications onto the PCCell1 cell using wsadmin $AdminApp or the Administrative Console. ADMU0003I: Node Node1 has been successfully federated. Generating database configuration files to /opt/IBM/WebSphere/AppServer/profiles/DmgrProfile/dbscripts/PCCell1. Generating database configuration files to /opt/IBM/WebSphere/AppServer/profiles/DmgrProfile/dbscripts/PCCell1.De1. Provisioning cell. Generating database configuration files to /opt/IBM/WebSphere/AppServer/profiles/DmgrProfile/dbscripts/PCCell1. Configuring the cell. Configuring the deployment manager. Provisioning deployment environment. Generating database configuration files to /opt/IBM/WebSphere/AppServer/profiles/DmgrProfile/dbscripts/PCCell1.De1. Performing security configuration. Creating clusters. Configuring data sources. Configuring the databases. Configuring cluster SingleCluster for capability Messaging. Configuring cluster SingleCluster for capability Application. Configuring cluster SingleCluster for capability Support. Provisioning managed node Node1. Creating cluster members. The HTTP and HTTPS ports for server SingleClusterMember1 on node Node1 are added to the virtual hosts list. Configuring the REST services end points. Saving configuration changes... Synchronizing node Node1. ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServer/profiles/Node1Profile/logs/syncNode.log ADMU0128I: Starting tool with the Node1Profile profile ADMU0401I: Begin syncNode operation for node Node1 with Deployment Manager workvm: 8879 ADMU0016I: Synchronizing configuration between node and cell. ADMU0402I: The configuration for node Node1 has been synchronized with Deployment Manager workvm: 8879 Stopping deployment manager profile DmgrProfile. ADMU0116I: Tool information is being logged in file /opt/IBM/WebSphere/AppServer/profiles/DmgrProfile/logs/dmgr/stopServer.log ADMU0128I: Starting tool with the DmgrProfile profile ADMU3100I: Reading configuration for server: dmgr ADMU3201I: Server stop request issued. Waiting for stop status. ADMU4000I: Server dmgr stop completed. The 'BPMConfig.sh -create -de configEditor.properties' command completed successfully.

Editing the BPMConfig properties file graphically

A tool is available to edit the BPMConfig properties file. This tool can be setup as follows:

When the browser is closed, it has been found that the tool does not end. Simply enter CTRL+C in the DOS window in which it is running in order for it to be ended.

Generating ONLY the DDL using BPMConfig

When we configure an instance of BPM, we have to create databases and tables within those databases. When the database configuration is performed by a DBA, the DBA may wish to have the DDL before we create the BPM environment. There may very well be processes and procedures that need to be followed long in advance of a BPM configuration. This means that we need the corresponding DDL much earlier than the BPM configuration. Instead of creating a whole environment just to get the correct DDL for application on a database, we can issue a command such that only the DDL be generated. The command for this is:

BPMConfig -create -sqlfiles <properties file> -outputDir <Target Dir>

The DDL for the BPM environment will then be found in the output directory supplied on the command.

Using the PMT to create servers

The Profile Management Tool (PMT) is a GUI interface for creating and augmenting instances of WAS profiles. These profiles are the core to running Process Centers and Process Servers.

The PMT tool is launched from the file called:

<Install>/WebSphere/AppServer/bin/ProfileManagement/pmt.bat

The first page of the wizard shows a list of the products that may be configured using PMT. There is a button to launch the profile management tool proper.

After configuring the profile, it is ready to be started. In Windows, a set of menu items have been added to the Start menu.

Using the command line to create server profiles

The PMT tool is graphical in nature. As an alternative to creating profiles using PMT, a command line tool called manageprofiles can be used to perform a profile creation from text files that are used as input to describe the parameters to be supplied. One advantage of using this mechanism is that the record of how the server was created is now made permanent as opposed to having to remember the values entered interactively in the PMT tool. In addition, the recreation of the servers can be scripted and re-executed in the event of a need to recreate the servers.

There are quite a few flags/parameters that need to be supplied. Some of the parameters are listed below. All the parameters can be found well documented and fully explained in the BPM InfoCenter.

|| |-create|| |-templatePath|The path to the template used to control the creation of the profile. The profile templates can be found in the <install>/profileTemplates folder. The BPM templates are in the BPM folder. These include:


|-profileName|Name of the profile to be created| |-adminUserName|Name of the admin userid| |-adminPassword|Password for the admin userid| |-dbType|Type of the database to be used:


|-procSvrDbName|Name of the database for Process Server (eg. BPMDB)| |-dbProcSvrUserId|Userid used by Process Server to connect to DB| |-dbProcSvrPassword|Password for userid used by Process Server to connect to DB| |-perfDWDbName|Name of the database for Performance Data Warehouse (eg. PDWDB)| |-dbPerfDWUserId|Userid used for the Performance Data Warehouse| |-dbPerfDWPassword|Password for userid used for Performance Data Warehouse| |-dbDelayConfig|Should the configuration of the databases be delayed. A boolean value of either true or false| |-dbName|Name of the database for common (BPM Advanced) tables| |-dbUserId|Userid for the common database| |-dbPassword|Password for the common database| |-configureBSpace|Should Business Space be configured? (true/false) The default is true.| |-configureBRM|Should Advanced Business Rules manager be configured? (true/false) The default is false.| |-winserviceCheck|Should a Windows service be created to start this profile. Defaults to false.| |-dbJDBCClassPath|Class path for JDBC drivers. Default is based on DB type.


|-dbHostName|Host where DB is installed| |-dbServerPort|Port number where DB is listening (eg. 50000)| |-dbCreateNew|? (true/false)| |-configureBPC|? (true/false)| |-defaultPorts|| |-webServerCheck|Should Web Server definitions be made (true/false). Defaults to false.|

It is strongly recommended to create a text file which contains all these parameters in the form of name=value pairs. This file is called a response file by the manageprofiles tool. The content of this response file can then be used as input to the manageprofiles command using the syntax:

manageprofiles -response <fileName>

An example configuration looks as follows:

create templatePath=C:/IBM/WebSphere/AppServer/profileTemplates/BPM/default.procctr.adv profileName=Test01 adminUserName=admin adminPassword=admin configureBSpace=false dbType=DB2_UNIVERSAL dbDelayConfig=true dbName=CMNDB2 dbUserId=db2admin dbPassword=db2admin procSvrDbName=BPMDB2 dbProcSvrUserId=db2admin dbProcSvrPassword=db2admin perfDWDbName=PDWDB2 dbPerfDWUserId=db2admin dbPerfDWPassword=db2admin defaultPorts=true omitAction=samplesInstallAndConfig

Installing to (DBA) managed databases

There are occasions where the database used for operation of IBPM is not accessible during installation. This is commonly because the database is owned by a Database Administrator (DBA) who does not want to grant broad authority to the IBPM connected userid. Instead, installation and configuration should proceed without connecting to the database and, once installed, a series of scripts are provided to the DBA which can examine their contents and convince the DBA that all is well. The DBA will then execute the scripts with administrative authority which will create the necessary artifacts for the product's operation. Once the database has been configured, the product will then be able to run.

After configuring a server without applying the database changes, the scripts for configuration can be found at:

<Profiles>/<Profile Name>/dbscripts

DB2

After profile creation for an IBPM Advanced, the following artifacts can be found in <Profiles>/<Profile Name>/dbscripts

Running the CommonDB scripts

In the CommonDB folder, we will find a command called configCommonDB.bat. This is a shell script that should be run with the flag "createDB" (eg. configCommonDB.bat createDB). When executed, this creates the CommonDB database and creates tables within it.

Loading the PerformanceDW database

Run the following commands:

db2 -tvf createDatabase.sql

This will create the PDW database (eg. PDWDB)

Next run the commands

db2 connect to PDWDB user db2admin db2 -tvf createTable_PerformanceDW.sql db2 terminate

Loading the Process Server database

Run the following commands:

db2 -tvf createDatabase.sql

This will create the Process Server database (eg. BPMDB)

db2 connect to BPMDB user db2admin db2 -tvf createTable_ProcessServer.sql db2 -tdGO -vf createProcedure_ProcessServer.sql db2 terminate

Loading the ProcessChoreographer Database

No explicit connect to a database is needed for this step as the SQL itself contains a CONNECT.

db2 -tvf createSchema.sql

Finally see the section on common steps for all database types. A sample Unix script for running all these commands together might be:

# Run from dbscripts folder HERE=$PWD DBUSER=db2admin NODESERVER=emoNode01_server1 db2 drop database CMNDB db2 drop database PDWDB db2 drop database BPMDB cd $HERE/CommonDB/DB2/CMNDB ./configCommonDB.sh createDB db2 terminate cd $HERE/PerformanceDW/DB2/PDWDB db2 -tvf createDatabase.sql db2 connect to PDWDB user $DBUSER db2 -tvf createTable_PerformanceDW.sql db2 terminate cd $HERE/ProcessServer/DB2/BPMDB db2 -tvf createDatabase.sql db2 connect to BPMDB user $DBUSER db2 -tvf createTable_ProcessServer.sql db2 -tdGO -vf createProcedure_ProcessServer.sql db2 terminate cd $HERE/ProcessChoreographer/DB2/CMNDB/BPEDB db2 -tvf createSchema.sql cd $HERE/BusinessSpace/$NODESERVER/DB2/CMNDB ./configBusinessSpaceDB.sh cd $HERE/../bin ./bootstrapProcessServerData.sh

This script seems to be needed to run as a userid with write permissions in the <Install> directories of WAS.

MSSQL

For Process Server

For Performance Data Warehouse

Common for all Databases

After creating the databases and tables, the tables must be populated. Run the command bootstrapProcessServerData from the <Profiles>/<Profile Name>/bin directory. This needs to be run from a command prompt. It will take a few minutes to execute. It is vital that the configured userid have sufficient permissions to perform this task. For Unix systems this appears to be a user with the ability to write into the <Profile> directory.

Experience seems to show that the command to be run must be

$ sudo ./bootstrapProcessServerData.sh -clusterName SingleCluster

Operation of the Process Server requires that there be SI Bus definitions. These are made during configuration. However, the databases needed to host these Messaging Engine Data Stores are not necessarily automatically created. If messages appear about message buses not being started, it may be that the following recipe needs to be executed.

An IBM BPM Standard server needs two SI Buses for its operation.

By default, these are configured to use BPMDB and PDWDB databases. They are also configured to attempt to create the databases and tables which, in this story, won't work. As such, some work is required before starting the server. WAS provides a command called sibDDLGenerator which is used to generate the DDL required to create the tables. Run the following command to generate the DDL:

sibDDLGenerator.bat -system sqlserver -version 2008 -platform windows -create -user mssql > C:\temp\sib.sql

Next, have the DBA run this DDL against both the PROCSVR database and the PERFDW database.

Now, we can start the server but it will not function correctly. We need to make some further administrative changes that can only be made while the server is running. Start the WAS Admin console and navigate to Service Integration > Buses > PROCSVR.<Cell Name>.Bus > Messaging engines > <Messaging Engine Name> > Message Store.

Change the schema name to be IBMWSSIB and un-check the "Create tables" check box.

Save and repeat this for the PERFDW bus. Stop and restart the server. If all has gone well, the Buses should show "green" when the server is re-started.

For the Performance Data Warehouse, there are stories about a command called configurePerfDW but I have not yet investigated this area.

The DB2 databases need some specific creation parameters:

Installing Process Designer

The Process Designer component is used to build and test BPMN based processes. It can be downloaded directly from an already running instance of Process Center. With Process Center running, go to its main page in the browser:

The installation happens silently. After installation, launch Installation Manager to apply maintenance.

Alternatively, Process Designer can be installed through Installation Manager:

Starting BPM

Once BPM is installed, we can start it. There is an order to starting the environment. This is:


For the deployment manager, use the "startManager" command found in the <DmgrProfile>/bin directory. It seems to take about 5 minutes to start.

For the Node Agent, use the "startNode -profileName <NodeProfile>" command found in the <Root>/bin directory. It seems to take about 2 minutes to start.

For the deployment environment, use the "BPMConfig -start <propertiesFile>" command. The log file for this will be found in <Node1Profile>/logs/<SingleClusterMember1>.

Stopping BPM

BPM can be stopped by shutting down the components in the following order


Personally, I like to use the WAS Admin console to achieve an environment shutdown. To stop a Deployment Environment, we can use:

To stop the node agent, I use:

and finally, to stop the Deployment Manager, I use:

The tasks can also be performed from the command line using combinations of WAS script commands and/or the BPMConfig command.

For the Node Agent, use the "stopNode" command found in the <Root>/bin directory.

For the deployment manager, use the "stopManager" command found in the DmgrProfile bin directory. Use the Cell Admin userid/password.

Resetting the databases

The databases used by the product contain the repository of the Process Center. Should we desire, we can reset these databases. This is a solution that is very extreme but will result in a reset system (back to factory defaults).

The content of the Process Center database can be populated with the command called:

bootstrapProcessServerData.bat

This command is fully documented in the InfoCenter. The scripts to create the tables needed for operation can be found in:

<WAS Profile>/dbscripts

Un-configuring BPM

If we wish to un-configure BPM, we should consider what that would mean. Specifically, it would mean the deletion of the WAS profiles plus any databases used by the product.

To see what profiles exist, run "manageprofiles -listProfiles"

To delete a profile run "manageprofiles -delete -profileName <name>"

After deleting a profile using manageprofiles, also remove any directories for that profile found at <Root>/profiles. There may be directories with the same names as the profiles just deleted.

In addition, delete any log files.


We may wish to delete the databases as well. Typically these are CMNDB, BPMDB and PDWDB. We can login as db2admin and execute:

$ db2 drop database CMNDB $ db2 drop database BPMDB $ db2 drop database PDWDB

Hiding the sample applications

After installation and configuration of the product, some sample applications can be seen in the Process Center. These also show up in the Process Portal as startable processes. It is likely that you will want to hide these so that they don't clutter up your environment. These samples are:


These samples can be hidden by archiving the process apps from within Process Center.

Creating a new Process Server in its own deployment environment

After having created an environment for our Process Center, we may wish to add a second deployment environment to accommodate a new Process Server.

Create the databases for BPMDB, CMNDB and PDWDB. Make sure that they are distinct Dbs from other servers.

Note: To see what databases are defined, run db2 list database directory.

To create the scripts for creating databases, we can run:

BPMConfig -create -sqlfiles <Config.properties> -outputDir <outputDir>

This will create a directory which contains the scripts needed to create the databases.

Connect to the WAS admin console for the Deployment Manager and visit Servers > Deployment Environments.

Now it will cook for a while. Numbers seen seem to show about 25 minutes of elapsed time from start to finish.

On first startup, the deployment manager works with the node agent to push the required files for the new server's operation to the target node. This too can take some time.

Frequently Asked installation Installation Questions


The command called "versionInfo" can also be used to provide a detailed listing of what is installed. Consider running this with the "-long" flag to get a very detailed listing.

Installing on Linux

So far we have spoken about installing BPM on Windows and now we will examine installation on Linux. When downloaded from IBM, the distribution is a set of binary files. Typically we will want:


The Linux environment needs to be modified. Specifically, the file pass needs the following added or changed:

# - stack - maximum stack size (KB) user_name soft stack 32768 user_name hard stack 32768 # - nofile - maximum number of open files user_name soft nofile 65536 user_name hard nofile 65536 # - nproc - maximum number of processes user_name soft nproc 16384 user_name hard nproc 16384 # - fsize - maximum file size user_name soft fsize 6291453 user_name hard fsize 6291453

Before setting these values, my ulimit values were:

$ ulimit -n 1024

and

$ ulimit -f unlimited

On Ubuntu, we also need to install:

Next we create a directory called "extract" and extract each of the archives into that new directory. We extract one at a time.

$ tar -xvf <filename> --directory extract

When done, we can run:

$ sudo ./launchpad.sh

Unfortunately, for me this didn't work so I used a manual installation procedure. Change into IM64 directory and run:

$ sudo ./install

Once the product is installed, we will want to install the maintenance. Go to IBM Fix Central and search for the latest. At the time of wiring mine was:

bpm.857.cf2017.03.delta.repository

Interestingly, this was a ZIP file and not a compressed TAR file. To extract, create a directory called extract2 and run:

$ unzip bpm.857.cf2017.03.delta.repository.zip -d extract2

Installation Recovery

If something goes wrong during installation and you need to re-isntall portions, here are some notes.


No Comments
Back to top