sheetal.desai wrote:

We have a situation where we have to support multiple environments -
40 and 45. Most of the code is the same but only the jar files are
different and will remain different between 40 and 45.

I created a single component and two streams - 40 Stream and 45 Stream
both based on the same baseline (say #10). Then we modified the jar
files for 45 Stream and created a baseline (#11).

Certain changes made in 40 will need to be delivered to both 40 Stream
and 45 Stream.

Can the RTC SCM experts help us determine the best practice for our
situation?

So far it sounds good. Two different streams that have the same
components is the right way to go.

When a change needs to go into both streams, there are two obvious
choices: (1) The developer making the change is responsible for
delivering the change to both streams. (2) The developer delivers only
to the 40 Stream, and someone else on the team has the task of regularly
pushing changes from the 40 Stream to the 45 Stream. I tend to prefer
#1, but #2 could work better if all 40 changes have to be made in 45 and
if the streams haven't diverged too much.

One problem we ran into is that when one of the users' made a change
in 45 Stream and created a new baseline (#12) - somehow the 40 Stream
was automatically based on this new baseline (#12). Not sure if RTC
did this automatically or something the user did. Can you help?

That sounds strange. Streams don't automatically pick up new baselines
or change sets. There has to be an explicit action, either a delivery
or a "replace contents", for a stream to change its contents. I am
guessing that it was done by a user who didn't fully understand how RTC
SCM is supposed to work, but I don't know of any way to confirm that.
It should be easy enough to recover from; just replace the contents in
the 40 Stream with the desired baseline.