I have seen this being called out in my team meetings that the Dev environment on which I have my application (e.g Application 'A') is a shared environment. There is one another team as well which is working on application 'B'.

It is for the same organization say OrgXYZ.
The class structure for my application would be like OrgXYZ-Work-AppA (application name is AppA)
For another team, it would be OrgXYZ-Work-AppB (application name is AppB)

I can understand that the organization ruleset will be shared here. What other things might be shared or we have to take care that might impact another application.

And on the infra part, how does this work? Will there be 1 Node/System on which the Pega server runs and that hosts 2 applications?

    25 days later

    @ospteam can you please reply..!!! need this info..

      mahi sorry for the delay.

      Don't complicate your assumptions. Your scenario is as simple as having multiple implementations on top of one enterprise application.

      Things that will be shared: The below list of features will be shared between the applications,
      1) FW application and its features
      2) Organization wide Work-, Data- classes
      3) Pega OOTB customizations if any (Assign-*, Operator ID classes, etc..)
      4) Common Integration pieces
      5) Shared rulesets if any
      6) Component application if placed in the application stack.
      7) Pega Components like BIX, which will always be added to the enterprise layer.

      About Infra: In most of the cases it would be the typical implementation with multiple Tomcat servers (Nodes) pointing to one common database server. Since it points to the same database server, special care is required to manage common tables and data.

      Hope this clarifies/answers your question.

          Write a Reply...

          -An Initiative Of OneStopPega- Love our work? Support Us🖤