Installation - Go2Group

luckyhillockΔιαχείριση Δεδομένων

29 Νοε 2012 (πριν από 4 χρόνια και 9 μήνες)

322 εμφανίσεις

Installation
................................
................................
................................
......................

2

Preparation

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

2

Download the Synchronizer Server

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

2

Install Synchronizer Client

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

5

Install JaM
-
Synchronizer

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

5

Install JaM r
pc plugin in JIRA Server
................................
............................

5

Install JIRA adapter for Synchronizer server

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

6

Configuration

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

6

Comment Replication

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

15

Attachment Replication

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

17

Setup requirement sync

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

17

Uninstall the Synchronizer

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

22



Installation

Preparation

If you are using QC 9, 10 or 11,

1. Go to directory "C:
\
Program Files
\
Common Files" and remove directory "Mercury
Interactive" if

it is present.

2. Open IE on the soap service machine. Go to QC portal page.

This is the url
http:
\
\
yourQCIP
\
qcbin

3 .Click the third link "Add
-
Ins Page" on the QC portal page. On that page, click "HP
Quality Center Connectivity" link. On that page, click

on "Download Add
-
in".

4. Run the executable you downloaded.


Download the Synchronizer Server

For QC
10 and
11, go to

http://update.external.hp.com/qualitycen
ter/qc110/sync/almsynchronizer/index.html

Download Synchronizer server
and client both
with version 1.40 build number 1120


For QC 9, g
o to
http://updates.me
rc
-
int.com/qualitycenter/qc90/sync/qcsynchronizer/index_9_2.html

Download Synchronizer server 1.3 and client 1.3


For backward compatibility reason, we use synchronizer 1.3 that comes with QC 9 as
an example. But the configurations work for QC 10 and 11.



Install Synchronizer Server

Please note

HP did mention you should not install the synchronizer
server
in the
QC

s box

. This is because HP use Jboss for
both
QC Server and Synchronzer
server, some ports
will conflict
.

Unzip the
QCSyncServer.zip
, and ex
ecute the setup.exe and click Next

..


Choose the installation directory


Server Configuration will popup after installation
automatically



U
ser name and password should be the account for starting the window
server( administrator/ plans) and the Domai
n is the machine name.


I
nstall Synchronizer Client


E
xecute the
QCSyncClient.msi

and choose the installation directory

Install JaM
-
Synchronizer

Install
JaM
rpc plugin
in JIRA Server

1.

atlassian
-
jira
\
WEB
-
INF
\
lib
I
nstall JaM
-
Synchronizer rpc
-
plugin

C
opy
//Pro
duct/Dev/JAM
-
Synchronizer
-
1.0/rpc
-
jira
-
plugin/target/go2group
-
jira
-
rpc
-
plugin
-
1.0.jar

into <JIRA_home>/
atlassian
-
jira
\
WEB
-
INF
\
lib

2.

restart jira

3.

enable the Accept remote API calls



Install
JIRA adapter for Synchronizer server

1.

stop the Synchronizer Server f
rom window service

2.

(this step is not needed now)
replace the
C:
\
Program Files
\
HP
\
Quality Center
Synchronizer
\
jboss
\
server
\
default
\
deploy
\
gossip.war

with
//Product/Dev/JAM
-
Synchronizer
-
1.0/Synchronizer/1.3/gossip.war

3.

copy all the libraries from
//Product/Dev
/JAM
-
Synchronizer
-
1.0/adapter/install/lib/

into
C:
\
Program
Files
\
HP
\
Quality Center Synchronizer
\
adapters
\
lib

4.

copy

JaM
-
Synchronizer jar file
//Product/Dev/JAM
-
Synchronizer
-
1.0/adapter/target/jira
-
adapter.jar

to
C:
\
Program Files
\
HP
\
Quality Center Synchronize
r
\
adapters
\
lib

5.

Copy th license file to
C:
\
Program Files
\
HP
\
Quality Center Synchronizer

\
dat
\
JaMSynchronizer_license.txt



Configuration

Make sure you
restart the HP Quality Center Synchronize
r

after installation.


Execute Synchronizer Client, field out Se
rver name,
password is empty string



Create a link for replication



F
ield out the Link

s name, and choose jira for the endpoint 2 type



In step2, field out all the QC

s
authentication

information.



In step3, field out the account for replication an
d jira

s url and which project you want
to replicate.

Of course, you have to create a
JIRA
project first.



C
hoose bug for replication entity type



C
hoose Yes for editing the link right now.



Now, navigate to Field Mapping


W
e
need to
map the require
d field, Description,Detected By,Summary,Status and
Severity.

If there are others field in QC defined as
required
, you have to map them
too.



Have value mapping for status, such as Closed



Closed,

Fixed


Resolved
,

New


Open,

Open


In Progress
,

Reopen


Reopen

Please Note:
As you can
try here
, you can

t map duplicated value such as Reopen
and
Rejected

in QC
to JIRA

s Reopen.

Have value mapping for Severity, such as
1
-
Low


Trivial
,

2
-
Medium


Minor
,

3
-
High


Major
,

4
-
Very High


Critical
,

5
-
Urgent


Blocker


R
egarding the
user mapping, there are two
fields:
reporter and assignee.

If you are not going to map the assignee right now, enable

Allow unassigned Issues


in jira.

Otherwise you have to add assignee field for replication and make sure all the
users are e
ither defined in the value mapping or all the users are identical in both
systems.


In this example, I create all the QC

s users in jira, since Synchronizer can

t define
duplicated value mapping, you have no way to map all the users in QC to one jira
user
.




S
ave and run integrate check now


Here you can see the log.



E
nable the link



C
lick the Incremental Synchroniz
a
tion



Y
ou should be able to see the defects get replicated to jira first.


If you want to try replication

again
, update issue in ji
ra then click the Incremental
Synchronization again will trigger the replication right away.


Comment
R
eplication

Comments are handled very differently in JIRA and Quality Center. In JIRA, comments are stored as a
log of individual entries. In Quality Cent
er, comments are stored in one field as one block of text, with
HTML markup used to format the field's appearance.
And in Quality Center comments are only
recorded in day format without hours and minutes.
For this reason, comments cannot be synchronized
li
ke regular fields.


You have to create a custom field in
JIRA(
QC Comm
ent
)

and
map
Comments in QC
replicated
to this field.


C
reate another custom field

(JIRA Comments)

in QC and map Comments in JIRA to
the custom field.

This only one way replication

(JIR
A to QC) since comments in JIRA
stored as many records.


Attachment Replication


All the QC attachments will be replicated into jira

s attachment.


Setup requirement sync

Setup a new Link:


Input the QC configurations:



Select “Requirement” to mapping:


Input JIRA configurations, please make sure the Project input is the proje
ct key, it is
often capitalized,
and also

make sure you input the correct license.


Requirement needs to mapping subtypes, please refer to the following screenshot, add
subtype m
apping like “Business”.


For the specified subtype, specify the master of endpoints. This is a little different
with Bug rules, because it only allows one direction creation.


S
pecify the Field mapping which is the same as Bug mapping, and make sure the
field
in red has to be mapped.



Create three custom fields on JIRA side.


Create “Is Folder” Multi CheckBoxes which indicates if the requirement is a folder or
requirement.

It has option value “true”, and no default value.


“Parent Requirement” is a te
xt field, and it allows to input an issue key in JIRA
.

Please note that when Parent Requirement is empty, it means to create a folder or
requirement under the root folder. This is necessary when create the first requirement
or folder on JIRA side.

Because
there is no synced issue from JIRA to QC, for sure
there is no parent requirement which can be specified.
So “Parent Requirement” can
be empty which will create a requirement or folder under root, if the value is not
empty, make sure it has to be a jira is
sue key which has already synced to QC.



“Parent Type” is a Select List which maps the Requirement Type on QC
side. Please

create this according to QC side types, make sure have a default value.



Requirements created in QC:


Requirement
s

synced to JIRA
:


Uninstall the Synchronizer

There are two components that you need to uninstall, one is Synchronizer server the
other is PostgreSQL 8.3


E
xecute the uninstall.exe under _uninst directory to have Synchronizer uninstall.



U
ninstall PostgreSQL from the
Add and Remove Programs


Remove postgres user from the user manager