|
|
|
Overview of SDK for UMC
Technical Note 1.0.9737490.3403544
Created 05-Oct-2001
Applies To
e-Vantage SDK for UMC
Component Object Model (COM)
Active Server Pages (ASP)
Goal
Overview of SDK for UMCFix
The Attachmate e-Vantage SDK for UMC is a set of Java and Microsoft Component Object Model (COM) APIs that allow you to easily add host access capabilities to your server-based custom applications (for example, Microsoft Active Server Pages (ASP) or Active Server Components). The SDK runs under NT and several flavors of UNIX.The Java and COM APIs provided in the SDK allow your applications to interact directly with host sessions configured using Attachmate e-Vantage Host Access Server (HAS) Management.
The architecture of e-Vantage SDK for UMC revolves around the Screen object model. Once you have acquired a configured Screen object using the SDK’s SessionLoader object, the Screen object allows you to interact with a 3270, 5250, T27, UTS, or VT host session. The Screen object provides access to the presentation space for reading from and sending data to the host. Screen objects are host-dependent, and there is a unique screen type for each type of emulation.
The presentation space is an area in PC memory where screen data are stored, and through which an automation application and the host communicate. Each running session has a presentation
space. Its contents are read, changed, or monitored with the Screen object.
The e-Vantage SDK takes full advantage of the latest Java and COM specifications and associated
development environments. The e-Vantage SDK also enables migration of your legacy HLLAPI (including INFOConnect™ and non-INFOConnect HLLAPI) applications. To facilitate migration, e-Vantage SDK provides many calls that correspond directly with your existing HLLAPI calls.
The e-Vantage SDK uses a Object-oriented programming model. Object-oriented programming model offers a powerful model for developing custom applications. Using objects speeds application development and improves the maintenance, reusability, and modifiability of these applications. This permits the SDK to be used from a number of development environments including:
• Microsoft Visual InterDev
• Microsoft Visual Basic
• Microsoft Visual C++
• Microsoft Visual J++
• IBM VisualAge for Java
This makes the SDK ideal for developers who need access to disparate systems. The SDK can be used to write custom connectors for data transfer or reface a green screen application with additional business logic. The SDK can run under a number of web applications servers. This permits the developer to integrate legacy data with a newer technology such as Oracle 8i or a third party application with interface APIs such as Peoplesoft. The SDK should be marketed to Integrators who develop applications for mid-ranges hosts such as the IBM AS/400 and Unisys Series A systems or older Unix systems.
The SDK under the covers is very similar to the Attachmate Enterprise Objects, a workstation, client-side development kit. The major difference is the SDK does not have any designer tools associated with it. The SDK object library can be imported into a development environment where the programmer can add the objects to their program. The SDK is also dependent on the Host Access Server Management console (HASM). The console manages the screen objects and access to those objects. Unisys terminal emulation has additional addressing needs. A companion product "Resource Server" acts like a Unisys DHCP server, issuing addresses as needed.
The following is an example using VBSCRIPT that would run under NT and IIS using Active Server Pages (ASP). Notice the KEYTYPE_HLLAPI syntax. This is very familiar to the programmer who has programmed against Attachmate transports in the past using HLLAPI.
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>e-Vantage Developed Active Server Page</title>
</head>
<body>
<script language="VBScript" runat="Server">
Dim loaderObj
Dim screenObj
set loaderObj = Server.CreateObject("SessionLoader.SessionLoader")
'
' request defined WebView "demand"
'
set screen.Obj = loaderObj.requestScreen("User1", "pass1","demand")
'
' Open session to 2200, note: webview demand auto opens to host
'
If screenObj.Open Then
'
' Wait for cursor positioned following Enter Userid/Password prompt
'
screenObj.waitForCursor 23,2,5000
'
' submit demand logon, can add additional logic to test for Account and Project-ID
' fields if necessary. userid/password should contain a valid logon.
'
screenObj.SendKeys "userid/password@E", screenObj.KEYTYPE_HLLAPI
screenObj.waitForString "DATE", 22, 2, 5000
Response.write("<p>")
Response.write("Logged onto demand!")
Response.write("</p>")
screenObj.Close
Else
Response.write("<p>")
Response.write("Open of WebView failed!")
Response.write("</p>")
End If
</script>
</body>
</html>.
