beas Server management

PATH: Administration > Utilities > Beas Manage Server.

A Beas service can be a web server, a service which executes planned activities or an asynchronous common server which executes transactions.

The web service can be activated more then once. Load balancing is supported.

A Beas service is the Beas application which is started as "service".

It is possible to simulate it

- for WEB Server: Tools > WebServer

- for all Services: Beas Manage Server - "Start Local Server" button.

A Web-Application which edits WEB queries (WEB sites, service queries etc.). Required to operate the Terminal App via browser.

Presentation See Beas WEB Server

This service offers all programs set up and enabled in Program groups administration.

Only the program group Terminal is installed and updated by default.

programgroups

A program group can be e.g. a WEB application as well as a WEB service. All the usual methods will be provided here by the beas Framework-like WEB-Application with finished Logon-screen (employees, customer etc.) as well as services like SOAP, REST with XML or JSON-format support.

Example: Program group "Terminal": Our mobile solution

Zebra_main_wdevice

Intern HTTP is used by default. This is a complete integrated WEB Service in beas. There is no need for an additional web server.

You can test all functions with Tools > WEB Server.

WEB_server_22

Every mondern browser can connect directly to the build in HTTP Server.

Compatibility mode

It is possible to use other HTTP Servers e.g. Apache, Tomcat, IIS. Beas provides relevant interfaces for this.
But all other variants are only compatible to WEB Application Version 1.0, not with any other WEB Services.

We do not recommend to use it.

See

Intern HTTP Server

Beas: Install Web Services

The WEB Applications are always administrated via Program group administration.
The program group Terminal is installed by default. See Terminal Apps.

With a common interface, activate asynchronous process working.

beas_common_Dashb

Window syste_common_dashboard.psr

Area of use:

- The WEB-Server service sends all Crystal Report

- SAP transactions to this service, via which this asynchronous can be worked off. This relieves the WEB server and reduces load peaks

- External services and third programs can be linked here e.g. to execute transactions

There are finished functions available.

A complete Beas script can be sent, as well. The script is then executed by this service.

See: Common_service

Time controlled activities can be executed here.

- Integration Hub: scan directories and read in files e.g. for machine connection, PDM connection etc.

- Perform calculation regularly

- Create statistics and send per mail

See: Server-Examples , planned activities

Beas_Manage_Server_2021_01

system_server_admin

All installed services on the current server / PC are in this list.

Field

Description

Status

Status of service (started, stopped, etc.)

Name

Displayed name of service

Type

Type of service (IIS, Tomcat, Apache)

Last Check

Time of last check

Start, Stop, Restart and Control-Center

Buttons to control the service, call up configuration of Tomcat or XAMPP.

Service settings are saved on the setup work station or server. These are usual Windows-Services.

The service logs on to the stored database; it does not necessarily have to be the current database.

If the service is not starting, proceed as follows:

1.	Try to re-start

2.	Uninstall service

3.	Re-start Server / PC (mandatory)

4.	Re-install service

For additional information See Troubleshooting on services.

Change settings of the selected service from the list.

Field

Description

Server

Displayed name of server

Services

Common Interface

Use this to connect external systems. Beas processes can be asynchronized, as well.

When activating this service, the following features are automatically moved to this service:

WEB APP printing

WEB APP all SAP transactions (asynchronous working)

Batch-calculation Price lists - Entries

Additionally, it can be used for communication between Beas and a third program.

Overload and deadlocks can be avoided by using asynchronous processing.

Clicking the icon opens the following window to set Max. Records:

beas_common_Dashb

Window syste_common_dashboard.psr

Clicking the icon below opens the "beas common service test" window for script editing:
interface_command :

Attention:

Start this service only once!

Planned activities

Execution of planned activities. The next field indicates the interval of query.
Clicking the icon opens the Planned activities window.

WEB Application Server

- For WebApp Terminal 1.0, 2.1 and WEB Product Configurator

- Activate all Rest Services and ODATA

Note:

This is a HTTP Server that does not support HTTPS Protocol. If you need HTTPS, you must use a "Router" between Client and Server, which translates the HTTPS to HTTP protocol.

If the user connects to the WEB Application, the current WEB Session has full access to Beas ServiceLayer.

The user has the possibility to manipulate the session and then receives full access to all Beas Service layer functions.

Attention: Do not use this for access from outside. This is ONLY an Intranet solution.

For higher security, you must use a middle layer, in which you can define the access rules.

Type

The following types are available:

Beas has an integrated WEB Server. This web server does not need any additional tools or interfaces.

It is entirely integrated and fast.

Limitations:

It works only with HTTP and not with HTTPS. If HTTPS is necessary, an Appache server can be used as a Proxi Server.

Certain services run ONLY with the internal HTTP Server, for example the WEB Product configurator or REST Services.

See internal HTTP Server

Alternative see Other HTTP Services (compatibility mode)

WEB Application V2.1

Configurator

BSL Service

Display the complete IP Address for the related Application

Icons:

Question Mark: More information

Arrow: Open this Application in default browser

Clipboard: Copy IP Address in Clipboard

Web Server Port

Every HTTP Service needs an own port. Standard is 80 or 8080. Define the Server Port for this HTTP Server Service

It is important to use a HTTP Port, which is not used by other services, otherwise the HTTP Service cannot be started.

In many cases Port 80 and 8080 are used from other HTTP services.

Use Tools > WEB Server to check which port is free.

If you need more then one WEB Service then you need for every service an another Port Number.

BSL Password

For using BSL Service (ODATA Service) outside the Terminal WEB Application, you need a password.
You can define additional Login Rule in Tab "Extended".

Database

All settings for login to SQL database.

Database

the database in use

Server
User
Password
Trusted connection

Connection information to the SQL Server.

Click on Button "Current Database" to connect to current connection information

It is possible to create service for another SQL Server. In this case, insert all connection information from the SQL Server.

Check SQL-Server

Note:

This checks the running services on the current machine.

Only working if the services and the SQL Server are running on the same machine and only one SQL server instance is activated.

Only compatible with MSSQL.

Debug to file

It is possible to activate the debug to file for every service. In the Protocol directory you can define the path for the log.

Notes: - If you activate this for more than one Service, use a different folder for each service.

- The log will grow to be a large file in a short time. Activate the debug log only if it is necessary and always remember to disable it.

- Web service is slow if debug log is active.

For more information see System Information.

Available from 2020.05.

Protocol directory

This is the folder where the protocol is stored - the log file is saved.

Select a directory to which both the service and the application have access.

It is best to choose a directory which was not created by Windows.

You can also select the directory in System information > Settings tab.

Project directory

Directory for customizations. Normally, the project directory is located at %allusers%.

In service mode, this directory is located under Windows\ with resulting access issues.

For this reason, the directory must be specified here. Beas generally adds the files to the correct directory.

The Service User need access to this project folder.

Buttons

Field	Description
Current data base	Name and patch of current database are read out and entered.
Development	This opens WEB Apps development window for Import/Export and Editing the Apps.
New	Creates a new server entry.
Delete	Deletes the selected server entry IMPORTANT After deletion the server needs to be restarted before a new service can be set up.
Start Server Local	Starts the selected server in local mode. This mode is used for debugging and development.
Protocol	This opens the protocol.
program groups	This opens the "Program groups: Administration" window.

Protocol contains the following information:

•	Start / Logon information from Services

•	Error messages

•	IP-address of current server

•	For Apache: monitored ports

•	For Apache: error log of Apache Servers

While starting process the service records all log information in the "Protocol Directory" folder.

This window reads the information from this file and inserts this in the Beas Protocol and displays the information in this area.

Note:

If the service does not have an active SQL connection, it uses the "Protocol Directory".

This only works if the Service has access to this folder.
It is important for every user to have access to this folder, especially the service user.

Installation notes, Service configuration

Note on licensing:

SAP B1: Per server one SAP Indirect license is required.

Beas: Depending on the used app the respective license needs to be purchased per parallel connection.

After the service was installed, in Windows–Service the settings need to be adapted:

- Windows - Service

- Set Startup-Type to "automatic (delayed)

service

If problems occur with the server connection or contacting the local printer, set to "logon" with account and name / password of the user who runs the services.

serverconnection2

IMPORTANT: set up a separate user, start Beas once with this user to set up the environment variables. If the password of this user is changed, the password needs to be changed here, as well .

If the service does not start:

•	Restart PC/Server

•	Check login: Windows Service / Logon - if "this account" was selected: is the password correct?

•	After an update: uninstall the service - restart PC - install service and check the entry

•	View Server administration - Protocol

•	In case of SQL-errors: Windows-Service: switch logon to "this account" – see Installation.

Work with WEB Services and installation (9/2019)

Webinar beas sever tools (8/2017)

Help URL: https://help.beascloud.com/beas202102/index.html?system_server_admin.htm

Beas Server management