What is Connector made by java and xml code in sailpoint? Please explain use of it in detail?

I want to know detail about it.

Hi Eram,
Generaly speaking.

Java Connector is a class which contains all methods needed to connect to the target application. For example in java connector class you implement “provision” method which is called whenever IIQ executes provisioning via this connector.

XML code is an instance of the connector class (it’s not exactly instance of the class but lets assume it is to simplify the answer) and in IIQ is called Application. It cantains all instance specific parameters of the connected application.

For example.
Active Directory connector jar contains all methods which allows IIQ to connect to any AD application. When you create an XML - Your Active Directory it will contain all details which Java connector needs to know in order to connect to your AD instance.

XML is also generic for all connectors as one of the parameters in it points to which connector class should be used for this this particular connection.

Hope its clear for you what is the difference between tlthis two terms. If you have any other question feel free to ask.

There are many options for making custom connectors. The decisions start with determining how to extract the aggregation data. If you need to write custom code to extract the data from the target, you will need to write a custom Connector. There are some examples out there of fully built custom connectors. If you can get your data via a delimited file or JDBC query, then you can use one of those connectors for the aggregations and then use an IntegrationConfig to do provisioning.

The Java code is the backbone of any of these custom connectors and the XML (for IntegrationConfig) or xhtml (for custom Connector) provides SailPoint with the framework that connects the SailPoint libraries to your target.

Sorry, your question is not very detailed. This is the best I can do without specifics. Can you elaborate?

I want to, What is the use of custom connector ? Why it is being used?

When there is no OutOfTheBox (OOTB) connector to fulfill your requirements, you can create a custom connector.

There is hardly any need to create a custom connector, as there are many connectors available for IdentityIQ:
https://documentation.sailpoint.com/connectors/identityiq/landingpage/landingpages/identityiq_connectivity_landing.html

– Remold

IIQ is delivering various OoTB connectors - some of them are specific to single application like Salesforce, AD and so on.

There are also more generic connectors eg. Webservice, Delimited File they allow you to connect to different applications if they only support this way of comunication.

Custom connector is a connector which you can build whenever you want to use app specific connector which does not yet exist, it’s also usefull when you, for some reason, cannot use generic type connector.

Your way of answer is really great sir.

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.