Deploying the SAS Embedded Process Parcel on Cloudera

After you run the SAS Deployment Manager to create the SAS Embedded Process parcel, you must distribute and activate the parcel on the cluster. Follow these steps:
Note: More than one SAS Embedded Process parcel can be deployed on your cluster, but only one parcel can be activated at one time. Before activating a new parcel, deactivate the old one.
  1. Log on to Cloudera Manager.
  2. In Cloudera Manager, choose Hoststhen selectParcels.
    The SASEP parcel is located under your cluster. The parcel name is the one from Step 6 in Using the SAS Deployment Manager to Create the SAS Embedded Process Parcel or Stack. An example name is 9.43.p0.1.
  3. Click Distribute to copy the parcel to all nodes and the SASEPHome directory is created.
    Note: If you have licensed and downloaded SAS Data Loader for Hadoop, the SAS Data Loader for Hadoop data quality components are silently deployed at the same time as the SAS Embedded Process for Hadoop.
    You can log on to the node and show the contents in the /opt/cloudera/parcel directory.
  4. Click Activate.
    This step creates a symbolic link to the SAS Hadoop JAR files.
    You are asked to restart the cluster.
  5. Click Restart to restart the cluster.
    Any processes that are running will not use the newly activated parcel until the cluster is restarted. This is a Cloudera requirement.
  6. Use the Add Service Wizard page to add the SASEP as a service on any node where HDFS is a client:
    1. Navigate to Cloudera Managerthen selectServices tab.
    2. Select Actionsthen selectAdd a Service.
    3. Select the SASEP service and click Continue.
    4. Select the dependencies for the SAS Embedded Process service in the Add Service Wizardthen selectSelect the set of dependencies for your new service page. Click Continue.
    5. Choose a location for the SAS Embedded Process ep-config.xml file in the Add Service Wizard then selectCustomize Role Assignments page. Click Select the set of dependencies for your new service page. Click OK.
      The ep-config.xml file is created and added to the HDFS /sas/ep/config directory. This task is done in the host that you select.
      Note: If your cluster is secured with Kerberos, the host that you select must have a valid ticket for the HDFS user.
    6. After the SAS Embedded Process ep-config.xml file is created, Cloudera Manager starts the SAS Embedded Process service. This step is not required. MapReduce is the only service that is required for the SAS Embedded Process. You must stop the SAS Embedded Process service immediately when the task that adds the SAS Embedded Process is finished. The SAS Embedded Process service no longer needs to be stopped or started.
  7. Review any additional configuration that might be needed depending on your Hadoop distribution.
  8. Validate the deployment of the SAS Embedded Process by running a program that uses the SAS Embedded Process and the MapReduce service. An example is a scoring program.
  9. If you have licensed and downloaded any of the following SAS software, additional configuration is required:
    • SAS Data Loader for Hadoop
      For more information, see Part 3, “Administrator’s Guide for SAS Data Loader for Hadoop”.
    • SAS High-Performance Analytics
      For more information, see SAS High-Performance Analytics Infrastructure: Installation and Configuration Guide.
Copyright © SAS Institute Inc. All rights reserved.