Install Operational Decision Manager


  1. Pre-Install
  2. Install
  3. Installation options
  4. Install ODM with the launchpad
  5. Install ODM with Installation Manager
  6. Install in silent mode
  7. Install Rule Solutions for Office
  8. Checking the installation
  9. Troubleshooting the installation
  10. Set up Ant automation
  11. Uninstall ODM


Pre-Install

  1. Install ODM standard or ODM Express?

  2. Acquire required licenses.

    Profile templates, used for augmenting WAS with ODM, require a Decision Server license. Business Rules Embedded, which includes a development environment, requires Decision Server license.

  3. Verify requirements are satisfied.

  4. Use standard directory naming conventions as much as possible when configuring ODM. For example, for the Dmgr profile directory, use something like...

      /opt/IBM/WebSphere/AppServer/profiles/Dmgr01

    ...rather than...

      /opt/IBM/WebSphere/AppServer/Dmgr01


Install Operational Decision Manager

  1. Download ODM installation archives

  2. Copy files to target host.

  3. Extract all disks to the same directory...

      WebSphere Application Server /disk1/WAS
      IBM SDK Java Technology Edition Version 7.0 for WebSphere /disk1/WASJDK7
      WebSphere eXtreme Scale /disk1/WXS
      Decision Server /disk2/WDS
      Profile templates for WAS /disk2/OW
      Embedded Rules /disk2/ER
      Decision Center /disk3/WDC

    Each directory contains copies of...

      Installation Manager (IM) Install product components
      Launchpad Install ODM binaries with GUI
      Response files Install ODM binaries in silent mode

    For AIX, the native UNIX tar command does not support long file names. If this becomes an issue, run the GNU version of tar.

    For WinZip, go to...

      Option | Configuration | Miscellaneous

    ...and clear...

      TAR file CR/LF conversion

  4. For a custom installation use the launchpad to install...

    Required software Description
    Installation Manager V1.6.0 or later Version supplied with ODM is 1.6.2.
    WebSphere Application Server Network Deployment V8.5.0.2 ODM is installed under WAS_HOME/
    WebSphere eXtreme Scale V8.6.0 Required by the Event runtime.

    For WAS ND install to Linux or AIX, edit...

      /etc/security/limits.conf

    ...and set..

      hard nofile 100000
      soft nofile 100000

  5. For custom installation, run Installation Manager and set repository locations for...

    • Decision Center
    • Decision Server
    • Profile templates
    • Business rules embedded


Installation options

Goal Option
Sample server option from launchpad. Defines a profile on WAS containing deployed applications to run the samples and tutorials. Includes an embedded Apache Derby database and WAS default messaging. Does not require any configuration.
Stand-alone server option from launchpad. Install only selected ODM components. Configures a single server profile on WAS. For development or small-scale production environments. Configured with the relevant augmentations. ODM components, including Decision Center consoles, Rule Execution Server, and the Event Widgets, are ready to use. The sample and tutorial applications are not available. During installation, select an existing database: DB2, Oracle, SQL Server, Derby Network Server. For Event runtime, select either WAS default messaging or WebSphere MQ.
Custom installation option from launchpad or IM. Install only required components. Extend Eclipse environment. Install in compatible IBM product. Requires Post-configuration steps. Tomcat, JBoss, WebLogic, and Java SE can be used with Decision Center and Decision Server Rules only.


Install ODM with the launchpad

A web browser is required to run the launchpad, either Firefox or Internet Explorer.

Install in a shared location for multiple users, or to a single location for a specific user.

Install either as a regular user or as an administrator.

On Windows7, install ODM in a directory other than Program Files or Program Files (x86). To install the ODM components with a version of IM that is already installed, verify the User Account Control setting in the Control Panel is not set at the lowest value. If set to minimum, launchpad is launched automatically in administrator mode, and installs a new version of IM in addition to the one that is already installed.


Install ODM with the sample server

To install IBM ODM with the sample server:

  1. Start the launchpad.

      ./launchpad.sh

  2. On the Welcome page, select Sample Server.

  3. Specify the directory where you want to install ODM.

  4. Enter a user ID and password for logging in to the WAS administration console and other applications such as the Event Widgets. For example:

    • User ID: odmadmin
    • Password: odmadmin

  5. If you have an ODM Express license, select the corresponding option.

  6. Click Next.

  7. Review the license agreement and notices, and select the check box to agree to the terms.

  8. At the bottom of the page, click Install Software.

    During the installation, the installer prompts you to confirm that you want to run the IM and other installation programs, click Yes to accept.

    The installation runs in the background. Do not close the launchpad even if the progress bar shows 100% completion. Wait until you get the message: Installation completed successfully. If you cancel before completion, files and folders already copied are not deleted. To fix...

    1. Uninstall products already installed
    2. Manually delete remaining files

  9. Click Close, Exit, OK.

  10. Verify following elements are installed...

      Decision Server Rules Rule Designer and Rule Execution Server
      Decision Server Events Event Designer and the event runtime
      Decision Center Decision Center Business Console and Decision Center Enterprise Console

    ...into directories...

      Operational Decision Manager WAS_HOME/ODM85/ODM
      WebSphere eXtreme Scale
      WebSphere Application Server
      WAS_HOME/ODM85/WAS/AppServer

  11. Start the sample server. A profile is configured on WAS Network Deployment to run the included samples and tutorials.


Install ODM with a stand-alone server

  1. Set up a database

    • IBM DB2 Universal Databaseā„¢
    • IBM DB2 for z/OS
    • Microsoft SQL Server
    • Oracle
    • Derby Network

  2. To use WebSphere MQ as the JMS provider for the event runtime...

    1. Install WebSphere MQ client.

    2. Create WebSphere MQ resources:

      • queue manager name
      • host
      • port
      • transport type
      • channel

  3. Determine components...

    • Decision Server Rules
    • Decision Server Events
    • Decision Center

    This installation option automatically installs the following required software:

    • WAS
    • WebSphere eXtreme Scale

  4. Start the launchpad.

  5. On the Welcome page, select Stand-alone Server.

  6. Enter the information required to install and configure Decision Center and Decision Server:

    1. Specify the directory where you want to install ODM. You can keep the default installation directory C:\Program Files\IBM\ODM85 or click Browse to specify a different location.

      On Windows 7, the Program Files and Program Files (x86) directories are protected, therefore if you are not installing ODM as an administrator, you might encounter difficulties running certain programs. To avoid this issue, install ODM in a directory other than Program Files or Program Files (x86).

    2. Enter a user ID and password for logging into the WAS administration console and all the other applications running on WAS such as Decision Center and the Event Widgets. For example:

      • User ID: odmadmin
      • Password: odmadmin

      Your user ID and password must not contain any white spaces.

      For security reasons, change your password and remove the temporary response files created by the launchpad after the installation is complete. These files are generated during the installation process in...

      • Windows: %TEMP%\IBM_LaunchPad_InstallType_TimeStamp
      • Unix: /tmp/IBM_LaunchPad_InstallType_TimeStamp

    3. Select the components to install and for which you have a license:

      • Decision Server Rules
      • Decision Server Events
      • Decision Center

    4. Select the method for allocating port values on the stand-alone server:

      • Recommended port values

        This option ensures that the port numbers are different from any other installations of WAS on the computer.

      • Default WAS port values

        This option uses the standard port numbers. However, you can run only one instance of WAS using these values at a time.

  7. Click Next.

  8. Specify the database to use:

    1. Select the database type.
    2. Enter the connection and authentication details for your database.

  9. Click Test Connection to make sure that the values that you have entered are correct.

    You cannot test the connection of a database on Derby Network Server.

  10. Click Next.

  11. Select the type of messaging to use for internal communications in Decision Server Events:

    • WAS default messaging
    • WebSphere MQ

      If you select Websphere MQ, manually create the resources and enter the details required.

  12. Click Next.

  13. Review the license agreement and notices, select the check box to agree to the terms, and then click Install Software.

    The installation runs in the background. At the end of the installation, the script to create the stand-alone server profile is started. Wait until it completes.

    If you cancel the installation before its completion, the files and folders that have already been copied onto your computer are not deleted. You must uninstall ODMs that the launchpad has already installed, and manually delete the remaining files before running the launchpad again.

When the installation is complete, the following components are installed...

By default, they are installed in the following directories:

The stand-alone server is configured, and you can start the server using the Start menu shortcut. To use the events Properties tool and legacy connectors, perform additional configuration steps.


Install a custom ODM configuration

  1. Start the launchpad.

  2. On the Welcome page, select Custom Installation.

  3. If you are an administrative user, and a shared drive is mounted, you can select check box...

      Install in a shared location for multiple users

  4. If Installation Manager not installed, click...

      Install IBM Installation Manager

    ...and follow the steps in the installation wizard.

  5. Click...

      Install IBM WAS Network Deployment

    ...and follow the steps in the installation wizard.

    In the WAS feature tree, do NOT select the option...

      Sample applications

    This would prevent the event runtime from running correctly.

    At the end of the installation, do NOT open the Profile Management Tool.

    By default WAS_HOME is set to...

      /opt/IBM/WebSphere/AppServer

  6. To install eXtreme Scale, click...

      Install WebSphere eXtreme Scale

    ...and follow the steps in the installation wizard.

    When prompted, set path for WAS_HOME directory. For example...

      /opt/IBM/WebSphere/AppServer

    Install WebSphere eXtreme Scale in the same directory in which you installed WAS.

    You might get a warning on the version of WAS. If you used the version of WAS packaged in the launchpad, you can ignore this warning, and click Next to continue the installation.

    At the end of the installation, do NOT open the Profile Management Tool.

  7. After installing the required software, install components:

      Decision Center

      Author, manage, and test

      Decision Server

      Development and runtime environments

      Business Rules Embedded

      Requires Eclipse 3.6. Requires IBM Decision Server license.

      Profile templates for WebSphere Application Server

      Deploy Decision Center and Decision Server on WAS. Requires IBM Decision Server license.

    To install the four components collectively, click Install Decision Manager.


Install ODM with Installation Manager

Installable components...

After completing installation, configure Decision Center and Decision Server.

Use the same user to install the required software, for example install ODM and WAS with the same user.

To install as root, run the install executable file in the IM directory. To install as non-root user, run the userinst executable. To install as group of users, install IM using the group mode, then run the groupinst executable file.


Package groups and the shared directory

IM specifies a default Package group and a Shared resources directory. Some packages cannot share a package group, in which case the option to use an existing package group is disabled. You can install ODM in an existing package group if you installed supported versions of compatible products such as...

...and you want to extend it with Rule Designer and Event Designer features.

When you install several packages at the same time, all the packages are installed into the same package group. After creating the package group, you cannot change the installation directory. The installation directory contains files and resources that are specific to ODM.

The shared resources directory is where Eclipse plug-ins and other files are located to be used by one or more product package groups. Specified during install. Name depends on the first product installed. You cannot change the directory location except by uninstalling. Do not edit or modify any files in this directory.


Languages

During the installation, you can select the languages to install. English is selected by default and it is always installed.

Language selection applies only to Eclipse features. A language pack is installed for each language that you select so that you can start Eclipse in the locale for these languages.

If you are extending an existing Eclipse, select the languages for which you already have the language packs installed. If you select a language that is not already installed in your existing Eclipse, you might get an error. To solve this issue, clear the languages that are not installed in your Eclipse.

The Rule Designer user interface is installed with all the supported locales. Therefore, even if you do not install a certain locale, for example French, the Rule Designer views and editors in Eclipse are still shown in this language (French) if you start Eclipse in this locale.


IM repository locations

If you install ODM directly from IM without going through the launchpad, specify the directories of the installers in the preferences.

  1. Start IM from the Windows Start menu or from a command line.

  2. Click...

      File | Preferences

    ...and specify the repository locations...

      Decision Center /path/to/extract/disk3/WDC
      Decision Server /path/to/extract/disk2/WDS
      Profile templates for WebSphere Application Server /path/to/extract/disk2/OW
      Business Rules Embedded /path/to/extract/disk2/ER

    IM retrieves ODM packages from the specified repository locations.


Run Installation Manager

If you are installing ODM from the Custom installation option of the launchpad, the paths to the repository locations of the various ODM components are automatically set in the IM preferences.

If you are using IM directly, specify the repository locations.

To install ODM with IM:

  1. On the Install Packages page, select...

    • Decision Center
    • Decision Server
    • Business Rules Embedded
    • Profile templates for WebSphere Application Server

    ...then click Next.

    Depending on your needs, you can install one or all of the packages on the same computer.

    You must have both Decision Center and Decision Server installed to run the Decision Center samples and to perform the complete scenario for the Getting Started tutorials.

  2. Review the license agreements for the selected packages, click I accept the terms of the license agreements, and then click Next.

  3. Optional: Click Next to accept the default path for the shared resources directory. Perform this step if ODM is the first product that you install with IM.

  4. Select a package group:

    1. Select Create a new package group to create a new package group for ODM.

      The default package group is ODM85 (For example, /opt/IBM/ODM85), and the name of the package group is IBM ODM.

    2. Click Next to continue.

      For more information see...

  5. To install a new instance of Eclipse, leave the page empty, do not select any directory, and click Next to continue.

    IM installs a new instance of Eclipse at the root of the package group directory.

    If you already have Eclipse installed, to use , install ODM in the existing Eclipse environment.

  6. On the Translations page, select the languages to install for this package, and then click Next.

  7. Select ODM features to install, and then click Next.

  8. Select Application Server Location, and browse to the installation of WAS where you want to deploy the applications, and then click Next. For example...

      /opt/IBM/WebSphere/AppServer

    By default, ODM supports JDK7. If you have an existing WAS that runs JDK6, upgrade your JDK version using the installation option IBM WebSphere SDK Java Technology Edition version 7.0.1.

  9. Select Server Security, and enter a user ID and password for the sample server profile on WAS, and then click Next. For example:

    • User ID: odmadmin
    • Password: odmadmin

    Your user ID and password must not contain any white spaces.

    For security reasons, change your password and remove the temporary response files created by the launchpad after the installation is complete. These files are generated during the installation process in these directories:

      /tmp/IBM_LaunchPad_InstallType_TimeStamp

    After completing the installation of ODM, you use the user ID and password to connect to the WAS administrative console, the Event Widgets and the Events Administration console.

  10. Optional: Select IBM ODM Express if you have the corresponding license, and check the Install option.

    If you want to upgrade from ODM Express to ODM, you cannot use the Modify packages option. Uninstall the Express version completely from your computer and then reinstall it using the launchpad or IM.

  11. On the Summary page, review the selected features before you install the packages, and then click Install.

  12. Wait until the installation is complete, and then click Finish.


Results

By default, ODM is installed under...

The products and features that are installed depend on what you selected in IM.


Install ODM in a compatible IBM product

You can install ODM in a compatible IBM product package group to share functions and a common user interface. You can install ODM in the package groups of one of the following products:

Before you start the installation, set the repository locations of these products are not selected in the preferences of IM.

Review ODM system requirements

  1. When prompted to select a package group in IM, select Use the existing package group.

    IM displays the list of package groups available. The package groups that are not compatible are disabled.

  2. Select the destination package group.

    The installation directory is automatically filled with the path to the selected product.

  3. Continue the installation.


Install ODM in an existing Eclipse environment

IM installs by default a new instance of Eclipse (version 3.6.2.4). However, if you already have a supported version of Eclipse, you can choose to extend it.


Install the required plug-ins and patch level

Before you install ODM in an existing Eclipse environment, make sure that it contains the required plug-ins, and that the current patch level is installed.

Rule Designer requires Eclipse SDK 3.6 with the following up-to-date plug-ins:

These plug-ins are automatically added as dependencies.

Install the appropriate patch level.

  1. Start Eclipse and click Help > Check for updates.

  2. Click Next.

  3. Review the items to be updated and click Next.

  4. Review the license terms, and select I accept the terms of the license agreement.

  5. Click Finish to install the required components.

  6. Click Restart Now if you are prompted to restart Eclipse.


Extend an existing Eclipse

If the required plug-ins are installed, you can extend your current Eclipse environment.

The Eclipse instance to extend must contain an initialization (.ini) file. If there is no such file, create one in the same folder as your Eclipse .exe file. The .ini file must have the same name as the Eclipse executable file. For example, eclipse.exe and eclipse.ini.

The package files are installed in the package group directory that you select, but the package functions are available in your Eclipse.

  1. In IM, when you are prompted to define your Eclipse, select the check box Extend an existing Eclipse.
  2. Browse to your compatible Eclipse IDE installation.
  3. Continue the installation.



Features

Installation Manager automatically enforces any dependencies between features and prevents you from clearing these dependencies.

After you finish installing packages, you can add or remove features from ODM using the Modify Packages wizard in IM.


Decision Center features

Feature Description
Decision Center Author, manage, and test their business and event rules. Includes a repository for storing business and event rules, and web interfaces such as: Decision Center Business Console and Decision Center Enterprise Console The Decision Center Business Console is supported on WAS V8.0. only.
Decision Center for Tomcat Archives to configure Decision Center on Tomcat.

    INSTALL_HOME/teamserver/applicationservers/tomcat
Decision Center for JBoss Archives to configure Decision Center on JBoss.

    INSTALL_HOME/teamserver/applicationservers/JBoss
Decision Center for WebLogic Archives to configure Decision Center on WebLogic.

    INSTALL_HOME/teamserver/applicationservers/WebLogic
Event Widgets for Decision Center Event Capture and Event Replay widgets. Capture events from a production system, and replay a sequence of events, typically on a test system.

Event Charting widgets include the Event Chart Manager widget to create and edit charts, the Event Chart widget to view charts as well as real-time charts, which display the history for events, actions, and filters.

The Event Tester widget provides a way to test the event logic in a business process. This widget is aimed at testing and must be used only on a test installation. Do not use it on a production installation as it might affect performance.

Rule Solutions for Office Create business rules in Microsoft Word or Excel. Copies the installer for Rule Solutions for Office to the installation directory. The executable file for the installer is copied to...

    INSTALL_HOME/Rule Solutions for Office/RuleSolutionsForOffice.exe
Samples and Tutorials Installs the projects for the samples and tutorials, and provides the sample server profile to run the samples and tutorials on WAS.

WAS is a prerequisite for this option.

Local help system Select to access the help contents locally. By default not selected because the help system points to the online information center. Does not work on 64-bit platforms, such as RHEL, that do not have a 32-bit compatibility library installed.


Decision Server features

Feature Description
Decision Server Rules
Rule Designer Development environment within Eclipse. Offers views and editors available from the Rule perspective in Eclipse.
Rule Designer > Scorecard Modeler Extra plug-ins integrated into Rule Designer for creating scorecards to be integrated and shared them across multiple platforms.
Rule Execution Server Execution platform for business rules that embeds the rule engine. Provides a console to manage and monitor execution of business rules. You can configure and deploy Rule Execution Server on a different WAS profile, or install it on other supported application servers.

Rule Execution Server for Tomcat Archives to configure Rule Execution Server on Tomcat.

    INSTALL_HOME/executionserver/applicationservers/tomcat
Rule Execution Server for JBoss Archives to configure Rule Execution Server on JBoss.

    INSTALL_HOME/executionserver/applicationservers/JBoss
Rule Execution Server for WebLogic Archives to configure Rule Execution Server on WebLogic. copied to...

    INSTALL_HOME/executionserver/applicationservers/WebLogic
Decision Server Events WAS is a prerequisite for Decision Server Events.
Event Designer A development environment within Eclipse to design, develop, test, deploy, and monitor event applications. Event Designer is available from the Event perspective in Eclipse.
Runtime > Event Runtime Execution platform that manages real-time business event coordination. Requires WebSphere eXtreme Scale. Must be deployed on WAS. License types include:

Non-production Use ODM for development. Can be deployed only as part of development and test environment for internal non-production activities.
Production Use ODM for production.

Runtime > Event Tester Enabler If selected, Event Tester widget is available.
Runtime > Event Connectors (Legacy) Data connections between the event runtime and external systems. Legacy connectors include email and ftp.
Event Widgets for Decision Server Replay production events on on a test system. Event Tester widget tests the logic a business process. For performance reasons, is not suitable for aproduction installation.
Integration Components Enables WebSphere ESB and WebSphere Message Broker to send and receive data from Decision Server Events.
Shared components
Samples and Tutorials Projects for the samples and tutorials. Provides sample server profile. WAS is a prerequisite.
Update sites for installation into other Eclipse products Compressed files containing the Eclipse update sites, and a copy of the Designer plug-ins, for installing Rule Designer and Event Designer features into an existing Eclipse.
Local help system Select to access the help contents locally. By default not selected because the help system points to the online information center. Does not work on 64-bit platforms, such as RHEL, that do not have a 32-bit compatibility library installed.
Profile templates for WAS Required for ODM on WAS. Events and rules profile templates.
Business Rules Embedded Configure behavior of a Eclipse Rich Client Platform (RCP) or a Dojo-based web applications.


Install in silent mode

  1. Edit...

      /path/to/diskX/IM/responsefiles/IM_Silent.xml

    ...and replace...

      !IM_REPOSITORY!

    ...with the path to the directory where the IM installer is located. For example...

      INSTALL_ROOT/diskX/IM

  2. Run one of the following commands:

    • If you are an administrator:

        installc /path/to.IM_Silent.xml -acceptlicense

    • If you are not an administrator:

        userinstc /path/to.IM_Silent.xml -acceptlicense


Set the response file WAS and WXS

WebSphere Application Server and WebSphere eXtreme Scale are prerequisites to the installation of the other ODM packages. You can install them silently using response files.


Set WAS response file

  1. Edit...

      diskX/responsefiles/Prerequisites_WAS_Silent.xml

    ...and replace...

      !WAS_REPOSITORY!

    ...with the path where the WAS installer is located. For example...

      INSTALL_ROOT/disk1/WAS

  2. Replace !WAS_PROFILE_ID! by any string.

    This value is used internally by IM to give a name to the WebSphere Application Server installation profile.

  3. Replace !WAS_HOME! with path to where to install WAS. For example:

      /opt/IBM\WAS

  4. To install WAS in 64-bit mode, set !BIT_64!, Otherwise, delete this line.

  5. Replace !WAS_SDK_FEATURE_BIT_ 32_OR_64! with either...

    • com.ibm.sdk.6_32
    • com.ibm.sdk.6_64

    ...depending on whether you want to install a 32-bit or a 64-bit WAS.


Set WebSphere eXtreme Scale response file

Edit

...and set the value of -OPT installLocation to directory where WAS is installed. For example:


Set the response file for Decision Server and Decision Center

In the same way as you have set up a response file for WebSphere Application Server and WebSphere eXtreme Scale, you can configure a response file for the silent installation of the ODM packages: Decision Center and Decision Server. IM uses response files to run the installation in silent mode. The following procedure explains how to set up the provided response files to run a silent install for Decision Center and Decision Server.

  1. Go to the location where you extracted the ODM installation disks and go to: diskX\responsefiles.

    Response files are available on any disk.

  2. In the file WODM_Silent.xml, replace !WDC_REPOSITORY! and !WDS_REPOSITORY! with the path where the Decision Center and Decision Server installers are located.

    For example: INSTALL_ROOT\disk3\WDC for Decision Center, and INSTALL_ROOT\disk2\WDS for Decision Server.

  3. Replace the variable !WODM_PROFILE_ID! by the value used internally by IM to give a name to the ODM installation profile: ODM V8.5.

    This profile corresponds to the IM profile, not to the WAS profile.

  4. Replace the variable !WODM_HOME! by the path to the directory where you want to install ODM. For example, c:\Program Files\IBM\ODM85.

  5. Replace the variables !ADMIN_USERNAME! and !ADMIN_PASSWORD! by the username and password required by WAS for security purposes.

  6. Replace the variables !WODM_FEATURES_DECISION_CENTER!, !WODM_FEATURES_DECISION_SERVER_RULES!, and !WODM_FEATURES_DECISION_SERVER_EVENTS! with a comma-separated list of the features to install.

    Product List of features
    Decision Center

    • jdk
    • base
    • Decision Center
    • Rule Solutions for Office
    • com.ibm.wdc.rules.samples.feature
    • com.ibm.wbdm.dts.tomcat.feature
    • com.ibm.wbdm.dts.jboss.feature
    • com.ibm.wbdm.dts.weblogic.feature
    • com.ibm.wdc.event.widgets.feature
    Decision Server Rules

    • com.ibm.wds.jdk.feature
    • base
    • com.ibm.wds.updatesites.feature
    • com.ibm.wds.rules.studio.feature
    • com.ibm.wds.rules.res.feature
    • com.ibm.wds.rules.samples.feature
    • com.ibm.wds.rules.scorecard.feature
    • com.ibm.wds.rules.res.tomcat.feature
    • com.ibm.wds.rules.res.jboss.feature
    • com.ibm.wds.rules.res.weblogic.feature
    Decision Server Events

    • com.ibm.wds.jdk.feature
    • base
    • com.ibm.wds.updatesites.feature
    • com.ibm.wds.studio.events.feature
    • com.ibm.wds.events.runtime.feature
    • com.ibm.wds.events.connectors.feature
    • com.ibm.wds.events.integration.feature
    • com.ibm.wds.events.propertiesui.feature
    • com.ibm.wds.event.widgets.feature
    • com.ibm.wds.events.tester.feature


Set the response file for Profile templates for WAS

If Decision Center and Decision Server are to be deployed on WebSphere Application Server, you can set up a response file to install the corresponding profile templates and runtime silently. IM uses response files to run the installation in silent mode. The following procedure explains how to set up the provided response files to run a silent install for Profile templates for WAS.

  1. Go to the location where you extracted the ODM installation disks and go to: diskX\responsefiles.

    Response files are available on any disk.

  2. In the file OW_Silent.xml, replace !OW_REPOSITORY! with the path where the Profile templates for WAS installer is located. For example:

      INSTALL_ROOT\disk1\OW

  3. Replace the variable !WODM_PROFILE_ID! by the value used internally by IM to give a name to the ODM installation profile: ODM V8.5.

    This profile corresponds to the IM profile, not to the WAS profile.


Install ODM silently

After all the response files are set up, you can start a silent installation. The following procedure explains how to perform a silent installation of ODM with IM. The installation must be performed in the shown order.

  1. Install Installation Manager:

    If you are an administrator...

      installc /path/to.IM/Silent.xml -acceptlicense

    If you are not an administrator...

      userinstc /path/to/IM_Silent.xml -acceptlicense

  2. Install WebSphere Application Server:

      cd IM_HOME/eclipse/tools
      ./imcl input /path/to/reponse/files/Prerequisites_Silent.xml -acceptLicense

  3. Install WebSphere eXtreme Scale:

      cd INSTALL_ROOT\WXS
      ./install -options "/path/to/reponse/files/wxssetup.response" -silent

  4. Install the ODM components:
      cd IM_HOME/eclipse/tools
      ./imcl input /path/to/response/files/WODM_Silent.xml -acceptLicense

  • Install Profile templates for WAS:

      cd IM_HOME/eclipse/tools
      ./imcl input /path/to/reponse/files/OW_Silent.xml -acceptLicense


    Install Rule Solutions for Office

    Once the installation of Decision Center is complete, you can manually run the installer for Rule Solutions for Office. If you installed ODM with IM, make sure that you selected the Rule Solutions for Office feature.

    You must have a supported version of Microsoft Office to install Rule Solutions for Office.

    Rule Solutions for Office is an optional component that provides a way for business users to create and edit business rules in Microsoft Word or Excel. The Rule Solutions for Office feature in IM copies the installer for Rule Solutions for Office to the installation directory.

    1. Navigate to INSTALL_HOME/Rule Solutions for Office/
    2. Double-click the RuleSolutionsForOffice.exe file to run it.
    3. Follow the steps in the installation wizard.


    Checking the installation

    After you have finished installing the ODM components, you can verify the content of the installation directory.

    In your file system, go to your INSTALL_HOME folder: for example...

      C:\Program Files\IBM\ODM85

    Use the table below to help you identify the ODM features that are installed on your computer:

    Component Folders
    Decision Server Rules
    Rule Designer studio
    Rule Execution Server executionserver
    Getting started tutorials gettingstarted
    Sample server shared/sampleServer
    .NET engine and migration tool dotnet
    Decision Server Events
    Event Designer connectors, runtime
    Decision Center teamserver, Rule Solutions for Office (optional)
    Business Rules Embedded rules-sdk

    If you have installed the component Profile templates for WebSphere Application Server, the corresponding folders are located in these directories:

    <WAS_InstallDir>/profileTemplates/rules for rules profiles.

    <WAS_InstallDir>/profileTemplates/wbe for events profiles.


    Troubleshooting the installation

    If you encounter difficulties installing ODM, you can check the installation logs or the limitations and known issues technote.

    When you contact IBM support, have the following information...

    • Version of IM installed
    • Components installed and version numbers
    • Operating system
    • IM logs

    Installation logs

    If you run into issues, check the installation logs...

    • Installation Manager:

        /var/ibm/InstallationManager/logs

    • Launchpad:

      • Windows:

          %TEMP%\IBM_LaunchPad_InstallType\

        If the launchpad fails before even starting the installation, no installation type is indicated in the folder name.

      • UNIX:

          /tmp/IBM_LaunchPad_InstallType/

    To find a list of the current limitations and known issues, check the technote Known limitations in ODM V 8.5


    Set up Ant automation

    To deploy RuleApps to Rule Execution Server, automate managerial tasks within Decision Center, and run many of the samples, have Ant installed on your computer.

    The required version of Ant is 1.7.1 (or later). If Ant is not installed, or your version is older than version 1.7.1, set up your environment to use the correct version of Ant. You can download Ant from http://ant.apache.org/, or you can use the Ant 1.7.1 distribution packaged in...

      INSTALL_HOME/shared/tools/ant

    To test and set up your environment to use Ant:

    1. Set the ANT_HOME environment variable to...

        INSTALL_HOME/shared/tools/ant

    2. Set the JAVA_HOME environment variable to the path to your JDK installation (1.6).

    3. Add the following to the PATH environment variable...

        INSTALL_HOME/shared/tools/ant/bin

    4. Test...

        ant -version


    Appendix

    Get started with the Sample Server

    The first time that you start the sample server, a profile (ODMSample) is configured on WebSphere Application Server Network Deployment to run the included samples and tutorials. You can start the sample server with the Start menu shortcut.

    On the start menu, click All Programs > IBM > package_group > Sample Server > Start server. package_group refers to the package group specified in IBM IM during installation. The default package group is ODM V8.5.

    The profile creation takes several minutes to complete. Wait until the build completes successfully.

    • If you are using the sample server profile to run Events, you can use the same username and password to log in to the Event Widgets and to the Events Administration console.

    • Single sign-on (SSO) authentication is activated for the sample server. SSO allows users to log in once and gain access to all applications without being prompted to log in again for each of them. If you use different sign-on credentials for the applications on the sample server, for example when performing certain samples and tutorials, you get an error message when you attempt to sign in to the second application.

      To avoid this issue, sign out of the first console and then sign in to the second console. Alternatively, you can sign in to all of the applications on the server using the credentials that you entered at installation time.



    Get started with the Stand-alone Server

    Before you start the stand-alone server for the first time, make sure that we create your database schema both for Rule Execution Server and Decision Center.

    To start the stand-alone server, choose...

      All Programs > IBM > package_group > Stand-alone Server > Start server

    package_group refers to the package group specified in IBM IM during installation. The default package group is ODM V8.5.

    To use the Events Properties tool (propertiesui) and legacy connectors (email and ftp), perform some additional configuration steps.


    Uninstall ODM

    To uninstall ODM, use the uninstall option of IM.

    Make sure that you stopped all the applications that run with ODM, including the server, any instance of Rule Designer or Event Designer, and the local help process if enabled.

    To uninstall the packages, log in to the system with the same user account that you used to install ODM packages. Make sure that you are using the correct instance of IM to uninstall ODM:

    • If you installed ODM as an administrator, uninstall it using the administrator instance of IM, which is accessible through the IBM IM start menu shortcut.

    • If you installed ODM as a nonadministrator user, uninstall it using the non-administrator instance of IM, which is accessible through the My IBM IM start menu shortcut.

    To be able to uninstall WebSphere Application Server and WebSphere eXtreme Scale properly, delete the ODMSample8500 profiles manually first. These profiles are created when you install ODM using the Sample server installation option of the launchpad.

    A package cannot be uninstalled when another package has a dependency on it, unless the dependent package is also selected to be uninstalled.

    1. Close the programs that you installed with IM.
    2. Launch IM from the Start menu.
    3. Select the components that you want to uninstall, then click Next and Uninstall.


    ODM Express

    Can only use business rules capabilities, not events capabilities, and cannot be used in clustered environment.

      Component name Installable
      Decision Server Rule Designer

      YES

      Event Designer

      NO

      Rule Execution Server

      YES

      Event runtime

      NO

      Event widgets NO
      Decision Center Business Console / Enterprise Console

      YES

      Rule Solutions for Office

      YES

      Event widgets

      NO

      Profile templates for WebSphere Application Server

      NO

      Business Rules Embedded

      NO

      Sample server

      YES

    To upgrade from ODM Express to ODM, first uninstall the Express version completely, and then install ODM.