IBM BPM Installation Blueprint

Project overview.

Here is a summary of what this project will achieve.

This project is designed to install IBM BPM using RapidDeploy.

The server in the project is Windows. It can be cloned to Linux but it will need different configuration in RD Project.

The project is preconfigured with one target environment.

Specific application configuration items can be changed between environments, by use of Data Dictionary items.

Prerequisites

• A remote Windows server with firewall configuration that allow connection from the machine when RapidDeploy instance is installed (for testing purposes we suggest to turn the firewall off).
• RapidDeploy Agent should be downloaded and running on a remote Windows server
• In this example we assume that IBM BPM binaries are already downloaded on your remote target server and extracted to  C:\Software\BPMInstaller path. It is worth to mention that it is possible to use binaries that you have locally. In this case you will need to add those binaries to your deployment package and then use Unzip task to extract binaries into chosen location.
• In this example we assume also that IBM Installation Manager is already installed. If you don’t have it yet, please use this RapidDeploy project to install IBM IM first
• IBM BPM installation is based on task that is included in  rapiddeploy-core-plugins-prd-generic-environment-filesystem.jar   and   rapiddeploy-orchestration.jar  – so make sure these jars are in your RapidDeploy agent  lib   folder or they are added to your project classpath
• Make sure you have correct values in your hosts file (http://www.rackspace.com/knowledge_center/article/how-do-i-modify-my-hosts-file).

What is preconfigured and demonstrated

• One target server for Windows. The user will need to configure the actual hostname for this logical server definition.
• Use of the RapidDeploy agent. If deploying to Linux then you’ll probably want to change this to use the SSH.
• IBMInstallationManagerExecuteCommandTask task to run imcl command with arguments based on task resources (see the task specification and investigate task resources on Orchestration tab )
• As you can read in IBM BPM documentation in order to install Business Process Manager it is necessary to have WebSphere® Application Server Network Deployment installed. Because you already have Installation Manager the only thing you need to do is to put correct packageID in IBMInstallationManagerExecuteCommandTask task (it is already configured in your sample project).

How to use this project.

1. Download the project to your desktop by clicking on one of the links. The file will be saved as INSTALL_BPM.zip
2. Log into your RapidDeploy instance as mvadmin.
3. Navigate to Resources-> Projects.
4. In the top right hand corner click on the Upload Project button.
5. Select the zip file you downloaded in step 1.
6. You are guided through a project import wizard. The important thing to check and change (if necessary) here is the path to the project storage directory (you will need to check it in SCM Repository tab, Artifact Repository tab and File System tab). Look at the example below:
   For example you are running RapidDeploy on Windows and your MV_HOME is set to C:/MV_HOME/midvision. Usually all RapidDeploy projects are stored in the  MV_HOME\projects directory. After importing our project, if you noticed that Project Root Directory path on the  SCM Repository  tab is   /rd/projects/INSTALL_BPM,  then in this case you will need to change the path to C:\mv_home\midvision\projects\INSTALL_BPM

   Change paths in Artifact Repository and File System in similar way

7. Once the project is imported, there are a couple of things you’ll need to do.
   • Firstly, you will need to change the server configuration. In order to do that navigate to  Resources  ->   Targets   ->    Servers and find aws-ihs-windows-server   (this is the name we used in our sample project). Edit this server – put correct Hostname then navigate to Transport tab and check if it is possible to connect to your remote Windows server by clicking Test Connection.
     Note that Successful connection is mandatory to go further!
   • Secondly, in sample project C:\IBM\BPM is set as a installation path – if you need to change this – please go to  Orchestration   tab and change DirectoryWriteCheckTask property and also put the same path in EnvironmentInstallation (Resources  ->   Targets   ->    Installations), make sure that path to Installation Manager specified in IBMInstallationManagerExecuteCommandTask task is correct.
   • You need to create deployment package. Go to  Packages tab, click  Create Package button.
8. Navigate to Jobs-> New Job.
   • Select the project you created earlier. You will see a tree view of server/installation.
   • Select the one you want to deploy and follow the wizard.
   • On the  Version  panel you select the version (package version) you want to deploy.
   • Since there is only one package, it is preselected. The latest package will always be preselected by default.
   • Click on the  Skip to Finish  checkbox and click  Next .
   • On the final tab click the  Start Job  button. The deployment is started and you see the tasks executed and job log in real time.