on 11-24-2008 4:10 AM
I have used "Export Repository schema" and exported the schema,But when i tried to create the repository from that exported schema,the repository is created
But am not able to Logon into it.I have used the same logon credentials as to the one i exported.
It Says invalid logons
Plz help me on this.
Hi Shifali,
Login as default Admin login and blank password and connect to the repository.
If this is working then navigate to the users table and once manually change the user's password to the previous one, and then try login in again with this newly updaated login credentials.
The users get exported and imported through this method however the users's pwd do not .So the pwd are also defaulted.
So try login in with the default Admin login and then reset your users pwds.
The possible reason for this could be the behaviour of MDM or else errors in your rep.
Correct your rep errors if any by rt clicking your rep and selecting repair.
Hope It Helped
Thanks & Regards
Simona Pinto
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does only the structures of tables comes into it.
Doesnt it carry the maps of import and syndication?
What about the ports that created in existing repository,will they not be exported?
Can you plz let me know what all/what it doesnt carry from schema.
Edited by: shifali charya on Nov 24, 2008 5:43 AM
Hi Shifali,
Below is the list of the Repository details that will be exported using the Export/Import Schema in MDM:
Item
Repository Properties
Name
Description
DBMS Server
Login
Port
Type
Languages
Table Properties
Name
Code
Description
Type
Primary Display Field
Display Fields
Unique Fields
Key Mapping
Attribute Image Variants
Text Value Image Variants
Alternative Display Fields
Field Properties
Name
Code
Description
Type
Required
Writeable Once
Matrix
Multilingual
Sort Index
Keyword
Display Field
Calculated
Sort Type
Search Tab
True Value
False Value
Default Value
Symbol
Lookup Table
Dimension
Default Unit
Decimal Places
Show Fractions
Multi-Valued
Default to Current Time
Default to Current Date
Selected Fields
Qualifier
Cache
Special Tables
Assignments*
Families
Relationships
Image Variants
Named Searches
Validations*
Admin Tables
Roles
Users
Connections
Change Tracking
Remote Systems
Ports- Ports properties not included
Links
XML Schemas
Reports
As per SP06
Hope It Helped
Thanks & Regards
Simona Pinto
Hi Shifali,
The Import and Export maps are identified using internal ids,which gets lost while transporting them using the Export/Import schema.
So if you have used the Export/import schema to transport your repository details then the Maps will not work properly.
To transport the maps the only efficient way is using the Archieve/Unarchieve option.
The schema option is more favourable when you just want to transfer the Repository design. Data, entries, and objects of the repository will not be transported using the schema option.
Workflows also will not get transfered using the schema option.
For transporting workflows you will have to rightly use the Archieve/Unarchieve option.
Hope It Helped
Thanks & Regards
Simona Pinto
Hi Shifali,
- Archieve/Unarchieve
- Master/Slave
- Duplicate Repository
These are all different options available for taking backups and Transporting the MDM rep.
It depends on which is the most appropiate method to perform the desired operation.
Archieve/Unarchieve feature are most commonly and efficiently used for transportation of your repository from one server to the other.
For eg:You can Archieve a rep in the Development server and unarchieve it on your Quality server.
Duplicating the rep is most commonly used in the following instances:
- Backup: Duplicate an MDM repository as a backup, allowing you to discard subsequent changes and revert to the point of duplication.
● Training: Use the duplicate for training purposes or experimentation by designers and other MDM repository maintenance personnel.
● Testing: Use the duplicate for testing purposes, to try out new ideas without affecting or endangering the active, online repository.
● Repartitioning: You can create the duplicate with a different number of partitions than the original.
● DBMS server transfer: You can create the duplicate under the control of a different DBMS Server than the original, to move the MDM repository from one DBMS Server to another as part of the duplication.
● DBMS brand transfer: You can create the duplicate under the control of a different DBMS brand than the original, to move the MDM repository from one DBMS brand to another as part of the duplication.
Hope It Helped
Thanks & Regards
Simona Pinto
Hi Shifali,
Archive command creats the .a2a file which can be trnasported to any system and then using UnArchive Command we can create the repository on any MDM Server while in case of Duplicate Repository it will create the duplicate on that Server itself you cannot transport it to another MDM server.
Regards,
Jitesh Talreja
Hi Shifali,
Everything will be there Ports, Remote Systems etc. This is strange why it has not included the Users. It actually compares the repository with Blank repository.
Regards,
Jitesh Talreja
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shifali,
Login with user=Admin and blank password.
My Observation It resets the Repository Users i.e. all the users will be deleted or reset to original but it does preserves the roles.
Regards,
Jitesh Talreja
Edited by: Jitesh Talreja on Nov 24, 2008 9:48 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
70 | |
26 | |
9 | |
9 | |
7 | |
6 | |
4 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.