Internal HTTP server

Administration > Utility programs > beas Server management > Internal HTTP server

Top  Previous  Next
Expand/Collapse Toggles

Beas has a integrated complete HTTP Server

 

http_intern

 

This allows a simple installation and usage of WEB applications

Terminal 2.1, WebConfigurator and all internal services  are compatible only to internal HTTP Server

 

Example of use see WEB Server

 

Advantages:

- Fast, because no additional interfaces are required

- Simple to use

- Fully integrated

 

Without use of a Proxy server there are following limitations

- Only HTTP, no HTTPS

- Can only transmit the images one after another instead of parallel

 

In general, the use of the internal WEB server is recommended.

Without additional services this is completely sufficient services at internal use or for presentation.

 
But a Proxy-server is required if a public access is required or larger image file is transmitted. The setup for this is very simple.

 

Display of different possibilities

 

Only internal beas WEB Server

The client communicates directly with beas AddOn, because this provides the HTTP Server at the same time.
Because the interface can be renounced, following will change:
a) Setup and support of Apache HTTP Server are not required
b) Faster processing of Inquiries

But no HTTPS is available

Good for intranet solution or presentation

  http_intern

Apache as Proxi Server

The HTTPS protocol has to be used if an internet access is required. The apache HTTP server be used. This routes the HTTPS inquiries to Beas http and application server using HTTP
 

http_apache_proxi

 

 

 

hmtoggle_plus1Additional information for setup of the Apache Servers as Proxy Server

It is possible integrate this server with apache to achieve server the pages using https instead of the standard http.

In this way you'll get another additional benefit: SPEED and Multithread for all static content as images.

 

Edit your apache configuration and load the proxy module

Replace the yellow area with correct ip adress and port.

 

# Open http.conf and uncomment this line:

# LoadModule proxy_http_module modules/mod_proxy_http.so

 

 

Edit your apache virtualhosts's ssl configuration and set this settings (delete blue text):

DocumentRoot "c:/program files(x86)/beas software/beas/httpserver"   # <= this  is the root path for you ssl web server

   <Directory />

       AllowOverride none

       Require all granted                                               # <= be sure we allow serve content from this folder

   </Directory>

 

   ProxyPass "/beasweb/static" !                                   # <= exclude static content

   ProxyPassReverse "/beasweb/static" !

   ProxyPass /beasweb http://localhost:10002/beasweb   # <= set the right server:port

   ProxyPassReverse /beasweb http://localhost:10002/beasweb

 

# If your apache server has access to the folder where your BitmapPath is, then you can do an Alias to improve the speed even more

# but you need a copy from all pictures in the apache server folder

ProxyPass /BitmapPath http://localhost:10002/BitmapPath

 

ProxyPassReverse /BitmapPath http://localhost:10002/BitmapPath

 

<Location "/productConfigurator/exec">

  ProxyPass "http://localhost:10002/productConfigurator/exec"

  ProxyPassReverse "http://localhost:10002/productConfigurator/exec"

</Location>

#############################################################++

hmtoggle_plus1Start Beas with HTTP Server

Beas can be started directly as HTTP Server

For this in the directory c:/program files(x86)/beas software/beas

start beas with the parameter /httpserver=[port]

 

Example:

 

beas.exe /httpserer=8080 user=manager pwd=manager database=training

 

Beas can now be used normally. But the HTTP server runs in the background and beas can be addressed directly.

 


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