Re: Understanding connector agent in remote system
a ConnId Connector Server  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 , 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
deploy a Java connector server on Windows
deploy the ConnId CMD bundle  onto such connector server
write the PowerShell scripts
configure Syncope (as explained in ) for using such
use the Admin Console to configure the CMD bundle as if it was
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 ).
On 22/02/2017 14:22, Tech wrote:
we checked from the documentation that the conn bundles could
be also deployed on the target system instead of that in
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
Syncope calls the remote connector deployed on the Server2
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.