BPM Process Server Installation

This document provides an example of installing and configuring IBM Business Process Manager Advanced Edition V 8.5.0.1, for an authoring environment, on Solaris, using IHS and Oracle.


Prerequisites


Install BPM 8.5 product and fixpack binaries

Product images /tmp/BPM_Install
Installation Manager  image /home/media/ibm_media/solaris/Sparc64/im/17/iml
Response file /tmp/BPM_Install/responsefiles/BPM/bpmAdv_solaris_response_nonroot_64bit_host608.xml
Fixpack Directory /tmp/ BPM_Install/fixpacks
Dmgr root install /opt/was85/bpmlocal1/
Dmgr Profile root install /opt/was85/bpmlocal1/profiles/dmgr
Node root install /opt/bpm85/bpmlocal1/
Node Profile root install /opt/bpm85/ bpmlocal1/profiles/node01
IHS root install /opt/ihs85/bpmlocal1/
IHS Response file /tmp/WP/IHS/responsefiles/samples/bpm/WASv85.ihs.install.xml
Plugin root install /opt/plugins85/bpmlocal1
PLG Response File /tmp/WP/IHS/responsefiles/samples/bpm/WASv85.plg.install.xml
ToolBox root install /opt/toolbox85/bpmlocal1
ToolBox Response File /tmp/WP/IHS/responsefiles/samples/bpm/WASv85.wct.install.xml
WCT PLG Definition Response file Node01 /opt/toolbox85/bpmlocal1/WCT/pct_responsefile.txt
WCT PLG Definition Response file Node02 /opt/toolbox85/bpmlocal1/WCT/pct_responsefile.txt
IIM root install /opt/iml
IIM Shared Lib /opt/bpm85/BPMShared
BPM Backup Directory /opt/bpm85/bpm_backup


Install the Installation Manager V7 on Dmgr node

Verify success...


Install Business Process Server product binaries on Dmgr

Verify success...


Install WAS and BPM fixpack and interim fixes on Dmgr

Verify success...

Run a version info...


Create Dmgr profile using Process Server Dmgr profile template

Verify success...

Start the dmgr

Verify success...

Log on to the console...


Install Business Process Server product binaries on nodes

Verify success...

On node01 and node02 install BPM binaries.

Verify success...


Install WAS and BPM fixpack and interim fixes on nodes

Verify success...

Run a version info...


Create custom profile using Process Server profile template on node01

Verify success...


Create custom profile using Process Server profile template on node02

Verify success...


Federate Node01 to Dmgr

Verify success...


Federate Node02 to Dmgr

Verify success...


Create Deployment Environment and configure clusters

  1. Log on to the WAS console and expand the Servers section and click on the Deployment Environment link as shown below:

  2. Click on the Deployment Environment and then click New.

  3. Enter...

    Deployment Environment name LocalDE_PS
    Deployment Environment administrator bpmadmin
    Password password
    Confirmation password password
    BPM Deployment Environment type Advanced Process Server
    Deployment Environment pattern Application, Remote Messaging and Remote Support

    Click Next

  4. Select both nodes and click next

  5. Leave default value and click next

  6. Enter the clusters name and members of clusters...

    Application Cluster/Member name appCluster/appClone01/appClone02
    Remote Messaging Cluster/ Member name meCluster/meClone01/meClone02
    Remote Support Cluster/ Member name supCluster/supClone01/supClone02

  7. Enter the Process Center connection information

  8. Enter the database information. Make sure "Create Tables" check box is selected.

  9. Click Generate Deployment Environment

  10. When complete, click save changes to finish

  11. Verify datasources test connection from WAS admin console...

      Resources | JDBC |Data Sources | Test Connection check box

  12. Serially start each cluster.

      Servers | Clusters | WAS Cluster | meCluster | Start
      Servers | Clusters | WAS Cluster | supCluster | Start
      Servers | Clusters | WAS Cluster | appCluster | Start

  13. Login to Process Admin console

      http://host608.myco.com:15025/ProcessAdmin

    ...and enter userid and password to login

  14. Login to Process Admin console


Add LDAP to the WebSphere federated repository

  1. Stop all BPM clusters members and node agents on all machines. Only the deployment manager should be running.

  2. Login to the WebSphere Integrated Solutions Console...

      https:// hostname:59043/ibm/console

    Navigate to...

      Security | Global Security | User account repository section | Configure | Manage Repository

  3. In the Add dropdown list, select LDAP repository

  4. Provide a meaningful name for the new repository in the Repository identifier field; we are using...

      LDAP1_BPM

    In the LDAP server section select an appropriate type of LDAP in the Directory type dropdown; here we choose IBM Tivoli Directory server.

    Specify the LDAP server's host name in the Primary host name field...

      myldap.myco.com

    Specify an LDAP port in the Port field.

    Specify an LDAP user and password in the Bind distinguished name and Bind password fields.

    The DN will be returned in the following format, which is what we enter for the Bind distinguished name:

      uid=wasbind,cn=wasadmins,o=myo,st=mn,c=us

  5. In the Repository dropdown, select your repository, and set the base DN. Click Ok and Save

  6. Login to the WAS console and navigate to...

      Users and Groups | Manage Users

    You should see the users from both the InternalFileRepository provider as well as the LDAP server.

  7. Add LDAP users and groups into BPM

    Login to the BPM Process Admin Console of one of the nodes as BPM administrator (bpmadmin)...

      https://hostname:15025/ProcessAdmin

    Then navigate to...

      User Management | Group Management

    In the search field type "my_admins" then click add Users link

    In the popup windows type wasbind then click "Add Selected" Repeat the same step for tw_authors group.

  8. At this point you should be able to login to BPM Process Admin/ Portal using wasbind

    Login to the WebSphere Integrated Solutions Console


Install IHS for BPM on each web server

  1. Run...

      umask 022
      ulimit -n 8800
      cd /opt/iml/eclipse/tools
      ./imcl -acceptLicense -showProgress input /tmp/WP/IHS/responsefiles/samples/bpm/WASv85.ihs.install.xml
      ./imcl -acceptLicense -showProgress input /tmp/WP/IHS/responsefiles/samples/bpm/WASv85.plg.install.xml
      ./imcl -acceptLicense -showProgress input /tmp/WP/IHS/responsefiles/samples/bpm/WASv85.wct.install.xml

    Verify success...

      /opt/iml/datalocation/logs/

  2. Configure WCT and PLG on node01 and node2

      umask 022
      ulimit -n 8800
      cd /opt/toolbox85/bpmlocal1/WCT/
      ./wctcmd.sh -tool pct \
                  -createDefinition \
                  -defLocName /opt/plugins85/bpmlocal1 \
                  -defLocPathname /opt/plugins85/bpmlocal1 \
                  -response /opt/toolbox85/bpmlocal1/WCT/pct_responsefile.txt 
      

    Verify success...

      /opt/plugins85/bpmlocal1/logs/

  3. Copy configurebpmWebServer1.sh and configurebpmWebServer2.sh file from node01 and node02 to...

      remote_dmgr:/opt/was85/bpmlocal1/bin

  4. On each node, run respective file...

      cd /opt/was85/bpmlocal1/bin
      ./ configurebpmWebServer1.sh
      ./ configurebpmWebServer2.sh

    Login to the Dmgr admin console and click...

      Servers | Servers Type | Web Servers

  5. Select both web server and click start.


+

Search Tips   |   Advanced Search