Install Operational Decision Manager v8.0.5


Installation overview

You can install Operational Decision Manager (ODM) using...

For detailed system and software requirements...

Before starting read Prerequisites.


Installation types

Sample Server installation Install the complete ODM product family, along with the applications and project to run the samples and tutorials.
Standalone Server installation Select packages to install. Configure a single server profile on WAS.
Custom Use Installation Manager to select the components to install. You can manually deploy ODM components on an existing application server or cluster.


Sample Server: development, test, and tutorials

The Sample Server defines a profile on WAS that contains the deployed applications to run the samples and tutorials. You can use the Sample Server to test the different features of ODM. This server includes an embedded Apache Derby database and WAS default messaging as the messaging provider.

The Sample Server does not require any configuration. The profile is created the first time that you start the Sample Server after installing ODM.


Standalone Server: development and production

Install ODM on a single stand-alone WAS.

When installing through the launchpad, requires little or no post-installation configuration. The server profile is created based on a set of parameters entered at installation time. When installation is complete, the profile is created and configured based on the information that you entered. The stand-alone server profile is configured with the relevant augmentations, and the ODM applications such as the Decision Center consoles, Rule Execution Server, and the Event Widgets are ready to use.

In this configuration, the sample and tutorial applications are not available.

Select a database created prior to the installation of ODM. Supported databases are...

For the Event runtime, select the type of messaging service. Options are...


Custom configuration: development and production

The ODM install media includes the following packages...


Installation prerequisites

Before installing ODM verify you have...


Before installing on Linux and AIX

Before installing WAS ND on Linux and AIX systems, set the process resource limits in...

If the value for the number of open files is too low, errors can occur when opening files or establishing connections. To change the open file limit, set...


Download and unarchive install media

ODM install media consists of multiple *.tar files. Extract all the tar files into the same directory.

For AIX, the native UNIX tar command does not support long file names. Use the GNU version of tar. On Windows, the cygwin version of tar works well.

Use short directory paths. For example: C:/IBM/ODM.

Running the launchpad directly from the DVDs can be slow. To improve performance, copy DVD contents to your computer before starting the launchpad.

If you use WinZip to extract the tar files, go to...

...and deselect...


Windows considerations

On Windows 7, if not installing ODM as an administrator, you might encounter difficulties running certain programs. To avoid, install ODM in a directory other than...

For example, something like...

On Windows 7, to install ODM with a version of Installation Manager already installed on your machine, verify the setting...

...is not set at the lowest value. If this value is set to the minimum, the launchpad is launched automatically in administrator mode and installs a new version of Installation Manager in addition to the one that is already installed.

For all other Windows versions, to install as an administrator you must have a user ID that belongs to the Administrator group.


Install from ODM launchpad

The launchpad installs...

  1. IBM Installation Manager (if not already on computer)
  2. WAS ND
  3. eXtreme Scale
  4. IBM Decision Center
  5. IBM Decision Server
  6. Server profile
  7. Samples and tutorials (Sample Server)

The Custom installer provides links to install the prerequisites manually, and prompts you to select the features within each package to install. For example, you can select the business rules archives for an application server other than WAS.

To start the ODM launchpad, cd to the root directory of the DVDs or extracted files.

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

You can install ODM either as a regular user or as an administrator. User privileges depend on the account used to log in to the computer.

If you install ODM using the launchpad custom installer, you can choose to...

To start the launchpad on Windows, cd INSTALL_ROOT and run either...

The choice of one or the other does not determine whether you install a 32 or 64-bit ODM, but whether the launchpad is run in 32 or 64-bit mode.

In Custom installation mode, you can select whether to install a 32-bit or a 64-bit WAS. In typical modes, the installation is silent and chooses the version that matches the operating system.

On Windows 7 right-click the launchpad.exe, and select...

On Linux, run...

Select the type of installation to perform:


Install ODM and the Sample Server

The Sample Server installer...

If you cancel the installation before completion, the files and folders already copied are not deleted. Before running the launchpad again...

  1. Use Installation Manager to uninstall ODM
  2. Manually delete the remaining files

If you do not have a license for IBM Decision Center, you can still use IBM Decision Center, but only to execute samples and tutorials.

  1. On the Welcome page of the launchpad, in the Sample Server section, click Next.

  2. Keep the default installation directory for ODM or click Browse to specify a different location.

  3. Enter a user ID and password for logging into the WAS administration console and other applications such as the Event widgets. For example:

      User ID odmadmin
      Password odmadmin

    Your user ID and password must not contain any space characters.

  4. Click Next.

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

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

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

    The installation takes a long time to complete. Do not close the launchpad even if the progress bar shows 100% completion. Wait until you get the message:

      Installation completed successfully

    This message indicates that the installation of the prerequisites and ODM is complete.

  7. Click Close, and then click Exit.

  8. Click OK to confirm that you want to exit the launchpad.

By default, ODM and the prerequisites are installed in...

ODM WAS_HOME/ODM801/ODM
WebSphere Application Server
WebSphere eXtreme Scale
WAS_HOME/ODM801/WAS/AppServer

After running the Sample Server installer in the launchpad, the following elements are installed...

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

The first time that you start the Sample Server using the start menu shortcut, a profile is configured on WAS Network Deployment to run the included samples and tutorials.


Install ODM and the Standalone Server

Use the Standalone Server installer to install ODM on a single server.

To install ODM on a stand-alone server, you must have an existing database for the business rules and event rules repositories. ODM supports the following database types...

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

In the Standalone Server installer, select ODMs to install and for which you have a license. The Standalone Server option also installs the prerequisite software:

The launchpad installs ODM and the prerequisite software silently.

The stand-alone server installer also prompts you to enter a set of parameters to create a single stand-alone server on WAS.

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...

  1. Uninstall ODM products that the launchpad has already installed using Installation Manager
  2. Manually delete the remaining files before running the launchpad again


Install ODM with Standalone Server

  1. On the Welcome page, in the Standalone Server section, click Next.

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

    1. Keep the default installation directory for ODM or click Browse to specify a different location.

    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 space characters.

    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 Standalone server:

      • Recommended port values

        Ensures that the port numbers are different from any other running installations of WAS on the computer.

      • Default WAS port values

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

  3. Click Next.

  4. Specify the database to use:

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

  5. Click Test Connection to verify the values entered are correct.

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

  6. Click Next.

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

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

  8. Click Next.

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

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

By default, ODM and the prerequisites are installed in the following directories:

After running the Standalone installer in the launchpad, depending on what you have selected, the following elements are installed on your computer:

After completing the installation of ODM, the Standalone Server is configured, and you can start the server using the start menu shortcut.

However, to use the events Properties tool and legacy connectors, perform additional configuration steps.


Install a custom configuration

Use the Custom installer to...

Use the launchpad to verify you have the correct versions of the prerequisites installed.


Install a custom configuration

  1. On the Custom installation page, specify the user privileges for the installation of the prerequisites and ODM.

    If you are an administrator or root user and you want to install as an administrative user, keep the default check box selected...

      Install in a shared location for multiple users

    If you are not an administrator or to install to your own user name, clear the check box.

    Install WAS and ODM with the same user privileges.

  2. If you do not have Installation Manager installed, click...

      Install IBM Installation Manager

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

  3. Click Install IBM WAS Network Deployment to run IBM Installation Manager.

    1. Follow the steps in Installation Manager.

      Do not select the option...

        Sample applications

      ...in the WAS feature tree. This prevents the event runtime from running correctly.

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

      No profile has been created yet.

      By default WAS is installed in...

        WAS_HOME/WebSphere/AppServer

  4. Click Install WebSphere eXtreme Scale to install a supported version of eXtreme Scale using the installation wizard.

    1. Follow the steps in the installation wizard.

    2. When prompted to indicate the installation directory, verify the path corresponds to your WAS directory. For example, C:\IBM\WebSphere\AppServer. You must 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.

    3. At the end of the installation, clear Launch the Profile Management Tool console, and then click Finish.

  5. After installing all the prerequisites, install the ODM packages using one of the following options:

    • Click IBM Decision Center to install Decision Center.

    • Click IBM Decision Server to install Decision Server.

    • Click IBM Business Rules Embedded to install Business Rules Embedded.

    Business Rules Embedded requires an IBM Decision Server license and the installation of Eclipse 3.6.

  6. Click Install Decision Manager to install all three products.

    The Installation Manager is launched.


Install using Installation Manager

In Installation Manager you can choose the packages and products of ODM to install. You must have a license for ODMs you intend to install.

Installation Manager enables you to install only a subset of ODM. In Installation Manager, you can also customize your installation for specific configurations, for example:

You can install...

  • Using Installation Manager through the launchpad
  • By invoking Installation Manager directly. Add the repository locations in the preferences.

    If you have the prerequisites already installed, or to install a part of a product that does not require any prerequisites, you can use Installation Manager directly. For example, to install only Rule Designer.

    ODM installable packages include...

      IBM Decision Center Author, manage, and test business rules and event rules.
      IBM Decision Server Development and runtime environments
      IBM Business Rules Embedded Development environment for adding business rules functionality to applications. Requires IBM Decision Server license.

    You can install ODM as an administrative user (root) or as a non-administrative user (non-root). Use the same user to install all required software. For example you must install ODM and WAS using the same user.

    • To install with an administrator user (root), run the install executable
    • To install with a non-root user, run the userinst executable
    • To install with a group of users, run the groupinst executable

    groupinst install offerings with different accounts, as long as both accounts are members of the same group.


    Package groups and the shared resources directory

    Installation Manager always installs ODM in a package group, which is used to group multiple packages into one manageable location.

    When installing ODM, Installation Manager proposes a default Package group and a Shared resources directory.

    A package group is a directory where compatible packages share common components such as a user interface or workbench.

    You can create a new package group or install the packages into an existing compatible package group. Some packages cannot share a package group, in which case the option to use an existing package group is disabled.

    You might want to install in an existing package group if you have installed supported versions of compatible products such as IBM Integration Designer or Rational Application Developer, or Rational Software Architect, 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 specific to ODM.

    The shared resources directory is where Eclipse plug-ins and other files are located so that they can be used by one or more product package groups. You can specify the shared resources directory only the first time that you install a package. The name of the shared resources directory depends on the first product that you have installed.

    You cannot change the directory location until you uninstall all packages.

    Installation Manager manages the contents of the shared resources directory. You must 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.

    The languages to select only apply to Eclipse features. For each language that you select, a language pack is installed, which allows you to start Eclipse in the locale for these languages.

    If you are extending an existing Eclipse, you must 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.


    Set up Installation Manager preferences

    If you have not run the launchpad, you can install the product directly using Installation Manager.

    You must manually set the repository locations in Installation Manager to retrieve ODM packages, except if you are running Installation Manager from the launchpad.

    For general information on Installation Manager, see IBM Installation Manager information center.

    1. Start Installation Manager from the Windows Start menu or from a command line.

    2. Click...

        File | Preferences

      ...and define the repository locations for IBM Decision Server, IBM Decision Center, and IBM Business Rules Embedded.

      Installation Manager retrieves product packages from specified repository locations.

      You can set repository locations using repository preferences

    3. On the IBM Installation Manager main page, click Install.

    4. Continue the installation of ODM.


    Install ODM with Installation Manager

    1. Install prerequisites

    2. Set the repository locations.

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

      • IBM Decision Center
      • IBM Decision Server
      • IBM Business Rules Embedded

      ...and then click Next. You can install one or all of the packages on the same computer.

      To run the Decision Center samples and tutorials, co-locate Decision Center and Decision Server on the same host.

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

    5. Only applicable if ODM is the first product installed using Installation Manager. Click Next to accept the default path for the shared resources directory.

    6. Select a package group:

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

        The default package group is ODM801. For example...

          C:\IBM\ODM801

        The name of the package group is IBM ODM.

      2. Click Next to continue.

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

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

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

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

      A set of features is already selected by default.

    10. Browse to your installation of WAS where you want to deploy the applications, and then click Next. For example...

        WAS_HOME/WebSphere/AppServer

    11. 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 space characters.

      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.

    12. On the Summary page, review the selected features before installing the packages, and then click Install.

      To change anything on a previous page, click Back and make your changes before clicking Install.

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

    By default, ODM is installed in...

      WAS_HOME/ODM801

    The products and features installed depend on what you selected in Installation Manager


    Install in a compatible IBM product

    When you install packages with Installation Manager, you can choose to install the packages into an existing package group. You might want to install compatible packages in the same package group to share functions between products and share a common user interface.

    You can install ODM in the package groups of the following products:

    • IBM Integration Designer
    • Rational Application Developer
    • Rational Developer for z (RDz)
    • Rational Software Architect

    Before installing ODM in the package group of these products, verify the repository locations of these products are not selected in the preferences of Installation Manager.

    To check the supported versions of these products, see...

    Install in a compatible product

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

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

    2. Select the package group to install in.

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

    3. Continue the installation.


    Install in an existing Eclipse

    By default, when you install ODM, Installation Manager installs a new instance of Eclipse. However, if you already have a supported version of Eclipse, you can choose to extend it.

    This procedure does not apply to Eclipse instances from other IBM products.


    Install the required plug-ins

    Before installing ODM in your Eclipse installation, verify it contains the required plug-ins.

    If you have an installation of Eclipse 3.6, you must install the following additional features:

    • GEF 3.6 (Graphical Editing Framework)
    • EMF 2.6 (Eclipse Modeling Framework)
    • BIRT 2.6 (Business Intelligence and Reporting Tools)
    • DTP 1.8 (Data Tools Platform)

    Rule Designer also requires WTP 3.2 (Web Tools Platform) and XSD 2.6 that are automatically added as dependencies.


    Install into existing Eclipse

    1. Start Eclipse and navigate to Help > Install New Software.

    2. In the Install wizard, in the Work with field, select...

        Helios - http://download.eclipse.org/releases/helios

      Eclipse checks for available features.

    3. Make sure that the Group items by category check box is selected.

    4. After Eclipse has downloaded available features, select the following categories and features:

      • Business Intelligence, Reporting and Charting > BIRT Framework
      • Database Development > Data Tools Platform Enablement Extender SDK
      • Modeling > EMF - Eclipse Modeling Framework SDK
      • Modeling > Graphical Editing Framework GEF SDK

      If you install a localized version of Rule Designer, you can download the language packs for the required plug-ins.

    5. Click Next.

      Eclipse calculates the dependencies and requirements.

    6. Review the items to be installed and click Next.

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

    8. Click Finish to install the required components.

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


    Extend an existing Eclipse

    Install ODM in an existing Eclipse.

    Before starting the installation with Installation Manager, verify your Eclipse version is compatible and that it contains the plug-ins and features required for Rule Designer and Event Designer.

    If you are installing Business Rules Embedded, verify you use Eclipse 3.6.

    The Eclipse instance to extend must have an initialization (.ini) file. If there is no initialization file, you must 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.

    You can extend an existing version of Eclipse using Installation Manager.

    When you extend Eclipse, the package functions are available in your Eclipse, but the package files are installed in the package group directory that you selected.


    Extend existing Eclipse

    1. In Installation Manager, when 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.


    Selecting the features to install

    When you install ODM using Installation Manager, you can select the features that you want within each package.

    A default set of features is selected for you but you can add or remove features depending on your needs.

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

    After you have finished installing the packages, you can still add or remove features from your product by running the Modify Packages wizard in Installation Manager.


    Decision Center

    Feature Description
    Decision Center Decision Center Business Console
    Decision Center Enterprise Console
          Installation artifacts for other application servers | Decision Center for Tomcat /teamserver/applicationservers/tomcat
          Installation artifacts for other application servers | Decision Center for JBoss /teamserver/applicationservers/JBoss
          Installation artifacts for other application servers | Decision Center for WebLogic /teamserver/applicationservers/WebLogic
          Event Widgets for Decision Center Event Capture; Event Replay; Event Chart Manager; Event Chart; Event Layout; Event Tester
    Rule Solutions for Office (for Windows only) Create business rules in Microsoft Word or Excel. Installer is...

      INSTALL_HOME/Rule Solutions for Office/RuleSolutionsForOffice.exe
    Samples and Tutorials Installs projects for samples and tutorials. Provides sample WAS server profile.


    Decision Server features

    Feature Description
    Decision Server Rules
    Rule Designer Development environment within Eclipse to design business rule applications. Available from the Rule perspective in Eclipse.
    Rule Designer > Scorecard Modeler Set of additional plug-ins integrated into Rule Designer. Create scorecards, integrate them into your business rules, and share them across multiple platforms.
    Rule Execution Server Execution platform for business rules that embeds the rule engine. Provides a console to manage and monitor the execution of business rules.

    By default, installed on the sample server profile on WAS. After completing the installation of ODM, you can also configure and deploy Rule Execution Server on a different WAS profile, or install it on other supported application servers.

    Select the type of license that you have:

    • Non-production License: Select this option to use ODM for development purposes.

      This license can only be deployed as part of development and test environment for internal non-production activities.

    • Production License: Select this option to use ODM for production.

    Rule Execution Server: Installation artifacts for other application servers > Rule Execution Server for Tomcat Archives to deploy Rule Execution Server on Tomcat. The archives are copied to /executionserver/applicationservers/tomcat.
    Rule Execution Server: Installation artifacts for other application servers > Rule Execution Server for JBoss Archive for deploying Rule Execution Server on JBoss. The archives are copied to /executionserver/applicationservers/JBoss.
    Rule Execution Server: Installation artifacts for other application servers > Rule Execution Server for WebLogic Archive for deploying Rule Execution Server on WebLogic. The archives are copied to /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 The event runtime is an execution platform that manages real-time business event coordination. The event runtime requires WebSphere eXtreme Scale and must be deployed and configured on WAS.

    Select the type of license that you have:

    • Non-production License: Select this option to use ODM for development purposes. This license can only be deployed as part of development and test environment for internal non-production activities.

    • Production License: Select this option to use ODM for production.

    Runtime > Event Tester Enabler If Event Tester Enabler is selected, then the Event Tester widget is available.
    Runtime > Event Connectors (Legacy) Event connectors provide data connections between the event runtime and external systems. Legacy connectors include email and ftp.
    Event Widgets for Decision Server By using the Event Capture widget and the Event Replay widget, you can capture events from a production system, and replay a sequence of events, typically on a test system.

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

    Integration Components You can install integration components into the tooling of WebSphere ESB and WebSphere Message Broker to allow these products to send and receive data from Decision Server Events.
    Shared components
    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.

    Update sites for installation into other Eclipse products Provides ZIP files containing the Eclipse update sites (and a copy of the Designer plug-ins) to install Rule Designer and Event Designer features into an existing Eclipse. This provides an alternate way of installing the Designer plug-ins into a supported Eclipse after the installation of ODM.
    Local help system By default this feature is not selected because the help system points to the online information center.

    You can select the Local help system option if you prefer accessing the help contents locally. To use the local help system, you only need an Internet connection the first time to download the help contents from the web. After downloading the help contents, you must set up the local help.

    The local help system does not work on 64-bits platforms, such as Red Hat Enterprise Linux (RHEL), that do not have a 32-bits compatibility library installed.


    Business Rules Embedded features

    With Business Rules Embedded, you can use business rules to dynamically configure the behavior of an Eclipse Rich Client Platform (RCP) application or a Dojo-based web application.

    Business Rules Embedded provides authoring components that support the creating and editing of business rules in Eclipse and Dojo environments. The SDK also provides an API for exporting the resulting rule projects to a full ODM system.

    The Business Rules Embedded application programming interfaces (APIs) support the following operations:

    • Generate a Business Object Model (BOM) from an XML schema.

    • Use the BOM to create a default vocabulary for a locale.

    • Create business rules individually or in decision tables.

    • Generate a rule project or a ruleset archive from a set of business rules.

    • Deploy and execute the ruleset archive on a licensed Rule Execution Server.

    • Export a rule project for import and editing in Rule Designer or Decision Center.

    Business Rules Embedded comes with two sample applications:

      xRules end-to-end RCP application that shows you how to edit, build, deploy, execute, and export simple business rulesets.
      wRules Dojo web application that shows you how to use the Dojo- based business rule and decision table editors.

    The SDK also includes a set of API tests that show you how to build, deploy, execute, and export the rulesets that are produced using either authoring environment.

    Source code is included for the sample applications and API tests. You can use the code in building your applications.


    Install in silent mode

    In some cases, ODM has to be installed within a specific configuration on multiple machines. The GUI installer makes the installation simple to perform on a single machine, but difficult and cumbersome to repeat on multiple machines. You can install ODM product packages by running Installation Manager in silent installation mode to automate the process, and deploy ODMs to multiple systems.

    You perform a silent installation by running Installation Manager with response files that correspond to ODMs to install. Template response files are provided with the installer to help you perform a silent install.

    You can install Installation Manager silently with the Installation Manager installer, and then use it to install silently ODM packages.

    This procedure explains how to install Installation Manager in silent mode. In this mode, there is no interaction with the Installation Manager user interface.

    ODM is bundled with Installation Manager version 1.6.0. Installation Manager version 1.5.2 or higher is required to install the ODM products.

    To install Installation Manager silently:

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

      The IM directory is available from any disk. If you use Linux 64-bits, the directory is IM64.

    2. cd diskX\responsefiles.

      The responsefiles directory is available from any disk.

    3. In the file IM_Silent.xml, replace !IM_REPOSITORY! with the path to the directory where the Installation Manager installer is located. A typical value is: INSTALL_ROOT\diskX\IM.

    4. 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 for required software

    WAS and WebSphere eXtreme Scale are prerequisites to the installation of the other ODM packages. In particular, WebSphere eXtreme Scale is required to install Decision Server Events. You can install them silently using the provided response files.

    Installation Manager 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 installation for WAS and WebSphere eXtreme Scale.

    Set up the response file for WAS

    1. Go to...

        ODM_INSTALL/diskX/responsefiles

      Response files are available on any disk.

    2. In the file Prerequisites_WAS_Silent.xml, replace !WAS_REPOSITORY! to the path where the WAS installer is located. For example:

        INSTALL_ROOT\disk1\WAS.

    3. Replace the variable !WAS_PROFILE_ID! by any string.

      This value is used internally by Installation Manager to give a name to the WAS installation profile.

    4. Replace the variable !WAS_HOME! by the path to the directory where you want to install WAS. For example:

        c:\IBM\WAS

    5. Replace the variable !BIT_64! by the value indicated in the file to install WAS in 64-bit mode. Otherwise, delete this line.

    6. Replace the variable !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 up the response file for WebSphere eXtreme Scale

    1. Go to...

        ODM_INSTALL/diskX/responsefiles

      Response files are available on any disk.

    2. Set the value of -OPT installLocation in the file wxssetup.response.xml to indicate the path to the directory where WAS is installed. For example:

        c:\IBM\WAS


    Set the response file for Decision Server and Decision Center

    1. cd ODM_INSTALL/diskX/responsefiles

      Response files are available on any disk.

    2. In the file WODM_Silent.xml, replace...

      • !WDC_REPOSITORY!
      • !WDS_REPOSITORY!

      ...with the paths where the Decision Center and Decision Server installers are located...

      • INSTALL_ROOT\disk3\WDC
      • INSTALL_ROOT\disk2\WDS

    3. Replace the variable !WODM_PROFILE_ID! by any string.

      This value is used internally by Installation Manager to give a name to the ODM installation profile.

      This profile corresponds to the Installation Manager 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:\IBM\ODM801

    5. Replace the variables...

      • !ADMIN_USERNAME!
      • !ADMIN_PASSWORD!

      ...with the username and password required by WAS for security purposes.

    6. Replace the variables...

      • !WODM_FEATURES_DECISION_CENTER!
      • !WODM_FEATURES_DECISION_SERVER_RULES!
      • !WODM_FEATURES_DECISION_SERVER_EVENTS!

      ...with the 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


    Install ODM silently

    After all the response files have been set up, you can start a silent install.

    The following procedure explains how to perform a silent install of ODM with Installation Manager. The installation should be performed in the shown order.


    Procedure

    1. To install Installation Manager:

      • If you are an administrator, type:

          installc /path/to/IM_Silent.xml -acceptlicense

      • If you are not an administrator, type:

          userinstc /path/to/IM_Silent.xml -acceptlicense

    2. To install WAS:

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

    3. To install WebSphere eXtreme Scale:

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

    4. To install the ODM packages.

        cd Installation_Manager/eclipse/tools
        ./imcl input /path/to/WODM_Silent.xml -acceptLicense


    Troubleshooting the installation

    If you encounter difficulties installing ODMs, you can check the installation logs or the limitations and known issues technote. You can find general information on Installation Manager and how to use it in the IBM Installation Manager information center.

    When contacting IBM support, verify you have the following information at hand:

    • Version of Installation Manager installed
    • Offerings installed and these version numbers
    • Operating System
    • Installation Manager logs


    Installation logs

    • Installation Manager:

      • Windows 2000, XP, and 2003:

          C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager\logs

      • Windows Vista, 7, and 2008:

          C:\ProgramData\IBM\Installation Manager\logs\.settings\logs

      • UNIX:

          /var/ibm/InstallationManager/logs

    • Launchpad:

      • Windows:

          %TEMP%\IBM_LaunchPad_<InstallType>\

        %TEMP% is the environment variable that defines the location of your Temp directory. <InstallType> refers to the type of installation that you selected. If the launchpad fails before even starting the installation, no installation type is indicated in the folder name.

    • UNIX:

        /tmp/IBM_LaunchPad_<InstallType>/


    Limitations and known issues

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


    Install Rule Solutions for Office

    After completing the installation of Decision Center using the launchpad or Installation Manager, you can then manually run the installer for Rule Solutions for Office.

    If you installed ODM using Installation Manager, verify 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 Installation Manager copies the installer for Rule Solutions for Office to your installation directory.


    Procedure

    1. Navigate to /Rule Solutions for Office/

    2. Double-click the RuleSolutionsForOffice.exe file to run it.

    3. Follow the steps in the installation wizard.


    Checking your installation

    You can find out what products of ODM you have installed through the launchpad and Installation Manager, by looking at the installation directory.

    After running the launchpad or Installation Manager, you can check what products you installed by looking at the folder on your computer, for example C:\IBM\ODM801.

    The folders under can be used to identify the features of ODM. Use the table below to help you identify what is installed on you 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


    Set up your environment to automate processes

    You must ensure that you have the correct version of Ant and that it is configured correctly.

    You must have version 1.7.1 (or later) of Ant correctly set up on your system to deploy RuleApps to Rule Execution Server, automate managerial tasks within Decision Center, and run many of the samples. If Ant is not installed, or your version is older than version 1.7.1, you must 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 at...

      /shared/tools/ant


    Automate process

    To test and set up your environment to use Ant:

    1. Verify ant version

        ant -version

    2. Set the ANT_HOME environment variable to...

        /shared/tools/ant

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

    4. Add the following directory to PATH...

        /shared/tools/ant/bin

    What to do next...

    Sample Server installation No configuration is required to develop, test, and run the tutorials and samples
    Standalone Server installation No configuration is required except for certain Event features
    Custom installation Configure the ODM applications on a production server.


    Get started with the Sample Server

    The first time that you start the Sample Server, a profile, ODMSample, is configured on WAS Network Deployment to run the included samples and tutorials. You can start the sample server using the start menu shortcut.

    On the start menu, click...

      All Programs | IBM | package_group | Sample Server | Start server

    The default package group is ODM V8.0.1.

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

    You can perform a number of introductory tasks using the environment that is installed for you by the Sample Server installer:

    • Perform the Getting started tutorials, and other component specific tutorials.
    • Run the samples from the Samples Console in Eclipse.

    If you are using the Sample Server profile to run Events, you can also use the same username and password to login 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, you must 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 Standalone Server

    After running the launchpad using the Standalone Server installer, you can start the stand-alone server using the start menu shortcut.

    On the start menu, click...

      All Programs | IBM | package_group | Standalone Server | Start server

    The default package group is ODM V8.0.1.

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


    Use your application in production

    Rule Designer and Event Designer are installed and you can start designing your application in Decision Server.

    Depending on your company.s needs and on ODMs of ODM that you want to use, some configuration is required:

    • To execute your rule-based application.
    • To execute your application using event processing.
    • For business users to edit and test rules in Decision Center,
    • To execute your application on a z/OS platform, install the required additional files using the SMP/E tool.
    • For business users to edit and test rules in Decision Center for z/OS, install the required additional files using the SMP/E tool

    To get a better understanding of the development lifecycle using ODM,


    2.11. Uninstall ODM

    To uninstall ODM after using the launchpad or Installation Manager, you must uninstall each product separately and in a specific order.

    Before uninstalling ODM, verify you have 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, you must log in to the system using the same user account used to install ODM packages. Make sure that you are using the correct instance of Installation Manager to uninstall ODM:

    • If you installed ODMs as an administrator, you must uninstall using the administrator instance of Installation Manager, which is accessible through the IBM Installation Manager start menu shortcut.

    • If you installed ODMs as a non-administrator user, you must uninstall using the non-administrator instance of Installation Manager, which is accessible through the My IBM Installation Manager start menu shortcut.

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

    You must uninstall each product separately and in a specific order. You can use Installation Manager to uninstall ODMs except for WebSphere eXtreme Scale.


    To uninstall ODMs

    1. Close the programs that you installed using Installation Manager.

    2. Uninstall IBM Decision Center and IBM Decision Server using Installation Manager.

      For more information on how to uninstall using Installation Manager

    3. Uninstall WebSphere eXtreme Scale using the installation program wizard

      You must uninstall WebSphere eXtreme Scale before uninstalling WAS.

    4. Uninstall WAS using Installation Manager.

      The uninstallation can take some time to complete.