...
With the core-service as an example the call command using an options file (in the same directory) looks like this:
yuuvis_rad_core-service_setup_x.y.z.exe --mode unattended --optionfile install.options |
...
https://learn.microsoft.com/en-us/windows/win32/msi/command-line-options
See here for (optional) parameters: https://help.optimal-systems.com/yuuvisRAD/v80/admin/en/administration/installation/home_installation.htm
...
|
|---|
Finreader
TBD
Capture-Crosscap
...
Download the below “setup.iss” file and and save it in the FineReader12 setup folder (where the setup.exe is).
| View file | ||
|---|---|---|
|
Open the file with a text-editor and adapt the installation directory in line 17 (szDir=<path>) to your needs.
Run “setup.exe /w /s /a /f1 setup.iss” with the working dir being the FineReader12 setup folder. See https://docs.revenera.com/installshield21helplib/helplibrary/IHelpSetup_EXECmdLine.htm for a list of all parameters supported by the installshield setup.exe
Copy the License File to <FineReader12>\Bin and <FineReader12>\Bin64.
Add the Bin and Bin64 folders to the Windows PATH environment variable.
Putting it together
For an automatic, unattended installation the setups should be called one after another in some sort of script or programm. This can for example be a simple batch or powershell script or a Java or C# program. It is also possible to realize this with a Dockerfile, running everything in docker-containers. However there are some things to pay attention to:
The systemuserapikey parameter needs to be defined in the script and equally passed to the core-service and the service-manager. Otherwise the core-service will generate the key itself and you will have to get it out of the registry before being able to pass it to the service-manager.
After the elasticsearch installation the service needs to be started and the file <elastcisearch>\bin\elasticsearch-set-initial-passwords.bat needs to be executed to initialize the elasticsearch users passwords (especially that of the elastic user). The script will return the set passwords on stdout and write the file <elasticsearch>\config\built-in.usr which contains the passwords. For the installation of the service-manager the password of the elastic user is required and thus it needs to be parsed and passed by the script / program.
It is expected that there is a database ready to use - with a db_owner user and the corresponding settings correctly initialized (see the system requirements / installation guid). This needs to be taken care of (in the script / program) beforehand.