Command Center Installation - Revision history

Masnes: /* Docker Install */

2025-11-20T21:41:35Z

Docker Install

← Older revision		Revision as of 21:41, 20 November 2025
Line 143:		Line 143:

	* [[Installing Docker on RedHat Enterprise Linux 8 \|RedHat Enterprise Linux 8]]		* [[Installing Docker on RedHat Enterprise Linux 8 \|RedHat Enterprise Linux 8]]
	* [[Installing Docker on CentOS 7 \|CentOS 7]] (EOL June 2024)
	* [[Installing Docker on RedHat Enterprise Linux 7\|RedHat Enterprise Linux 7]] (EOL June 2024)
	* [[Oracle Linux 8]]		* [[Oracle Linux 8]]
	* [[Installing Docker on Ubuntu 20.04\|Ubuntu 20.04]]		* [[Installing Docker on Ubuntu 20.04\|Ubuntu 20.04]]
	* [[Installing_Docker_on_Amazon_Linux_2\|Amazon Linux 2]]		* [[Installing_Docker_on_Amazon_Linux_2\|Amazon Linux 2]] (EOL 2025-06)

	Other versions of Linux may work correctly, but these are the versions and processes that have been verified.		Other versions of Linux may work correctly, but these are the versions and processes that have been verified.

2025-08-08T03:02:50Z

How to backup and restore a system

← Older revision		Revision as of 03:02, 8 August 2025
Line 473:		Line 473:
	*'''Restore from the database'''		*'''Restore from the database'''

	sudo ./RestoreCommandCenterDatabase.sh YYYY-MM-DD		sudo ./RestoreCommandCenterDatabase.sh YYYY-MM-DD_HHMMSS

	*'''Verify that Command Center is populated with the correct information'''		*'''Verify that Command Center is populated with the correct information'''

2025-08-08T03:02:30Z

How to backup and restore a system

← Older revision		Revision as of 03:02, 8 August 2025
Line 450:		Line 450:
	sudo ./BackupCommandCenterDatabase.sh		sudo ./BackupCommandCenterDatabase.sh

	This will create two files <code><home>/commandcenter/backup/commandcenter_backup_YYYY-MM-DD.sql</code> and <code><home>/commandcenter/backup/LRM_backup_YYYY-MM-DD_HHMMSS.sql</code> Where YYYY-MM-DD is the current date.		This will create two files <code><home>/commandcenter/backup/commandcenter_backup_YYYY-MM-DD_HHMMSS.sql</code> and <code><home>/commandcenter/backup/LRM_backup_YYYY-MM-DD_HHMMSS.sql</code> Where YYYY-MM-DD is the current date.

	*'''Stop the currently running Command Center container and its associated MySQL container'''		*'''Stop the currently running Command Center container and its associated MySQL container'''

2025-08-08T03:02:05Z

How to backup and restore a system

← Older revision		Revision as of 03:02, 8 August 2025
Line 450:		Line 450:
	sudo ./BackupCommandCenterDatabase.sh		sudo ./BackupCommandCenterDatabase.sh

	This will create two files <code><home>/commandcenter/backup/commandcenter_backup_YYYY-MM-DD.sql</code> and <code><home>/commandcenter/backup/LRM_backup_YYYY-MM-DD.sql</code> Where YYYY-MM-DD is the current date.		This will create two files <code><home>/commandcenter/backup/commandcenter_backup_YYYY-MM-DD.sql</code> and <code><home>/commandcenter/backup/LRM_backup_YYYY-MM-DD_HHMMSS.sql</code> Where YYYY-MM-DD is the current date.

	*'''Stop the currently running Command Center container and its associated MySQL container'''		*'''Stop the currently running Command Center container and its associated MySQL container'''

2025-08-08T03:01:31Z

Return to the previous version

← Older revision		Revision as of 03:01, 8 August 2025
Line 354:		Line 354:
	3. Restore the database to match your previous Command Center server version		3. Restore the database to match your previous Command Center server version

	sudo ./RestoreCommandCenterDatabase.sh YYYY-MM-DD		sudo ./RestoreCommandCenterDatabase.sh YYYY-MM-DD_HHMMSS

	==Edit install.conf ==		==Edit install.conf ==

2025-08-08T03:01:14Z

Note: Restoring the database

← Older revision		Revision as of 03:01, 8 August 2025
Line 336:		Line 336:

	chmod +x *.sh		chmod +x *.sh
	sudo ./RestoreCommandCenterDatabase.sh YYYY-MM-DD		sudo ./RestoreCommandCenterDatabase.sh YYYY-MM-DD_HHMMSS

	Check your database backup sql file under '''$home_directory/commandcenter/backup''' folder, they are named '''commandcenter_backup_$current_date.s'''ql, for example, if you backup the database on 2023 September 20th, you will see a commandcenter_backup_2023-09-20.sql file, and you can use below command to restore it		Check your database backup sql file under '''$home_directory/commandcenter/backup''' folder, they are named '''commandcenter_backup_$current_date.s'''ql, for example, if you backup the database on 2023 September 20th, you will see a commandcenter_backup_2023-09-20.sql file, and you can use below command to restore it

	sudo ./RestoreCommandCenterDatabase.sh 2023-09-20		sudo ./RestoreCommandCenterDatabase.sh 2023-09-20_482027

	== Return to the previous version ==		== Return to the previous version ==

2025-04-17T12:56:33Z

← Older revision		Revision as of 12:56, 17 April 2025
Line 119:		Line 119:
	Otherwise, follow this link for a suggested HTTPS configuration:		Otherwise, follow this link for a suggested HTTPS configuration:
	* [[ HTTPS configuration \| HTTPS Configuration ]]		* [[ HTTPS configuration \| HTTPS Configuration ]]

			==HTTP/2==

			HTTP/2 is recommended but not necessary for the Command Center installation as it will provide a noticeable performance boost when leveraged. HTTP/2 does require HTTPS be used so this will only be possible if the previous HTTPS configuration has already been performed.

			If HTTP/2 support will be added, follow this link for a suggested HTTP/2 configuration:
			* [[ HTTP2 Configuration \| HTTP2 Configuration ]]

	== Email Sender ==		== Email Sender ==

2025-01-23T23:00:37Z

Moving from a non SSO to an SSO configuration

← Older revision		Revision as of 23:00, 23 January 2025
Line 363:		Line 363:
	# Provide your saml directory, idp.xml, sp.xml, saml_configuration.conf and saml-keystore.jks file must be in this directory		# Provide your saml directory, idp.xml, sp.xml, saml_configuration.conf and saml-keystore.jks file must be in this directory
	samlpath=		samlpath=

			See: [[Command Center SSO Installation]]

	==Run UpdateCommandCenter.sh==		==Run UpdateCommandCenter.sh==

2025-01-23T23:00:10Z

SSO

← Older revision		Revision as of 23:00, 23 January 2025
Line 161:		Line 161:
	* SSO Connection		* SSO Connection
	* Management		* Management

			See: [[Command Center SSO Installation]]

	= New Command Center Installation =		= New Command Center Installation =

2025-01-23T18:07:36Z

Edit install.conf

← Older revision		Revision as of 18:07, 23 January 2025
Line 354:		Line 354:

	See full [[Command_Center_Installation#Configuration \| Configuration ]] above.		See full [[Command_Center_Installation#Configuration \| Configuration ]] above.

			=== Moving from a non SSO to an SSO configuration ===

	If you need to update your Command Center from non SSO version to SSO version, you need to have samlpath set up in install.conf file, and idp.xml, sp.xml, saml_configuration.conf and saml-keystore.jks file must be in this directory		If you need to update your Command Center from non SSO version to SSO version, you need to have samlpath set up in install.conf file, and idp.xml, sp.xml, saml_configuration.conf and saml-keystore.jks file must be in this directory