Consultor Eletrônico

Menu: Environments > Application Server

Application servers are used to run processes in servers other than the one used to run the Console. Regardless of the selection entered on the application servers configuration screen, each stage of the process asks whether it should use the application servers registered. If you have not made application servers available to the Console, this option will be disabled in the following stages.

For processes of checking settings and data, assumptions, dictionary preparation and dictionary correction, only the first application server register will be used. Thus, for these processes, you can connect to the databases in single-user mode. For the data update stage, all registered application servers are used simultaneously, sharing the programs among themselves.

The servers register will specify an entry for each agent available in Appserver brokers. The Console regards a register entry as a server. The broker executes the balancing between Appserver agents.

If the application server is in a server (or more) other than the Console server, you must copy the following directories to compose the data directory of the Console for the Appserver. If the appserver is Unix/Linux, the copy must be via FTP to avoid problems with line terminators.

If the server has the 64 bit Progress installed, you must copy the char64 directory in the Console work directory, following the same aforementioned rules.

You must configure an Appserver broker with the following parameters:
1. Operation mode: State-reset
2. Work directory: Point it to the Console data directory copied to the application server.
3. Agent startup parameters: -cpstream "ibm850" –d dmy –numsep 46 –numdec 44 -s 500
4. Pooling interval: Enter the quantity of agents the Appserver broker will offer. The Console regards each agent as a server.

Note: Do not indicate any .pf file with database connection in the AppServer configuration. The Environments Management Console automatically connects the database while running the update process.

The agent initialization parameters may also regard parameter -h, by specifying the number of databases to be simultaneously connected by the agents, and parameter -Mm, if the connection is in client-server mode.

The Appserver brokers must be available when configuring the application servers in the Console. The Appserver agents you cannot connect will be ignored in the update and entered in the log conversao.txt.

To add a new Application Server in the Environment Management Console, click 'New' in the menu to the left of the Console.
1. Server description: Enter a name.

2. Connection parameters: The connection to be set in the console screen requires the following parameters:
-------------------------------------------------------
-AppService <broker> -H <hostname> -S 5162
-------------------------------------------------------

Where:
a. -AppService: Name of appserver broker
b. -H: Name or IP of server where the appserver is created.
c. -S: 5162 is the port of default NameServer. If you use a NameServer other than the default, enter the corresponding port.

3. Number of agents: Enter how many agents for the appserver broker.

Then click 'Save'.

You can register as many brokers as you need, even indicating to different machines.

Test server: After making the necessary registrations, the 'Test Server' button will test the access to all the configured servers at the same time, reporting with Status: OK. If you cannot connect to a configured server, the console will display an error message in the Status field and open a new field below as 'Errors': this field shows the details of the errors.