• State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 93 subscribers
  • Views 469 views
  • Users 0 members are here
Options
Related

Sync project not flowing ITShopOrg.UID_ParentITShopOrg

craigehunter
over 1 year ago

Hi,

Just wondering, before I raise with OI support, if anyone has encountered an issue similar to the one below.

I have a sync project that syncs system roles to ITShop shops. Mapping is very basic:

Ident_Org <- Ident_ESet

ITShopInfo <- vrtITShopInfo ("SH")

UID_ParentITShopOrg <- vrtUID_ParentITShopOrg (<uid of parent>)

But when I run the sync, only the first two attributes are synced, and UID_ParentITShopOrg is ignored. This is true for both simulation and execution.

For troubleshooting I have refreshed the schema, deleted and recreated the UID_ParentITShopOrg  mapping rule.

Any thoughts/help will be appreciated,

Craig

  • 0 over 1 year ago

    Mate,

    Do the following to get a trace log and you should see what's going on.

    HTH, B.

    Trace Debug Connector/Sync Issues

    Add these lines to globallog.config or stdioprocessor.exe.config:    

    Find StdioProcessor.exe.config in your job server installation dir.

    Add the below lines:

           <rules>

                  <!-- Debug logger definitions for trace log -->

                  <logger name="SystemConnector" minlevel="Trace" writeTo="debug"/>

                  <logger name="*" minlevel="Trace" writeTo="debug"/>

           </rules>

     In the file here (snip from config file):

      <nlog autoReload="true" xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="">www.w3.org/.../XMLSchema-instance">

        <variable name="appName" value="StdioProcessor"/>

        <include file="${basedir}/globallog.config" ignoreErrors="true"/>

    ================== just here in the file ======================

      </nlog>

    Then save it and run again ……. Whichever user the js runs as go to c:\users\<jsuser>\appdata\local ……….. and keep going to one identity manager …. Then stdioprocessor …. Then debug.

    You should get a trace log/debug file in there.