Silent Installation
Silent installation is useful when you need to deploy ActiveBatch on many machines.
Note: The installation features did change significantly with ActiveBatch V12. Earlier version silent installs need to be reviewed and modified accordingly.
The portion of the installation that is silenced is the User Interface (or interactive) portion of the install. ActiveBatch uses the Windows Installer (msiexec). To invoke the Windows Installer directly start a CMD session. Msiexec uses a combination of parameters and qualifiers. To install a software product you invoke the /package (or /install) qualifier. That qualifier takes the file specification of the input .msi file.
Msiexec /package activebatch.msi
The above command will start an ActiveBatch installation. For troubleshooting purposes, you can add the /log qualifier. Depending on the value of the log file various information can be logged for later analysis. Adding /q (for quiet) allows you to bypass the user interface portion of the installation. Adding /l (for logging) allows you to log the Windows Installer events in a log file.
Normally an installation is interactive in which a person is asked to provide various information that the installation process can act upon. Since this is a silent installation, you must enter that information as part of the command-line. This information is entered through one or more property-value pairs. The syntax for the property-value pair is:
Property=value
If the value contains a string it must be quoted.
To install specific features, you need to use the ADDLOCAL property. This property allows you to add local features. When multiple features are to be added, list them in a comma separated fashion. The main feature ‘Common’, must always be used for installing any feature of ActiveBatch as it contains files which are needed for any feature installed.
The main features are: Common, Client, Job_Scheduler, Client, REST_API, Reporting_Services and Execution_Agent. The default will install all features. Components must be passed in a specific order ("Common, Client, Administration, Tools, Client_Tools,Management_Tools,Job_Scheduler,Execution_Agent") and Job Scheduler must be configured for the installation to succeed.
Client sub features are: Administration_Tools (Availability Manager, Service Manager, and Update Service), Management_Tools (ActiveBatch Console, Dashboard, Management Utilities), and Client_Tools (Date Test, Date Admin, Date Sub, and command-line interface). Please note that the Client feature must be present when specifying the sub-features to ensure inclusion of files that are common to all Client sub-features.
For example, in order to install an Execution Agent with the ActiveBatch Console, the ADDLOCAL would use a comma separated list (without spaces) of: ADDLOCAL=Common,Client,Management_Tools,Execution_Agent.
DEK and TK values can be passed to the ActiveBatch installer during silent install.
INSTALLDIR (Optional). If specified, indicates the target location the product is install to. By default, C:\Program Files\ASCI\ActiveBatchv14 is used. Note: If a 32-bit installation is performed on a 64-bit system, \Program Files (x86)\ASCI\ActiveBatchV14 will be used.
INSTALLFOLDERX86 (Optional). If specified, indicates the 32-bit location of x86 program files for a 64-bit installation of the 64-bit ActiveBatch kit. Default is \Program Files (x86)\ASCI\ActiveBatchV14.
ABAT_EA_USERNAME. This parameter represents the service username of the Execution Agent. It is only applicable if the Execution Agent is being installed.
ABAT_EA_PASSWORD. This parameter represents the service username of the Execution Agent password. It is only applicable if the Execution Agent is being installed.
ABAT_EA_DESCRIPTION (Optional). If specified, this parameter represents the Directory services published description for the Execution Agent. It is only applicable if the Execution Agent is being installed.
ABAT_EA_NAME (Optional). If specified, this parameter represents the Directory services published name for the Execution Agent. It is only applicable if the Execution Agent is being installed.
ABAT_JSS_DB_CONNECTION_STRING.
This mandatory parameter indicates an Oracle or MSSQL Connection string for a New or Existing database. For MSSQL, this should include a Provider, Data Source, Initial Catalog, type of DB Security should be used, and the SQL Server machine name that hosts the database. For Oracle, this should contain the Provider and Data Source. No default.
ABAT_JSS_DB_ACTION (Optional). If specified, this parameter indicates whether to use an existing database or create a new one. “SetupNewDatabase” indicates that a new database is to be created and used. “SetupExistingDatabase” indicates that an existing database is to be updated from V9/V10/V11/V12 to V14. “JoinExistingDatabase” indicates that an existing V14 database is to be used (as in a failover JSS installation where the DB has already been created or updated). Default=SetupNewDatabase.
ABAT_JSS_DB_USERNAME. This parameter is mandatory for Oracle only and represents the DB username. It is only applicable if the Job Scheduler is being installed. No default.
ABAT_JSS_DB_PASSWORD. This parameter is mandatory for Oracle only and represents the DB user’s password. It is only applicable if the Job Scheduler is being installed. No default.
ABAT_JSS_DB_DATAFILE. This is the Datafile for Oracle Tablespace and is mandatory when creating a new Oracle Database. It is only applicable if the Job Scheduler is being installed. No Default.
ABAT_JSS_DB_TABLESPACENAME. This is the Tablespace name for Oracle and is mandatory when creating a new Oracle Database. It is only applicable if the Job Scheduler is being installed. No Default.
ABAT_JSS_USERNAME. This parameter represents the service username of the Job Scheduler. It is only applicable if the Job Scheduler is being installed.
ABAT_JSS_PASSWORD. This parameter represents the service username of the Job Scheduler’s password. It is only applicable if the Job Scheduler is being installed.
ABAT_JSS_DESCRIPTION (Optional). If specified, this parameter represents the Directory services published description for the Job Scheduler. It is only applicable if the Job Scheduler is being installed.
ABAT_JSS_NAME (Optional). If specified, this parameter represents the Directory services published name for the Job Scheduler. It is only applicable if the Job Scheduler is being installed.
ABAT_JSS_SMTP_FROM. This parameter represents the SMTP From prompt (ie. user@company.com). It is only applicable if the Job Scheduler is being installed.
ABAT_JSS_SMTP_SERVER. This parameter represents the SMTP server. It is only applicable if the Job Scheduler is being installed.
ABAT_JSS_SERIAL_KEY. This property represents one or more serial numbers. If multiple serial numbers are specified, separate each one with a semi-colon. The string value cannot exceed 2048 characters (Windows Installer limitation). This property is required for a Job Scheduler installation.
ABAT_JSS_DB_COLLATIONNAME (Optional). If specified, represents the database collation name to be used when creating a SQL Server database. Default=Server collation default (usually SQL_Latin1_General_CP1_CI_AS).
ABAT_SSP_CERTIFICATESTORENAME (Optional if HTTPS not used). If specified, represents the Certificate Store Name (i.e. My Root, …).
ABAT_SSP_CERTIFICATETHUMBPRINT (Optional if HTTPS not used). If specified, represents the Certificate Thumbprint that will be bound to the Port.
ABAT_SSP_DESCRIPTION (Optional). Description for the configuration.
ABAT_SSP_GENERATECERTIFICATE (Optional if HTTPS not used). If specified, a Boolean value (0 or 1) that indicates whether a request should be made to the domain requesting a certificate. If the request fails, a self-signed certificate that expires in 1 year is created and added to both the Personal and Trusted CA Root Stores. The certificate is then bound to the Port. This option should not be specified, if _CERTIFICATESTORENAME and _CERTIFICATETHUMBPRINT are specified.
ABAT_SSP_HTTPSPORT (Optional). If specified, a port number to be used for HTTPS binding in IIS. The default value is 443.
ABAT_SSP_INSTALLPATH. Install path of the SelfServicePortal.
ABAT_SSP_NAME. Name for the configuration.
ABAT_SSP_SERIAL_KEY. License key used to activate the Self Service Portal.
ABAT_SSP_USEHTTPS. A Boolean value (0 or 1) used to enable the use of HTTPS.
ABAT_SSP_VIRTUALDIRECTORY. The name of the virtual application, and subsequent endpoint name.
ABAT_SSP_WEBSITE. The name of the website you want to install the virtual application to.
ABAT_WC_CERTIFICATESTORENAME (Optional if HTTPS not used). If specified, represents the Certificate Store Name (i.e. My Root, …).
ABAT_WC_CERTIFICATETHUMBPRINT (Optional if HTTPS not used). If specified, represents the Certificate Thumbprint that will be bound to the Port.
ABAT_WC_DESCRIPTION (Optional). Description for the configuration.
ABAT_WC_GENERATECERTIFICATE (Optional if HTTPS not used). If specified, a Boolean value (0 or 1) that indicates whether a request should be made to the domain requesting a certificate. If the request fails, a self-signed certificate that expires in 1 year is created and added to both the Personal and Trusted CA Root Stores. The certificate is then bound to the Port. This option should not be specified, if _CERTIFICATESTORENAME and _CERTIFICATETHUMBPRINT are specified.
ABAT_WC_HTTPSPORT (Optional). If specified, a port number to be used for HTTPS binding in IIS. The default value is 443.
ABAT_WC_INSTALLPATH. Install path of the Web Console.
ABAT_WC_NAME. Name for the configuration.
ABAT_WC_SERIAL_KEY. License key used to activate the Web Console.
ABAT_WC_USEHTTPS. A Boolean value (0 or 1) used to enable the use of HTTPS.
ABAT_WC_VIRTUALDIRECTORY. The name of the virtual application, and subsequent endpoint name.
ABAT_WC_WEBSITE. The name of the website you want to install the virtual application to.
REST_API_PORT. The port on which the REST_API Endpoint will be hosted. DEFAULT VALUE: 443
REST_API_GENERATECERTIFICATE. Issues a request to the domain requesting a certificate. If the request fails, it generates a self-signed certificate that expires in 1 year and adds it to both the Personal and Trusted CA Root stores. Afterward, that certificate is bound to the Port. VALID VALUES: 0 (=false), 1 (=true)
IMPORTANT NOTE: This option should NOT be used if you specify a certificate using REST_API_CERTIFICATESTORENAME & REST_API_CERTIFICATETHUMBPRINT options.
REST_API_CERTIFICATESTORENAME. Specify the Certificate Store Name (i.e. My, Root,...)
IMPORTANT NOTE: This option must be used in conjunction with REST_API_CERTIFICATETHUMBPRINT.
REST_API_CERTIFICATETHUMBPRINT. Specify the Certificate Thumbprint that will be bound to the Port.
IMPORTANT NOTE: This option must be used in conjunction with REST_API_CERTIFICATESTORENAME.
REST_API_DEFAULTAUTHTOKENLIFETIME. The default authentication token lifetime when none is specified on a login. DEFAULT VALUE: 1 hour MAX VALUE: The current value of REST_API_MAXAUTHTOKENLIFETIME option
FORMAT: ddd.hh:mm:ss
REST_API_MAXAUTHTOKENLIFETIME. Sets the maximum lifetime that can be requested for an authentication token on login. DEFAULT VALUE: 30 days MAX VALUE: 365 days FORMAT: ddd.hh:mm:ss