We are using NDS-to-NDS DirXML drivers to migrate...
Articles and Tips: qna
01 Jan 2003
Q.
We are using NDS-to-NDS DirXML drivers to migrate users from our corporate Tree to a local tree. We have extended the schema of our corporate tree with auxiliary and effective classes.
In the corporate tree, we are able to map auxiliary classes' attributes. But it's not possible in the local tree--only effective classes are visible. In the corporate tree, T1, we have extended schema with two classes:
Aux class: name="AuxCLASS" with an attribute "AuxFloor". Eff class: name="EffCLASS" with an attribute "EffGroup".
In the local tree, T2, we haven't extended the schema.
We are trying to map "AuxFloor" in T1 with "L" attribute in T2. In T1, we are able to map "AuxFloor" with "L." In T2, AuxClass and all these attributes are not visible when we try to map "AuxFloor" with "L" in the Mapping Rule, but we are able to see the "EffClass" attributes.
Is it possible to replicate information in auxiliary classes through the NDS-to-NDS DirXML driver, or do we have to use effective classes?
A.
You should remove AuxCLASS and EffClass from the filters in T1. Add AuxFloor and EffGroup to the filters for the effective classes that the auxiliary classes will be used on in T1. (Probably User. You will need to check the "Show all attributes from all classes" check box on the filter editor panel.)
You can put the schema mapping rule on either tree, but not both, and either map the attributes in a nonclass-specific way, or map them for the specific classes that will have the attributes. You may have to hand edit the XML for the schema mapping rule, since I'm not sure how well the schema discovery mechanism works for auxiliary classes.
Which ever side you put the schema mapping rule on, make sure that the NDS name is the one used in that tree and the application name is the one used in the other tree. If you are really trying to get fancy and do something like map both L and AuxFloor from T1 to L on T2, you will likely have to use a stylesheet in addition to standard schema mapping rule, since the standard schema mapping rules only support one-to-one mappings.
* Originally published in Novell AppNotes
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.