Understanding connector agent in remote system

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Understanding connector agent in remote system

Tech

Dear experts,

we checked from the documentation that the conn bundles could be also deployed on the target system instead of that in Syncope.

We want to understand with you if it would be possible to configure a similar scenario and to validate if our understanding is correct:

  • Syncope is deployed on Server1 and the target system on the Server2.
  • Syncope calls the remote connector deployed on the Server2 (using REST?)
  • The remote connector deployed on Server2 extracts the data (SELECT FIRSTNAME, LASTNAME FROM USER;)
  • The remote connector caches the result of the query
  • Syncope extract the information from the remote connector and take them to Server1.

Is that correct?

Thanks

Reply | Threaded
Open this post in threaded view
|

Re: Understanding connector agent in remote system

ilgrosso
Administrator

Hi,
a ConnId Connector Server [1] can be essentially seen as a remote container for connector bundles.

Normally, Syncope is configured to look up for connector bundles from a local directory, but there are more options [2], including referencing connector servers.

Once a (Java or .Net) connector server is set up and running, Syncope will be able to use the connector bundles deployed there as if they were instead deployed in a local directory.

As you can imagine, this is especially useful when, for example, you are running Syncope on Linux but need to provision by using PowerShell scripts, which require to be run on Windows.
In this case, all you need is to
  1. deploy a Java connector server on Windows
  2. deploy the ConnId CMD bundle [3] onto such connector server
  3. write the PowerShell scripts
  4. configure Syncope (as explained in [2]) for using such connector server
  5. use the Admin Console to configure the CMD bundle as if it was deployed locally
The communication between Syncope and ConnId connector servers is based on a TCP protocol defined by ConnId, which can also use SSL (as explained in [2]).

HTH
Regards.

On 22/02/2017 14:22, Tech wrote:

Dear experts,

we checked from the documentation that the conn bundles could be also deployed on the target system instead of that in Syncope.

We want to understand with you if it would be possible to configure a similar scenario and to validate if our understanding is correct:

  • Syncope is deployed on Server1 and the target system on the Server2.
  • Syncope calls the remote connector deployed on the Server2 (using REST?)
  • The remote connector deployed on Server2 extracts the data (SELECT FIRSTNAME, LASTNAME FROM USER;)
  • The remote connector caches the result of the query
  • Syncope extract the information from the remote connector and take them to Server1.

Is that correct?

Thanks

-- 
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/