implementation:wms:install_licenseconfig
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
implementation:wms:install_licenseconfig [2019/02/22 11:17] vise maintenance v18.4 automatic/manual licensing |
implementation:wms:install_licenseconfig [2019/09/17 13:03] (current) vise upgrading to v19.2 |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ==== 3.2.2. Produmex License Server configuration ==== | + | ==== 3.3.2. Configuring the Produmex License Server ==== |
| - | <WRAP round important>Starting from version 18.4 the license module uses the Boyum IT portal for the licenses. This means that the old license file cannot be used anymore. | + | <WRAP round important>Starting from version 18.4 the license module uses the Boyum IT portal the licenses and the old license file cannot be used anymore. |
| - | So when upgrading from a version older than 18.4 to version 18.4 or higher, you need to make sure that you have a license on the [[https://license.boyum-it.com/Account/Login?ReturnUrl=%2F|Boyum IT Portal]].</WRAP> | + | When upgrading from a version older than 18.4 to version 18.4 or higher, make sure that you have a license on the [[https://license.boyum-it.com/Account/Login?ReturnUrl=%2F|Boyum IT Portal]].</WRAP> |
| - | === 3.2.2.1. Running the Produmex License Configurator === | + | === 3.3.2.1. Running the Produmex License Configurator === |
| - | Run the Produmex License Configurator as follows. | + | 1. On the Produmex Suite Installer screen click on the ''Config'' button of the Produmex License Server. |
| - | * Option 1: On Produmex Suite Installer, click on the ''Config'' button on the line of the installed Produmex License Server. On the opening form click on the ''Run'' button to start the license configurator. | + | |
| - | {{ :implementation:wms:license:run.png |Running the License Configurator}} | + | 2. On the opening form click on the ''Run'' button to start the license configurator. |
| - | * Option 2: Run the Produmex License Configurator file. The file name is: //Produmex.Sbo.Logex.Licensing.Configurator.exe// \\ The file is located in for example: //C:\Program Files (x86)\Produmex\Produmex License Server// \\ Make sure that the License Configurator is started in Administrator mode. | + | Note: In the future the Produmex License Configurator can also be started by running the Produmex.Sbo.Logex.Licensing.Configurator.exe file. Make sure that the License Configurator is started in Administrator mode. (Example of file location: C:\Program Files (x86)\Produmex\Produmex License Server) |
| - | === 3.2.2.2. The license file – online and offline solutions === | + | === 3.3.2.2. The license file – online and offline solutions === |
| The License Configurator offers two different options of licensing, **automatic** and **manual**: | The License Configurator offers two different options of licensing, **automatic** and **manual**: | ||
| Line 19: | Line 18: | ||
| {{ :implementation:wms:license:10.automatic_vs_manual_options.png |}} | {{ :implementation:wms:license:10.automatic_vs_manual_options.png |}} | ||
| - | **Automatic licensing is an online licensing option** implying that with active Internet connection your license is automatically downloaded from the Boyum IT portal. | + | **Automatic licensing is an online licensing option**. With active Internet connection your license is automatically downloaded from the Boyum IT portal. |
| **In contrast, manual licensing is an alternative offline solution.** If you have a problem with automatic licensing, for example you do not have active internet connection, manual licensing makes it possible to add your license data manually. In this case you can obtain the data from the offline license generator of the Boyum IT Portal. | **In contrast, manual licensing is an alternative offline solution.** If you have a problem with automatic licensing, for example you do not have active internet connection, manual licensing makes it possible to add your license data manually. In this case you can obtain the data from the offline license generator of the Boyum IT Portal. | ||
| - | It is also possible to switch between the two options later on. | + | Later on it is also possible to switch between the two options. |
| - | * If you wish to switch from automatic to manual licensing in the future, the current license remains in the system until you add a new license file manually. | + | * If you switch from automatic to manual licensing in the future, the current license remains in the system until you add a new license file manually. |
| - | * If you wish to switch from manual to automatic licensing in the future, the current license remains in the system until the new license file has been downloaded from the portal. Once it is downloaded, the system will use your online license instead of the previously added manual one. | + | * If you switch from manual to automatic licensing in the future, the current license remains in the system until the new license file is downloaded from the portal. Once it is downloaded, the system uses your online license instead of the previously added manual one. |
| - | The next sections will describe the steps of the automatic and the manual licensing process in details. | + | The next sections describe the steps of the automatic and the manual licensing process in details. |
| - | == 3.2.2.2.1. Online solution: automatic licensing == | + | == 3.3.2.2.1. Automatic licensing == |
| - | When you open the License Configurator, the automatic option is checked in by default, therefore the License Configurator will try to download your licensing data from the Boyum IT portal automatically. | + | When you open the License Configurator, the Automatic license type is checked in by default and the License Configurator tries to download your licensing data from the Boyum IT portal automatically. |
| If you have active Internet connection and your license can be downloaded, you will see the following message: | If you have active Internet connection and your license can be downloaded, you will see the following message: | ||
| - | {{ :implementation:wms:license:1.new_automatic_license_file_loaded..png |Automatic license file}} | + | {{ :implementation:install:boyum:20._new_automatic_license_file_loaded.png |Automatic License File Loaded}} |
| - | Click ''OK'' and no further action is needed from your side. | + | 1. Click ''OK''. |
| - | Hereinafter, if you have no internet connection in the future, the License Configurator uses the online license it has downloaded from the Boyum Portal last time. | + | 2. Click ''Save Configuration'', then click ''OK''. |
| - | Please continue with section //3.2.2.3 The License Configurator window//. | + | 3. Click ''Restart Service'', then click ''OK''. |
| - | == 3.2.2.2.2. Offline solution: manual licensing == | + | Note: If you have no internet connection in the future, the License Configurator will use the online license it has downloaded from the Boyum Portal last time. |
| + | |||
| + | If you do not need manual licensing, continue with section //3.3.2.3 The License Configurator window//. | ||
| + | |||
| + | == 3.3.2.2.2. Manual licensing == | ||
| In case you are not connected automatically to the license system or you have no active internet connection, you will see the following error message: | In case you are not connected automatically to the license system or you have no active internet connection, you will see the following error message: | ||
| - | {{ :implementation:wms:license:2.could_not_retrieve_license.png |Online license error message}} | + | {{ :implementation:install:boyum:21._online_license_cannot_be_retrieved.png |Online License Cannot be Retrieved.}} |
| 1. Click ''OK'' and select the Manual option. | 1. Click ''OK'' and select the Manual option. | ||
| - | 2. At this point the License Configurator sends the automatic message that your offline license file cannot be retrieved. Click ''OK''. | + | 2. Now the License Configurator sends the automatic message that your offline license file cannot be retrieved. Click ''OK''. |
| - | {{ :implementation:wms:license:3.could_not_retrieve_license_-_offline.png |Offline license error message}} | + | {{ :implementation:install:boyum:22._offline_license_cannot_be_retrieved.png |Offline License Cannot be Retrieved}} |
| 3. Visit the [[https://license.boyum-it.com/licensekey|offline license generator of Boyum IT Portal]] to get your license data. | 3. Visit the [[https://license.boyum-it.com/licensekey|offline license generator of Boyum IT Portal]] to get your license data. | ||
| Line 62: | Line 65: | ||
| * click ''Submit''. | * click ''Submit''. | ||
| - | Fore more information on how to obtain a manual license, please click [[https://support.boyum-it.com/hc/en-us/articles/226546427-How-to-get-a-manual-license|here]]. | + | Note: For more information on the installation number click [[https://support.boyum-it.com/hc/en-us/articles/226546427-How-to-get-a-manual-license|here]]. |
| {{ :implementation:wms:license:get_manual_license.png |Get manual license}} | {{ :implementation:wms:license:get_manual_license.png |Get manual license}} | ||
| Line 72: | Line 75: | ||
| 5. Copy all the data to a new document of a text editor and save it to your local drive as a txt file. This will be your license file. | 5. Copy all the data to a new document of a text editor and save it to your local drive as a txt file. This will be your license file. | ||
| - | 6. On the License Configurator window click on the ''Choose new license file'' button and browse the license file. | + | 6. On the License Configurator screen click on the ''Choose new license file'' button and browse the license file. |
| - | + | ||
| - | {{ :implementation:wms:license:4.choose_new_license_file.png |Choose new license file}} | + | |
| 7. The License Configuration informs you that your manual license file has been loaded. Click ''OK''. | 7. The License Configuration informs you that your manual license file has been loaded. Click ''OK''. | ||
| - | |||
| - | {{ :implementation:wms:license:5.manual_license_file_has_been_loaded.png |Manual license loaded}} | ||
| 8. Click on the ''Save configuration'' button to save configurations and then click ''OK''. | 8. Click on the ''Save configuration'' button to save configurations and then click ''OK''. | ||
| - | {{ :implementation:wms:license:6._license_file_saved._restart_needed..png |Saving configuration}} | + | 9. Restart the service by clicking on the ''Restart Service'' button. Now you are informed that the license server has started. Click ''OK''. |
| - | 9. Restart the service by clicking on the ''Restart Service'' button. At this point you are informed that the license server has started. Click ''OK''. | + | === 3.3.2.3. The License Configurator screen === |
| - | {{ :implementation:wms:license:7._service_started.png |Restarting service}} | + | {{ :implementation:install:boyum:23._license_configurator_window.png |The License Configurator Screen}} |
| - | === 3.2.2.3. The License Configurator window === | + | On the Licenses section every license from the license file is listed. |
| - | + | ||
| - | a) On the Licenses section every license from the license file is listed. | + | |
| License parameters: | License parameters: | ||
| Line 98: | Line 95: | ||
| * Use Assigned Name (Y/N): Defines whether a user has to be assigned to the license or not. If the ‘UseAssignedName’ option is active for a license, you have to link user(s) to the license. | * Use Assigned Name (Y/N): Defines whether a user has to be assigned to the license or not. If the ‘UseAssignedName’ option is active for a license, you have to link user(s) to the license. | ||
| - | b) Under Assigned Names every company that is included in the configuration file of the license manager is listed. (//Produmex.Sbo.Logex.Licensing.Configurator.exe//) | + | Under Assigned Names every company that is included in the configuration file of the license manager is listed. (//Produmex.Sbo.Logex.Licensing.Configurator.exe//) |
| * Connection Name | * Connection Name | ||
| * Company | * Company | ||
| Licenses that are currently in use are listed on the ‘Active licenses’ tab. | Licenses that are currently in use are listed on the ‘Active licenses’ tab. | ||
| - | * License type = The license type. | + | * License type: The license type. |
| - | * Assigned name = the SBO user/ thin client that is using the license. | + | * Assigned name: The SBO user/ thin client that is using the license. |
| - | * User name = The Windows user that is using the license. | + | * User name: The Windows user that is using the license. |
| - | * User domain = The server/PC where the license is being used. | + | * User domain: The server/PC where the license is being used. |
| - | * Process ID = The Process ID that is using the license. | + | * Process ID: The Process ID that is using the license. |
| + | |||
| + | === 3.3.2.4. License types === | ||
| + | |||
| + | 1. **Produmex WMS Professional license (Add-On)**\\ | ||
| + | It is needed to run the add-on in SAP Business One. On the License Configurator screen this is called //AddOnUser//. | ||
| + | |||
| + | Add-on licenses have to be assigned to specific user(s). The number of assigned users is not limited. Only assigned users are entitled for a Produmex License. | ||
| + | |||
| + | The number of the available licenses defines the number of users that can use the Produmex WMS add-on concurrently. If there are more users than the number of licenses, the principle of “first come, first served” is applied. | ||
| - | {{ :implementation:wms:license:9.active_licenses.png |License Configurator window}} | + | Each time a user starts the add-on, the system checks whether the user is an assigned user and whether there is a free license that can be allocated for the user: |
| + | * If the user is not an assigned user, no license is allocated for the user. | ||
| + | * If the user is an assigned user and there is a free license, the system allocates it to the user. | ||
| + | * If the user is an assigned user and there is no free license, no license is allocated for the user. In this case the Produmex WMS add-on can be started, but when the user tries to open a function that requires a license, an error message is displayed. | ||
| - | === 3.2.2.4. License types === | + | After the user logs out, the system deallocates the license from the user. |
| - | == 3.2.2.4.1. Produmex WMS Professional (Add-On)== | + | Note: One user can only be assigned once even if multiple databases contain the same user. If a given user is logged in one database, the user can only log in another database if there is a free license. If a user is logged in two databases, the user uses two licenses. |
| - | The license that is needed to run the add-on in SAP Business One. On the license configuration this is called ‘AddOnUser’. | + | |
| - | Add-On licenses have to be assigned to specific user(s). The number of the assigned users is not limited. Only assigned users are entitled for a Produmex License. | + | 2. **Produmex WMS Terminal license (Device Client)** \\ |
| + | It is needed to run flows on the Fat Client (a scanner or a touchscreen). On the License Configurator screen this is called //DeviceUser//. | ||
| - | To assign users to the add-on license, first select the company on the top of the Assigned Names section. Then select the license type from the ‘Show available names for type’ dropdown menu. Under ‘Available’ every user available from the selected company is listed. Select the name and click on the left arrow icon to assign it to the selected license type. To retract a user, select its line from the Assignments list and click on the right arrow icon. | + | The terminal licenses are unassigned licenses. If the license has to be assigned, it can be assigned to every Fat Client defined in the Organizational Structure of the company. The number of assigned clients is not limited. |
| - | If different companies have different users, they all have to be configured in the same Produmex license server. You have to get the list of users for each connection string, and assign them all together into a single list of assigned users. | + | Device clients have concurrent licensing meaning that licenses do not have to be assigned to a certain client. Instead the system allows as many concurrent connections as the total number of available licenses. |
| - | The sequence of the assigned users has no impact on license allocation. | + | Each time logging in on a client, the system checks whether there is a free license slot that can be allocated for the client. |
| + | * If there is a free license, the system allocates it to the client. | ||
| + | * If there is no free license, an [[support:supportguidev2:licenseissues#no_fat_client_license_available|error message]] is displayed. | ||
| - | {{ :implementation:wms:license:8.addonuser_license.png |License assignments}} | + | After the logout, the system deallocates the license from the client. |
| - | The number of the available licenses defines the number of users that can use the Produmex Add-On concurrently. If there are more users than the number of licenses, the principle of “first come, first served” will be applied. | + | 3. **Produmex 3PL Module** \\ |
| + | It is needed to use the [[implementation:wms:3plprocess|3PL invoicing]] functionality. On the License Configurator screen this is called //Mod_3PL//. | ||
| - | Each time a user starts the add-on, the system will check whether the user is an assigned user and whether there is a free license that can be allocated for the user: | + | This license is an //unassigned// license. There are 99999 licenses available and when the Mod_3PL license is active, every add-on user has access to the 3PL invoicing functionality. |
| - | * If the user is not an assigned user, no license will be allocated for the user. | + | |
| - | * If the user is an assigned user and there is a free license, the system will allocate it to the user. | + | |
| - | * If the user is an assigned user and there is no free license, no license will be allocated for the user. | + | |
| - | After the user logs out, the system will deallocate the license from the user. | + | |
| - | The Produmex Add-On will load even though there is no allocated license for the user. When the user tries to open a function that requires a license, an error message will be displayed. | + | 4. **Produmex EDI Interface** \\ |
| + | It is needed to use the additional functionality for [[implementation:wms:edi_module|EDI messages]]. On the License Configurator screen this is called //Mod_EDI//. | ||
| - | Please note: One user can only be assigned once, even though multiple databases contain the same user. If a given user is logged in one database, the user can only log in another database if there is a free license. If a user is logged in two databases, he/she uses two licenses. | + | This license is an //unassigned// license. There are 99999 licenses available and when the Mod_EDI license is active, every add-on user has access to the EDI functionality. |
| - | == 3.2.2.4.2. Produmex WMS Terminal (Device Client) == | + | === 3.3.2.5. License assignment === |
| - | The license that is needed to run flows on the device (typically a scanner or a touchscreen). On the license configuration this is called ‘DeviceUser’. | + | To assign users to licenses, proceed as follows. |
| - | The terminal licenses are unassigned licenses. If the license has to be assigned, it can be assigned to every thin client defined in the Organizational Structure of the company. The number of the assigned clients is not limited. | + | {{ :implementation:install:boyum:24._license_assignment.png |License Assignment}} |
| - | Device clients have concurrent licensing meaning that licenses do not have to be assigned to a certain client, but instead the system will allow as many concurrent connections as the total number of available licenses. | + | 1. Select the company on the top of the //Assigned Names// section. |
| - | Each time logging in on a client, the system will check whether there is a free license slot that can be allocated for the client. | + | 2. Select the necessary license type from the //Show available names for type// drop-down menu. Under //Available// every user available from the selected company is listed. |
| - | * If there is a free license, the system will allocate it to the client. | + | |
| - | * If there is no free license, an [[support:supportguidev2:licenseissues#no_fat_client_license_available|error message]] will be displayed. | + | |
| - | After the logout, the system will deallocate the license from the client. | + | 3. Select the name and click on the left arrow icon to assign it to the selected license type. \\ |
| + | If different companies have different users, they all have to be configured on the same Produmex license server. You must get the list of users for each connection string and assign them all together into a single list of assigned users. | ||
| + | |||
| + | Note: The sequence of the assigned users has no impact on license allocation. | ||
| + | 4. Click ''Save Configurations'' and close the License Configurator screens. | ||
| - | == 3.2.2.4.3. Produmex 3PL Module == | + | The next section describes the configuration steps of Produmex SB1 Notification Listener. If you do not need the component, on the Produmex Suite Installer screen click ''Save'' and close the screen. You can continue with section [[implementation:wms:install_storedprocedures|3.4. Adaptation of Stored Procedures]]. |
| - | The license that is needed to use the [[implementation:wms:3plprocess|3PL invoicing]] functionality. On the license configuration this is called ‘Mod_3PL’. | + | |
| - | This license is an ‘Unassigned’ license. There is 99999 licenses available, which means that when the Mod_3PL license is active, every add-on user has access to the 3PL invoicing functionality. | ||
| - | == 3.2.2.4.4. Produmex EDI Interface == | ||
| - | The license that is needed to use the additional functionality for [[implementation:wms:edi_module|EDI messages]]. On the license configuration this is called ‘Mod_EDI’. | ||
| - | This license is an ‘Unassigned’ license. There is 99999 licenses available, which means that when the Mod_EDI license is active, every add-on user has access to the EDI functionality. | ||
implementation/wms/install_licenseconfig.1550834262.txt.gz · Last modified: 2019/02/22 11:17 by vise
