Install DataStax Enterprise and OpsCenter using Yum repositories on RHEL-based systems.

Install DataStax Enterprise and OpsCenter using APT repositories on Debian-based systems.

Install DataStax Enterprise on any Linux-based platform, including 32-bit platforms.

DataStax provides a binary tarball distribution for installing DataStax Enterprise on SUSE Linux.

Install on Amazon EC2 or HP cloud.

Steps for installing the same version as other nodes in your cluster.

DataStax Enterprise includes advanced data protection for enterprise-grade databases including internal authentication, object permissions, encryption, Kerberos authentication, and data auditing.

DataStax Enterprise authentication with Kerberos protocol uses tickets to prove identity for nodes that communicate over non-secure networks.

Client-to-node encryption protects data in flight from client machines to a database cluster.

Node-to-node encryption protects data that is transferred between nodes in a cluster using SSL (Secure Sockets Layer).

Generate SSL certificates for client-to-node encryptions or node-to-node encryption.

Install packages to use cqlsh with a Kerberized cluster.

Transparent data encryption (TDE) protects at rest data. TDE requires a secure local file system to be effective.

Auditing is implemented as a log4j-based integration.

Internal authentication is based on Cassandra-controlled login accounts and passwords.

Use GRANT/REVOKE to grant or revoke permissions to access Cassandra data.

The system_auth and dse_security keyspaces store security authentication and authorization information.

Opening the required ports to allow communication between the nodes.

The Hadoop component in DataStax Enterprise enables analytics to be run across DataStax Enterprise's distributed, shared-nothing architecture. Instead of using the Hadoop Distributed File System (HDFS), DataStax Enterprise uses Cassandra File System (CFS) keyspaces for the underlying storage layer.

DataStax Enterprise schedules a series of tasks on the analytics nodes for each MapReduce job that is submitted to the job tracker.

A Hive or Pig analytics job requires a Hadoop file system to function. For use with DSE Hadoop, DataStax Enterprise provides a replacement for the Hadoop Distributed File System (HDFS) called the Cassandra File System (CFS).

The Cassandra File System (CFS) consists of two layers: cfs and cfs-archive. Using cfs-archive is recommended for long-term storage of huge files.

DataStax Enterprise includes a Cassandra-enabled Hive MapReduce client.

The DataStax ODBC Driver for Hive provides Windows users access to the information that is stored in DSE Hadoop.

DataStax Enterprise integrates Apache Mahout, a Hadoop component that offers machine learning libraries.

DataStax Enterprise includes a Cassandra File System (CFS) enabled Apache Pig Client to provide a high-level programming environment for MapReduce coding.

Migrating data using Sqoop topics.

DataStax Enterprise supports Open Source Solr (OSS) tools and APIs, simplifying migration from Solr to DataStax Enterprise.

Supported and unsupported DSE Search and Solr features.

Solr terms include several names for an index of documents and configuration on a single node.

Installing and starting Solr nodes.

Steps for setting up Cassandra and Solr for the tutorial.

Configure Solr Type mapping.

Requirements and steps for creating a Solr index.

A brief description and illustration of DSE Search.

A brief description about query Solr data.

Use a discovery process to develop a plan to ensure sufficient memory resources.

About using real-time (Cassandra), Hadoop, or search (Solr) nodes in the same cluster.

Topics for using DSE Search.

Topics for performance tuning and solving performance degradation, high memory consumption, or other problem swith DataStax Enterprise Search nodes.

A comparison of DSE Search and Open Source Solr.

Use the custom update request processor (URP) to extend the Solr URP. Use the field input/output transformer API as an option to the input/output transformer support in OS Solr.

Production deployment planning requires knowledge of the initial volume of data to store and an estimate of the typical application workload.

Choose a data partitioner and replica placement strategy.

A deployment scenario with a mixed workload cluster has only one data center for each type of workload.

A deployment scenario with a mixed workload cluster has more than one data center for each type of node.

Use single-token architecture deployment when you are not using virtual nodes (vnodes).

Tokens assign a range of data to a particular node within a data center.

To expand your EC2 implementations, use OpsCenter to provision a new cluster, add a new cluster, or add nodes to a cluster.

Table of dse commands for using DataStax Enterprise

Use the dsetool utility for Cassandra File System (CFS) and Hadoop-related tasks, such as managing the job tracker, checking the CFS, and listing node subranges of data in a keyspace.

Ways to enable, disable, and use the disk health checker>

The pre-flight check tool is available for packaged installations. This collection of tests can be run on a node to detect and fix a configuration. The yaml_diff tool filters differences between cassandra.yaml files.

Using sstableloader tool with Kerberos/SSL.

To install DSE on Oracle Enterprise Linux 6.x and later, install the 32-bit versions of the glibc libraries.

Locations when DataStax Enterprise was installed from a tarball.

Locations when DataStax Enterprise was installed from a package.

The configuration file for Kerberos authentication, purging of expired data from the Solr indexes, and setting Solr inter-node communication.

Starting and stopping DataStax Enterprise as a service or stand-alone process.

Troubleshooting examples are useful to discover and resolve problems with DSE. Also check the Cassandra troubleshooting documentation.

DataStax Enterprise allows you to stream your web and application log information into a database cluster via Apache log4j.