PowerTerm WebConnect OCX
This guide is subject to the following conditions and restrictions:
• The proprietary information belonging to Ericom® Software is supplied solely for the purpose of assisting explicitly and properly authorized users of PowerTerm WebConnect®.
• No part of its contents may be used for any other purpose, disclosed to any person or firm, or reproduced by any means, electronic and mechanical, without the express prior written permission of Ericom® Software.
• The text and graphics are for the purpose of illustration and reference only. The specifications on which they are based are subject to change without notice.
• The software described in this document is furnished under a license agreement. The software may be used or copied only in accordance with the terms of that agreement.
• Information in this document is subject to change without notice. Corporate and individual names and data used in examples herein are fictitious unless otherwise noted.
Copyright© Ericom Software. All rights reserved.
Ericom® and PowerTerm® are registered trademarks of Ericom® Software, which may be registered in certain jurisdictions.
Other company and brand, product and service names are trademarks or registered trademarks of their respective holders.
A key advantage that PowerTerm WebConnect OCX Control has is that this advance product uses nothing more than the robust and powerful, well-known and carefully debugged PowerTerm emulation engine, which is embedded in the HTML page or a Visual Basic application and exposes methods, events and properties to the client-side scripts. This allows any alterations and adjustments made to the original AS/400 or VT application to be reflected in the resulting web application totally "on-the-fly".
PowerTerm WebConnect OCX Control can be used in any Web scenario or a Visual Basic application where interaction with legacy systems is required and where cost effectiveness, time to market and non-intrusiveness are important.
The following configuration of development and run-time environments found to be compatible with PowerTerm WebConnect OCX Control requires:
To create a connection with HTML:
PowerTerm WebConnect Administration Tool definitions
2. Define a login script and keyboard mapping in the PowerTerm WebConnect Administration Tool if desirable.
Note For further information on keyboard mapping, refer to the online documentation for the PowerTerm WebConnect Administration Tool.
3. Customize the Settings in the PowerTerm WebConnect Administration Tool if desirable.
4. Confirm that the connection is satisfactory.
Note Not required.
For further information, refer to the online documentation for the PowerTerm WebConnect Administration Tool.
1. Determine the location of the OCX controls on the HTML page using Object tags.
2. Specify the CAB file in codebase as shown below:
<OBJECT id="WebConnectOCX" style="LEFT: 0px; TOP: 0px; RIGHT:0px; BOTTOM: 0px;"
classid=clsid:2A74D83E-280F-11d5-9ED9-0050DAD6BDFC width=0 height=0 VIEWASTEXT>
<PARAM NAME="_Version" VALUE="131072">
<PARAM NAME="_ExtentX" VALUE="9525">
<PARAM NAME="_ExtentY" VALUE="6350">
<PARAM NAME="_StockProps" VALUE="0">
3. In order to enable the PowerTerm WebConnect OCX Control you must first connect to PowerTerm WebConnect server using the LoginToServer method of Setup interface.
If (WebConnectOCX.Setup.LoginToServer("HOSTNAME", 4000, "USERNAME", "PASSWORD", true) == true)
4. After the server connection was established, select the connection that you defined previously by the OpenSession method of Setup interface. PowerTerm WebConnect OCX Control upon identifying the connection, opens the session, runs a login script, and applies the keyboard mapping and all the visual settings.