SWIFTAlliance Workstation 6.0 - Installation and ... · Welcome to the SWIFTAlliance Workstation Installation and Administration Guide. ... 4.1 Problems with Workstation/Server Connectivity

SWIFTAlliance Workstation 6.0

Installation and Administration GuideThis guide is intended for the person responsible for installing and administering SWIFTAlliance Workstation. Priorknowledge of using a Windows application is assumed in this guide.

2 January 2007

SWIFTNet Interfaces

Legal Notices

Copyright

Copyright © S.W.I.F.T. SCRL ("SWIFT"), avenue Adèle 1, B-1310 La Hulpe, Belgium, or its licensors, 2007.All rights reserved.

You may copy this publication within your organisation. Any such copy must include these legal notices.

Confidentiality

This publication may contain SWIFT or third-party confidential information. Do not disclose this publicationoutside your organisation without the prior written consent of SWIFT.

Disclaimer

SWIFT supplies this publication for information purposes only. The information in this publication may changefrom time to time. You must always refer to the latest available version.

Translations

The English version of SWIFT documentation is the only official version.

Trademarks

SWIFT, S.W.I.F.T., the SWIFT logo, Sibos, SWIFTNet, SWIFTAlliance, SWIFTStandards, SWIFTReady, andAccord are trademarks of S.W.I.F.T. SCRL. Other SWIFT-derived service and product names, includingSWIFTSolutions, SWIFTWatch, and SWIFTSupport are tradenames of S.W.I.F.T. SCRL. SWIFT is the tradingname of S.W.I.F.T. SCRL. Other product or company names in this publication are tradenames, trademarks,or registered trademarks of their respective owners.


2 Installation and Administration Guide

PrefaceWelcome

Welcome to the SWIFTAlliance Workstation Installation and Administration Guide.

About SWIFTAlliance Workstation

SWIFTAlliance Workstation is a simple, cost-effective way to send and receive messages overthe SWIFT network (or telex network, if licensed) using a PC. Computers installed withSWIFTAlliance Workstation can connect to any SWIFTAlliance server running under UNIX orWindows 2003.

About this guide

This guide is intended for the person responsible for installing and administering SWIFTAllianceWorkstation. Prior knowledge of using a Windows application is assumed in this guide.

This guide is structured as follows:

• "Introduction" details the requirements that must be met in order to install SWIFTAllianceWorkstation.

• "Installing SWIFTAlliance Workstation" describes the installation and product upgrade steps.

• "Administration Tasks" describes how to update and configure SWIFTAlliance Workstation.

• "Troubleshooting" helps to resolve initial problems with SWIFTAlliance Workstation setup andusage.

Conventions used in this guide

Before you start using SWIFTAlliance documentation, it is important that you are familiar with thefollowing notational conventions:

• Menu names and field names within windows are printed in bold type, for example, the Filemenu

• Window names are printed in bold type and begin with uppercase letters, for example, theAccess Control window

• Source code is printed in Courier font

• The word "select" means that you select an item in a list or execute a command

• The word "click" means that you position the cursor on an item and press the left mouse button

• Reference to titles of other manuals appear in italics

Preface

2 January 2007 3



Table of Contents

1 Introduction ....................................................................................................................................................... 7

1.1 Preliminary Checks ................................................................................................................................... 7

1.1.1 System Requirements for SWIFTAlliance Workstation ..................................................... 7

1.1.2 Testing TCP/IP Connectivity With the Server Host ........................................................... 7

1.1.3 Checking Hardware Requirements ...................................................................................... 8

1.2 Windows Group and User Accounts .................................................................................................... 10

1.3 Windows Security Enhancement for SWIFTAlliance Workstation .................................................. 10

1.3.1 File Permissions .................................................................................................................... 11

1.3.2 Registry Permissions ............................................................................................................ 13

2 Installing SWIFTAlliance Workstation ................................................................................................. 17

2.1 Installing Workstation for the First Time .............................................................................................. 17

2.2 Installing Workstation and Replacing an Existing Version ................................................................ 24

2.3 Installing Workstation and Retaining a Previous Version ................................................................. 27

3 Administration Tasks .................................................................................................................................. 33

3.1 Installation Application Window ............................................................................................................ 33

3.2 SWIFTAlliance Control ........................................................................................................................... 33

3.2.1 Main SWIFTAlliance Control Window ................................................................................ 34

3.2.2 TCP Configuration on the SWIFTAlliance Workstation .................................................. 34

3.2.3 Adding or Modifying an Instance ........................................................................................ 35

3.2.4 Activating an Instance .......................................................................................................... 37

3.2.5 Removing an Instance .......................................................................................................... 37

3.2.6 Displaying the Active Instance on the Sign-on Window .................................................. 38

3.2.7 Adding a Server to the "Hosts" File .................................................................................... 38

3.3 Patches ..................................................................................................................................................... 39

3.3.1 Patch/Upgrade Program ...................................................................................................... 39

3.3.2 Installing Patches .................................................................................................................. 41

3.3.3 Removing Patches ................................................................................................................ 41

3.4 Version Info .............................................................................................................................................. 42

3.5 Report ........................................................................................................................................................ 44

3.6 Command Prompt ................................................................................................................................... 44

3.7 Selecting an Earlier Version of Workstation ........................................................................................ 45

3.8 Disabling Microsoft Internet Information Server (IIS) ........................................................................ 45

3.9 Restarting Microsoft Internet Information Server (IIS) ....................................................................... 46

3.10 Removing SWIFTAlliance Workstation ................................................................................................ 47

3.10.1 Removing a Workstation ...................................................................................................... 47

3.10.2 Removing Previous Versions of SWIFTAlliance Workstation ........................................ 47

4 Troubleshooting ............................................................................................................................................ 49

4.1 Problems with Workstation/Server Connectivity ................................................................................ 49

4.2 Problems Logging In When First Using SWIFTAlliance .................................................................... 50

Table of Contents

2 January 2007 5

4.3 Printing Problems on Windows ............................................................................................................. 51



1 Introduction

1.1 Preliminary Checks

1.1.1 System Requirements for SWIFTAlliance Workstation

Overview

The following table describes the system requirements for SWIFTAlliance Workstation:

Category Requirement

Hardware Intel Pentium III or higher processor.

Minimum 17" colour monitor with SVGA resolution (at least1024 x 768 pixels).

A hard disk with a partition of 100 MB (NTFS recommended) offree space (either locally or on a networked file server) tocontain SWIFTAlliance Workstation.

Local area network A LAN adapter (Ethernet or Token Ring) to enable TCP/IPprotocol.

Peripherals (local or network) A CD drive.

3.5 inch diskette drive.

Printer.

Operating system Windows XP Professional.

Note: For details of Service Pack levels, please see the releaseletter of the latest patch.

SWIFT Message Standards contextsensitive Field Help

For the SWIFT Message Standards Field Help in the MessageCreation, or Message Modification applications, and so on. Tofunction (invoked by pressing F1 function key in a messagefield), Microsoft Internet Explorer must be installed.

Paging Space For Paging Space, use Microsoft guidelines (1.5 times the RAMof your system).

System RAM for SWIFTAlliance Workstation

Operating System Minimum Memory Size (MB) Advised Memory Size (MB)

Windows XP Professional 128 192

Minimum Disk Space for SWIFTAlliance Workstation

Minimum Software Disk Space(MB)

Minimum Database Disk Space(MB)

Advised Database Disk Space(MB)

250 not applicable not applicable

1.1.2 Testing TCP/IP Connectivity With the Server Host

Introduction

Ensure that you have TCP/IP connectivity between the workstation and the computer where theSWIFTAlliance servers are installed.

Introduction

2 January 2007 7

Note If DNS is enabled on your network, TCP/IP connectivity is automatically checked.

To test the connection:

1. Start a Command Prompt window. (To start a Command Prompt window, click Start andthen select Run. In the Run dialog box, type cmd and click OK ).

2. Type

ping <hostname>where <hostname> is the name of the server component.

3. If the TCP/IP connection is working correctly, a response like the following is shown:

Pinging <hostname> [IP Address] with 32 bytes of data Reply from[hostname IP Address] .....

4. If the response fails, contact your Windows system administrator.

1.1.3 Checking Hardware Requirements

Introduction

The Setup program checks for the minimum requirements (see "System Requirements forSWIFTAlliance Workstation" on page 7). Before you start installing SWIFTAlliance Workstation,you can also run a program to check that the machine you are installing on meets the minimumrequirements. If any problems are detected, you must resolve them before you can installWorkstation software.

Note SWIFTAlliance Workstation has been qualified on Windows XP Professional in"single user mode".

To configure this mode:

1. Log on as Administrator

2. Select Start/Control Panel/User Accounts and Change the way users log onor off

3. Clear Use the Welcome screen

4. Click Apply Options .

To check requirements:

1. Log on to Windows as Administrator or as another Windows user that is a member of the localadministrator group.

2. Insert the SWIFTAlliance Access/Entry/RMA/Workstation release CD into the CD drive. If thecomputer you are installing SWIFTAlliance Workstation on does not have a CD drive, you canconnect to one over the network. To do this, select Map Network Drive from the Toolsdirectory of Windows Explorer. Confirm beforehand that the target drive on the host machineis set up for sharing.

3. Click Start and Run .



4. Type the following command:

<drive>:\win32\checkhw WORKSTATIONwhere <drive> is the appropriate drive name, either locally or on the network.

An example is shown here:

Note Please note that WORKSTATION must be typed in capital letters.

5. After a few moments, a window appears with the results:

If the message Not OK to install appears, take the corrective action indicated.

A red check mark appears to indicate what failed. For example, if there is a red check markbeside Running as Administrator, it means that you are not signed on with rights as anAdministrator. You must sign off and then sign on as a different Windows user with theappropriate rights.

If there is a red check mark beside TCP/IP Software Installed, ensure that there is a TCP/IP connection between the computer where you want to install SWIFTAlliance Workstationand the SWIFTAlliance server.

Close the window to terminate the program.

Introduction

2 January 2007 9

Note Unless stated otherwise, you cannot install SWIFTAlliance Workstation until allthe checks are passed.

1.2 Windows Group and User AccountsDescription

The SWIFTAlliance Workstation software provides the option during installation to allow theconfiguration of group and user accounts for the Windows operating system. If this option ischosen, two groups are created, and each group has one user. The groups are AllianceAdministrators and Alliance Users. The users are AllAdm and AllUsr. Both users get the Windowsright to log on locally to the PC where SWIFTAlliance is installed. Furthermore, AllAdm is a memberof the Windows administrators group.

Note If group or user accounts already exist with these names, they are not updated duringinstallation.

When someone logs on to SWIFTAlliance Workstation using AllAdm as the user name, theSWIFTAlliance control window appears. When logging on with AllUsr, the Access Controlapplication starts automatically after successful entry of operator name and password.

Further maintenance of these accounts is the responsibility of the Windows administrator. Forexample, you can configure a screen saver to automatically lock a workstation, restrict logon hours,keep track of recently used passwords, and so on.

1.3 Windows Security Enhancement forSWIFTAlliance Workstation

Introduction

The overall system security is the responsibility of the system owner. The actual installation of theSWIFTAlliance software does not modify the security settings of the Windows system. TheSWIFTAlliance software provides its own internal protection mechanisms. This is in the form ofdetection and reporting of any system changes or tampering that can result in an unusable system.

To enhance security further, the users and user groups created by the SWIFTAlliance softwareduring installation can be set up for exclusive use of the SWIFTAlliance software. This preventsuse by users that are not part of the Alliance user groups. This can be achieved by modifying thefile and registry permission as described in the following procedures.

The SWIFTAlliance installation procedure creates two users and two groups on the local machine:

• Users: AllAdm and AllUsr.

AllAdm belongs to the Alliance Administrators and the Local Administrators groups and AllUsrbelongs to the Alliance Users group.

• Groups: Alliance Administrators and Alliance Users.

When AllAdm is used to log on to Windows, the SWIFTAlliance Control application is automaticallystarted. When AllUsr is used to log on to Windows, the access control application is automaticallystarted. The local administrator can add more users to the Alliance Users group, thus allowingmultiple users to access and run the SWIFTAlliance Workstation. Note that in this section, AllUsrcan represent any user that is a member of the Alliance Users group.



The following procedure disallows the use of the SWIFTAlliance software by any other user thanAllAdm or AllUsr. Also, AllAdm is the only Windows user that is able to install/deinstall patches ordeinstall the SWIFTAlliance software. Modification or deletion of elements in the SWIFTAlliancerelease-tree or registry by another user is prevented.

1.3.1 File Permissions

To change the file permissions:

1. Log on as Alliance Administrator AllAdm, on your machine.

This must be the Alliance Administrator created during installation of the SWIFTAlliancesoftware (the default is AllAdm).

2. Stop the SWIFTAlliance Control application.

3. Using Windows Explorer, move to the top level of your installation directory, (for example\Win32app\SWIFT\Alliance\Workstation) and right-click on directory-file (forexample \Workstation).

4. From the drop-down menu, select Properties and in the window that appears select theSecurity tab. Click Advanced and in the window that appears select the Owner tab:

Select AllAdm as owner of the directory-file, ensure Replace owner on subcontainers andobjects is selected and then click OK to carry out the operation.

5. The Properties Window for the directory is now displayed:

Introduction

2 January 2007 11

6. Click Advanced and clear Inherit from parent the permission entries that apply to childobjects. Include these with entries explicitly defined here. Then click OK .

7. Click Remove in the Security dialog box. Click OK in the Advanced Security Settings dialogbox. Confirm the changes when prompted by selecting Yes.

8. In the Workstation Properties dialog box, add user AllAdm and group Alliance UsersSecurity tab. Click Add and then select Alliance Administrator (AllAdm) and then AllianceUsers.



For Alliance Administrator (AllAdm) check Full Control, and for Alliance Users, check Read& Execute, List Folder Contents, and Read.

1.3.2 Registry Permissions

Introduction

Using the regedt32 program, change the security on the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\S.W.I.F.T.\SWIFTAlliance\6.0.0

To change the registry permissions:

1. Log on as Alliance Administrator AllAdm, on your computer.

Note This must be the Alliance Administrator created during installation of theSWIFTAlliance software. The default is AllAdm.

2. Stop the SWIFTAlliance Control application.

3. From the Windows Start menu select Run and then type in the program name:

regedt32Then click OK .

4. The Registry Editor window appears:

5. Select the registry key for SWIFTAlliance Release 6.0.0 (HKEY_LOCAL_MACHINE\SOFTWARE\S.W.I.F.T.\SWIFTAlliance\6.0.0):

6. Change the owner to AllAdm by clicking (using the right mouse button) the 6.0.0 key andselecting Permissions from the menu.

Introduction

2 January 2007 13

In the window that appears click Advanced . Finally, select the Owner tab:

Select AllAdm as owner of the registry key. Ensure Replace owner on subcontainers andobjects is selected and then click OK to carry out the operation.

7. The Permissions window Security tab for the directory is now displayed:

8. Click Advanced and clear Inherit from parent the permission entries that apply to childobjects. Include these with entries explicitly defined here.



9. Click Remove .

Click OK in the Advanced Security Settings window. Confirm the changes when promptedby clicking Yes .

10. Next add user AllAdm, SYSTEM, and group Alliance Users in the Permissions windowSecurity tab.

Click Add and then select Alliance Administrator (AllAdm).

Repeat this step to add SYSTEM and group Alliance User.

11. Next check the permissions. They must be:

Alliance Administration(AllAdm) Full Control and Read

Alliance Users Read

SYSTEM Full Control and Read

12. Repeat the procedure for the Alliance Users Registry subkey Operator Settingspermissions:

Select the registry subkey and set the permissions of Alliance Users to "Full Control" asdescribed earlier.

13. Log on as AllUsr.

14. Close the sign-on window and take ownership of the operator settings key using the proceduredescribed earlier.

Introduction

2 January 2007 15



2 Installing SWIFTAlliance WorkstationIntroduction

The procedure to follow for installing Workstation 6.0.0 depends on whether you already haveWorkstation installed or not.

If you already have Workstation 5.5 or 5.9 installed on a machine:

• you can remove 5.5 or 5.9 and then install 6.0.0

• you can have 5.5, or 5.9, and 6.0.0 available on the same machine (it may be useful for testingpurposes).

The sequence of tasks in installation varies somewhat, depending on which approach you choose.Within this section, there are steps to follow for each installation scenario.

2.1 Installing Workstation for the First TimeIntroduction

Follow these instructions only if a previous version of Workstation is not installed.

If an earlier version of SWIFTAlliance Workstation is installed, remove it before continuing.

Procedure


2. Ensure that the correct Service Pack for Windows is installed. See the Release Letter fordetails. To find out which service pack is installed use the winver command. Open aCommand Prompt window and type:

winverThe dialog box that appears shows various information about the Windows operating systemincluding the service pack version.


4. Click Start , select Run and then type the following:

<CD drive>:\win32\setupWhere <CD drive> is the drive letter of the CD.

5. The Setup program runs and the Welcome window is displayed:

Installing SWIFTAlliance Workstation

2 January 2007 17

Click Next .

6. The License Agreement window is displayed.

Read the License Agreement and then click the appropriate button. If you selectAcknowledged and agreed as above, click Next to continue with the installation.

7. The System Date/Time check window is displayed:



If the actual date and time at your location are not the same as the system date and timedisplayed, click Cancel and adjust the settings on your machine before restarting theinstallation. Otherwise click Next to continue.

8. The Setup Options window is displayed:

9. Select SWIFTAlliance Workstation. The Setup program checks that the computer meetsminimum requirements.

The installation Check Hardware/Software window appears:

• If a Stop sign appears against the check indicating that your computer has failed. Youcannot proceed with the installation of SWIFTAlliance until you have resolved the problem.

• If the check program discovers potential problems, they are signalled using a red checkmark. You can proceed with the installation but you should fix the problems before actuallyrunning SWIFTAlliance.

• If a GO sign appears, your computer meets the minimum requirements and you canproceed with the installation.

Close the window to continue.

10. The following screen is displayed.


2 January 2007 19

If you do not want to set up user accounts now, select Do not create Alliance accounts andgo to step 15. Otherwise, select Create Alliance accounts and the following screen isdisplayed.

This exercise creates two user groups and each group has one user. The groups are AllianceAdministrators and Alliance Users. The users are AllAdm and AllUsr. Both get the right to logon locally to the PC where SWIFTAlliance is installed. Furthermore, AllAdm is a member ofthe administrators group.

Enter the password you want to use for the AllUsr and re-enter it for confirmation. Enter thepassword you want to use for the AllAdm and re-enter it for confirmation. Click Back if youwant to return to the previous window. Click Next to continue to the next step.

11. The destination folder is then displayed where the SWIFTAlliance Workstation software is tobe installed. By default the installation program displays the directory:

<Drive letter>:\Win32App\SWIFT\Alliance\You can change the directory using the browse button. If this directory does not exist, you areprompted to allow the install program to create it automatically. The new directory selectionis shown in the destination folder window.

Click Next to confirm your directory selection.

Note Software cannot be installed in the root directory.

12. Select a program folder name. The default is SWIFTAlliance Workstation.

Click Next and a summary of your current settings is displayed. If they are correct, clickNext . If they are not, click Back and change them. Click OK .

13. The installation begins and the installation progress indicator appears.

14. After a few minutes the SWIFTAlliance Control window appears.



You must specify the Primary Instance to which the SWIFTAlliance Workstation softwarecan connect. Optionally, you can also specify a Fallback Instance. In each case define theserver, server's IP address and port number, instance name, and port number. Some of thesefields are completed automatically depending on your configuration.

The window fields are described here:

Field Description

Primary Instance Identifies the details of the primary SWIFTAllianceAccess or Entry server connection.

Fallback Instance Identifies the details of the secondarySWIFTAlliance Access or Entry serverconnection.

Server The host name of the SWIFTAlliance Access orEntry system.

IP address The IP address of the SWIFTAlliance (Access orEntry) system.

The field is only editable if your local systemcannot resolve the host name of theSWIFTAlliance Access or Entry system. Forexample, through the local hosts file or throughDNS.

Boot Port The number of the port used by the "swa_boot"process for the SWIFTAlliance Access or Entryserver to which this instance is to connect.

This field defaults to 48009 and is only editable ifSWIFTAlliance Workstation cannot contact theswa_boot process. For example, if swa_boot isnot running, or is running on another port.


2 January 2007 21

Field Description

Instance name The name of the SWIFTAlliance Access or Entryinstance on the SWIFTAlliance Access or Entrysystem.

Server Port The port number used by the main server of thespecified SWIFTAlliance Access or Entryinstance on the SWIFTAlliance Access or Entrysystem.

This field is only editable if SWIFTAllianceWorkstation cannot contact the swa_boot processon the SWIFTAlliance Access or Entry system.

Release The release of the SWIFTAlliance Access or Entryinstance.

Server OS The Operating System installed on yourcomputer.

This field is only editable if SWIFTAllianceWorkstation cannot contact the swa_boot processon the SWIFTAlliance Access or Entry system.

Software Path The directory in which SWIFTAlliance Access orEntry is installed on your local system.

This field is not editable.

15. In the Server field, select the server you want to connect SWIFTAlliance Workstation to.Display a list of available servers by clicking the down arrow. Remember that Workstation canconnect to either UNIX or Windows based servers.

If the server does not appear in the drop-down list, this is because it is not defined in yourhosts file.

Adding the server name to the host file is only required if the server name resolution is doneusing this file. If DNS is enabled on your network, simply type the name of the server machineand press <Tab>.

Note Make sure that the server name you select is not an alias name for the host.Otherwise, there can be problems when using the Message Exchangeapplication.

16. If the server that you want to connect to is not in the list, click Add to display this window:

Enter the Server name and it's IP address. If you do not know what to enter for these values,continue as follows:

• Go to the server.

• Type the command hostname

• Copy the server name that appears.

To find the IP address on UNIX servers:

• AIX, type:



ping <hostname>

• Solaris, type:

ping -s <hostname>Copy the TCP/IP address that appears. The IP address is listed. Press Ctrl + C to stop theping process.

To find the IP address on Windows servers, type:

• ping <hostname>Copy the TCP/IP address that appears. The IP address is listed. Press Ctrl + C to stop theping process.

17. After you have supplied values for server name and IP address, click OK to add the serverto your hosts file. A backup of the hosts file is created before the modification is made.

18. In the Instance Name field, select an instance. More than one instance may be available.When only a single instance is available, the name of this instance appears automatically.

19. Select either the Primary or Fallback connection to be used by clicking Active Instance inthe appropriate tab.

20. Click OK to accept the values that you entered in the SWIFTAlliance Control dialog box.

21. The Setup program adds Windows user groups and user accounts, and creates short-cuts inthe program folder.

22. After a while, the following window is displayed:

Installation is now complete. Click Yes, I want to restart my computer now and then clickFinish .

23. After restarting, log on to Windows locally with the user accounts AllAdm and AllUsr. In theLogon dialog box select options and in the Log on to (domain) field, select the name of thePC (this is the local machine). Change the passwords. Inform the person that will be usingSWIFTAlliance Workstation which user account and password to use when logging on.

Note The rest of this section concerns replacing an existing version on the same machine.If a previous version is not installed, please continue with the next section.


2 January 2007 23

2.2 Installing Workstation and Replacing an ExistingVersion

Introduction

Follow these instructions if Workstation 5.5 or 5.9 is already installed and you want to overwrite itwith Workstation 6.0.0 software.

This will install 6.0.0 in the same folder as 5.5, or 5.9, and replace the 5.5 or 5.9 software thatexists.

Procedure








Click Next .





7. The System Date/Time check window is displayed.

If the actual date and time at your location are not the same as the system date and timedisplayed, then click Cancel and adjust the settings on your machine before restarting theinstallation. Otherwise click Next to continue.



2 January 2007 25

Select SWIFTAlliance Workstation. The Setup program checks that the computer meetsminimum requirements.






9. The destination folder shows where the SWIFTAlliance Workstation software is to be installed.

If the default directory name is not the directory where Workstation 5.5 or 5.9 is currentlyinstalled, click Browse... to locate the appropriate directory.


10. The Setup program recognises that Workstation 5.5 or 5.9 exists in the directory and displaysthe following dialog box:



Select No, I want to overwrite the Workstation 5.5 (or 5.9) software and click Next .

11. The Select Program Folder dialog box appears, showing the name of the program folderwhere Workstation 6.0.0 is to be installed.

If you want to keep the Workstation 5.5 or 5.9 software, see "Installing Workstation andRetaining a Previous Version" on page 27 and follow the instructions there.

Click Next .

12. Select a program folder name. The default is SWIFTAlliance Workstation.


13. A summary of your selections appears:

Review the settings displayed. If they are correct, click Next and continue with the next step.If they are not correct, click Back and change them. Alternately, you can click Cancel at thispoint, which displays a window where you can stop the installation.


15. The Setup program adds Windows user groups and user accounts, and creates short-cuts inthe program folder. After a while, the following window is displayed:

Installation is now complete. Select Yes, I want to restart my computer now and then clickFinish .


2.3 Installing Workstation and Retaining a PreviousVersion

Introduction

Follow these instructions if Workstation 5.5 or 5.9 is already installed and you want to install 6.0.0in a different folder on the same machine


2 January 2007 27

Using this approach, the Setup program does not prompt you to overwrite Workstation 5.5 or 5.9software.

Procedure




3. Using Windows Explorer, define the directory where you want to install the SWIFTAllianceWorkstation 6.0.0 software.





Click Next .





8. The System Date/Time check window is displayed.

If the actual date and time at your location are not the same as the system date and timedisplayed, then click Cancel and adjust the settings on your machine before restarting theinstallation. Otherwise click Next to continue.



2 January 2007 29

Select SWIFTAlliance Workstation. The Setup program checks that the computer meetsminimum requirements.






10. The destination folder is next displayed where the SWIFTAlliance Workstation software is tobe installed.

Click Browse... to select the appropriate directory, then click OK .


Click OK .

11. The Ask User Destination Path dialog box shows the directory where the SWIFTAllianceWorkstation software is to be installed.

Click Next .

12. The Select Program Folder dialog box appears:

Select a program folder name. The default is SWIFTAlliance Workstation.


13. A summary of your selections appears:

Review the settings displayed. If they are correct, click Next and continue with the next step.If they are not correct, click Back and change them. Alternately, you can click Cancel at thispoint, which displays a window where you can stop the installation.


After a while, a window appears where you select WS 6.0.0. The software path is updated.



Click OK .

15. The Setup program adds Windows user groups and user accounts, and creates shortcuts inthe program folder.

After a while, the following window is displayed:

Installation is now complete. Select Yes, I want to restart my computer now and then clickFinish .



2 January 2007 31



3 Administration Tasks

3.1 Installation Application WindowDescription

Use the Installation application to update and configure SWIFTAlliance.

Example

Icon descriptions

SWIFTAlliance Control

Enables you to change the server and instance you are connected to.

Uninstall SWIFTAlliance

Removes SWIFTAlliance from your computer.

Patch/Upgrade

Used to install or remove SWIFTAlliance patches from your computer.

Version Info

Shows which versions of the SWIFTAlliance executable files are installed on your computer andto check that they have not been tampered with.

Report

Generates a system status report.

Command Prompt

Used to run SWIFTAlliance commands.

3.2 SWIFTAlliance ControlIntroduction

The SWIFTAlliance Control application allows you to set up and control access to theSWIFTAlliance Server Instances. For a SWIFTAlliance Workstation on a SWIFTAlliance Serveryou normally have only the "Primary" and "Fallback" Instances that you set up during installation.For a stand-alone Workstation installation you can set up as many SWIFTAlliance Access or EntryServer instances as you require for the different connections you need.

Administration Tasks

2 January 2007 33

To do this you must create an "Instance Configuration" on the SWIFTAlliance Control applicationfor each SWIFTAlliance Server instance that you intend to connect to. Each Instance Configurationsetup in this way is listed on the main SWIFTAlliance Control window.

3.2.1 Main SWIFTAlliance Control Window

Description

This window is used to create an "Instance Configuration" on the SWIFTAlliance Controlapplication for each SWIFTAlliance Server instance that you intend to connect to.

Example

Field descriptions

Name

Identifier of the instance configuration.

Server

Hostname of the SWIFTAlliance server machine.

Instance

Identifier of the SWIFTAlliance instance on the server machine.

Release

Release of the SWIFTAlliance instance.

Status

Indicates which instance is "Active". Only one instance can be active at any one time.

3.2.2 TCP Configuration on the SWIFTAlliance Workstation

Port configuration

The SWIFTAlliance Workstation must know the IP address of the SWIFTAlliance Workstationmachine and the bootstrap port (port of the swa_boot). This port is held in the registry perSWIFTAlliance Workstation instance.

The Control application makes an RPC call to the swa_boot daemon process on the machinewhere the SWIFTAlliance Workstation servers are running, and on the default port of swa_boot(currently 48009). If the system administrator of the SWIFTAlliance Workstation servers has



configured swa_boot to run on a non-default port, then you are requested to supply another PortNumber. This is required when the instance is configured (see the following section).

SSL authentication

If Server Authentication is being used, then the SWIFTAlliance Workstation must know the DN ofthe SWIFTAlliance Workstation servers and must have a corresponding CA certificate. Before thesetup of the Server Authentication, the CA certificate file must be distributed to the SWIFTAllianceWorkstations. The Instance Configuration application retrieves the DN for the SWIFTAllianceWorkstation machine (from the .cert_dn file) and propose this as the DN. Check that the proposedDN is the correct one for the selected SWIFTAlliance Workstation instance. The DN name andcertificate location are stored in the registry for each instance (primary, fallback and so on.).

The Server Authentication check box is unset by default.

If the Server Authentication check box is set, then communication with the SWIFTAlliance serversuses SSL and Server Authentication. In this case, if the SWIFTAlliance servers are running withoutSSL, an error is reported.

If the authentication fails (for example, due to an expired certificate), an authentication errormessage appears.

Certificate expiry

In case of certificate renewal, the new certificate must be distributed on the SWIFTAllianceWorkstation as described in the previous section.

3.2.3 Adding or Modifying an Instance

Introduction

SWIFTAlliance Workstation can be configured to connect to multiple instances of theSWIFTAlliance Server. This is achieved by setting up an "instance configuration" onSWIFTAlliance Workstation which can be selected to connect to the required server instance.

Note Only one instance configuration can be selected at any one time. Therefore, only oneserver instance can be "active" for this SWIFTAlliance Workstation.

To add an instance configuration:

1. Start the SWIFTAlliance Control application.

2. From the Instance Configuration menu, select New.

3. The Instance Configuration Details window is displayed.


2 January 2007 35

For a description of the fields in this window, see page 21.

Note The Boot port must contain the port number for the swa_boot of theSWIFTAlliance Access server to which this instance is to connect. By default thisis 48009, however, if the port used by the SWIFTAlliance Access server isdifferent you must enter the actual value in this field.

This field is editable on SWIFTAlliance Workstation only when swa_boot is notrunning on the specified port on the server. For example, when swa_boot isrunning on another port on the server, or the server is stopped. If the field isgreyed out, it means that the correct port is configured and that swa_boot isrunning on the server.

4. If Secure Communication with Server is required, enable the check box provided. The SSLCertificate DN and CA Certificate Location fields become available.

Enter the required SSL Certificate DN and the location of the CA Certificate.

5. Once you have entered all the required details, select Add from the InstanceConfiguration menu to create and save the Instance Configuration.



Note Not all the fields allow the configuration data to be entered directly. If DNS or DHCPis activated on your system, or the server information is already present in your"Hosts" file, the IP Address is entered automatically after you have entered the"Server" name. If this does not occur you need to add the Server name and IPAddress to your "Hosts" file (see "Adding a Server to the "Hosts" File" onpage 38). Also, once the Server and IP Address have been entered normally theServer OS field will be filled out automatically.

To modify an instance configuration:


2. From the Instance Configuration main window, select the Instance Configuration you wantto modify.

3. From the Instance Configuration menu, select Open.

4. In the Instance Configuration Details window, change the configuration data for the instanceas required.

5. Select Modify from the Instance Configuration menu to save the updated InstanceConfiguration.

3.2.4 Activating an Instance

Prerequisite

Before you can connect to a SWIFTAlliance server instance, you must make its "instanceconfiguration" the "active" instance configuration on SWIFTAlliance Workstation. How to do thisis explained in the following procedure.

To activate an instance configuration


2. From the Instance Configuration main window, select the Instance Configuration of theSWIFTAlliance server instance you want to activate.

3. From the Instance Configuration menu, select Activate. The status of the instance changesto "Active".

3.2.5 Removing an Instance

To remove an instance configuration

1. Start the SWIFTAlliance Control Application.

2. From the Instance Configuration main window, select the instance configuration to beremoved.

3. From the Instance Configuration menu, select Remove.

You are prompted to confirm the removal. Click Yes to complete the removal of the InstanceConfiguration from your system.


2 January 2007 37

Note It is not possible to remove an "active" instance configuration. You must first "activate"another instance configuration, to "de-activate" the instance configuration you wantto remove.

3.2.6 Displaying the Active Instance on the Sign-on Window

Introduction

To identify which SWIFTAlliance server instance you are connecting to, you can select to displayits instance configuration identifier on the Sign-on window. It is also possible to select anotherinstance from the Sign-on window if this option is selected.

Sign-on window if this option is selected.


2. From the File menu, select Active Instance visible in Sign-On Dialog.

The next time you start SWIFTAlliance Workstation, the Sign-on window will contain the nameof the instance configuration of the SWIFTAlliance server instance which is currently active.A drop-down menu lists any other instance configurations setup on your system.

3. The default Active Instance must be at the same release level as the Workstation.

If not, an error message like the following is shown:

If you want to continue, click Yes and a list of available instances is displayed. Otherwise,click No to cancel the sign-on.

3.2.7 Adding a Server to the "Hosts" File

Overview

First determine the Host name and IP Address of the SWIFTAlliance server computer you wantto connect to, and then add it to the Hosts file of the computer where you are runningSWIFTAlliance Workstation.

To determine the Host (Full Computer) name and IP Address of a SWIFTAlliance Windows server

1. Go to the server machine.

2. Click Start and select Settings and then Control Panel.

3. From the Control Panel click System and then the Computer Name tab. Copy the FullComputer Name. This is the computer's "Hostname".

4. Click Start and select Programs, Accessories and then Command Prompt.



5. In the Command Prompt window, type ping <host name> (the command syntax may varydepending on your platform).

6. Copy the TCP/IP address that appears. The IP address is the first line that appears. PressCtrl + C to stop the ping process.

To determine the Host name and IP Address of a SWIFTAlliance UNIX server

1. Go to the server machine.

2. Open an Xterm.

3. Type hostname and then copy the name that is displayed.

4. For AIX, type ping <host name>For Solaris, type ping -s <host name>

5. Copy the TCP/IP address that appears. The IP address is the first line that appears. PressCtrl+C to stop the ping process.

To add a server (Host name and IP Address) manually

1. Display the Instance Configuration Details window by selecting New from the InstanceConfiguration menu.

2. Enter a name for the instance configuration.

3. From the Instance Configuration menu, select Add Server to Hosts file. The Add Hostswindow now appears.

• In the Server field, enter the "Hostname" of the SWIFTAlliance server machine.

• In the IP Address field, enter the IP address of the SWIFTAlliance server machine.

• Click OK

4. The system makes a backup of the "Hosts" file. Click OK to confirm the creation of the backup.The server information is added to the "Hosts" file.

3.3 Patches

3.3.1 Patch/Upgrade Program

Description

The Patch/Upgrade program enables you to install and remove any software patches that aredistributed to you.

There are two types of patch:

• "Mandatory cumulative patches", which are sent to all SWIFTAlliance Workstation users. Eachcumulative patch includes the previous cumulative patch. As a consequence only onemandatory patch can be installed at a time.

• "Optional patches", which are sent to selected SWIFTAlliance Workstation users and whichaffect specific deliverables, such as .exe and .dll files. Optional patches do not include anyprevious patches.


2 January 2007 39

Example

When you double-click the Patch/Upgrade icon the following dialog box appears:

Field descriptions

Current Patch Level

The level of the cumulative patch (if there is one installed).

List of Installed Patches

The release level and a short description of all the patches that are currently installed, includingthe latest cumulative patch. The Deinstall button becomes available if you select the latest patch.

List of Performed Upgrades

Historical information about all SWIFTAlliance upgrades that have been performed on the system.This field is deactivated when no upgrade information is available.

Patch location

The location of the patch description file (.inf) to be installed on a CD drive or on disk. Use thebrowse button ( ... ) to locate and select this file.

Distributed Patch

When the Patch location field points to an .inf file this field displays information about the patchif it is not invalid. A patch is invalid if it is a cumulative patch that is older than the currently installedone.

The Install button only becomes available when a valid patch is selected. When a valid patch isselected the following information is displayed:

• the patch level (RRXX where RR is the base release level).

• a short description (up to 40 characters) of the patch.



3.3.2 Installing Patches

To install a patch:

1. Read the Release Letter.

2. Insert the installation CD for the patch or download the patch from the Download Centre onwww.swift.com.

3. Click Start and select Programs. Select SWIFTAlliance Workstation.

4. Select Installation.

5. Double-click Patch/Upgrade. The Patch/Upgrade window opens.

6. Select the .inf file in the Patch location field using the browse button ( ... ).

7. Click Install to start the installation.

For cumulative patches:

• If there is a cumulative patch currently installed on the system it is removed. Eachdeliverable affected by the current patch is restored to its base release version.

• Optional patches are not removed and deliverables affected by optional patches are notrestored to the base release version even if one exists.

For optional patches:

• Some existing optional patches may be removed if required. Information about whichpatches are being removed appears in the bottom left of the dialog box. Deliverablesaffected by removed patches are restored to their base release versions.

For all patches:

• For each deliverable supplied with the patch, the version on the system gets copied to itsbase release version and the patch version gets copied onto the system.

• The system records that the patch has been installed. The patch level, type of patch anda short description are recorded for all patches. For optional patches, a list of affecteddeliverables and optional patches to be removed is also recorded

• Some existing optional patches may be removed if required. Information about whichpatches are being removed appears in the bottom left of the dialog box. Deliverablesaffected by removed patches are restored to their base release version.

3.3.3 Removing Patches

To remove a patch:

1. Read the Release Letter.



4. Double-click Patch/Upgrade. The Patch/Upgrade window opens.

5. Select the latest patch in the List of Installed Patches box.

6. Click Deinstall .


2 January 2007 41

For cumulative patches:

• All the patched deliverables not patched by optional patches are restored to their baserelease version.

• The record that the patch had been installed is removed.

For optional patches:

• All the patched deliverables are restored to their base release version.

• The record that the patch had been installed is removed.

3.4 Version InfoDescription

The Version Info program interrogates your SWIFTAlliance system and lists all the .exe and .dllfiles that are currently installed.

Example

The Version Info window looks like the following example:

Field descriptions

File Name

The name of each file.

File Size

The size of each file.



Product Name

The name of the related product.

Product Version

The version number of the product.

Internal Version

(files that have been installed as a result of patches can have different versions)

Build Stamp

SWIFTAlliance version indicator

Build Date

Date this version was created.

Checking files

When you select Check Signature from the View menu, the files are analysed to see if they havebeen tampered with. A tampered file is one that has been overwritten by an unofficial version ofthe file or has been modified in some way.

The window looks like the following example:


2 January 2007 43

3.5 ReportIntroduction

The Report utility allows you to generate a system status report. This report, which may be outputto file or printer, is useful for diagnostic purposes and may also be used to record the current statusof your system.

To generate a configuration report:

1. Open the SWIFTAlliance Installation application.

2. Click the Report icon.

3. In the Output To field, select one of the following target destinations for the report:

• File: The text of the report is written to a file. When you click OK , you are prompted toenter the path name of the file in which the report is to be written.

• Printer: The text of the report is sent to the default printer.

4. In the Filter field, select the checkbox next to one of the following types of information:

• Operating System: Details related to your operating system is included in the report.

• File System: Details related to the file systems currently defined is included in the report.

• Paging Space: Details of the paging space currently allocated on your system is includedin the report.

• Hardware Configuration: Details related to hardware such as tape drives, disk drives, andnetwork adapters is included in the report.

• SWIFTAlliance Release: Details of the installed SWIFTAlliance release is included in thereport.

• Patches: Details of the patches installed on your system is included in the report.

• SWIFTAlliance Registry: Details of the registry keys relating to SWIFT on your machine.

• Instance Configurations: Details of each Instance Configuration saved in the registry onyour workstation (SWIFTAlliance Workstation only).

5. Having selected the type of report and destination, click OK . The type of report selected isthen generated and output to a file or default printer.

3.6 Command PromptDescription

The Command Prompt starts an environment that is preset for SWIFTAlliance Access or Entry.Any command line application (such as BANK_query) can to be launched from the CommandPrompt.

To use the Command Prompt:





3. Double-click Command Prompt.

4. Type the command of your choice.

5. To close the window, type exit in the command prompt window.

3.7 Selecting an Earlier Version of WorkstationIntroduction

This section describes how to use Workstation 5.5, or 5.9 when you have Workstation 6.0.0installed on the same machine.

To select a version of Workstation:

1. Click Start and select Programs.

2. Select SWIFTAlliance Workstation 5.9 and click Select Workstation.

3. In the Version drop-down menu, select the version you want to use (WS 5.5 or WS 5.9) andclick OK .

The environment variables are updated.

4. Click Start and select Programs again, and select the folder that corresponds to the versionthat you want to use.

5. Click the Workstation icon.

6. The Workstation Sign On window appears.

3.8 Disabling Microsoft Internet Information Server(IIS)

Introduction

Because of the web publishing capabilities of the IIS, the presence of this software on your machinea possible security hazard to your operations. This section gives you instructions on how to disablethis software in your Windows XP installation.

There are two ways to stop the Microsoft Internet Information Server (IIS):

• From the Command Prompt

• From the Control Panel

Note On Windows XP, IIS is not installed by default.

From the Command Prompt

1. Click Start/Programs/Accessories/Command Prompt.

2. In the Command Prompt window type

net stop iisadmin


2 January 2007 45

This works for version 4.0 and above of the Microsoft Internet Information Server (IIS). If alower version is installed, the command returns an error saying that the service does not exist.In that case, you should type

net stop w3svcIf this also returns an error saying that the service does not exist, then it means that theMicrosoft Internet Information Server (IIS) is simply not installed.

From the Control Panel

1. Click Start/Settings/Control Panel.

2. Double-click on Administrative Tools.

3. Double-click on Services.

4. Select IIS Admin Service from the list and select Stop from the Action menu.

5. If a confirmation dialog Stop Other Services is displayed, select Yes .

If the Microsoft Internet Information Server (IIS) version is lower than 4.0, IIS AdminService is not in the list. In that case, select World Wide Web Publishing Service and thenselect "Stop"

If World Wide Web Publishing Service is not in the list, then it means that the MicrosoftInternet Information Server (IIS) is simply not installed.

3.9 Restarting Microsoft Internet Information Server(IIS)

Introduction

You can restart the IIS from either:

• the Command Prompt

• the Control Panel

From the Command Prompt

1. Click Start/Programs/Accessories/Command Prompt.

2. In the Command Prompt window type

net start w3svc

From the Control Panel

1. Click Start/Settings/Control Panel.

2. Double-click Administrative Tools.

3. Double-click Services.

4. Select World Wide Web Publishing Service and then select Start from the Action menu.



3.10 Removing SWIFTAlliance WorkstationImportant

The Uninstall SWIFTAlliance program completely and irreversibly removes an installation ofSWIFTAlliance Workstation from your computer. Do not use it unless you are sure that you wantto do this. There is a warning message before the installation is removed.

3.10.1 Removing a Workstation

To remove a SWIFTAlliance 6.0.0 Workstation:

1. From the SWIFTAlliance Workstation 6.0.0 Installation application window, select theUninstall SWIFTAlliance application to start the process.

2. The following message is displayed:

Do you want to completely remove the selected application and all ofits components ?Click OK to continue the removal of the software, or click Cancel to terminate the process.

3. Finally you need to reboot your system to complete the process. Click Next when prompted.

3.10.2 Removing Previous Versions of SWIFTAllianceWorkstation

When SWIFTAlliance Workstation Release 6.0.0 is installed next to Release 5.5 or 5.9, to removeSWIFTAlliance Workstation Release 5.5 or 5.9, execute the following steps.

1. Click Start and select Programs.

2. Select SWIFTAlliance Workstation 5.9 and click Select Workstation.

3. In the Version drop-down menu, select the version you want to remove (WS 5.5 or WS 5.9)and click OK .

The environment variables are updated.

4. Click Start and select Programs again, and select the folder that corresponds to the versionthat you want to use.

5. Click the Installation icon.

6. Select Uninstall SWIFTAlliance.

7. The following message is displayed:

Do you want to completely remove the selected application and all ofits components ?Click OK to continue the removal of the software, or Cancel to terminate the process.

8. Finall, reboot your system to complete the process. Click Next when prompted.


2 January 2007 47



4 Troubleshooting

4.1 Problems with Workstation/Server ConnectivityIntroduction

The following problems may occur when signing on to a workstation:

• a message appears after 5 minutes stating that the SWIFTAlliance servers are shutting down.This however is not true.

• you receive a message that the SWIFTAlliance servers are not running.

These are described in the following sections.

Servers shutting down ?

You probably forgot to add the TCP/IP address together with the computer name of the workstationto the HOSTS file on the server.

Try to "ping" the server. At a Command Prompt type:

ping <server name>

• If the server responds with a message Reply from followed by the server's TCP/IP address,the server is available. Check the IP address in the hosts file on the server and compare it tothe IP address of the workstation (unless using DNS).

• If the message Request timed out appears then the server is not responding which eithermeans that it is switched off or the network connection has been broken. Add the workstationname and its TCP/IP address to the hosts file of the server (or fix settings in your DNS).

Servers not running ?

There can be several reasons for this:

• The installation of SWIFTAlliance Workstation is incorrect. Run SWIFTAlliance Control from theInstallation application in the SWIFTAlliance program folder. Check that the Server Name andIP address are correct.

• Workstation and Server must be on the same SWIFTAlliance patch level.

• The correct version of Windows XP must be installed, with the correct Service Pack.

• The package "90:Workstation" must be in the Selected pane of the licensing window on theserver. You can check this by using the Licensing Application in System Administration or report.

• There may be a network problem. Try to "ping" the server. At a Command Prompt type:

ping <server name>

• The computer name and the host name of the server are different. Check this by typinghostname at a Command Prompt and comparing it with the computer name that appears whenyou double-click the Network icon in the Control Panel application and look in theIdentification tab.

Troubleshooting

2 January 2007 49

• swa_boot is the SWIFTAlliance instance name provider. This service is started up at boot time.Check on the server, in Control Panel, Services, if the service "SWIFTAlliance InstanceProvider" is present, started and automatic. If necessary, you can start this service as follows:

– Go to Control Panel, Services: select "SWIFTAlliance Instance Provider" and click Start .

– Or open a Command Prompt window and type:

cd <installation directory>\INS\bin\win32\swa_boot -install

• You have already exceeded the maximum number of workstation sign-on attempts. Dependingon your licence, you are allowed to sign-on to a limited number of workstation connections atone time. Typically, if you have a licence for one workstation, and the server workstation isalready running, you cannot run another workstation.

4.2 Problems Logging In When First UsingSWIFTAlliance

Log in problems

Check the following:

• that the card reader is connected, with the correct cards inserted

• the related events in the Event Journal

Also, make sure the SIS component is started by stopping and restarting this component. Use thefollowing steps:

1. From System Management, select File, Stop Component, SIS SWIFT Interface Servicesand then click Stop .

2. Wait for about 1 minute.

3. From the same File menu, select Start Component, SIS SWIFT Interface Services, andthen click Start

Messages not printed

If messages are not printed out although you have made successful connections, check if thereis a printer connected to the default "Printer" message partner:

1. Run the Application Interface application.

2. Double-click Printer.

3. Look in the Connection method field. If you want all received messages to be printed, selectPrinter Name and select a printer (see the section "Managing Message Partner Profiles" inthe System Management Guide for more information).

4. Ensure that a printer is defined in Print Manager.



4.3 Printing Problems on WindowsIntroduction

SWIFTAlliance Workstation checks the status codes returned by the operating system from thetime that the print job is submitted until it completes. Unfortunately the operating system or printerdrivers sometimes give the wrong or no status codes. This results in SWIFTAlliance generatingfalse events which all begin with NROFF_ when in fact the job was okay and then it re-submits thejob giving a duplicate report.

This problem has been reported to Microsoft but in the meantime the following workarounds canbe used if you experience the problem of false printing events and duplicate reports.

The workarounds are presented in order of having least impact on the integrity of report printingand should be applied in order, until the problem is resolved. All printing events should be checkedfor correctness before assuming that they are false - for example, if NROFF_EXIT_PAPEROUT isgenerated and the printer is indeed out of paper then the event is correct and no workaround isrequired. Note that the event NROFF_INTERNAL_ERROR is always a valid error.

Workaround 1

The source of the problem can lie in the printer driver. If there are new versions of the driver thenthese can be installed. If this does not help and there are older versions of the driver then thesecan also be tried. Make a copy of the printer and install the old driver for the copy. Make this copyprinter the default for SWIFTAlliance default printer.

The advantage of this workaround is that SWIFTAlliance will continue to monitor the progress andfinal status of the print job. If this does not help then you can go on to the next workaround.

Workaround 2

Add NROFF_IGNORE_SPOOL_STATUS as a System Variable with value Yes (Control Panel/System/Advanced/Environment Variables/New) on the server machine if automatic printing hasthe problem or on each workstation that has the problem for manual printing.

This means that SWIFTAlliance will not monitor the status of the print job. The danger is that cansomeone actually delete the print job (Control Panel/Printers) then this will not be detected andthe report could be nonexistent or incomplete.

If there is no change or if the problem still occurs albeit less frequently then go on to the nextworkaround.

Workaround 3

Add NROFF_IGNORE_EXIT_CODE as a System Variable with value Yes.

This means that SWIFTAlliance does not check the final status of the print job. The danger is thatif the print job fail for any reason, such as a jam, out of paper and so on. then this will not bedetected and the report can be nonexistent or incomplete. In fact the only error that will be detectedis if the printer is not physically there and you are on the machine that has the printer connected.

This workaround must be used with caution and users should physically check the outcome ofreporting. Users may prefer not to apply the workaround and instead to accept occasional duplicatereports.

Troubleshooting

2 January 2007 51



Documents

SWIFTAlliance Workstation 6.0 - Installation and ... · Welcome to the SWIFTAlliance Workstation Installation and Administration Guide. ... 4.1 Problems with Workstation/Server Connectivity