<<

Contents

Search

>>

 

The Ebus-2T-Server

 

The Ebus-2T-Server is needed with programs that were created in the 2-Tier model (2-Tier-Programme, 2-Tier-Applets).

 

 

The 2-Tier model

 

The 2-Tier Model is a Client-Server-Model, where the Client is only responsible for the screen display and the Server is only responsible for program processing. Client and Server programs run on different computers in the network or on the Internet. RDT connections are also possible.

 

With the generation of a Java program two programs are created:

 

1. The Client program <Programname>_Client.java or <Programname>_Applet.java
2. The Server program <Programname>_2T.java or <Programname>_2T_Applet.java

 

The Server programs <Programname>_2T.java and <Programname>_2T_Applet.java require the Ebus-2T-Server for execution. The Ebus-2T-Server loads the program and executes it when the respective client logs in with the Ebus-2T-Server.

 

The 2-Tier model has the following advantages:

 

1.

All macros of all executed programs are executed centrally on one computer. If the Index Files are also on this computer, file data will not be transferred via the network since the Ebus-2T-Server takes on the data access for all clients. From the perspective of the Ebus-2T-Server the data are local. The Ebus-2T-Server can run on any computer of the network, it does not have to be a special server.

2.

The Client is an independent program, which is merely responsible for painting the screen. Therefore it communicates with the Server program. The Server program informs the Client about which windows shall be opened or closed and which fields shall be displayed. The Client conducts the painting of the masks, the Server only transfers the necessary data (e.g. the text for the button labels). Due to this technique only small quantities of data are transferred between Client and Server. This is also the reason why even with low data transmission rates a satisfactory processing speed is reached.

3.

Data protection: Only the Ebus-2T-Server has to access the Index File data, for all other computers in the network the access can be blocked.

4.

Various ways of connection: The Ebus-2T-Server can be called via the network, a RDT connection or via Internet.

 

 

Start of the Ebus-2T-Server

 

The Ebus_2T_Server is started by the following command:

 

run_Ebus_2T_Server  <Directory>  <Servername>[:<Port>]  [quiet]

 

<Directory> is the working directory of the Ebus_2T_Server.

 

<Servername> is the name or the IP address of the computer on which the Ebus_2T_Server is started.

 

quiet is optional. The Ebus_2T_Server runs without dialog windows.

 

<Port> specifies at what port the Ebus-2T-Server runs. If no <Port> is specified, the standard port 1099 will apply.

 

 

 

Button "Terminate Server": The Ebus-2T-Server is closed. If there are still programs connected with the Ebus-2T-Server the user will be asked whether the running programs shall be closed.

 

Button "Settings":

             

 

 

Open files exclusively: If this checkbox is set, all Index Files will be opened exclusively by the Ebus-2T-Server. Data are accessed considerably faster since no record locking is necessary. If this checkbox is not set, other programs in addition to the Ebus-2T-Server can also access the Index Files.

 

Client Timeout: Specifies after how many minutes a client connection will be disconnected if the client has not sent a sign of life for the specified period of time.

 

Server Restart Timeout: Sometimes memory problems occur under windows when the Ebus-2T-Server runs without interruption for a longer period of time. Windows does not always release the needed memory, which sooner or later results in the computer being busy swapping, the swapping and swapping in of main memory pages. The specification of a Server Restart Timeout (e.g. 30 minutes) has the following effects: If no user is logged on to the Ebus-2T-Server for 30 minutes, the Ebus-2T-Server will restart itself, provided that the command by which the Ebus-2T-Server was started is specified with complete path under Restart command, e.g. C:\Server\run_server.bat  D:\Daten  Server1

 

After a restart the Server will be restarted only if at least one user logged on once and the specified timeout after the last user log-out has run out.

 

 

Button "Language": The language can be spcified. Available are German and English.

 

 

Button "Password": You can specify a password that must be entered if the Ebus-2T-Server shall be closed. If a password is specified, the Ebus-2T-Server can not be closed if the right password is not entered. The password is only valid for the current program run. After a restart of the Ebus-2T-Server the password must be specified again.

 

 

Button "User": The programs that are currently connected with the Ebus-2T-Server are displayed. For every running program the following data are displayed:

Serial number   computer name   user name   program name

 

Button "Logfile": The log file contains a record of when the Ebus-2T-Server was started and closed. Additionally, all runtime errors are recorded.

 

Button "Logon Journal": The logon record keeps record of when the Ebus-2T-Server was started and closed and when the user logged on or off.

 

Button "Memory": The current assignment of memory space is displayed:

total memory shows the size of the memory space currently used by the Ebus-2T-Server.

free memory shows how much of the memory space is not being used by total memory.

max memory shows the maximum of memory space that the Ebus-2T-Server may use.

 

 

 

Start of the client programs

 

2T-Applets are started over a html file or a php file (see Applet).

 

2T-Client programs are started by the command procedure

 

run_<Programname>_client.bat  <Serveraddress> <Clientaddress>  (Windows)

 

or

 

 run_<Programname>_client.sh  <Serveraddress> <Clientaddress>  (Unix/Linux).

 

<Serveradresse> is the name or the IP address of the computer on which the Ebus-2T-Server runs.

 

<Clientadresse> is the name or the IP address of the Client computer. This parameter may be missing, normally it must only be specified if the Ebus-2T-Server is accessed via the Internet.

 

 

Automatic stopping of the Ebus-2T-Server

 

The Ebus-2T-Server periodically (all 20 seconds) checks whether the file ebus_server_stop.dat exists in the current directory of the Ebus-2T-Server. If the file exists and no users are connected the Ebus-2T-Server will be terminated.

 

If the first line of the file ebus_server_stop.dat contains the number 1, the Ebus-2T-Server will be be terminated even if there are users connected.

 

The file ebus_server_stop.dat can be used to stop the Ebus-2T-Server when it has been startet in quiet mode.

 

At the start of the Ebus-2T-Servers an existing file ebus_server_stop.dat is deleted.

 

 

Installing Ebus-2T-Server as a service under Windows

 

Ebus_2T_Server_Service.bat is installing the Ebus-2T-Server as a service under Windows:

 

Ebus_2T_Server_Service.bat <Directory>  <Servername>[:<Port>]

 
Attention: The command line window must have administrator rights.

 

The parameter --JvmMx=256 specifies the memory of the Ebus-2T-Server in megabytes.

 

After the call of Ebus_2T_Server_Service.bat a dialog is shown on which the service can be started:

 

 

The Ebus-2T-Server is started in quiet mode because a service has no graphical user interface. All informations are written to the following log files:

 

Name of  log file

content

Ebus_2T_Server.logon

Logon / Logoff informations

Ebus_2T_Server.log

Start-, Stop- and Error-Messages of the Ebus-2T-Server

jakarta_service_<Date>.log

Protocoll of starting and stopping the service

stdout_<Date>.log

Messages of the Ebus-2T-Server

 

The above dialog can be called by the following command:

 

prunmgr //ES//Ebus2TServer

 

The following command uninstalls the service:

 

prunsrv //DS//Ebus2TServer

 

Attention: prunsrv.exe has to be specified as a exception in the Windows Firewall (Allow a program or feature through Windows Firewall).

 

 

Installing a client programm as a service under Windows

 

start_client_service.bat is installing a client program as a service under Windows:

 

start_client_service.bat has to be called with the following parameters:

 

start_client_service <Client-Program-Name> <Client-Path> [<Serveraddress> [<Clientaddress>]]

 

<Client-Program-Name> is the name of the client program, e.g. Customer_Client

 

<Client-Path> is the directory, in which the client program <Client-Program-Name> shall be started as a service. This directors must contain the files policy.txt, prunmgr.exe and prunsrv.exe.

 

<Serveradresse> is the name or the IP address of the computer on which the Ebus-2T-Server runs.

 

<Clientadresse> is the name or the IP address of the client computer. This parameter may be missing, normally it must only be specified if the Ebus-2T-Server is accessed via the Internet.

 

The following command calls the dialog in order to start and to stop the service:

 

prunmgr //ES//<Client-Program-Name>

 

The following command uninstalls the service:

 

prunsrv //DS//<Client-Program-Name>

 

To install a java program as a service under Windows see Run of an Ebus program.