Installing silently using the command line

You can install IBM® Business Process Manager silently using the command line. With this method, you need to run only one command to perform the installation.

Before you begin

If you do not have the prerequisite base products that are necessary for IBM Business Process Manager Standard installation, you must install the base products as part of the silent installation. The required base products are:
  • IBM Installation Manager
  • WebSphere® Application Server Network Deployment, including the ejbdeploy and thinclient features.
When you install the product, also install any available cumulative fixes or fix packs by adding the repository where you downloaded the fix.

About this task

During the silent installation, the following tasks are peformed:
  • Installation Manager is installed or updated to the appropriate level.
  • The required base products and IBM Business Process Manager Standard are installed.

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

Procedure

  1. Run the following command to generate encrypted passwords using Installation Manager to securely connect to DB2 and the administrative console.
    Important: If you are running Windows 7, Windows Vista, or Windows Server 2008, start your command prompt by right-clicking and selecting Run as administrator.
    extract_directory/IM64/tools/imutilsc -silent -nosplash encryptString password_to_encrypt
    Note: If you already have 32-bit Installation Manager installed, you can run the command from the extract_directory\IM\tools directory.
  2. Read and accept the license terms before installing. Adding -acceptLicense to the command line means that you accept all licenses.
  3. Run the following command:
    Important: If you are running Windows 7, Windows Vista, or Windows Server 2008, start your command prompt by right-clicking and selecting Run as administrator.
    extract_directory/IM64/tools/imcl install list_of_package_IDs -acceptLicense -installationDirectory location -repositories repository -properties key=value,key=value -showVerboseProgress -log logName.log
    where:
    • list_of_package_IDs is a list of the IDs for the products and features that you want to install. You must include the required features. The syntax is packageID,feature,feature, with multiple products separated by spaces.
      Table 1. Package IDs
      Product Package ID Feature and Description
      IBM BPM Standard com.ibm.bpm.STD.v85
      • StandardProcessCenter
      • StandardProcessServer.NonProduction - Test, staging, or development use
      • StandardProcessServer.Production - Production use
      WebSphere Application Server Network Deployment com.ibm.websphere.ND.v85
      • core.feature: Required. WebSphere Application Server core content.
      • ejbdeploy: Required. Pre-Enterprise JavaBeans (EJB) 3.0 modules.
      • thinclient: Required. Stand-alone thin clients and resource adapters.
      • embeddablecontainer: Embeddable EJB container.
      • samples: Sample applications feature.
      • com.ibm.sdk.6_64bit: 64-bit SDK.
      Installation Manager com.ibm.cic.agent
      • agent_core: Installation Manager core content.
      • agent_jre: Installation Manager Java Runtime Environment (JRE).
      IBM WebSphere SDK Java Technology Edition 7 com.ibm.websphere.IBMJAVA.v70 Java™ TE 6 is installed with WebSphere Application Server Network Deployment, but if you install Java TE 7, it will be used instead. If you install Java TE 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.
      IBM WebSphere SDK Java Technology Edition 7.1 com.ibm.websphere.IBMJAVA.v71 If you want to use Java 7.1, install this option and switch to it by following the instructions in the topic Switching the edition of Java used in IBM BPM.
      DB2 Express for Windows 64-bit com.ibm.ws.DB2EXP.winia64 DB2 must match the operating system
    • location is the path to the directory where you want to install the products. To install into an existing supported instance of WebSphere Application Server Network Deployment, specify its directory.
      Tip: Keep the installation path as short as possible. Otherwise, you might run into problems later when the paths of other components, when added to this path, exceed the 255-character path limit.
    • repository is the path to the repository where you have extracted the files:
      extract_directory/repository/repos_64bit
      For more than one repository, separate the repository locations with commas.
    • key=value is a list of the keys and values you want to pass to the installation, separated by commas. Do not put spaces between the commas.Create encrypted passwords using the IBM Installation Manager.
      Note: This table is applicable only when you install DB2 Express.
      Table 2. Keys
      Key Description
      user.db2.admin.username User name with authority to access the DB2 database
      user.db2.admin.password Encrypted password for the user name with authority to access the DB2 database. Choose a password that complies with the password policy of your system (for example, Windows 2008).
      user.db2.port Port for the DB2 database. The default value is 50000.
    • logName is the name of the log file to record messages and results.
    Running this command installs the product with the default features. To install any specific features or make other changes, see the reference link for the command-line arguments for imcl.

Results

Installation Manager installs the list of products and writes a log file to the directory that you specified. The log file is empty if there are no errors or warnings.

Example

The following example installs IBM Business Process Manager Standard, WebSphere Application Server Network Deployment, and DB2 Express on Windows.
Tip: If you copy the example, make sure there are no line breaks.
imcl install com.ibm.bpm.STD.v85,StandardProcessCenter com.ibm.websphere.ND.v85,core.feature,ejbdeploy,thinclient,embeddablecontainer,samples,com.ibm.sdk.6_64bit com.ibm.ws.DB2EXP.winia64 -acceptLicense -installationDirectory C:/IBM/BPM85 -repositories D:/temp/BPM/repository/repos_64bit -properties user.db2.admin.username=bpmadmin,user.db2.admin.password="Vvrs88V/a9BUdxwodz0nUg==" -showVerboseProgress -log silentinstall.log
The following example installs IBM Business Process Manager Standard, , a cumulative fix from another directory, WebSphere Application Server Network Deployment, and DB2 Express on Windows.
Tip: If you copy the example, make sure there are no line breaks.
imcl install com.ibm.bpm.STD.v85,StandardProcessCenter com.ibm.websphere.ND.v85,core.feature,ejbdeploy,thinclient,embeddablecontainer,samples,com.ibm.sdk.6_64bit com.ibm.ws.DB2EXP.winia64 -acceptLicense -installationDirectory C:/IBM/BPM85 -repositories D:/temp/BPM/repository/repos_64bit,/usr/tmp/BPMCF -properties user.db2.admin.username=bpmadmin,user.db2.admin.password="Vvrs88V/a9BUdxwodz0nUg==" -showVerboseProgress -log silentinstall.log

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.