Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Moving (export/import) projects between RTC servers?

Hi

I have set up a production RTC env and testing RTC env, they are identical, all using WAS7 and Oracle 11g, same integration to LDAP, but they are totally separated and independent.

Now I want to take a copy of projects created in production RTC and import it into the testing RTC. What's the best tools to do that?

1. Should not change any JTS setting, e.g. the db, LDAP., etc. I don't want these two envs have any hard link.
2. Users are already synced, due to they are integrated to the same AD/LDAP.
3. I want everything project related.

This technote and related work items tells me export and import single project is not possible at this moment. The technote says "The repotool only allows you to export the entire repository." What's included in this "entire repository"? Can I use repotool for my purpose?
https://www-304.ibm.com/support/docview.wss?uid=swg21326998

0 votes



5 answers

Permanent link
This is actually an instance of the "change public server URL"
discussion. In 3.0 and later, the only way to do this kind of testing
is to set up your test repository in an environment where you can
locally assign the test server machine the hostname of the public server
machine.

Cheers,
Geoff

On 10/3/2011 3:23 PM, hujirong wrote:
Hi

I have set up a production RTC env and testing RTC env, they are
identical, all using WAS7 and Oracle 11g, same integration to LDAP,
but they are totally separated and independent.

Now I want to take a copy of projects created in production RTC and
import it into the testing RTC. What's the best tools to do that?

1. Should not change any JTS setting, e.g. the db, LDAP., etc. I don't
want these two envs have any hard link.
2. Users are already synced, due to they are integrated to the same
AD/LDAP.
3. I want everything project related.

This technote and related work items tells me export and import single
project is not possible at this moment. The technote says "The
repotool only allows you to export the entire repository."
What's included in this "entire repository"? Can I use
repotool for my purpose?
https://www-304.ibm.com/support/docview.wss?uid=swg21326998

0 votes


Permanent link
This is actually an instance of the "change public server URL"
discussion. In 3.0 and later, the only way to do this kind of testing
is to set up your test repository in an environment where you can
locally assign the test server machine the hostname of the public server
machine.

Cheers,
Geoff


I don't understand. What I want is to duplicate the project contents from the production server to my test server. I don't want my production and test server have any link.

Simple question, is there a way for me to export the project related assets from the production server and import them into the test server?

Thanks
Jirong

0 votes


Permanent link
The only way you currently can export your project related assets from
the production server and import them into the test server is to use
either the RTC repository tools to dump/load your entire repository, or
use the underlying DBMS mechanism to dump/load your repository. But in
either case, when you load your repository onto the test server, you can
only reliably access it using the URL from the production server.

Thus my answer below.

Cheers,
Geoff

On 10/6/2011 12:08 PM, hujirong wrote:
gmclemmwrote:
This is actually an instance of the "change public server
URL"
discussion. In 3.0 and later, the only way to do this kind of
testing
is to set up your test repository in an environment where you can
locally assign the test server machine the hostname of the public
server
machine.

Cheers,
Geoff

I don't understand. What I want is to duplicate the project contents
from the production server to my test server. I don't want my
production and test server have any link.

Simple question, is there a way for me to export the project related
assets from the production server and import them into the test
server?

Thanks
Jirong

0 votes


Permanent link
But in
either case, when you load your repository onto the test server, you can
only reliably access it using the URL from the production server.

Thus my answer below.

Cheers,
Geoff


Now I understand, although I am totally don't want to do this now. But still have a question: "using the URL from the production server", isn't this URL being used by/pointing to production repository already?

e.g. when I use https://production_server:9443/ccm, am I using the production repo or test repo?

Jirong

0 votes


Permanent link
Yes, that was why in my original response, I said:

the only way to do this kind of testing is to set up your test
repository in an environment where you can locally assign the test
server machine the hostname of the public server machine.

How exactly you do that local assignment varies depending on your
platform (e.g. playing with /etc/hosts files and such).

Cheers,
Geoff

On 10/7/2011 12:08 PM, hujirong wrote:
gmclemmwrote:
But in
either case, when you load your repository onto the test server, you
can
only reliably access it using the URL from the production server.

Thus my answer below.

Cheers,
Geoff

Now I understand, although I am totally don't want to do this now. But
still have a question: "using the URL from the production
server", isn't this URL being used by/pointing to production
repository already?

e.g. when I use https://production_server:9443/ccm, am I using the
production repo or test repo?

Jirong

0 votes

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Oct 03 '11, 3:17 p.m.

Question was seen: 6,580 times

Last updated: Oct 03 '11, 3:17 p.m.

Confirmation Cancel Confirm