Administration Utility programs Distributed landscape - robinfeng/beashelp GitHub Wiki

εˆ†ε‘η¨‹εΊ

Configuration of Server management

Server management Introduction
Server Management Administration tab Protocol Planned activities tab Examples of activities E-Mail tab Extended tab Distributed server landscapes Troubleshooting

By using different types of servers and the possibility to run services simultaneously, it is possible to configure complex, distributed server landscapes. This chapter is about some scenarios.

Scenario 1: Demo area of Beas Mobile

This scenario is to configure a dedicated demo area next to the productive environment for beas Mobile. This demo area is placed on a separated database.

  1. Setup of beasService #Prod

clip0011

First step is to setup a productive environment to provide apps. For this create a new service in the Server Manager and activate Common Interface and HTML-Server. After changing select a type for the service (for example XAMPP). The important part is to select the correct directory for the connector and for the communication directory. It's suggested to use a structure like this:

clip0012

Tip 1: Make sure the selected directory already exist. You can install the needed files to the connector directory by clicking the icon next to the related field (Server Manager). If you have trouble to install the files, you can unzip them manually from the installed archive (common: C:\Program Files (x86)\beas software\beas\program\beasweb\beasweb.zip) to copy them to the target directory.

Tip 2: The directory for the connector should contain a folder beasweb. In Server Manager this directory should by the directory of communication.

Tip 3: If you want to use Tomcat you have to make sure, the communication directory (Server Manager) is the same as in index.jsp of the connector.

  1. Setup of beasService #Demo

clip0013

Follow the steps to create the productive services and modify the settings for the directories of communication and for the connector (a) like in the Screenshot. Additionally make sure the connection to the database is switched to the demo system (b).

  1. Die DI-API konfigurieren

You can modify the settings for the DI API on Tab Common. This setting is saved to the current database. If you want to modify this for the specific instance of the service, use the beas client to connect to the related database.

  1. Test your systems

Make sure your Apache or Tomcat is running. The system should be reachable with URL http://myserver/prod and http://myserver/demo.

Scenario 2: Load Balancing for BEAS Mobile

Current server systems are using multicore architectures and a high reserves of memory (RAM) . To allow beas-Services to use these resources in optimized way it is recommended to install multiple services for load balancing. Especially if it is needed to provide applications to a high amount of mobile devices, the installation of a multi-service architecture should be considered. It is possible to split the load for HTML-Services, to render the application interface, in multiple instances and give them separated URL endpoints to access.

  1. Setup the Common Interface Service

First the so called Common Interface Service is needed to process the business logic asynchronously. It is necessary to set the Asynchrone Processing on Tab Extended.

Server_CI

  1. Adding HTML-Services

Now, the preferred amount of service instances could be added. Important is to make sure, that any service uses it's own folder for the Connector and for communication.

clip0016

In this case the instances are accessible by the urls http://myserver/p01, http://myserver/p02, ... .

Server_HTML1 3. System test

Before testing make sure that any services to test are running. Additional check the status of the Apache or the Tomcat service.

Call the Websites: http://myserver/p01 http://myserver/p02 http://myserver/p03

For all URLs BEAS should be accessible.

  1. Service pool

After all services have been set up, you can assign single instances to a service pool. This pool makes sure, that all instances are loaded with the same number of sessions.

Note: in case of overload, a task is re-reouted to another service. For this case, it is necessary to keep the URL field always up-to-date.

clip0017

θΏ”ε›ž δΈ»ι‘΅