Installation Middleware4j

The application should be downloaded from Downloads

You will find versions for Windows (32 and 64 bit), MacOS and Linux. The screens below show the Windows installation.

Windows will ask you to confirm that you want to install the software. Click Yes if you want to proceed.

<img width="438" alt="middleware01" src="https://github.com/C4J/Commander4j-Middleware/assets/20553038/b26523d2-bf69-4c3c-b13c-24ac566c448e">
The installer will load.....

<img width="626" alt="middleware02" src="https://github.com/C4J/Commander4j-Middleware/assets/20553038/83b8bab9-0ba6-4266-9ca0-d397d7709c76">
Click on Next to begin the install.

<img width="626" alt="middleware03" src="https://github.com/C4J/Commander4j-Middleware/assets/20553038/d2c91591-6a3e-47da-a1cd-8378b49f5137">
The licence is displayed for you to read. If you are happy with it then click Agree.

<img width="627" alt="middleware04" src="https://github.com/C4J/Commander4j-Middleware/assets/20553038/eca82f2c-35dd-4c4f-bfc1-f4a92fa28d33">
The default installation path is shown. I recommend not installing into the Windows Program Files folders as those folders will default to read-only after the install and this will cause issues with message processing and log files.

<img width="626" alt="middleware05" src="https://github.com/C4J/Commander4j-Middleware/assets/20553038/09ca6962-4417-40f5-bee0-529e57314c40">
The install progress is displayed.

<img width="626" alt="middleware06" src="https://github.com/C4J/Commander4j-Middleware/assets/20553038/e040b806-8ca8-42ba-a4bb-30eee7b9309e">
This message will be displayed when the install is complete.

At this point you can run the Middleware GUI application which is just a standard visual status display.

However the middlware application is intended to be an always on backgroud task which just processes messages without any interaction.

To configure middlware to run as a service on a Windows computer use the following steps.

<img width="968" alt="middleware_service0" src="https://github.com/C4J/Commander4j-Middleware/assets/20553038/55755c34-5d20-435f-8353-cb1b11ab63ca">

In order to install a windows service you need to run a command from the command prompt with admin permissions. This is a windows requirement.

<img width="570" alt="middleware_service1" src="https://github.com/C4J/Commander4j-Middleware/assets/20553038/55256158-f792-49b6-b695-5abbf0d1106f">

Windows will ask you if you are sure you want to open the command prompt with admin rights.

<img width="734" alt="middleware_service2" src="https://github.com/C4J/Commander4j-Middleware/assets/20553038/023f670a-5bce-4734-bd2c-61af2275bb69">

When the command prompt has opened you need to change into the folder where you installed the application. Then run the command shown above.

<img width="968" alt="middleware_service3" src="https://github.com/C4J/Commander4j-Middleware/assets/20553038/ba9978b4-a7f4-49a1-8ea0-11c330924f22">

By default the account which a newly created service runs under is "System" which won't allow the program to connect to things like network shares. If you want the middleware to be able to collect and process files from network shares you will need to amend the service to run under a regular windows account - possibly a domain account. The account to use is your choice and depends on the folder/share/file permissions that you want the middleware to access. See the next screen for information on how to assign a specific account to the service.

<img width="1197" alt="middleware_service4" src="https://github.com/C4J/Commander4j-Middleware/assets/20553038/6cbf2ea9-99bd-4cd5-bc83-8ce4db1bfc0e">