[midPoint] Re. Upgrading the AD connector server & connector

[Deepak Natarajan]

Hi Ivan -

Apologies for the late reply.

Let me tell you the whole story :) So when I was trying to get the AD
resource to work on midpoint, I realised that there were newer version of
both the .NET connector server, and the connector itself (I landed up on
Oracle's site when I was investigating some issue and found everything
there).

The connector server version is :
Connector Server 11.1.2.1.0 - July 2, 2013
And the AD connector : 1.1.0.6380

So after the connector "discovery" step (after I imported my connector host
configuration), I realised that now the list of connectors had TWO
connectors - the old one  (I cannot remember the version exactly) and a
definition for the new one (1.1.0.6380). It seems that both of these
definitions have the same connector type :

Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector

So now, when I imported the AD resource, there was an error - it seems that
the query inside <connectorRef>, the <q:equal> query, returns two matches
(since I have both the definitions).

So just to test this, I went to the object list and edited the Connector
object (the new one) and just modified the connector type string a little.
And then it worked.

Subsequently I manually deleted the old connector definition so there are
no conflicts.

I hope this clarifies your question..?

-deepak




On 31 October 2013 08:14, Ivan Noris <ivan.noris at evolveum.com> wrote:

>  Hi Deepak,
>
> can you please clarify why you did have to change the connectorType?
>
> After you did the Connector Discovery, was the connector object created in
> midPoint? In my case, the connector object contains:
>
>
> <connectorType>Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector</connectorType>
>
> After that, you imported your AD resource, (with original connector
> reference) - didn't that work? Was this the reason why you had to update
> the connector type?
>
> AFAIK you never have to update anything in the connector object itself (or
> I've never had to).
>
> Regards,
> Ivan
>
>
> On 10/30/2013 11:20 AM, Deepak Natarajan wrote:
>
>
>  Hi -
>
>  I'm experimenting with updating the .NET connector server and the
> connector itself (for midpoint 2.2). I don't know if I should be doing
> this, but what the heck :)
>
>  I obtained the "latest" .NET connector server from Oracle and installed
> it on Windows Server 2008 R2. And also the latest active directory
> connector.
>
>  On midpoint I configured the connector host - no errors here, the
> discovery was successful.
>
>  In the list of connector objects, I see a new connector now :
> ICF Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector
> v1.1.0.6380 @APOS/AD Connector Server (Vejle)
>
>  [
> I had to adjust the schema for this and change the ConnectorType to
>
> <connectorType>Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector.1.1</connectorType>
> to avoid an error when importing the resource again]
>
>  When I try to test my new AD resource, I get the following error below :
>
>   Error resolving connector reference in
> resource:70a9c241-4c8e-4d72-b3f2-79015e476299(APOS AD (Vejle) Resource):
> Error creating connector instace: The classes (JAR) of
>
> *connector: ICF
> Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector v1.1.0.6380
> @APOS/AD Connector Server (Vejle)
> (OID:637e281c-dc20-41f5-8197-b83886ec4319) were not found by the ICF
> framework; connector
> type=Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector.1.1,
> version=1.1.0.6380 Cause: *
> The classes (JAR) of connector: ICF
> Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector v1.1.0.6380
> @APOS/AD Connector Server (Vejle)
> (OID:637e281c-dc20-41f5-8197-b83886ec4319) were not found by the ICF
> framework; connector
> type=Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector.1.1,
> version=1.1.0.6380
> [ HIDE ERROR STACK ]
> *com.evolveum.midpoint.util.exception.ObjectNotFoundException: The classes
> (JAR) of connector: ICF
> Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector
> v1.1.0.6380 @APOS/AD Connector Server (Vejle)
> (OID:637e281c-dc20-41f5-8197-b83886ec4319) were not found by the ICF
> framework; connector *type=Org.IdentityConnectors.ActiveDirectory.ActiveDirectoryConnector.1.1,
> version=1.1.0.6380
> at
> com.evolveum.midpoint.provisioning.impl.ConnectorManager.createConfiguredConnectorInstance(ConnectorManager.java:147)
> at
> com.evolveum.midpoint.provisioning.impl.ConnectorManager.getConfiguredConnectorInstance(ConnectorManager.java:122)
> at
> com.evolveum.midpoint.provisioning.impl.ResourceManager.getConnectorInstance(ResourceManager.java:803)
> at
> com.evolveum.midpoint.provisioning.impl.ResourceManager.completeResource(ResourceManager.java:244)
> at
> com.evolveum.midpoint.provisioning.impl.ResourceManager.putToCache(ResourceManager.java:144)
> at
> com.evolveum.midpoint.provisioning.impl.ResourceManager.getResource(ResourceManager.java:138)
> at
> com.evolveum.midpoint.provisioning.impl.ProvisioningServiceImpl.getObject_aroundBody0(ProvisioningServiceImpl.java:189)
> at
> com.evolveum.midpoint.provisioning.impl.ProvisioningServiceImpl$AjcClosure1.run(ProvisioningServiceImpl.java:1)
>
>  Does this mean my experiment has failed? It looks like something in the
> midpoint core has to change to accommodate new connector versions?
>
>  Thanks!
>
>  -deepak
>
>
> _______________________________________________
> midPoint mailing listmidPoint at lists.evolveum.comhttp://lists.evolveum.com/mailman/listinfo/midpoint
>
>
> --
>   Ing. Ivan Noris
>   Consultant
>   Evolveum, s.r.o
>   ___________________________________________________
>   "Semper cautus - semper paratus - semper idem Vix."
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint
>
>


-- 
Trilobyte Systems ApS
Copenhagen, Denmark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20131104/e603bb5d/attachment.htm>