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 Assigning IDs for Use within Your Application.

Several sample configuration files, are provided in <Installation Location>\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";
Try
{
	SessionLoader sl = new SessionLoader();
	m_ScreenObj = (IScreenUPG) sl.requestScreenEx("","", XMLData, 0);
}
	catch (SessionException se)
{
	System.out.println(se.getMessage());
}

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.

Assigning IDs for Use within Your Application

You must ensure your SDK application manages IDs programmatically within the XML configuration unless one of the following conditions are met:

If one of these conditions is not met, you must create an XML configuration for each unique terminal ID. You must create an equal or greater number of XML configurations than will be used at any one time by your application.

Once a host connection has been established, your application can communicate directly with the host session using the various APIs provided in Attachmate Verastream SDK for Unisys and Airlines.

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