Escolar Documentos
Profissional Documentos
Cultura Documentos
Surendra Ramanapudi
Performance Test Lead/Architect
Table of Contents
1.
2.
A.
3.
4.
INTRODUCTION.................................................................................................................................................... 4
SCRIPTS.............................................................................................................................................................. 4
PERSON SEARCH SERVICE................................................................................................................................. 4
ENVIRONMENT CONFIGURATION........................................................................................................................ 5
EXECUTION......................................................................................................................................................... 9
1. Introduction
As a part of MDM Performance Testing Build Phase, 4 different flows were identified.
They are Person Search Service, Maintain Account Service, Maintain Member Service and service calls from
and Some Web Interface (Provided by IBM MDM).
This document explains the Technical Design for developing these scripts
2. Scripts
a. Person Search Service
Person Search Service uses JMS channel of MDM application and communicated via IBM MQ. This means the
search requests are placed into the ODS Request Queue in the form of XML files. They communicate with
MDM through JMS port. This communication is considered as XML over JMS. To accomplish this, Loadrunner
WebServices protocol is used. It is not SOAP over HTTP, It is SOAP over JMS. So some configurations has to
be done as prerequisites.
Below sections provide more technical details of the script development process.
Draft
Page 2
3/5/2015
3. Environment Configuration
1. Install JDK 1.7.02
2. Install IBM WebShpere client
3. Then go to this location C:\Program Files\IBM\Web Sphere MQ\java\bin
4. Edit the JMSAdmin.config file. Please see the Line #27 and Line # 41 in the below snap shot of the
JMSAdmin.config file
Draft
Page 3
3/5/2015
5. Create a .SCP file and placed it in the same directory as JMSAdmin.config file is
Draft
Page 4
3/5/2015
For Example: In UAT2, the Request Queue and Response Queue under same queue manager. So the .scp file
looks as below.
def qcf(ODSDSXT1) qmgr(ODSDSXT1) transport(CLIENT) host(mq-odsdsxt1.test.hcscint.net)
channel(ODSDSXT1.USR.SVRCONN) port(3120)
def q(MDM.MESSAGING.HI.REQUEST.UAT2) qu(MDM.MESSAGING.HI.REQUEST.UAT2)
def q(MDM.MESSAGING.HI.SUCCESSFUL_RESPONSE.UAT2)
qu(MDM.MESSAGING.HI.SUCCESSFUL_RESPONSE.UAT2)
end
6. Then The JMSAdmin.config file is executed by passing the queue information in the .SCP file.
7. This creates JNDI Binding file in the Location specific in the JMSAdmin.config file. In this location
Draft
Page 5
3/5/2015
Draft
Page 6
3/5/2015
Draft
Page 7
3/5/2015
4. Execution
Execution of this script is performed in HP Performance Center 11.5.
The following items to be considered before execution the formal Test.
a. The steps from 1 to 8 in the section 3 are to be implemented on each load injector
b. If the Request and response Queues belong to the same Queue Manager the above .SCP file format
works
c. If the request and response queues belong to different queue mangers then. Different approach to be
implemented
d. If the response queue belongs to MDM queue manager, Then We need Citrix VPN access. In this case
it will be challenge to execute a test in Performance Center. Performance Center needs service ID to
login and Load injectors. The admin privileges should be granted to these nodes and the service ID.
Draft
Page 8
3/5/2015