Skip to Content
author's profile photo Former Member
Former Member

Used DC issue

Hello,

I have a issue with adding used DCs.

I have one external library DC...say "extlib"

This has all the jar files required.

I have one Portal standalone DC...say "portaldc1"

This portal dc has java classes in the src.API package. These classes require the jars in extlib.

I have one web dynpro DC....say "webdc1"

This webdc1 uses classes in portaldc1 and also require extlib.

What kind of public parts do I have to create and add as used DCs.

I also want to make sure that, when I make changes to any classes in "portaldc1", I just build and redeploy "portaldc1"...I do not want to build and redeploy "webdc1" each time I change portaldc1.

Is this achievable?

Any help is greatly appreciated.

Thanks

MLS

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on May 20, 2009 at 10:42 AM

    Hi Laxmi,

    You can create the public part of type API for deploying / compiling other DC.

    If you do any changes to the used DC you'll have to redeploy the used DC as well as the application using that DC.

    So each time you make changes to "portaldc1" its better to redeploy "webdc1" also or it might lead to inconsistency.

    Regards,

    Seema Rane.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 20, 2009 at 02:51 PM

    Hello Seema,

    Thanks for your reply.

    The issue is, we have like 10 or more web dynpro applications using this core "portaldc1". So each time we change something in "portaldc1", we don't want to rebuild and deploy all the 10 web dynpros.

    Is it possible?

    Thanks

    MLS

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 20, 2009 at 03:02 PM

    Hi Laxmi,

    If all the DCs that will access the library also access the "portaldc1", then expose the libraries through "portaldc1". But, how you structure your DC will be upto your requirement and design.

    To your second question, if you build a DC, lets call it DC1, being used by other DCs and check it in. CBS automatically marks all the DCs using DC1 as dirty. This is to ensure that are inconsistency in the source repository and all the dependencies changes do not affect the using DCs. Then based on the settings CBS will build the dirty DCs. In case the dependencies have changed like a used methos is removed or a method signature is changed etc then a DC using this depenency will become Broken.

    Broken DCs are a way of the CBS to inform the users that something is wrong and needs to be fixed.

    Regards,

    Kartikaye

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 21, 2009 at 08:00 AM

    Hi Laxmi,

    It is always better to redeploy the 10 DCs as well after redeploying "portaldc1" to be on the safer side or else it might lead to broken DC's which will be more tideous to correct.

    Regards,

    Seema Rane.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.