cobi.wms:print_service
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| cobi.wms:print_service [2023/05/24 15:15] – [How it works / Limitations] tkammer | cobi.wms:print_service [2025/10/22 12:50] (current) – thuth | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| ===== How it works / Limitations ===== | ===== How it works / Limitations ===== | ||
| - | **Currently, | + | **Currently, |
| The service generates XML files and puts them in a folder that is scanned by Coresuite Designer, which takes care of the actual printing. | The service generates XML files and puts them in a folder that is scanned by Coresuite Designer, which takes care of the actual printing. | ||
| Line 25: | Line 25: | ||
| **NOTE:** All of the above is done by Coresuite, not by the COBI.wms Print Service. | **NOTE:** All of the above is done by Coresuite, not by the COBI.wms Print Service. | ||
| - | ===== Installation | + | ===== Installing the COBI.wms Print Service |
| - | Download: {{cobiwms-print-service.zip}} | + | First of all, make sure that a recent version of the Microsoft .NET Framework is installed. |
| - | - Extract | + | Download |
| - | - Run the following command in '' | + | |
| - | - Create '' | + | - Extract the ZIP into a folder called exactly |
| - | - You can now start/stop the service from the MS Windows | + | - Open the folder, right-click on '' |
| + | - At the bottom of the Properties window, check " | ||
| + | - Start '' | ||
| + | - Enter this command: '' | ||
| + | - Create | ||
| + | |||
| + | **Note:** Currently it is not supported to install the service under any other path than '' | ||
| + | |||
| + | After the service is installed and the configuration file is created, you can start/stop the service from the MS Windows | ||
| Example config for single-tenant setup (e.g. on-premises or private cloud): | Example config for single-tenant setup (e.g. on-premises or private cloud): | ||
| Line 69: | Line 77: | ||
| In a multi-tenant environment, | In a multi-tenant environment, | ||
| - | Note that the COBI.wms Print Service does not support encrypted communication. | + | **NOTE: |
| + | |||
| + | ===== Troubleshooting ===== | ||
| + | |||
| + | First of all, make sure that the COBI.wms Print Service and the Coresuite Service are both actually running. | ||
| + | |||
| + | If XML files **are** appearing in the '' | ||
| + | |||
| + | * Make sure the Print Definition ID and Layout ID are configured correctly in the Android app. See [[COBI.wms: | ||
| + | * Make sure Coresuite Service (or an SAP Business One Client with the Coresuite Designer add-on) is running and that it's configured correctly. | ||
| + | |||
| + | If the XML files are **not** appearing in the '' | ||
| + | |||
| + | * Double-check the configuration file. For example, note that you must use double-backslashes ('' | ||
| + | * Make sure the COBI.wms Print Service is really running by using the MS Windows **Services** application. | ||
| + | * Make sure the TCP Port on which the Service is listening can be reached from the Android devices COBI.wms is running on. | ||
| + | * Use the MS Windows **Event Viewer** application on the server on which the COBI.wms Print Service is running, and navigate to **Windows Logs --> Application**, | ||
| + | |||
| + | If the COBI.wms Print Service is running but not logging anything at all, it means that it's not receiving any commands from the Android app, in which case double-check that the TCP Port is open and reachable from the Android devices. | ||
| - | ===== Update | + | ===== Updating |
| - Stop the service. | - Stop the service. | ||
| - | - Extract the contents of the new ZIP file into '' | + | - Extract the contents of the new ZIP file into '' |
| - Start the service. | - Start the service. | ||
cobi.wms/print_service.1684934115.txt.gz · Last modified: by tkammer