Import Contacts from LDAP to SM using Connect-IT

Hi Experts,

 

I am trying to import all the contacts from LDAP to Service Manager using Connect IT. I am able to import the contacts successfully.

 

The issue is that, I am not able to populate the "HP Service Manager ID(operator. id)" of contact. g with the sAMAccountName from LDAP using CIT.

Can anyone please help me with the mapping for this particluar field. I am Having hard time synchonizing contacts with operators.

 

Thanks and Regards,

Sanjeev

Tags:

  • Hi,

     

    Please provide screen shot of your scenario mapping with sestination feilds & contact.g form with operator.g.

     

    Thanks

     

  • Verified Answer

    Hi,

     

    The issue got resolved.

     

    Modified the Contact's External Access Definition by adding operator.id and giving a value to it.

    Restarted the CIT. The added value in extaccess got displayed in CIT's destination source.

    Mapped the value with the desired LDAP attribute.


    Worked like Charm. Contacts and operators got synchronized.

     

    Thanks,

    Sanjeev

  • Does anyone have a Connect-IT LDAP to SM scenario they could share?

  • Hi Josie,

     

    Wont be able to share the scenario because I dont have the access to the Connect IT Server right now. But can assist you in building the scenario.

     

    Thanks and Regards,

    Sanjeev

  • I am really interested in seeing what AD/LDAP Elements are used and there  Filter clauses.  I would also like to see how people are filtering in their mapping scripts.

  • I am really interested in seeing what AD/LDAP Elements are used and there  Filter clauses.  I would also like to see how people are filtering in their mapping scripts.

  • Another example would be to see how people are parsing the AD\LDAP name from Distguished Name to contact.name

  • Another example would be to see how people are parsing the AD\LDAP name from Distguished Name to contact.name

  • Hi,

     

    As far I remember I have created a scenario which imports the contact from Ad to SM and creates operator at the same time.

     

    Scenario:

    (To import users from LDAP)

    Source Connector 1: LDAP Connector

    Destination Connector 1: ServiceDesk Web Services.(Need to publish the table as web service using extaccess. By default Contact table is published as web service.)

    Mapping 1:

    Document Type: Create Contacts

    contact.name(Contact)-->[samAccountName](LDAP)

    email(Contact)--->[samAccountName] "@yourdomain.com"(LDAP)

    full.name(Contact)--->[cn.person](LDAP)

    operator.id(Contact)--->[samAccountName](LDAP) (Note: You wont find opertor.id in the destination element list untill and unless you add it in contact web services from extaccess)

    Key:

    contact.name(Contact)--->[samAccountName](LDAP)

     

    Document Type: Update Contacts

    contact.name(Contact)-->[samAccountName](LDAP)

    email(Contact)--->[samAccountName] "@yourdomain.com"(LDAP)

    full.name(Contact)--->[cn.person](LDAP)

    operator.id(Contact)--->[samAccountName](LDAP)

    Key:

    contact.name(Contact)--->[samAccountName](LDAP)

     

    (Create operators)

    Source Connector: Destination Connector 1

    Destination Connector 2: ServiceDesk Web Services(Publish the operator table as web service from extaccess also define the fields that you want to use while defining the mapping)

    Mapping 2:

    Document Type: Create Operators


    operator.id(Contact)--->name(Operator)

    contact.name(Contact)--->contact.name(Operator)

    full.name(Contact)--->full.name(Operator)

    email(Contact)--->email(Operator)

    key:

    operator.is(Contact)--->name(Operator)

     

    Document Type: Update Operators


    operator.id(Contact)--->name(Operator)

    contact.name(Contact)--->contact.name(Operator)

    full.name(Contact)--->full.name(Operator)

    email(Contact)--->email(Operator)

    key:

    operator.is(Contact)--->name(Operator)

     

     

    Now, run the scenario.

     

    Hope that helps,

    Sanjeev

  • Hi,

     

    As far I remember I have created a scenario which imports the contact from Ad to SM and creates operator at the same time.

     

    Scenario:

    (To import users from LDAP)

    Source Connector 1: LDAP Connector

    Destination Connector 1: ServiceDesk Web Services.(Need to publish the table as web service using extaccess. By default Contact table is published as web service.)

    Mapping 1:

    Document Type: Create Contacts

    contact.name(Contact)-->[samAccountName](LDAP)

    email(Contact)--->[samAccountName] "@yourdomain.com"(LDAP)

    full.name(Contact)--->[cn.person](LDAP)

    operator.id(Contact)--->[samAccountName](LDAP) (Note: You wont find opertor.id in the destination element list untill and unless you add it in contact web services from extaccess)

    Key:

    contact.name(Contact)--->[samAccountName](LDAP)

     

    Document Type: Update Contacts

    contact.name(Contact)-->[samAccountName](LDAP)

    email(Contact)--->[samAccountName] "@yourdomain.com"(LDAP)

    full.name(Contact)--->[cn.person](LDAP)

    operator.id(Contact)--->[samAccountName](LDAP)

    Key:

    contact.name(Contact)--->[samAccountName](LDAP)

     

    (Create operators)

    Source Connector: Destination Connector 1

    Destination Connector 2: ServiceDesk Web Services(Publish the operator table as web service from extaccess also define the fields that you want to use while defining the mapping)

    Mapping 2:

    Document Type: Create Operators


    operator.id(Contact)--->name(Operator)

    contact.name(Contact)--->contact.name(Operator)

    full.name(Contact)--->full.name(Operator)

    email(Contact)--->email(Operator)

    key:

    operator.is(Contact)--->name(Operator)

     

    Document Type: Update Operators


    operator.id(Contact)--->name(Operator)

    contact.name(Contact)--->contact.name(Operator)

    full.name(Contact)--->full.name(Operator)

    email(Contact)--->email(Operator)

    key:

    operator.is(Contact)--->name(Operator)

     

     

    Now, run the scenario.

     

    Hope that helps,

    Sanjeev