Verastream SDK for Airlines
Defining an XML Configuration

In order to communicate with the host, your SDK application needs to use an XML configuration (a named collection of terminal emulation settings) that contains information about the host connection and session your application uses. You can either create an .xml file that contains this information and reference it from your application, or you can embed the XML configuration data within the application. The number of configurations your application needs is determined by how you manage IDs. See Using Reflection ID Manager

Several sample configuration files, are provided in <Installation Location>\Program Files (x86)\Attachmate\VerastreamSDK\samples\xml. You can modify one of these files or create a similar file for your own use. The various sample applications provided with the SDK illustrate both ways to define a configuration for your application. See the Sample Applications Overview for more details.

The XML configuration must include the following information:

You can accomplish all of this by calling the SessionLoader object, as shown below:

ScreenUPG m_ScreenObj;
String XMLData = "Specific to terminal Type";
        SessionLoader sl = new SessionLoader();
        m_ScreenObj = (IScreenUPG) sl.requestScreenEx("","", XMLData, 0);
        catch (SessionException se)

Where XMLData contains the screen object specific to your host type. For more information, see Requesting a Screen Object, which contains links to the XMLData parameters for each host/connection type available.

The SessionLoader object and the screen type packages are documented in the Attachmate Verastream SDK for Unisys and Airlines Javadoc and .NET documents.

Setting up a Secure Connection

The Verastream SDK supports secure connections through SSL/TLS for the following host systems:

3270 5250 ALC MATIP  ALC Shares


Prerequisites for Secure Connections


Before you attempt a secure connection, you will need to set up the Verastream SDK for server authentication as shown in  Setting up the SDK for Secure Connections .

Parameters for Secure Connections

After you have set up the SDK for secure connections, you will need to add the following parameters to your XML configuration:

Parameter Value Description
SecureConnection true Create a TLS-secured connection.
false Create a normal unsecured TCP connection (default).
FIPSMode true Enforce FIPS 140-2 operation (default).
false Allow non-FIPS-approved operation.
KeyStoreFile path Path to the Key Store file (required).
KeyStoreFormat (JKS, BKS, PKCS12) Format of the Key Store file (required).
KeyStorePWD password Password used to create the Key Store file (required).


Using Reflection ID Manager

To use the Reflection ID manager, add the IDMgr parameter to the session XML:

IDMgr="<URL for ID Manager>" causes the session to request an ID/Address from ID Manager. For Example:


ID Manager requires that an exact set of criteria be supplied in the request, (no more, and no less).  To supply selection criteria, include only the appropriate parameters in the following list:

Parameter Value Description
IDMgrPool PoolName Will be sent as specified.
IDMgrIPAddress address The actual IP address will be sent if you supply an empty string, but it may not be the address you expect.
IDMgrDomainName name The DNS name of the system will be sent if you supply an empty string.
IDMgrUserName user The name of the current user will be sent if you supply an empty string.
IDMgrSessionName name A dummy session name will be sent if you supply an empty string.
IDMgrHostAddr address Will be sent as specified.
IDMgrHostPort port Will be sent as specified.
IDMgrApplication appl Will be sent as specified.
IDMgrAssocSet assoc Will be sent as specified.

The ID is released when a session is closed, so you must make certain to close all sessions when terminating your application.  Otherwise, the IDs will not be available next time.

Related Topics
The Screen Object Model
Requesting a Screen Object
Common Tasks