FAQ Pages: WebConnect Problems

FAQ for PowerTerm WebConnect

Choosing between a 7 or 8 bit VT emulation type

We are transferring our site (Data Bases & emulations) from 7 bit to 8 bit.
The emulation found to be suitable for that purpose is VT220-7.

When we tried to use VT220-8 I noticed that the use of "upper-arrow" (which is used in Unix to show the previous command) did not function in the right way, while with VT220-7 works as expected.

  1. What is the meaning of the 7 or 8 in the VT220?
  2. Is there any problem with working with VT220-7 for full 8 bit environment?
  3. Can I configure the VT220-8 to work the same way as VT220-7 while using the "upper-arrow"?
In regards to your questions about moving from 7 to 8 bits:
Changing to VT 220-8 has to do with the way escape sequences are sent:
  1. Using VT 220-8 a "CSI" will be sent as "CSI" char (hex 9B).
  2. Using VT 220-7 it will be sent as a 2 bytes sequence esc [ (hex 1B 5B).
The "upper arrow" is CSI A (i.e. esc [ A ) in -7 mode.; you need to do the following:
  1. Open WebConnect Administration Tool.
  2. Double click on the relevant connection.
  3. Click the Settings button.
  4. In the Emulation tab choose a VT###-7 terminal type.
  5. In the General tab check the "Use 8 Bit Data Characters" check box.

HLLAPI - Screen contents in a long string

When the customer implements the HLLAPI component, he receives the contents of the expected screen in a long string without "divisions".

This is the correct behavior; HLLAPI always returns the information in a string. In order to parse the string, the customer would need to implement it in the tool in use.

Restoring the VT terminal defaults. HostView client

How can the user restore the VT terminal defaults from the client side?

If you are using a VT or an ANSI emulation you can map a key or soft-key with:
display \033\[!p
If you need also to clear the screen then use:
display \033\[!p;activate-menu-item ClearScreen

Modifying WebConnect web components automatically

How can I modify WebConnect web components automatically?

WebConnect Web Modifier is designed to assist you, the Administrator, with making server address changes to your PowerTerm WebConnect Web Components.

If you have recently added an additional PowerTerm WebConnect server to your farm, or removed one, this utility will modify all of the relevant html pages to make such changes much less tedious to accomplish.

NOTE: This utility requires that you have Microsoft .NET Framework 1.1 installed on your server.
  1. Download WCWebModifier.exe
  2. Copy "WCWebModifier.exe" to the "x:\Program Files\Ericom Software\WebConnect 5.y\" folder on any server that contains the PowerTerm WebConnect Web Components. Substitute the drive letter for "x" and the PowerTerm WebConnect version for "y", so for example, if you are working with PowerTerm WebConnect 6.0 on C:, your path would be "C:\Program Files\Ericom Software\WebConnect 6.0".
  3. Launch the "WCWebModifier.exe" utility and for each PowerTerm WebConnect server you would like accessible from the same web pages, check a box for a WebConnect Server. If you have modified the listener port on that server, also check the Port Number underneath that server and type in your server address and port number. This utility allows you to place up to 4 servers into each HTML page.
The default PtAgent Settings can be modified as well. The default settings are: "/NOSELFUPDATE /SHORTCUT=BOTH /AUTOLOGIN=NO". If you would like to change settings based on options you have read within the Administrator's Guide for PowerTerm WebConnect, you can simply change this options list and this utility will make all changes for you.

When you are done setting your servers, ports, and PtAgent settings, you simply click the "Apply" button, and the utility will modify all files required.

There are only 2 errors that this utility will generate.
  1. After you click "Apply", if a file does not exist, it will tell you which file.
  2. If you are receiving an application crash notification, it is because you need to have Microsoft .NET Framework 1.1 installed on your server.