Any suggestions on how to promote from dev to test to prod and manage the database without re-keying the configuration please?
Promoting from one environment to another
promoting from one environment to another
On August 16th, 2011 mbh says:
We are a charity in the UK deploying IMIS for the first time to service 100,000 members and 200 staff on an ASI hosted infrastructure
We have been told by the ASI Consultant that there is not way of segregating configuration data from actual members data (not the WCM element)
As we move from dev to prod for the first time it shouldnt be an issue but when we get to change things, they indicate we would need to manually key in the configuration each time, but we do not know how large a job this will be
I would have expected the config tables to be readily identifiable and there to be no issue????
Grateful for your views please
MBH
Normally for a new
On August 17th, 2011 lpapageorgiou says:
Normally for a new implementation we keep a blank database that is purely used for setup. So no records or transactions are processed in here (unless you want to add some staff records).
We then have a separate database to run test conversions. For go live we then run the conversion in the blank database that should have all the latest setup. So during that time, configuration changes are made manually to both databases.
Why would you want to automatically transfer configuration after go live?
Leo
promoting between environments
On August 18th, 2011 mbh says:
The platform is being rolled out in tranches, so prod can have some but not all of the config on board when we reach the next tranche, which might have sizeable changes, it sounds as though we have to rekey the config from dev to test and then to prod on each move????
Re-keying introduces the opportunity for further human error
I am told this is not how other crms work such as MS Dynamics
Any suggestions
Mike
At the end of the day all of
On August 18th, 2011 lpapageorgiou says:
At the end of the day all of the configuration changes are stored in the database, so you can script them out and move the data across that way if you like.
What type of configuration changes did you want to move across? I have a script that compares the configuration between two databases if that helps...
Leo
promoting between environments
On August 18th, 2011 mbh says:
yes please Leo, it may help.
Where are the config settings held in the database?
Mike
What is your email address?
On August 18th, 2011 lpapageorgiou says:
What is your email address? The script will give you an idea of where things are stored.
Note: The script compares differences between gen tables, member types, UD tables and windows, activity type differences, missing reports, general system setting differences.
promoting between environments
On August 18th, 2011 mbh says:
Depends on what you mean by config
On August 22nd, 2011 Bruce Wilson says:
Some areas of iMIS are designed for export and import. IQA and business objects are especially suited to this. If you get any "document" (query, BO, report, etc.) the way you like it, you should be able to export it from one database and import it to the other, so long as:
- The document does not have custom security applied. Set it back to "Administrator Full Control" before exporting, then change the access after import.
- The document refers only to standard business objects, or BOs that were already created in one database before it was copied to the other, or that have been exported from one and imported to the other. If the object it depends on doesn't follow these rules, it will have a different internal key, and iMIS will reject the import.
Other areas may require a bit more effort. If you manually export Gen_Tables, iMIS has an import available. System_Params and SystemConfig are usually pretty easy to synchronize manually (but *definitely* make a backup first).
In general, this is why most experienced AiSPs keep a fully-configured-but-empty database. That's really the easiest way to be sure.
--
Bruce Wilson
Director, Technical Services
RSM McGladrey, Inc.
What exactly are you trying
What exactly are you trying to promote? Are you building a WCM website in dev? Are you just making basic configuration changes?