Running Two Server Instances on the Same Hostname Using Different Ports
/documentation/pages/Guides/Application Server/Running two server instances on the same hostname.xml
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.
Running Multiple Instances of the Alpha Anywhere Application Server
/documentation/pages/Guides/Application Server/Running Multiple Instances of the Alpha Anywhere Application Server.xml
Step by step instructions for running multiple instances of the application server:
Configuring and Running the Standard Application Server
/documentation/pages/Guides/Application Server/Server Settings/index.xml
Overview of configuring and running the Standard Application Server and Development Server. The Application Server settings control the server behavior, including configuring SSL, custom error pages, HTTP Publishing, and security.
How to Install Alpha Anywhere Community Edition and the Alpha Anywhere Developer Edition on the same System
/documentation/pages/HowTo/Installation/Install Community Edition Side by Side Developer.xml

Alpha Anywhere Community Edition and the full Alpha Anywhere Developer Edition can be run side-by-side on the same system.

Using a Systray Caption to differentiate multiple server instances
/documentation/pages/Guides/Application Server/Using a Systray Caption to differentiate multiple server instances.xml
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.
AlphaDAO - Stored Procedures and Output Arguments on the SQL Server
/documentation/pages/Guides/Databases/Stored Procedures/AlphaDAO - Stored Procedures and Output Arguments on the SQL Server.xml
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.
Restricting Access by IP Address on the Standard Application Server
/documentation/pages/Guides/Application Server/Restricting Access by IP Address.xml

Access can be restricted to specific IP addresses for your Alpha Anywhere web applications and web services.

How to Test Connection Strings on the Application Server
/documentation/pages/GettingStarted/GettingStartedTutorials/Basic Tutorials/Connection String Genie.xml
Named AlphaDAO connection strings must be defined relative to the server in a publishing profile. The Application Server's Connection String Builder Genie can be used to create and test published connection strings. Connection strings can then be copied to the publishing profile in the Alpha Anywhere Development Environment.
Placing a Running Count on a Report
/documentation/pages/Guides/Report/Adding System and Calculated Fields/Placing a Running Count on a Report.xml
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.
Using the "Same Condition as Previous" Setting
/documentation/pages/Guides/Desktop/Design/Platform/Xbasic Action Scripting/Introduction/Using the Same ConditionasPrevious Setting.xml
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.