It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×6,115
×1,305

question asked: Oct 10 '12, 7:23 a.m.
question was seen: 4,858 times
last updated: Oct 22 '12, 9:22 a.m.

Related questions

How to Make One RAM Repository Update Another One

0
Dan Duce (253●47●45) | asked Oct 10 '12, 7:23 a.m.
I'm researching a potential configuration that would work as follows:

Having two instances of RAM: 
           - one of which is a "normal" intance where assets are created, go through a lifeycle and are published.
           - the second instance is read only and gets updated from assets that are published in the first instance

The second instance would have a different user audience than the first instance  As assets were approved and published in Instance 1 they would by copied to Instance 2 where different user access permissions would be applied.

I'm wondering what is the best way to handle moving approved assets from the first instance to the second and then updating new versions as they are published?  Essentially, I want Instance 1 to be the authoritative copy and Instance 2 is just for reference.

Thanks,

Accepted answer

0
permanent link
Gili Mendel (1.8k●5●6) | answered Oct 18 '12, 7:58 a.m.
JAZZ DEVELOPER
edited Oct 18 '12, 7:59 a.m.
The only way to do this today, is to create a (Java) synchronizer, that will sync the two:

Run on some interval, look for approve (categorized to be published) assets, and create them on the read only repository, and create a link between these assets.

If assets are created, updated, or archived... it will propagate these to the read only repo.
Dan Duce selected this answer as the correct answer
Comments
Gili Mendel commented Oct 22 '12, 9:22 a.m.
JAZZ DEVELOPER

One more suggestion... as you create these assets on the read only repo. Set them with the same GUID/version

One other answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Gili Mendel (1.8k●5●6) | answered Oct 10 '12, 11:27 a.m.
JAZZ DEVELOPER
What is it that the 2nd instance has, that would not achieve with a lifecycle:  preApproved, only viewed by submitter and approvers?
Comments
Dan Duce commented Oct 10 '12, 11:44 a.m.

Entirely different audiences for each.   The first would be like the definitive library for all assets.  The second (and possibly other) instance would take a subset of the assets and make them viewable for a select audience.  The two instances would authenticate using different directories and could be in different zone with respect ot firewalls.
The main requirement is that there have to be two separate instances.  We can't grant access to the definitive library to everyone.

Gili Mendel commented Oct 15 '12, 8:21 a.m. | edited Oct 15 '12, 8:22 a.m.
JAZZ DEVELOPER

Not there yet understanding the "...Entirely different audiences for each..."
If assets are not visible to a large audience until they are approved, and you can filter by state (in the case you are one of the approvers) ... why have two watches to tell the time?

Dan Duce commented Oct 17 '12, 9:47 a.m.

Hi Gili,
The use case here could be something like the following.  For internal users, we have a repository that authenticates against our internal LDAP.  As assets are approved we want to copy them to a separate repository which exists outside of the firewall for customer access in a read only mode.  A separate LDAP would be used ot authenticate customers.  We can't allow customers to access the repository on the internal network.
Thanks,

Gili Mendel commented Oct 18 '12, 7:56 a.m.
JAZZ DEVELOPER

k,  multi tenancy; got it.

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.