It's all about the answers!

Ask a question

Migration of RTC 3.0.1.1 from Server1 to Server2


sriramak s (1762018) | asked Dec 17 '11, 5:24 a.m.
Hi,

We are planning to migrate the RTC 3.0.1.1 Physical Server to differnt Virtual Server.which is integrated with RRC 3.0.1.1. Backend DB2 database.. websphere 7.0 64 bit. and enabled with LDAP .

In RTC Server we already have Source Code and Workitems.

Process Templates has been coustmized.

and also its been integrated with Rational Insight running on differnet server websphere 6.0 32 bit.

Please let me know the best practise to migrate from one physical serve to Virutal server but he name will change on the server..

whats the impact on the exist data and process configurations.

Regards,
Arun

3 answers



permanent link
Geoffrey Clemm (30.1k33035) | answered Dec 17 '11, 12:08 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
You cannot change the registered URL for a 3.0.1 repository (i.e. the
URL prefix users type into their web browser or in their Eclipse
repository connection field). You can change the physical machine that
hosts the repository, by making the appropriate changes in DNS or create
a reverse proxy to redirect messages to the original registered URL to
the new machine.

In 4.0, you should be able to change the registered URL of a repository.

Cheers,
Geoff

On 12/17/2011 5:38 AM, sriramak wrote:
Hi,

We are planning to migrate the RTC 3.0.1.1 Physical Server to differnt
Virtual Server.which is integrated with RRC 3.0.1.1. Backend DB2
database.. websphere 7.0 64 bit. and enabled with LDAP .

In RTC Server we already have Source Code and Workitems.

Process Templates has been coustmized.

and also its been integrated with Rational Insight running on
differnet server websphere 6.0 32 bit.

Please let me know the best practise to migrate from one physical
serve to Virutal server but he name will change on the server..

whats the impact on the exist data and process configurations.

Regards,
Arun

permanent link
sriramak s (1762018) | answered Dec 30 '11, 7:08 a.m.
Hi,

Thanks for the information...

I would like to request what exact information need to be changed in DNS for server migration... can you please give me more details..

for the below recommended below solutions..

You can change the physical machine that
hosts the repository, by making the appropriate changes in DNS


or create
a reverse proxy to redirect messages to the original registered URL to
the new machine.


####################

If we have done fresh installation and setup on the new server, what are the steps needs and artifcates needs to be imported into new server..

correct me if I am wrong...


Regards,
Sriramak


###################################################


You cannot change the registered URL for a 3.0.1 repository (i.e. the
URL prefix users type into their web browser or in their Eclipse
repository connection field). You can change the physical machine that
hosts the repository, by making the appropriate changes in DNS or create
a reverse proxy to redirect messages to the original registered URL to
the new machine.

In 4.0, you should be able to change the registered URL of a repository.

Cheers,
Geoff

On 12/17/2011 5:38 AM, sriramak wrote:
Hi,

We are planning to migrate the RTC 3.0.1.1 Physical Server to differnt
Virtual Server.which is integrated with RRC 3.0.1.1. Backend DB2
database.. websphere 7.0 64 bit. and enabled with LDAP .

In RTC Server we already have Source Code and Workitems.

Process Templates has been coustmized.

and also its been integrated with Rational Insight running on
differnet server websphere 6.0 32 bit.

Please let me know the best practise to migrate from one physical
serve to Virutal server but he name will change on the server..

whats the impact on the exist data and process configurations.

Regards,
Arun

permanent link
Geoffrey Clemm (30.1k33035) | answered Dec 30 '11, 9:53 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
DNS maps a hostname to an IP address, such as:
myhost.mycompany.com -> 127.33.55.10
To change this to a new machine, update the DNS table to map the
hostname of the RTC server to be the IP address of the new machine.

Cheers,
Geoff

On 12/30/2011 7:23 AM, sriramak wrote:
Hi,

Thanks for the information...

I would like to request what exact information need to be changed in
DNS for server migration... can you please give me more details..

for the below recommended below solutions..

You can change the physical machine that
hosts the repository, by making the appropriate changes in DNS


or create
a reverse proxy to redirect messages to the original registered URL to

the new machine.


####################

If we have done fresh installation and setup on the new server, what
are the steps needs and artifcates needs to be imported into new
server..

correct me if I am wrong...


Regards,
Sriramak


###################################################


gmclemmwrote:
You cannot change the registered URL for a 3.0.1 repository (i.e. the

URL prefix users type into their web browser or in their Eclipse
repository connection field). You can change the physical machine
that
hosts the repository, by making the appropriate changes in DNS or
create
a reverse proxy to redirect messages to the original registered URL
to
the new machine.

In 4.0, you should be able to change the registered URL of a
repository.

Cheers,
Geoff

On 12/17/2011 5:38 AM, sriramak wrote:
Hi,

We are planning to migrate the RTC 3.0.1.1 Physical Server to
differnt
Virtual Server.which is integrated with RRC 3.0.1.1. Backend DB2
database.. websphere 7.0 64 bit. and enabled with LDAP .

In RTC Server we already have Source Code and Workitems.

Process Templates has been coustmized.

and also its been integrated with Rational Insight running on
differnet server websphere 6.0 32 bit.

Please let me know the best practise to migrate from one physical
serve to Virutal server but he name will change on the server..

whats the impact on the exist data and process configurations.

Regards,
Arun

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.