+

Search Tips   |   Advanced Search

Creating a response file for installing HCL Digital Experience in Linux

Use IBM Installation Manager to record a response file based on your environment, and also to automate your installation on multiple servers.

We can also use the console mode to generate a response file. Go to Installing with the console for a Linux environment for more information. After reviewing the summary information, enter G to generate a response file instead of I to install.

  1. Start all servers and applications that require a port number to avoid port conflicts when installing HCL Portal. If we are installing multiple copies of HCL Digital Experience on the server, start the existing Configuration Wizard servers.

    Note: Currently, the cw_profile starting point always defaults to 10200. If you install a second version of portal on the same server, customize the cw_profile port value. Edit...

      InstallationManager_root/InstallationManager/eclipse/tools/imcl.ini

      ...and add...

        -Dcwprofile_startingport=new_starting_port_number

    • cd InstallationManager_root/eclipse

    • Start the recording: ./IBMIM -record pathtoresponsexmlfile -skipInstall tempinstalldirectory imcl -c IBMIM.exe -record pathtoresponsexmlfile -skipInstall tempinstalldirectory

        -record

        This parameter indicates recording the actions and parameters into the response file. The pathtoresponsexmlfile text is the name of the response file, for example Wp8SampleResp.xml. The tempinstalldirectory text is the directory where the response file is recorded.

        -skipInstall

        This parameter indicates that no actual installation is completed even though it leads to the final pane.

        tempinstalldirectory

        This value is a directory where the installation saves the history and data when you record the response files.

    • Add the repositories where the installation media exists:

      1. Open the IBM Installation Manager and go to File > Preferences > Repositories.

      2. Select Add Repositories.

      3. Select Browse and go to the Portal-install-eimage/Setup/repository.config file and then click OK.

      4. Ensure that all required repositories are checked. Then, click Test Connections to ensure that the IBM Installation Manager can successfully access the directory where the service repositories are stored.

      5. Select Apply.

      6. Select OK.

    • On the main IBM Installation Manager panel, select Install.

    • Optional: If we are installing Portal to an existing copy of WebSphere Application Server, then select only HCL Portal Server on the Install Packages screen. To complete this installation option, your existing copy of WebSphere Application Server must meet the following requirements:

      • WebSphere Application Server v8.5.5.2 or later
      • Java v8.0.3.
      • No existing Portal profile

      Skip the following step, if you choose to install to an existing copy of WebSphere Application Server.

    • On Install Packages: Select packages to install, select the following packages, and then click Next:

      • IBM WebSphere Application Server Network Deployment
      • HCL Portal Server
      • IBM WebSphere SDK Java Technology Edition

        Note: For new installations, you must have SDK Java version 8.0.3.

        Note: The IBM WebSphere SDK Java Technology Edition option is required for a HCL Digital Experience installation even though it might be marked as "Optional" on the Select packages to install screen.

      Tip: If we have a HCL Portal Enable license, you must select both the HCL Portal ServerHCL Portal Express and HCL Portal Enable packages.

    • On Install Packages: Select the fixes to install screen, select any required fixes. Then, click Next.

    • Accept the license agreement and then click Next.

    • Enter the directory where we want to store shared resources and then click Next.

    • Complete the following steps on the Install Packages: Installation Directory panel:

      The installation directory specified must NOT contain any files or the following characters: ~ ! @ # $ % ^ & * ( ) + { } | < > ? ` = [ ] ; ' , . " and spaces.

      1. Select the WebSphere Application Server Package Group Name and then enter the installation directory path.

      2. Select the HCL Digital Experience Package Group Name and then enter the installation directory path.

      3. Click Next.

    • Select the translations to install and then click Next.

    • Optional: If you chose to install Portal to an existing copy of WebSphere Application Server, select the available copy of WebSphere Application Server, and click Next.

      Note: Skip this step, if we are not installing Portal to an existing copy of WebSphere Application Server.

    • On Install Packages: Select the features to install, expand the WebSphere Application Server and HCL Digital Experience packages to modify the features we want to install and then click Next.

      Note: Ensure that Portal Server Profile is selected to create a profile that contains the Portal application server and the product binary files. Clear this option if we need a binary only installation for migration or the clustered environment.

      Note: As you select the items, read the Details section for information.

    • On Profile configuration details, enter the user ID and password for the configuration wizard administrator. Then, click Next.

    • If you selected the Portal Server Profile package, click Enter the Administrator user ID and password for the Portal Server. Then, select either the Standard or Advanced configuration mode and then enter the parameter details for the selected configuration mode.

      Note: Select Advanced if we want to specify Uniform Resource Identifier (URI) information that is specific to your company.

    • Confirm the Summary information and then click Install.

    • After the Installation Manager finishes creating the response file, click Finish and then close the Installation Manager to complete the response file recording.

    • If you plan to install on a different server, copy the response file to the response file directory on that server. Open the response file, make any necessary changes to the repository location. Search for value= and make any necessary changes for the new server.