Alpha Anywhere Standard Application Server


The Alpha Anywhere Standard Application Server is used with web and mobile applications.


The Alpha Anywhere Application Server handles HTTP and HTTPS requests from a client browser or server. The Application Server is responsible for handling Ajax Callbacks and translating Xbasic in .a5w pages and components (such as Grid, UX, Tabbed UI, etc) into HTML, CSS, and JavaScript to be executed in the client's browser. The Application Server also services other types of content - XML, JSON, multimedia, etc - that is stored in the server's file system and interacts with databases and other web services required by an application.

For information about the Alpha Anywhere Application Server for IIS, see the Alpha Anywhere Application Server for IIS.

Running Alpha Anywhere as a Service

So here's the challenge. When your system reboots -- possibly after a power failure or (more commonly) because of a Windows security update -- you need the Alpha Application Server to start running again automatically. Any easy way to do this is to put the program in your startup folder.

Running Two Server Instances on the Same Hostname Using Different Ports

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

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

Run multiple applications or web sites by using multiple Application Server configuration files

Traditionally, Application Server administrators provide service for multiple applications by using a single instance of the Application Server, placing each distinct application within a different subdirectory under the webroot.

Installing an SSL Server Certificate

When you receive the SSL Server Certificate:

Application Server Functionality

Browser tracking, caching of A5I files, caching of Gzipped output, MIME types, session files , session variables, and trace logging.

Check the clock

Web applications depend on accurate time keeping. Sessions are managed using a cookie, and the server sets a lifetime for that cookie based on what it thinks is the current time. The client then receives the cookie and acts on it based on its own clock. Additionally, the server will direct the client to store responses that it sends in a cache until a specified time.

Restricting Access by IP Address

The Application Server Control Panel allows you to restrict access by IP address on the Access tab. This is a server-wide configuration. To implement this at the page level, add some Xbasic to the top of your restricted pages to check the IP address, which is available to you as REQUEST.REMOTE_ADDR . Something like the following if added to your pages would only allow access by the specified IP address. Anyone else would be redirected to a different page.

Configuring and Running the Standard Application Server

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.

Starting the Standard Application Server

Instructions for starting and stopping the Alpha Anywhere Standard Application Server

Using a Systray Caption to differentiate multiple server instances

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.

See Also