Installing SAFEQ Cloud unattended/silently

The SAFEQ Cloud installer supports installing unattended or silently, for example to install SAFEQ Cloud using an automated script to very quickly install, configure and deploy SAFEQ Cloud in larger configurations.

The unattended installation is done by:

Creating a configuration file with settings for the server
Running the SAFEQ Cloud installer with command line switch

Configuration file

Create the configuration in an editor such as Notepad+ or SublimeText on Windows or gedit or vi on Linux.

CODE

############################################################################
# Server role, one of: primary, primary-cluster, primary-customer, secondary
############################################################################
HCP_SERVER_ROLE=primary

###########################################
# for all roles: domain name of the account
###########################################
HCP_PRIMARY_ACCOUNT_DOMAIN=acme.eop.com

# default keystore to use instead of the built-in one
HCP_DEFAULT_KEYSTORE=""

# password for default keystore
HCP_DEFAULT_KEYSTORE_PASSWORD=""

# default truststore to use instead of the built-in one
HCP_DEFAULT_TRUSTSTORE=""

# password for default truststore
HCP_DEFAULT_TRUSTSTORE_PASSWORD=""

# Default API key. For primary server it will be added to root account.
# For secondary server it will be used when registering it.
HCP_DEFAULT_API_KEY=

# default API key name, only for primary server.
# If not specified the "API key created by unattended install" name will be used.
HCP_DEFAULT_API_KEY_NAME=

#############################
# Settings for secondary role
#############################
HCP_PRIMARY_SERVER_ADDRESS=

###############################################
# Settings for primary or primary-customer role
###############################################

# name of the root account
HCP_PRIMARY_ACCOUNT_NAME="acme"

# default admin user name
HCP_ADMIN_USERNAME="admin"

# default admin password
HCP_ADMIN_PASSWORD="admin"

# database cluster type: builtin or external
HCP_DB_CLUSTER_TYPE=builtin

#####################################################################
# Database cluster parameters, for primary-cluster or for external db
#####################################################################
# Database type, pgsql, mssql, oracle
HCP_DB_TYPE=pgsql
# only for pgsql and mssql
HCP_DB_CREATE_DATABASE=yes

# parameters for both eopng_config and eopng_documents data sources
HCP_DB_HOSTNAME=acmedb.eop.com
HCP_DB_PORT=5432
HCP_DB_USERNAME="postgres"
HCP_DB_PASSWORD="postgres"
# only for oracle, database instance name
HCP_DB_NAME=

# only for oracle, parameters for eopng_documents data source
HCP_DB_HOSTNAME2=
HCP_DB_PORT2=
HCP_DB_USERNAME2=
HCP_DB_PASSWORD2=
# only for oracle, database instance name
HCP_DB_NAME2=

# Comma-separated list of services to bootstrap, for primary, primary-customer or secondary.
# Possible service names are: storage,ipp,authentication,api,converter,documentoutput,terminalclient,mobileprint,message
HCP_SERVICES=
HCP_SERVICES_PREFIX=""

Don’t use Notepad to create the configuration files, as Windows line endings will break the configuration file.

If HCP_SERVICES omitted from conf file; if it’s a primary it adds the standard services, and if secondary, no services are added.

If HCP_SERVICES_PREFIX is empty or omitted, it will name them as “authentication service”, “ipp service” etc.

Command line switches

CODE

-i <filename.conf>    - install or upgrade in unattended mode
-u                    - upgrade in unattended mode

For example:

CODE

./safeq-cloud-server-3.0-release-setup-linux-x86_64.bin -i secondary-acme.conf