BxLogistics installation part 1 - BxEngine

Can be downloaded from our partner portal https://partner.bxsoftware.no/
Demands login to the portal, if you don't have an account, you can contact us on support@bxsoftware.no and we will create a user account for you as long as you exist as a dealer of our solutions.

Download the "BxEngine for BxLogistics/BxSales/BxStockCount" file that can be found under Releases in Home.

License key for BxEngine

You can find the license key under Licenses. Search for a customer to find the licenses and press the license key button to copy the license.

Admin access on applications server

BxEngine is often installed on the same server as app server for the ERP solution, but can also be installed in other places, depending on which ERP system is being used.

i.ex:

• Visma Global: Needs access to SDK / API to Visma Global, therefore it is almost always installed on the Visma Global app server.

• Visma Business: Needs access to the EDI area for Visma Business, either on the same machine or via a UNC / network address. Access is also needed for VB installation catalogue if you are using VBS instead of EDI.

  • By using UNC path to EDI or VBS tracks, a service user must be added with access to the specific areas on the BxEngine service.
• SAP B1: If BxEngine is installed on a different server than the SAP server, you need to install SQL Server Native Tools 20xx and SAP DI API SDK as well.
• Visma.net: Only needs access to the BxEngine SQL database, integration setup is done with a user login/integration user in Visma.net, token generating. Can be installed wherever it is preferrable as long as there is an MS-SQL server available.
• Uni Økonomi Desktop: Must be installed on the same server as theUni import service for BX is installed, usually on the Uni Økonomi serveren.
    

Creating a SQL database and user

• BxEngine database - Here, you will give your database a name and click OK.
   
• BxEngine login - General - Make sure there's an SQL Server authentication, and turn off "Enforce password policy". If you don't turn it off, it will lead to passwords expiring, which will lead the business to a halt, or that you must log in again and create a new password first before you can move forward inside the BxEngine service setup. Default database is added to the BxEngine database created in the previous step.
  
  
  
  • User Mapping - Ownership to the BxEngine database
    • db_owner
    • default schema dbo
    • If it's set up towards Visma.net you only need db_owner on the BxEngine database - you can then skip the next step and move straight to "Installation".
    
  • Reading right for the ERP database
    • db_datareader
    • default schema i.ex. dbo (Visma Business/NET/SAP/Uni) or company name (Visma Global)
    • If it's set up towards Visma.net you only need db_owner in the BxEngine database
    • If it's to be integrated towards Uni Micro ERP, it's also necessary with db_datawriter access
    

Installation

Start the BxEngine.msi file that you downloaded earlier and follow the instructions, it is only Next -> Choose wanted installation catalogue -> Next -> Complete.

When the installation is complete, you can start the BxEngine Monitor via the icon that should now have appeared on the desktop. Be patient, on some servers/PC's it can take a second before the program actually boots up.

When the BxEngine Monitor appears, you will first encounter a setup box. It will ask for a license key and information about the BxEngine database.

• License key: Retrieved from main license in the partner portal -> licenses
• SQL Server: SQL Server\eventuell instans
• Database: BxEngine - Remember! It's important that it's set to the BxEngine database
• bruker: bxengine - the user you've just created
• passord: **********

It's important that the bxengine user has db_owner access on the BxEngine database, both during installation and operation, as the database structure is susceptible to change during upgrades.

• It's not the ERP database that is to be added here, only the database that BxEngine will create its own columns in.
• Do not use easily guessed passwords! It is recommended to use a generated password that will be used only for this user account.
• It is not possible to log in to the database using Windows Authentication - it must be an SQL user.

Initialising the database

When the database information is added, you can click Confirm.

From there, you will receive a question whether or not you are running the init script that created the necessary columns. On a brand new installation, you will always receive this question. When moved, the same question will appear, but for this you simply press No. But since this is a new installation, you will click Yes. Eventually you will receive a message that will inform you that the script is now running - click OK. And finally you will receive a message that  informs you that the license is validated - click OK on this one as well. If you do not receive the OK button on your license dialogue box, please check if the firewall is opened up for these ports/addresses

 

Service user startup and adjustment

Now that the database is ready, the BxEngine Monitor will display a status image and start up the Windows service. At this point you must restart the service and if needed, add another service user if BxEngine needs access to the network stations.

The next step is the setup in BxAdmin: BxLogistics installation part 2 - BxAdmin