Release Notes
ASNA Browser Terminal ®
Release date: 2024-07-09

Important notices

ASNA Browser Terminal® must be installed on a server that has no other instances of DataGate WebPak. This means no websites running on Wings, Mobile RPG, or AVR.

If you intend to use ASNA Browser Terminal for user access across the public Internet we strongly recommend securing the server site with Secure Socket Layer and/or other data protection measures.

Installation Notes

ASNA Browser Terminal® must be installed on a server that has no other instances of DataGate WebPak. This means no websites running on Wings, Mobile RPG, or AVR.

The download packages on this page include the components for BTerm and WebPak. The downloadable package for DataGate 17.0 for IBM i can be found on the ASNA Downloads Page

ASNA Browser Terminal will install into a virtual directory in the host machine's www root directory.

Warning If you intend to use ASNA Browser Terminal for anything other than strictly in-office purposes, strongly consider securing the server site with Secure Socket Layer and other data protection measures.

Downloading with Microsoft Edge

If this software is downloaded via Edge you may receive a message stating that this file "is not commonly downloaded" when attempting to install it. In this event click the View Downloads button, select the ASNA product to install from that list, and confirm that you'd like to install it.

Similarly, attempting to install the software directly through Microsoft Windows may cause a "Windows protected your PC" message to appear. In this event click the small More Info prompt on the left, and click Run Anyway on the following window.


Secure Sockets Layer (SSL)

The DataGate client software contained in this release significantly changes the way Secure Sockets Layer (SSL) connections are configured. DataGate SSL support was introduced in Version 15 as an option for secure network communications between DataGate clients and servers. In prior releases, DataGate client connection configurations, by default, specified an SSL-enabled connection. This allowed many users to enhance the security of their applications by simply installing the new, SSL supporting DataGate release. Unfortunately, other customers experienced connection and security issues due to shifting standards and evolving platform infrastructure supporting SSL, as offered by Windows and IBM i. In this release, DataGate client users must now "opt-in" when configuring new connections secured with SSL. When a new connection configuration is created, the default setting is to specify a non-SSL, or "clear-text" connection to the server. DataGate connections are typically configured as "database names". A database name is a collection of properties defining all the information needed to connect to a DataGate server from the client computer. Existing database names are not affected by this change, but new database names are affected: Database names created by prior releases retain the same SSL configuration as they had when created or modified. The default configuration of new database names will specify non-SSL connections.

Creating SSL-Enabled Database Names

Online documentation linked below fully details the process of creating an SSL-enabled database name configuration using DataGate Studio. The process is very similar for users of DataGate Monitor. [Read more about DataGate's SSL support](

Other DataGate SSL Options

DataGate offers many options for enhancing the security of its client/server connection with SSL. For full details of options available for both the client and server, please [consult the online documentation.](

Configuring DataGate Connections Programmatically

Connection configurations are represented in DataGate as instances of the SourceProfile class in the DataGate .NET API. While most users and applications will configure connections via database names, some programs use the DataGate API directly. Users of the SourceProfile class are advised that the changes in this release may represent a **breaking change** to the behavior of your programs. The default value of the SourceProfile.SslOptions property is now SslOptions.None; in previous releases the default value was SslOptions.Request. If your program does not explicitly set this property, connections made with the SourceProfile instances you create will be clear-text, rather than SSL-enabled. If you directly create and use SourceProfile instances in your programs, ASNA highly recommends modifying them to explicitly set SourceProfile.SslOptions before deploying this DataGate release.

Database Name Migration From Non-SSL Releases

Database names created by DataGate releases prior to Version 15 do not contain SSL-related configuration information. When these database names are read by Version 15 software, the configuration is migrated to include SSL configuration options. Prior to this release, those migrations would enable SSL connections, unless otherwise explicitly changed by the user. Henceforth, automatic database name migrations will disable SSL in the connections they represent. Users who deploy applications using the database names contained in configuration files created with prior, non-SSL supported DataGate releases are advised that changes in this release may represent a **breaking change** in this deployment strategy, for reasons outlined in the previous paragraph.


Software Requirements

**Platform support/product requirements** Platform support and product requirements are detailed on our [Product Requirements page](

Signing On

*To run ASNA Browser Terminal after installation, navigate a web browser to:

For further instructions see the Browser Terminal User's Guide.

Changes Since Version:

Clients - DataGate

DataGate Server

Monarch WebControls

Serengeti - Code Generator Tools

Visual RPG IDE Project