This is the last article of this series. Here I will introduce how to configure the server and it will upload the source code.
Directory structure:
aquait-appserver /
- application /
- db_connection_pool.config Configuring the connection pool to the base
- Configuring modules modules.config
- services.config service configuration
- messaging.config Configuring the messaging
- security.config Security Settings
- lib /
- Runtime-bin_2009r1.jar aquaitrt
- mail.jar mail Service
- log /
- Configuring logging logging.config
- server.config Server Configuration
- start.sh
- stop.sh
- start.cmd Scripts to start and stop the server
- start.sh
- stop.cmd
- stop.sh
logging.config
handlers = java.util.logging.ConsoleHandler, java.util.logging.FileHandler
java.util.logging.FileHandler.level = ALL
java.util.logging.FileHandler.pattern =. / log / server.% u.txt
java.util.logging.FileHandler.limit = 50000
java.util.logging.FileHandler.count = 1
java.util.logging.FileHandler.formatter = com.aquait.utils.logging.ServerFormatter
java.util.logging.ConsoleHandler.level = INFO
java.util.logging.ConsoleHandler.formatter = com.aquait.utils.logging.ServerFormatter
File that configures the logging. The server uses the standard Java SE API for logging. The default file defines two handlers. The first and second files generated logs on to the console. For more details, see http://java.sun.com/javase/6/docs/api/java/util/logging/package-summary.html.
server.config
# Server config
# Server listening port
#
port = 6666
# Worker pool size
#
workers.poolsize = 10
# Shutdown password
#
shutdown.password = _shut_down_now_server_
This file defines three server parameters. First, the TCP / IP on which the server listens for connections. Clients must be connected to this port. The second parameter defines the number of workers (threads) that deal with customer orders. And the third is the password to download the server. Lowered by the stop script that communicates the defined port and sends a special message. The server can only be downloaded from the same host where you are running.
db_connection_pool.config
# DBConnectionPoolModule configuration
#
# Examples:
# Url = jdbc: oracle: thin: @ <host>: <port>: <database>
# Driverclass = oracle.jdbc.driver.OracleDriver
#
enable = false
url = <url>
username = <user>
password = <pass>
driverclass = <driver_class>
autocommit = false
poolsize = 5
MaxPoolSize = 10
This file controls the parameters of the pool of connections to the database.
modules.config
# Modules to load
# Format:
# Module.name = <module_name>
# Module [<module_name>]. Class = <module_class>
#
This file delcaran modules that will be deployed on the server. Each module can have a varible amount of parameters.
messaging.config
# MessagingModule configuration
#
enable = false
poolsize = 10
# Security realms
# Format (<n> starts at 0):
# Security_realm [<n>] = <security_realm_class>
#
This file configures the server security. You can define multiple realms that are executed in order for each customer order.
services.config
# Services
# Format:
# Service [<service_name>]. Interface = <service_interface>
# Service [<service_name>]. Implementation = <service_implementation>
# Service [<service_name>]. Parameter [<param_name>] = <param_value>
#
This file configures the services that are published on the server. For each service, you should configure the interface and the implementation of this. Also, optionally, you can add initialization parameters.
With this we end this series. I'm always the order with any questions you have regarding this server.
Download source code: aquaitrt_2009-10-14.tar.gz

Hello very interesting application server, you hang a ejmplo ask how to use a small ejemplito. Regards
Dear friend I am very interested in this topic because I am developing an application and request an application server so I leave my mail we contacted johanagn@hotmail.com Greetings
In the coming days, I will publish an article with an example of how to implement a service with this application server. Greetings and thanks for the interest.