Browserless Application Installer - Revision history

Anw: Categorisation

2024-05-08T11:40:10Z

Categorisation

← Older revision		Revision as of 13:40, 8 May 2024
Line 275:		Line 275:

	This information should be obtained when reporting any issues to Aptean.		This information should be obtained when reporting any issues to Aptean.

			[[Category:Browserless]]

Gxr at 11:51, 15 February 2024

2024-02-15T11:51:20Z

← Older revision		Revision as of 13:51, 15 February 2024
Line 256:		Line 256:
	Browserless Oracle Build 14/02/2024 11:20:24.60		Browserless Oracle Build 14/02/2024 11:20:24.60

	Client: client TMS		Client: {client} TMS
	Build Version: {1.0}		Build Version: 1.0
	Java Version: 17.0.9+9		Java Version: 17.0.9+9
	Production URL: {url}		Production URL: {url}

Gxr at 10:49, 15 February 2024

2024-02-15T10:49:03Z

← Older revision		Revision as of 12:49, 15 February 2024
Line 254:		Line 254:
	The install versions are contained in the file calidus_info.txt, for example:		The install versions are contained in the file calidus_info.txt, for example:

	Browserless Oracle Build 14/02/2024 11:20:24.60		Browserless Oracle Build 14/02/2024 11:20:24.60

	Client: client TMS		Client: client TMS
	Build Version: {1.0}		Build Version: {1.0}
	Java Version: 17.0.9+9		Java Version: 17.0.9+9
	Production URL: {url}		Production URL: {url}
	Test URL: {url}		Test URL: {url}
	QA URL: n/a		QA URL: n/a

	This shows:		This shows:

Gxr: Updates from latest changes

2024-02-15T10:35:33Z

Updates from latest changes

← Older revision		Revision as of 12:35, 15 February 2024
Line 7:		Line 7:

	The installers create the following shortcuts on the Windows Start menu:		The installers create the following shortcuts on the Windows Start menu:
	* Aptean Calidus-TMS		* Aptean Calidus-TMS (or Aptean Calidus-WMS)
	** A link to your test system.		** A link to your test system.
	** A link to your production system.		** A link to your production system.
Line 26:		Line 26:
	File locations for the install are:		File locations for the install are:
	* USER install:		* USER install:
	** C:\Users\{name}\AppData\Roaming\Aptean Calidus-TMS		** C:\Users\{name}\AppData\Roaming\Aptean Calidus-{TMS/WMS}
	* ADMIN install:		* ADMIN install:
	** C:\ProgramData\Aptean Calidus-TMS		** C:\ProgramData\Aptean Calidus-{TMS/WMS}


	The installer includes the Oracle JRE required to run the system - this is NOT installed on the client PC for use by other applications.		The installer includes the Oracle JRE required to run the system - this is NOT installed on the client PC for use by other applications.
Line 37:		Line 38:

	The uninstaller will remove all elements of the application install, including all JRE and temporary elements of the install.		The uninstaller will remove all elements of the application install, including all JRE and temporary elements of the install.

			{{Note}} The uninstaller would generally be executed from the Add/Remove programs windows feature.

	{{Note}} The uninstaller for the Administrative installer will also require administrative privilege to run and remove the application.		{{Note}} The uninstaller for the Administrative installer will also require administrative privilege to run and remove the application.



Line 50:		Line 54:

	{{Note}} The installer used will determine whether administrative rights should be included.		{{Note}} The installer used will determine whether administrative rights should be included.


			== Running the Un-Installer Remotely ==

			The unsintall of the application may be run silently through system administration routes, for example through commissioning or MDM platforms.

			It is recommended that this is then uninstalled through scripts, running the command as follows:

			{uninstaller} /VERYSILENT /SUPPRESSMSGBOXES /NORESTART

			{{Note}} The installer used will determine whether administrative rights should be included.


	{{Note}} Check the following section for other command-line parameters that may be used on installation or uninstallation.		{{Note}} Check the following section for other command-line parameters that may be used on installation or uninstallation.


	== Full Command Line Parameters ==		== Full Command Line Parameters ==
Line 239:		Line 254:
	The install versions are contained in the file calidus_info.txt, for example:		The install versions are contained in the file calidus_info.txt, for example:

	Browserless Oracle Build 24/01/2024 15:35:41.46		Browserless Oracle Build 14/02/2024 11:20:24.60
	Java Version: 17.0.9+9
	~~Frmsal Version~~: ~~290325~~		Client: client TMS
			Build Version: {1.0}
			Java Version: 17.0.9+9
			Production URL: {url}
			Test URL: {url}
			QA URL: n/a

	This shows:		This shows:
	* ''Browserless Oracle Build'' - the date/time of the build for the installer.		* ''Browserless Oracle Build'' - the date/time of the build for the installer.
			* ''Client'' - the client
			* ''Build Version'' - the version of installer
	* ''Java Version'' - the version of the Oracle JRE		* ''Java Version'' - the version of the Oracle JRE
	* ''~~Frmsal Version~~'' - the ~~version of~~ the ~~certified access file and expiry date in DDMMYY form e.g. "290325"~~		* ''Production URL'' - the URL for the production system
			* ''Test URL'' - the URL for the test system
			* ''QA URL'' - the URL for UAT/QA

			There is also an Additional Information section

	This information should be obtained when reporting any issues to Aptean.		This information should be obtained when reporting any issues to Aptean.

Anw: Changed shortcut links

2024-02-14T10:32:05Z

Changed shortcut links

← Older revision		Revision as of 12:32, 14 February 2024
Line 7:		Line 7:

	The installers create the following shortcuts on the Windows Start menu:		The installers create the following shortcuts on the Windows Start menu:
	* Calidus-TMS		* Aptean Calidus-TMS
	** A link to your test system.		** A link to your test system.
	** A link to your production system.		** A link to your production system.
Line 14:		Line 14:
	The links configured are specific to the installer, Aptean's client and applications available to that client.		The links configured are specific to the installer, Aptean's client and applications available to that client.

	Each link is named ~~following the Aptean standard~~:		Each link is named as follows:
	* ~~A 3 character code indicating Aptean's customer e.g. PSD, ABC, etc.~~		* Client Name.
	* A single character indicating the application e.g. ~~"T" for "TMS"~~		* The system type in brackets
	* ~~A 3 character~~ system ~~designation~~		** Prod - the production system
	** ~~PRD~~ - the production system		** Test - the test system
	** ~~TST~~ - the test system
	** UAT - the UAT system.		** UAT - the UAT system.

Anw: Updated with latest version notes

2024-02-14T10:29:04Z

Updated with latest version notes

← Older revision		Revision as of 12:29, 14 February 2024
Line 27:		Line 27:
	File locations for the install are:		File locations for the install are:
	* USER install:		* USER install:
	** C:\Users\{name}\AppData\~~Local\Programs~~\Calidus-TMS~~\{Client-Version}~~		** C:\Users\{name}\AppData\Roaming\Aptean Calidus-TMS
	* ADMIN install:		* ADMIN install:
	** C:\~~Program Files (x86)~~\Calidus-TMS~~\{Client-Version}~~		** C:\ProgramData\Aptean Calidus-TMS

	The installer includes the Oracle JRE required to run the system - this is NOT installed on the client PC for use by other applications.		The installer includes the Oracle JRE required to run the system - this is NOT installed on the client PC for use by other applications.

Anw: Minor correction

2024-01-30T09:53:22Z

Minor correction

← Older revision		Revision as of 11:53, 30 January 2024
Line 34:		Line 34:

	Each application is digitally signed and certified.		Each application is digitally signed and certified.

			The installer also installs an Application Uninstaller application in the application directory shown above: unins000.exe.

			The uninstaller will remove all elements of the application install, including all JRE and temporary elements of the install.

			{{Note}} The uninstaller for the Administrative installer will also require administrative privilege to run and remove the application.

Anw: Minor correction

2024-01-30T09:41:10Z

Minor correction

← Older revision		Revision as of 11:41, 30 January 2024
Line 4:		Line 4:
	Two installers are provided:		Two installers are provided:
	* USER install - does not require admin privileges.		* USER install - does not require admin privileges.
	* ADMIN install - requires Admin privileges.		* ADMIN install - requires Admin privileges, which will be requested when the installer is started, if the user running the installer has the capability of elevating to Administrative level.

	The installers create the following shortcuts on the Windows Start menu:		The installers create the following shortcuts on the Windows Start menu:
Line 44:		Line 44:
	{installer} /VERYSILENT /SP- /SUPPRESSMSGBOXES		{installer} /VERYSILENT /SP- /SUPPRESSMSGBOXES

	{{Note}} The installer used will determine whether ~~adminstrative~~ rights should be included.		{{Note}} The installer used will determine whether administrative rights should be included.

	{{Note}} Check the following section for other command-line parameters that may be used on installation or uninstallation.		{{Note}} Check the following section for other command-line parameters that may be used on installation or uninstallation.

Anw: Added remote installation details

2024-01-30T09:29:19Z

Added remote installation details

← Older revision		Revision as of 11:29, 30 January 2024
Line 37:		Line 37:

	== Running the Installer Remotely ==		== Running the Installer Remotely ==

			The installation application may be run silently through system administration routes, for example through commissioning or MDM platforms.

			It is recommended that this is then installed through scripts, running the command as follows:

			{installer} /VERYSILENT /SP- /SUPPRESSMSGBOXES

			{{Note}} The installer used will determine whether adminstrative rights should be included.

			{{Note}} Check the following section for other command-line parameters that may be used on installation or uninstallation.


			== Full Command Line Parameters ==

	The installer supports the following command-line parameters:		The installer supports the following command-line parameters:

Anw: Initial Creation

2024-01-30T09:22:26Z

Initial Creation

New page

If required, Aptean provides installers that install Start Menu application shortcuts to access your systems.

Two installers are provided:
* USER install - does not require admin privileges.
* ADMIN install - requires Admin privileges.

The installers create the following shortcuts on the Windows Start menu:
* Calidus-TMS
** A link to your test system.
** A link to your production system.
** A link to your UAT system.

The links configured are specific to the installer, Aptean's client and applications available to that client.

Each link is named following the Aptean standard:
* A 3 character code indicating Aptean's customer e.g. PSD, ABC, etc.
* A single character indicating the application e.g. "T" for "TMS"
* A 3 character system designation
** PRD - the production system
** TST - the test system
** UAT - the UAT system.

== Technical Details ==

File locations for the install are:
* USER install:
** C:\Users\{name}\AppData\Local\Programs\Calidus-TMS\{Client-Version}
* ADMIN install:
** C:\Program Files (x86)\Calidus-TMS\{Client-Version}

The installer includes the Oracle JRE required to run the system - this is NOT installed on the client PC for use by other applications.

Each application is digitally signed and certified.

== Running the Installer Remotely ==

The installer supports the following command-line parameters:

;/HELP, /?
:Shows a summary of this information. Ignored if the UseSetupLdr [Setup] section directive was set to no.

;/SP-
:Disables the This will install... Do you wish to continue? prompt at the beginning of Setup. Of course, this will have no effect if the DisableStartupPrompt [Setup] section directive was set to yes.

;/SILENT, /VERYSILENT
:Instructs Setup to be silent or very silent. When Setup is silent the wizard and the background window are not displayed but the installation progress window is. When a setup is very silent this installation progress window is not displayed. Everything else is normal so for example error messages during installation are displayed and the startup prompt is (if you haven't disabled it with DisableStartupPrompt or the '/SP-' command line option explained above).

:If a restart is necessary and the '/NORESTART' command isn't used (see below) and Setup is silent, it will display a Reboot now? message box. If it's very silent it will reboot without asking.

;/SUPPRESSMSGBOXES
:Instructs Setup to suppress message boxes. Only has an effect when combined with '/SILENT' or '/VERYSILENT'.

:The default response in situations where there's a choice is:
* Yes in a 'Keep newer file?' situation.
* No in a 'File exists, confirm overwrite.' situation.
* Abort in Abort/Retry situations.
* Cancel in Retry/Cancel situations.
* Yes (=continue) in a DiskSpaceWarning/DirExists/DirDoesntExist/NoUninstallWarning/ExitSetupMessage/ConfirmUninstall situation.
* Yes (=restart) in a FinishedRestartMessage/UninstalledAndNeedsRestart situation.
:The recommended choice in a PrivilegesRequiredOverridesAllowed=dialog situation.

:5 message boxes are not suppressible:
* The About Setup message box.
* The Exit Setup? message box.
* The FileNotInDir2 message box displayed when Setup requires a new disk to be inserted and the disk was not found.
* Any (error) message box displayed before Setup (or Uninstall) could read the command line parameters.
* Any task dialog or message box displayed by [Code] support functions TaskDialogMsgBox and MsgBox.

;/ALLUSERS
:Instructs Setup to install in administrative install mode. Only has an effect when the [Setup] section directive PrivilegesRequiredOverridesAllowed allows the commandline override.

;/CURRENTUSER
:Instructs Setup to install in non administrative install mode. Only has an effect when the [Setup] section directive PrivilegesRequiredOverridesAllowed allows the commandline override.

;/LOG
:Causes Setup to create a log file in the user's TEMP directory detailing file installation and [Run] actions taken during the installation process. This can be a helpful debugging aid. For example, if you suspect a file isn't being replaced when you believe it should be (or vice versa), the log file will tell you if the file was really skipped, and why.

:The log file is created with a unique name based on the current date. (It will not overwrite or append to existing files.)

:The information contained in the log file is technical in nature and therefore not intended to be understandable by end users. Nor is it designed to be machine-parsable; the format of the file is subject to change without notice.

;/LOG="filename"
:Same as /LOG, except it allows you to specify a fixed path/filename to use for the log file. If a file with the specified name already exists it will be overwritten. If the file cannot be created, Setup will abort with an error message.

;/NOCANCEL
:Prevents the user from cancelling during the installation process, by disabling the Cancel button and ignoring clicks on the close button. Useful along with '/SILENT' or '/VERYSILENT'.

;/NORESTART
:Prevents Setup from restarting the system following a successful installation, or after a Preparing to Install failure that requests a restart. Typically used along with /SILENT or /VERYSILENT.

;/RESTARTEXITCODE=exit code
:Specifies a custom exit code that Setup is to return when the system needs to be restarted following a successful installation. (By default, 0 is returned in this case.) Typically used along with /NORESTART. See also: Setup Exit Codes

;/CLOSEAPPLICATIONS
:Instructs Setup to close applications using files that need to be updated by Setup if possible.

;/NOCLOSEAPPLICATIONS
:Prevents Setup from closing applications using files that need to be updated by Setup. If /CLOSEAPPLICATIONS was also used, this command line parameter is ignored.

;/FORCECLOSEAPPLICATIONS
:Instructs Setup to force close when closing applications.

;/NOFORCECLOSEAPPLICATIONS
:Prevents Setup from force closing when closing applications. If /FORCECLOSEAPPLICATIONS was also used, this command line parameter is ignored.

;/LOGCLOSEAPPLICATIONS
:Instructs Setup to create extra logging when closing applications for debugging purposes.

;/RESTARTAPPLICATIONS
:Instructs Setup to restart applications if possible.

;/NORESTARTAPPLICATIONS
:Prevents Setup from restarting applications. If /RESTARTAPPLICATIONS was also used, this command line parameter is ignored.

;/LOADINF="filename"
:Instructs Setup to load the settings from the specified file after having checked the command line. This file can be prepared using the '/SAVEINF=' command as explained below.

:Don't forget to use quotes if the filename contains spaces.

;/SAVEINF="filename"
:Instructs Setup to save installation settings to the specified file.

:Don't forget to use quotes if the filename contains spaces.

;/LANG=language
:Specifies the language to use. language specifies the internal name of the language as specified in a [Languages] section entry.

:When a valid /LANG parameter is used, the Select Language dialog will be suppressed.

;/DIR="x:\dirname"
:Overrides the default directory name displayed on the Select Destination Location wizard page. A fully qualified pathname must be specified. May include an "expand:" prefix which instructs Setup to expand any constants in the name. For example: '/DIR=expand:{autopf}\My Program'.

;/GROUP="folder name"
:Overrides the default folder name displayed on the Select Start Menu Folder wizard page. May include an "expand:" prefix, see '/DIR='. If the [Setup] section directive DisableProgramGroupPage was set to yes, this command line parameter is ignored.

;/NOICONS
:Instructs Setup to initially check the Don't create a Start Menu folder check box on the Select Start Menu Folder wizard page.

;/TYPE=type name
:Overrides the default setup type.

:If the specified type exists and isn't a custom type, then any /COMPONENTS parameter will be ignored.

;/COMPONENTS="comma separated list of component names"
:Overrides the default component settings. Using this command line parameter causes Setup to automatically select a custom type. If no custom type is defined, this parameter is ignored.

:Only the specified components will be selected; the rest will be deselected.

:If a component name is prefixed with a "*" character, any child components will be selected as well (except for those that include the dontinheritcheck flag). If a component name is prefixed with a "!" character, the component will be deselected.

:This parameter does not change the state of components that include the fixed flag.

:Example:
:Deselect all components, then select the "help" and "plugins" components:
:/COMPONENTS="help,plugins"
:Example:
:Deselect all components, then select a parent component and all of its children with the exception of one:
:/COMPONENTS="*parent,!parent\child"
:/TASKS="comma separated list of task names"
:Specifies a list of tasks that should be initially selected.

:Only the specified tasks will be selected; the rest will be deselected. Use the /MERGETASKS parameter instead if you want to keep the default set of tasks and only select/deselect some of them.

:If a task name is prefixed with a "*" character, any child tasks will be selected as well (except for those that include the dontinheritcheck flag). If a task name is prefixed with a "!" character, the task will be deselected.

:Example:
:Deselect all tasks, then select the "desktopicon" and "fileassoc" tasks:
:/TASKS="desktopicon,fileassoc"
:Example:
:Deselect all tasks, then select a parent task and all of its children with the exception of one:
:/TASKS="*parent,!parent\child"
:/MERGETASKS="comma separated list of task names"
:Like the /TASKS parameter, except the specified tasks will be merged with the set of tasks that would have otherwise been selected by default.

:If UsePreviousTasks is set to yes, the specified tasks will be selected/deselected after any previous tasks are restored.

:Example:
:Keep the default set of selected tasks, but additionally select the "desktopicon" and "fileassoc" tasks:
:/MERGETASKS="desktopicon,fileassoc"
:Example:
:Keep the default set of selected tasks, but deselect the "desktopicon" task:
:/MERGETASKS="!desktopicon"
:/PASSWORD=password
:Specifies the password to use. If the [Setup] section directive Password was not set, this command line parameter is ignored.

:When an invalid password is specified, this command line parameter is also ignored.

The uninstaller supports the following command-line parameters:

;/SILENT, /VERYSILENT
:When specified, the uninstaller will not ask the user for startup confirmation or display a message stating that uninstall is complete. Shared files that are no longer in use are deleted automatically without prompting. Any critical error messages will still be shown on the screen. When '/VERYSILENT' is specified, the uninstallation progress window is not displayed.

:If a restart is necessary and the '/NORESTART' command isn't used (see below) and '/VERYSILENT' is specified, the uninstaller will reboot without asking.

;/SUPPRESSMSGBOXES
:Instructs the uninstaller to suppress message boxes. Only has an effect when combined with '/SILENT' and '/VERYSILENT'. See '/SUPPRESSMSGBOXES' under Setup Command Line Parameters for more details.

;/LOG
:Causes Uninstall to create a log file in the user's TEMP directory detailing file uninstallation and [UninstallRun] actions taken during the uninstallation process. This can be a helpful debugging aid.

:The log file is created with a unique name based on the current date. (It will not overwrite or append to existing files.)

:The information contained in the log file is technical in nature and therefore not intended to be understandable by end users. Nor is it designed to be machine-parsable; the format of the file is subject to change without notice.

;/LOG="filename"
:Same as /LOG, except it allows you to specify a fixed path/filename to use for the log file. If a file with the specified name already exists it will be overwritten. If the file cannot be created, Uninstall will abort with an error message.

;/NORESTART
:Instructs the uninstaller not to reboot even if it's necessary.

== Support Details ==

The application is installed with a signed and certified file denoting the access to the system.

The install versions are contained in the file calidus_info.txt, for example:

Browserless Oracle Build 24/01/2024 15:35:41.46
Java Version: 17.0.9+9
Frmsal Version: 290325

This shows:
* ''Browserless Oracle Build'' - the date/time of the build for the installer.
* ''Java Version'' - the version of the Oracle JRE
* ''Frmsal Version'' - the version of the certified access file and expiry date in DDMMYY form e.g. "290325"

This information should be obtained when reporting any issues to Aptean.