Change Prod Repository Type Without Reinstallation
F
Fathia Jama
started a topic
over 2 years ago
Change Prod Repository Type Without Reinstalling the xDM application?
Best Answer
F
Fathia Jama
said
over 2 years ago
Refer to official Semarchy xDM documentation for complete details on Repository Type.
This article provides details on changing Repository Type, in a Production environment.
In some instances, the Prod repository may have been initially created as Design, vs Deployment, which is the recommended Repository Type for Production environments. With the Deployment type repository, you can only import closed model editions and cannot edit them.
Create a brand new schema on your prod database.
Export any existing Prod models.
Update your repository datasource in your startup configuration to point to the brand new schema created.
Restart Tomcat in order to persist changes. After restart, the administrator will be prompted to create a new repository. Choose the repository type DEPLOY.
Follow this article to reuse the existing data locations, as well as the data contained within.
Deploy the previously exported models into their corresponding data locations.
Refer to official Semarchy xDM documentation for complete details on Repository Type.
This article provides details on changing Repository Type, in a Production environment.
In some instances, the Prod repository may have been initially created as Design, vs Deployment, which is the recommended Repository Type for Production environments. With the Deployment type repository, you can only import closed model editions and cannot edit them.
Create a brand new schema on your prod database.
Export any existing Prod models.
Update your repository datasource in your startup configuration to point to the brand new schema created.
Restart Tomcat in order to persist changes. After restart, the administrator will be prompted to create a new repository. Choose the repository type DEPLOY.
Follow this article to reuse the existing data locations, as well as the data contained within.
Deploy the previously exported models into their corresponding data locations.
R
Ron Branch
said
7 months ago
We were unable to locate the PDF referred to in this section: 5. Follow the attached pdf document to reuse the existing data locations, as well as the data contained within. (PDF document attached to the "Question" section of article)
Please advise as to the location of the Questions section of this thread.
P
Pranoti Kotangale
said
2 days ago
We also need to add secret token in setenv.sh, as the setup asks for it when the repository datasource is changed to point to new repository schema.
Fathia Jama
Change Prod Repository Type Without Reinstalling the xDM application?
Refer to official Semarchy xDM documentation for complete details on Repository Type.
This article provides details on changing Repository Type, in a Production environment.
In some instances, the Prod repository may have been initially created as Design, vs Deployment, which is the recommended Repository Type for Production environments. With the Deployment type repository, you can only import closed model editions and cannot edit them.
- Oldest First
- Popular
- Newest First
Sorted by Oldest FirstFathia Jama
Refer to official Semarchy xDM documentation for complete details on Repository Type.
This article provides details on changing Repository Type, in a Production environment.
In some instances, the Prod repository may have been initially created as Design, vs Deployment, which is the recommended Repository Type for Production environments. With the Deployment type repository, you can only import closed model editions and cannot edit them.
Ron Branch
We were unable to locate the PDF referred to in this section:
5. Follow the attached pdf document to reuse the existing data locations, as well as the data contained within. (PDF document attached to the "Question" section of article)
Please advise as to the location of the Questions section of this thread.
Pranoti Kotangale
We also need to add secret token in setenv.sh, as the setup asks for it when the repository datasource is changed to point to new repository schema.
export SEMARCHY_SETUP_TOKEN=mySecretValue
-
xDM Compatibility with Java 17?
-
xDM on Docker
-
How to Upgrade Apache Tomcat?
-
Application Server Gives 404 Error
-
Amazon Aurora support
-
Is It Possible to Import a V5.1.1 Data Model to V5.2.8?
-
"500 Internal Server Error" While Opening with Localhost
-
Enable Access to Azure File Storage?
-
Why am I getting Status 404 -- Not Found Error on Azure?
See all 29 topics