Liaison User Guide

Table of Contents

1.

I

NTRODUCTION

... 1

1.1 Overview...1

1.2 An Explanation of the Liaison Objects ...2

1.3 A word about this manual...3

1.4 Contact information ...4

1.5 Schematic...5

2.

P

REPARING FOR

L

IAISON

... 6

2.1 Liaison Requirements ... 6

2.2 Communications Considerations... 9

2.3 Atlanta Athena Terminal Security... 11

2.4 Atlanta PID Configurations ... 12

2.5 Atlanta User File Maintenance... 13

2.6 PC/PCM IMPACT ON SYSTEM PRINT... 14

2.7 Have a Look at the Website ... 15

3.

I

C

... 16

3.1 The Possible Sources ... 16

3.2 Installation – An easy step-by-step process ... 16

3.3 Configuration ... 22

3.3.1 Starting the Liaison Commander ...22

3.3.2 First Time Running Liaison ...22

3.3.4 Liaison Configuration Wizard – Step 1 of 6 (Description)...24

3.3.5 _{Liaison Configuration Wizard – Step 2 of 6 (Terminal Login)...25}

3.3.6 Liaison Configuration Wizard - Step 3 of 6 (Application)...26

3.3.7 Liaison Configuration Wizard - Step 4 of 6 (Colors) ...28

3.3.8 Liaison Configuration Wizard - Step 5 of 6 (Communications)...29

3.3.8.1 Protocol Selection...30

3.3.8.2 TCP/IP Configuration...31

3.3.8.3 _{X.25 Configuration ...32}

3.3.8.4 DialUp Configuration...33

3.3.8.5 PC/PCM Configuration Wizard ...35

3.3.9 Liaison Configuration Wizard Step 6 of 6 ...45

3.4 Adding a Shortcut on the Windows Desktop ... 46

4.

O

PERATION

... 51

4.1 Invoking the Program ... 51

4.2 About the Commander... 54

4.3 Session Configuration Wizard ... 55

4.4 The Emulation Screen... 56

4.5 Menu Contents... 57

4.6 The Tool Bar... 65

4.7 Split Screen ... 66

4.8 The Status Bar ... 68

4.9 User Friendly GUI's (Graphical User Interface) ... 69

4.9.1 DCS Boarding GUI ...69

4.9.2 SDCS Check-In GUI ...70

4.9.3 World Tracer GUI...71

4.10Closing Liaison... 72

5.

U

SING

PC/PCM

... 73

5.1 Display of the PC/PCM Monitoring Tool (aka PC/PCM) ... 73

5.2 PC/PCM Menu ... 74

5.2.1 Device ...74

5.2.2 View ...76

5.2.3 Diagnostics ...78

5.2.4 Help...79

5.3 Device Type Window... 79

5.4 System Messages Window ... 79

5.5 Diagnostics ... 80

5.6 Troubleshooting PC/PCM... 81

6.

L

IAISON

S

CRIPTS

... 90

6.1 Record Script... 98

6.2 Playback Script ... 105

6.3 Liaison Script Assistant - Version 1.0.2... 109

6.4 Scripting Commands... 112

7.

A

PPENDICES

... 115

7.1 Appendix A - PC/PCM Configuration Wizard ... 115

7.1.1 Message Printer...117

7.1.2 Ticket Printer...120

7.1.3 Automated Ticketing and Boarding (ATB) ...126

7.1.4 Boarding Pass Printer One/Two ...133

7.1.5 Bag Tag Printer...139

7.2 Appendix B - X.28 Asynchronous Configuration... 144

7.3 Appendix C - Slow/No Response Analysis for TCP-IP Liaison ... 148

7.4 Appendix D - EICON Cards and Cables ... 149

7.5 Appendix E – Windows XP and Liaison ... 150

7.5.1 Liaison Installation in Windows XP Environment... 150

7.5.2 Removing the Default File Sharing Option ... 151

7.5.3 Creating the SITA Share... 152

1. Introduction



1.1 Overview

THE OBJECT CONCEPT

Liaison is a family of program objects that are combined to allow access to the SITA Airline Application Services (AAS) division mainframe applications from PC’s. The user interface can be either through various high-level Graphical User

Interfaces (GUI) or through expert (native) mode terminal emulation. Communications objects for TCP/IP, X.25, and X.28 are available, as is the PC/PCM printer control object. An object exists for UTS emulation to the Atlanta IS hosts, and an object for 3270E emulation to the London IS hosts is new with version 5.1. These different objects flexibly combine in the client PC to create a product tailored to the specific needs of the user.

Installing and managing the client workstation is also made easier using objects. A coded algorithm (Registration Key) is entered during the installation process, designating which objects are to be included, as indicated in the contract. The installer only needs to insert a few simple communication values to complete the process. The user now decides which objects are to be activated, simply by pointing to and clicking on an icon.

GRAPHICAL USER INTERFACE (GUI)

The GUIs are presentation software designed to allow the user to easily determine what needs to be processed in the required order. For example, the check-in procedure occurs in a predictable sequence. As each step is completed, the program is intuitive enough to determine when that step is finished, and presents the next step automatically, without the agent having to know the mainframe entry. The principal idea is to remove much of the memorization of the host formats; thereby reducing the training time normally needed for agents.

ORIGIN/PROGRESSION OF LIAISON

This family of products was originally developed in the 16-bit environment, able to run in the Windows 3.X operating system. However, as more PC’s converted to or were purchased with Win95/WinNT, incompatibilities were increasingly experienced since these newer workstations operate under 32-bit architecture. The old 16 bit applications will not run under Win98. This situation presented a challenge to convert the previous family of products to the 32-bit environment. Other challenges also arouse in the area of expanding emulation and

communications environments. This challenge has been met with the complete conversion to 32-bit architecture, the addition of TCP/IP and X.25

communications objects, addition of the TN3270E terminal emulation object, and the addition/enhancement of GUI objects.

KEY BENEFITS

Some benefits of Liaison include:

• Improved cost per workstation equates to reduced cost of ownership • Eliminates dependency on third party software vendors

• 32-bit environment offers better memory management and more stability • Introduces dynamic PIDs for ATLIS connectivity

• Rapid application development

• GUI environment reduces training time • Simplified installation

1.2 An Explanation of the Liaison Objects

As mentioned previously, Liaison is comprised of multiple objects. The following sections breakdown each object type:

The Commander

All sessions may be added, deleted, configured, and launched from this toolbar. It appears when the user starts the Liaison application from the Desktop Shortcut or from Start / Programs / Liaison The Emulator Commonly referred to as "Expert Mode", this screen allows native

transactions to be entered GUI Modules

GUI (Graphical User Interface) screens provide a user-friendly environment. These programs prompt agents for the next

transaction, layout information in picture form, and often anticipate the next command. Liaison offers several GUI options, such as

Ticketing, World Tracer, and both Boarding and Checkin for DCS Scripting

Sometimes referred to as "macros", several commands can be run sequentially by starting a script. They may contain anything from a single entry mask to dozens of mainframe entries without pausing. See Section 6 for additional information

Printer Handling

Printer security and dialogue are handled on a local basis using the PC/PCM object. The PC/PCM print-handling object may also be applied to applications requiring secured printing jobs, such as Departure Control or Ticketing, or may be used with standard parallel printers for system printing.

Comms Options

This object offers the user the option of selecting the communications protocol to be employed when in dialogue with the host system in ATL. TCP/IP, X.25, and X.28 communications are available for use with Liaison. Note P1024C can not be used with Liaison

Terminal Emulation

Objects

1.3 A word about this manual

This manual is included in hard copy form with the initial Liaison shipment to an airline. Should you desire more copies, a softcopy is always copied to the default install location during the install process. This default location is C:\PROGRAM FILES\SITA\LIAISON. The file is in both Microsoft Word and Adobe PDF versions; UserGuide.doc or UserGuide.pdf. You may download the PDF version from our Internet site

1.4 Contact information

For Liaison contract and pricing issues, please contact your SITA account manager or BDM. They will coordinate with the Atlanta Sales Support Team (SST). Also contact your account manager or BDM to place orders for all connections to the SITA network, be they TCP/IP (LANAS or ISNET), X.25 or X.28.

Liaison Support

During Atlanta Business Hours

8:30 am. – 5:00 pm.

Liaison [email protected]

ATLHDXS

ZZ HELPDSK

Passenger Services Help Desk

[email protected]

LIAISON GUI APPLICATION SUPPORT

DCS and RES ATLHDXS

TKT ATLGTXS

Additional Support specific to Liaison GUI Applications

WT ATLGBXS

EICON

EICON Card &

EICON X.25 Gateway Software

Sales EIS Julie Cody NYCBTXS

631-244-2509 x240

[email protected]

ATHENA TERMINAL SECURITY

Initial setup of Airline Athena Terminal

Security

REQUIRED FOR X.25 X.28 TCP-IP

[email protected]

Further

requests for USERID/PASSWORDS Airline Terminal Security Administrator

PID CONFIGURATIONS

[email protected]

SITA PID CONFIGURATIONS

1.5 Schematic

The following page is a schematic of how a Liaison client connects to the mainframe host in Atlanta.

L ia is o n S c h e m a tic

2.

Preparing for

Liaison

2.1 Liaison Requirements

Liaison will function properly on any 32 Bit Windows Operating system. There are specific settings for multiple Login Users when using Windows XP. Please refer to

Appendix E – Windows XP for detailed instructions.

For XP installations with only one Login there are no changes required as long as the Login user is either an ‘administrator’ or ‘power user’.

It will be necessary to follow Microsoft’s requirements for minimum PC hardware

requirements. Keep in mind that Microsoft has withdrawn support from Windows 95 and Windows 98. Liaison will continue to support users with those operating systems, but keep in mind that future versions of Liaison may preclude the use of the older non-supported Windows versions.

In addition, the Liaison software is delivered on CD-ROM, so at least one PC should have a CD-ROM drive. The other PCs should either have their own CD-ROM, or be able to access a shared CD-ROM. If the PC’s are to be networked, the necessary LAN

Printers

The following printers have been homologated for use with Liaison

ATB Devices Bag Tag

Printers Gate Readers Document Printers Dassault BPR 600/TPR

800 Genicom 201 Dassault 320 OKI 180

Documax A3300 IER 411 IER 607 OKI 320

Genicom ATB 1550xp IER 423 IER 627A TI 810

IER ATB models

457,508,512,557, and 567 IER 508 Unimark 2000 TI 885

Sigma 7200 IER 512C

ASIC

Dassault A640 Dassault

Tahiti

Dassault Tahiti Unimark 6000 Unimark 4000 and Sprite

Fujitsu 9811

Certified

Peripheral Firmware

The following table contains Firmware Versions certified for Liaison Desktop., Muse, and Cute operations.

Liaison Desktop Firmware

Device Last Firmware Version Certified Firmware Version

Dassault 640 DLD1.GAE1.01 DLD1.GAE1.01

Fujitsu 9811 Contact Fujitsu and specify SITA Liaison Desktop IER 411 98.044/10 98.944/10 IER 508 98614 1.01 98614 1.01 IER 508BP 98614 1.00 98614 1.00 IER 517 92708 1.03 92708 1.03 IER 512C ASIC 92934 1.01 92934 1.01 IER 512C AEA BP 930771 1.00 930771 1.00 IER 512C AEA BT 929342 2.00 929342 2.00 IER 557 STANDARD 90385 1.02 90385 1.02 IER 557 TURBO 90479 1.02 90479 1.02 IER 567 96600/2.01 96600/2.01 IER 627A 91709 1.01 91709 1.01

Unimark 2000 Contact Unimark and specify SITA Liaison Desktop Unimark 4000 Contact Unimark and specify SITA Liaison Desktop Unimark 6000 Contact Unimark and specify SITA Liaison Desktop Unimark Sprite Contact Unimark and specify SITA Liaison Desktop

The following tables contain Firmware Versions certified for SITA Cute and Arinc Muse operations.

SITA CUTE Firmware

IER Peripheral Device Last Firmware Version Certified Firmware Version

IER 512C NS 92708 1.03 92708 1.03 IER 512B NS 92643 1.06 92643 1.05 IER 512C ASIC 92915 1.01 92915 1.01 IER 512B ASIC 92903 1.01 92903 1.01 IER 508 98615 1.00 98615 1,00 IER 557 STANDARD 90322 1.02 90322 1.02 IER 557 TURBO 90479 1.02 90479 1.02

IER 567 Not yet certified

ARINC MUSE Firmware

IER Peripheral Device Last Firmware Version Certified Firmware Version

IER 512C ASIC 92901 3.10 92901 3.05

IER 512B NS 92675 1.00 98602 1.00

IER 508 98602 1.00 98614 1.00

IER 557 STANDARD 90387 3.06 90387 3.03

IER 557 TURBO 90437 3.06 90437 3.04

IER 567 Not yet certified

2.2 Communications Considerations

Liaison has been developed to connect to the SITA IS host systems via the SITA

network. It utilizes today's latest protocols, which allow secure, fast, and dynamic service. The SITA BDM or Account Manager can assist in ordering any type of circuit. The following is a listing of protocols available in the Liaison Communications library and an explanation of what must be in place before Liaison can be installed:

TCP/IP

Transmission Control Protocol / Internet Protocol TCP-IP is used over SITA's LANAS or ISNET connectivity. The airline subscriber must have processed a request for this service with SITA. This service includes a SITA installed CISCO router on site or at the local center to enable the connectivity. The airline must use registered IP addresses, which can be obtained though SITA.

This is an asynchronous (dial-up) type of connectivity, available at most of SITA’s worldwide locations. Anyone can obtain the telephone access number, but two layers of security must be satisfied before access to the ATL host is permitted. The airline subscriber must apply to SITA network for a Network User ID (NUI) and Password through their Account

Manager.

X.28

An existing NUI/Password may be utilized. Contact your Account Manager if you do not already have a NUI/Password. Both the

NUI/Password and the access phone numbers for the SITA XPAD are the same for Liaison X.28 access and Sitatext X.28 access.

Dial-up connections always use dynamic PIDs; static PIDs are not allowed over dialup. Any time dynamic PIDs are used, a master dynamic PID must be established. Advise the following information to

Liaison [email protected]

They will contact SYS to request the master dynamic PID to be configured.

• Default City Code • Default Office Number • Default Hard Copy PID • Country Code

In addition, a modem connection must be provided for dial-up access. If you are planning multi-PC access via X.28 on a permanent basis, make sure your local SITA office has sufficient resources to support it.

X.25

This connectivity is applied for through the local SITA representative (Account Manager or BDM), who provides dedicated circuits to the subscriber site. A gateway device is required to "manage" the sessions on site. For X.25 communications, this is accomplished via an Eicon communications gateway PC. Additional Eicon LAN client software is required on each Liaison

workstation to communicate locally with the Eicon gateway. If only one workstation is required at a site, the communications gateway and client PC can be combined in the same PC. In this case, the Eicon LAN client software is not required. Please refer to Appendix D. Eicon Cards and Cables.

ADDITIONAL REQUIREMENTS FOR X.25

Communications Gateway

The X.25 communications requirements are as follows:

OS Windows NT,2000,or XP

Eicon card: Refer to Appendix D. Eicon Cards and Cables.

Your Local Account Manager should be able to advise you further. Eicon

Gateway that extends the WAN capabilities of Microsoft Windows NT, 2000 & XP. By Eiconcard Connections for Windows NT, 2000 & XP is a server-based router taking advantage of the versatility of the Eiconcard, branch offices can meet their needs for Internet and Intranet access, routing and remote access.

Eiconcard Connections for Windows NT, 2000 & XP includes drivers which enable Eiconcards to work in the Windows NT, 2000 & XP environment.

Eicon

Client

Eicon LAN client 32 bit software is required for each workstation connecting via X.25. Note the 16 bit version of the Eicon LAN client will NOT work with Liaison.

Contacts

Eicon components are available from EIS. Contact either your local EIS office, or Julie Cody, Equant New York, at [email protected] or

Telephone 631-244-2509 x240. Pricing must be obtained from EIS.

X.25 communications gateway installation support is available from Eicon Technologies at WWW.Eicon.Com

2.3 Atlanta Athena Terminal Security

When a successful connection is made through the network to the DCP, Athena terminal security then provides another level of security. It allows passage through to an Atlanta host system from the DCP.

ESTABLISHING TERMINAL SECURITY

Athena terminal security, i.e. the “ENTER USER ID/PASSWORD” prompt, must be applied for from [email protected]. They establish a master administrator account for the airline. The master administrator then assigns User ID/Passwords for other airline personnel.

Please do not send Athena terminal security requests to Liaison support. We are not authorized to perform or request terminal security configurations, and

2.4 Atlanta PID Configurations

When a successful connection is made through the network and Athena terminal security, an additional layer of security is provided in the PID configuration, or CONLNK file. They ensure the security and access level allowed for each PID.

MIGRATING EXISTING PIDS

Moving from a P1024C to a X.25 or TCP/IP environment is a completely new environment away from the airline proprietary transports. This impacts the way in which PIDs are configured both in the host system and in SITA's

communications management. This impact is not Liaison specific; any terminal emulation to Atlanta will be impacted in the same way.

Traditionally (i.e. with the P1024C protocol), network routing is assigned to each PID from the concentrator level down to the RID/SID level. With a TCP/IP or X.25 connection, this all changes. A LANAS or ISNET connection uses IP addresses for both the individual workstation and the ATL host. An X.25 connection uses Destination Network Addresses (DNA’s) which are similar to a telephone number. While all existing PIDs may be used with Liaison, they must be reconfigured to accommodate this new environment. Contact SITA/ATLIS

[email protected] to have your PID numbers converted before

installing Liaison.

The COMS: ASCU command will not work on PIDs configured for X.25 or TCP/IP access. There is a new command COMS: TELCON that should be used instead. The format is the same except the word TELCON is substituted for ASCU, i.e.

COMS: TELCON/PID/(PID#).

Once the PID configurations have been adjusted, it is advisable to review each PID and verify whether or not it is configured as PC/PCM.This can be done by the command PDQ:D/(pid #), i.e. PDQ:D/12345. Look at the “Device Type” field. PPCM indicates it is a PC/PCM PID. A sample PDQ:D display follows.

»pdq:d/44682

PDQ STATUS 09SEP/18:45 OFFC:PDK1 ZZ:CSC USER:XS DEVICE TYPE:PPCM

PID H ALT PRI NBR EXP 44682 N 1 0 0

44682 N 2 0 0 44682 N 3 0 0 44682 N 4 0 0 ALL 0

Customers may change the “styp” field in the conlnk, but to change to or from PCPCM a corresponding changes must be made by

REQUESTING NEW PIDS

New users should also contact [email protected] to request PIDs. They will require some additional information, such as PID type (PC/PCM or CRT), TCP/IP address for TCP/IP connections, etc. See the Liaison Web site HTTP://57.250.224.47 to download a Pid request form and detailed Pid information.

Please do not send PID requests to Liaison support; we are not authorized to request PID configurations and sending requests to us only delays the process.

2.5 Atlanta User File Maintenance

AGENT AND OFFICE FILES

For static PIDs, related files, such as AGENT and OFFICE files, should not be impacted. For dynamic PIDs, an agent cannot sign in as user groups 11-16; 17 is the most powerful level allowed. Dynamic PID sign ins must be protected, i.e. must have an account number specified in the agent file.

ZZADDR FILE

For PC/PCM PIDs, the ZZADDR records must be designated as "MSG" for printer traffic, and "CRT" for on-screen traffic. Note the MSG or CRT designation will not show in a UMDF display when initiated from a non-PC/PCM PID. The configuration on the host must match the configuration in PC/PCM.

For example:

1. If the host ZZADDR record shows CRT (>UMDF/ZZADDR/xxx or ZZM:V/xxx),

PC/PCM must have ‘Messages to CRT’ checked. ‘Message to CRT’ is the default setting in Liaison PCPCM Configuration Wizard.

2. If the host ZZADDR record shows MSG (>UMDF/ZZADDR/xxx or ZZM:V/xxx),

PC/PCM must have ‘Message Printer’ checked, and the message printer must be properly configured.

Failure to properly configure in this area will result in a message ‘PID suspension avoided’ each time a ZZ message is received.

Note whether a ZZ address is configured for the CRT, the printer, or there is no ZZ address configured. It is recommended that you always check the

2.6 PC/PCM IMPACT ON SYSTEM PRINT

The configuration for system print handling is managed differently in the Liaison world. Traditionally, all forms of printing are generated from a terminal command, sent to the ATL host, and in response, the print job is sent to the printer PID associated with the terminal PID. All types of dialogue, such as acknowledgements or errors, are

communicated from the printer back to the application in ATL. The printing is executed after several messages are relayed back and forth.

PC/PCM still takes the print messages from the application in ATL, but all in one message to the PC. Once the entire message is received, the PC acknowledges, and the conversation between the PC and ATL is finished. At this point, the PC turns its attention to the printer device attached to it, whether it is for printing tickets, boarding cards, bag tags, or simple system printing. Acknowledgements, errors, end of job indicators, etc., are handled locally between the printer and the PC/PCM program. This greatly reduces the dependency on communications between the host application in ATL and the workstation/printer.

With PC/PCM, all CRT and printer traffic is handled through the same PID. A separate PID number is no longer assigned to printers. It is important to note that the workstation PID number must be designated as a PC/PCM device to enable this feature. Printers may still be shared with PC/PCM. Also note that ZZ message traffic when sent to a PC/PCM PID can either be received by the CRT device (TYPE=CRT) or printed to the attached MSG printer (TYPE=MSG).

AN EXAMPLE

If you had 5 workstations in an area sharing one ticket printer and one message printer, the workstation with the ticket printer and message printer attached would have a PC/PCM PID. The other workstation PIDs would be configured as standard CRT PIDs. The CONLNK ODVN and TKTP fields on the 4 workstations without printers would point to the PC/PCM PID number. The CONLNK of the workstation controlling the printers would have the ODVN and TKTP fields pointing to in itself.

Liaison would only have PC/PCM configured on the workstation controlling the printers. PC/PCM would have at least two (2) boxes checked and configured, Message Printer and Ticket Printer. “Messages to CRT” could also be checked.

An alternate to this example would be to configure all 5 PIDS as PCPCM PIDS. The four PC’s without a printer attached would select only ‘Messages to CRT’ in the PC/PCM configuration wizard.

2.7 Have a Look at the Website

There is plenty of useful information (including documents, like this one) from the

Liaison Support Web Site. Included are details on the communications

environment where

Liaison

operates. You may access by pointing your Internet

Browser to

HTTP://57.250.224.47

and navigate to the Liaison link.

3. Installation and Configuration

3.1 The Possible Sources

Liaison may be installed using the following media:

• Compact Disc (CD)

• Liaison Internet website:

HTTP://57.250.224.47

3.2 Installation – An easy step-by-step process

Before you begin, know the following:

Liaison Registration Key

The content of this key depends upon the applications you are working with, the communication protocols used, and the 2 character airline code. This key is provided by Atlanta with the CD on a 1 page printout. It is 34 characters separated into 5 subsections by dashes (-) Athena terminal security User ID/Password Static PIDs-PID numbers

Ensure they have been properly configured. Dynamic PIDs Ensure the master dynamic PID has been setup IP addresses for

Rendezvous servers

Their order is important. The IP addresses for the production boxes are 57.5.64.250 and 57.5.64.251.

X.28 NUI/password

X.25

OSI NSAP. For PSA, it is 9001031. For PSB, it is 9001181. World Tracer connections currently always are routed through PSA, and thus would use 9001031. This may change in the future.

Please note that it is the AIRLINES responsibility to distribute new versions of Liaison within the airline. Further it is the AIRLINES responsibility to keep SITA advised as to the current number of licensed copies. Please notify the following people depending upon on your region.

SITA Sales Region/ACC

Sales Manager

e-mail Telephone

NEU and ECEU

Chris Leadbeater (LON)

[email protected]

+44 (0)20 8476 4553

NAM and CALA

Bil Ghuman (ATL)

[email protected]

+1 770 850 4570

NACA & AUSPAC

Gil Turner (SYD)

[email protected]

+61 4 2213 3321

EUROMED & MEACSA

Jean-Marc Perreaux

(PAR)

INSTALLATION STEPS

Please note this section explains Liaison installation into a non-CUTE/MUSE environment. If you are a CUTE/MUSE site administrator who is installing Liaison, please refer to SITA CUTE Installations Section 3.5

1. Please shut down all applications currently running on your desktop. This includes the Microsoft Office Shortcut toolbar.

2. Insert the Liaison CD. If Windows is configured to AutoRun CDs, setup will launch automatically when the CD is inserted. Otherwise locate and double click setup.exe on the root directory of the Liaison Installation CD.

3. The notes for the current release of Liaison are shown first.

If this is a new installation, just click Next to continue. If you are upgrading a previous version of Liaison, you may want to peruse the release notes before clicking Next to see if anything is of interest.

4. Carefully select the type of setup you need.

5. The setup process gives you an option to choose a Destination Folder. Click Next > in order to install to the default location

(C:\Program Files\SITA\Liaison).

The Liaison files will then proceed to be copied to the specified location. You may get a message titled "Read Only File Detected" as shown below. If you do, please click Yes to overwrite the file. (KEYBOARD NAVIGATION: TAB TO HIGHLIGHT YES> AND ENTER)

6. The recommended procedure is to install a shortcut on your Windows desktop. The Icon will be written if you click yes on the following prompt.

7. The next step will ask to restart your computer. Please select "Yes, I want to restart my computer now". (KEYBOARD NAVIGATION: TAB TO HIGHLIGHT STATEMENT AND PRESS THE SPACEBAR) before clicking Finish

3.3 Configuration

3.3.1 Starting the Liaison Commander

Before the configuration process can begin, the Liaison commander must be started. From the Windows desktop, you can start Liaison in one of two ways. One is to click on the Start button, then highlight Programs to see the Liaison

program group.

(KEYBOARD NAVIGATION: WITH ALL PROGRAMS MINIMIZED, TAB TO HIGHLIGHT Start AND ENTER.) There will be at least four choices in this menu. Liaison is the one with the Globe icon The second way to start Liaison is to double click the Liaison shortcut on the desktop.

3.3.2 First Time Running Liaison

If this is the first time you are running Liaison, two things will happen. First, you will see a window saying “It does not appear that you have used Liaison before on this computer. Do you wish to set it up now?” You must answer Yes to proceed. Second, you will be asked to enter the Liaison Registration Key. This is a five-part key, with each part separated by dashes. As you enter the key, you must press Tab where the dashes appear in the written key. When you are finished entering the Registration Key, click OK (KEYBOARD NAVIGATION: PRESS ENTER.).

The key is included with the Liaison shipment, or with the email announcing the shipment. It will look similar to the following display. Each enabled option included is checked off and the registration key is at the bottom of the form.

3.3.3 Starting the Configuration Process

After successfully starting Liaison, the Liaison Commander is displayed as shown below.

To add a new session or edit an existing session, click on the Settings button (the Session Configuration Wizard). (KEYBOARD NAVIGATION: F1)

To edit an existing session, you may also right click the session icon and select Configure. A list of 6 choices, described below, will be displayed. Each choice corresponds to a step in the Liaison configuration wizard, and access via this method may be used as a shortcut to the desired configuration item.

Description Liaison configuration wizard step 1 of 6. Used as the initial step to create a new session, add a description for a session, or select an existing session to edit

Terminal Login

Liaison configuration wizard step 2 of 6. Most commonly used to enable and specify the Athena terminal security Userid/password entry. It can also be used to choose to automatically start this session when the Liaison

commander is started, and to enter a unique registration key applicable for this session only.

Application

Liaison configuration wizard step 3 of 6. Used to specify if the session will be used only for expert mode or for both expert mode and GUI access. Another function is to enable the trace log function. A trace log is often required by Atlanta for debugging in case of problems

Colors Liaison configuration wizard step 4 of 6. The foreground _{and background colors are selectable for the session}

Communications

Liaison configuration wizard step 5 of 6. Options for the selection of communications protocol, static or dynamic PID access and enabling PC/PCM. The PC/PCM configuration will be started from this option the if PC/PCM option is selected for this session

PCPCM Wizard This option is a direct link to screen 1 of 5 of the PCPCM _Wizard.

Note

3.3.4 Liaison Configuration Wizard – Step 1 of 6 (Description)

After initiating the session configuration process, the Liaison Configuration Wizard – Step 1 of 6 will appear as illustrated below.

New session name

Type in the name for first session. This name cannot be longer than eight characters. Make the name descriptive, i.e. if using the Checkin or Boarding GUIs, perhaps use CKI or Boarding. If using static PIDs, you may want to use the PID number as the session name

Description

If desired, you can type in a long description for the session name (up to 40 characters) for the session. This description will show as the cursor is positioned over the session icon on the commander

If you want to edit an existing session,

choose one from the list below

If you wish to edit an existing session, instead of adding a new session, click the session name to edit.

The selected session will be displayed in the New session name field.

Cancel Click the Cancel button to exit this window with no changes Back

The Back button is grayed out on step 1 of the Liaison configuration wizard because there is no previous step to which to return

Next Click Next to continue on to step 2 of the Liaison configuration _wizard Finish Click Finish to exit the Liaison configuration wizard, saving _{any changes made (i.e. to the description).}

3.3.5 Liaison Configuration Wizard – Step 2 of 6 (Terminal Login)

The Liaison Configuration Wizard Step 2 of 6 can be displayed in one of two ways: • Click Next > when finished with Step 1 of the Liaison configuration wizard. • Right click the session, then click Configure / Terminal Login.

Automatic Login

Select automatic login for automatic transmission of your Athena Terminal security USERID and PASSWORD. This is not encouraged for obvious security reasons.

Unattended Device

If your PID is defined as a UNAT or unattended device type check that as well. Liaison will periodically verify your connection. If there is no response to the UNAT transaction the re-transmission of your terminal security login will be attempted. This process will continue on a timed basis until the connection is re-established. This unique re-connect feature is not enabled on non-unat sessions. Also keep in mind that only UNAT, limited Gabriel functions, and printing are allowed on UNAT pids.

Session Registration

In certain circumstances more than one Liaison registration key is needed to allow access via Rendezvous to more than one Gabriel partition on the same Liaison installation. If this is the case select the check box and enter the registration key for the specific session you are installing. If not this session will use the default registration key specified when Liaison was first installed. See section 3.3.2

Automatically Start this Session…

Click this button and the Liaison Commander will start this session when it initializes.

Cancel Click the Cancel button to exit this window with no changes

Back The Back button is grayed out on step 1 of the Liaison configuration wizard _{because there is no previous step to which to return} Next Click Next to continue on to step 2 of the Liaison configuration wizard

3.3.6 Liaison Configuration Wizard - Step 3 of 6 (Application)

• Click Next > when finished with Step 2 of the Liaison configuration wizard. (KEYBOARD NAVIGATION: TAB TO HIGHLIGHT NEXT> AND ENTER.)

Liaison Configuration Wizard – Step 3 of 6

Which application would you like this

session to use?

The Liaison Configuration Wizard Step 3 lists all available

Liaison GUI applications. Items that are grayed out are not

available with your registration key. Please note that even if a GUI item is grayed out, you can still access the

application via expert mode (provided your airline is configured for said access).

Special Options

After you choose an application, you will see any extra options that can be selected. For the UTS Terminal Emulation, you may elect to display an extra set of GABRIEL prompts. For the other applications, you may select to startupthe session in "FormMode" (GUI) or "Expert Mode".

Trace logging

Check this option to enable the Liaison trace logging function. This option is very important if you are having problems with printing.

Atlanta will often need to see a trace log to resolve print problems. Once this option is enabled, a record of all printer and CRT traffic will be recorded in the pcpcm log file. Default location is C:\PROGRAM FILES\SITA\LIAISON\PCPCM\COMPUTER NAME. This file will contain traffic from the time the session is started until it is terminated. When sending a trace log file to Atlanta, please be sure the problem you are experiencing is reproduced during the session.

Do not start the session again without recreating the problem, or your log file will be overwritten.

File size limit (Kbytes)

The default value for this entry is 2. This should be

increased; a value of 1400 is recommended. 1400K will fit on a diskette should you need to copy the file to a diskette for transmission to Atlanta, plus this file size should be sufficient to capture any errors that may occur.

Cancel Click the Cancel button to exit the Liaison Configuration Wizard without saving any changes made so far.

Back Click the Back button to return to the Liaison Configuration Wizard Step 2 of 6, Terminal Login.

Next Click the Next button to continue to the Liaison Configuration Wizard Step 4 of 6, Colors.

Finish Click the Finish button to exit Liaison configuration and retain any modification made thus far.

3.3.7 Liaison Configuration Wizard - Step 4 of 6 (Colors)

The Liaison Configuration Wizard Step 4 of 6 can be displayed in one of two ways: • Click Next > when you are finished with Step 3.

(KEYBOARD NAVIGATION: TAB TO HIGHLIGHT NEXT> AND ENTER

• Right click the session, then click Configure / Colors •

This step of the Liaison Configuration Wizard allows you to choose which colors you prefer for the terminal emulation session. Reference the sample text at the bottom left of the screen to help choose your combination of background and foreground colors.

Background color

Click on an item in the Background color list box to select that color as your background color on the terminal emulation screen.

Foreground color

Click on an item in the Foreground color list box to select that color as your foreground color on the terminal emulation screen.

Sample This box shows a sample of the current color combination you have selected.

Cancel Click the Cancel button to exit the Liaison Configuration Wizard without saving any changes.

Back Click the Back button to return to the Liaison Configuration Wizard Step 3 of 6, Application.

Next Click the Next button to continue to the Liaison Configuration Wizard Step 5 of 6, Communications.

Finish Click the Finish button to finish your configuration and save all changes made during this configuration session.

3.3.8 Liaison Configuration Wizard - Step 5 of 6 (Communications)

• Click Next > when you are finished with Step 4. (KEYBOARD NAVIGATION: TAB TO HIGHLIGHT NEXT> AND ENTER.

• Right click the session, then click Configure / Communications.

Number of seconds to wait

before timing out

The default value of 30 seconds is normally sufficient. However, dialup connections may need to have this value increased to 60 or even 90.

Advanced or Communications

During initial session configuration, this button will display as Advanced. When modifying a session, it will display as

Communications. In either case, this is where the most important portion of the Liaison configuration is done. This is where the communications protocol is selected, PID types and numbers are specified, destination addresses are specified, and PC/PCM is configured.

Cancel Click the Cancel button to exit the Liaison Configuration Wizard without saving any of the specified changes.

Back Click the Back button to return to Step 4 of the Liaison Configuration Wizard, color selection.

Next Click the Next button to continue to Step 6 of the Liaison Configuration Wizard, confirmation of your selections.

Finish Click the Finish button to exit the Liaison Configuration Wizard and save all specified changes.

3.3.8.1 Protocol

Selection

After clicking the Advanced or Communications button, you will see a Protocol window and a list of protocol choices, as illustrated below:

Connection Name

This is the session name specified in the Liaison Configuration Wizard Step 1 of 6. It cannot be changed at this point

Type

This is an important configuration item. Verify that your selection is correct. If using DialUp protocol, also reference Appendix D – X.28 Asynchronous Configuration. If you have an X.25 connection to the SITA network (ie: An Eicon Gateway), select X.25 here. If you have a TCP-IP connection to the SITA network (ie: a router is used to connect to LANAS,ISNET, or ICN connection), then select TCP-IP here.

PC/PCM

For static PIDS note that it is important that the selection here matched the PID type on the host. If they do not match, you may see something similar to (PSA:PDQ:IR displayed on your terminal screen every 45 seconds, making it very difficult to work. If you have any printers attached to this session, make sure to check the PC/PCM option. This will enable PC/PCM for the session, and will enable the PC/PCM configuration wizard during session

configuration. (KEYBOARD NAVIGATION: TO CHECK OR UNCHECK THE PC/PCM BOX, TAB TO PC/PCM AND PRESS THE SPACEBAR.) Note: Static PIDs must be

properly configured for PC/PCM and dynamic require proper host and Rendezvous setup

OK Click the OK button to continue to the configuration for the selected protocol. _(K EYBOARD NAVIGATION: TAB TO HIGHLIGHT OK AND ENTER.)

CANCEL Click the Cancel button to cancel protocol configuration and return to the _{Liaison Configuration Wizard Step 5 of 6, communications} After clicking OK when finished selecting a Protocol, the displays will vary, depending on which protocol was selected, and whether or not PC/PCM was selected. Please reference the section on your selected protocol. If PC/PCM was checked, also reference the section on PC/PCM.

3.3.8.2 TCP/IP

Configuration

If the TCP/IP protocol was selected, a window entitled "TCP/IP Properties" appears as illustrated below.

Rendezvous IP Addresses

The production Rendezvous IP addresses are 57.5.64.250 and 57.5.64.251. Reconnect

delay (in seconds)

If the connection to the host is lost, Liaison will try to automatically reconnect. This value is the number of seconds to wait before attempting the reconnection. Some LAN’s are configured such that if the connection goes down, an alternate route will automatically be put into place. This usually takes effect after a set period. Therefore, if the LAN automatically reconnects after 20 seconds, a value of 20-30 should be entered in this field

PID Type Select either Dynamic or Specific (Static). For the latter, you must supply the PID number in the space provided. Enter only the PID number, no P or anything. (For Infoconnect users, a P had to be specified before the number; this is not required in Liaison). Remember that Static PIDs must be properly configured for your airline, and require special configuration to support PC/PCM. If you chose ‘Enable Automatic Sign In’ Step 2 of the Liaison Configuration Wizard, the PID specified here must be able to use the specified sign-in

Note: When configuring Dynamic PIDs, refer to Appendix D – X.28 Asynchronous Configuration Dynamic PID Properties.

OK Click OK when you are finished with the TCP/IP Properties window. (KEYBOARD

NAVIGATION: TAB TO HIGHLIGHT OK AND ENTER.)

Cancel Click Cancel to abort the TCP/IP configuration and return to the Liaison Configuration Wizard Step 5 of 6.

3.3.8.3 X.25

Configuration

If the X.25 configuration option was selected, the following window will display:

OSI NSAP

The OSI NSAP varies depending on the system being accessed:

PSA-9001031 or PSB-9001181. Airlines using only Worldtracer are routed through PSA. Enter the PSA value of 9001031.

Application The default value of ATHENA should be used

PID

You must supply the PID number in the space provided. Enter only the PID number without prefix or suffix. (Note: Infoconnect users were required to insert a P before the number; this is not required in Liaison). Remember that if you are using PC/PCM, the PID must be properly configured to be able to support PC/PCM. If you chose ‘Enable Automatic Sign In’ Step 2 of the Liaison Configuration Wizard, the PID number specified here must be able to use the specified sign-in

OK Click OK when finished entering values in this window to continue with the Liaison configuration

Cancel Click Cancel to abort the X.25 configuration and return to Liaison Configuration Wizard step 5 of 6

3.3.8.4 DialUp Configuration

If the DialUp protocol was selected, a window entitled “DialUp Properties” appears as illustrated below:

DialUp configuration is explained more completely in Appendix D, X.28 Asynchronous Configuration, but the most relevant points are highlighted below.

Dial Number

Enter the telephone number of the local SITA XPAD. The number defaults to the Atlanta number, but a closer (and thus cheaper for access) number should be obtained from local SITA

The Network NUI is obtained from the Airlines Account Manager.

Network NUI

The NUI and Password are issued upon receipt of an X.28 request. The NUI will be 8 characters long. The first 4 characters are

controlled by the Liaison registration key and will appear on this screen automatically. If they appear incorrectly on this screen, you must obtain a modified registration key from

[email protected]

Network Password

This value is obtained along with the NUI. It is used for security purposes. It will display as asterisks (*).

PAD ID (DNA)

The default value of 9001031,PDX28M is appropriate for users connecting to the PSA system. If connecting to PSB, change this value to 9001181,PDX28M

After clicking OK to continue, the following screen will display:

Dynamic PID Properties are also explained more completely in Appendix D, X.28 Asynchronous Configuration. Some of the more relevant points are highlighted below:

Destination

The destination host is entered here. The default is X28PSA for the PSA system. (default)

X28PSB for the PSB system

X28DEV for the development system X28BAG for World Tracer

X28FQT for Fare Quote

X28OFL for PSB development system

Country Code The 2 letter ISO country code of the location originating the session should be entered in this field

City The 3 letter IATA City code indicating the location of the session origination point should be entered in this field

Perform Inline CLR

This is used to enable SDCS on dynamic PIDs. Clicking the Perform Inline CLR will enable the fields in the bottom portion of the window.

These fields are completed in the same manner as the DCS DPID: transaction screen.

3.3.8.5

PC/PCM Configuration Wizard

Generally, all printers connected to a PC for PC/PCM require standard null modem RS232 cabling. If the PC COM port is nine (9)pin, a standard 25 pin to 9 pin adapter may be used.

PC/PCM CONFIGURATION WIZARD – STEP 1 OF 5

After the protocol configuration windows, Liaison configuration will resume along the same path. If the PC/PCM box was checked in the protocol configuration, the PC/PCM Configuration Wizard will start. If the PC/PCM box was unchecked, the Liaison Configuration Wizard – Step 6 of 6 will display to allow confirmation of your selections. The PC/PCM configuration wizard is explained on the following pages.

The items on the

PC/PCM CONFIGURATION WIZARD – STEP 1 OF 5

Three digit IATA carrier code required with ATB

and BTP devices

This option will only appear on CUTE/MUSE

installations. This is the IATA standard 3 digit carrier code.

This number can be obtained by central site personnel from the Bag/Acctng code field on an ACCM display. Update Data Warehouse

Check this option to enable updates to the OEC Data Warehouse. This option will appear grayed out if your registration key does not allow the Data Warehouse option. This option is no longer in production. • Message Printer • Ticket Printer • Automated Ticketing/Boarding • Boarding Pass Printer One • Boarding Pass Printer Two • Bag Tag Printer • Boarding Gate

Reader • OCR • File

• Messages to CRT

Each of these items can be selected as an active device type by clicking on the check box next to the

description. To start configuration check the options that apply to the printing environment you wish to employ using PC/PCM print management.

(KEYBOARD NAVIGATION: TAB TO DESIRED FIELD(S) AND PRESS THE SPACEBAR.)

When you have selected the printer type, click on the applicable printer icon (KEYBOARD NAVIGATION: TAB THEN SPACEBAR).

The “Messages to CRT” field must match the host regarding whether ZZ messages are displayed on the screen or directed to a message printer. If Messages to CRT is not checked, Message Printer must be selected. If it is checked, the session would still need a printer for system prints. This could be either a printer attached to this PC, or a printer on another PC. In either case, the CONLNK ODVN field should point to the appropriate PID.

Refer to Appendix A PC/PCM for a complete description of PC/PCM configuration

Cancel

Click the Cancel button to quit the PC/PCM

Configuration Wizard without saving any changes. You will return to the Liaison Configuration Wizard Step 5 of 6, Communications.

Back The Back button is grayed out on this screen. Next The Next button is grayed out on this screen. Done

Click the Done button when all times have been configured. You will be returned to the Liaison Configuration Wizard Step 5 of 6, Communications.

PC/PCM CONFIGURATION WIZARD – STEP 2 OF 5

In step 2 of the PC/PCM Configuration Wizard, the printer device manufacturer and model is selected. In our example, a standard parallel printer is used. This step is not applicable for CUTE sites; the CUTE Peripheral Manager handles it.

Manufacturer and Physical Device Type Selection

Manufacturers

All manufacturers that have one or more approved printers for the device type will be listed in this box. Note for a Message Printer, any Standard Parallel printer on the Windows Hardware Compatability List SHOULD work. Check the Web Site http://www.microsoft.com/hcl/default.asp to ensure the printer is compatible with your Microsoft Operating System. Printers not on the HCL can not be expected to work. Printers not compatible with NT can act very strange. For instance, the HP 720C is listed as not compatible on the HCL. At one site, local prints appeared to work well, but system prints would appear on the Windows printer queue, then just disappear.

A setting on some printers (HP printers in particular) which has been know to cause problems is the spool settings Raw / EMF setting. Raw should be selected. EMF can cause system prints to misbehave; for example to print every other line.

Printers For each approved manufacturer, all approved devices will be listed in this box.

Cancel Click Cancel to quit the PC/PCM Configuration Wizard without saving any changes. You will return to the Liaison Configuration Wizard step 5 of 6. Back Click the Back button to return to the PC/PCM Configuration Wizard step

1 of 6

Next Click the Next button to continue to PC/PCM Configuration Wizard step 3 of 6.

Done The Done button is grayed out because you cannot skip steps in configuring a device.

PC/PCM CONFIGURATION WIZARD – STEP 3 OF 5 (PARALLEL)

This step will show a different screen, depending the whether a serial or parallel device was selected. The screen for a parallel device is shown first.

Please Select A Parallel Printer

Click on the down arrow on the right side of this box to see a list of all installed Windows printer drivers. Please note that a Liaison terminal emulation session does not have the ability to change the printer. If you wish to print to a different printer, you must change it through the PC/PCM configuration wizard. Also note that all Windows printers installed, including USB devices are selectable.

Cancel

Click the Cancel button to exit the PC/PCM Configuration Wizard without saving any changes. Both changes made in Liaison Configuration Wizard step 5 and in the PC/PCM Configuration Wizard will not be saved. You will return to the Liaison Configuration Wizard Step 5.

Back Click the Back button to return to the PC/PCM Configuration Wizard Step 2 of 5.

Next Click the Next button to continue to the PC/PCM Configuration Wizard Step 4 of 5.

Done The Done button is grayed out at this point because you can not skip steps in configuring a device.

PC/PCM CONFIGURATION WIZARD – STEP 3 OF 5 (SERIAL)

If a serial printer had been selected, selections for baud rate, etc. as seen in the following screen would display. Note, this screen will not appear for CUTE configurations, as the Peripheral Manager handles these configuration items.

Field definitions for the

Field definitions for the PC/PCM CONFIGURATION WIZARD – STEP 3 OF 5 Default To

Select to use either DCS Values or Ticketing Values for printer controls or leave this field blank (default) for no print defaults.

Please select a serial port for this

device

Select a serial port. Choose the port the printer is physically connected to. In this example, we are using a Boarding Pass Printer connected to COM2.

Serial Parameters Tab

The items on this tab (Baud Rate, Data Bits, Stop Bits, Parity, Flow Control) should be set to match the printer. Some printers have the ability to dump their configurations. In other printers, these settings are controlled by the dip switch settings. Refer to the printer manufactures manual to determine these values.

Flow Control

When setting the flow control parameters on the printer, the choices work in pairs, i.e. DTR/DSR, RTS/CTS, or

XON/XOFF. So either none of these should be set to ON, or one (1) pair should be set to ON while all others are OFF. The PC/PCM configuration should always match the printer configuration. Therefore, if you make a change to the printer, PC/PCM must also be changed.

Override STX/ETX Tab

The Start of Text (STX) and End of Text (ETX) values can be overridden. In some older equipment, the STX/ETX values were stored in the firmware and could not be changed. In this case, PC/PCM could be set to match the printer firmware. If nothing is entered, STX of 02 and ETX of 03 are used.

Device Specific Tab

Parameters that do not apply to all devices will appear on this tab. Some examples are “Ack all printer input” and “Send Escape Sequences”.

Cancel

Click Cancel to exit the PC/PCM Configuration Wizard without saving changes. All changes made in the Advanced Communications configuration will also not be retained. Back Click the Back button to return to PC/PCM Configuration

Wizard Step 2.

Next Click the Next button to proceed to Step 4.

Done The Done button is grayed out because you must complete all steps in configuring a device.

PC/PCM CONFIGURATION WIZARD – STEP 4 OF 5

The next step defines the form size. The default setting for a message printer appears below. Change as needed, then click

Next > (KEYBOARD NAVIGATION: TAB TO HIGHLIGHT NEXT > AND ENTER.)

The form position settings normally need not be modified. Some situations require a serial message printer with no form feeds. Heavy volume message printers are often set up as follows in order to reduce the amount of paper used.

• Set the Top Margin to 0 and the Lines per Page to 5.

• Use The Generic/Text Only Printer Driver (included with MS Windows).

• Set the “Paper Source” on the Generic/Text Only Driver set up to ‘Continuous-No Page Break.

• Do not click the ‘form feed after message option’ CHARACTER TRANSLATIONS TAB

Carriage Return /Line Feed options

If you have problems with either printing on the same line multiple times, or double spacing when the printer should singe space, adjust these settings.

Form Feed after message

Leave this box unchecked to not form feed at the end of each message printed unless you are using a laser-jet or ink-jet printer.

ATB devices use a different Step 4 as their print positions are controlled through PECTABs. Step 4 for these devices consists of PECTAB selection and a button that controls at what point CLF code translations occur (within the device or within the PC/PCM program).

Primary Input or select the

primary

Parametric Table (Pectab) identifier for this device. Coordinate with the application to determine the proper Pectab. DCS allows

customization of Pectabs. Ticketing Pectabs will be a standard format.

The following are standard Ticketing Pectab formats. A1 ATB IATA 722C PTAB W/MAG - 1LN FOP-OPATB 155 A2 ATB IATA 722C PTAB W/MAG - 2LN FOP-OPATB 155 B1 ATB IATA 722C PTAB W/MAG - 1LN FOP - ALN 155 B2 ATB IATA 722C PTAB W/MAG - 2LN FOP - ALN 155 D1 ATB ITINERARY/MAILING ADDRESS CARD 96 Y1 ATB IATA 722C PTAB W/O MAG Charge Form 57 Input Only

Additionally input only, Pectabs can be specified in this line. These Pectabs will not automatically be transmitted to the printer when required.

Tran Code Length

The transaction code length is usually 5. CLF Translation

Point

The translation point is usually PC/PCM. Sometimes the printer firmware is sophisticated and will do the Pectab translations, such as an IER 557/607 with CUTE firmware.

Cancel

Click Cancel to exit the PC/PCM Configuration Wizard without saving changes. All changes made in the Advanced

Communications configuration will not be retained.

Back Click the Back button to return to PC/PCM Configuration Wizard Step 3.

Next Click the Next button to continue on to Step 5 of the PC/PCM Configuration Wizard.

Done The Done button is grayed out because you cannot exit the

CUTE sites have an additional tab on Step 4, Logos. They also have a Boarding Gate Reader check box. This is illustrated below:

Airline or class logos to be printed on ATB devices are added here. Before adding a logo, the logo file(s) must have been manually copied to the appropriate location. It is suggested to copy the file to U:\al\userarea, where al specifies the 2-character airline code. Logos are not included on the Liaison distribution CD as they are unique to each airline. To add a logo, do the following:

• Click the Add button.

• Browse to the location where the logos are stored. Highlight the logo you want to add and click Open.

• Enter the logo ID. The logo ID should correspond to the Pectab

location.These values should be given to the installer by SITA Atlanta. • Repeat steps 1-3 for each logo. After all logos have been added, click

PC/PCM CONFIGURATION WIZARD – STEP 5 OF 5

The final step is a review of the settings selected for the PC/PCM printer. Click Done if the settings are correct. (KEYBOARD NAVIGATION: TAB TO DONE AND ENTER.)

If multiple devices are to be configured, you may click the "Configure Another Device" button, which will take you back to Step 1 for another device.

3.3.9 Liaison

Configuration Wizard Step 6 of 6

You should now be in the Liaison Configuration Wizard at the sixth and final Step. Please review the options that you have chosen before clicking or highlighting Finish.

Click Finish to create a new button on your Liaison Commander toolbar. (KEYBOARD NAVIGATION: TAB TO HIGHLIGHT FINISH AND ENTER.)

3.4 Adding a Shortcut on the Windows Desktop

• During the installation process, a query appears asking if a shortcut on the Windows desktop is desired.

• If "Yes" is selected, an icon will appear in the desktop.

• If "No" is selected, it is still possible to go back to the desktop and add this icon per normal Win95/WinNT procedures.

• Note that during an upgrade, if “No” is selected, any existing icon will be removed from the desktop.

3.5 SITA CUTE Installations

Installation at CUTE-NT sites requires some administrative steps before and after the Liaison installation. They are outlined in brief below. Refer to the CUTE Policies and Procedures document for further information.

Prepare for installation

• Make the user a member of the administrator's group. • In the system policy editor set the user policy to the

default-admin policy.

• Remove the mandatory profile by renaming NTUSER.MAN to NTUSER.DAT.

Install and configure

Liaison:

• Log in to the server as the user and run the installation on the server.

• Install Liaison by running setup.exe from the Liaison CD, if the CD does not autorun.

• Add /m /ial, where al is the 2 letter airline code, as a command line parameter for the Liaison executable. • Configure Liaison.

• Remove /m as a command line parameter for the Liaison executable.

• Test Thoroughly Revert to

original configuration

• Reinstate the mandatory profile by renaming NTUSER.DAT to NTUSER.MAN.

• Set the user's policy to the default user's profile. • Remove the administrator's group from the user's

account.

The Liaison installation is explained step by step below:

Follow the steps outlined above under “Prepare for installation” above. Login as the user.

Please shut down all applications currently running on your Win95/WinNT desktop. This includes the Microsoft Office Shortcut toolbar.

Locate setup.exe on the root directory of the Liaison Installation CD. If Win95/WinNT is configured to AutoRun CDs, setup will launch automatically.

The notes for the current release of Liaison are shown first.

If this is a new installation, click Next to continue. If you are upgrading a previous version of Liaison, you may want to peruse the release notes before clicking Next to see if anything is of interest. (KEYBOARD NAVIGATION: PRESS ENTER.)

CUTE Workstation Installation

Click Next after selecting CUTE/NT for a second screen with specific CUTE instructions:

The setup process gives you an option to choose a Destination Folder.

Simply click Next > in order to install to the default location, U:\(user)\te\5.1.

(KEYBOARD NAVIGATION: TAB TO HIGHLIGHT NEXT> AND ENTER) Note this CUTE software

is installed to the airlines directory on drive U, whereas the default location for a non-CUTE install is the C:\PROGRAM FILES\SITA\LIAISON directory.

You may get a message titled "Read Only File Detected" as shown below. If you do, please click Yes to overwrite the file.

(KEYBOARD NAVIGATION: TAB TO HIGHLIGHT YES> AND ENTER)

• Add /m /ial, where al is the 2 letter airline code, as a command line parameter for the Liaison executable.

• Configure Liaison as described in section 3.3 Configuration

• Test Liaison. Once everything is working properly, continue with the remaining steps.

• Remove /m as a command line parameter for the Liaison executable. • Revert to original configuration, again referring to CUTE documentation for

details:

Reinstate the mandatory profiles by renaming NTUSER.DAT to NTUSER.MAN. Set the user's policy to the default user's profile.

Remove the administrator's group from the user's account.

For server installation reference the ‘Group Management Tools’ document available on the Liaison Web Site HTTP://57.250.224.47. It describes the methodology for server installs.

4. Operation

4.1 Invoking the Program

The easiest way to start Liaison is from the desktop shortcut. Simply double-click on the icon and the Liaison "splash-screen" is activated. This is a multi-media introduction, showing a globe surrounded by an expanding frame. Concurrently, a crescendo of string music plays in the background. This takes approximately 7-10 seconds, at which time the Liaison Commander appears. Liaison is now ready to start the sessions of choice.

The splash screen can be deactivated/reactivated by right clicking on the Settings button on the Liaison Commander, then select "Configuration Toolbar".

Once the "Configure Toolbar" is selected, the following screen is displayed. The 'Show opening movie' can then be set or unset as desired.