CTMS - User contributions [en-gb]

Browserless Application Creation

2024-02-15T13:38:03Z

Gxr:

{{Note}} '''For internal use only'''

== Introduction ==

All of the code to generate Browserless Oracle installers is located here:
[https://apteanonline.sharepoint.com/:f:/r/teams/RDCALIDUS/Shared%20Documents/CALIDUS%20TMS/BrowserlessOracle?csf=1&web=1&e=vQZ5Qi Browserless Oracle on Sharepoint]

== Folder Contents ==

{{Note}} Folders in red below are working directories and should '''not''' be accessed/maintained when creating builds.

* '''Builds'''

:This directory contains a temporary folder for each client/version built and is generated during the browserless oracle build for each client

* '''Config'''

:This directory contains batch files which are used for configuring each individual client. See the Creating an installer package for details.

* '''Documents'''

:Documentation relating to the process

* '''Installers'''

:This directory contains the built executable installers for release to the client. there will be a folder for each client/version built

* '''Java'''

:This directory contains the java versions which will be build into the installer packages

* '''Resource'''

:This directory contains the scripts, sources and configuration files used in the build

* '''Setup'''

:This directory contains the software which must be installed on the users PC prior to running the installer creation process.
:{{Note}} These are for CREATING installer packages, and are NOT required on the final users machines.

== Creating an Installer package ==

*Pre-Requisites

:InnoSetup and Launch4J must be installed before an installer can be created. Run the installers from the Setup directory and accept all defaults during the process.

*Creation process

The batch script to create an installer is in the main Browserless Oracle directory:

createNewBuild.bat

Before this is executed, a Config script is required. These are stored in the Config directory.

The scripts should be named by client. To create a new script for a new client, copy an existing one, rename and then amend it.

A client script should look like this:

set WMSTMS=
set BUILD=
set PREFIX=
set PROD=
set TEST=
set QA=
set JAVA_VER=
REM **** USE _GENERATE GUI.bat to generate a unique GUID for each client - ONLY DO THIS ONCE PER CLIENT!!!
set GUID=

*WMSTMS - Should be either TMS or WMS dependent on the system
*BUILD - the build version of the installer e.g. 1.0
*PREFIX - the clients "short" code (usually the first part of the database name before tst or prd) e.g. psdt, lfst, schw etc.
*PROD - the Production URL for the client
*TEST - the Production URL for the client
*QA - the Production URL for the client. Leave blank (but do not remove the line) if no QA/UAT system exists.
*GUID - a unique identifier for the client which is used to identify the install in the registry.
:If this is a new client script, run '''_GENERATE GUI.bat''' to generate a new GUID:

Generated GUI:
bcc4b78c-11c7-4bf0-840d-275b5bc729be
This has been pasted into the clipboard - Paste this into the "<client>".bat file on the line GUID=xxx
Press any key to continue . . .

:Paste this value onto the GUID line

:{{Note}} Once generated, these GUID values should not be changed for the client

Once the client script has been created, the '''createNewBuild.bat''' can be executed.

This will prompt for a client ID, which should match the name of the client script.

Once executed, the process will generate all of the files needed for the installer, sign them, and package them into an exe.

Example:

Client: Polar Speed
Polar Speed Browserless Oracle Build 15/02/2024 11:35:45.14
Create calidus_info.txt
launch4j
signtool - EXE
Inno Setup USER
Inno Setup ADMIN
signtool - Installer
Press any key to continue . . .

The above run would create 2 installers (User/Admin) in the Installers directory within Aptean Calidus-TMS or WMS and then a client/version directory:

Aptean Calidus-TMS-Polar Speed_ADMIN.exe
Aptean Calidus-TMS-Polar Speed_USER.exe

These are the signed executable installers which should be issued to the client. {{Note}} '''These installers should be tested on your own PC before issue to the client'''

== Additional Technical Details ==

*'''Java'''

New Java JRE packages should be downloaded from the [https://adoptium.net/en-GB/temurin/releases/?variant=openjdk17&os=windows&arch=x64&package=jre Eclipse Temurin] site and placed in the Java directory as jdk-xxx
{{Note}} This may change if we start using Oracle Java packages.

Once this is done, you should edit '''createJavaJRE.bat''' and change the set JAVA=xxx to match the folder above.

Run '''createJavaJRE.bat''' to create a java-xxx directory which has a cut down version of Java with only the required files to run browserless oracle.

The java-xxx should then be added to the JAVA_VER parameter inside the required Config script for the client.

*'''frmsal'''

The frmsal jar files are located in Resource\frmsal

The build process will try to locate a frmsal file which matches the exe being produced e.g. psdttst.frmsal.jar.
If it finds a specific frmsal for the build it will use this, and if not, it will use the generic frmsal.jar

*'''Signing Certificate'''

The certificate is located in Resource\Aptean. If updated, the following lines will need amending in Resouce\core.bat:

set CERT=..\..\Resource\Aptean\Aptean_Inc.pfx
set CERTPASS=A23cDez37Fx
set CEREX=29/03/2025

*'''Additional Info File'''

The file \Resource\calidus_info_generic.txt will be pulled into the calidus_info.txt file built into the installer exe.

Any '''non-client''' specific info which is required can be added to this file.

[[Category:Browserless]]
[[Category:Development]]

Browserless Application Creation

2024-02-15T13:37:30Z

Gxr:

{{Note}} For internal use only

== Introduction ==

All of the code to generate Browserless Oracle installers is located here:
[https://apteanonline.sharepoint.com/:f:/r/teams/RDCALIDUS/Shared%20Documents/CALIDUS%20TMS/BrowserlessOracle?csf=1&web=1&e=vQZ5Qi Browserless Oracle on Sharepoint]

== Folder Contents ==

{{Note}} Folders in red below are working directories and should '''not''' be accessed/maintained when creating builds.

* '''Builds'''

:This directory contains a temporary folder for each client/version built and is generated during the browserless oracle build for each client

* '''Config'''

:This directory contains batch files which are used for configuring each individual client. See the Creating an installer package for details.

* '''Documents'''

:Documentation relating to the process

* '''Installers'''

:This directory contains the built executable installers for release to the client. there will be a folder for each client/version built

* '''Java'''

:This directory contains the java versions which will be build into the installer packages

* '''Resource'''

:This directory contains the scripts, sources and configuration files used in the build

* '''Setup'''

:This directory contains the software which must be installed on the users PC prior to running the installer creation process.
:{{Note}} These are for CREATING installer packages, and are NOT required on the final users machines.

== Creating an Installer package ==

*Pre-Requisites

:InnoSetup and Launch4J must be installed before an installer can be created. Run the installers from the Setup directory and accept all defaults during the process.

*Creation process

The batch script to create an installer is in the main Browserless Oracle directory:

createNewBuild.bat

Before this is executed, a Config script is required. These are stored in the Config directory.

The scripts should be named by client. To create a new script for a new client, copy an existing one, rename and then amend it.

A client script should look like this:

set WMSTMS=
set BUILD=
set PREFIX=
set PROD=
set TEST=
set QA=
set JAVA_VER=
REM **** USE _GENERATE GUI.bat to generate a unique GUID for each client - ONLY DO THIS ONCE PER CLIENT!!!
set GUID=

*WMSTMS - Should be either TMS or WMS dependent on the system
*BUILD - the build version of the installer e.g. 1.0
*PREFIX - the clients "short" code (usually the first part of the database name before tst or prd) e.g. psdt, lfst, schw etc.
*PROD - the Production URL for the client
*TEST - the Production URL for the client
*QA - the Production URL for the client. Leave blank (but do not remove the line) if no QA/UAT system exists.
*GUID - a unique identifier for the client which is used to identify the install in the registry.
:If this is a new client script, run '''_GENERATE GUI.bat''' to generate a new GUID:

Generated GUI:
bcc4b78c-11c7-4bf0-840d-275b5bc729be
This has been pasted into the clipboard - Paste this into the "<client>".bat file on the line GUID=xxx
Press any key to continue . . .

:Paste this value onto the GUID line

:{{Note}} Once generated, these GUID values should not be changed for the client

Once the client script has been created, the '''createNewBuild.bat''' can be executed.

This will prompt for a client ID, which should match the name of the client script.

Once executed, the process will generate all of the files needed for the installer, sign them, and package them into an exe.

Example:

Client: Polar Speed
Polar Speed Browserless Oracle Build 15/02/2024 11:35:45.14
Create calidus_info.txt
launch4j
signtool - EXE
Inno Setup USER
Inno Setup ADMIN
signtool - Installer
Press any key to continue . . .

The above run would create 2 installers (User/Admin) in the Installers directory within Aptean Calidus-TMS or WMS and then a client/version directory:

Aptean Calidus-TMS-Polar Speed_ADMIN.exe
Aptean Calidus-TMS-Polar Speed_USER.exe

These are the signed executable installers which should be issued to the client. {{Note}} '''These installers should be tested on your own PC before issue to the client'''

== Additional Technical Details ==

*'''Java'''

New Java JRE packages should be downloaded from the [https://adoptium.net/en-GB/temurin/releases/?variant=openjdk17&os=windows&arch=x64&package=jre Eclipse Temurin] site and placed in the Java directory as jdk-xxx
{{Note}} This may change if we start using Oracle Java packages.

Once this is done, you should edit '''createJavaJRE.bat''' and change the set JAVA=xxx to match the folder above.

Run '''createJavaJRE.bat''' to create a java-xxx directory which has a cut down version of Java with only the required files to run browserless oracle.

The java-xxx should then be added to the JAVA_VER parameter inside the required Config script for the client.

*'''frmsal'''

The frmsal jar files are located in Resource\frmsal

The build process will try to locate a frmsal file which matches the exe being produced e.g. psdttst.frmsal.jar.
If it finds a specific frmsal for the build it will use this, and if not, it will use the generic frmsal.jar

*'''Signing Certificate'''

The certificate is located in Resource\Aptean. If updated, the following lines will need amending in Resouce\core.bat:

set CERT=..\..\Resource\Aptean\Aptean_Inc.pfx
set CERTPASS=A23cDez37Fx
set CEREX=29/03/2025

*'''Additional Info File'''

The file \Resource\calidus_info_generic.txt will be pulled into the calidus_info.txt file built into the installer exe.

Any '''non-client''' specific info which is required can be added to this file.

[[Category:Browserless]]
[[Category:Development]]

Browserless Application Creation

2024-02-15T13:36:48Z

Gxr:

{{Note}} For internal use only

== Introduction ==

All of the code to generate Browserless Oracle installers is located here:
[https://apteanonline.sharepoint.com/:f:/r/teams/RDCALIDUS/Shared%20Documents/CALIDUS%20TMS/BrowserlessOracle?csf=1&web=1&e=vQZ5Qi Browserless Oracle on Sharepoint]

== Folder Contents ==

{{Note}} Folders in red below are working directories and should '''not''' be accessed/maintained when creating builds.

* '''Builds'''

:This directory contains a temporary folder for each client/version built and is generated during the browserless oracle build for each client

* '''Config'''

:This directory contains batch files which are used for configuring each individual client. See the Creating an installer package for details.

* '''Documents'''

:Documentation relating to the process

* '''Installers'''

:This directory contains the built executable installers for release to the client. there will be a folder for each client/version built

* '''Java'''

:This directory contains the java versions which will be build into the installer packages

* '''Resource'''

:This directory contains the scripts, sources and configuration files used in the build

* '''Setup'''

:This directory contains the software which must be installed on the users PC prior to running the installer creation process.
:{{Note}} These are for CREATING installer packages, and are NOT required on the final users machines.

== Creating an Installer package ==

*Pre-Requisites

:InnoSetup and Launch4J must be installed before an installer can be created. Run the installers from the Setup directory and accept all defaults during the process.

*Creation process

The batch script to create an installer is in the main Browserless Oracle directory:

createNewBuild.bat

Before this is executed, a Config script is required. These are stored in the Config directory.

The scripts should be named by client. To create a new script for a new client, copy an existing one, rename and then amend it.

A client script should look like this:

set WMSTMS=
set BUILD=
set PREFIX=
set PROD=
set TEST=
set QA=
set JAVA_VER=
REM **** USE _GENERATE GUI.bat to generate a unique GUID for each client - ONLY DO THIS ONCE PER CLIENT!!!
set GUID=

*WMSTMS - Should be either TMS or WMS dependent on the system
*BUILD - the build version of the installer e.g. 1.0
*PREFIX - the clients "short" code (usually the first part of the database name before tst or prd) e.g. psdt, lfst, schw etc.
*PROD - the Production URL for the client
*TEST - the Production URL for the client
*QA - the Production URL for the client. Leave blank (but do not remove the line) if no QA/UAT system exists.
*GUID - a unique identifier for the client which is used to identify the install in the registry.
:If this is a new client script, run '''_GENERATE GUI.bat''' to generate a new GUID:

Generated GUI:
bcc4b78c-11c7-4bf0-840d-275b5bc729be
This has been pasted into the clipboard - Paste this into the "<client>".bat file on the line GUID=xxx
Press any key to continue . . .

:Paste this value onto the GUID line

:{{Note}} Once generated, these GUID values should not be changed for the client

Once the client script has been created, the '''createNewBuild.bat''' can be executed.

This will prompt for a client ID, which should match the name of the client script.

Once executed, the process will generate all of the files needed for the installer, sign them, and package them into an exe.

Example:

Client: Polar Speed
Polar Speed Browserless Oracle Build 15/02/2024 11:35:45.14
Create calidus_info.txt
launch4j
signtool - EXE
Inno Setup USER
Inno Setup ADMIN
signtool - Installer
Press any key to continue . . .

The above run would create 2 installers (User/Admin) in the Installers directory within Aptean Calidus-TMS or WMS and then a client/version directory:

Aptean Calidus-TMS-Polar Speed_ADMIN.exe
Aptean Calidus-TMS-Polar Speed_USER.exe

These are the signed executable installers which should be issued to the client. {{Note}} '''These installers should be tested on your own PC before issue to the client'''

== Additional Technical Details ==

*'''Java'''

New Java JRE packages should be downloaded from the [https://adoptium.net/en-GB/temurin/releases/?variant=openjdk17&os=windows&arch=x64&package=jre Eclipse Temurin] site and placed in the Java directory as jdk-xxx
{{Note}} This may change if we start using Oracle Java packages.

Once this is done, you should edit '''createJavaJRE.bat''' and change the set JAVA=xxx to match the folder above.

Run '''createJavaJRE.bat''' to create a java-xxx directory which has a cut down version of Java with only the required files to run browserless oracle.

The java-xxx should then be added to the JAVA_VER parameter inside the required Config script for the client.

*'''frmsal'''

The frmsal jar files are located in Resource\frmsal

The build process will try to locate a frmsal file which matches the exe being produced e.g. psdttst.frmsal.jar.
If it finds a specific frmsal for the build it will use this, and if not, it will use the generic frmsal.jar

*'''Signing Certificate'''

The certificate is located in Resource\Aptean. If updated, the following lines will need amending in Resouce\core.bat:

set CERT=..\..\Resource\Aptean\Aptean_Inc.pfx
set CERTPASS=A23cDez37Fx
set CEREX=29/03/2025

*'''Additional Info File'''

The file \Resource\calidus_info_generic.txt will be pulled into the calidus_info.txt file build into the installer exe.

Any '''non-client''' specific info which is required can be added to this file.

[[Category:Browserless]]
[[Category:Development]]

Browserless Application Creation

2024-02-15T13:32:39Z

Gxr:

{{Note}} For internal use only

== Introduction ==

All of the code to generate Browserless Oracle installers is located here:
[https://apteanonline.sharepoint.com/:f:/r/teams/RDCALIDUS/Shared%20Documents/CALIDUS%20TMS/BrowserlessOracle?csf=1&web=1&e=vQZ5Qi Browserless Oracle on Sharepoint]

== Folder Contents ==

{{Note}} Folders in red below are working directories and should '''not''' be accessed/maintained when creating builds.

* '''Builds'''

:This directory contains a temporary folder for each client/version built and is generated during the browserless oracle build for each client

* '''Config'''

:This directory contains batch files which are used for configuring each individual client. See the Creating an installer package for details.

* '''Documents'''

:Documentation relating to the process

* '''Installers'''

:This directory contains the built executable installers for release to the client. there will be a folder for each client/version built

* '''Java'''

:This directory contains the java versions which will be build into the installer packages

* '''Resource'''

:This directory contains the scripts, sources and configuration files used in the build

* '''Setup'''

:This directory contains the software which must be installed on the users PC prior to running the installer creation process.
:{{Note}} These are for CREATING installer packages, and are NOT required on the final users machines.

== Creating an Installer package ==

*Pre-Requisites

:InnoSetup and Launch4J must be installed before an installer can be created. Run the installers from the Setup directory and accept all defaults during the process.

*Creation process

The batch script to create an installer is in the main Browserless Oracle directory:

createNewBuild.bat

Before this is executed, a Config script is required. These are stored in the Config directory.

The scripts should be named by client. To create a new script for a new client, copy an existing one, rename and then amend it.

A client script should look like this:

set WMSTMS=
set BUILD=
set PREFIX=
set PROD=
set TEST=
set QA=
set JAVA_VER=
REM **** USE _GENERATE GUI.bat to generate a unique GUID for each client - ONLY DO THIS ONCE PER CLIENT!!!
set GUID=

*WMSTMS - Should be either TMS or WMS dependent on the system
*BUILD - the build version of the installer e.g. 1.0
*PREFIX - the clients "short" code (usually the first part of the database name before tst or prd) e.g. psdt, lfst, schw etc.
*PROD - the Production URL for the client
*TEST - the Production URL for the client
*QA - the Production URL for the client. Leave blank (but do not remove the line) if no QA/UAT system exists.
*GUID - a unique identifier for the client which is used to identify the install in the registry.
:If this is a new client script, run '''_GENERATE GUI.bat''' to generate a new GUID:

Generated GUI:
bcc4b78c-11c7-4bf0-840d-275b5bc729be
This has been pasted into the clipboard - Paste this into the "<client>".bat file on the line GUID=xxx
Press any key to continue . . .

:Paste this value onto the GUID line

:{{Note}} Once generated, these GUID values should not be changed for the client

Once the client script has been created, the '''createNewBuild.bat''' can be executed.

This will prompt for a client ID, which should match the name of the client script.

Once executed, the process will generate all of the files needed for the installer, sign them, and package them into an exe.

Example:

Client: Polar Speed
Polar Speed Browserless Oracle Build 15/02/2024 11:35:45.14
Create calidus_info.txt
launch4j
signtool - EXE
Inno Setup USER
Inno Setup ADMIN
signtool - Installer
Press any key to continue . . .

The above run would create 2 installers (User/Admin) in the Installers directory within Aptean Calidus-TMS or WMS and then a client/version directory:

Aptean Calidus-TMS-Polar Speed_ADMIN.exe
Aptean Calidus-TMS-Polar Speed_USER.exe

These are the signed executable installers which should be issued to the client. {{Note}} '''These installers should be tested on your own PC before issue to the client'''

== Additional Technical Details ==

*'''Java'''

New Java JRE packages should be downloaded from the [https://adoptium.net/en-GB/temurin/releases/?variant=openjdk17&os=windows&arch=x64&package=jre Eclipse Temurin] site and placed in the Java directory as jdk-xxx
{{Note}} This may change if we start using Oracle Java packages.

Once this is done, you should edit '''createJavaJRE.bat''' and change the set JAVA=xxx to match the folder above.

Run '''createJavaJRE.bat''' to create a java-xxx directory which has a cut down version of Java with only the required files to run browserless oracle.

The java-xxx should then be added to the JAVA_VER parameter inside the required Config script for the client.

*'''frmsal'''

The frmsal jar files are located in Resource\frmsal

The build process will try to locate a frmsal file which matches the exe being produced e.g. psdttst.frmsal.jar.
If it finds a specific frmsal for the build it will use this, and if not, it will use the generic frmsal.jar

*'''Signing Certificate'''

The certificate is located in Resource\Aptean. If updated, the following lines will need amending in Resouce\core.bat:

set CERT=..\..\Resource\Aptean\Aptean_Inc.pfx
set CERTPASS=A23cDez37Fx
set CEREX=29/03/2025

.

[[Category:Browserless]]
[[Category:Development]]

Browserless Application Creation

2024-02-15T13:31:49Z

Gxr:

== Installer Creation ==

{{Note}} For internal only

=== Introduction ===

All of the code to generate Browserless Oracle installers is located here:
[https://apteanonline.sharepoint.com/:f:/r/teams/RDCALIDUS/Shared%20Documents/CALIDUS%20TMS/BrowserlessOracle?csf=1&web=1&e=vQZ5Qi Browserless Oracle on Sharepoint]

=== Folder Contents ===

{{Note}} Folders in red below are working directories and should '''not''' be accessed/maintained when creating builds.

* '''Builds'''

:This directory contains a temporary folder for each client/version built and is generated during the browserless oracle build for each client

* '''Config'''

:This directory contains batch files which are used for configuring each individual client. See the Creating an installer package for details.

* '''Documents'''

:Documentation relating to the process

* '''Installers'''

:This directory contains the built executable installers for release to the client. there will be a folder for each client/version built

* '''Java'''

:This directory contains the java versions which will be build into the installer packages

* '''Resource'''

:This directory contains the scripts, sources and configuration files used in the build

* '''Setup'''

:This directory contains the software which must be installed on the users PC prior to running the installer creation process.
:{{Note}} These are for CREATING installer packages, and are NOT required on the final users machines.

== Creating an Installer package ==

*Pre-Requisites

:InnoSetup and Launch4J must be installed before an installer can be created. Run the installers from the Setup directory and accept all defaults during the process.

*Creation process

The batch script to create an installer is in the main Browserless Oracle directory:

createNewBuild.bat

Before this is executed, a Config script is required. These are stored in the Config directory.

The scripts should be named by client. To create a new script for a new client, copy an existing one, rename and then amend it.

A client script should look like this:

set WMSTMS=
set BUILD=
set PREFIX=
set PROD=
set TEST=
set QA=
set JAVA_VER=
REM **** USE _GENERATE GUI.bat to generate a unique GUID for each client - ONLY DO THIS ONCE PER CLIENT!!!
set GUID=

*WMSTMS - Should be either TMS or WMS dependent on the system
*BUILD - the build version of the installer e.g. 1.0
*PREFIX - the clients "short" code (usually the first part of the database name before tst or prd) e.g. psdt, lfst, schw etc.
*PROD - the Production URL for the client
*TEST - the Production URL for the client
*QA - the Production URL for the client. Leave blank (but do not remove the line) if no QA/UAT system exists.
*GUID - a unique identifier for the client which is used to identify the install in the registry.
:If this is a new client script, run '''_GENERATE GUI.bat''' to generate a new GUID:

Generated GUI:
bcc4b78c-11c7-4bf0-840d-275b5bc729be
This has been pasted into the clipboard - Paste this into the "<client>".bat file on the line GUID=xxx
Press any key to continue . . .

:Paste this value onto the GUID line

:{{Note}} Once generated, these GUID values should not be changed for the client

Once the client script has been created, the '''createNewBuild.bat''' can be executed.

This will prompt for a client ID, which should match the name of the client script.

Once executed, the process will generate all of the files needed for the installer, sign them, and package them into an exe.

Example:

Client: Polar Speed
Polar Speed Browserless Oracle Build 15/02/2024 11:35:45.14
Create calidus_info.txt
launch4j
signtool - EXE
Inno Setup USER
Inno Setup ADMIN
signtool - Installer
Press any key to continue . . .

The above run would create 2 installers (User/Admin) in the Installers directory within Aptean Calidus-TMS or WMS and then a client/version directory:

Aptean Calidus-TMS-Polar Speed_ADMIN.exe
Aptean Calidus-TMS-Polar Speed_USER.exe

These are the signed executable installers which should be issued to the client. {{Note}} '''These installers should be tested on your own PC before issue to the client'''

== Additional Technical Details ==

*'''Java'''

New Java JRE packages should be downloaded from the [https://adoptium.net/en-GB/temurin/releases/?variant=openjdk17&os=windows&arch=x64&package=jre Eclipse Temurin] site and placed in the Java directory as jdk-xxx
{{Note}} This may change if we start using Oracle Java packages.

Once this is done, you should edit '''createJavaJRE.bat''' and change the set JAVA=xxx to match the folder above.

Run '''createJavaJRE.bat''' to create a java-xxx directory which has a cut down version of Java with only the required files to run browserless oracle.

The java-xxx should then be added to the JAVA_VER parameter inside the required Config script for the client.

*'''frmsal'''

The frmsal jar files are located in Resource\frmsal

The build process will try to locate a frmsal file which matches the exe being produced e.g. psdttst.frmsal.jar.
If it finds a specific frmsal for the build it will use this, and if not, it will use the generic frmsal.jar

*'''Signing Certificate'''

The certificate is located in Resource\Aptean. If updated, the following lines will need amending in Resouce\core.bat:

set CERT=..\..\Resource\Aptean\Aptean_Inc.pfx
set CERTPASS=A23cDez37Fx
set CEREX=29/03/2025

.

[[Category:Browserless]]
[[Category:Development]]

Browserless Application Creation

2024-02-15T13:29:23Z

Gxr:

== Installer Creation ==

{{Note}} For internal only

=== Introduction ===

All of the code to generate Browserless Oracle installers is located here:
[https://apteanonline.sharepoint.com/:f:/r/teams/RDCALIDUS/Shared%20Documents/CALIDUS%20TMS/BrowserlessOracle?csf=1&web=1&e=vQZ5Qi Browserless Oracle on Sharepoint]

=== Folder Contents ===

{{Note}} Folders in red below are working directories and should '''not''' be accessed/maintained when creating builds.

* '''Builds'''

:This directory contains a temporary folder for each client/version built and is generated during the browserless oracle build for each client

* '''Config'''

:This directory contains batch files which are used for configuring each individual client. See the Creating an installer package for details.

* '''Documents'''

:Documentation relating to the process

* '''Installers'''

:This directory contains the built executable installers for release to the client. there will be a folder for each client/version built

* '''Java'''

:This directory contains the java versions which will be build into the installer packages

* '''Resource'''

:This directory contains the scripts, sources and configuration files used in the build

* '''Setup'''

:This directory contains the software which must be installed on the users PC prior to running the installer creation process.
:{{Note}} These are for CREATING installer packages, and are NOT required on the final users machines.

=== Creating an Installer package ===

*Pre-Requisites

:InnoSetup and Launch4J must be installed before an installer can be created. Run the installers from the Setup directory and accept all defaults during the process.

*Creation process

The batch script to create an installer is in the main Browserless Oracle directory:

createNewBuild.bat

Before this is executed, a Config script is required. These are stored in the Config directory.

The scripts should be named by client. To create a new script for a new client, copy an existing one, rename and then amend it.

A client script should look like this:

set WMSTMS=
set BUILD=
set PREFIX=
set PROD=
set TEST=
set QA=
set JAVA_VER=
REM **** USE _GENERATE GUI.bat to generate a unique GUID for each client - ONLY DO THIS ONCE PER CLIENT!!!
set GUID=

*WMSTMS - Should be either TMS or WMS dependent on the system
*BUILD - the build version of the installer e.g. 1.0
*PREFIX - the clients "short" code (usually the first part of the database name before tst or prd) e.g. psdt, lfst, schw etc.
*PROD - the Production URL for the client
*TEST - the Production URL for the client
*QA - the Production URL for the client. Leave blank (but do not remove the line) if no QA/UAT system exists.
*GUID - a unique identifier for the client which is used to identify the install in the registry.
:If this is a new client script, run '''_GENERATE GUI.bat''' to generate a new GUID:

Generated GUI:
bcc4b78c-11c7-4bf0-840d-275b5bc729be
This has been pasted into the clipboard - Paste this into the "<client>".bat file on the line GUID=xxx
Press any key to continue . . .

:Paste this value onto the GUID line

:{{Note}} Once generated, these GUID values should not be changed for the client

Once the client script has been created, the '''createNewBuild.bat''' can be executed.

This will prompt for a client ID, which should match the name of the client script.

Once executed, the process will generate all of the files needed for the installer, sign them, and package them into an exe.

Example:

Client: Polar Speed
Polar Speed Browserless Oracle Build 15/02/2024 11:35:45.14
Create calidus_info.txt
launch4j
signtool - EXE
Inno Setup USER
Inno Setup ADMIN
signtool - Installer
Press any key to continue . . .

The above run would create 2 installers (User/Admin) in the Installers directory within Aptean Calidus-TMS or WMS and then a client/version directory:

Aptean Calidus-TMS-Polar Speed_ADMIN.exe
Aptean Calidus-TMS-Polar Speed_USER.exe

These are the signed executable installers which should be issued to the client. {{Note}} '''These installers should be tested on your own PC before issue to the client'''

== Additional Technical Details ==

*'''Java'''

New Java JRE packages should be downloaded from the [https://adoptium.net/en-GB/temurin/releases/?variant=openjdk17&os=windows&arch=x64&package=jre Eclipse Temurin] site and placed in the Java directory as jdk-xxx
{{Note}} This may change if we start using Oracle Java packages.

Once this is done, you should edit '''createJavaJRE.bat''' and change the set JAVA=xxx to match the folder above.

Run '''createJavaJRE.bat''' to create a java-xxx directory which has a cut down version of Java with only the required files to run browserless oracle.

The java-xxx should then be added to the JAVA_VER parameter inside the required Config script for the client.

*'''frmsal'''

The frmsal jar files are located in Resource\frmsal

The build process will try to locate a frmsal file which matches the exe being produced e.g. psdttst.frmsal.jar.
If it finds a specific frmsal for the build it will use this, and if not, it will use the generic frmsal.jar

*'''Signing Certificate'''

The certificate is located in Resource\Aptean. If updated, the following lines will need amending in Resouce\core.bat:

set CERT=..\..\Resource\Aptean\Aptean_Inc.pfx
set CERTPASS=A23cDez37Fx
set CEREX=29/03/2025

[[Category:Browserless]]
[[Category:Development]]

Browserless Application Creation

2024-02-15T13:25:29Z

Gxr:

== Installer Creation ==

{{Note}} For internal only

=== Introduction ===

All of the code to generate Browserless Oracle installers is located here:
[https://apteanonline.sharepoint.com/:f:/r/teams/RDCALIDUS/Shared%20Documents/CALIDUS%20TMS/BrowserlessOracle?csf=1&web=1&e=vQZ5Qi Browserless Oracle on Sharepoint]

=== Folder Contents ===

{{Note}} Folders in red below are working directories and should '''not''' be accessed/maintained when creating builds.

* '''Builds'''

:This directory contains a temporary folder for each client/version built and is generated during the browserless oracle build for each client

* '''Config'''

:This directory contains batch files which are used for configuring each individual client. See the Creating an installer package for details.

* '''Documents'''

:Documentation relating to the process

* '''Installers'''

:This directory contains the built executable installers for release to the client. there will be a folder for each client/version built

* '''Java'''

:This directory contains the java versions which will be build into the installer packages

* '''Resource'''

:This directory contains the scripts, sources and configuration files used in the build

* '''Setup'''

:This directory contains the software which must be installed on the users PC prior to running the installer creation process.
:{{Note}} These are for CREATING installer packages, and are NOT required on the final users machines.

=== Creating an Installer package ===

*Pre-Requisites

:InnoSetup and Launch4J must be installed before an installer can be created. Run the installers from the Setup directory and accept all defaults during the process.

*Creation process

The batch script to create an installer is in the main Browserless Oracle directory:

createNewBuild.bat

Before this is executed, a Config script is required. These are stored in the Config directory.

The scripts should be named by client. To create a new script for a new client, copy an existing one, rename and then amend it.

A client script should look like this:

set WMSTMS=
set BUILD=
set PREFIX=
set PROD=
set TEST=
set QA=
set JAVA_VER=
REM **** USE _GENERATE GUI.bat to generate a unique GUID for each client - ONLY DO THIS ONCE PER CLIENT!!!
set GUID=

*WMSTMS - Should be either TMS or WMS dependent on the system
*BUILD - the build version of the installer e.g. 1.0
*PREFIX - the clients "short" code (usually the first part of the database name before tst or prd) e.g. psdt, lfst, schw etc.
*PROD - the Production URL for the client
*TEST - the Production URL for the client
*QA - the Production URL for the client. Leave blank (but do not remove the line) if no QA/UAT system exists.
*GUID - a unique identifier for the client which is used to identify the install in the registry.
:If this is a new client script, run '''_GENERATE GUI.bat''' to generate a new GUID:

Generated GUI:
bcc4b78c-11c7-4bf0-840d-275b5bc729be
This has been pasted into the clipboard - Paste this into the "<client>".bat file on the line GUID=xxx
Press any key to continue . . .

:Paste this value onto the GUID line

:{{Note}} Once generated, these GUID values should not be changed for the client

Once the client script has been created, the '''createNewBuild.bat''' can be executed.

This will prompt for a client ID, which should match the name of the client script.

Once executed, the process will generate all of the files needed for the installer, sign them, and package them into an exe.

Example:

Client: Polar Speed
Polar Speed Browserless Oracle Build 15/02/2024 11:35:45.14
Create calidus_info.txt
launch4j
signtool - EXE
Inno Setup USER
Inno Setup ADMIN
signtool - Installer
Press any key to continue . . .

The above run would create 2 installers (User/Admin) in the Installers directory within Aptean Calidus-TMS or WMS and then a client/version directory:

Aptean Calidus-TMS-Polar Speed_ADMIN.exe
Aptean Calidus-TMS-Polar Speed_USER.exe

These are the signed executable installers which should be issued to the client. {{Note}} '''These installers should be tested on your own PC before issue to the client'''

== Additional Technical Details ==

*'''Java'''

New Java JRE packages should be downloaded from the [https://adoptium.net/en-GB/temurin/releases/?variant=openjdk17&os=windows&arch=x64&package=jre Eclipse Temurin] site and placed in the Java directory as jdk-xxx
{{Note}} This may change if we start using Oracle Java packages.

Once this is done, you should edit '''createJavaJRE.bat''' and change the set JAVA=xxx to match the folder above.

Run '''createJavaJRE.bat''' to create a java-xxx directory which has a cut down version of Java with only the required files to run browserless oracle.

The java-xxx should then be added to the JAVA_VER parameter inside the required Config script for the client.

*'''frmsal'''

*'''Signing Certificate'''

The certificate is located in Resource\Aptean. If updated, the following lines will need amending in Resouce\core.bat:

set CERT=..\..\Resource\Aptean\Aptean_Inc.pfx
set CERTPASS=A23cDez37Fx
set CEREX=29/03/2025

[[Category:Browserless]]
[[Category:Development]]

Browserless Application Creation

2024-02-15T13:12:22Z

Gxr:

== Installer Creation ==

{{Note}} For internal only

=== Introduction ===

All of the code to generate Browserless Oracle installers is located here:
[https://apteanonline.sharepoint.com/:f:/r/teams/RDCALIDUS/Shared%20Documents/CALIDUS%20TMS/BrowserlessOracle?csf=1&web=1&e=vQZ5Qi Browserless Oracle on Sharepoint]

=== Folder Contents ===

{{Note}} Folders in red below are working directories and should '''not''' be accessed/maintained when creating builds.

* '''Builds'''

:This directory contains a temporary folder for each client/version built and is generated during the browserless oracle build for each client

* '''Config'''

:This directory contains batch files which are used for configuring each individual client. See the Creating an installer package for details.

* '''Documents'''

:Documentation relating to the process

* '''Installers'''

:This directory contains the built executable installers for release to the client. there will be a folder for each client/version built

* '''Java'''

:This directory contains the java versions which will be build into the installer packages

* '''Resource'''

:This directory contains the scripts, sources and configuration files used in the build

* '''Setup'''

:This directory contains the software which must be installed on the users PC prior to running the installer creation process.
:{{Note}} These are for CREATING installer packages, and are NOT required on the final users machines.

=== Creating an Installer package ===

*Pre-Requisites

:InnoSetup and Launch4J must be installed before an installer can be created. Run the installers from the Setup directory and accept all defaults during the process.

*Creation process

The batch script to create an installer is in the main Browserless Oracle directory:

createNewBuild.bat

Before this is executed, a Config script is required. These are stored in the Config directory.

The scripts should be named by client. To create a new script for a new client, copy an existing one, rename and then amend it.

A client script should look like this:

set WMSTMS=
set BUILD=
set PREFIX=
set PROD=
set TEST=
set QA=
set JAVA_VER=
REM **** USE _GENERATE GUI.bat to generate a unique GUID for each client - ONLY DO THIS ONCE PER CLIENT!!!
set GUID=

*WMSTMS - Should be either TMS or WMS dependent on the system
*BUILD - the build version of the installer e.g. 1.0
*PREFIX - the clients "short" code (usually the first part of the database name before tst or prd) e.g. psdt, lfst, schw etc.
*PROD - the Production URL for the client
*TEST - the Production URL for the client
*QA - the Production URL for the client. Leave blank (but do not remove the line) if no QA/UAT system exists.
*GUID - a unique identifier for the client which is used to identify the install in the registry.
:If this is a new client script, run '''_GENERATE GUI.bat''' to generate a new GUID:

Generated GUI:
bcc4b78c-11c7-4bf0-840d-275b5bc729be
This has been pasted into the clipboard - Paste this into the "<client>".bat file on the line GUID=xxx
Press any key to continue . . .

:Paste this value onto the GUID line

:{{Note}} Once generated, these GUID values should not be changed for the client

Once the client script has been created, the '''createNewBuild.bat''' can be executed.

This will prompt for a client ID, which should match the name of the client script.

Once executed, the process will generate all of the files needed for the installer, sign them, and package them into an exe.

Example:

Client: Polar Speed
Polar Speed Browserless Oracle Build 15/02/2024 11:35:45.14
Create calidus_info.txt
launch4j
signtool - EXE
Inno Setup USER
Inno Setup ADMIN
signtool - Installer
Press any key to continue . . .

The above run would create 2 installers (User/Admin) in the Installers directory within Aptean Calidus-TMS or WMS and then a client/version directory:

Aptean Calidus-TMS-Polar Speed_ADMIN.exe
Aptean Calidus-TMS-Polar Speed_USER.exe

These are the signed executable installers which should be issued to the client. {{Note}} '''These installers should be tested on your own PC before issue to the client'''

=== Creating an Installer package ===

[[Category:Browserless]]
[[Category:Development]]

Browserless Application Installer

2024-02-15T11:51:20Z

Gxr:

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, 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:
* Aptean Calidus-TMS (or Aptean Calidus-WMS)
** 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 as follows:
* Client Name.
* The system type in brackets
** Prod - the production system
** Test - the test system
** UAT - the UAT system.

== Technical Details ==

File locations for the install are:
* USER install:
** C:\Users\{name}\AppData\Roaming\Aptean Calidus-{TMS/WMS}
* ADMIN install:
** 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.

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 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.

== 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 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.

== Full Command Line Parameters ==

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 14/02/2024 11:20:24.60

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:
* ''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
* ''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.

Browserless Application Creation

2024-02-15T11:39:54Z

Gxr:

== Installer Creation ==

{{Note}} For internal only

=== Introduction ===

All of the code to generate Browserless Oracle installers is located here:
[https://apteanonline.sharepoint.com/:f:/r/teams/RDCALIDUS/Shared%20Documents/CALIDUS%20TMS/BrowserlessOracle?csf=1&web=1&e=vQZ5Qi Browserless Oracle on Sharepoint]

=== Folder Contents ===

{{Note}} Folders in red below are working directories and should '''not''' be accessed/maintained when creating builds.

* '''Builds'''

:This directory contains a temporary folder for each client/version built and is generated during the browserless oracle build for each client

* '''Config'''

:This directory contains batch files which are used for configuring each individual client. See the Creating an installer package for details.

* '''Documents'''

:Documentation relating to the process

* '''Installers'''

:This directory contains the built executable installers for release to the client. there will be a folder for each client/version built

* '''Java'''

:This directory contains the java versions which will be build into the installer packages

* '''Resource'''

:This directory contains the scripts, sources and configuration files used in the build

* '''Setup'''

:This directory contains the software which must be installed on the users PC prior to running the installer creation process.
:{{Note}} These are for CREATING installer packages, and are NOT required on the final users machines.

=== Creating an installer package ===

*Pre-Requisites

:InnoSetup and Launch4J must be installed before an installer can be created. Run the installers from the Setup directory and accept all defaults during the process.

*Creation process

The batch script to create an installer is in the main Browserless Oracle directory:

createNewBuild.bat

Before this is executed, a Config script is required. These are stored in the Config directory.

The scripts should be named by client. To create a new script for a new client, copy an existing one, rename and then amend it.

A client script should look like this:

set WMSTMS=
set BUILD=
set PREFIX=
set PROD=
set TEST=
set QA=
set JAVA_VER=
REM **** USE _GENERATE GUI.bat to generate a unique GUID for each client - ONLY DO THIS ONCE PER CLIENT!!!
set GUID=

*WMSTMS - Should be either TMS or WMS dependent on the system
*BUILD - the build version of the installer e.g. 1.0
*PREFIX - the clients "short" code (usually the first part of the database name before tst or prd) e.g. psdt, lfst, schw etc.
*PROD - the Production URL for the client
*TEST - the Production URL for the client
*QA - the Production URL for the client. Leave blank (but do not remove the line) if no QA/UAT system exists.
*GUID - a unique identifier for the client which is used to identify the install in the registry.
:If this is a new client script, run '''_GENERATE GUI.bat''' to generate a new GUID:

Generated GUI:
bcc4b78c-11c7-4bf0-840d-275b5bc729be
This has been pasted into the clipboard - Paste this into the "<client>".bat file on the line GUID=xxx
Press any key to continue . . .

:Paste this value onto the GUID line

:{{Note}} Once generated, these GUID values should not be changed for the client

Once the client script has been created, the '''createNewBuild.bat''' can be executed.

This will prompt for a client ID, which should match the name of the client script.

Once executed, the process will generate all of the files needed for the installer, sign them, and package them into an exe.

Example:

Client: Polar Speed
Polar Speed Browserless Oracle Build 15/02/2024 11:35:45.14
Create calidus_info.txt
launch4j
signtool - EXE
Inno Setup USER
Inno Setup ADMIN
signtool - Installer
Press any key to continue . . .

The above run would create 2 installers (User/Admin) in the Installers directory within Aptean Calidus-TMS or WMS and then a client/version directory:

Aptean Calidus-TMS-Polar Speed_ADMIN.exe
Aptean Calidus-TMS-Polar Speed_USER.exe

These are the signed executable installers which should be issued to the client.

[[Category:Browserless]]
[[Category:Development]]

Browserless Application Creation

2024-02-15T11:36:32Z

Gxr:

== Installer Creation ==

{{Note}} For internal only

=== Introduction ===

All of the code to generate Browserless Oracle installers is located here:
[https://apteanonline.sharepoint.com/:f:/r/teams/RDCALIDUS/Shared%20Documents/CALIDUS%20TMS/BrowserlessOracle?csf=1&web=1&e=vQZ5Qi Browserless Oracle on Sharepoint]

=== Folder Contents ===

{{Note}} Folders in red below are working directories and should '''not''' be accessed/maintained when creating builds.

* '''Builds'''

:This directory contains a temporary folder for each client/version built and is generated during the browserless oracle build for each client

* '''Config'''

:This directory contains batch files which are used for configuring each individual client. See the Creating an installer package for details.

* '''Documents'''

:Documentation relating to the process

* '''Installers'''

:This directory contains the built executable installers for release to the client. there will be a folder for each client/version built

* '''Java'''

:This directory contains the java versions which will be build into the installer packages

* '''Resource'''

:This directory contains the scripts, sources and configuration files used in the build

* '''Setup'''

:This directory contains the software which must be installed on the users PC prior to running the installer creation process.
:{{Note}} These are for CREATING installer packages, and are NOT required on the final users machines.

=== Creating an installer package ===

*Pre-Requisites

:InnoSetup and Launch4J must be installed before an installer can be created. Run the installers from the Setup directory and accept all defaults during the process.

*Creation process

The batch script to create an installer is in the main Browserless Oracle directory:

createNewBuild.bat

Before this is executed, a Config script is required. These are stored in the Config directory.

The scripts should be named by client. To create a new script for a new client, copy an existing one, rename and then amend it.

A client script should look like this:

set WMSTMS=
set BUILD=
set PREFIX=
set PROD=
set TEST=
set QA=
set JAVA_VER=
REM **** USE _GENERATE GUI.bat to generate a unique GUID for each client - ONLY DO THIS ONCE PER CLIENT!!!
set GUID=

*WMSTMS - Should be either TMS or WMS dependent on the system
*BUILD - the build version of the installer e.g. 1.0
*PREFIX - the clients "short" code (usually the first part of the database name before tst or prd) e.g. psdt, lfst, schw etc.
*PROD - the Production URL for the client
*TEST - the Production URL for the client
*QA - the Production URL for the client. Leave blank (but do not remove the line) if no QA/UAT system exists.
*GUID - a unique identifier for the client which is used to identify the install in the registry.
:If this is a new client script, run '''_GENERATE GUI.bat''' to generate a new GUID:

Generated GUI:
bcc4b78c-11c7-4bf0-840d-275b5bc729be
This has been pasted into the clipboard - Paste this into the "<client>".bat file on the line GUID=xxx
Press any key to continue . . .

:Paste this value onto the GUID line

:{{Note}} Once generated, these GUID values should not be changed for the client

Once the client script has been created, the '''createNewBuild.bat''' can be executed.

This will prompt for a client ID, which should match the name of the client script.

Once executed, the process will generate all of the files needed for the installer, sign them, and package them into an exe.

Example:

Client: Polar Speed
Polar Speed Browserless Oracle Build 15/02/2024 11:35:45.14
Create calidus_info.txt
launch4j
signtool - EXE
Inno Setup USER
Inno Setup ADMIN
signtool - Installer
Press any key to continue . . .

[[Category:Browserless]]
[[Category:Development]]

Browserless Application Creation

2024-02-15T11:31:49Z

Gxr:

Browserless Application Creation

2024-02-15T11:31:18Z

Gxr:

Browserless Application Creation

2024-02-15T11:17:28Z

Gxr:

Browserless Application Creation

2024-02-15T11:07:25Z

Gxr:

Browserless Application Creation

2024-02-15T11:05:06Z

Gxr:

Browserless Application Creation

2024-02-15T11:04:00Z

Gxr:

Browserless Application Creation

2024-02-15T11:03:16Z

Gxr:

Browserless Application Creation

2024-02-15T11:01:50Z

Gxr:

Browserless Application Creation

2024-02-15T11:01:07Z

Gxr:

== Installer Creation ==

{{Note}} For internal only

=== Introduction ===

All of the code to generate Browserless Oracle installers is located here:
[Browserless Oracle on Sharepoint](https://apteanonline.sharepoint.com/:f:/r/teams/RDCALIDUS/Shared%20Documents/CALIDUS%20TMS/BrowserlessOracle?csf=1&web=1&e=vQZ5Qi "Link")

=== Folder Contents ===

{{Note}} Folders in red below are working directories and would not need to be accessed/maintained when creating builds.

* '''Builds'''

This directory contains a folder for each client/version built and is generated during the browserless oracle build for each client

* '''Config'''

This directory contains batch files which are used for configuring each individual client. See the Creating an installer package for details.

* '''Documents'''

Documentation relating to the process

* '''Installers'''

This directory contains the built executable installers for release to the client. there will be a folder for each client/version built

* '''Java'''

This directory contains the java versions which will be build into the installer packages

* '''Resource'''

This directory contains the scripts, sources and configuration files used in the build

* '''Setup'''

This directory contains the software which must be installed on the users PC prior to running the installer creation process.

{{Note}} These are for CREATING installer packages, and is NOT required on the final users machines.

=== Creating an installer package ===

[[Category:Browserless]]
[[Category:Development]]

Browserless Application Installer

2024-02-15T10:49:03Z

Gxr:

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, 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:
* Aptean Calidus-TMS (or Aptean Calidus-WMS)
** 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 as follows:
* Client Name.
* The system type in brackets
** Prod - the production system
** Test - the test system
** UAT - the UAT system.

== Technical Details ==

File locations for the install are:
* USER install:
** C:\Users\{name}\AppData\Roaming\Aptean Calidus-{TMS/WMS}
* ADMIN install:
** 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.

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 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.

== 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 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.

== Full Command Line Parameters ==

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 14/02/2024 11:20:24.60

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:
* ''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
* ''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.

Browserless Application Creation

2024-02-15T10:39:34Z

Gxr:

== Installer Creation ==

{{Note}} For internal only

=== Introduction ===

All of the code to generate Browserless Oracle installers is located here:
[Browserless Oracle on Sharepoint](https://apteanonline.sharepoint.com/:f:/r/teams/RDCALIDUS/Shared%20Documents/CALIDUS%20TMS/BrowserlessOracle?csf=1&web=1&e=vQZ5Qi "Link")

=== Folder Contents ===

{{Note}} Folders in red below are working directories and would not need to be accessed/maintained when creating builds.

==== Builds ====

This directory contains a folder for each client/version built and is generated during the browserless oracle build for each client

==== Config ====

This directory contains batch files which are used for configuring each individual client. See the Creating an installer package for details.

==== Documents ====

Documentation relating to the process

==== Installers ====

This directory contains the built executable installers for release to the client. there will be a folder for each client/version built

==== Java ====

This directory contains the java versions which will be build into the installer packages

==== Resource ====

This directory contains the scripts, sources and configuration files used in the build

==== Setup ====

This directory contains the software which must be installed on the users PC prior to running the installer creation process.

{{Note}} These are for CREATING installer packages, and is NOT required on the final users machines.

=== Creating an installer package ===

[[Category:Browserless]]
[[Category:Development]]

Browserless Application Creation

2024-02-15T10:37:46Z

Gxr: Initial

== Installer Creation ==

{{Note}} For internal only

=== Introduction ===

All of the code to generate Browserless Oracle installers is located here:
[Browserless Oracle on Sharepoint](https://apteanonline.sharepoint.com/:f:/r/teams/RDCALIDUS/Shared%20Documents/CALIDUS%20TMS/BrowserlessOracle?csf=1&web=1&e=vQZ5Qi "Link")

=== Folder Contents ===

{{Note}} Folders in red below are working directories and would not need to be accessed/maintained when creating builds.

==== Builds ====

This directory contains a folder for each client/version built and is generated during the browserless oracle build for each client

==== Config ====

This directory contains batch files which are used for configuring each individual client. See the Creating an installer package for details.

==== Documents ====

Documentation relating to the process

==== Installers ====

This directory contains the built executable installers for release to the client. there will be a folder for each client/version built

==== Java ====

This directory contains the java versions which will be build into the installer packages

==== Resource ====

This directory contains the scripts, sources and configuration files used in the build

==== Setup ====

This directory contains the software which must be installed on the users PC prior to running the installer creation process.

{{Note}} These are for CREATING installer packages, and is NOT required on the final users machines.

=== Creating an installer package ===

Browserless Application Installer

2024-02-15T10:35:33Z

Gxr: Updates from latest changes

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, 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:
* Aptean Calidus-TMS (or Aptean Calidus-WMS)
** 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 as follows:
* Client Name.
* The system type in brackets
** Prod - the production system
** Test - the test system
** UAT - the UAT system.

== Technical Details ==

File locations for the install are:
* USER install:
** C:\Users\{name}\AppData\Roaming\Aptean Calidus-{TMS/WMS}
* ADMIN install:
** 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.

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 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.

== 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 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.

== Full Command Line Parameters ==

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 14/02/2024 11:20:24.60

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:
* ''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
* ''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.