README File WinFIOL 7.0 (c) Copyright 2005 Ericsson AB. All rights reserved. ********************************************************************** ********************************************** ************************ This README file contains information that supplements WinFIOL's User's Guide and built-in online help system. ********************************************** ********************** ************************************************ ************************ README FILE CONTENTS. 1. 2. 3. 4. 5. 6.
Installation What's New in this version WinFIOL contents Known problem areas CommandForm Technical support
********************************************************************** ********************************************** ************************ ********************************************** ********************** ************************************************ ************************ 1. Installation Installation is done by running setup.exe on the WinFIOL 7.0 CD. Select WinFIOL in the list of tools to install. WinFIOL can be uninstalled from: Windows Start menu | Settings | Control Panel, open the Add/Remove Programs dialog, select WinFIOL and Tools. ********************************************************************** ********************************************** ************************ ********************************************** ********************** ************************************************ ************************ 2. What's New in this version a) A simplier simplier channel and file view window which makes it easier easier to locate, start and handle channels, script and log files. b) A new Wizard that makes it easier to create new channels. Available from menu Channel | New. c) Starting a copy of an an already already opened channel is simplified by using cloning. d) All Preferences are easily accessable from a single menu. e) Transmit/Process dialogs can be docked together. f) SEA protocol driver added. g) Undress tool supports more options. h) New target CPP(NCLI) that support the NCLI application in Cellobased environment. i) Many new script commands. See the help for a list of new commands.
j) Much smaller installation package. k) Much quicker installation and removal of the WinFIOL package. l) Multi-user environments are supported using a seperate server license. m) A configuration change affects all users in a multi-user environment. For further information, see the Product Revision Information (PRI) for WinFIOL. ********************************************************************** ********************************************************************** 3. Contents: WinFIOL 7.0 CXCH 135 002/1 R7A This version of WinFIOL includes the following: Target drivers: - IOG 3, IOG 11, IOG20, APG30, APG40, ERIPAX, MD110, OSS(AXE), OSS(TGW) and CPP(NCLI) support Protocol drivers: - Telnet(TCP/IP), RS232(Serial), Modem(Telephony), WFShare (for channel sharing with OPTool), Secure Shell v.2 (SSH) and SEA.
Plug-ins: - Script plug-in, monitoring plug-in, active printout plug-in, dangerous commands plug-in, error log plug-in Character translation files for: - Denmark, Finland, France, Hungary, Spain, Sweden LDAP client support: - To access data for the Target Manager Network/Tree of Exchanges dialog. Browser Library drivers(Documentation Browser support): - ALEX, KRSWin, DocView CommandForm support: - Start CommandForm Tool from a button on WinFIOL.
A.) Target driver dll files and the targets they are supporting: ---------------------------------------------------------------
trgiog11.trg - IOG 3 (May be used "as is", no longer officially supported.) - IOG 11 - IOG 20 - APG 30 - APG 40 - OSS(AXE) - CPP(NCLI) (Supports NCLI in Cello targets) - Generic NE (Supports non-AXE targets) trgoss9x.trg - OSS(TGW) with single logon support through Telnet Gateway (TGW). See below for more information. trgmd110.trg
- MD110 eripax.trg - Eripax B.) Communication protocol driver dll files: --------------------------------------------rs232.prt (Serial protocol) tapi.prt (Modem protocol, using Windows Telephony API, TAPI) telnet.prt (telnet over TCP/IP) wfshare.prt (WinFIOL channel sharing using Microsoft COM technology) ssh.prt (Secure shell, if available) sea.prt (SEA)
C.) Character translation files: (For different countries) ---------------------------------------------------------- denmark.xlt, finland.xlt, france.xlt, hungary.xlt, spain.xlt, sweden.xlt D.) Using Telnet Gateway with Single login driver ----------------------------------------------------The new target driver OSS(TGW) must be used to support a single login procedure when using the Telnet Gateway. No login information should be specified in Channel Properties, instead a login dialog box is shown the first time any NEs is accessed through the OSS(TGW) target. The given user name and password is then automatically used in all subsequent login attempts. The user name and password cannot be changed unless the current logged in user is logged off. A log off is done by right clicking the Channel window and selecting the "Log Off" choice. The login dialog box is then shown the next time a Connect (F5) is pressed. The user name and password is remembered over a connection loss.
NOTE: Target driver OSS(TGW) is always used for OSS-RC.
IMPORTANT1: When using a TMOS LDAP structure, use OSS as Terminal type when defining the OSS(TGW) driver in LDAP and add the new attribute login.type=tgwsingle. The target driver is set to OSS(AXE) if the login.type attribute is not set.
IMPORTANT2: Note that OSS(TGW) does not support CN-OSS. Target driver OSS(AXE) shall be used for CN-OSS.
E.) Using the X.25 I/O Mediator together with WinFIOL -----------------------------------------------------The X.25 mediator, a new Ericsson gateway product, offering telnet and FTP communication between a TCP/IP and an X25 network, can be used with WinFIOL with the telnet protocol driver. Some extra X.25 mediator prompts have been added among the default prompts for each target supported by trgiog11.trg. See Channel Properties | Target, for the respective target. r>,[space]:,[space]> are the minimum settings added for the actual
prompts like the three following (where Mediator> is the prompt from the mediator itself, and leading spaces in target prompts is AT-port legacy behaviour that occurs, because X25 is using AT-ports): Mediator> : > In WinFIOL channel properties the prompts and the mediator command to send MML commands over X25 can be automated with the Login/Logout settings (Login Engine) under Channel Properties | Login/logout | Add where the prompts and the respective responses needed are: Prompt Response ------------Login: Password: Mediator> mmlcall iog7 at-7 NOTE: The parameters to the mmlcall command is an example, check this with your organisation, it depends on how the IOG is configured.
********************************************************************** ********************************************************************** 4. Known problem areas (Problems and limitations): Also see the EM-support web site for any Trouble Reports. Known Problem: Work-around: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Limitation: The Login Engine can now detect a failed logon and will re-start the logon process from the beginning of the login script. Note however that it will not detect a failed logon, if the login script does not contain anymore prompt/response pair after the password is given. Solution: Add a dummy login For example, on a Prompt: login: Password: $
statement after the password is returned. Unix system: Response: user password \r
or for apg40: Prompt: login name: password: Domain: >
Response: user password domain \r
The last prompt/response pair enables the login script to detect a
failed logon. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Limitation: The login script failed when connecting to an AT-terminal that has been set-up to receive alarm printouts. The connection triggers the ceasing of some alarms in the exchange. These alarm printouts are then printed on the AT-terminal before the actual connect sent by WinFIOL is handled. It appears that the exchange sometimes looses the connect character when printing the alarm printout causing WinFIOL to remain hung until the login sequence times out waiting for an exchange prompt that never comes. Solution: Add two dummy carriage returns at the beginning of the login script: For example: Prompt: Response: LE_Send \r LE_Send \r USERCODE: user PASSWORD: password ********************************************************************** ********************************************************************** 5. CommandForm CommandForm is a program that WinFIOL uses to present a graphical command form in which to fill in an MML command and present alternative parameters and options as well as checking the syntax. ********************************************************************** ********************************************************************** 6.
Technical support
For technical assistance please contact your local Ericsson company.
