General Document - Strate

towerdevelopmentData Management

Dec 16, 2012 (4 years and 7 months ago)

373 views
















S
S
T
T
R
R
A
A
T
T
E
E




M
M
M
M
F
F
E
E


I
I
N
N
S
S
T
T
A
A
L
L
L
L
A
A
T
T
I
I
O
O
N
N


G
G
U
U
I
I
D
D
E
E


F
F
O
O
R
R


M
M
A
A
R
R
K
K
E
E
T
T


T
T
E
E
S
S
T
T
I
I
N
N
G
G











STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
2

of
39



D
D
O
O
C
C
U
U
M
M
E
E
N
N
T
T


P
P
A
A
R
R
T
T
I
I
C
C
U
U
L
L
A
A
R
R
S
S




COPYRIGHT NOTICE


Contents of this document are protected under South African copyright law. No part of this document
can be copied, completely or partly, either elec
tronically or manually, without the written consent of
STRATE
.

-

THIS DOCUMENT REMAINS THE SOLE PROPERTY OF STRATE




DISCLAIMER

Although there has been extensive analysis and research placed into this document. It is still subject to
changes from the audie
nce or any party that is supporting or endorsing this document. This revisions
and editions will be recorded as per the various versions that are released.



VERSION CONTROL

The current version of this document is
Version 1.0
. If the reader requires additi
onal copies of any
versions of this document, then contact the Document Administrator.



DOCUMENT ADMINISTRATION

Godfrey Mthombeni

STRATE

: IT Systems

Telephone

: 027 11 7595
401

E
-
mail:


godfreym@strate.co.za



safe@strate.co.za




STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
3

of
39

1

Table of Contents

1

TABLE OF CONTENTS

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

3

2

J2EE TERMINOLOGY

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

4

3

P
RE
-
REQUISITES FOR INSTA
LLATION OF MMFE

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

6

3.1

A
PPLICATION
S
ERVER

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

6

3.2

J
AVA
R
UNTIME
E
NVIRONMENT

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

6

3.3

M
ESSAGING
/

Q
UEUE
D
EFINITIONS

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

6

3.4

D
ATABASE

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

7

3.5


N
AMING
&

JNDI

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

8

3.5

S
ECURITY AND
U
SER
A
DMINISTRATION

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

9

4

MMFE INSTALLATION

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

10

4.1

D
ATABASE
S
ETUP

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

10

4.2

MQ

C
ONFIGURATION

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

12

4.2.1

Setting up MQ from scratch

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

12

4.2.2

Setting up MQ for participants who are already connecting to Strate

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

14

4.3

JMSA
DMIN FOR
J
B
OSS

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

15

4.3.1

Setup

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

15

4.3.2

Running JMSAdmin

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

16

4.4

A
PPLICATION
S
ERVER
S
ETUP
................................
................................
................................
................................
......

18

4.4.1

JBoss

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

18

4.4.2

Webs
phere Application Server Setup

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

23

5

MMFE SETUP

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

38

6

INSTALLATION CHECKLI
ST

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

39




STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
4

of
39

2

J2EE Terminology


Application Server

This is software that has implemented the J2EE sp
ecification for hosting J2EE
applications.

An application server may host multiple applications in the same way that a DBMS
may host multiple databases.

Application servers are also referred to as Containers.

Some app
-
servers allow for the configuration of

multiple nodes on the same server,
these nodes may also be referred to as Containers.

Examples of application servers include:

WebSphere, WebLogic & JBoss.

JAR file

A JAR file is a collection of executable Java classes and resources such as images
and pr
operty files.

JAR files have the same format as ZIP files.

JAR is an acronym for Java Archive.

WAR file

A WAR file is a specialised JAR file that has a specific internal directory structure
and some mandatory files.

WAR is an acronym for Web Archive.

WAR
files contain HTML, JSP’s, Java Classes and deployment descriptors.

bAo⁆楬e

A渠bAo⁦il攠is⁡ sp散ialis敤⁊A删oil攠瑨tt⁨ s⁡⁳灥cific⁩湴敲湡e⁤ir散瑯ty⁳瑲畣瑵t攠
慮搠d潭攠e慮摡瑯ty⁦il敳.

bAo⁩s⁡渠ncr潮ym⁦潲⁅ot敲灲is攠erchiv攮

bAo⁦il敳⁣潮t慩渠nA删o
il敳I tA删oil敳⁡ 搠摥ploym敮t⁤ scri灴prs.

䑥灬oyme湴n䑥acri灴潲

A⁦il攠i渠nj䰠i潲o慴a瑨t琠t灥cifi敳⁴ 攠牵湴im攠e整ei湧s f潲⁊㉅b⁣潭灯湥湴n⸠.桥r攠
慲攠aw漠oa瑥t潲楥s ⁤ 灬oyme湴nd敳cri灴prs.

g㉅b⁳p散ific⁤ ploym敮琠摥scri灴prs whic栠hre⁵ 敤 by 慬l
A灰lic慴i潮⁓敲e敲e.

s敮摯r⁳灥cific⁤数loym敮琠t敳cri灴prs⁴桡琠tp散ify⁡ 摩ti潮慬 i湦潲o慴a潮⁦潲⁡o
灡r瑩cul慲aA灰lic慴io渠n敲eer.

gpm

g慶愠p敲v敲⁐慧eⰠIs⁡渠䡔䵌ik攠eil攠eh慴ais⁣潭灩le搠i湴n⁳敲el整ea湤 數散畴u搠dt
r畮⁴ m攮

p敲el整

A⁳灥ci慬is敤
gav愠al慳s⁴ 慴ais⁥ 散u瑥t i渠n敳灯湳攠t漠o⁲敱略s琠tr潭⁡ w敢
扲bws敲e

bg_

b湴nr灲楳攠eav愠_敡測nis⁡ g㉅b⁣潭灯湥湴n⁴ a琠tm灬敭敮瑳⁢ si湥ss
functionality. There are two types of EJB, namely session and entity beans. EJB’s
慲攠灡ck慧敤 i渠nA删oil敳 睩
瑨t摥ploym敮琠摥scri灴潲o.

p敳si潮⁂敡n

mr潶id敳⁡ s敲eic攠e湤 摯es 琠t敡l wit栠h敲eis瑥t琠d慴a.

p敳si潮⁢ 慮say 扥 p瑡t敦畬爠 瑡tel敳s.



STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
5

of
39

Entity Bean

Implements the persistence requirements for business objects including storing,
updating, deleting
and retrieval.

Entity beans can be implemented using either BMP or CMP.

BMP

Bean Managed Persistence is implemented by embedding the SQL statements into
the program.

CMP

Container Managed Persistence is implemented by specifying the SQL statements
in the

deployment descriptors for the container to execute at runtime.

JNDI

Java Naming and Directory Interface, is a service that allows objects to be mapped
to a namespace and retrieved and used at runtime.

JDBC

Java Database Connectivity, is an API that ena
bles Java programs to access and
manipulate databases, in much the same way that ODBC enabled database access
for other programming languages.

JMS

Java Messaging Service, is an API for messaging.

This API does for messaging what JDBC does for database acc
ess. Namely it
allows for a vendor neutral implementation that can be configured for a specific
messaging vendor implementation at runtime.




STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
6

of
39

3

Pre
-
requisites for Installation of
MMFE


3.1

Application Server

MMFE

is built as a J2EE v1.3 compliant application, an
d therefore requires that a

J2EE 1.3 compliant Application Server is present that
MMFE

can be deployed onto.


Application Servers that have been tested include:

JBoss 4.0.1

WebSphere 5.1


3.2

Java Runtime Environment

MMFE

has been built and tested using JDK 1.
4.2.


3.3

Messaging / Queue Definitions

The MM
FE application uses the JMS API for messaging.

This effectively means that any JMS compatible software can be used to implement
the messaging requirements
of MM
FE.

JMS compatible messaging products include MQ Serie
s, JBoss MQ, WebLogic MQ, SilverStream, and TIBCo etc.

However the messages th
at are being sent to and from MM
FE are SWIFT messages, and the application at the
other end of the queue will be delivering or receiving messages to and from SWIFT, the applicati
on at the other
end of the queue will therefore have to support the same messaging product.

The applications that handle SWIFT connectivity include:

SWIFT Alliance, Merva and MiNT.

The only messaging product supported by these applications is IBM’s MQ Seri
es,

now re
-
branded as WebSphere MQ.

The IBM Service Pack MA88 must be applied to MQ Series to enable JMS access.


It is possible to implement a custom application that interfaces with
MMFE

via JMS and communicates with the
SWIFT connectivity application vi
a a file based or other interface, however that is beyond the scope of this
document.


Handles to the queues are obtained via JNDI lookups, please see the section on JNDI & Naming.





STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
7

of
39

The queue naming convention has therefore adopted a new naming standard a
s follows:

Local Queues



MMFE
.ORDERS.IN



MMFE
.QUERIES.IN



MMFE
.RESPONSES.IN

Remote Queues



MMFE
.ORDERS.OUT



MMFE
.QUERIES.OUT

Local
Error Queue



MMFE
.ERROR.QUEUE


A runmqsc script “MMFE
_QDEF.txt” is supplied for the definition of the MQ Queues in the following di
rectory of
the
installation CD
:

/dist/mq/

3.4

Database

MMFE

uses Hibernate, and therefore requires that the Application Server has been configured with an
appropriate datasource.

The MM
FE application database design has avoided the use of column data
-
types tha
t are not supported in a
consistent manner across multiple databases, such as BOOLEAN, LONG VARCHAR and BLOB.

However two of the MM
FE tables require above average length VARCHAR columns,

some databases may require non
-
default options to be configured befor
e defining the database. For example
DB2 requires a table space to be defined with a page size of 32K.

The tables and columns mentioned above are:

BB_MSG_IN.BB_MSG VARCHAR(12288)

AG_SAFE_LOG.AG_MESSAGE VARCHAR(30000)


Databases that have been tested includ
e:

Microsoft SQL Server 2005

Sybase

PostgreSQL 8.0.1

Oracle 9i

DB2 UDB 7.0


The use of Hibernate means that the Application Server handles calls to the database on behalf of the application.

The mapping of Java types to the underlying database column type
s is normally achieved through the use of
Container configuration files and Vendor specific Application deployment descriptors.





STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
8

of
39

3.5

Naming & JNDI

Wherever possible the MM
FE
distribution

has been used as a qualifier, this has been applied to the databas
e,
queue names and JNDI entries.

The qualifier is as follows:

mmfeDist


As mentioned in the terminology, JNDI is a service that allows objects to be mapped to a namespace and
retrieved and used at runtime. The namespace is represented in a tree
-
like struct
ure, the nodes are referred to as
contexts, and the root is referred to as the initial context.


EJB’s are bound to a JNDI context; the cont
ext naming convention used by MM
FE is as follows:

ejb/strate/mmfeDist
/MailBean


This represents the JNDI
name of the

MailBean in the mmfeDist

application.

The JNDI names are specified in the Vendor Specific deployment descriptors, and the EJB are bound to the
specified names at deploy time.


The handle to the Queue Manager and Queues are also obtained via JNDI lookups.

The names used by
MMFE

are as follows:

jms/mmfeDist
_XAQueueConnectionFactory

jms/mmfeDist
_ORDERS_IN

jms/mmfeDist
_ORDERS_OUT

jms/mmfeDist
_QUERIES_IN

jms/mmfeDist
_QUERIES_OUT

jms/mmfeDist
_RESPONSES_IN

jms/mmfeDist
_ERROR_QUEUE


These JNDI entries must exist b
efore the application is deployed.

The names are case sensitive.

The properties of the JMS objects are defined by the JNDI entry,

e.g. Queue Manager name, Queue Name etc.


MQ Series Service Pack MA88 includes a command line tool JMSAdmin, that is used to c
reate JNDI administered
JMS objects.

A JMSAdmin script “mmfe
_MQJMS.scp” is supplied for the definition of the J
MS Objects that are used by MMFE
.
This script can be found in the follow
ing directory on the installation CD
:

/dist/jms/




STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
9

of
39

The

3.5

Security and User
Administration

The MMFE application uses the same security and roles as the SAFE application.
The J2EE platform has built in
security and role func
tionality that is now used by MM
FE.

Security has been externalised, user ID’s are created
once for all applic
at
ions on the application server.
Additional roles can be defined and applied to the application
without source
-
code modification.


Security constraints can be applied from two tiers:

The web tier in the /WEB
-
INF/web.xml file.

The EJB tier in the /META
-
INF
/ejb
-
jar.xml file.


MM
FE has not restricted access to any methods in the EJB tier.

Access restrictions have be defined in the web tier, using the following roles

SAFE_User, SAFE_Admin

SAFE_Creater
,
SAFE_Updater
,

SAFE_Deleter
,
SAFE_Releaser
,

SAFE_Transmit
ter
,
SAFE_IA_User
,

S
AFE_MC_User
,
S
AFE_TR_User


The restrictions prevent unauthenticated users from logging into the
MMFE

application, and allow only
SAFE_Admin users to access the Admin/system URL.

The SAFE_Admin role has also been applied to various
acti
on buttons, resulting in the restriction of SAFE_User access to functions such as delete.

SAFE_[FLAVOUR]
_User

is used to give access to safes different flavours (Trader, Issuing agent).



STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
10

of
39

4

MMFE

Installation

This section describes the steps for setting up the
MMFE application for both Websphere Application Server v 5.1
and Jboss 4.0.1.

4.1

Database Setup

The scripts for creating the tables and indexes for the database can be found in the following directory on the
installation CD:
dist
\
ddl
\
<database>.


Follow the
instruction below for your specific database.

MSSQL SETUP:

1. create new db MMFE

2. create new login (Security/Logins):


-

Name: mmfeDistUser


-

SQL Server Authentication, password: password


-

Database: MMFE


-

Database Access tab:


*

permit user d
b_owner on MMFE

3. Log on us
ing Query Analyzer, user: mmfeDist
User, password: password

4. Check that y
our selected database is MMFE

5. Copy create script

(
mmfe
_mssql_create.sql
)


-

Rename [your_database_owner]
---
>
mmfeDist
User


-

run

6
. Clear screen & c
opy index script (
mmfe
_mssql_indexes.sql
)


-

Rename [
your_database_owner]
---
> mmfeDist
User


-

run

7
. Clear screen & copy index script (
mmfe
_mssql_
data
.sql
)


-

Rename [
your_database_owner]
---
> mmfeDist
User


-

run



DB2 SETUP

1. C
reate new db MMFE

2.
Create a user called mmfeDist
User and assign the right authorities.

3. Go to Command Center

and logon to MMFE

4. Copy create script (
mmfe
_
db2
_create.sql
)


-

Rename
database_name

---

> MMFE


-

Rename your_database_owner

---
> mmfeDist
User


-

Rename
table_
space

---

> to your selected table space name


-

run

5
.
Clear screen & copy index script (
mmfe
_
db2
_indexes.sql
)


-

Rename
your_database_owner]
---
> mmfeDist
User


-

run


6
. Clear screen & copy index script (
mmfe
_db2
_
data
.sql
)


-

Rename your_database_own
er

---
> mmfedist
User


-

run


ORACLE SETUP

1.
create new db MMFE

2.
Create a user called mmfeUser
User and assign the right roles.

3. Go to Oracle SQL Command



STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
11

of
39

4. Copy create script (
mmfe
_
oracle
_create.sql
)


-

Change the connection string Connect <userNam
e>/<password>
@
<SERVICE NAME>


-

run

6. Clear screen & copy index script (
mmfe
_
db2
_indexes.sql
)


-

Rename [
your_database_owner]
---
> mmfeDist
User


-

run


7. Clear s
creen & copy index script (mmfe
_oracle
_
data
.sql
)


-

Rename [
your_database_owner]
---
> mmf
eDist
User


-

run


SYBASE SETUP

1. create new db MMFE

2. Create a user called mmfeDist
User and assign the right roles.

3. Open Sybase SQL command

4. Copy create script (
mmfe
_sybase_create.sql
)


-

run

6. Clear screen & copy index script (
mmfe
_
sybase
_in
dexes.sql
)


-

run

7. Clear s
creen & copy index script (mmfe
_
sybase
_
data
.sql
)


-

run



STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
12

of
39


4.2

MQ Configuration

4.2.1

Setting up MQ from scratch


You can configure your MQ using the comman
d line or Websphere MQ Explorer

MQ
configuration

through the command line

(Both
Windows and Linux)

COMMAND LINE SETUP


1.

Create a queue manager

Type
crtmqm
-
t 999999999
-
h 51
2
-
u SYSTEM.DEAD.LETTER.QUEUE
[
QMAN NAME
]

2.

Create the channels


Open
dist
\
mq
\
CHLDEF_MMFE
.txt


Replace

[BIC_8]
with

your eight character bic code
.

Depending on whether
you are connecting to Strate through Wan or Swift, your channels will
either point to
196.23.98.33
or to your swift MQ. If you are going through Swift, you must speak
to your Swift resource for assistance. Also the channel names might be different depending

on
how it is
set up

on
your
Swift.

Make the changes accordingly.


Save the file.


Go to the <MQ>
\
bin directory


Type

runmqsc

[
QMAN NAME
]

< [directory path]
\
CHLDEF_MMFE
.txt

and press Enter


Check for errors and confirm that all the queues and channels have
been created.

3.

Create the queues


Open
dist
\
mq
\
QDEF_MMFE
.txt


Replace

[BIC_8]
with

your eight character bic code
.


The following properties on the remote queue definitions will depend on whether you are going
through Swift or Wan. Again, If you are going throu
gh Swift, speak to your Swift resource for the correct
properties.

i.

RQMNAME(GATEWAY.TEST
)

ii.

RNAME(GATEWAY.QC.[BIC_8].TO.MMS
)

iii.

XMITQ([BIC_8].TO.GW
A
Y.TST
.XMITQ)


Save the file


Type
runmqsc
[
QMAN NAME
]

< [directory path]
\

QDEF
_MMFE
.txt

and press Enter


Check for
errors and confirm that all the queues have been created.





STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
13

of
39


MQ configuration through the Websphere MQ Explorer (Windows)

WEBSPHERE MQ EXPLORER

1.


Create a queue manager called [QMAN NAME
]

1.1
Dead Letter Queue:
SYSTEM.DEAD.LETTER.QUEUE

1.2 Max H
andle Limit: 512

or 1000


Depending on whether you are connecting to Strate through Wan or Swift, your channels will
either point to
196.23.98.33

or to your swift MQ. If you are going through Swift, you must speak
to your Swift resource for assistance. Als
o the channel names might be different depending on
how it is set up on your Swift. Make the changes accordingly.


2.


Create a transmission queue named
[BIC_8]
.
TO.GWY.TST.XMITQ
with the following attributes:

2.1.


Usage: Transmission

2.2.



Trigger Data:
[BIC_8]
.TO.G
WAY.TEST

(this is the name of the sender channel you’ll be
cr敡瑩湧⁳桯r瑬yF

㈮㌮
† †

f湩tial⁑略略⁎慭e㨠Wvpqb䴮j䡁乎bi⹉义.n


††††

䍲e慴a 愠a敮d敲⁣h慮湥l慭敤
孂䥃f㡝
⹔l⹇
tAv⹔bpq

wi瑨t瑨t⁦ollo睩湧⁡ 瑲i扵瑥tW

㌮ㄮ



C潮n散瑩o渠乡m攺e
ㄹ㘮㈳⸹㠮8㌠
E
ㄴㄷ
F㬠瑨is⁩s⁴ 攠e慣桩湥 C⁰潲琠瑨攠e潲r敳灯湤i湧
r散敩v敲⁣桡n湥l⁩s lis瑥湩n朠gn

㌮㈮
† †

qr慮smissi潮⁑略略㨠
x_䥃f㡝
⹔l.
dtv.qpq.u䵉jn


††††

䍲ea
瑥t愠牥a敩v敲⁣桡湮敬 湡m敤⁇
t
Av⹔bpq
.ql.

[BIC_8]

with default a
ttributes.

5.


Create a server connection channel named

[BIC_8]
.CHANNEL with default attributes. This
channel will be used by the MQ client to talk to this MQ server.

6.


Create the following local queues:

6.
1.


MMFE
.ORDERS.IN;

6.2.



MMFE
.QUERIES.IN;

6.3.


MMFE
.RESPONSES.IN;

6.4.


MMFE
.
ERRORS.QUEUE;

7.


Create the following remote queues:

7.1.


MMFE
.ORDERS.OUT;

7.2.


MMFE
.QUERIES.OUT;

7.3
.


Both these queues should have the following attributes:

7.5.1.



Remote Queue Name: GATEWAY.QC
.

[BIC_8]
.TO.
MMS

7.5.2.


Remote
Queue Manager Name: GATEWAY.TEST

7.5.3.


Transmission Queue Name:
[BIC_8]
.TO.
GWY.TST.XMITQ

8.


Create a queue manager alias named GATEWAY.
TEST
. This is to accommodate possible COA
(Confirmation of Arrival) & COD (Confirmation of Deli
very) requests from GATEWAY.TEST
. You create a
queue manager alias the same way as creating a remote queue except for supplying a Remote Queue
Name. This queue manager alias should have the following att
ributes:

8.1.


Remote
Queue Manager Name: GATEWAY.TEST

8.2.


Transmission Queue:
[BIC_8]
.TO.
GWY.TST.XMITQ

9.


Create the following local user & group:

9.1.


Create a local group called mqm

9.2.


Create a user called gateway (with

any password) and add this user to the mqm group

9.3.


This is also to accommodate possible COA (Confirmation of Arrival) & COD
(Confirmation of Deli
very) requests from GATEWAY.TEST
.







STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
14

of
39

4.2.2

Setting up MQ for participants who are already connecting to S
trate

Command line
configur
ation for Windows and Linux. Be
cause your are already connecting

to Strate, your Queue
Manager Name, Remote Qu
eue Name
Transmission Queue Name
and Channels
won

t change.
Check your
current test

setup for the correct values.

COMMA
ND LINE SETUP

1.

Open
dist
\
mq
\
QDEF_MMFE
.txt

1.1

If you are connecting to Strate through Swift, change the remote queue properties accordingly.

1.1.1

Wan

1.1.1.1

Remote Queue Name:

RNAME
(
[YOUR CURRENT TEST

REMOTE QUEUE NAME]
)

1.1.1.2

Remote Queue Manager Name:
RQMNAME(
GATEWAY.TEST
)

1.1.1.3

Tra
nsmission Queue Name:
XMITQ(
[YOUR CURRENT TEST

TRANSMISSIN QUEUE NAME]
)

1.1.2

Swift

1.1.2.1

Remote Queue Name:
RNAME
(
[YOUR CURRENT TEST

REMOTE QUEUE

NAME])

1.1.2.2

Remote Queue Manager Name:
RQMNAME
(
[
YOUR CURRENT TEST

REMOTE QUEUE
MANAGER
NAME])

1.1.2.3

Transmission Queue Name

XMITQ(
[
Y
OUR CURRENT TEST
TRANSMISSION QUEUE
NAME]
)

1.2

Save the file.

2

Go to <MQ>
\
bin directory

3

Type
runmqsc [
QMAN NAME
] <
[directory path]
\
QDEF_MMFE
.txt

4

Check for errors and confirm that all the queues have been created and are pointing to the right place.



WEBSPHERE MQ EXPLORER

1

Create the following local queues:

1.1

MMFE
.ORDERS.IN

1.2

MMFE
.ORDERS.IN

1.3

MMFE
.RESPONSES.IN

1.4

MMFE
.ERRORS.QUEUE

2

Create the following remote queues

2.1

MMFE
.ORDERS.OUT

2.2

MMFE
.QUERIES.OUT

2.3

Both these queues should have the following attributes

2.3.1

Wan

2.3.1.1

Remote

Queue Name:
[YOUR CURRENT TEST

REMOTE QUEUE NAME]

2.3.1.2

Remote
Queue Manager Name: GATEWAY.TEST

2.3.1.3

Transmission Queue Name:
[YOUR CURRENT TEST

TRANSMISSIN QUEUE
NAME]

2.3.2

Swift

2.3.2.1

Remote Queue Name:
(
[
YOUR CURRENT TEST

REMOTE QUEUE
NAME])

2.3.2.2

Remote Queue Manager Name:
(
[
YOU
R CURRENT TEST

REMOTE QUEUE

MANAGER

NAME])

2.3.2.3

Transmission Queue Name:
XMITQ(
[
YOUR CURRENT TEST

TRANSMISSION
QUEUE NAME]
)





STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
15

of
39

4.3

JMSAdmin for JBoss

4.3.1

Setup

For JMSAdmin to work, the MQ client must be installed on the same box as the JBoss application server.


Edi
t JMSAdmin.config file.
Make sure that the properties below are the only properties that are not commented
out. Replace [JNDI PATH] with the path your are going to use for JBoss.

INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory

PROVIDER_U
RL=file:///
[JNDI PATH]

SECURITY_AUTHENTICATION=none


Edit your JMSAdmin file and add the following lines:
Make sure that these jar files are in the
MQ_JAVA_INSTALL_PATH
\
lib
\

directory.


1.
Windows

set MQ_classpath=
%
MQ_JAVA_INSTALL_PATH
%
\
lib
\
com.ibm.mq.ja
r

set MQ_classpath=%MQ_classpath%;
%
MQ_JAVA_INSTALL_PATH
%
\
lib
\
com.ibm.mqjms.jar

set MQ_classpath=%MQ_classpath%;
%
MQ_JAVA_INSTALL_PATH
%
\
lib
\
jms.jar

set MQ_classpath=%MQ_classpath%;
%
MQ_JAVA_INSTALL_PATH
%
\
lib
\
jndi.jar

set MQ_classpath=%MQ_classpath%;
%
MQ_JAVA_I
NSTALL_PATH
%
\
lib
\
connector.jar

set MQ_classpath=%MQ_classpath%;
%
MQ_JAVA_INSTALL_PATH
%
\
lib
\
fscontext.jar

set MQ_classpath=%MQ_classpath%;
%
MQ_JAVA_INSTALL_PATH
%
\
lib
\
providerutil.jar


2. Linux

export MQ_JAVA_INSTALL_PATH="
[MQ PATH]
"

if [ "x$
MQ_classpath
" = "
x" ]; then



MQ_classpath
="$MQ_JAVA_INSTALL_PATH/bin:


$MQ_JAVA_INSTALL_PATH/lib/jms.jar:


$MQ_JAVA_INSTALL_PATH/lib/jndi.jar:




$MQ_JAVA_INSTALL_PATH/lib/com.ibm.mq.jar:


$MQ_JAVA_INSTALL_PATH/lib/com.ibm.mqjms.jar:


$MQ_JAVA_I
NSTALL_PATH/lib/fscontext.jar:


$MQ_JAVA_INSTALL_PATH/lib/providerutil.jar:


$MQ_JAVA_INSTALL_PATH/lib/connector.jar"

fi


3
.
add string

below, i
n
sert it between the word java and the word
-
DMQJMS_LOG_DIR

Windows:
-
cp %MQ_classpath%


L
inux:

-
classpath "$
MQ_classpath
"



STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
16

of
39

4.3.2

Running JMSAdmin

1

Open dist
\
jms
\
MMFE
_MQJMS.scp

1.1

JBoss and MQ running on the same box

1.1.1

Replace [QMAN NAME] with the actual queue manager name

# define a queue connection factory

def QCF(mmfedist
_QueueConnectionFactory) QMANAGER([Q
MAN NAME])

# define a xa queue connection factory

def XAQCF(mmfeDist
_XAQueueConnectionFactory) QMANAGER([QMAN NAME])


1.1.2

Remove the text below

# define a queue connection factory

def QCF(mmfeDist
_QueueConnectionFactory) HOSTNAME([CLIENT_MQ_BOX])
PORT([CLIENT
_MQ_BOX_LISTENER_PORT]) TRANSPORT(CLIENT)
CHANNEL([CHANNEL NAME])

# define a xa queue connection factory

def XAQ
CF(mmfeDist
_XAQueueConnectionFactory)
HOSTNAME([CLIENT_MQ_BOX]) PORT([CLIENT_MQ_BOX_LISTENER_PORT])
TRANSPORT(CLIENT) CHANNEL([CHANNEL NAME])


1.2

Running on separate boxes

1.2.1

Replace the following properties

1.2.1.1

Host name: [CLIENT_MQ_BOX]

1.2.1.2

Listener Port: [CLIENT_MQ_BOX_LISTENER_PORT]

1.2.1.3

Server Connection Channel name: [CHANNEL NAME]

# define a queue connection factory

def QCF(mmfeDist
_QueueConnectionFactory) H
OSTNAME([CLIENT_MQ_BOX])
PORT([CLIENT_MQ_BOX_LISTENER_PORT]) TRANSPORT(CLIENT)
CHANNEL([CHANNEL NAME])

# define a xa queue connection factory

def XAQCF(mmfeDist
_XAQueueConnectionFactory)
HOSTNAME([CLIENT_MQ_BOX]) PORT([CLIENT_MQ_BOX_LISTENER_PORT])
TRANSPO
RT(CLIENT) CHANNEL([CHANNEL NAME])


1.2.2

Remove the following text

# define a queue connection factory

def QCF(mmfeDist
_QueueConnectionFactory) QMANAGER([QMAN NAME])

# define a xa queue connection factory

def XAQCF(mmfeDist
_XAQueueConnectionFactory) QMANAGER([
QMAN NAME])



STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
17

of
39


1.3

Save the file

2

Go to MQ client bin folder [directory path]
\
java
\
bin

3

Type JMSAdmin < [directory path]
\
MMFE
_MQJMS.scp

4

Check for errors



STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
18

of
39

4.4

Application Server Setup

4.4.1

JBoss

You have two options on how you can setup your JBoss. You can either elect to

set it up from scratch or
you can
copy your current SAFE

JBoss.


4.4.1.1

Configuring from Scratch

1

Create a directory on your server
and call it java

2

Copy
dist
\
jboss
\
jboss
-
4.0.1
.zip to the java directory and extract it

there
.
Your JBoss path should look
something

like:
\
java
\
jboss
-
4.0.1

3

Go to the directory

\
java
\
jboss
-
4.0.1
\
server
\
mmfeDist

3.1

\
cp

mmfeDist
-
hibernate.cfg.xml
.<database name>
-

rename the file for your database from
mmfeDist
-

hibernate.cfg.xml
.<Database Name> to
mmfeDist
-
hibernate.cfg.xml


3.2

\
deploy

mmfeDi
st
-
<Database Name>
-
ds.xml

-

Delete mmfeDist
-
<Database Name>
-
ds.xml

files for the
databases that you are not using. Eg. If you database is MQSQL, delete
mmfeDist
-
db2
-
ds.xml
,
mmfeDist
-
oracle
-
ds.xml
, and
mmfeDist
-
sybase
-
ds.xml
. You’ll only keep
mmfeDist
-
mss
ql
-
ds.xml
.






STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
19

of
39


4.4.1.2

Copy safeDist

JBoss

1

Copy your safeDist

JBoss
-
4.0.1 to the java directory

2

Rename the directory

\
java
\
jboss
-
4.0.1
\
server
\
safeDist

to

\
java
\
jboss
-
4.0.1
\
server
\
mmfeDist

3

Go to the directory

\
java
\
jboss
-
4.0.1
\
server
\
mmfeDist

4.1

\
cp

Rename the fil
e
safeDist
-
hibernate.cfg.
xml to mmfeDist
-
hibernate.cfg.xml

Edit mmfeDist
-
hibernate.cfg.xml change:

<property name="con
nection.datasource">java:/safeDist
_DS</property>

to

<property name="con
nection.datasource">java:/mmfeDist
_DS</property>

4.2

\
deploy

Rename
the file safeDist
-
<database Name>
-
ds.xml

to mmfeDist
-
<database Name>
-
ds.xml

Delete safeDist
-
<version>.ear

4.3

\
deploy
\
jms

4.3.1
Edit jms
-
ds.xml

and replace safeDist with mmfedist
.

4.3.2

Rename
safeDist
-
mq
-
service.xml

to mmfeDist
-
mq
-
service.xml

Edit mmfeDist
-
mq
-
se
rvice.xml

and replace
safeDist with mmfeDist

4.3.3

Rename
Q3
-
mq
-
destinations
-
service.xml

to QC
-
mq
-
destinations
-
service.xml

Edit

QC
-
mq
-
destinations
-
service.xml

and replace
safe
Dist with mmfeDist
.

4.4

\
log

Delete everything in this directory.

4.5

\
temp


Delete eve
rything in this directory.

4.6

\
work


Delete everything in this directory.




STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
20

of
39


4.4.1.3

Configuring JBoss

1 Go to the directory

\
java
\
jboss
-
4.0.1
\
server
\
mmfeDist

1.1
\
conf


1.1.1 Edit
ext_jndi.properties



Change the JNDI PATH to point t
o JNDI directory you created when


you were setting up JMSAdmin

java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory

java.naming.provider.url=file:///
<
JNDI PATH
>

1.1.2

Log4j.xml



We’ve sent you a log4j.xml file, which

you need to c
opy to this directory
,
replacing
the one that’s in this directory.

1.1.3

login
-
config.xml



Edit this file only if you want to authenticate your users through Active
Directory
:

1.
Remove the existing login
-
module under other “should be the last one in the fi
le”


search for:
<application
-
policy name = "other">

2. Add the following


<login
-
module code="org.jboss.security.auth.spi.LdapLoginModule" flag="required">



<module
-
option name="debug">true</module
-
option>



<modul
e
-
option name="java.naming.provider.url">ldap://domainController.company.co.za:389</module
-
option>



<module
-
option name="java.naming.factory.initial">com.sun.jndi.ldap.LdapCtxFactory</module
-
option>



<module
-
option name="java.
naming.security.authentication">simple</module
-
option>



<module
-
option name="rolesCtxDN">OU=Users,OU=IT,DC=company,DC=co,DC=za</module
-
option>



<module
-
option name="uidAttributeID">userPrincipalName</module
-
option>




<module
-
option name="roleAttributeID">memberOf</module
-
option>



<module
-
option name="roleAttributeIsDN">true</module
-
option>




<module
-
option name="roleNameAttributeID">name</module
-
option>



<module
-
option n
ame="matchOnUserDN">true</module
-
option>



<module
-
option name="principalDNSuffix">@company.co.za</module
-
option>



</login
-
module>

3. Save the file


1.1.4


1.2
\
cp


1.2.1 users.properties
-

Copy the users.proper
ties file from your old Safe JBoss to this directory.


1.2.2 roles.properties
-


you’ll need to configure the roles for all the users in the


Users.properties file. Read section 3.5 above for the available roles
.

1.3
\
deploy


Edit mmfeDist
-
<database Name>
-
ds.xml


Database URL:
<connection
-
url><
/
connection
-
url>

-

Make sure it is pointing to the right box
and the right database.

Database user name : <user
-
name>user
-
name</user
-
name>
-


Database pass
word: <password>password</password>




Copy
\
dist
\
ears
\
jboss
\
[windows or linux]
\
mmfeDist
-
<version>.ear to this directory.



1.5

\
deploy
\
jms



STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
21

of
39


Edit jms
-
ds.xml and make sure the <JNDI PATH> is pointing to the correct
JNDI directory.


<attribute
name="Properties">java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory


java.naming.provider.url=file:/<JNDI PATH>



2 Go to
\
ja
va
\
jboss
-
4.0.1
\
server
\
mmfeDist


2.1
\
bin

2.1.1 Linux



Create a shell file to start JBoss: startJboss.sh

export JBOSS_HOME=<JBOSS HOME PATH>
/jboss
-
4.0.1

export WORKDIR=$JBOSS_HOME/bin

echo backing up nohup.out [$WORKDIR/nohup.out]

rm $WORKDIR/nohup.out

cd $WORKDIR

nohup ./run.sh

c mmfeDist

&




Create a shell file to stop JBoss: startJboss.sh

export JBOSS_HOME
=<JBOSS HOME PATH>
/jboss
-
4.0.1

export WORKDIR=$JBOSS_HOME/bin

echo Shutting Down $WORKDIR/shutdown.sh
--
server=localhost:8888
-
S

$WORKDIR/shutdown.sh
--
server=localhost:8888

S





Memory Setting: Edit run.sh.

The memory setting will depend on the amount of memory on your box

Change:

# Setup JBoss sepecific properties

JAVA_OPTS="$JAVA_OPTS
-
Dprogram.name=$PROGNAME"


To

# Setup JBoss sepecific properties

JAVA_OPTS="$JAVA
_OPTS

-
Xms128m

Xmx
512
m

-
Dprogram.name=$PROGNAME"


2.1.2

Windows

Edit run.bat and add the memory setting below.

Add it just above this line:

set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%
\
lib
\
endorsed

rem Sun JVM memory allocation pool parameters. Modify as appropria
te.

set JAVA_OPTS=%JAVA_OPTS%
-
Xms128
m
-
Xmx512m



Creat
e a start JBoss bat file: mmfeDist
.bat

set JAVA_HOM
E=[Directory Path]
\
j2sdk1.4.2

run
-
c mmfeDist






STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
22

of
39

4.4.1.4

Run JBoss

Linux

startJboss.sh


Windows

Run mmfeDist
.bat



STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
23

of
39

4.4.2

Websphere Application Serv
er Setup

4.4.2.1

Installing Websphere

The important thing you need to remember when install
ing

Websphere Application Server
5.1
, is that you need to
do a custom install.
Under the custom tab,
make sure that Embedded Messaging is checked and
only Client Only
is che
cked.


4.4.2.2

Installing Patches for Websphere Application Server 5.1

The patches are located in
\
dist
\
was
\
patches

directory on the installation CD. Install the relevant patches for your
operating system.

Before running the patches, make sure that the following
services are stopped:



䥂䴠䡔TP⁓敲e敲



䥂䴠W敢s灨敲攠e灰lic慴io渠n敲v敲



We扳灨敲攠䵑
if⁩湳瑡ll敤 ⁴桥⁳慭攠e潸⁡ ⁴ 攠ep灬ica瑩o渠n敲e敲e




Wi湤潷s⁐慴ah敳

ㄮ1

Was㔱0
-
jdk
-
wi渮z


ㄮㄮ1

啮zi瀠p桥 W慳㔱0
-
jdk
-
wi渮zi瀠p漠愠air散瑯ty 潮 yo畲⁳敲e敲

ㄮㄮ1

䥮I瑡tl⁴ 攠ei灡ck
by⁲畮nin朠
異摡瑥Wiz慲搮a慴
.

ㄮㄮ1

S敬散琠䥮s瑡ll⁦i灡cks.

ㄮ1

睡w㔱0彣f㕟睩渮zip

ㄮ㈮1

畮zi瀠
睡w㔱たcf㕟wi渮zip

ㄮ㈮1

䥮I瑡tl⁴ 攠ei灡ck⁢y⁲畮nin朠
異摡瑥Wiz慲搮a慴

ㄮ㈮1

S敬散琠䥮s瑡ll⁦i灡cks



䱩n畸⁐慴ah敳

㈮2

睡w㔱0彪摫彬i湵.zip

㈮ㄮ2

啮zip

睡w㔱0彪摫彬i湵.zip

㈮ㄮ2

䥮I瑡tl⁴ 攠ei灡ck⁢y⁲
畮nin朠
異摡瑥Wiz慲搮ah

㈮ㄮ2

S敬散琠t湳瑡tl⁦i灡cks

㈮2

睡w㔱0彣f㕟li湵.zip

㈮㈮2

啮zi瀠
睡w㔱0彣f㕟li湵.zip

㈮㈮2

䥮I瑡tl⁴ 攠ei灡ck⁢y⁲畮nin朠
異摡瑥Wiz慲搮ah

㈮㈮2

S敬散琠t湳瑡tl⁦i灡cks


4.4.2.3

mmfeDist

configuration setup for Websphere Application Server 5.1

Copy the directory
\
di
st
\
was
\
mmfeWasDist

to somewhere on your server.

Go to the directory [Directory Path]
\
mmfeWasDist

Rename
mmfeDist
-
hibernate.cfg.xml
.<Your Database Name>
mmfeDist
-
hibernate.cfg.xml

and delete the
other
mmfeDist
-
hibernate.cfg.xml
.<Other Database Name File>.




STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
24

of
39

4.4.2.4

MSSQL setup

If you are running Microsoft SQL

Server Database, you need to do the following setup:

Go to
\

dist
\
was
\
mssql

1

\
lib

1.1

Copy the *.jar files to a directory on your Websphere Application Server box.


2

\
mssql
SQLServer JTA

2.1

C
opy file sqljdbc.dll to SQL S
erver’s ‘Binn’ folder
⸠.朠

y
mr潧r慭⁆楬敳
y
jicr潳潦琠
pn䰠p敲e敲
y
jppni
y
_i湮

㈮2

創渠scri灴

i湳瑪摢c⹳ql ⁓n䰠i敲v敲⁡e⁳a


If you are running MS SQL Server on a Windows 2003 operating system, You’ll need to configure your server to
allow XA transaction. Foll
ow the instructions blow:


1. Open Component Services. (Start

S整ei湧s

䍯湴r潬 P慮敬


A摭i湩s瑲慴av攠e潯ls


䍯C灯湥n琠
S敲eic敳)

㈮2Exp慮搠瑨t 瑲敥 view⁴漠o潣慴a⁴桥⁣潭灵瑥爠w桥r攠you w慮琠瑯 瑵牮渠n異灯rt⁦潲⁘A⁴牡湳慣瑩o湳
f潲o
數慭灬攬eMy 䍯C灵瑥爩
.

㌮3剩杨t
-
click⁴ 攠e潭灵瑥爠湡t攬e慮搠dh敮⁣lick⁐r潰er瑩敳.

㐮4䍬ick⁴ 攠eS䑔䌠瑡CⰠ,n搠d桥渠nlick⁓散畲楴y⁃潮fig畲慴uo渮

㔮5啮摥r⁓散畲楴y S整ei湧sⰠclick⁴ ⁳敬散琠瑨攠e桥ck⁢ x⁦潲⁘A Tr慮s慣瑩潮s⁴ 瑵t渠n渠瑨ts⁳u灰潲琮

㘮6O灥渠䍯mm慮搠di湥

㜮7Typ
攠牥来dit

8

C
r敡t攠e⁲敧is瑲y慭敤
-
val略 畮d敲⁴e攠e潬lowi湧⁲e杩s瑲yey㨠

††
䡋EY彌OCAL彍A䍈䥎E
\
SOFTWA剅
\
䵩cr潳潦t
\
MS䑔C
\
XA䑌D

㤮9䥮Iyo畲⁲敧is瑲y慭敤
-
v慬u攬e乡N攠es⁴ 攠eil攠湡m攠ef⁴ 攠eA⁄䱌
:

sqlj摢c⹤ll

,⁔y灥⁩s S瑲in朠⡒䕇_SZ)Ⱐ
慮搠d桥 val略⁩
s⁴ 攠e畬l⁰ t栠h慭攠e
E朠䌺
\
Pro杲慭⁆楬敳
\
䵩cr潳潦琠tQ䰠S敲v敲
\
MSSQL
\
Bi湮
\

s煬j摢c.摬l
)
瑨t⁄䱌⁦il攮

㄰⸠
G漠扡ck⁴ ⁃潭灯湥湴nS敲eic敳

ㄱ⸠.i杨琠tlick ⁴ 攠e潭灵瑥爠湡t攬e慮搠dlick⁳瑯t⁍S⁄ C

ㄲ⸠.i杨琠tlick ⁴ 攠e潭灵瑥爠湡t攬e慮搠dlick⁳瑡牴⁍t
䑔C

4.4.2.5

Websphere Administration Console

Startup your Websphere Application server and login to Websphere Administration Console





STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
25

of
39

4.4.2.6

Manage Websphere Variables

Click Environment and select Manage Websphere Variables.

1

MMFE
_WAS_CP

Create a new variable. The valu
e should point to the
directory: [Directory Path]
\
mmfeWasDist

you
setup earlier in 4.5.3.


2

Database specific Drivers


MSSQL Server


MSSQLSERVER_JDBC_DRIVER_PATH

should point to where you copied the jar to. Refer to
4.5.4.


DB2


DB2_JDBC_DRIVE
R_PATH

should point to the jdbc driver for DB2.


Oracle


ORACLE_JDBC_DRIVER_PATH

should point to the jdbc driver for Oracle.


Sybase


SYBASE_JDBC_DRIVER_PATH

should point to the jdbc drive for Sybase

3

MQ


MQJMS_LIB_ROOT

should be pointing to:
$
{MQ_INSTALL_ROOT}/java/lib


MQ_INSTALL_ROOT

should be pointing to the MQ install directory: <Path>
\
IBM
\
WebSphere MQ



STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
26

of
39

4.4.2.7

Servers

Click Server


Application Servers

1

Create a new Server

-

Click Servers > Application Servers > New:

-

Server name:

-

Click Next > Finish

-

Save changes

2

Logging and Tracing


Diagnostic Tracing Service


䍨C湧e⁡ c潲摩湧ly

†††† ††† ††
qr慣攠e灥cific慴ao渠nmf攪=慬l=敮慢l敤

†††† ††† †††
qr慣攠併瑰畴u⁍ k攠e桥散敳s慲y⁨慮g敳


P

qr慮s慣瑩潮⁓敲eice

p整et桥

q潴ol⁴牡湳慣ti潮i
f整em攠eim敯畴u慮d⁴ e⁃ ien琠tn慣瑩vity⁴im敯畴u

Q

䵥ss慧攠䱩s瑥湥r p敲eic攠e


Lis瑥t敲eP潲瑳



䍬ick⁓敲e敲e >⁁灰lic慴io渠S敲e敲e‾mf敓敲e敲e>⁍敳s慧攠eis瑥t敲⁓ervice‾ 䱩s瑥t敲⁐潲瑳



䑥Di湥⁴桥⁌is瑥t敲⁐潲瑳

o

OrderMsgListenerBeanPortQC


Name: Orde
rMsgListenerBeanPortQC

Initial State:Started

Connection factory JNDI name:jms/mmfeDist_XAQueueConnectionFactory

Destination JNDI name:mmfeDist_ORDERS_IN


o

QueryMsgListenerBeanPortQC


Name: QueryMsgListenerBeanPortQC

Initial State:Started

Connection fa
ctory JNDI name:jms/mmfeDist_XAQueueConnectionFactory

Destination JNDI name:mmfeDist_QUERIES_IN


o

ResponseMsgListenerBeanPortQC


Name: ResponseMsgListenerBeanPortQC

Initial State:Started

Connection factory JNDI name:jms/mmfeDist_XAQueueConnectionFacto
ry

Destination JNDI name:mmfeDist_RESPONSES_IN




Sav攠e桡湧敳⁡ 瑥爠敡t栠h敦i湩ti潮


5

Pr潣敳s⁄敦i湩tio渠n


J慶愠Vir瑵慬 䵡chi湥

㐮4††䍬慳s灡瑨t ⁒数l慣攠[灡瑨t wit栠hh攠ec瑵慬 灡t栮


㐮4

G敮敲楣⁊V䴠Mrg畭敮瑳††(䵥m潲y⁓整ei湧s)


q桥 j敭潲y⁳整ei湧 睩ll 摥p
敮d渠no眠w畣栠y潵r
mac桩湥 桡s.


㘠S
sir瑵tl⁈潳琠t整epW

†††
Click⁖ir瑵慬⁈潳瑳‾⁎ewW

†††† ††
††††

†† †

J

乡k攺emmfe
p敲e敲彨潳t

††††
䍬ick⁏h



STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
27

of
39


Click Virtual Hosts > mmfe
Server_host > Host Aliases; define

the following



(NOTE: look at your default_host's aliases, the below should normally just increment


default_host's ports by 1; just make sure they're unique within your installation,


else use other port numbers as

needed):

-

Host Name: *, Port: 9081

-

Host Name: *, Port: 81

-

Host Name: *, Port: 9444

-

Save changes

-

Click Application Servers > mmfeServer > Web Container;


set Default virtual host to mmfeServer_host

-

Click OK

-

Save changes






STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
28

of
39

4.4.2.8

Resources

a)

Websphere MQ J
MS Provider

Fill in / browse the Node & Server fields & click Apply; click WebSphere MQ





Queue Connection Factories


Websphere MQ Queue Connection Factories

1.


(
mmfeDist
_XAQueueConnectionFactory
)

1.1

Name:
mmfeDist
_XAQueueConnectio
nFactory

1.2

JNDI Name:
jms/

mmfeDist
_XAQueueConnectionFactory

1.3

Component
-
Managed Authentication Alias: None

1.4

Container
-
Managed Authentication Alias: None

1.5

Mapping Configuration Alias: DefaultPrincipalMapping

1.6

Queue Manager:
[QUEUE MANAGER NAME]

1.7

Host:
[
HOST
IP ADD
RESS]

or [HOST NAME
]

1.8

Port:
[PORT]

1.9

Channel [SERVER CONNECTION CHANNEL NAME]

1.10

Transport Type: CLIENT

1.11

CCSID: <ENTER CCSID>


2

mmfeDist

_XAQueueConnectionFactory_XA

2.1

Name:
mmfeDist
_XAQueueConnectionFactory
_XA

2.2

JNDI Name:
mmfeDist
_XAQueueConnectionFactory

2.3

Component
-
Managed Authentication Alias: None

2.4

Container
-
Managed Authentication Alias: None

2.5

Mapping Configuration Alias: DefaultPrincipalMapping

2.6

Queue Manager:
[QUEUE MANAGER NAME]

2.7

Host:
[
HOST
IP ADDRESS]

or [HOST NAME
]

2.8

Port:
[PORT]

2.9

Channel [SERVER CONNECTION CHANNEL
NAME]

2.10

Transport Type: CLIENT

2.11

CCSID: <ENTER CCSID>


Websphere MQ Queue Destinations

1

mmfeDist
_ERROR_QUEUE

1.1
Name:
mmfeDist
_ERROR_QUEUE

1.2
JNDI Name
:
mmfeDist
_ERROR_QUEUE

1.3
Persistence: APPLICATION DEFINED

1.4
Priority: APPLICATION D
EFINED

1.5
Expiry: APPLICATION DEFINED

1.6
Base Queue Name:
MMFE
.ERROR.QUEUE

1.7
Target Client: JMS or MQ


2

mmfeDist
_ERROR_QUEUE_XA

2.1
Name:
mmfeDist
_ERROR_QUEUE
_XA

2.2
JNDI Name: jms/

mmfeDist
_ERROR_QUEUE

2.3
Persistence: APP
LICATION DEFINED

2.4
Priority: APPLICATION DEFINED

2.5
Expiry: APPLICATION DEFINED

2.6
Base Queue Name: MMFE
.ERROR.QUEUE

2.7
Target Client: JMS or MQ


3

mmfeDist
_ORDERS_IN



STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
29

of
39


3
.1 Name:
mmfeDist
_ORDERS_IN

3
.2 JNDI Name:
mm
feDist
_ORDERS_IN

3
.3 Persistence: APPLICATION DEFINED

3
.4 Priority: APPLICATION DEFINED

3
.5 Expiry: APPLICATION DEFINED

3
.6 Base Queue Name: MMFE
.
ORDERS
.
IN

3
.7 Target Client: JMS or MQ


4

mmfeDist
_ORDERS_IN
_XA

4
.1 Name:
mmfeDist
_ORDERS_IN
_XA

4
.2 JNDI Name: jms/
mmfeDist
_ORDERS_IN

4
.3 Persistence: APPLICATION DEFINED

4
.4 Priority: APPLICATION DEFINED

4
.5 Expiry: APPLICATION DEFINED

4
.6 Base Queue Name:
MMFE
.
ORDERS
.
IN

4
.7 Target Client: JMS or MQ


5

mmfeD
ist
_QUERIES_IN

5
.1 Name:
mmfeDist
_QUERIES_IN

5
.2 JNDI Name:
mmfeDist
_QUERIES_IN

5
.3 Persistence: APPLICATION DEFINED

5
.4 Priority: APPLICATION DEFINED

5
.5 Expiry: APPLICATION DEFINED

5
.6 Base Queue Name:
MMFE
.
QUERIES.IN

5
.7

Target Client: JMS or MQ


6

mmfeDist
_QUERIES_IN
_XA


6
.1 Name:
mmfeDist
_QUERIES_IN
_XA

6
.2 JNDI Name: jms/
mmfeDist
_QUERIES_IN
_XA

6
.3 Persistence: APPLICATION DEFINED

6
.4 Priority: APPLICATION DEFINED

6
.5 Expiry: APPLICATION

DEFINED

6
.6 Base Queue Name:
MMFE
.
QUERIES.IN

6
.7 Target Client: JMS or MQ


7

mmfeDist
_RESPONSES_IN

7
.1 Name:
mmfeDist
_RESPONSES_IN

7
.2 JNDI Name:
mmfeDist
_RESPONSES_IN

7
.3 Persistence: APPLICATION DEFINED

7
.4 Priority: APPLICAT
ION DEFINED

7
.5 Expiry: APPLICATION DEFINED

7
.6 Base Queue Name:
MMFE
.
RESPONSES
.
IN

7
.7 Target Client: JMS or MQ


8

mmfeDist
_RESPONSES_IN
_XA

8
.1 Name:
mmfeDist
_RESPONSES_IN
_XA

8
.2 JNDI Name: jms/
mmfeDist
_RESPONSES_IN

8
.3 Persiste
nce: APPLICATION DEFINED

8
.4 Priority: APPLICATION DEFINED

8
.5 Expiry: APPLICATION DEFINED

8
.6 Base Queue Name: MMFE
.
RESPONSES
.
IN

8
.7 Target Client: JMS or MQ




STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
30

of
39

9

mmfeDist
_ORDERS_OUT

9
.1 Name:
mmfeDist
_ORDERS_OUT

9
.2 JNDI Name:
m
mfeDist
_ORDERS_OUT

9
.3 Persistence: APPLICATION DEFINED

9
.4 Priority: APPLICATION DEFINED

9
.5 Expiry: APPLICATION DEFINED

9
.6 Base Queue Name:
MMFE
.
ORDERS
.
OUT

9
.7 Target Client: JMS or MQ


10

mmfeDist
_ORDERS_OUT
_XA

10
.1 Name:
mmf
eDist
_ORDERS_OUT
_XA

10
.2 JNDI Name: jms/
mmfeDist
_ORDERS_OUT

10
.3 Persistence: APPLICATION DEFINED

10
.4 Priority: APPLICATION DEFINED

10
.5 Expiry: APPLICATION DEFINED

10
.6 Base Queue Name:
MMFE
.
ORDERS.OUT

10
.7 Target Client: JM
S or MQ


11

mmfeDist
_QUERIES_OUT

1
1.1 Name:
mmfeDist
_QUERIES_OUT

1
1.2 JNDI Name: mmfeDist
_QUERIES_OUT

1
1.3 Persistence: APPLICATION DEFINED

1
1.4 Priority: APPLICATION DEFINED

1
1.5 Expiry: APPLICATION DEFINED

1
1.6 Base Queue Name:

MMFE
.
QUERIES.OUT

1
1.7 Target Client: JMS or MQ


12

mmfeDist
_QUERIES_OUT
_XA

12.1 Name:
mmfeDist
_QUERIES_OUT
_XA

12.2 JNDI Name: jms/mmfeDist
_QUERIES_OUT

12.3 Persistence: APPLICATION DEFINED

12.4 Priority: APPLICATION DEFINED

12.5

Expiry: APPLICATION DEFINED

12.6 Base Queue Name:
MMFE
.
QUERIES.OUT

12.7 Target Client: JMS or MQ



b) JDBC Providers

Fill in / browse the Node & Server fields & click Apply; click WebSphere MQ





Queue Connection Fa
ctories


1 MQSQL Server


Name:
Microsoft JDBC driver for MSSQLServer 2000 (XA)


Classpath:
${
MSSQLSERVER_JDBC_DRIVER_PATH
}/
msbase.jar


${
MSSQLSERVER_JDBC_DRIVER_PATH
}/
mssqlserver.jar


${
MSSQLSE
RVER_JDBC_DRIVER_PATH
}/
msutil.jar


Implementation Classname:
com.microsoft.jdbcx.sqlserver.SQLServerDataSource


Data

Sources

(mmfeDist
_DS)


Name: mmfeDist
_DS



JNDI Name: mmfeDist
_DS


Container Ma
naged Persistence: Checked


Datasource Helper Classname:
com.ibm.websphere.rsadapter.ConnectJDBCDataStoreHelper


Mapping
-
Configuration Alias: DefaultPrincipalMapping



STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
31

of
39


Custom Properties:



databaseName
: MMFE


serverName: [DATABASE SERVER IP ADDRESS] or [DATABASE SERVER HOST NAME]


portNumber: 1433


user:<database username>


password: <database password>


enable2Phase co
mmit: true


2 Oracle


Name:

Oracle JDBC Driver (XA)


Classpath:
${ORACLE_JDBC_DRIVER_PATH}/ojdbc14.jar


Implementation Classname:
oracle.jdbc.xa.client.OracleXADataSource


Data Sources:


Name: mmfeDist
_DS




JNDI Name: mmfeDist
_DS


Container Managed Persistence: Checked



Datasource Helper Classname:
com.ibm.websphere.rsadapter.OracleDataStoreHelper


Mapping
-
Configuration Alias: DefaultPrincipalMapping



Custom Properties:


URL:
jdbc:oracle:thin:@
<
server name or IP

address>:1521:MMFE


user:<database username>


password: <database password>


3 DB2


Name:

DB2 JDBC Driv
er (XA)


Classpath:
${
DB2_JDBC_DRIVER_PATH
}/
db2jcc.jar


${
DB2_JDBC_DRIVER_PATH
}/
db2jcc_license_cu.jar


${
DB2_JDBC_DRIVER_PATH
}/
db2jcc_license_cisuz.jar


im
plementation Classname:

com.ibm.db2.jcc.DB2XADataSo
urce


Data Sources:


Name:
mmfeDist
_DS


JNDI Name:
mmfeDist
_DS


Container Managed Persistence: Checked


Datasource Helper Classname:
com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper



Mapping
-
Configuration Alias: DefaultPrincipalMapping


Custom Properties:


serverName:[DATABASE SERVER IP ADDRESS] or [DATABASE SERVER HOST NAME]



databaseName: MMFE



driverType:[DRIVER TYPE]


portNumber:[PORT NUMBER]


username:<database username>


password:<database password>


4
Sybase


Name:

Sybase JDBC Driver (XA)



Classpath:

${
SYBASE_JDBC_DRIVER_PATH
}/
jconn2.jar


Implementation Classname:

com.sybase.jdbc2.jdbc.SybXADataSource


Data Sources:


Name:
mmfeDist
_DS


JNDI Name:
mmfeDist
_DS


Container Managed Persisten
ce: Checked


Datasource Helper Classname:
com.ibm.websphere.rsadapter.SybaseDataStoreHelper


Mapping
-
Configuration Alias: DefaultPrincipalMapping


Custom Properties:


serverName: [DA
TABASE SERVER IP ADDRESS] or [DATABASE SERVER HOST NAME]


databaseNa
me:MMFE


portNumber:[PORT NUMBER]


username:<database username>



STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
32

of
39


passwo
rd:<database password>





4.4.2.9

Security

Go to Security


Global Security

LDAP Setup

LDAP setup for Microsoft Active Directory (taken from IBM Websphere V5.0 Security Handbook Series. Dec
2002)




STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
33

of
39




STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
34

of
39





STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
35

of
39









STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
36

of
39



4.4.2.10

Setup start / stop

shortcuts:

Go to Start Menu > Programs > IBM WebSphere > Application Server v5.1

Duplicate shortcut "Start the Server" as "Start the Server (mmfeServer)";





change it's target by replacing server1 with mmfeServer, e.g.:




"C:
\
Program Files
\
WebSphere
\
AppServer
\
bin
\
startServer.bat" mmfeServer





-
user yourUser
-
password yourPassword

Duplicate shortcut "Stop the Server" as "Stop the Server (mmfeServer)";






change it's target by replacing server1 with mmfeServer, e.g.:



"C:
\
Program Files
\
WebSphere
\
AppServer
\
bin
\
stopServer.bat" mmfeServer





-
user yourUser
-
password yourPassword


Restart Websphere application Server before Proceeding.

4.4.2.11

Installing mmfeDist

Copy
\
dist
\
ears
\
was
\
mmfeDist
-
1.0.0
.<version>.ear to a directory on the server running Websphere Application
Server.

Under Administrative Console: Go to Application


install New
Application

Install new MMFE application:

-

Copy the ear file under [install cd]/dist/ears/websphere to a local location on your WebSphere
server

-

Click Applications > Install New Application

-

Tick Server path & provide the local location on your WebSphere ser
ver where you put the new
MMFE

ear file; click Next

-

Tick Generate Default Bindings; tick Default virtual host name for web modules: and put in
mmfeServer_host in the space supplied; click Next

-

Application Security Warnings: click Continue

-

Tick Pre
-
compile
JSP and ma
ke the Application Name: MMFE
; click Next

-

Provide Listener Ports for Messaging Beans: sp
ecify OrderMsgListenerBeanPortQC,
QueryMsgListenerBeanPortQC & ResponseMsgListenerBeanPortQC

respectively; click Next

-

Provide JNDI Names for Beans: click Next

-

Map EJB references to beans: click Next

-

Map resource references to resources: click Next

-

Map resource env entry references to resources: click Next

-

Map virtual hosts for web modules: tick both mmfeDist Web
-
App and SAFE_SOAP Web
-
App
and specify mmfeServer_
host for both; click Next

-

Map modules to application servers: Tick all modules, select mmfeServer and click Apply; click
Next

-

Map security roles to users/groups: apply your company specific security user/role mapping;
click Next



STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
37

of
39

-

Ensure all unprotected 2.0
methods have the correct level of protection: click Next

-

Summary: click Finish

-

Save changes

-

Restart your mmfeServer server

-

The URL to access your new
ly installed MMFE

should be something like:

-

http://server:9081/mmfeDist









STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
38

of
39

5

MMFE

Setup



1

Log in to MMFE
.




䱯朠i渠睩瑨t愠as敲e
t桡t

桡s⁡摭i湩s瑲慴a潮⁲i杨瑳.

ㄮN

q桥⁕剌⁦潲⁊_潳s⁩s㨠W瑴瀺p⼼p敲e敲⁎慭放W
Y灯rt>
L
mmf敄est

ㄮN

q桥⁕剌⁦潲ot敢s灨敲攠e灰lic慴a潮 p敲v敲⁩s›
桴hp
⼯Yp敲e敲⁎慭放W
Y灯rt>⽭m晥䑩st

†††† ††† †††††† †††††† ††††† †††
†††††† †††
†††
桴瑰t㨯⼼p敲v敲⁎慭放WY灯rt>⽭mf敄est


2

You’ll be presented with a
䵍cb⁆lavo畲⁓ur敥n
W

P

p敬散琠瑨攠䙬慶潵r
fr潭⁴ 攠er潰⁤ow渠扯x

a湤 敮瑥爠t桥⁂m i搮d
The Click “Add Flavour”

Q

剥灥慴as瑥t″ f潲⁡ol⁴
桥⁆ 慶o畲u⁴ 慴a湥敤⁣潮fig畲ud

E
if⁲敱畩r敤F
.

R

Click “Please Select A Role” from the Menu on the left.

S

p敬散琠tnyo湥 潦⁴ 攠䙬慶o畲uL
Roles you’ve just added

T

䍬ick⁁摭i湩s瑲慴ao渠


mm晥䑩st

s整異

䵡k攠e桡湧敳 慣c潲摩n杬y.

㜮7††
䱡s琺⁔桥 l慳琠tr摥r⁉搠
s桯ul搠扥 z敲e
.

㜮7††
E湶ir潮
m敮琠
乯㨠C

㜮7††
䵍FE

B䥃㨠Yo畲⁂uC⁣潤攠e潲⁴桥osel散t敤⁆ 慶潵r⽒/le

㜮7††
䵍S B䥃㨠ST剁ZAJ0
塘X

㜮7††
䵡x⁎畭扥r ⁲潷s⁦潲⁳瑡t畳⁉ 瑩m慴a潮s㨠

Ent敲⁴桥e湵m扥r ⁲潷s yo甠w
潵l搠wa湴nr整畲湥搠d潲⁡o
s瑡t畳
in瑩m慴a潮 煵敲y

㜮7††
Tr慮s灯r琠typ攺eW慮
潲⁓睩ft

Sel散琠睡渠if y潵 慲攠a潮n散瑩n朠gir散瑬y S瑲a瑥t潲⁳wif琠tf yo甠ur攠
c潮湥c瑩湧⁴漠S瑲慴a vi愠S睩ft

㜮7⁒数e慴as瑥t‷ 1⁴ 㜮7⁦潲⁡ol⁴ 攠䙬慶潵rs⽒/l敳 yo甠uav攮


8

䥭灯r琠t慰灩湧s⁡湤 Styles桥整e

䍯湦i杵re yo甠u慰灩n杳⁡ 搠dtyl
敳桥整e慣c潲oi湧ly
.






STRATE MMFE Installation Guide For Market Testing


Error! Reference source not found.

Release Date: 19 June 2008


Page
39

of
39

6


Installation Checklist


Client Name:

________________________________________________________________

MQ Location:

________________________________________________________________

JMSAdmin Location:

________________________________________________
__________
______

MQ Server Name:

________________________________________________________________

Application Server Name:

________________________________________________________________

Application Server Location:

____________________________________
____________________________

Database Name:

________________________________________________________________

Operating System:

________________________________________________________________

MMFE

Flavour

__________________________________________________
______________


Contact Details


Contact Person:


__________________________________________________________


Email Address:

__________________________________________________________


Telephone Number:

______________________________________
____________________


Cell phone

Number:

__________________________________________________________