Downloading and Running the Siebel Lift Utility (Container Mode)

You can use the procedures in this topic to download and run the Siebel Lift utility using container mode. This option is recommended. It is the default option on Linux, though it can also be used on Windows, where you are running Linux containers on Windows. This topic is part of Downloading and Running the Siebel Lift Utility.

Note: If you use the tasks in this topic (for container mode), then do not perform the tasks for non-container mode.
Note: Separate procedures are provided for running the Siebel Lift utility in silent mode or in interactive mode. It is recommended to run the Siebel Lift utility in silent mode. For information about the settings equivalent to the response file options, see Running the Siebel Lift Utility in Interactive Mode (for Non-Container Mode).

Downloading the Siebel Lift Utility (for Container Mode)

Use the following procedure to download the Siebel Lift utility for container mode.

To download the Siebel Lift utility for container mode (Linux only)

  1. Obtain the file siebelliftutility_container.zip from SCM, as described at the end of the procedure in Downloading and Installing Siebel Cloud Manager.

  2. Extract the contents of the ZIP file. This file contains the following contents:

    • execute_lift_container.sh. A shell script used to run the Docker container.

    • volumemounts.ini. Contains local paths for Docker container volume mounts.

    • oci_config_template.ini. Contains OCI credentials details (for interactive mode only). To be populated only if OCI object storage is used during "lift-and-shift".

    • oracle_db_config_template.ini. Contains Oracle Database details (for interactive mode only).

    • lift_utility_responsefile_template.resp. A response file template used for silent mode execution of the utility.

    • tnsnames.ora. A template of the tnsnames.ora file, containing database connection credentials details.

  3. Install and configure Docker software for managing containers.

  4. Update the volumemounts.ini file with the required values. In particular, note the following:

    • While executing the Siebel Lift utility from the Docker container, provide the mounted volume path of the Docker container at the location indicated by STAGING_LOCATION (as specified in volumemounts.ini), such as /liftstage.

    • If you will run the Siebel Lift utility in silent mode, then keep the response file template (lift_utility_responsefile_template.resp) at the location indicated by TEMPLATES_FILE_LOCATION (as specified in volumemounts.ini), such as /templates.

    • If you will run the Siebel Lift utility in interactive mode, and you want to provide the OCI and database related configuration details via files, then keep the oci_config_template.ini and oracle_db_config_template.ini template files at the location indicated by TEMPLATES_FILE_LOCATION (as specified in volumemounts.ini), such as /templates.

    • If you need to access the log files outside the Docker container, then also update the local mounted path value for the variable LIFT_TOOL_LOG_LOCATION (as specified in volumemounts.ini).

  5. Update the tnsnames.ora file with the required values.

    While executing the Siebel Lift utility from the Docker container to generate database artifacts, create a directory named tns inside the local mounted path for /templates. Copy the provided tnsnames.ora file to this tns folder and update it with the database connection details as needed.
    Note: Alternatively, you can use actual database connect string details as input instead of the TNS profile name while running the Siebel Lift utility. In this case, you do not need the provided tnsnames.ora file.
  6. While executing the Siebel Lift utility from the Docker container to generate database artifacts (deployment kits), provide the database client location, which is /usr/lib/oracle/12.2/client.

Running the Siebel Lift Utility in Silent Mode (for Container Mode)

Use the following procedure to run the Siebel Lift utility in silent mode.

To run the Siebel Lift utility in silent mode (for container mode)

  • Run a command like the following in a shell:

    sh execute_lift_container.sh -m silent -v volumemounts.ini -f lift_utility_responsefile_template.resp -s <smc_password> -d <database_password> -a <DNS1:IP1>,<DNS2:IP2>

    In the sample command, the flag:

    • -m is the mode of the execution (silent or interactive).
    • -v is the volume mount file location.
    • -f is the response file location required for silent mode execution.
    • -s is the SMC Authenticated Password required for silent mode execution.
    • -d is the table owner password required for silent mode execution.
    • -a is the comma-separated list of DNS:IP hosts mappings. This is an optional parameter.
    Note: It is recommended to run the Siebel Lift utility in silent mode. For information about the settings equivalent to the response file options, see Running the Siebel Lift Utility in Interactive Mode (for Non-Container Mode).

Running the Siebel Lift Utility in Interactive Mode (for Container Mode)

Use the following procedure to run the Siebel Lift utility in interactive mode.

To run the Siebel Lift utility in interactive mode (for container mode)

  • Run a command like the following in a shell:

    sh execute_lift_container.sh -m interactive -v volumemounts.ini -a <DNS1:IP1>,<DNS2:IP2>

    In the sample command, the flag:

    • -m is the mode of the execution (silent or interactive).
    • -v is the volume mount file location.
    • -f is the response file location required for silent mode execution.
    • -s is the SMC Authenticated Password required for silent mode execution.
    • -d is the table owner password required for silent mode execution.
    • -a is the comma-separated list of DNS:IP hosts mappings. This is an optional parameter.
    Note: For more information about interactive mode, see Running the Siebel Lift Utility in Interactive Mode (for Non-Container Mode).
    Note: When running the Lift utility in container mode, make sure that the user group 1000 has the necessary access to all the volume mounts. Run the following commands to grant required access to user group 1000:
    chown -R 1000:1000 <all_volume_mount_folders>
    chmod -R g+rwx <all_volume_mount_folders>