Skip to main content
Hitachi Vantara Lumada and Pentaho Documentation

Configure Carte to Be a Dynamic Slave Instance

Follow the directions below to set up static Carte slave servers.

Note: If you already have Carte installed on the target machines, you can skip the initial installation steps.
  1. Retrieve a pdi-ee-client archive package from the Pentaho Customer Support Portal.
  2. On each machine that will act as a Carte server (slave), create a /pentaho/design-tools/ directory.
  3. Unpack the archive to the /pentaho/design-tools/ directory on each machine. Two directories will be created: data-integration and license-installer.
  4. Copy over any required JDBC drivers and PDI plugins from your development instances of PDI to the Carte instances.
  5. Create a carte-slave-config.xml configuration file using the following example as a basis:
    <!-- the masters node defines one or more load balancing Carte instances that will manage this slave -->
    <!-- uncomment the next line if you want the DI Server to act as the load balancer -->
    <!--	    <webAppName>pentaho-di</webAppName> -->
    <!-- the slaveserver node contains information about this Carte slave instance -->
    Note: The slaveserver <name> must be unique among all Carte instances in the cluster.
  6. Run the Carte script with the carte-slave-config.xml parameter.
    ./ carte-slave-config.xml
  7. If you will be executing content stored in a DI Repository, copy the repositories.xml file from the .kettle directory on your workstation to the same location on your Carte slave. Without this file, the Carte slave will be unable to connect to the DI Repository to retrieve PDI content.
  8. Ensure that the Carte service is running as intended.
  9. To start this slave server every time the operating system boots, create a startup or init script to run Carte at boot time with the same config file option you specified earlier.
You now have a Carte slave to use in a dynamic cluster. You must configure a Carte master server or use the DI Server as a load balancer.