How to Migrate e-Vantage SDK Programs to VHI

By migrating e-Vantage SDK terminal emulation applications to Host Integrator's powerful integration platform, you make them available to Web applications, mobile apps, and SOA Web services. Host Integrator contains a .NET class library, EAO2V, that is also accessible through a COM interface and provides you with the ability to do just that.

The e-Vantage SDK library currently supports only 3270 terminal type sessions.

The classes, methods, and properties that comprise the e-Vantage SDK HLLAPI Adapter are documented in a MSDN-style compiled help system that is included with Verastream Host Integrator.

Migrating VB.NET or C# Programs

  1. In your .NET e-Vantage SDK program, remove the reference to the e-Vantage SDK library, and add a reference to both the EAO2V library and the .NET connector:
    %VHI_ROOT%\lib\dotnet\Attachmate.Verastream.HostIntegrator.EAO2V.dll
    %VHI_ROOT%\lib\dotnet\WRQ.Verastream.HostIntegrator.dll
    
  2. In your code, add using directives for these classes.
    using Attachmate.Verastream.HostIntegrator.EAO2V;
    using WRQ.Verastream.HostIntegrator;
    
  3. You do not need to deploy a model as the e-Vantage SDK adapter uses the standard model Terminal3720, which is already deployed. You can use a different model if necessary. To use a different model, In the VHI Design Tool, create a model that connects to the same host and port as the e-Vantage SDK program. Leave the model empty (no entities) to get started. Set the property AtmConTN3270.Name to a string in the form modelname@sesssrvrhostname.
  4. Compile and debug your code.

Migrating Microsoft Office Visual Basic for Applications (VBA) Programs

The COM interface to the EAO2V library is not based on the Verastream Host Integrator COM connector. It is a .NET class library. While it is possible to use both the EAO2V COM interface and the Host Integrator COM connector in your VBA program, these two connectors are unrelated; you cannot share sessions between the two. Microsoft Office VBA interfaces use COM; if you are not using Microsoft Office VBA, we recommend the use of .NET because it offers more flexibility.

  1. In your Microsoft Office VBA program, remove the reference to the e-Vantage SDK library, and add a reference to the EAO2V COM library:
    %VHI_ROOT%\lib\dotnet\Attachmate.Verastream.HostIntegrator.EAO2V.tlb
  2. You do not need to deploy a model as the e-Vantage SDK adapter uses the standard model Terminal3720, which is already deployed. You can use a different model if necessary.

    To use a different model:

  3. All e-Vantage SDK programs start with two assignments: assigning both the screen and connection objects to the session. Change your VBA code to use "Set" statements.

  4. Compile and debug your code.

What do I need to watch out for?

Depending on the situation, you may have to make additional changes to the EXTRA! client program, see Troubleshooting Your e-Vantage SDK Migration.

Related Topics
Bullet Troubleshooting Your e-Vantage SDK Migration
Bullet Migrating e-Vantage SDK Applications to Verastream Host Integrator
Bullet Model Debug Messages
Bullet Host Integrator API Introduction
Bullet .NET Application Requirements