If you run two instances of the Alpha Anywhere Application Server on the same machine with the same hostname but different ports, you may encounter a problem of the sessions conflicting between the two instances. The way to fix this is to use different cookie names on the two instances.

Improvements from Alpha Five V10

Step by step instructions for running multiple instances of the application server:

Overview of configuring and running the Classic Application Server and Development Server. The Application Server settings control the server behavior, including configuring TLS/SSL, custom error pages, HTTP Publishing, and security.

The Application Server creates an icon in the Windows Systray to access the Control Panel and indicate the server's state. Each icon is visually identical when running multiple instances of the Application Server, so it becomes difficult to associate each icon with the correct server instance.

Xbasic classes used to implement web services are not reloaded unless the Classic Application Server is restarted or the __AARegisterClasses.a5w page is called.

If you have a SQL server stored procedure that sets the value of an output argument, reading the value in the output argument, after the stored procedure has executed can be tricky. That's because you have to ensure that you first loop through all of the result sets that are returned by the stored procedure before reading the output arguments.

The condition for an action can be copied to other actions that use the same conditions using the *[ui:Action is conditional and Same as Previous]* option.

This procedure explains how to place a running count of items on a report that produces something like the following. Note the sequence of numbers at the left of each Product ID.