Introduction

You can install Decision Server Insights (DSI) for different purposes. The purpose depends on the stage at which you are at in the life cycle of the solution. There are typically three broad stages in the deployment of a solution: development, testing, and production. In all of these stages you need to install DSI on one or more machines. To create a DSI cluster for testing and production purposes, you must install DSI on multiple machines. For machines that you intend to run a production runtime server you must configure the license type for production during the installation.

Install DSI for development purposes

DSI can be installed for development by configuring Installation Manager (IM) and following the steps in the user interface. For development purposes, you get an IDE and the possibility to test your solution on a development server.

  1. First of all, install IM on your machines. IM is provided on disk 1 of the ODM installers, and can be installed without the user interface by running the following command: disk1\IM\installc.exe -silent -acceptLicense. You can install Installation Manager using the product media, using a file obtained from the Passport Advantage site, or using a file containing the most current version of IM from the IBM download website.
  2. Add the repository location for DSI in the IM preferences (the DSI repository (repository.config) is on disk 4 of the ODM installers).
  3. Start IM:
    a. In the IM UI, change the shared resource directory to the location that IM uses, for example C:\IBMIM\IMShared.
    b. If the host machine runs Windows, change the installation directory to remove Program Files.
    c. Select the features you want to install:

    Features page for DSI install

    d. In the Common Configurations page, choose the option that best fits the use case of the target host. The most common option for development is I don’t intend to create a Runtime server.

    Common Configurations page for DSI install

Note: You can extend an existing Eclipse on your computer with Insight Designer. To do this, select the update sites directory in IM and apply it after installing DSI. When you have installed the update site, it is possible to install Insight Designer on top of an Eclipse IDE on another machine without reinstalling DSI.

Install DSI for testing and production purposes

If you want to create a cluster of servers where you can test your solutions you might not want to do all of these steps in the IM UI on multiple machines. In this case, you can automate the installation by using the silent mode of IM. These commands can be used in scripts so that you can install/update/uninstall DSI in an automated way.

To be able to create a new cluster for testing and production purposes you must install IM and DSI on all of the host machines. You can install both in silent mode.

How to install a DSI cluster in silent mode if you can run IM in GUI mode on a network host

  1. Run the following command on one machine to get a response file for IM, which you can then use for all of the other hosts:
    disk1/IM/installc -record /home/user/myresponsefiles/im_responsefile.xml -skipInstall /opt/IBM/IM
  2. Install IM silently on all of the hosts by using the response file:
    disk1/IM/installc input /home/user/myresponsefiles/im_responsefile.xml -log /home/user/silent_install_log.xml -acceptLicense
    If you want to install a nonadministrator instance of IM only for the current user, use userinstc. For example:
    disk1/IM/userinstc input /home/user/myresponsefiles/im_responsefile.xml -acceptLicense
  3. Add the repository location for DSI in the IM preferences (the DSI repository (repository.config) is on disk 4 of the ODM installers).
  4. Create a response file for installing DSI:
    You can record your steps in the IM GUI:
    $IM_HOME/eclipse/IBMIM -record /home/user/myresponsefiles/dsi_responsefile.xml -skipInstall /opt/IBM/ODMInsightsXXX
    Tip: A DSI cluster is likely to have machines that host runtime servers and machines that do not host runtime servers. DSI in production, requires that the software license is notified of each runtime server. To make life easier, you can make two response files: one file for hosts that you do intend to run a runtime server, and another file for hosts that you do not intend to run a runtime server (these hosts can run a catalog, inbound, or outbound server or any combination of these).
  5. Open and modify the response file(s) and clearly identify the difference between the response file that is intended for machines hosting a runtime server for use in production, and the response files that are not.
    /home/user/myresponsefiles/dsi_runtime_responsefile.xml
    /home/user/myresponsefiles/dsi_noruntime_responsefile.xml
    The response files include a number of variables that you can check/modify.
    Two sets of features are generated by the command (default and all) that you can use to select features. You can create a custom set of features if you need, and set a features variable value to this set.
    Note: The names of the features included in the install are:
    com.ibm.cis.cisdev.feature – Sample server
    com.ibm.cis.designer.feature – Insight Designer
    com.ibm.cis.designer.sample.feature – Tutorial and sample projects
    com.ibm.cis.designer.wdt.feature – WebSphere Application Servers Developer Tools
    com.ibm.cis.runtime.feature – Insight Server
    com.ibm.cis.updatesite.feature – Update site for Insight Designer
    com.ibm.cis.wdt.updatesite.feature – Update site for WDT
    Documentation – Local Help
  6. Run the installation of DSI silently on each machine. Use the appropriate response file for each host. For example, to use the runtime response file for machines hosting runtime servers in production:
    $IM_HOME/eclipse/tools/imcl -accessRights nonAdmin -input /home/user/myresponsefiles/dsi_runtime_responsefile.xml -silent -acceptLicense

How to install a DSI cluster in silent mode if you don’t want to run IM in GUI mode

If you already installed DSI on a development machine, you can use the template /doc/silent/CIS_silent.xml file, which includes the following variables:
!CIS_REPOSITORY!: The path of your Decision Server Insights repository
!CIS_HOME!: The installation path to which you want to install the product.
You must also change the profile key to match your runtime server option. Leave the default value of ‘true’ if you intend to use the host to run a runtime server in production.

<profile id='Decision Server Insights V8.9.1' installLocation='!CIS_HOME!'>
	<data key='eclipseLocation' value='!CIS_HOME!'/>
	<data key='cic.selector.nl' value='fr, es, it, en, de, nl, pl, pt_BR, ru, ja, ko, sv, zh, zh_TW'/>
    <data key='user.prod.cis' value='true'/>
</profile>

The 3 values for ‘user.prod.cis’ are:

  • ‘true’ – I intend to create a runtime server (as well as possibly other server types) for use in production
  • ‘false’ – I intend to create a runtime server (as well as possibly other server types) for use in nonproduction
  • ‘none’ – I don’t intend to create a container server

You can also generate a response file using the generateResponseFile command if you do not want to run the GUI. For example:
./imcl generateResponseFile -repositories source_repository
./imcl generateResponseFile -connectPassportAdvantage
./imcl generateResponseFile [packageId[_Version]]... -repositories source_repository
./imcl generateResponseFile [packageId[_Version]]... -connectPassportAdvantage
The generated response file installs all packages and fixes that are found in the source repositories or in Passport Advantage.

A response file from the generateResponseFile command includes the following variables:
<variable name='sharedLocation'
<variable name='installLocation'
You must also change the profile key to match your runtime server option. Leave the default value of ‘true’ if you intend to use the host to run a runtime server in production:

<profile id='Decision Server Insights V8.9.1' installLocation='${installLocation}'>
    <!-- Common Data: -->
    <!-- User data for Production -->
    <data key='user.prod.cis' value='true'/>
</profile>

How to install a DSI cluster in silent mode in a secure production environment that has no GUI

Run the imcl install command and select the features you want. For example, to install only the runtime feature from PassportAdvantage you can use the following command:
./imcl install package_name,com.ibm.cis.runtime.feature -connectPassportAdvantage, -cPA -iD /opt/ibm/
Tip: You can use the imcl listAvailablePackages command to give you the package name and number. DSI package names start with “com.ibm.websphere.cis.ia.”.
For more information on the imcl install command, see Installing packages by using the imcl commands.

What to do next

  1. Create a new server(s) on the new host machines using the server templates, which are located under $DSI_HOME/runtime/wlp/templates/servers.
  2. Follow the steps to configure each server, and to include all of the servers in the cluster: Configuring an Insight Server topology for testing and production.
    Note: All of the configuration steps, which modify a set of XML files in each of the servers, can be scripted and combined with the installation steps.

Related information

Join The Discussion

Your email address will not be published. Required fields are marked *