Installing/updating ifix3 on SOME of the RQM package groups
Hi,
Right now I have 3 RQM 2.0.1 ifix1 that I'll upgrade later. I have a request to
migrate two repositories from another location to my server. I got the ifix and configured Installation Manager to find it. I selected a freshly installed RQM package group and just before the final step:
Warning: Make sure that all instances of Rational Quality Manager are stopped before proceeding....
I understand there are shared jar files, but would proceeding be a recipe for disaster should I keep pressing forward ?
Right now I have 3 RQM 2.0.1 ifix1 that I'll upgrade later. I have a request to
migrate two repositories from another location to my server. I got the ifix and configured Installation Manager to find it. I selected a freshly installed RQM package group and just before the final step:
Warning: Make sure that all instances of Rational Quality Manager are stopped before proceeding....
I understand there are shared jar files, but would proceeding be a recipe for disaster should I keep pressing forward ?
3 answers
Can anyone answer ?
Hi,
Right now I have 3 RQM 2.0.1 ifix1 that I'll upgrade later. I have a request to
migrate two repositories from another location to my server. I got the ifix and configured Installation Manager to find it. I selected a freshly installed RQM package group and just before the final step:
Warning: Make sure that all instances of Rational Quality Manager are stopped before proceeding....
I understand there are shared jar files, but would proceeding be a recipe for disaster should I keep pressing forward ?
Hi
Short answer is "yes" you may be setting yourself up for disaster. If
you're running RQM on WAS you should do both the "requestReset" step and
delete the <WASpathtoprofile>\temp[rqm|rqmhelp] war directories. The
"Update entire app" process in WAS usually does delete the temp but to
be doubly sure I shut WAS down, delete the temp dir and restart WAS.
Freddy
On 9/07/2010 3:53 AM, yzwkzfn wrote:
Short answer is "yes" you may be setting yourself up for disaster. If
you're running RQM on WAS you should do both the "requestReset" step and
delete the <WASpathtoprofile>\temp[rqm|rqmhelp] war directories. The
"Update entire app" process in WAS usually does delete the temp but to
be doubly sure I shut WAS down, delete the temp dir and restart WAS.
Freddy
On 9/07/2010 3:53 AM, yzwkzfn wrote:
Can anyone answer ?
yzwkzfnwrote:
Hi,
Right now I have 3 RQM 2.0.1 ifix1 that I'll upgrade later. I have
a request to
migrate two repositories from another location to my server. I got
the ifix and configured Installation Manager to find it. I selected
a freshly installed RQM package group and just before the final
step:
Warning: Make sure that all instances of Rational Quality Manager
are stopped before proceeding....
I understand there are shared jar files, but would proceeding be a
recipe for disaster should I keep pressing forward ?
I'm using tomcat based deployment. I updated my two 'fresh' RQM201 installs to ifix3 w/o affecting other repositories.
Hi
Short answer is "yes" you may be setting yourself up for disaster. If
you're running RQM on WAS you should do both the "requestReset" step and
delete the <WASpathtoprofile>\temp[rqm|rqmhelp] war directories. The
"Update entire app" process in WAS usually does delete the temp but to
be doubly sure I shut WAS down, delete the temp dir and restart WAS.
Freddy
On 9/07/2010 3:53 AM, yzwkzfn wrote:
Can anyone answer ?
yzwkzfnwrote:
Hi,
Right now I have 3 RQM 2.0.1 ifix1 that I'll upgrade later. I have
a request to
migrate two repositories from another location to my server. I got
the ifix and configured Installation Manager to find it. I selected
a freshly installed RQM package group and just before the final
step:
Warning: Make sure that all instances of Rational Quality Manager
are stopped before proceeding....
I understand there are shared jar files, but would proceeding be a
recipe for disaster should I keep pressing forward ?