Skip to Content
avatar image
Former Member

Maint and Dev project in one landscape

hi experts

Initially we had a proposal for dual landscape to manage maintenance and development landscape using retrofit. but we have a situation to manage maintenance and implementation project in one landscape.


i.e,  Dev - QA - PROD  - this landscape should manage both development and maintenance projects


My initial thoughts to define the solution


  1. create two different projects  - one maintenance project and one implementation project for development team
  2. customizing changes are implemented using the TR from implementation project , whereas work bench objects needs to be done using enabling the CSOL. so that developer A and B can work independently using different TR.  - is these possible to have different TR's from two different project for the same workbench object ?
  3. Implementation projects TR's will be moved before the test cycle to QA
  4. during the QA test cycle , if same objects conflict occurs - urgent CR can be created to resolve the conflicts
  5. after testing in QA, the implementation project TR will be moved to Prod

Is these feasible and workable solution to implement in landscape ?

Please advice with possible options

Thanks

Sol man

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    May 19, 2015 at 07:23 PM

    Hi,

    Below might be helpful to you

    create two different projects  - one maintenance project and one implementation project for development team

    yes you can create multiple projects either maintenance or implementation in one dev system, based on your release strategy, all these projects can run parallely.  there can be same objects touched across the projects. Risks can be avoided if the TR created via ChaRM Process.

    customizing changes are implemented using the TR from implementation project , whereas work bench objects needs to be done using enabling the CSOL. so that developer A and B can work independently using different TR.  - is these possible to have different TR's from two different project for the same workbench object ?

    yes, basically even if you dont have CSOL activated also, you would still be able to edit the object unless some other user is in the system at the same time and is editing the object already. so you have to wait until the first one finish the work,

    if you activated CSOL, it locks the objects in LIMU level, so you can either or the way you can control the 2 developers who is trying to edit the sam objects, the entire use case for CSOL for avoiding risk on parallel projects runnning on same developement system or parallel projects running on 2 different system with same Production system, it ultimately prevents the risks.

    Implementation projects TR's will be moved before the test cycle to QA

    yes, you can set the phase actions, by charm Standard  Process TR moved to QA before Test phase, keep it as it is!

    during the QA test cycle , if same objects conflict occurs - urgent CR can be created to resolve the conflicts

    whenever CSOL conflicts occurs if it is warning, you can ignore and proceed, if error lock you need to contact Administrator to remove the lock from lockmon table in solution manager, you need to define the process for handling CSOL,

    after testing in QA, the implementation project TR will be moved to Prod

    yes, defaulit it works as the same.

    Hope this helps,

    With Best wishes,

    Jansi

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 19, 2015 at 03:03 PM

    hi experts

    Any answer is appreciated and help in decision making

    Thanks

    Sol man

    Add comment
    10|10000 characters needed characters exceeded