Best Practices when splitting a large model to several small ones : Portal

Start a new topic

Answered

Best Practices when splitting a large model to several small ones

Sebastian.agnvall

started a topic 7 months ago

In a model, there are currently several diagrams that have limited to no relations between each other. It has therefore been discussed to take this model, extract the diagrams, and put these into their own models and data locations. This is primarily done to ease future model deployments.

In order to carry out a task like this, what would be the recommended steps to take, and what type of risks may occur?

Best Answer

Stephanie Fourrier said 6 months ago

Hi Sebastian,

one of our consultants proposed the following step by step actions to achieve your needs with less risk :

Export model
Rename model in xml file (search & replace model name)
Import new model (ideally on a dedicated instance and repository if you want no impact in case of maintenance or xDM upgrades)
Delete unnecessary elements
Create new data location and deploy the new model
Synchronize data (via integration middleware and proper data loads, or via insert select sql statements)

We hope this is helpful!

Stéphanie.

1 Comment

Stephanie Fourrier

said 6 months ago

Answer

Hi Sebastian,

one of our consultants proposed the following step by step actions to achieve your needs with less risk :

Export model
Rename model in xml file (search & replace model name)
Import new model (ideally on a dedicated instance and repository if you want no impact in case of maintenance or xDM upgrades)
Delete unnecessary elements
Create new data location and deploy the new model
Synchronize data (via integration middleware and proper data loads, or via insert select sql statements)

We hope this is helpful!

Stéphanie.