Skip to main content

Web Server Installation

The Beas Web Client is served by the Beas Web Server, installed once on a central server. After it is installed and configured, every user in the organisation reaches the Web Client from a browser, with no further setup on their machine. Users who prefer the desktop application install that on their own machine; it connects to the same server.

This topic covers the server. The SAP Web Extensions — the part that adds Beas to SAP Business One's own screens — are installed by the same installer but are a separate step with their own settings; they are covered in SAP Web Client › Installation.

note

This topic is aimed at consultants and administrators carrying out the installation. End users do not need it.

Prerequisites​

  • A Windows server to host the Beas Web Server, reachable from the users' browsers.
  • The SAP Business One Service Layer installed and reachable, with its server name and port.
  • The database server (Microsoft SQL Server or SAP HANA), with credentials that can reach the Beas company database.
  • Two free ports on the server — see the port table below.
  • The Beas Server Installer.

Configuration​

Server installation steps​

  1. Launch the Beas Server Installer and choose the destination location for the files.
  2. Under Select Components, choose Web Server + SAP Web Extensions, then Next and Install.
  3. Configure the SAP Service Layer connection: enter its server name and port.
  4. Configure the database connection: choose the database type (MSSQL / HANA), then enter the database server name and its credentials.
  5. Set the HTTPS port for the Beas Web Client.
  6. Set the HTTP base port for the Beas Legacy API.
  7. Configure the SSL/TLS certificate for HTTPS, then Next and Install.
caution

Choosing Generate a self-signed certificate automatically lets you finish the installation, but browsers do not trust such a certificate. Users see a security warning, and the Beas buttons and tiles inside the SAP Web Client can fail without saying why, because the browser refuses the connection. For anything beyond a test system, install a certificate the users' browsers already trust.

When the server installation finishes, the installer opens the SAP Web Extensions setup. Continue with SAP Web Client › Installation.

Ports​

SettingDefaultChosen to avoid
SAP Service Layer50000— the port the Service Layer itself listens on
Beas Web Client (HTTPS)4040040000, used by the SAP Web solution
Beas Legacy API (HTTP base port)5040050000, used by the SAP Service Layer

Both defaults can be changed during installation. If you change the Web Client port, the users' address changes with it.

User workflow​

To confirm the server is working, from a browser on a user's machine:

  1. Open https://<server>:<https-port>.
  2. The Beas Web Client sign-in screen appears. See Introduction.
  3. Sign in and choose a company.

If the page does not load, the usual causes are the port not being open on the server firewall, or the certificate not being trusted by the browser. Note that the server has to be reachable from the users' browsers, not only from the SAP server — every Beas screen is opened by the browser directly.

note

The Beas Web Client address is written into the SAP Web Extensions when they are deployed. If the server name, the port or the scheme changes later, the extensions have to be deployed again — see SAP Web Client › Installation.

Limitations​

  • One installation serves one Beas Web Server address and one database platform.
  • The installer runs on Windows only.