produmex wms - complete installation guidewiki.produmex.name/lib/exe/fetch.php?media=... · windows...

2018/08/08 21:49 1/68 Produmex WMS - Complete Installation Guide

- http://wiki.produmex.name/

Produmex WMS - Complete Installation Guide

Produmex WMS Installation Guide

Disclaimer

This documentation and training is provided to you by Produmex N.V. The documents are neitherapproved nor in any way acknowledged or endorsed by SAP.

For SAP Business One, only the documentation and training officially released by SAP shall be bindingupon SAP. SAP shall not be responsible for any content of this documentation and training and thisdocumentation and training shall not be binding upon SAP in any way.

The official current SAP Business One documentation and training for SAP Business One is available athttp://service.sap.com/smb/sbocustomer.

1. Introduction

This guide explains the Produmex Suite Installer. This tool allows for the complete installation andconfiguration of the Produmex WMS and its components.

The components you can install with this tool are the Produmex Tools, the Produmex License server,the Produmex SB1 Notification listener and the Produmex FatClient. The Produmex add-on isregistered and installed like a regular SAP add-on, however Produmex uses an Add-on loader toupload the files to the database.

How to do this will be described in this guide.

2. Prerequisites

The prerequisites for the installation of the Produmex WMS for SAP Business One are:

Windows Server 2008 (minimum)●

Installation of MS SQL Server or SAP HANA●

Installation of SAP Business One 9●

Installation of .NET 4.6.2 framework (Every machine running Produmex WMS)●

Installation of Crystal Reports basic runtime for Visual Studio 2008●

Administrative rights●

A valid Produmex license-file.●

http://service.sap.com/smb/sbocustomer

Last update:2018/03/1212:56

implementation:wms:completeinstallguide http://wiki.produmex.name/doku.php?id=implementation:wms:completeinstallguide

http://wiki.produmex.name/ Printed on 2018/08/08 21:49

The ComLicenseBridge (Only SQL environment, on server where SAP license service is running)●

After installing the .NET 4.6.2, restart the computer before any other install or upgrade process.

For some prerequisites you can have a look at:ftp://public:[email protected]/Install/Prerequisites

If these are not installed on your computer, please install these prior to the installation of theProdumex WMS components.

Note: if you have any antivirus software installed, you need to add the .exe of the Produmex SuiteInstaller as an exception.

Please make sure all prerequisites are installed, otherwise Produmex will not work!

2.1. HANA database privileges

When using a HANA user other than SYSTEM, you need to grant additional privileges to that user inaddition to the standard privileges recommended by SAP.

You can set the proper privileges by executing the following SQL queries. Make sure you replace theuser, schemas and password before executing the queries. In the examples, the user is calledDBUSER, the company schema is TEST_WMS and the Produmex schema is PMX_TEST_WMS.

Creating a user:

CREATE USER DBUSER PASSWORD B1UserPwd NO FORCE_FIRST_PASSWORD_CHANGE;

SAP recommendations:

ALTER USER DBUSER DISABLE PASSWORD LIFETIME;GRANT AFLPM_CREATOR_ERASER_EXECUTE TO DBUSER WITH ADMIN OPTION;GRANT CONTENT_ADMIN TO DBUSER;GRANT CATALOG READ, CREATE SCHEMA, ROLE ADMIN, USER ADMIN TO DBUSER WITHADMIN OPTION;GRANT EXPORT, IMPORT, INIFILE ADMIN, LOG ADMIN TO DBUSER;GRANT CREATE ANY, SELECT ON SCHEMA SYSTEM TO DBUSER WITH GRANT OPTION;GRANT SELECT, EXECUTE, DELETE ON SCHEMA _SYS_REPO TO DBUSER WITH GRANTOPTION;GRANT SELECT, INSERT, DELETE, UPDATE, EXECUTE, CREATE ANY, DROP ON SCHEMASBOCOMMON TO DBUSER WITH GRANT OPTION;GRANT SELECT, INSERT, DELETE, UPDATE, EXECUTE ON SCHEMA COMMON TO DBUSERWITH GRANT OPTION;

ftp://public:[email protected]/Install/Prerequisites



Additional privileges required for Produmex WMS:

GRANT SELECT, INSERT, DELETE, UPDATE, EXECUTE, CREATE ANY, DROP, ALTER,INDEX, TRIGGER, REFERENCES ON SCHEMA TEST_WMS TO DBUSER WITH GRANT OPTION;CREATE SCHEMA PMX_TEST_WMS; -- skip this line if the PMX schema alreadyexistsGRANT SELECT, INSERT, DELETE, UPDATE, EXECUTE, CREATE ANY, DROP, ALTER,INDEX, TRIGGER, REFERENCES ON SCHEMA PMX_TEST_WMS TO DBUSER WITH GRANTOPTION;

3. Executing a new installation

In this and the following sections we will describe how to perform a full and new installation ofProdumex WMS. First, copy the Produmex Installation Zip File to your computer(Produmex_PNG_XXX.zip)

Make sure that you copy the right version for your system.

32 bit: Produmex_PNG_x_x_ x_x.zip●

64 bit: Produmex_PNG_x_x_ x_x.x64.zip●

It is not possible to mix the two versions in one environment. Make sure that you either use the32 bit or the 64 bit version of the software per environment.

Extract it to a directory (e.g. with the same name as the version number e.g.{driveletter}:\Produmex_PNG_523) Preferably, do not extract it within the {driveletter}:\Program Filesdirectory as this might cause interference with installed components later.

We recommend to keep this directory on a shared folder accessible from all servers. That way youcan use the same configuration when you need to install and upgrade multiple components onseparate systems (e.g.: a SAP server and a terminal server).

When opening the unzipped folder, we need to select the folder corresponding to our SAP version weare running. The supported SAP versions depend on which Produmex Build you are installing. Seehere an example with folders for SAP Versions 9.0 / 9.0 HANA / 9.1 / 9.1 HANA / 9.2 / 9.2 HANA.

Last update:2018/03/1212:56



Afterwards, locate the directory of the Produmex Suite installer (e.g:Produmex_PNG_4_1_1_2\9\ProdumexSuiteInstaller) and execute the .exe. Make sure you haveadministrator privileges when executing this application.

After launching the .exe file, the End User Licence Agreement window will open up. Produmex canonly be installed if the License Agreement is accepted.

After accepting the License Agreement, the system proceeds to Produmex Suite Installer.

Now we can start the configuration, in the following chapters will be describe step-by-step the fieldsyou need to fill in.

3.1. Starting a fresh installation

These steps below detail the initial setup of the Produmex Suite Installer. This configuration can besaved and reused for upgrades. It can also be modified. Please see: 6. Adding a new database to an



existing installation

3.1.1. General Tab

3.1.1.1. System/server related fields

1. Shows the name of the server we are currently running the SuiteInstaller on. It’s recommended tostart the installation on the SAP server. In the example, our SAP server name is DEV_SAP9_FR.

2. Fill the domain name of the server where the SAP license service is installed. This should be exactlythe same as what has been configured in SLD. This should include the port number of the SAP licenseserver. On MSSQL, the port number is typically 30000, and on HANA the port number is typically40000.

3. Fill the domain name of the server where the database is installed. On HANA, the port number ofthe database server should also be included. The default port number is usually 30015.

4. Select the type of the database management system installed on the server.

5. Fill the database username that has dbo rights on the SBO company database(s).

6. Fill the Database user password.

7. Fill the database culture.

3.1.1.2. Database/company related fields

8. Select Production or Test environment. This field corresponds with the Target Environment that isselected on top of the Produmex SuiteInstaller. This feature can be used to install 2 different versionsof the Produmex Suite on 1 server. One version can be the TEST version, and the other version can be

Last update:2018/03/1212:56



the PRODUCTION version. In this field, we will tell the system which database/company will be part ofthe production environment, and which database/company will be used as a test database. Whendoing an initial demo installation, you can leave it as is on production.

9. Fill the Alias for the so-called “ConnectionString”. This will be the name we will use troughout therest of the installation and configuration. It’s highly recommended to use the database name as youralias. This to avoid any confusion.

10. Fill the name of the company database. In the given example it is “SBODemo_US”.

11. Fill the name of the Produmex database. When doing an initial installation, the Produmexdatabase does not exist yet. So it will be created based on the name we give here. It’s recommendedto use the company database name, with a PMX_ prefix. So in the given example is becomes“PMX_SBODemo_US”.

12. Fill the SAP User name. Typically the manager user is used here.

13. Fill the SAP User password. After this data has all been filled, we can test the connections. For thiswe have 2 buttons saying “…test…” for each database/company we have added.

14. This button will test the SBO connection trough DI-API – click it to start the test.

15. This button will test the direct SQL connection trough SQL Native Client – click to test.

When these tests have succeeded, make sure to hit the Save button on the bottom right corner.When saving this configuration, the system will create a .config file that we will re-use later forpotential upgrades.

3.1.2. Creating a new TAB per server

For each server that will have a Produmex WMS component installed, we will make a new tab in theSuiteInstaller screen. Typically, we have at least 2 servers.



SAP server with the Produmex Tools, Fat Client & License Service (and other optional services)●

installed.Terminal server with the Produmex Fat Client (= scanner application) installed.●

The Produmex license server should be installed on the same server as the SAP license server.

We can now add a new tab (for the SAP server in this example) by clicking on the + icon next to theGeneral tab. Then fill the name of the SAP server:

3.1.2.1. Select required components for server

1. With this button, we can tell the application that this is the server we are currently working on. Thiswill be saved so the SuiteInstaller will open on the correct tab, depending on what server you areopening it on. So we need to start by pushing this button to assign this server.

2. When the button was pushed, we can see the name of the server appearing on the “Systemassignment” field.

3. With these checkboxes, we can decide what will have to be installed on this server. Typically, a SAPserver has the Tools, License Server & Fat Client installed. If we need a SBO Notification Listener or a

Last update:2018/03/1212:56



Scalecomm service, this is typically also installed on the SAP server.

4. This shows the current version of the Produmex WMS.

5. This shows the version of the Produmex WMS that we are about to install.

6. These Install buttons allow us to install the components one by one.

7. These Uninstall buttons allow us to uninstall the components one by one.

8. Config button will be used for the Tools & License Server (and for the optional SBO NotificationListener).

9. Install / uninstall all: these buttons will install or uninstall all the checked components.

10. Has custom files checkbox indicates if there are custom files to be installed, such as customerspecific workflowscripts. If this is tagged, you will be prompted for the directory were the custom filesare unzipped to. This directory will have a name such as “Project_OEC_1_0_0_327”.

So in our example, we have checked the Tools, License Server & Fat Client. If we click on “Install all’(9), it will do the installation of all these components:

Please note: It is not possible to have more than one Produmex License Server and Scalecommservice version installed on a server.

If you tagged “Has custom files” on, on the General tab you will be prompted to locate the directory.



Afterwards you need to locate the directory where you can find these files.

3.2. Component configuration

Components, that have an active 'Config' button after they were installed, have their ownconfiguration that needs to be set up. Click on the 'Config' button on the corresponding line to startthe component configuration.

Last update:2018/03/1212:56



3.2.1. Produmex tools configuration

Here you can see the configuration screen for the Produmex tools. Here you can select an instancealias which will connect to a company database that will be updated to the most recent Produmexversion.

Click the 'Start' button to start the UpdateDatabase tool.

This tool consists of 3 steps, which you can enable or disable by using the checkboxes on the top ofthe window:

Upgrade database●

Update localizations●

Update add-on files●

You can also change the connection to use by using the drop-down list on the top of the window. Thedrop-down list is filled with all connection strings found in the configuration file of theUpdateDatabase tool.

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Acompleteinstallguide&media=implementation:wms:installation:config.png



3.2.1.1. Upgrade database

In the first step, the tool will upgrade your database to the most recent Produmex version. This stepwill only be executed if the “Upgrade database” checkbox is activated.

During this step, UDF’s might need to be created in SBO. Seeing how this is an intensive action, thisaction is optional, but vital if you want to complete a full installation.

You can disable the creation of UDF’s by deactivating the “Create User Defined Fields (slow on bigDB’s)” checkbox on the top of the window. In this case, you will have to create the UDF’s manually inSBO; the UpdateDatabase tool will prompt you to do so.

Last update:2018/03/1212:56



If you would like to use the integrated Produmex Manufacturing solution, enable the “Integration withProdumex Manufacturing” checkbox as well. For more information about the how to install theintegrated solution please see: How to work with both Produmex Manufacturing and Produmex WMS.

During the database upgrade, stored procedures are installed or updated as well. ThePMX_SP_TransactionNotification stored procedure is only added in the case of a fresh installation orwhen upgrading from a version lower than 6.3. To update the PMX_SP_TranscationNotification duringthe upgrade, enable the “Force to re-install PMX_SP_TransactionNotification” checkbox.

Only use this checkbox to add the SP when it is missing, but keep in mind that this is a cleaninstall, so if this SP was customized, these customizations will be lost.

Before starting the Tools Upgrade, backup the stored procedure. If for some reason the storedprocedure has to be re-installed, install it manually from the backup.

Run the database upgrade by clicking on the 'Start' button. Here the tool displays its actions. Whenstarting from a new database without previous version of Produmex WMS installed, it will adjust the

http://wiki.produmex.name/doku.php?id=implementation:manufacturing:wms_integration#recommended_installation_steps



database by first adding UDT’s, UDO’s, adding UDF’s to SAP tables, creating PMX-tables, foreign keys,etc..

When this tool is running, and you have selected customer specific files in the previous steps you willsee these kinds of messages:

“Found custom ‘AddUpdateData.cs’: updates the database with custom UDF’s/UDT’s, PMX-tables,●

etc..This cs-script executes custom database-adjustments specific for that customer.“Found custom ‘: If a custom script is found and inserted to the database, you can see the name of●

the script here. In this example a EnterPickingQuantityHookFlow is inserted into the database orupdated if it already exists.

3.2.1.2. Update localizations

The second step performs an update for the localizations. This step will update any translations to themost recent version of the current Produmex WMS version.

This step will only be executed if the “Update localizations” checkbox is activated.

Last update:2018/03/1212:56



3.2.1.3. Update add-on files

The final step you have the option to upload the Produmex suite add-on files necessary to run theProdumex suite add-on.

This step will only be executed if the “Update add-on files” checkbox is activated.



In this screen you can see the files required to upload. By default the Add-on Uploader will search inthe build directory in which it is located.

Select the row(s) corresponding to the installation you are doing, and click ‘Upload’. After uploading,close the screen.

3.2.1.4. Closing the tool

Last update:2018/03/1212:56



After all the selected steps have been executed, you can close the screen. To do so, press the ‘x’cross in the top-right corner of the window.

3.2.2. Produmex License Server configuration

3.2.2.1. Additional installation steps for SAP HANA

If you are using SAP HANA, you need to update the Produmex License Server's configuration file. Thisfile is located in the installation folder of Produmex License Server, for example C:\Program Files(x86)\Produmex\Produmex License Server\

The configuration file is called 'Produmex.Foundation.Licensing.Sbo.ServiceHost.exe.config'

See the picture below to locate it more easily:



Open that file with a text editor (e.g. notepad), and locate the section called 'appSettings':

Locate the line that contains 'SapHanaLicenseServer', and do the following:

uncomment that line (remove the '<! - -' and '- - >' at the beginning and at the end of the line)●

replace the license server (default: imdbhdb:40000) by the actual SAP license server's address●

Finally, save the configuration file.

3.2.2.2. Request a Produmex license

For more information about requiring a license please see: Requesting a Produmex License key

http://wiki.produmex.name/doku.php?id=implementation:general:requestlicense

Last update:2018/03/1212:56



3.2.2.3. Configure licenses

Run the Produmex License Configurator.

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.

Run the Produmex License Configurator file. The file name is:●

Produmex.Sbo.Logex.Licensing.Configurator.exeThe file is located in for example: C:\Program Files (x86)\Produmex\Produmex License ServerMake sure that the License Configurator is started in Administrator mode.

Click on the ‘Choose new license file’ button and browse the license file.

On the Licenses section every license from the license file is listed.

License parameters:

Type: The type of the license.●

Valid Till: The expiration date of the license.●

Count: The number of licenses.●

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.

Under Assigned Names every company that is included in the configuration file of the licensemanager is listed. (Produmex.Sbo.Logex.Licensing.Configurator.exe)

Connection Name●

Company●

Click on the ‘Save configuration button’ to save configurations. Please note: You have to save theconfigurations even if ‘UseAssignedName’ is not active for any license type.

Restart the service by clicking on the ‘Restart Service’ button.

If you restart the service for the first time, and it does not start, make sure you have installed theCOM License bridge AND .NET Framework 4.6.2. (See "Prerequisites" section)

Licenses that are currently in use are listed on the ‘Active licenses’ tab.

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Acompleteinstallguide&media=implementation:wms:license:run.png



License type = The license type.●

Assigned name = the SBO user/ thin client 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.●

Process ID = The Process ID that is using the license.●

3.2.2.4. License types

3.2.2.4.1. Produmex WMS Professional (Add-On)

The license that is needed to run the add-on in SAP Business One. On the license configuration this iscalled ‘AddOnUser’.

Add-On licenses have to be assigned to specific user(s). The number of the assigned users is notlimited. Only assigned users are entitled for a Produmex License.

To assign users to the add-on license, first select the company on the top of the Assigned Namessection. 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 theleft arrow icon to assign it to the selected license type. To retract a user, select its line from theAssignments list and click on the right arrow icon.

If different companies have different users, they all have to be configured in the same Produmexlicense server. You have to get the list of users for each connection string, and assign them alltogether into a single list of assigned users.

The sequence of the assigned users has no impact on license allocation.

Last update:2018/03/1212:56



The number of the available licenses defines the number of users that can use the Produmex Add-Onconcurrently. If there are more users than the number of licenses, the principle of “first come, firstserved” will be applied.

Each time a user starts the add-on, the system will check whether the user is an assigned user andwhether there is a free license that can be allocated for the user:

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 usertries to open a function that requires a license, an error message will be displayed.

Please note: One user can only be assigned once, even though multiple databases contain the sameuser. If a given user is logged in one database, the user can only log in another database if there is afree license. If a user is logged in two databases, he/she uses two licenses.

3.2.2.4.2. Produmex WMS Terminal (Device Client)

The license that is needed to run flows on the device (typically a scanner or a touchscreen). On thelicense configuration this is called ‘DeviceUser’.

The terminal licenses are unassigned licenses. If the license has to be assigned, it can be assigned toevery thin client defined in the Organizational Structure of the company. The number of the assignedclients is not limited.



Device clients have concurrent licensing meaning that licenses do not have to be assigned to acertain client, but instead the system will allow as many concurrent connections as the total numberof available licenses.

Each time logging in on a client, the system will check whether there is a free license slot that can beallocated for the client.

If there is a free license, the system will allocate it to the client.●

If there is no free license, an error message will be displayed.●

After the logout, the system will deallocate the license from the client.

3.2.2.4.3. Produmex 3PL Module

The license that is needed to use the 3PL invoicing functionality. On the license configuration this iscalled ‘Mod_3PL’.

This license is an ‘Unassigned’ license. There is 99999 licenses available, which means that when theMod_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 EDI messages. On the licenseconfiguration this is called ‘Mod_EDI’.

This license is an ‘Unassigned’ license. There is 99999 licenses available, which means that when theMod_EDI license is active, every add-on user has access to the EDI functionality.

3.2.3. Produmex SB1 Notification listener

3.2.3.1. Configuring the database

In order to activate the SB1 Notification listener, you need to enable the service broker; first you clickthe config button of the Produmex SB1 Notification Listener. This will show the following screen:

Click the “Run in console Mode” button of the configuration database option. This will show thefollowing console.

http://wiki.produmex.name/doku.php?id=support:supportguidev2:licenseissues#no_fat_client_license_available

http://wiki.produmex.name/doku.php?id=implementation:wms:3plprocess

http://wiki.produmex.name/doku.php?id=implementation:wms:edi_module

Last update:2018/03/1212:56



Do NOT perform this action on an environment with active users.

Simply hit ENTER to finish the database configuration.

3.2.3.2. Listing the actions

You need to list any actions where that the Produmex SB1 Notificationlistener needs to listen to.To do this click the “Run in console mode” of the list actions option.

The tool will add the actions to the config-file located in the installation folder of the Produmex SB1Notificationlistener.

Afterwards press ENTER to exit.



3.3. Adaptation of stored procedures

3.3.1. Enable the standard PMX stored procedure

3.3.1.1. With Microsoft SQL Server

After the configuration is done you need to enable the (custom) stored procedures in the storedprocedure of SAP named “SBO_TransactionNotification”.

When applying the Produmex Add-on the first time to a database you will also need to adapt thestored procedure “SBO_SP_TransactionNotification”

To do this open “SQL Server Management Studio” and connect to your database server.●

Expand the “Databases” folder and locate the database to which you want to apply the Produmex●

Add-on.Open this database directory and open the “Programmability\Stored Procedures” subdirectory.●

Locate the “dbo.PMX_SP_TransactionNotification” stored procedure, right-click it and select●

“Modify”.

Locate the “Produmex Logex Addon Code” at the end of this stored procedure (see illustration below)

Last update:2018/03/1212:56



Copy the “Produmex Logex Addon Code”.This code should now be pasted in the “SBO_SP_TransactionNotification” stored procedure, modifythis stored procedure in the same way you modified the PMX_SP_TransactionNotification.

Paste the “Produmex Logex Addon Code” at the end of it. With a new installation you will see amarked area like “– ADD YOUR CODE HERE”.



Afterwards you need to uncomment the SP by clicking the “uncomment” button in SQL managementstudio. The end result should look like this:

After these modifications. Execute the SBO_SP_TransactionNotification stored procedure.

3.3.1.2. With SAP HANA

After the configuration is done you need to enable the (custom) stored procedures in the storedprocedure of SAP named “SBO_TRANSACTIONNOTIFICATION”.

Last update:2018/03/1212:56



When applying the Produmex Add-on the first time to a database you will also need to adapt thestored procedure “SBO_SP_TRANSACTIONNOTIFICATION”

To do this open “SAP HANA Studio” and connect to your SAP HANA server.●

Expand the “Catalog” folder and locate the schema to which you want to apply the Produmex Add-●

on.Right-click on this schema and select “SQL Console” to open a new SQL console●

Keep this SQL console open during the whole process.

Then locate the “SBO_SP_TRANSACTIONNOTIFICATION” stored procedure:

Expand the schema directory and open the “Procedures” subdirectory.●

Locate the “SBO_SP_TRANSACTIONNOTIFICATION” stored procedure, right-click it and select “Open●

Definition”.

Open its content by opening the “Create statement” tab:



Copy the content into the SQL console.

Next, locate the “PMX_SP_TransactionNotification” stored procedure, right-click it and select “OpenDefinition”.

Open its content by opening the “Create statement” tab, and locate the “Produmex Logex AddonCode” at the end of this stored procedure (see illustration below)

Last update:2018/03/1212:56



Copy the “Produmex Logex Addon Code”.●

This code should now be pasted into the SQL console, where you have already pasted the content of●

the “SBO_SP_TRANSACTIONNOTIFICATION” stored procedure. Paste the “Produmex Logex AddonCode” at the end of it. With a new installation you will see a marked area like “– ADD YOUR CODEHERE”.You also need to uncomment the copied code by removing the leading '–' from each line.●

Finally, add the following line on the top of your SQL console:●

DROP PROCEDURE SBO_SP_TransactionNotification;

The SQL console should look like this



Finally, execute the code in your SQL console to modify the SBO_SP_TRANSACTIONNOTIFICATIONprocedure.

3.3.2. Enable a custom stored procedure

When installing a custom build, it is possible a custom stored procedure is added to the database andneeds to be modified in the same way as the standard stored procedure.

Produmex custom development usually only requires a modification of thePMX_SP_transactionNotification stored procedure. It is possible other kind of SAP stored need to

Last update:2018/03/1212:56



be modified, although unlikely.If this is the case, the stored procedures will be added on the company database in the sameway a custom TransactionNotification stored procedure is added.If you are unsure if such a modification is required, please contact your designated supportaddress (eg: [email protected] ) and one of our helpdeskadministrator will contact you as soon as possible.

First you need to modify the custom stored procedure. In this example:PMX_SP_OECTransactionNotification.

Copy the commented text and modify the PMX_SP_TransactionNotification again.Add the text and uncomment it.



The end result should look something like this:

After these modifications. Execute the PMX_SP_TransactionNotification stored procedure.

Last update:2018/03/1212:56



3.3.3. Enable the Notification Listener stored procedure

After the Notification Listener configuration is done you need to enable the stored procedures in thestored procedure of SAP named “PMX_TransactionNotification”.

This step is only necessary if you intend to use the SB1 Notification Listener.

To do this open “SQL Server Management Studio” and connect to your database server.●

Expand the “Databases” folder and locate the PMX database (not the Company database) to●

which you want to apply the Produmex Add-on.Open this database directory and open the “Programmability\Stored Procedures” subdirectory.●

Locate the “dbo.PMX_SP_TransactionNotificationQueue” stored procedure, right-click it and select●

“Modify”.

Locate the “Produmex SboNotification Queue Code” at the end of this stored procedure (seeillustration below)



Copy the “Produmex SboNotification Queue Code”.This code should now be pasted in the “PMX_SP_TransactionNotification” stored procedure, in theCompany database. Modify this stored procedure in the same way you modified thePMX_SP_TransactionNotificationQueue

Paste the “Produmex SboNotification Queue Code” at the end of it, right after the code you havecopied for the Produmex Addon stored procedure (see “Enable the standard PMX stored procedure”).

Last update:2018/03/1212:56



Afterwards you need to uncomment the SP by clicking the “uncomment” button in SQL managementstudio.The end result should look like this:

After these modifications. Execute the PMX_SP_TransactionNotification stored procedure.

3.4. Registering the Produmex add-on



For our next step we need to register the Produmex add-on component in Sap Business One.

Make sure you run SAP Business One Client as administrator.

3.4.1. Install the add-on

3.4.1.1. On Premise

3.4.1.1.1. Install Add-On loader

In SAP Business One open the Add-On Administration window from Administration > Add-Ons. Click onthe ‘Register Add-On’ button. On the opening Add-on Registration form browse the add-on loaderinstallation .ard file after clicking on the ‘…’ button. The installation file is located in the installationzip folder \<SBO Version>\AddOnLoader. Selecting this file also opens the associated add-oninstallation package. Check the ‘Install as part of Registration’ checkbox and click on ‘OK’.

On the opening add-on installer select the installation folder, then press ‘Next’. After the installation isfinished, SAP Business One needs to be closed and restarted.

Last update:2018/03/1212:56



3.4.1.1.2. Set preferences

Start SAP Business One and navigate to Administration > Add-Ons > Add-On Administration. On the‘Company Preferences’ tab select the Produmex Add-On Loader. Tick the ‘Active’ checkbox and setthe Default Group.

On the ‘User Preferences’ tab select the user ‘manager’ and verify that for the Produmex Add-OnLoader the Preferences is set to the wished value.

3.4.1.2. In SAP cloud

3.4.1.2.1. Install the Add-On Loader on the Could Control Center



Create a Produmex sub folder within the folder you defined as the Extension Repository Path in CloudControl Center. Upload the zip folder of the lightweight installer to this Produmex folder. Do not unzipthe file.

The zip folder is named:Produmex_WMS_<versionnumber>.<SBOversion>_AddOnLoader_lightweight.zip.

It can be found in the installation zip folder of Produmex WMS:Produmex_WMS_<versionnumber>.<SBOversion>\<SBOversion>\AddOnLoader.

Regardless of the environment displayed in the name of the Produmex WMS installation folder,the lightweight installer zip contains both the x32 bit and the x64 bit installation files.

On the Could Control Center, navigate to Landscape Management > Extensions.

Check whether the installation file is listed on the Extensions grid then press the ‘Synchronize All’button to install the Produmex Add-On Loader. Confirm that you would like to synchronize allextensions.

If the installation is successful, on the opening Synchronization Report the status on the line of theProdumex Add-On Loader is successful. The installation zip is automatically moved to the ProdumexShared Repository folder.

Last update:2018/03/1212:56



3.4.1.2.2. Deploy the Add-On Loader to the Service Unit

When upgrading the add-on to a new version, make sure that the add-on is not running on anypresentation server. If there is a running add-on, the upgrade will fail.

Next deploy the add-on loader on every service unit where you would like to use it.

Navigate to Landscape Management > Service Units. On the Service Units grid select the targetservice unit.

On the Service Unit Details grid go to the Extensions tab and click on the Deploy button. Follow thesteps of the Extension Deployment Wizard. Select the Produmex Add-On Loader at the SelectExtensions step then finish the deployment.



3.4.1.2.3. Assign the add-on loader to the tenant(s)

Finally assign the Produmex Add-On Loader to the tenant(s) where you would like to use it.

This step is not required in the case of a version upgrade.

Go to Customer Management > Tenants. Select the tenant on the Tenants grid. On the Tenant Detailsgrid navigate to the Extensions tab, then click on the ‘Assign’ button. Follow the steps of theExtension Assignment Wizard. In the Select Extensions step select the Produmex Add-On Loader, thenfinish the assignment.

Last update:2018/03/1212:56



3.4.2. Update database

This step is not required in the case of a version upgrade.

In SAP Business One navigate to Administration > Add-Ons >Add-On Manager > ‘Installed Add-Ons’tab. If the Produmex Add-On Loader is not running, select it then click on ‘Start’.

On the opening screen click on the ‘Update database’ button to perform the needed databasechanges. If the database is already updated, ‘Database up-to-date’ checkbox is checked and this stepcan be skipped.

Then click on the ‘Set DB credentials’ button. On the opening form enter the DB credentials. After thecredentials are set, click on the ‘Exit Add-On’ button to download the files needed for the add-on.



3.5. Configuration for clients

Organizational structure

Make sure the IP address or host name of the server where the PMX License Server is running is filledin, add-on clients will require this to be able to connect.

Last update:2018/03/1212:56



You can do this initially on the SBO license server itself because the add-on will try to connect locallyif this field is empty.

If it is not possible to run the add-on on the machine running the PMX License Server, you will have toenter this information in the database, after creating the company element. Table “PMX_OSCO”, field“SboLicenseServerAddress”: only enter the IP address or host name, no port or other information isallowed.

4. Performing a version update

4.1. Uninstalling and installing the components

Installing a new version of Produmex suite over an older version is similar to installing a completelynew version. This chapter will explain every step that needs to be taken to perform a version update.Seeing some steps are equal to the steps of a completely new installation, this chapter will not go intodetail on these steps. For more details, please refer to the instructions described in the previouschapters.

First, make sure no one is logged in the SAP live environment, neither SAP users nor Device-clients. To verify this, check the Task manager and disconnect every user that still has a connectionopen to the server.

Device-clients like touchscreen-terminals and scanners keep most of their data in cache, such ascompany settings and any installation files. When these devices boot, they will connect to the serverand retrieve the new scripts and other installation files.

As a best practice, copy the configuration file (ProdumexInstallConfig.xml) of your previousinstallation in the ProdumexSuiteInstaller directory of your new version. In this way you will not haveto specify your SAP Business One databases manually.

Second, we need to remove the old components. To do this, start the Produmex Suite installer as anadministrator.

In order to proceed with the upgrade, you have to accept the End User Licence Agreement.



Then, click the uninstall button of each component to remove the component.

Note: It is not necessary to remove the “Produmex Licensing Server” for the installation of a newversion of the Produmex Add-on. In case it is not removed, the “Produmex Licensing Module” will nothave to be re-installed during the installation process. If you do need to reinstall the ProdumexLicense Server, make sure you back up the PmxLicenseData.xml file from the install directory so youcan use this after the installation.

Afterwards, you need to install every component. Now you need to run the UpdateDatabase tool byclicking the config button of the Produmex Tools component.

4.2. Configuration of the components

Running the UpdateDatabase tool is similar as installing a new version. Only the steps taken aresomewhat different:

Last update:2018/03/1212:56



Here the UpdateDatabase tool will look for the version installed and add every database modificationit needs. Just like in previous steps taken, we will see custom adjustment executed if applicable.

Besides this, you need to update the localizations and upload the addon-files to the database. Do notforget to browse for the custom project build if needed.



Afterwards, click upload.

Next you need configure the notification listener. Return to the system tab of the Produmex Suiteinstaller and click the config button of that component.

Make sure the service broker is enabled by running the “Configure database” option in Console mode.If the service broker is enabled you will see the following message:

Next you need to list the actions in the same manner as performing a new installation., run the “ListActions” option in console mode and when the tool is done, press ENTER.

Next you need to adjust the standard SBO_SP_TransactionNotification with the T-SQL code from the“PMX_SP_TransactionNotification” stored procedure as descripted in point 3.3. , the same goes for anycustom stored procedures if any are included in the custom version.

Afterwards you can start SAP Business One and the addon-files will be automatically loaded. Makesure the company settings on your organizational structure settings are correct.

Last update:2018/03/1212:56



4.3. Install the new AddOnLoader

In general for an upgrade of Produmex it is not needed to install a new version of the add-onloader. But in certain cases this is needed. On the compatibility matrix you can see which add-onloader version is required for the given add-on version. Please also refer to the release notes ofthe add-on version you would like to upgrade to.

On the following matrix you can see which add-on loader is required for which Produmex WMS add-onversion:

Add-on version Add-on loader version6.* 6

7.0 and up 7

It is possible to have multiple add-on loader versions installed on one server.

For more information about how to install the Add-on Loader please see: 3.4. Registering theProdumex add-on

5. Check the link between the SAP database and the PMX database

After installing PMX, you'll have an organizational structure. When you made this company with arestore of another database, the link between the SAP and the PMX database will be wrong.

You can check this with following query; this query should be executed on the SAP database. youhave to have a link to the correct PMX database;

When you did a restore of another existing database, you'll also have to run the following storedprocedure on the PMX database. You'll have to give the SAP database as a parameter.

http://wiki.produmex.name/doku.php?id=implementation:releasenotes:wms

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Acompleteinstallguide&media=implementation:27-01-2016_17-31-45.png



6. Adding a new database to an existing installation

To modify the existing configuration or to add a new database, follow these steps:

1. Add new connection

Go to the General tab of Produmex Suite Installer.

To add a new database, click on the green + button. Set the connection details as described in:●

3.1.1. General tabTo modify the connection of an already set database, change the configurations.●

It is recommended to test the SBO and the direct connection before continuing by clicking on the‘Test’ buttons.

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Acompleteinstallguide&media=implementation:27-01-2016_17-39-27.png

Last update:2018/03/1212:56



2. Go the tab of the server

Go to the tab of the server you would like to connect the database.

3. Update connection string

Press the ’Update connection string’ button. The connection strings assigned to the selectedenvironment will be added to every configuration file that belongs to that environment.

The connection strings will be added to the following configuration files:

Produmex Tools configuration●

Produmex License Server Configuration●

Produmex ScaleComm Configuration●

Produmex Fat Client Configuration●



Please note: Already added connection strings will not be removed from the configuration files.

4. Run database upgrade

Run the database upgrade on the new database.

On the tab of the server select the ‘Produmex Tools’ component and click on the ‘Config’ button. Onthe opening Produmex Tools form select the new database and click on the ‘Run’ button.

For more information please see: 3.2.1. Produmex tools configuration

5. Adjust stored procedures

For more information about enabling the stored procedures please see: Adaptation of storedprocedures

It’s important to check if the references between the company database/schema and the Produmexdatabase/schema are set correctly and are pointing to the right database.

Check the following stored procedures:

SBO_SP_TransactionNotification/SBO_SP_TRANSACTIONNOTIFICATION●

PMX_SP_TransactionNotification/PMX_SP_TRANSACTIONNOTIFICATION●

additional stored procedures if the customization requires their modification●

If you are using SAP HANA, also check the references in the following stored procedures:

PMX_SP_TRANSACTIONNOTIFICATIONCHECKS●

PMX_SP_TRANSACTIONNOTIFICATIONSTOCK●

Last update:2018/03/1212:56



6. Assign Add-on Loader

Make sure that the Add-On Loader is assigned to the new company database.

Setup Mobile Devices

Windows CE

1. Setup the Wi-Fi connection

Press the ‘Connections’ button → Select the ‘Find WLANs’ option → Select a network and press it →Press ‘Connect’.

Adjust the profile settings in the ‘Profile Entry’ window. After pressing on the ‘Finish’ button, theprofile will be active.



It is recommended to set the IP address to Manual Fixed IP instead of DHCP. Make sure that thesuggested IP address is not in use. Another solution would be to leave the PDA in DHCP, and set theFixed IP as a setting in the router’s DHCP lease table.

To set the correct country open the ‘Options’ window. Select the ‘Regulatory’ option then select thecountry. Make sure that the ‘Enable 802.11d’ option is not checked.

Save the ‘Profiles and Options’ to the fixed memory of the scanner. In the ‘Options’ window select‘Export’ from the dropdown menu. Press the ‘Export All Profiles’ button then press ‘Save’.

2. Setup Remote Desktop Connection

Open the ‘Remote Desktop Connection’ window. In the ‘General’ tab, fill in the ‘User name’ and‘Password’ fields.In the ‘Loc Res.’ tab, select the keyboard setting ‘On the local computer’ from the dropdown menu.In the ‘Exp.’ tab, disable ‘Themes’.

Last update:2018/03/1212:56



Then go back to the ‘General’ tab and save the settings to the fixed memory.

How to set up auto startWe recommend to set up the automatic start of Produmex WMS for the Windows RDP user.Open Computer Management and navigate to the Users folder via: System Tools > Local Usersand Groups. Select the device form the list and choose the Properties option from the right-clickmenu.On the opening Properties screen go to the Environment tab. On the Starting program sectionenable the ‘Start the following program at logon’ checkbox and add the file with its path to the‘Program file name’ field.When configuring auto start this way, the RDP session is automatically logged of after theProdumex WMS application is closed.

Please note: The exact steps might differ from the steps described, depending on operationsystem used.



3. Setup config for standard DataWedge to send AIM ID’s

1. Press the DataWedge icon2. Select 'Advanced Configuration'3. Select 'Profiles'4. Select 'Profile0'5. Select 'Input'

6. Select 'Scanner'7. Select the scanner type8. Select 'Scan params'9. Select 'CodeID'

Last update:2018/03/1212:56



10. Set to 'Aim'. Press '0.Back' to go out of this screen.11. Come back to this screen and check whether the CodeID is set to Aim. If yes, select 'Home'.12. Select 'Exit'.13. Click 'OK' to confirm exit.

4. Setup for power usage (Recommended)

4.1. Automatic sleep mode

Go to control panel → Power → Advanced tab → 'On Battery power' setting

To set an interval, choose an interval (mx 5 min) from the dropdown list.

To turn off the automatic sleep mode, uncheck the box. The device will never go into sleep mode.

4.2. Backlight



It is possible to set up so that the back light is cut after a certain amount of time or not at all. You canchoose this yourself, depending on the intensity of your battery usage. We recommend to set thebacklight with a timeout, because this is the main battery consumer.

5.Change Intercharacter delay setting

When the gun is sending chars too quickly through the RDP, it might cause incorrect character displayon the scanner.

To avoid this issue, setup interchar delay on DataWedge. Go to the ‘Advanced Configuration’ menu.

Follow these steps: Profiles > Profile0 > Output > KeyStroke > InterCharacter Delay

Last update:2018/03/1212:56



Specify “10” into the text box, and press Save. Go back until you come back to the main screen andthen 0.Exit.

6. How to access the memory slider bar

Select Start > Settings > Control Panel.1.On the Control Panel scroll down until you see the 'System' icon. Double click on the icon. The2.System Properties screen will open.Go to the 'Memory' tab. A slider bar will show on the screen with the following verbiage: Move the3.slider to the left for more memory to run programs. Move it to the right for more storage space.Only unused RAM (dark portion of the slider bar) can be adjusted.



6. Screenshot tool for Windows CE

Before connecting the device, make sure you have an USB dongle for the connection. Also make surethat the Windows Mobile Device Center is installed on your PC. If not, download it from the followinglink: http://www.microsoft.com/en-US/download/details.aspx?id=14

After connecting the device to the PC, the Windows Mobile Device Center will start automatically.Select the ‘Connect without setting up your device’. On the next screen, select ‘Browse the contentsof your device’ from ‘File Management’. The menu of the device will open in a new window.

Download the screenshot tool from the Produmex FTP:ftp://public:[email protected]/Hardware/ScreenshotTool/ScreenshotTool.zip

http://www.microsoft.com/en-US/download/details.aspx?id=14

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Acompleteinstallguide&media=implementation:install:scanner:wmdc.png

ftp://public:[email protected]/Hardware/ScreenshotTool/ScreenshotTool.zip

Last update:2018/03/1212:56



Extract the .zip file. Copy the terminal.exe and paste it onto the device through the Windows MobileDevice Center. It is recommended to paste it into the ‘My Documents’ folder.

On your PC, execute the PC.exe file from the Screenshot Tool folder. This will open a window wherethe scanner screen will be displayed after the connection setup.

On the device, execute the terminal.exe. Press ‘Ok’ on the ‘About CERDisp’ window. On the ‘RemoteDisplay Control’ window, press ‘Connect’. ON the next window add the hostname to the ‘Hostname’field then press ‘Ok’.

Now the screenshot tool is running on your PC and the device can be accessed through the previouslyopened window.

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Acompleteinstallguide&media=implementation:install:scanner:menu_sst.png

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Acompleteinstallguide&media=implementation:install:scanner:termial.png

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Acompleteinstallguide&media=implementation:install:scanner:device_screenshottool.png

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Acompleteinstallguide&media=implementation:install:scanner:device_screenshottool.png



Android

1. Setup Wi-Fi connection

Set up the Wi-Fi connection on the device from Android settings.

2. Setup Remote Desktop Connection

Install Remote Desktop on your device. If the device has access to Google Play, install the MicrosoftRemote Desktop app from Google Play, otherwise download the Microsoft Remote Desktop .apk fileand install it manually on the device.

Open the Remote Desktop app and set up your connection.

Press the ‘+’ icon and select ’Desktop’ to add a new connection. Press ’ADD MANUALLY’.

Last update:2018/03/1212:56



Enter the IP address or the host name as the PC name. Add the user account by entering the username and password.

Press ’Show additional options’ and select ’Customize display resolution’ from the expanded menu.

The handheld fat client is designed to work on a 240×320 resolution. If the resolution of the device isgreater than 240×320, custom display settings are needed.

Press ’Show additional options’ and select ’Customize display resolution’ from the expanded menu.

Enable the custom display resolution and add a custom resolution and scaling. The optimal resolution



and scaling depends on the device. Finding the optimal resolution and scaling might require sometrial and error.

Please note: Scaling is available beginning from Windows 8.1 and Windows Server 2012 R2.

Go back to the Add desktop menu and press ‘SAVE’ to save your configurations.

Open remote desktop and press the icon. Set the mouse mode to ’Touch’. Press the ‘Touch’ iconon the right sidebar. The mouse mode is ‘Touch’ if the ‘Mouse Pointer’ icon is displayed.

http://wiki.produmex.name/lib/exe/detail.php?id=implementation%3Awms%3Acompleteinstallguide&media=implementation:wms:android:icon.png

Last update:2018/03/1212:56



2.1. Display settings

We recommend to set the orientation as ‘Portrait’. This can be done in the following ways:

2.1.1. Remote desktop

Set the orientation of the Remote Desktop app to Portrait. Open the app settings and select the‘Display’ menu. Set the Orientation to ‘Lock to portrait’.

2.2.2. Device

Set the orientation of the device to Portrait or disable Auto-Rotate on the device.

3. Configure automatic start

We recommend to configure Produmex WMS to start automatically on connection. This can be done inthe following ways:

3.1. Startup folder shortcut

Create a shortcut in the Startup folder. Please note: The location of the Startup folder depends on theoperating system version. On the ‘Shortcut’ tab of Properties add the access path and the startupconfigurations of the fat client to the Target field.

http://wiki.produmex.name/doku.php?id=implementation:wms:fatclientconfig



3.2. Batch file

Create a batch file containing the access path and the startup configurations of the fat client.

Example:

"C:\Program Files (x86)\Produmex\Produmex FatClient\Produmex.Sbo.Logex.Execute.FatClient.exe" /f+ /s- /w:240 /h:320/a:Produmex.Foundation.SlimScreen.WinGui.PocketSize /i:SCAN_2

Create a scheduled task for the batch file that is triggered at log on.

http://wiki.produmex.name/doku.php?id=implementation:wms:fatclientconfig

Last update:2018/03/1212:56



4. Scanning configurations

On most systems scanning settings are assigned to profiles. By default the settings of the defaultprofile are applied, but it is possible to create specific profiles for applications. Profile handling maydiffer based on the device.

Set the following scanning configurations for the profile you would like to use:

Set the code type to AIM ID.1.Set to send ENTER after the barcode data2.

Configuration steps may differ based on the device and the Android version. This documentationincludes the configuration steps for the following:

Honeywell Dolphin 75e – Android 6.0.1.●

Zebra MC9200 – Android 4.4.4.●

4.1. Example 1: Honeywell Dolphin 75e – Android 6.0.1

Open Android Settings. From the Honeywell settings select ‘Scanning’.



Press ‘Internal Scanner’ and select the profile you would like to use from the list of profiles.

Press ‘Data Processing Settings’. In the Data Processing Settings menu set the Symbology Prefix to‘AIM’. To send the ENTER key after the barcode data, add ‘\r’ as the Suffix.

Last update:2018/03/1212:56



4.2. Example 2: Zebra MC9200 - Android 4.4.4

Open the DataWedge app. Select the profile you would like to use from the list of profiles.

From the BARCODE INPUT plugin select ‘Scan params’. Press ‘Code Id Type’ and set the code ID typeto AIM.



From the KEYSTROKE OUTPUT plugin open ‘Basic data formatting’ and enable the ‘Send ENTER key’setting.

5. Setup for power usage

We recommend to adjust the following settings in order to save on power usage:

5.1. Sleep mode

Adjust the sleep mode settings.

5.2. Backlight

Adjust the backlight settings. The configuration steps depend on the device.

Last update:2018/03/1212:56



From:http://wiki.produmex.name/ -

Permanent link:http://wiki.produmex.name/doku.php?id=implementation:wms:completeinstallguide

Last update: 2018/03/12 12:56

http://wiki.produmex.name/

http://wiki.produmex.name/doku.php?id=implementation:wms:completeinstallguide