Tomcat and Xampp Service

Administration > Utility programs > beas Server management > Tomcat and Xampp Service

 Top  Previous  Next
Expand/Collapse Toggles

Follow types available:

 

- XAMPP Apache PHP

- B1 Server Tomcat JSP

- Internet Information Service (ISS)

 

Attention: In future we will support only the internal HTTP Service.

The new WEB APPS are not compatible to other solutions.

 

For all three post-selections you need to indicate the accessible local HTML folder. A network folder is accepted. Files required for beas are automatically copied.

Information on different services

Type

Description

Internal HTTP Server

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

It is fully integrated and fast.

 

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

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

 

See internal HTTP Server

 

XAMPP Apache

XAMPP Apache needs to be installed in advance.

Download from:
https://www.apachefriends.org

 

Install to C:\XAMPP .

 

The service needs to be installed as well and started.

Not compatible to WEB APP Version 2 and WEB Configurator

 

B1 Server Tomcat JSP

Installed automatically by SAP B1 if Integration Solution Components have been installed.

 

The correct folder is proposed automatically. Changing / Modification of the folder is not allowed.

 

Note:

Beas required administration rights on the Tomcat folder. Beas might be launched with administrator rights.

 

Note: Not compatible to WEB APP Version 2 and WEB Configurator

Internet Information Service (ISS)

The PHP version is used.

Not compatible to WEB APP Version 2 and WEB Configurator.

external Server PHP

uses a selected external PHP Server

 

Note: Not compatible to WEB APP Version 2 and WEB Configurator.

 

 

If the HTML server is not located in the local network "external server PHP" can be selected. See also the separate manual: WEB Apps installation and troubleshooting

 

For Tomcat and XAMPP the following functions are available:

tool-verweis opens the control center

20_fenstereinstellungen cogwheel: opens the configuration file

 

 

The following, additional fields are available:

Internal Connector

Using an internal connector, Beas works based on the files. Only the folder to be monitored is to be specified here.  

Directory connector

This is the directory where the connector is stored. The connector consists of a bundle of files, as index.php, or *.jsp and some sub-directories for bitmaps. If XAMPP is used, the path is

c:\xampp\ htdocs\

Directory communication

Beas communicates via files with the connector. The directory is allocated automatically and should not be changed. Generally, it is the folder \beasweb\ within the connector folder.

External Connector

An external connector is used when the web server is located outside the local network, e.g. in a data center. This communication does not take place by means of files, but by the WEB protocol. Beas queries every second if there is a request on the web server.

 

For this purpose, the content of %program files%\beas software\beas\program\beasweb\beasweb.zip needs to be installed on the web server. The following files are not required: .htaccess, index.jsp

 

The connector requires a sub-directory "beasweb" with rights to read and write.

 

Beas communicates with connectorread.php and connectorwrite.php and requires global variables (must be enabled in PHP if necessary)

URL Connector

URL of Connectors

Connector Password

Password. Set up on opposite party in common.php

Performance Monitoring

If enabled, every activity usable for performance monitoring will be logged.

 

IMPORTANT:

Activate this option only for analysis, then deactivate again.

Use the arrow left to the field to call up. The average processing time is displayed in ms.

Service Pool

Various services can be managed in one "pool" by assignment to a service pool. If one service has to process more sessions than another at the moment of first access, the task is re-routed to another service of the pool.

 

Note: For the re-routing to be working correctly, the field Url always needs to be  up-to-date.

 

(See also Distributed Server landscape)
Help URL: https://help.beascloud.com/beas202204/index.html?tomcatandxampp.htm