Step 1. Compile and Create the Service and Parcel

Download the Aspire projects from https://stgit.searchtechnologies.com/aspire/cloudera-parcels/tree/3.2

Step 1a. Compile the service

1. Compile the project using the command:

   Code Block
   language java theme RDark
   cloudera-parcels>mvn clean install

   
   

2. Put the jar of the aspire-csd project on the directory /opt/cloudera/csd on the machine where the Cloudera server was installed.

Step 1b. Create the parcel

1. On the project aspire-parcel execute the command

   Code Block
   language java theme RDark
   tar zcvf ASPIRE-3.2-el7.parcel ASPIRE-3.2 --owner=root --group=root

   Check this page to ascertain which parcel suffix to use.

2. Put the parcel on the parcel repository that you are going to use, and update/create the manifest file, this can be done using this python file make_manifest.py with the following command:

   Code Block
   language java theme RDark
   python ./make_manifest.py /path/of/parcels/repository

   
   

Step 2. Download, Distribute and Activate the Parcel

1. Go to the Cloudera Manager Parcels management page and look for the Aspire parcel that should be available to download.
2. Click Download and wait until download process is done.
3. Click Distribute.
4. After the distribution is done, click Activate.
   • The parcel should be activated on all instances of the Cloudera Cluster.
     

Step 3. Add the New Service

On the cluster, click Add Service to go to the add service wizard.

Step 3a. Add Aspire as a service

 In the wizard, Aspire should be listed as a service to install.

1. Select Aspire from the available services.
2. If not selected automatically, select the Zookeeper service to use.
3. Select the hosts where Aspire Server will be installed.

Image Removed

Image Removed

Step 3b. Configure Aspire

1. Common settings
   • Aspire Version: The Aspire version
   • Maven username: Enter the username of the maven account
   • Maven password: Enter the password of the maven account
     
     
2. No SQL settings
   • DB provider implementation: Select the implementation of the no SQL db provider to use.
     
     
3. HBase settings, these will be ignored if the provider is not HBase
   
   • HBase Properties: Specify the required Hbase properties to use in the format: NAME:VALUE.
   • HBase config path: The path to the HBase config files.
   • The HBase user to use with Kerberos.
   • HBase Kerberos Keytab: The HBase keytab to use with Kerberos
     
     
4. Mongo settings, these will be ignored if the provider is not Mongo
   • Mongo DB server: The Mongo DB server to use.
     
     
5. Authentication settings
   • Authentication type: The type of authentication user by the Aspire Admin UI.
     
     
6. Ldap settings, these will be ignored if the authentication type is set to None
   
   • LDAP server: The ldap server to validate against.
   • LDAP Authentication: The ldap authentication to use (anonymous/simple/DIGEST-MD5).
   • LDAP Search Base: The search base for ldap queries for the user's dn.
   • LDAP Admin Group DN: If empty, disables group based access control. Otherwise, holds the dn of the group that may access the administration pages.
   • LDAP Groups Hold Members: Indicates that ldap group objects hold the membership information. By default, user objects are expected to hold group membership.
   • LDAP User DN Query: The ldap query used to find the dn for the user that logged in.
   • LDAP Member Attribute: The attribute of the ldap object (be it user or group) that holds information about group membership.

After you click Add, it will take a moment for Aspire to download all of the necessary components (Jar files) from the Maven repository and load them into Aspire.

When that's done, the publisher will appear in the Workflow Tree.

1. • .