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,
Go to Solution.
Please provide screen shot of your scenario mapping with sestination feilds & contact.g form with operator.g.
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.
Does anyone have a Connect-IT LDAP to SM scenario they could share?
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.
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
As far I remember I have created a scenario which imports the contact from Ad to SM and creates operator at the same time.
(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.)
Document Type: Create Contacts
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)
Document Type: Update Contacts
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)
Document Type: Create Operators
Document Type: Update Operators
Now, run the scenario.
Hope that helps,
Do I have to create a separate ServiceDesk Web Services for operator updates or can I use the create one some how?
Yes you have to create an operator webservice using extaccess. Also define the required fields.
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.
Can you please post the scenario. Or the mapping that you have defined to import thr operators.
However, I couldnot pull in the password of the users from LDAP to HPSM using Connect IT. If you want the operators to get authenticated from LDAP, then you need to configure the scldapconfig file.
I got my scenarios working. Thank you for your help.
I have a question on creating/filling th mangaer field.
My contact name is concatination of contact.name + (operator.id).
This statement will get me my contact.name. RetVal=UCase((RightPart(LeftPart((Replace([manager],"\","")),",OU=",0,"CN=",0)))
But how do I get the samaccount name for the name found?