Manually install the DataStax Agent as an RPM package
Whenever possible, install the DataStax Agent automatically on the nodes in your DataStax Enterprise (DSE) clusters.
If automatic installation fails for any nodes, you must manually install the agent on those nodes.
Your DSE installation type determines the required agent installation type:
-
DSE tarball installations: See Manually install the DataStax Agent with a tarball.
-
DSE RPM package installations: Use the procedure described on this page.
-
DSE Debian package installations: See Manually install the DataStax Agent as a Debian package.
Prerequisites
-
Your DSE cluster is deployed and running.
-
DSE OpsCenter is installed and configured to manage your DSE cluster.
-
JMX connectivity is enabled on each node in the cluster.
-
You have root or sudo access to the machines where the agents will be installed.
Download the agent package
To deploy agents manually, you need the agent software files. These files are available on IBM Fix Central in the OpsCenter fix packs for each OpsCenter version.
Find the OpsCenter fix pack for your current OpsCenter version, download the agent archive from that fix pack, and then deploy your agents:
-
Find your version of OpsCenter on IBM Fix Central:
-
Go to Fix Central.
-
In the Product selector field, begin typing
IBM DataStax OpsCenter, and then select that option from the menu. -
In the Release field, select the version that you want to install.
-
Click Continue.
-
On the Identify fixes page, click Continue to use the default Browse for fixes option.
-
On the Select fixes page, select the fix pack (OpsCenter version) you want to install, and then click Continue.
Depending on the product and version, more fix packs might be available if you set the Platform filter to All, and then click Submit.
-
If prompted, sign in with your IBMid.
An IBMid account with MFA enabled is required. If you don’t have one, create an IBMid account. If your organization uses Enterprise Federation (EF) for authentication with corporate credentials, see the IBMid EF documentation.
-
On the Download options page, select Download using your browser (HTTPS), and then click Continue.
-
Review the terms and conditions, and then click I agree to activate the download links.
-
-
Click the DataStax Agent RPM package link to download that file, for example,
datastax-agent-VERSION-rpm.zip. -
Extract the RPM files from the
.zipfile:unzip datastax-agent-VERSION-rpm.zipYou can use the included package signing public key (
rpm-signing.pub.key) to set up and verify the RPM packages. -
Import the package signing public key:
sudo rpm --import rpm-signing.pub.key -
Set up a local Yum repository to host the downloaded RPM files:
- Apache
-
See Apache in the Red Hat documentation for more information.
- nginx
-
See nginx in the Red Hat documentation for more information.
- Red Hat Satellite
-
See Uploading content to custom RPM repositories in the Red Hat Satellite documentation for more information.
-
Add the local DataStax Yum repository to a file called
/etc/yum.repos.d/datastax.repo:[datastax] name=DataStax Agent Repo baseurl=file://REPOSITORY_DIRECTORY_PATH enabled=1
Deploy the agent
-
Install the DataStax Agent:
sudo yum install datastax-agentIf you are using an earlier version of OpsCenter, add the supported version to the command:
sudo yum install datastax-agent-6.8.VERSION_NUMBER -
In the DataStax Agent configuration, set
stomp_interfaceto the IP address that OpsCenter is using. You might have to create theaddress.yamlfile.echo "stomp_interface: reachable_opscenterd_ip" | sudo tee -a /var/lib/datastax-agent/conf/address.yamlFor package installations,
address.yamlis located at/var/lib/datastax-agent/conf/address.yaml. -
If SSL communication is enabled in
opscenterd.conf, use SSL inaddress.yaml:echo "use_ssl: 1" | sudo tee -a /var/lib/datastax-agent/conf/address.yamlFor package installations,
opscenterd.confis located at/etc/opscenter/opscenterd.conf. -
Start the DataStax Agent:
sudo service datastax-agent start
Configure JAVA_HOME for the DataStax Agent
The DataStax Agent cannot find the current user’s environment variables by default. Therefore, if Java isn’t in the machine’s PATH, then the agent’s log shows an error on startup:
nohup: cannot run command 'java': No such file or directory
To avoid this error, you can set the JAVA_HOME environment variable on the nodes where the agents are installed:
-
Navigate to
/etc/default/, and then create a file nameddatastax-agent. -
In this file, set
JAVA_HOMEand any other custom environment variables that the agent might need:JAVA_HOME = /usr/lib/jvm/java-8-oracle -
Repeat for all nodes where the agent is installed and Java isn’t set in the PATH.