copy common code using project in another database via DCM

[Devendra]

All,

 

I am implementing "common code structure" that allows to replicate common code from parent database to all children databases. Users on Children database will be able to read/execute code but can’t modify it. Only parent database user can modify common code. Common code includes everything .. source code, header file and libraries.

 

I have decided to use DCM functionality. (Any other better method?)

 

Step performed:

(a) DCM enabled (initiate) parent database.

(b) Create transfer set

(d) Add specific project with common code in transfer set using following command:

 

ccm dcm -add -ts "TS_TEST1" <four part project name>

 

(e) Generate transfer

ccm dcm -generate -dbid MYID -ts TS_TEST1

 

(f) Since I chose direct transfer, it automatically receives it.

 

At the end I can see that transfer is successful.

 

BUT, when I fire up Synergy webclient to see project on children database, I don't see that project or any files under there.

 

How do I verify that transfer is successful and all objects along with project are replicated?

 

Am I using wrong method to achieve above task? If yes, any other pointers to right direction?

 

-Devendra

[David Honey]

Hi Devendra,

You are not seeing it in the target database because you have not performed a DCM receive of the transferred package in that database.
You state:

        (f) Since I chose direct transfer, it automatically receives it.

That's not true. All that direct transfer mode does is to generate the transfer package in the DCM receive directory of the destination database.

You can do either of the following:

1. Start a session on the destination database and perform a DCM receive.
2. Use the -receive option on your ccm dcm -generate command. This will require that the machine hosting the destination database is a trusted host.

Best regards,
David.

--
You received this message because you are subscribed to the Google Groups "Synergy CM Tool" group.
To unsubscribe from this group and stop receiving emails from it, send an email to synergy-cm-to...@googlegroups.com.
To post to this group, send email to synergy...@googlegroups.com.
Visit this group at http://groups.google.com/group/synergy-cm-tool.
For more options, visit https://groups.google.com/groups/opt_out.

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

[Ruediger Friedel]

Hi Devendra,

 

Maybe I am not understanding your exact requirements correctly, but why wouldn’t you use baselines and the built-in propagation methods (Integration Testing > System Testing) for what you are trying to do?  Your “common code structure” would simply be a baseline that your users could use in their projects (as included component).  By nature a baseline can’t be modified.

 

I am probably oversimplifying this, just wanted to share my thought that came to mind while reading your question.

 

-Rudi.

[Devendra]

Thanks Rudi!

 

But, "common code structure" will be still keep updated/modified on parent database. It means, we need to keep updating to new baseline. How is that possible? (May be I need to do some more readings ..)

[Devendra]

Hi David,

 

I did run "ccm dcm -receive -all" on destination database. It says "No transfer sets found to receive.". I do see that files are received under dcm/receive directory.

 

Thanks!

To unsubscribe from this group and stop receiving emails from it, send an email to synergy-cm-tool+unsubscribe@googlegroups.com.
To post to this group, send email to synergy-cm-tool@googlegroups.com.
Visit this group at http://groups.google.com/group/synergy-cm-tool.
For more options, visit https://groups.google.com/groups/opt_out.

[cmtodd]

If the package was generated, transferred, and received, then the objects should be there.  Check the DCM event log on both the sending side and receiving side for any messages and to check what was in the package.

As far as using new baselines, you can of course setup additional DCMs for each Baseline (either manually, or setup a job to look for new baselines in the appropriate state).  If you want the using/parent projects in the receiving dB to pick up new baselines you send auto-magically when they run update, then look into "component tasks".

If you are concerned with users in the receiving dB(s) copying the project and editing, then protect the project and content with Group security (obviously not read, use only write security).

One last tip, just in case you are new to component subprojects, make sure you release the component projects with the "relative to parent" WA property so that the using parent(s) will get a snapshot of the subproject in the parent project WA (assuming that is what you desire which is usually the case).

Todd