cobi.wms:installation_guides
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
cobi.wms:installation_guides [2022/05/02 13:23] – tkammer | cobi.wms:installation_guides [2025/02/19 14:29] (current) – thuth | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
The steps you need to follow for implementing COBI.wms depend on the type of your SAP Business One installation. | The steps you need to follow for implementing COBI.wms depend on the type of your SAP Business One installation. | ||
- | |||
- | ===== On-premises or private cloud, MS SQL Server, SBO 9.3 or earlier ===== | ||
- | |||
- | If you have an **on-premises or private cloud** installation of SAP Business One **Version 9.3 or older**, based on Microsoft **SQL Server** then please refer to the following steps. | ||
- | |||
- | - Import the **[[B1i Scenario Package]]** | ||
- | - Afterwards, copy the **Trigger** URL as described in the linked page and temporarily save it somewhere | ||
- | - Follow all the steps of the following section (on-prem with Service Layer), with the following differences: | ||
- | - Use the Trigger URL for the '' | ||
- | - Make sure that TCP Port 8080 for Integration Framework is opened on the server | ||
===== On-premises or private cloud, with Service Layer ===== | ===== On-premises or private cloud, with Service Layer ===== | ||
Line 19: | Line 9: | ||
- Create the **[[Management Database]]** | - Create the **[[Management Database]]** | ||
- Create the database itself by copy-pasting the correct creation script into //SQL Server Management Studio// or //HANA Studio// | - Create the database itself by copy-pasting the correct creation script into //SQL Server Management Studio// or //HANA Studio// | ||
- | - Import licenses | + | - Add SAP Business One connections |
- | - Add SAP Business One connections | + | - Import licenses |
- (For HANA: Install and start the **[[HANA Proxy]]**) | - (For HANA: Install and start the **[[HANA Proxy]]**) | ||
- | - Install COBI.wms from the Google Play Store on an Android device that can access the SAP Business One server | ||
- Make sure that the TCP ports for direct DB queries and Service Layer are not blocked | - Make sure that the TCP ports for direct DB queries and Service Layer are not blocked | ||
- MS SQL Server: 1433 | - MS SQL Server: 1433 | ||
- HANA Proxy: 30075 | - HANA Proxy: 30075 | ||
- Service Layer: 50000 (https) or 50001 (http) | - Service Layer: 50000 (https) or 50001 (http) | ||
- | - (optional) Use **{{cobiwms-config.html}}** to generate a Settings QR Code | + | |
- | - Open COBI.wms on the Android device and scan the Settings QR Code (or enter the settings manually) | + | |
+ | - Open COBI.wms on the Android device and scan the Settings QR Code or enter the settings manually | ||
- Click Connect and take note of the device ID on the right side of the screen below the Login button | - Click Connect and take note of the device ID on the right side of the screen below the Login button | ||
- | - Assign a license to that device ID (see Management | + | - Assign a license to that device ID (see [[Management_database# |
- | - Log in to COBI.wms | + | - Log in to COBI.wms and make a test booking |
- | - (optional) Create COBI.wms users in the Management Database | + | - (optional) Create COBI.wms users in the Management Database |
- | - (optional) Disable all modules for all devices and enable them for users instead to force user login | + | - (optional) Disable all modules for all devices and enable them for users instead to force user login (see [[management_database# |
+ | |||
+ | ===== (SBO 9.3 or earlier only) On-premises or private cloud, MS SQL Server ===== | ||
+ | |||
+ | **Warning: The use of Integration Framework with COBI.wms is deprecated and highly discouraged for new installations. | ||
+ | |||
+ | If you have an **on-premises or private cloud** installation of SAP Business One **Version 9.3 or older**, based on Microsoft **SQL Server** then please refer to the following steps. | ||
+ | |||
+ | - Import the **[[B1i Scenario Package]]** | ||
+ | - Afterwards, copy the **Trigger** URL as described in the linked page and temporarily save it somewhere | ||
+ | - Follow all the steps of the previous section (on-prem with Service Layer), with the following differences: | ||
+ | - Use the Trigger URL for the '' | ||
+ | - Make sure that TCP Port 8080 for Integration Framework is opened on the server | ||
===== Public cloud ===== | ===== Public cloud ===== | ||
Line 59: | Line 61: | ||
When connecting to a cloud deployment of SAP Business One, COBI.wms cannot establish a direct database connection and instead has to request all data over Service Layer. | When connecting to a cloud deployment of SAP Business One, COBI.wms cannot establish a direct database connection and instead has to request all data over Service Layer. | ||
- | This is done by checking **Update SQL queries** in the login screen, below the login button, before logging in. (This will create the Queries if they were not created yet, and update them to the newest version if they were already created but not up-to-date, so it's recommended to do this once for every new version of COBI.wms.) | + | This is done by checking **Update SQL Queries** in the login screen, below the login button, before logging in. (This will create the Queries if they were not created yet, and update them to the newest version if they were already created but not up-to-date, so it's recommended to do this once for every new version of COBI.wms.) |
For this SQL Query creation/ | For this SQL Query creation/ | ||
Line 72: | Line 74: | ||
* **[[Print Settings]]**: | * **[[Print Settings]]**: | ||
* **[[Label Templates]]**: | * **[[Label Templates]]**: | ||
+ | |||
+ | ===== FAQ ===== | ||
+ | ==== SQL Server Port Issue: ==== | ||
+ | When connecting to the SQL Server, you may encounter issues that are often related to firewall restrictions or SQL Server configuration problems. | ||
+ | |||
+ | **Explanation: | ||
+ | The issue is typically due to one of the following reasons:\\ | ||
+ | - **Firewall Blockage:** The SQL port (commonly port 1433) might not be open between the COBI.wms device and the SAP Server. \\ | ||
+ | - **Server Configuration: | ||
+ | |||
+ | **Steps to Diagnose and Resolve:** | ||
+ | |||
+ | 1. **Check Port Accessibility: | ||
+ | - From any Windows client on the same network as the COBI.wms device, open a PowerShell console. | ||
+ | - Execute the following command (replace `< | ||
+ | PowerShell: | ||
+ | | ||
+ | |||
+ | | ||
+ | The PowerShell output should show `TcpTestSucceeded : True`. | ||
+ | If it shows **False**, the port is likely blocked by the firewall. | ||
+ | |||
+ | 2. **Verify SQL Server Configuration: | ||
+ | - If the port is accessible (i.e., `TcpTestSucceeded` is True) but the connection still fails, the SQL Server might be blocking TCP/IP connections. | ||
+ | - On the server running the SAP MSSQL Server, open **SQL Server Configuration Manager**. | ||
+ | - Navigate to **SQL Server Network Configuration** → **Protocols for [InstanceName]** | ||
+ | | ||
+ | - **Ensure that TCP/IP is enabled.** | ||
+ | |||
+ | 3. **Using a Dynamic TCP/IP Port (if necessary): | ||
+ | - If problems persist, consider connecting via the dynamic TCP/IP port: | ||
+ | - In **SQL Server Configuration Manager**, double-click on **TCP/IP**. | ||
+ | - Go to the **IP Addresses** tab and locate the dynamic port setting. | ||
+ | - Enter the dynamic port number in COBI.wms under the " | ||
+ | - Make sure the dynamic port is also allowed through the firewall. | ||
+ | You can verify this by running the PowerShell command again, substituting port 1433 with the dynamic port number. | ||
+ | |||
+ | **Customer Confirmation: | ||
+ | One customer confirmed that switching to the dynamic port resolved their connection issues. | ||
+ |
cobi.wms/installation_guides.1651490587.txt.gz · Last modified: 2022/05/02 13:23 by tkammer