- Copy the Hub rpm file to the system where it will be installed.
-
If you have a previous version of Hub or IIC
installed:
-
If you are using a Splunk Forwarder with Hub/IIC, then stop the Splunk Forwarder with the command:
$SPLUNK_HOME/bin/splunk stop
To verify that the Forwarder started, use the command:
$SPLUNK_HOME/bin/splunk status
- Locate and note its install path for use in a later step.
-
If previous version is IIC, stop the existing services by running these commands as root user:
/opt/OV/vp400/bin/vp400sv -stop
service vp400conf stop
- Uninstall the previous version of Hub/IIC. Existing configuration files will be left untouched by the uninstall and can be reused. For details to remove previous versions, see the uninstall section of the appropriate version of Installation Guide.
-
If you are using a Splunk Forwarder with Hub/IIC, then stop the Splunk Forwarder with the command:
-
Run the Linux rpm command:
- For Intel Linux:
rpm --upgrade /tmp/IronstreamHub-1.3.1-1.x86_64.rpm
- For Power Linux:
rpm --upgrade /tmp/IronstreamHub-1.3.1-1.ppc64le.rpm
where, /tmp is the directory where the rpm file was saved.
After the rpm command is run:- Open inbound network traffic on ports 80 and 9850 and bind port 80 to the Hub portal service with the commands. To do this, as 'root', enter:
firewall-cmd --zone=public --permanent --add-port 80/tcp firewall-cmd --zone=public --permanent --add-port 9850/tcp firewall-cmd --reload setcap CAP_NET_BIND_SERVICE=+eip /opt/ihub/bin/ironstreamhubportal
This last command is necessary because the Hub Portal port is lower than 1024. It is not necessary for the UI port of 9850.
- The ibmiconfig service will start, which allows access to the browser-based Configuration Tool.
- The Ironstream Hub Portal service will start automatically. This is a web browser-based user interface where Ironstream data pipelines are configured.Note: The Hub service is installed in Manual mode. The service will not stay running if there are no pipelines.You should start it when you have defined pipelines and after this you may wish to change the service to be Automatic so it starts up after a reboot, using the mechanism appropriate to the edition of Linux you are running.
- For Intel Linux:
-
This step can be skipped if the Hub processes on the Linux server are to run as a root. To run the Hub processes as a non-root user:
- Log into the Linux server as the root user.
-
Make sure all Hub processes are stopped by issuing these commands:
systemctl stop ironstreamhub
systemctl stop ibmiconfig
systemctl stop ironstreamhubportal
- The user name under which the Hub processes will be run must be part of a Linux user group with the same name as the user name. That group will be given group ownership of Hub directories and files.
-
If the group and user name that will be used to run the Hub processes already exists, run this command, replacing username with the user name that will run the server processes:
/opt/ihub/bin/configure_user.sh username
-
If you want to manually create the group then run this command, replacing username with the user name that will run the server processes:
groupadd username
-
If the group already exists, you can check which profiles are assigned to it by running this command, replacing username with the user name that will run the server processes:
getent group username
-
If the user name that will be used to run the Hub processes does not exist, and you want the configure script to create the user using the Linux useradd command, run this command. This will create the user ID user name using the useradd command and will also create a group with the same user name:
/opt/ihub/bin/configure_user.sh username -createuser
- Restart the server processes with these commands:
systemctl start ironstreamhub
systemctl start ibmiconfig
systemctl start ironstreamhubportal
-
If you are using a Splunk Forwarder then start it using the command:
$SPLUNK_HOME/bin/splunk start
To verify that the Forwarder started, use the command:
$SPLUNK_HOME/bin/splunk status
The user name for the Hub processes is stored in the 10-user.conf file located in the /etc/systemd/system/ironstreamhub.service.d directory, the /etc/systemd/system/ibmiconfig.service.d directory and the /etc/systemd/system/ironstreamhubportal.service.d directory.
To change the user for the Hub processes later, repeat the steps in this section.