Pre-installation Procedures

spinabundantInternet and Web Development

Jul 30, 2012 (5 years and 2 months ago)

293 views

Pre Installation guide


Table of Contents

Pre
-
installation Procedures

................................
................................
..........................

2

Pre
-
Installation Checklist for Interchange Upgrade from Commbridge

...............................

2

Prerequisites for Linux Platform

................................
................................
.................

2

Capture a Directory / File Listing of the Existing Commb
ridge Installation

....................

2

Capture the WebSphere MQ Version Information

................................
......................

3

Capture Existing CBTrace Log File

................................
................................
...........

3

Create a Backup of Existing Commbridge Installation Tree

................................
.........

3

Prerequisites for Windows Platform

................................
................................
............

4

Pre
-
Installation Checklist for Interchange Upgrade from Previous Version

..........................

4

Capture a directory / file listing of the existing Commbridge installation

......................

4

Capture
the WebSphere MQ version information

................................
.......................

4

Capture Existing CBTrace Log File

................................
................................
...........

5





Pre
-
installation

Procedures


Pre
-
installation procedures describe a check list of prerequisites, requirements, and basics necessary
before you install Interchange on your system. Preinstallation

procedures cover:



Commbridge migration and upgrade installation Linux and Windows users to Interchange



New Interchange Installation for Windows and Linux users



Upgrade Interchange Installation from previous Interchange version of Windows and Linux
systems

Pre
-
I
nstallation Checklist

for Interchange Upgrade from Commbridge

In order to preserve the current Commbridge behavior, it is important to gather some machine
-
specific
information prior to the Interchange installation. Please refer to your platform speci
fic commands for
either Linux or Windows.

Please ensure that the appropriate firewalls have been opened between the new client endpoint server
and the Interchange server. It is recommended to leave 5
-
7 business days for lower environments
(development, te
st, QA) and 10 business days for production. For external partners and clients outside
of the MagNet Commonwealth network, more time is often needed for installation and validation, so
allow for 5 additional business days.


Prerequisites for
Linux

Platfor
m




Minimum of twenty
-
five megabytes of free storage



Ability to login (sudo) to the MQ/FTE user on the install host successfully

$ sudo su
-

MQ/FTE



Machine must be able to access the XML Gateway. Verify by trying to telnet to the gateway
using Port 443.


N
ote:

the following example uses the QA version of the XML Gateway, but you need to use the
appropriate Gateway for your verification (e.g. Test, QA, Prod):

$ telnet wsgwalt.mass.gov443# QA XML Gateway

$ telnet wsgw.mass.gov443# Prod XML Gateway


Capture a

Directory / File Listing of the Existing Commbridge Installation

Capture a directory / file listing of the existing Commbridge installation, and save to a file.

This information is used to configure the Legacy Commbridge (LCB) wrapper scripts to work in
your
environment.

1.

Change directory to the root of the existing installation:

$ cd /opt/cb

2.

Capture the list of available environments

$ ls
-
lR > /tmp/Commbridge_files.txt


Capture the WebSphere MQ Version Information

Do the following:

1.

Capture the
version information:

$ /opt/mqm/bin/dspmqver > /tmp/dspmqver.txt


Capture Existing CBTrace Log File

Capture an existing CBTrace log file to verify current Commbridge behavior on this host. This
information is used to configure the Legacy Commbridge (LCB)
wrapper scripts to work in your
environment.

Do the following:

1.

Change directory to a service currently used by your system:

$ cd */opt/cb/dev/ctr/ltimelog/bin*


$ cp ./CBTrace.log > /tmp/CBTrace.log # verify there is a CBTrace
file


Create a Backup of Exi
sting Commbridge Installation Tree

The following procedure is optional but recommended:

1.

In Linux systems, options such as tar or cpio are example commands used. You should work
with your recommended technical contact to create a backup of existing installa
tion.

2.

Check size of Commbridge (CB) file tree

$ du
-
ks ./cb

3.

Verify there is sufficient file space for the backup installation

$ df
-
k ./cb

$ cd /opt

$ tar
-
cvf /tmp/CB.tar ./cb




Prerequisites for Windows Platform



Minimum of twenty
-
five megabytes of free

storage



Ability to login as the MQ/FTE user on the install host

MQ/FTE



Machine must be able to access the XML Gateway. Verify by trying to telnet to the gateway
using Port 443.


Note:

the following example uses the QA version of the XML Gateway, but you need to use the
appropriate Gateway for your verification (e.g. Test, QA, Prod):


=For QA:

$ telnet wsgwalt.mass.gov443

For Production:

$ telnet wsgw.mass.gov443

Pre
-
Installation Checkl
ist for Interchange Upgrade from Previous
Version

The following pre
-
installation checklist provides the requirements, prerequisites, and basics necessary
for upgrading from a previous version of Interchange.


Capture a directory / file listing of the exist
ing Commbridge installation

Capture a directory / file listing of the existing Commbridge installation, and save to a file. This
information is used to configure the Legacy Commbridge (LCB) wrapper scripts to work in your
environment.

1.

Change directory to t
he root of the existing installation:

$ cd
\
opt
\
cb

2.

Capture the list of available environments

$ dir
-
L
\
tmp
\
Commbridge_files.txt

Capture the WebSphere MQ version information

Capture the WebSphere MQ version information and save to a file.

Do the followi
ng:

1.

Capture the version information:

$ C:
\
Program Files
\
IBM
\
WebSphere MQ
\
bin
\
dspmqver >
%TEMP%
\
dspmqver.txt


2.

If you receive an error (The system cannot find the program specified), then use the actual
location of the program.


Capture Existing CBTrace

Log File

Capture an existing CBTrace log file to verify current Commbridge behavior on this host. This
information is used to configure the Legacy Commbridge (LCB) wrapper scripts to work in your
environment.

Note:

Your system and service names may var
y.


Do the following:

1.

Change directory to the root of the existing service:

$
$ cd C:
\
{*}{_}opt
\
cb
\
dev
\
ctr
\
ltimelog
\
bin_*


$ copy .
\
CBTrace.log
\
tmp
\
CBTrace.log # verify there is a CBTrace
file


Note:

We recommend creating a backup of your existing Commbr
idge installation file tree, by sending the files to a
compressed zip folder from the root of the Commbridge installation.


Example using Winzip from directory containing installation files:


winzip .*.* Commbridge.zip