Step 1. Launch Aspire and open the Content Source Management Page

Before

launching Aspire, you need to change the felix.properties file and add

these lines:

# To append packages to the default set of exported system packages,
# set this value.
org.osgi.framework.system.packages.extra=\
 ...
 sun.security.krb5, \
 com.sun.security.auth.callback

# The following property makes specified packages from the class path
# available to all bundles. You should avoid using this property.
org.osgi.framework.bootdelegation=\
 ...
 javax.security.sasl, \
 sun.security.krb5

Launch Aspire (if it's not already running). See:

• Launch Control

• Browse to: http://localhost:50505.

  For details on using the Aspire Content Source Management page, please refer to Admin UI

Step 2. Add a new Content Source

For this step, please follow the step from the Configuration Tutorial of the connector of you choice, please refer to Connector list

Step 3. Add a new Publish to SolrCloud to the Workflow

To add a Publish to SolrCloud, drag from the Publish to SolrCloud CDH (or a custom component using app-publish-to-sorlj-cdh coordinates) rule from the Workflow Library and drop to the Workflow Tree where you want to add it.

This will automatically open the Publish to SolrCloud window  window for the configuration of the publisher.

Step 3a. Specify Publisher Information

 In the Publish to SolrCloud window window, specify the following connection information to publish to the SolrCloud  .

Name: Enter

a unique name

for the publisher.

SolrJ Configuration

1. Choose a Connection Method (This name must be unique).Enter the Connection Method Type:
   • CloudSolrServer:
   This method connects
   • Connects using a
   zookeeper
   • Zookeeper url
   .
   • HttpSolrClient:
   This method connects
   • Connects using a
   solr
   • Solr url (direct connetion to Solr)
2. Enter the  Enter a Host urlURL, depends depending on the selection of the Connection Method:
   • Zookeeper Host:
   A list of zookeeper
   • Zookeeper hosts and
   port comma separated
   • ports in a comma delimited list (ie: zkHost1:2181, zkHost2:2181, zkHost3:2181)
   • Solr Host: A single Solr host and port (ie: solrHost:8993)
3. Enter the Zookeeper chroot: If you're using a ZooKeeper instance that is shared by other systems, it's recommended to isolate we recommend isolating the SolrCloud znode tree using ZooKeeper's chroot support.
   (For instanceexample, to ensure all znodes created by SolrCloud are stored under /solr,)
4. Enter the Solr collection name (same collection Collection Name: Same collection of all Solr instances of the cloud).
5. XSL File PathTransform: set Set to the default parameter to use the default XSL transformation file. To use a custom file.
6. Field List list XPath: XPath expression to process field list.
7. Id Field: The Id used for identify identification the on Solr index.
8. Zookeeper Client Timeout: timeout Timeout for the client.
9. Zookeeper Connect Timeout: timeout Timeout for the client.
10. Force Commit: If true, force a commit every time a batch is send sent to the index.
11. Commit with milliseconds: milliseconds Milliseconds to wait before commit a batch to the index.
12. Use Kerberos Authentication: Enable the authentication through Kerberos
    • CoreSite.xml: The path for the hadoop core-site.xml file
    • Login Configuration Properties: The path of the pseudo jaas properties file, please check Login Config File.
13. Max Tries: Maximum number of retry attempt to index.
14. Retry Wait: Seconds to wait before re-trying to index.
15. Debug: Check if you want Select the check box to run the publisher in debug mode.

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.

Anchor
LoginFile LoginFile

Step 3b. Edit Login Config File

The Login Config

file is a pseudo JAAS (Java Authentication and Authorization Service) file. Basically, use only the properties inside the JAAS file.

For example:

 Normal JAAS File

Client {
 com.sun.security.auth.module.Krb5LoginModule required 
 useKeyTab=true
 keyTab="/home/centos/solr.keytab"
 storeKey=true
 doNotPrompt=true
 useTicketCache=false
 principal="solr/[email protected]"; 
};

The Login Config file for the publisher should be something like this, with only the properties propertyName=propertyValue (

module name and

login type are not necessary).

useKeyTab=true
keyTab="/home/centos/solr.keytab"
storeKey=true
doNotPrompt=true
useTicketCache=false
principal="solr/[email protected]"