Connectivity

WebSphere MQ Interface 7.0

For Alliance Access 7.0

Installation Guide
This installation guide explains how to install and configure the WebSphere MQ Interface for Alliance Access (MQSA). The document also describes how to add and remove MQSA patches. This document is for programmers, system administrators, and support staff who implement a message-exchange interface. Familiarity with the basics of Alliance Access and WebSphere MQ is a prerequisite for readers of this document.

30 September 2011

WebSphere MQ Interface 7.0 for Alliance Access 7.0

Table of Contents
. Preface .............................................................................................................................................................................3 1 Introduction ....................................................................................................................................................... 4
1.1 1.2 1.3 MQSA Product Overview ......................................................................................................................... 4 Supported Platforms ................................................................................................................................. 4 Overview of Installation Procedure ......................................................................................................... 4

Installing a Component Medium .............................................................................................................. 6

2.1 2.2 Installation Prerequisites .......................................................................................................................... 6 SMQS and SMQA Installation Media ..................................................................................................... 7

Installing SMQS and SMQA ........................................................................................................................ 9

3.1 3.2 3.3 3.4 Preparing the Alliance Access Server Host .......................................................................................... 9 Installation and Registration of SMQS ................................................................................................. 10 Installation and Registration of SMQA ................................................................................................. 10 SMQA Installation on Alliance Workstation ......................................................................................... 11

Upgrading from a Previous Release of MQSA ................................................................................. 13

4.1 4.2 4.3 4.4 4.5 Prerequisites ............................................................................................................................................ 13 SMQS and SMQA Upgrade on Alliance Access ................................................................................ 14 SMQS Post-upgrade Activity ................................................................................................................. 15 Upgrading SMQA on Alliance Workstation ......................................................................................... 16 SMQA Post-upgrade Activity ................................................................................................................. 16

Adding and Removing Patches .............................................................................................................. 18

5.1 5.2 Adding a Patch ........................................................................................................................................ 18 Removing a Patch ................................................................................................................................... 19

Choosing WebSphere MQ Server or WebSphere MQ Client ..................................................... 21

6.1 6.2 Dynamics .................................................................................................................................................. 21 Migration from One to the Other ........................................................................................................... 21

Removing the MQSA Component .......................................................................................................... 22

. Appendix A Recovering from an Installation Failure ................................................................................24

A.1 Recovery Activity ..................................................................................................................................... 24

. Legal Notices ...............................................................................................................................................................25

Installation Guide

Preface

Preface
Purpose of this document This document explains how to install and configure the WebSphere MQ Interface for Alliance Access (referred to in this document simply as MQSA). It also includes information about upgrading MQSA, and adding and removing MQSA patches. Read this document in conjunction with Alliance Access guides and WebSphere MQ guides, before installing or upgrading MQSA. Intended audience This document is intended for programmers, system administrators, and support staff who are responsible for implementing a message-exchange interface. It is assumed that the reader of this document is familiar with the basics of Alliance Access and WebSphere MQ to install, configure, maintain, and operate the MQSA software. Related documentation This document references the following documents: WebSphere MQ Interface Release Letter WebSphere MQ Interface User Guide Alliance Access Installation and Administration Guide Alliance Workstation Installation and Administration Guide

30 September 2011

WebSphere MQ Interface 7.0 for Alliance Access 7.0

1
1.1

Introduction
MQSA Product Overview
What is WebSphere MQ Interface for Alliance Access? The WebSphere MQ Interface for Alliance Access software application (referred to in this document as MQSA) provides a reliable communication between financial applications and Alliance Access through IBM WebSphere MQ. It enables SWIFT messages to be exchanged between Alliance Access and other financial applications. MQSA is a product of the Alliance Access Developers Toolkit (referred to in this document as ADK). It accesses message-queuing services by using ADK functions to communicate with Alliance Access and WebSphere MQ functions. Alliance Access and MQSA Alliance Access enables you to build components that can be fully integrated using the ADK. MQSA is composed of two such components, SMQS and SMQA. The SMQS component runs on the same host as the Alliance Access servers and handles the messaging between Alliance Access and WebSphere MQ. SMQA is the GUI component and runs on Alliance Workstation.

1.2

Supported Platforms
Alliance Access MQSA is available for Alliance Access running on the operating systems specified in the WebSphere MQ Interface Release Letter. MQSA graphical user interface The MQSA graphical user interface (GUI) runs on Alliance Workstation, which runs on the operating systems specified in the WebSphere MQ Interface Release Letter.

1.3

Overview of Installation Procedure

ADK components ADK components must be installed and registered before they can be used in the Alliance Access environment. The application used for installation and registration is adk_install: The installation part of adk_install sets the component directory structure in the Alliance Access instance, and copies the program files to the target location on disk. The registration part of adk_install defines the ADK component in the Alliance Access database. SMQS and SMQA components Both the SMQS and the SMQA components must be installed and registered on the host on which the Alliance Access servers are running. The SMQA component must also be installed (but not registered) on every Alliance Workstation on which you intend to use the MQSA GUI.

Installation Guide

Introduction

Upgrading MQSA If you are upgrading MQSA, then see the WebSphere MQ Interface Release Letter for details of valid upgrade paths. Note You can upgrade from MQSA 6.0 or MQSA 6.3 to MQSA 7.0 in a UNIX environment. On Windows, a fresh installation of MQSA 7.0 is required. Switching between server and client versions It is sometimes necessary to switch between the MQSA Server and the MQSA Client versions. This is explained in "Choosing WebSphere MQ Server or WebSphere MQ Client" on page 21. Windows and UNIX The procedure for installing and registering a component is similar on Windows and UNIX. Therefore, this document shows screenshots from only the Windows platform - the application has a similar interface on UNIX.

30 September 2011

WebSphere MQ Interface 7.0 for Alliance Access 7.0

2
2.1

Installing a Component Medium

Installation Prerequisites
Media and knowledge You must have the following items: The MQSA components installation medium The installation secret key (or cipher), provided in the WebSphere MQ Interface Release Letter The appropriate password: for UNIX, an Alliance administrator (in most cases, the administrator is all_adm) for Windows, a user with Administrator privileges. MQSA installation passwords. These are required once the component has been installed and registered. The security officers (LSO and RSO operators) must enter and approve these passwords from the Security Definition application. For details, see the WebSphere MQ Interface User Guide. An approved time window within which to perform this activity. This component operation must be carefully scheduled because it requires exclusive access to the whole Alliance Access environment. This means that, during the operation, no Alliance Access activity is permitted on the system and no Alliance Access Administrator may be logged on. Software Make sure that the following minimum requirements are fulfilled: Correct Alliance Access software level (see the WebSphere MQ Interface Release Letter) Alliance Access is licensed with the ADK RUN TIME option (the licensing of your Alliance Access software must contain the package string 99:TOOLKIT RUN-TIME). All Alliance Access servers are stopped; no Alliance Access process running. WebSphere MQ (client or server) software is installed on the Alliance Access computer. A system dead-letter queue is defined on each queue manager being accessed by MQSA. For details of dead-letter queues, see the WebSphere MQ Interface User Guide. When installing MQSA, the system administrator must decide whether to use the WebSphere MQ Server version or the WebSphere MQ Client version. Disk space requirements for the installation of MQSA are minimal. A maximum of 10 MB is sufficient. If you are upgrading, then delete all SMQS trace files and ensure that sufficient space is available for the ADK installation program (adk_install) to back up the existing SMQS directories. The adk_install program uses a temporary directory during the installation. This directory is taken from either of the following values: the environment variable ADK_TMP if it is defined

Installation Guide

Installing a Component Medium

the environment variable TMPDIR if it is defined the default value /tmp on UNIX the default value C:\temp on Windows. Back-up Before installing MQSA, back up Alliance Access fully (database and software). See the appropriate Installation and Administration Guide for your system.

2.2

SMQS and SMQA Installation Media

Available installation media for the Alliance Access server The installation media must first be transferred to the Alliance Access server. The following table identifies the relevant installation media:
Installation media for SMQS and SMQA Platform AIX AIX AIX SunOS SunOS SunOS Win32 Win32 Win32 Media Name SMQSMediumAIX-C SMQSMediumAIX-S SMQAMediumAIX SMQSMediumSunOS-C SMQSMediumSunOS-S SMQAMediumSunOS SMQSMediumWin32-C SMQSMediumWin32-S SMQAMediumWin32

When installing MQSA, the system administrator must decide whether to use the WebSphere MQ Server version or the WebSphere MQ Client version. The installation media name for SMQS is suffixed by -S for the server version, and -C for the client version. For patch media, the media name contains an indication of the patch, where <mmnn> refers to the patch level being added, as shown in the following table:
Installation media for patches Platform AIX AIX AIX SunOS SunOS SunOS Win32
30 September 2011

Media Name SMQSMediumAIXPatch<mmnn>-C SMQSMediumAIXPatch<mmnn>-S SMQAMediumAIXPatch<mmnn> SMQSMediumSunOSPatch<mmnn>-C SMQSMediumSunOSPatch<mmnn>-S SMQAMediumSunOSPatch<mmnn> SMQSMediumWin32Patch<mmnn>-C

7

WebSphere MQ Interface 7.0 for Alliance Access 7.0

Platform Win32 Win32

Media Name SMQSMediumWin32Patch<mmnn>-S SMQAMediumWin32Patch<mmnn>

Installation Guide

Installing SMQS and SMQA

3
3.1

Installing SMQS and SMQA

Preparing the Alliance Access Server Host
To prepare the Alliance Access server host: 1. 2. Copy the media appropriate to your system, as listed in "SMQS and SMQA Installation Media" on page 7. Start the adk_install utility, by performing one of the following procedures, depending on the platform you are using: On Windows: a. Start the Installation application by clicking Start/Programs/Alliance Access/ Installation. b. In the Installation Application - Alliance window, double-click Command Prompt. c. At the command prompt, start the ADK installation utility. Enter the following commands, in the order shown: cd /D %ALLIANCE%\INA\bin\win32 adk_install On UNIX: a. Log on to the system as the Alliance administrator (in most cases the administrator is all_adm). b. From the System Administration Application, open an Xterm window. c. Invoke the ADK installation utility, by entering the following commands on the command line, in the order shown: cd $ALLIANCE/INA/bin/$ARCH ./adk_install STANDALONE The Alliance Access Set-up program starts, and shows the following dialog box:

30 September 2011

WebSphere MQ Interface 7.0 for Alliance Access 7.0

3.2

Installation and Registration of SMQS

To install and register SMQS: After following the procedure described in "Preparing the Alliance Access Server Host" on page 9, take the following steps: 1. 2. 3. In the Component field, type SMQS. Select the Install component option button under Software. In the Input device field, type the path of the installation files. The path must not contain spaces. For example: For AIX, type one of the following: /tmp/SMQSMediumAIX-C /tmp/SMQSMediumAIX-S For Windows, type one of the following: C:\Temp\SMQSMediumWin32-C C:\Temp\SMQSMediumWin32-S 4. 5. 6. In the Cipher field, type the installation secret code (provided in the WebSphere MQ Interface Release Letter). Start the installation by clicking
OK

Verify the success of the installation, by using the contents of the adk_install window to track progress. If verification fails, then see Appendix A, "Recovering from an Installation Failure" on page 24.

7. 8.

After successful installation, clear the Input Device field and select the Register option button under Services. Start the registration by clicking OK . Verify the success of the registration, by using the contents of the adk_install window to track progress. If verification fails, then see Appendix A, "Recovering from an Installation Failure" on page 24.

The SMQS component is now installed and registered. Warning Do not quit the installation utility yet. You must first install the graphical application (SMQA), as described in "Installation and Registration of SMQA" on page 10.

3.3

Installation and Registration of SMQA

To install and register SMQA: After following the procedure described in "Preparing the Alliance Access Server Host" on page 9, take the following steps: 1. 2. In the Component field, type SMQA. Select the Install component option button under Software.
Installation Guide

10

Installing SMQS and SMQA

3.

In the Input device field, type the path of the installation files. For example: For AIX, type the following: /tmp/SMQAMediumAIX For Windows, type the following: C:\Temp\SMQAMediumWin32

4. 5. 6.

In the Cipher field, type the installation secret code (provided in the WebSphere MQ Interface Release Letter). Start the installation by clicking
OK

Verify the success of the installation, by using the contents of the adk_install window to track progress. If verification fails, then see Appendix A, "Recovering from an Installation Failure" on page 24.

7. 8.

After successful installation, clear the Input Device field and select the Register option button under Services. Start the registration by clicking OK . Verify the success of the registration, by using the contents of the adk_install window to track progress. If verification fails, then see Appendix A, "Recovering from an Installation Failure" on page 24. The SMQA component is now installed and registered.

9.

Click

Quit

to end the installation program.

3.4

SMQA Installation on Alliance Workstation

Installing SMQA on Alliance Workstation Only SMQAMediumWin32 must be installed on Alliance Workstation, as follows: 1. 2. Start the Installation application: Start/Programs/Alliance Workstation/Installation. Right-click, select Run as... and select your administrator account. In the Installation Application - Alliance window, double-click Command Prompt. Note It is not necessary to register the installation on Alliance Workstation. If there are different versions of Alliance Workstation on the same computer, then ensure that you have selected the correct version of the Installation application which has the release 7.0 Command Prompt icon. For details, see the Alliance Workstation Installation and Administration Guide, "Administration Tasks". 3. At the command prompt, start adk_install, by entering the following commands in the order shown: cd /D %ALLIANCE%\INA\bin\win32 adk_install The Alliance Set-up dialog box appears.

30 September 2011

11

WebSphere MQ Interface 7.0 for Alliance Access 7.0

4. 5. 6.

In the Component field, type SMQA. Select the Install component option button. In the Input device field, type the path of the installation files (note that the path must not contain spaces, and must not refer to a network drive). For example: C:\Temp\SMQAMediumWin32

7. 8. 9.

In the Cipher field, type the installation secret code (provided in the WebSphere MQ Interface Release Letter). Start the installation by clicking Click
Quit OK

to end the installation program.

12

Installation Guide

Upgrading from a Previous Release of MQSA

4
4.1

Upgrading from a Previous Release of MQSA

Prerequisites
SMQS and SMQA MQSA can be upgraded from the previous version of MQSA. Ensure that the MQSA software level is correct. For details of valid migration paths, see the WebSphere MQ Interface Release Letter. The upgrade procedure deletes all the files in the SMQS and SMQA component directories, so ensure that the SMQS Exit library and the SMQA configuration files are safe-stored (as explained in the following sections). Note The configuration files located in $ALLIANCE_DB/ADK_DIR/SMQS (UNIX platforms) or %ALLIANCE_DB%\ADK_DIR\SMQS (Windows platforms) are not affected by the upgrade.

SMQS-specific If the SMQS exit library being used was supplied by an external vendor, then it must be safestored. In such cases, it is imperative that you contact the vendor to make sure that the version of the exit library is compatible with the latest version of MQSA. The exit library in previous releases has one of the following names, depending on the platform used: libSMQSExits.a (for AIX) libSMQSExits.so (for Oracle Solaris) SMQSExits.dll (for Windows) Since release 6.2, the exit libraries are standardised across all platforms and are named as follows: libSMQSExits.a (for AIX) libSMQSExits.so (for Oracle Solaris) libSMQSExits.dll (for Windows) Note The name of the exit library on Windows has changed and must therefore be renamed to libSMQSExits.dll if you restore a previous (externally supplied) library from earlier than release 6.2.

The location of the exit library is as follows: On UNIX, the library is in the $ALLIANCE/SMQS/bin/$ARCH directory, where $ARCH refers to the platform on which the Alliance Access servers are running. On Windows, the library is located in the %ALLIANCE%\SMQS\bin\%ARCH% folder.

30 September 2011

13

WebSphere MQ Interface 7.0 for Alliance Access 7.0

SMQA-specific On Alliance Workstation, the SMQA configuration file, SMQA.dat, must be backed up prior to the upgrade. This file is located in %ALLIANCE%\SMQA\data.

4.2

SMQS and SMQA Upgrade on Alliance Access

To upgrade SMQS and SMQA on Alliance Access: 1. 2. Copy the media. Start the adk_install utility, as follows: On Windows: a. Start the Installation application by clicking Start/Programs/Alliance Access/ Installation. b. In the Installation Application - Alliance window, double-click Command Prompt. c. At the command prompt, enter the following command: cd /D %ALLIANCE%\INA\bin\win32 d. Enter the following command: adk_install On UNIX: a. Log on to the system as the Alliance administrator (in most cases the administrator is all_adm). b. From the System Administration Application, open an Xterm window. c. Invoke the ADK installation utility, by entering the following commands in the order shown: cd $ALLIANCE/INA/bin/$ARCH ./adk_install STANDALONE 3. 4. 5. In the Component field, type the name of the component being upgraded (SMQS). Select the Upgrade component option button under Software. In the Input device field, type the path of the installation files. For example: For AIX, type one of the following: /tmp/SMQSMediumAIX-C /tmp/SMQSMediumAIX-S For Windows, type one of the following: C:\Temp\SMQSMediumWin32-C C:\Temp\SMQSMediumWin32-S 6. 7. In the Cipher field, type the installation secret code (provided in the WebSphere MQ Interface Release Letter). Start the instalation by clicking
OK

.
Installation Guide

14

Upgrading from a Previous Release of MQSA

8.

Verify the success of the installation, by using the contents of the adk_install window to track progress. If verification fails, then see Appendix A, "Recovering from an Installation Failure" on page 24.

9.

Then clear the Input device field and click the Register option button followed by

OK

10. Verify the success of the registration, by using the contents of the adk_install window to track progress. If verification fails, then see Appendix A, "Recovering from an Installation Failure" on page 24. Warning After you have successfully verified the registration, do not stop the adk_install utility. Perform the same actions to upgrade the SMQA component, as explained in the following steps.

11. In the adk_install window, enter the component name (SMQA), the input device name (such as /tmp/SMQAMediumAIX or C:\temp\SMQAMediumWin32), and the cipher key (see the WebSphere MQ Interface Release Letter). 12. Select the Upgrade component option button, and start the installation by clicking
OK

13. Verify the success of the upgrade, by using the contents of the adk_install window to track progress. If verification fails, then see Appendix A, "Recovering from an Installation Failure" on page 24. 14. Then clear the Input device field and click the Register option button followed by
OK

15. Verify the success of the registration, by using the contents of the adk_install window to track progress. If verification fails, then see Appendix A, "Recovering from an Installation Failure" on page 24. MQSA is now upgraded. 16. Click
Quit

to leave the adk_install utility.

4.3

SMQS Post-upgrade Activity

Restore the SMQS Exit library After SMQS has been upgraded, it is necessary to restore the SMQS Exit library that was safestored earlier to its original location ($ALLIANCE/SMQS/bin/$ARCH on UNIX or %ALLIANCE% \SMQS\bin\%ARCH% on Windows).

30 September 2011

15

WebSphere MQ Interface 7.0 for Alliance Access 7.0

4.4

Upgrading SMQA on Alliance Workstation

Upgrading SMQA on Alliance Workstation There is no SMQS component running on Alliance Workstation. The following steps must be performed to install the SMQA component on each Alliance workstation: 1. 2. 3. Start the Installation application by clicking Start/Programs/Alliance Workstation/ Installation. In the Installation Application - Alliance window, double-click Command Prompt. Start the ADK installation utility. Enter the following commands at the Command Prompt, in the order shown: cd /D %ALLIANCE%\INA\bin\win32 adk_install 4. In the adk_install window, enter the component name (SMQA), the input device name (such as C:\temp\SMQAMediumWin32), and the cipher key (see the WebSphere MQ Interface Release Letter). Select the Install component option button, and start the installation by clicking
OK

5. 6.

Verify the success of the installation, by using the contents of the adk_install window to track progress. If verification fails, then re-check all required pre-requisites and try the process again. If the installation still fails, then make a note of the exact failure reported and call Support for assistance.

7.

Click

Quit

to end the installation program.

Note

It is not necessary to register SMQA on Alliance Workstation. The installation of SMQA on Alliance Workstation must be performed at the same time as the SMQA is upgraded on the Alliance Access server. Otherwise a version failure occurs and SMQA cannot be started.

4.5

SMQA Post-upgrade Activity

Restore the SMQA configuration file You must only perform this step if you upgrade from release 6.x to 7.0. After SMQA has been installed, you must restore the SMQA configuration file that was safestored to the new location of the file in release 7.0. Use the %APPDATA% to find the location of the configuration file, as follows: %APPDATA%\SWIFT\SWIFTAlliance Workstation\<instance configuration name>\SMQA\data

16

Installation Guide

Upgrading from a Previous Release of MQSA

Location of SMQA configuration file For reference purposes, the following table outlines the location of the SMQA configuration file in several releases:
Release 6.0 6.2, and 6.3 7.0
%ALLIANCE%\SMQA\data C:\Documents and Settings\<username>\Application Data\SWIFT \SWIFTAlliance Workstation\<instance configuration name>\SMQA\data C:\Users\<username>\AppData\Roaming\SWIFT\SWIFTAlliance Workstation\<instance configuration name>\SMQA\data

Location

30 September 2011

17

WebSphere MQ Interface 7.0 for Alliance Access 7.0

Adding and Removing Patches

Generic information This section describes how to add (install) or remove an MQSA patch. The instructions in this section are generic in that they apply to both MQSA components, SMQS and SMQA.

5.1

Adding a Patch
Validity Adding patches to the SMQS component must be done on the Alliance Access server. Adding patches to the SMQA component must be done on the Alliance Access server and on each Alliance workstation that has SMQA installed. To add a patch: 1. Remove any existing MQSA patches that are already installed. For details, see "Removing a Patch" on page 19. 2. 3. Copy the correct media. For details, see "Installation media for patches" on page 7 Start the adk_install utility, as follows: On Windows: a. Start the Installation application by clicking Start/Programs/Alliance Access/ Installation. b. In the Installation Application - Alliance window, double-click Command Prompt. c. At the command prompt, enter the following commands in the order shown: cd /D %ALLIANCE%\INA\bin\win32 adk_install On UNIX: a. Log on to the system as the Alliance administrator (in most cases the administrator is all_adm). b. From the System Administration application, open an Xterm window. c. Invoke the ADK installation utility, by entering the following commands in the order shown: cd $ALLIANCE/INA/bin/$ARCH ./adk_install STANDALONE

18

Installation Guide

Adding and Removing Patches

The Alliance Access Set-up program starts, and shows the following dialog box:

4. 5. 6.

In the Component field, type the name of the patch to be added (SMQA or SMQS). Select the Add patch option button under Software. In the Input device field, type the path and filename of the patch media (note the path must not contain spaces). For example, for an SMQA patch for AIX: /tmp/SMQAMediumAIXPatch1234.

7. 8.

In the Cipher field, type the installation secret code (provided in the WebSphere MQ Interface Release Letter). Start the installation by clicking
OK

The component patch is now added.

5.2

Removing a Patch
Validity Removing patches from the SMQS component must be done on the Alliance Access server. Removing patches from the SMQA component must be done on the Alliance Access server and for each Alliance workstation that has SMQA installed. To remove a patch: 1. Perform one of the following procedures: On Windows: a. Start the Installation application by clicking Start/Programs/Alliance Access/ Installation. b. In the Installation Application - Alliance window, double-click Command Prompt. c. At the command prompt, start adk_install by entering the following commands in the order shown: cd /D %ALLIANCE%\INA\bin\win32 adk_install

30 September 2011

19

WebSphere MQ Interface 7.0 for Alliance Access 7.0

On UNIX: a. Log on to the system as the Alliance administrator (in most cases the administrator is all_adm). b. From the System Administration application, open an Xterm window. c. Invoke the ADK installation utility, by entering the following commands in the order shown: cd $ALLIANCE/INA/bin/$ARCH ./adk_install STANDALONE The Alliance Access Set-up program starts, and shows the following dialog box:

2. 3. 4.

In the Component field, type the name of the patch to be removed (SMQA or SMQS). Select the Remove patch option button under Software. Start the removal by clicking
OK

The component patch is now removed.

20

Installation Guide

Choosing WebSphere MQ Server or WebSphere MQ Client

6
6.1

Choosing WebSphere MQ Server or WebSphere MQ Client

Dynamics
Dynamics When the requirements or configuration of WebSphere MQ change, it may be necessary to migrate the MQSA software from a WebSphere MQ (WSMQ) Server to a WSMQ Client, or from a WSMQ Client to a WSMQ Server.

6.2

Migration from One to the Other

Migration from one to the other Before you migrate the MQSA software, perform a complete backup of Alliance Access. Only SMQS must be upgraded. To migrate SMQS to a WSMQ Client or to a WSMQ Server, follow the procedure in "Upgrading from a Previous Release of MQSA" on page 13. This copies all the files from the ADK medium to the Alliance Access release tree. Note Before the migration, you must remove any SMQS patches, and re-install them once the migration has been completed. No registration of the component is necessary because the Alliance Access database is already up-to-date.

30 September 2011

21

WebSphere MQ Interface 7.0 for Alliance Access 7.0

Removing the MQSA Component

Summary and Prerequisites All references to the component must be removed from the Alliance Access database. Before you remove the MQSA software, perform the following: Mmake a complete back-up of Alliance Access. Stop the SMQS component on the day before you intend to remove it, because the Alliance Journal must contain no event that has been generated by the component. To remove the MQSA component: 1. For the Routing application, do one of the following actions: Activate a temporary schema. Create a new empty schema and activate it. 2. 3. 4. For each routing point, check and remove each rule that is routing to an SMQS routing point. In the Message File application, complete and archive all instances present in the Alliance Access database. For details, see the Alliance Access Daily Operations Guide. In the System Management application, remove from the target list each instance of SMQSFromMQSeries and SMQSToMQSeries that is used as a target by any queue. For details, see the Alliance Access System Management Guide. For the Security Definition application (and only if you have operators using the MQSA GUI), select the profile to which the application is granted and remove it from the list. For details, see the Alliance Access Security Guide. Note Operators assigned to this profile must be approved. For details, see the Alliance Access Security Guide. The operators with this profile cannot be logged on to Alliance Access during this operation. 6. 7. 8. 9. In the Event Journal application, archive all entries. For details, see the Alliance Access Daily Operations Guide. Stop all affected instances of Alliance server. Start the adk_install utility as described in "Preparing the Alliance Access Server Host" on page 9. Perform the following actions (for the SMQS and SMQA components): a. Empty the Input device field. b. Deregister the component. c. Remove the component. d. Delete the directory SMQS within the ADK storage directory.

5.

22

Installation Guide

Removing the MQSA Component

On UNIX, this directory is in $ALLIANCE_DB/ADK_DIR. On Windows, it is in %ALLIANCE_DB%\ADK_DIR.

30 September 2011

23

WebSphere MQ Interface 7.0 for Alliance Access 7.0

Appendix A

Recovering from an Installation Failure

A.1 Recovery Activity
Recovering from an installation failure If the installation fails, then restore the Alliance Access back-up made before you started the installation process, as described in the Alliance Access Installation and Administration Guide.

24

Installation Guide

Legal Notices

Legal Notices
Copyright SWIFT 2011. 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 publication outside your organisation without the prior written consent of SWIFT. Disclaimer SWIFT supplies this publication for information purposes only. The information in this publication may change from time to time. You must always refer to the latest available version on www.swift.com. Translations The English version of SWIFT documentation is the only official version. Trademarks SWIFT is the trade name of S.W.I.F.T. SCRL. The following are registered trademarks of SWIFT: SWIFT, the SWIFT logo, the Standards Forum logo, 3SKey, Innotribe, Sibos, SWIFTNet, SWIFTReady, and Accord. Other product, service, or company names in this publication are trade names, trademarks, or registered trademarks of their respective owners.

30 September 2011

25