Absent Member.. Absent Member..
Absent Member..
3257 views

Import Contacts from LDAP to SM using Connect-IT

Jump to solution

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 (1)
0 Likes
1 Solution

Accepted Solutions
Absent Member.. Absent Member..
Absent Member..

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

View solution in original post

0 Likes
15 Replies
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

Hi,

 

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

 

Thanks

 

0 Likes
Absent Member.. Absent Member..
Absent Member..

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

View solution in original post

0 Likes
Absent Member.. Absent Member..
Absent Member..

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

0 Likes
Absent Member.. Absent Member..
Absent Member..

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

0 Likes
Absent Member.. Absent Member..
Absent Member..

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.

0 Likes
Absent Member.. Absent Member..
Absent Member..

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

0 Likes
Absent Member.. Absent Member..
Absent Member..

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

Absent Member.. Absent Member..
Absent Member..

Thanks Sanjeev!

 

Do I have to create a separate ServiceDesk Web Services for operator updates or can I use the create one some how?

0 Likes
Absent Member.. Absent Member..
Absent Member..

HI,

 

Yes you have to create an operator webservice using extaccess. Also define the required fields.

 

Thanks,

Sanjeev

 

0 Likes
Absent Member.. Absent Member..
Absent Member..

Hi Sanjeev,

 

I finally was able to get an Operator Add scenario running.  However, when I either produce the document or run it as a service no operator accounts are created. 

 

I have attached my scenario report.

 

Any idea's?

 

Thanks,

 

Josie

0 Likes
Absent Member.. Absent Member..
Absent Member..

Scenario Report

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.