1. Deploying Siebel CRM Containers on Kubernetes using Siebel Cloud Manager
  2. Downloading and Running Siebel Installer for SCM

Downloading and Running Siebel Installer for SCM

This topic describes the steps to download Siebel Installer for SCM, run the installer to lay down the SCM image and SCM Helm chart, and verify the SCM image and SCM Helm chart in the container registry.

This topic includes the following sections:

Overview of Siebel Installer for SCM

Siebel Installer simplifies the task of downloading the SCM artifacts required to set up SCM on a Kubernetes cluster on premises or in the cloud. Siebel Installer lays down the SCM image and the SCM Helm chart, required to install SCM, in an assigned directory and then pushes them to the user specified container registry.

Downloading the Build

To download the installer:

  1. Download the media file from My Oracle Support (MOS). For example, p37481729_251_Linux-x86-64.zip.
    Note: Here, the file name is representational and will change with the build. The format of the media file name is <patch_id >_<release_tag>_<platform>.zip, where:
    • <patch_id> is the patch or the bug number. For example, 37481729.
    • <release_tag> is the SCM release version. For example, 251 for the SCM release 25.1.
    • <platform> is the platform you wish to install SCM on. For example, Linux-x86-64.
  2. Extract the media zip file to the directory (which will be referred to as the "installation directory" in the steps later) from which you want to run the installer, as follows:
    cd <installation_directory>
unzip p37481729_251_Linux-x86-64.zip
    The following files are extracted in the installation directory:
    drwxrwxrwx 3 root root   3 Oct 22 10:40 ext
drwxrwxrwx 2 root root   4 Oct 22 10:41 resources
drwxrwxrwx 2 root root   2 Oct 22 10:41 logs
drwxrwxrwx 3 root root   3 Oct 22 11:13 archives
-rwxrwxrwx 3 root root   3 Oct 25 09:31 README.html
-rwxrwxrwx 1 root root 186 Oct 25 09:31 runInstaller.sh
drwxrwxrwx 3 root root   3 Oct 29 07:24 jre
-rwxrwxrwx 1 root root  53 Nov 22 06:46 installer.properties
    Note: Make a note of this installation directory; later you'll run the SCM installation from this directory.
  3. (Optional) Configure the non-root user to push the images to the container registry, as follows:
    Note: You must perform this step only if you want to run the installer as a non-root user.
    sudo /sbin/usermod --add-subuids <first-last> --add-subgids <first-last> <uid> 
podman system migrate
/usr/bin/systemctl --user daemon-reload

    The variables in the example have the following values:

    • <uid> is the non-root user ID.
    • <first-last> is the subordinate user/group IDs range that the non-root user is allowed to use. For example, 20000-265536.
  4. (Optional) Sign in to the container registry using Podman and Helm utilities.
    Note: If you sign in to the container registry now, which is before running the installer, you need not provide the registry credentials in the SCM configuration details when you run the installer. The credentials with which you've logged in to the container registry are used to push the SCM image and SCM Helm chart to the container registry.

Running Siebel Installer

You can run Siebel Installer either in the GUI mode or silent mode.

Running the Installer in the GUI Mode

To run the installer in the GUI mode:

  1. Start the installer in the GUI mode as follows:
    sh runInstaller.sh
  2. Complete the installation as follows:
    1. In the Installation Location screen, click Browse to select the directory to store the SCM artifacts and click Next.
    2. In the Component Selection screen, the installation component "Siebel Cloud Manager" and configuration task "Siebel Cloud Manager Configuration" are selected by default. Click Next to continue.
      Note: Don't deselect "Siebel Cloud Manager" or "Siebel Cloud Manager Configuration". If you deselect “Siebel Cloud Manager,” the installer will throw an error and you'll not be able to proceed with the installation. If you deselect "Siebel Cloud Manager Configuration", the installer will not upload the SCM image and SCM Helm chart to the container registry.
    3. In the Configuration Details screen, enter the container registry details required to push the SCM image and SCM Helm chart to the container registry:
      • Container registry URL: The container registry URL to push the SCM image and the SCM Helm chart to. For example, harbor-registry.corpxyz.mytenancy02phx.oraclevcn.com.
      • Container registry URL prefix: The prefix for the container registry URL. It's used to construct the repository path. This field is optional or mandatory based on the registry used. If the registry mandates that the prefix be specified for better organization of projects or namespaces, then this field is mandatory; else it's optional and can be left blank. For example, if the prefix is mytenancy and the suffix is scmxyz, then the repository path will be iad.ocir.io/mytenancy/scmxyz/image-name.
        Note: For OCI container registry, the prefix is mandatory and must be the OCI namespace. Additionally, you can also include an optional suffix. For example, if the namespace is mytenancy and the suffix is scmproject, then the prefix will be mytenancy/scmproject.
      • Container registry URL UserName: The user name to access the container registry. It is optional if the installer is launched from the session in which the user has already logged in to the container registry.
      • Container registry Password: The password to access the container registry. It is optional if the installer is launched from the session in which the user has already logged in to the container registry.
    4. In the Summary screen, review details and click Install.
    5. Optionally, you can save the installation response messages to a response file. To create a response file:
      1. Click Save Response File.
      2. Go to the required directory.
      3. Enter the response file name.
      4. Click Save.
    6. In the Installation Progress screen, as the installation progresses, appropriate messages are displayed. After you receive the message "Post Installation Configuration Complete", click Next.
    7. In the Finish Installation screen, after the installation is complete, the "Installation is successful" message is displayed along with the path and name of the log file. Click Close.

Running the Installer in the Silent Mode

You can use the silent mode to perform a fresh installation, reconfiguration or upgrade. The silent mode installation uses a response file that contains information required by the installer to complete the installation. A sample response file is available in the Siebel Installer location. The INSTALLATION_TYPE parameter in the response file allows you to define the type of installation you want to perform.

You can run the installer in the silent mode using one of the following options:

  • Option 1: Using the sample response file available in the installer location as follows:

    1. Update the response file:
      • Set the INSTALLATION_TYPE parameter to one of the following values:
        • Fresh
        • Upgrade
        • Reconfiguration
        Note: Reconfiguration only performs the post-install tasks, it doesn't perform the installation of binaries again.
      • Set the values of other parameters as per your environment configuration.

      Here's a sample of the updated response file:

      	[Installation Details]
INSTALLATION_TYPE="Fresh"
SIEBEL_HOME_LOCATION="/home/siebel"
SELECTED_COMPONENTS="Siebel Cloud Manager"
SELECTED_CONFIGURATION_COMPONENTS="Siebel Cloud Manager"
[Siebel Cloud Manager Configuration]
CONTAINER_REGISTRY_URL=harbor-registry.xxx.xxxx.xxxx.com
CONTAINER_REGISTRY_URL_PREFIX=abc
CONTAINER_REGISTRY_USERNAME=user1
CONTAINER_REGISTRY_PASSWORD=BJUkxRM2ZtUjxxxxxl3Q0t4MkllcldOWGxjVW82QjlNaWdsXXXXXXZ
      Note: Passwords in the response file are encrypted. Before you add or update passwords in the response file, you must encrypt the passwords using the Siebel encryption utility as follows:
      jre/bin/java -jar ext/jlib/EncryptString.jar <password>
    2. Run the installer in the silent mode using the updated response file as follows:
      • Linux:
        ./runInstaller.sh -silent -responseFile <Location of responsefile>
      • Windows:
        runInstaller.bat -silent -responseFile <Location of responsefile>

  • Option 2: Generating the response file using the GUI and then running the installer in silent mode using the generated response file, as follows:

    1. Run Siebel Installer in the GUI mode and navigate through the installation screens providing required information until you reach the Summary screen.

      For more information on running Siebel Installer in GUI mode, see Running the Installer in the GUI Mode.

    2. In the Summary screen, create a response file as follows:
      1. Click Save Response File.
      2. Go to the required directory.
      3. Enter the response file name.
      4. Click Save.
    3. Cancel the installation.
    4. Run Siebel Installer in silent mode using the response file created in step b. For more information on running Siebel Installer in silent mode, see Option 1 discussed in this section.

Verifying the SCM Image and SCM Helm Chart in the Container Registry

After the installer is run successfully, you must verify that the SCM image and SCM Helm chart are available in the container registry for smooth SCM installation through one of the following ways:

  • Open the log file and look for the following messages:
    Uploaded image and helm chart to customer registry
Post install configuration step completed for Siebel Cloud Manager Configuration
Post Installation Configuration Completed.
  • Sign in to the container registry and verify the image from the interface provided by the registry; for example, the GUI.