| Robert Brown 2006-01-20, 6:05 pm |
| Thoughts that come to mind are
a) the Toolkit's IdResGen.zip is flawed (perhaps try the Full Install zip?)
b) the Toolkit's IdResolveKeys.properties doesn't have an ORGENTITY
entry row (ORGENTITY=@DN:DN) Unlikely...
c) the Toolkit's dn for the organization in your ORGENTITY table isn't a
match. Also unlikely since you said it is a db mirror of production.
d) a later Toolkit fixpack may correct the idresgen problem
Your xml looks valid from here...not really surprising since it works in
production.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~
As a side note, I have seen XSL translation problems with the
xmltransform utility when a variable is used for an organization's
primary key.
<!-- The orgentity reference ID that is used as the organization of
the user entities (-2003 = 'B2C Organization' in ORGENTITY) -->
<xsl:param name="OrgentityMemberID" select="-2003" />
This above line works fine when dereferencing the $OrgentityMemberID
later in the XSL file.
<!-- The orgentity reference ID that is used as the organization of
the user entities (equivalent to 'Supplier Hub Organization' in
ORGENTITY) -->
<xsl:param name="OrgentityMemberID" select="7000000000000000151" />
This will not dereference properly, forcing you to copy the organization
value everywhere in the XSL. Something about an XSL string length
limitation. I can't remember what the limit was but I did test with
increasingly larger numbers until it bombed.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~
R
> Thanks for the reply ...
>
> You are correct, the problem I am seeing is occuring in the toolkit environment. I have tested this on the server and everything resolves as expected (note the databases are replicas so it should work on both).
>
> One of the tables not resolving properly is Orgentity. The xml I have is as follows:
>
> <orgentity orgentity_id="@supp_hub_org_id" orgentityname="Supplier Hub Organization" orgentitytype="OU" dn="ou=supplier hub organization,o=supply chain management organization,o=root organization">
> <ISA>
> <member member_id="@supp_hub_member_id" type="O" state="1" />
> </ISA>
> </orgentity>
>
> <ffmcenter ffmcenter_id="@marketplace_ffmcenter_id" member_id="@supp_hub_member_id" name="MarketPlace Home" defaultshipoffset="0" />
>
> The result is a new orgentity_id & member_id is generated even though that record does exist exactly in the db. Also, for ffmcenter, the member_id is not resolved.
>
> Any idea on what I can try to get my toolkit environment working?
>
|