Saltbox B1 On-Premises Technical Requirements


First published on: 02/27/2025/3:32 pm

 

 

The following Saltbox requirements apply only to on-premises implementations of SAP Business One.

 

Introduction

Vision33 has developed the Saltbox product to extend workflow and integration capabilities for SAP Business One (SAP B1).

 

This document explains the various environmental dependencies you must fulfill before setting up Saltbox in an on-premises SAP Business One environment.

 

The SQL and HANA installation sections refer to the type of SAP Business One Database installation you use.

 

You should only reference one of the sections, as applicable.

 

Requirements

SQL Installations ONLY

Terminology

  1. AppServer – B1WebAPI is installed on this server – for SQL installations only
  1. SAP B1 servers – SAP B1 server
  1. Database server –SQL database server
  1. Saltbox – This is an iPaaS (integration platform as a service) developed by Vision33

SAP B1 user licenses

  1. B1 indirect user license (required all the time to run B1WebAPI/Service Layer)

SQL installations: The SAP B1 user with a B1 indirect user license is required to set up B1WebAPI on AppServer.

 

This is a mandatory requirement and is needed for the project to move ahead.

 

Internal AppServer to SAP B1 Server Port/Firewall Requirements

Depending on the SAP B1 version, certain ports must be opened on SAP B1 servers to allow access from the AppServer.

 

Here is a list of ports that must be opened from AppServer to SAP B1 servers.

 

INBOUND firewall rules for Windows firewall of the SAP B1 server and database server.

 

If you have questions, contact your Vision33 consultant.

SAP Version

 

Earlier than V 9.2 PL05

30000/tcp

30010/tcp

V 9.2 PL05 and later

40000/tcp

 

 

SQL databases - MS SQL

1433/tcp

1434/tcp

1434/udp

 

External Ports Whitelisting/Port Forwarding

Saltbox IP whitelisting/port forwarding

To use the Saltbox (iPaaS) platform, you must open port 443/tcp to the AppServer that's hosting the B1WebAPI.

 

If 443/tcp isn't available, you can use 4033/tcp.

 

  • When opening the port, we require whitelisting the Saltbox server IP.
    • The IP you need to whitelist: 
      • Saltbox IP: 34.196.190.164
      • This IP address will need to be confirmed by the Saltbox Cloud team, as there could be regional variations.
      • Port: 443 or 4033/tcp
  • Port forwarding:
  • Open an INBOUND rule on the Windows firewall on the AppServer to allow access for the IP and port above.
  • Open an INBOUND port forward firewall rule on your corporate firewall to allow access for the IP and port above to the AppServer.

 

SSL Certificates and DNS Record Entry

Saltbox integration will require a trusted 3rd-party SSL certificate (self-signed are not allowed) to be installed on the AppServer and a DNS entry.

 

  1. AppServer

With the AppServer running on-premises, you need a Trusted SSL certificate to be applied/installed on the AppServer.

 

We recommend creating the following certificate name: B1webapi.yourcompanysdomainname.com

 

NOTE: If you need more than one instance of the B1WebAPI, we recommend the following to differentiate from other B1WebAPI installations: Saltbox.yourcompanysdomainname.com

 

*If you need help with this, please contact your Vision33 consultant.

 

  1. External DNS entry

An external DNS entry will be required for your certificate name.

 

This entry would point to the public IP of the firewall in which you are completing the whitelisting and port forwarding in the steps above listed in the section called “External Ports Whitelisting/Port Forwarding".

 

Application Server - Server Specifications (SQL Installations)

Hardware
  • 4-8 GB RAM or higher
  • 2GHz Dual Core processor or better
  • 100 GB hard drive or higher
  • 100 Mb network or better
Software
  • Recommended Windows Server Datacenter, Enterprise, Standard, or Web Edition 2022.
    • Ensure all stable security patches have been applied.
  • IIS including IIS6 Compatibility Modules
  • .Net Framework 4.6 (or higher)
  • SAP Business One 9.3 requires both 32-bit and 64-bit versions of:
    • B1 client
  • DI-API
  • SAP Business One 10 requires:
  • B1 client
  • DI-API
  • Legacy DI-API

 

Note: These specifications should address a typical customer's requirements. If a client is an LE or large customer, specs should be verified.

 

HANA Installations Only

Terminology

  1. Proxy server – Required for HANA installations only
  2. SAP B1 servers – SAP B1 server
  3. Database server – HANA or SQL database server
  4. Saltbox – This is an iPaaS (integration platform as a service) developed by Vision33

SAP B1 User licenses

  1. B1 indirect user license (required all the time to run B1WebAPI/Service Layer).

HANA installations: The SAP B1 user with a B1 indirect user license is required for the Service Layer to connect to SAP B1 with Saltbox.

 

This is a mandatory requirement and is needed for the project to move ahead.

 

 

External Ports Whitelisting/Port Forwarding

Set up proxy (Nginx) server
  • SSL Certificate with the chosen URL (We suggest saltbox.customerdomain.com)
  • Destinations (4300 & 50000 on the HANA server)
  • The client will need to provide the Service Layer URL
Set up Saltbox query extension
  • Set up V33SALTBOX user – with correct schema permissions
  • Vision33 can provide direction if required
  • Provide HANA Workbench URL
  • Creation of a HANA User, HANA role, and addition of the query extension will be completed by Vision33 IT

 

Application Server - Server Specifications

Hardware
  • Proxy server (HANA installations) – Depending on the type of Saltbox integration, you may need a B1WebAPI server instead of or in addition to a proxy server.
  • FTP server – Depending on the type of Saltbox integration, you could need an FTP server.
  • Small (1CPU, 2GB RAM) Linux host (Recommended)  Open SUSE

 

Vision33 is here to help with questions.

 

Please contact your Vision33 project manager if you need assistance. They'll arrange a call with the appropriate team members.

 

-