Skip to main content

Pentaho+ documentation has moved!

The new product documentation portal is here. Check it out now at docs.hitachivantara.com. 

 
Version Data Integration and Analytics
Hitachi Vantara Lumada and Pentaho Documentation

Installing the Carte Server on AWS

  1. Last updated
  2. Save as PDF

These instructions provide the steps necessary to deploy Docker images of the Carte Server on AWS.

Parent Topic
Child Topics

Prerequisites for installing the Carte Server on AWS

Observe the following prerequisites before installing the Carte Server:

  • A stable version of Docker must be installed on your workstation.
  • You must have an AWS account to complete this installation.
  • Amazon AWS CLI must be installed on your workstation.
  • The following software versions are supported:

    ApplicationSupported version
    EKSv1.x
    Dockerv20.10.21 or a later stable version
    AWS CLIv2.x
Parent Topic

Process overview for installing the Carte Server on AWS

Use the following steps to deploy the Carte Server on the AWS cloud platform:

  1. Download and extract Pentaho for AWS.
  2. Create an Amazon ECR.
  3. Load and push the Pentaho Docker image to ECR.
  4. Create an S3 bucket.
Parent Topic

Download and extract Pentaho for AWS

Download and open the package files that contain the files needed to install Pentaho.

Procedure

  1. Navigate to the Support Portal and download the AWS version of the Docker image with the corresponding license file for the applications you want to install on your workstation.

  2. Extract the image to view the directories and the readme file.

    The image package file (<package-name>.tar.gz) contains the following:
    Directory or file nameContent description
    imageDirectory containing all the Pentaho source images.
    yamlDirectory containing YAML configuration files and various utility files.
    README.mdFile containing a link to detailed information about what we are providing for this release.
Parent Topic

Create an Amazon ECR

Before pushing the Pentaho image to AWS, you need to create an Amazon ECR.

Procedure

  1. Create an ECR repository to load the Pentaho image.

    For information on how to create an Amazon ECR, see instructions for creating a private repository on AWS.

  2. Record the name of the ECR repository that you have created in the Worksheet for AWS hyperscaler.

Parent Topic

Load and push the Pentaho Docker image to ECR

Select and tag the Pentaho Docker image and then push it to the ECR registry.

Procedure

  1. Navigate to the image directory containing the Pentaho tar.gz files.

  2. Select and load the tar.gz file into the local registry by running the following command:

    docker load -i <pentaho-image>.tar.gz

  3. Record the name of the source image that was loaded into the registry by using the following command:

    docker images

  4. Tag the source image so it can be pushed to the cloud platform by using the following command:

    docker tag <source-image>:<tag> <target-repository>:<tag>

  5. Push the image file into the ECR registry using the following Docker command:

    docker push <target-repository>:<tag>
    The AWS Management Console displays the uploaded image URI.

    For general AWS instructions on how to push an image to AWS, see Pushing a Docker image.

  6. Record the newly created ECR repository URI in the Worksheet for AWS hyperscaler.

Parent Topic

Create an S3 bucket for the Carte Server

You must create an S3 bucket to deploy the Carter Server image on AWS.

Procedure

  1. Create an S3 bucket .

    To create an S3 bucket, see Creating a bucket. To upload a file to S3, see Uploading objects.

  2. Record the newly created S3 bucket name in the Worksheet for AWS hyperscaler.

  3. Upload files into the S3 bucket.

    After the S3 bucket is created, manually create any needed directories as shown in the table below and upload the relevant files to an appropriate directory location by using the AWS Management Console. The relevant Pentaho directories are explained below:
    DirectoryActions
    /root

    All the files in the S3 bucket are copied to the PentahoServer's /home/pentaho/.kettle directory.

    If you need to copy a file to the Pentaho server's /home/pentaho/.kettle directory, drop the file in the root directory of the S3 bucket.

    This directory contains the Pentaho licenses files.

    Jdbc-drivers

    If your Pentaho installation needs JDBC drivers, do the following:

    1. Add the jdbc-drivers directory to your S3 bucket.
    2. Place the drivers in this directory.

    Any files within this directory will be copied to Pentaho’s lib directory.

    plugins

    If your Pentaho installation needs additional plugins installed, do the following:

    1. Add the plugins directory to your S3 bucket.
    2. Copy your plugins to the plugins directory.

    Any files within this directory are copied to Pentaho’s plugins directory. For this reason, the plugins should be organized in their own directories as expected by Pentaho.

    The relevant Pentaho files are explained below:
    FileActions
    content-config.properties

    The content-config.properties file is used by the Pentaho Docker image to provide instructions on, which S3 files to copy over and their location.

    The instructions are populated as multiple lines in the following format:

    ${KETTLE_HOME_DIR}/<some-dir-or-file>=${APP_DIR}/<some-dir>

    A template for this file can be found in the templates project directory.

    The template has an entry where the file context.xml is copied to the required location within the Docker image:

    ${KETTLE_HOME_DIR}/context.xml=${APP_DIR}/context.xml
    content-config.sh

    This is a bash script that can be used to configure files, change file and directory ownership, move files around, install missing apps, and so on.

    You can add it to the S3 bucket.

    It is executed in the Docker image after the other files are processed.

Parent Topic

Worksheet for AWS hyperscaler

To access the common worksheet for the AWS hyperscaler, go to Worksheet for AWS hyperscaler.

Parent Topic