Ruleset components are stored local and on the server. After provisioning the local component will be stored on the server.
For testing multiple editing usage, we removed both the server and the locally stored .CLS file. When opening the ruleset out of Datastage and select the just deleted classification file, Datastage will present the previous locally stored CLS and create this file on the filesystem.
Our questions:
- Where does datastage gets this information from?
- Are ruleset components also stored in the XMETA database?
- How can we prevent that in case of multiple editors, old local classification files will override newer files on the server?
Thanks in advance!
Where does QualityStage store ruleset component data?
-
- Premium Member
- Posts: 8
- Joined: Wed Aug 30, 2006 3:50 am
- Location: the Netherlands
- Contact:
In my quick testing with 8.5, the rule set is 'locked' when one user opens it for editing. A second person will get a warning message, so there should not be a case of 'multiple editors'.
When the first person is modifying a rule and select double click any component (classification, dictionary, etc), or select the overrides option, the data is copied from the repository (XMETA) to the client file system (C:\IBM\InformationServer\Clients\Classic\QS_TEMP). When you close the editor, the data is put back into the repository (XMETA). You will then need to provision the rule set to put the changes to the server.
When the first person is modifying a rule and select double click any component (classification, dictionary, etc), or select the overrides option, the data is copied from the repository (XMETA) to the client file system (C:\IBM\InformationServer\Clients\Classic\QS_TEMP). When you close the editor, the data is put back into the repository (XMETA). You will then need to provision the rule set to put the changes to the server.
Regards,
Robert
Robert
-
- Premium Member
- Posts: 8
- Joined: Wed Aug 30, 2006 3:50 am
- Location: the Netherlands
- Contact: