Question

1
Replies
327
Views
Arpita Das (Arpita_D)
ING, Netherlands

ING, Netherlands
NL
Arpita_D Member since 2013 29 posts
ING, Netherlands
Posted: May 9, 2018
Last activity: May 18, 2018
Posted: 9 May 2018 6:03 EDT
Last activity: 18 May 2018 6:54 EDT
Closed

Application merge prior to upgrade

Client say has 10+ applications in the scope of upgrade. All the applications are separate installations altogether leading to 10+ independent upgrades. They want to check the feasibility to merge 3 small- medium sized applications(say one in 7.1.8 and two in 7.1.6 and 7.1.5) through a POC.


While doing so, high level plan is to merge the rules of the selected 3 applications -


Import the Rules RAP of 7.1.6 and 7.1.5 application in 7.1.8 Rules schema and start maintaining one Rules Schema (just like performing Install and Migrate approach). Data schema would be separate for 3 of them. 7.1.6 and 7.1.5 Data Schema would be upgraded to 7.1.8. So eventually there is one Rules Schema and 3 separate Data Schema. Post the merge in 7.1.8, it will be upgraded to 7.3....Rules at one go and Data separately for 3 apps.


Questions:


1)What considerations should be taken at the App server configuration to support the above mentioned change? On App server side, Would we require to configure JNDI settings by logically separating into separate JVMs.


2) Is there any potential impact in split schema configuration with one rules and multiple data schema to support multiple applications?


3) Any best practice suggestions if there is any technical constraint or severe cons which may impact maintainability down the line.


For example - if Rules Schema of 3 apps are merged some infra sizing at the hardware end might be required, or say with this approach in future all applications have to upgrade at the same.

Client say has 10+ applications in the scope of upgrade. All the applications are separate installations altogether leading to 10+ independent upgrades. They want to check the feasibility to merge 3 small- medium sized applications(say one in 7.1.8 and two in 7.1.6 and 7.1.5) through a POC.

While doing so, high level plan is to merge the rules of the selected 3 applications -

Import the Rules RAP of 7.1.6 and 7.1.5 application in 7.1.8 Rules schema and start maintaining one Rules Schema (just like performing Install and Migrate approach). Data schema would be separate for 3 of them. 7.1.6 and 7.1.5 Data Schema would be upgraded to 7.1.8. So eventually there is one Rules Schema and 3 separate Data Schema. Post the merge in 7.1.8, it will be upgraded to 7.3....Rules at one go and Data separately for 3 apps.

Questions:

1)What considerations should be taken at the App server configuration to support the above mentioned change? On App server side, Would we require to configure JNDI settings by logically separating into separate JVMs.

2) Is there any potential impact in split schema configuration with one rules and multiple data schema to support multiple applications?

3) Any best practice suggestions if there is any technical constraint or severe cons which may impact maintainability down the line.

For example - if Rules Schema of 3 apps are merged some infra sizing at the hardware end might be required, or say with this approach in future all applications have to upgrade at the same.

Please suggest.

Regards,

Arpita

System Administration Upgrades
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.