Installing components locally

You can install Operational Decision Manager components locally, notably for development purposes, by using the Installation Manager wizard mode.

1. Add the location of your file repositories in Installation Manager. You can review what disks contain your product components at the end of the Obtaining the installers topic.
   1. Open Installation Manager.
   2. In the Preferences menu, add the paths to the repositories.
   3. Click Apply, and then OK.
2. On the Installation Manager welcome page, select Install.
3. Select the installation packages that you want to install, and then click Next.

   If your application server is WebSphere® Application Server, you should also select the profile templates that correspond to the Operational Decision Manager component you want to install. The profile templates make the configuration of Decision Server and Decision Center on WebSphere Application Server much easier.

4. Review and accept the terms of the license agreement, and then click Next.
5. Specify a package group name and an installation directory:
   1. Select an existing or create a new package group name. A package group name is a directory in which product packages share resources with other product packages in the same group. The default package group name is Operational Decision Manager 8.9.1.
   2. Enter an installation directory path. The installation directory is where you install the product components.
      Tip: To avoid user privilege conflicts in Windows 7, change the default installation directory to a directory outside of Program Files and Program Files (x86).
   3. Click Next.
6. Optional: Select Extend an existing Eclipse if you want to later install Decision Server Rules directly into an existing, compatible version of Eclipse. Then click Next. To install into an existing Eclipse outside of Installation Manager, you can alternatively select the Eclipse update sites in step 8.

   Your Eclipse must have the appropriate patches and must contain an initialization (.ini) file. If there is no such file, create one in the same folder as your Eclipse executable file (.exe). See Install into an Existing Eclipse instance for more guidance.

   In Decision Server Insights, the necessary Eclipse update sites are automatically installed to the <InstallDir>/studio/update-sites directory.

7. Select the product interface languages to install. Then click Next. A language pack is installed for each language that you select so that you can start Eclipse in the locale for these languages. English is the default language and is always installed.
8. Select the product features that you want to install. Then click Next.
   Tip: The local help system includes the local documentation and Eclipse contextual-sensitive help. Select Local help system if you plan to use the documentation locally or in a shared network. By default this feature is not selected.
9. Complete the common configurations page:
   • For Decision Server Rules and Decision Center:
     1. Under Liberty Server Location, navigate to your installation of WebSphere Application Server Liberty. For example, enter: <IBM_InstallDir>/wlp. Then click Next.
     2. Select your license type, the purpose of your installation, and the unit of measurement for your license. Then click Next. For information about license types and the units of license measurements, see Licensing.
   • For Decision Server Insights, select one of the following options and click Next:
     • I intend to create a runtime server (as well as possibly other server types) for use in production
     • I intend to create a runtime server (as well as possibly other server types) for use in non-production
     • I don't intend to create a runtime server
10. Review the summary of the features you are about to install and then click Install.
11. When the installation completes, click Finish.