Page 1 of 1

Problem while Ldap reader.

Posted: Thu Jul 19, 2012 2:54 pm
by praveen543
Hello

i am trying to upload data to OIA from My local Active Directory using OIA(Oracle Identity analytic) etl process.I that I am using some graph code.can any one suggest me.is it correct way or not.if any method is there pls share me.


<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Graph SYSTEM "/opt/Oracle/OIA_Install/conf/schemas/etlgraph.dtd">
<Graph name="ADread" rbacxExecuteAlways="true">
<Global>
<Metadata id="InMetadata" fileURL="/opt/Oracle/OIA_Install/import/etl/graphs/metadata/ADread.fmt"/>
</Global>
<Phase number="0">
<Node id="INPUT0" type="LDAP_READER">
<attr name="ACTIVE_DIRECTORY_URL"><![CDATA[ldap://172.30.30.38]]></attr>
<attr name="ACTIVE_DIRECTORY_USER"><![CDATA[administrator]]></attr>
<attr name="ACTIVE_DIRECTORY_PW"><![CDATA[Password123]]></attr>
<attr name="ACTIVE_DIRECTORY_BASE_DN"><![CDATA[dc\=GECOMFIN,dc\=com]]></attr>
<attr name="guiDescription"><![CDATA[Read data with new attributes from LDAP directory.]]></attr>
<attr name="filter"><![CDATA[cn=*]]></attr>
<attr name="base"><![CDATA[${ACTIVE_DIRECTORY_BASE_DN}]]></attr>
</Node>
<Node id="REFORMAT0" type="REFORMAT" transformClass="com.vaau.rbacx.etl.clover.components.ReformatAccount">
</Node>
<Node id="OUTPUT0" type="com.vaau.rbacx.etl.clover.components.DelimitedDataWriter" fileURL="/opt/Oracle/OIA_Install/import/in/ADusers1.csv"/>

<Edge id="INEDGE" fromNode="INPUT0:0" metadata="InMetadata" toNode="REFORMAT0:0"/>
<Edge id="OUTEDGE" fromNode="REFORMAT0:0" metadata="InMetadata" toNode="OUTPUT0:0"/>
</Phase>
</Graph>

when ever trying to execute this code some error will displying like Ldap_Reader
Fatal error while reading graph. Graph Name: ADread.grf
java.lang.RuntimeException: java.lang.RuntimeException: Unknown component: LDAP_READER class: LDAP_READER

pls help me out...

Thanks
praveen

Re: Problem while Ldap reader.

Posted: Thu Jul 19, 2012 3:47 pm
by kubosj
Hi,

I am afraid your issue is caused by bug: https://bug.javlin.eu/browse/CLS-743

Can you please send me your version of Server? I guess it is happening on Server, right?

Re: Problem while Ldap reader.

Posted: Fri Jul 20, 2012 8:28 am
by praveen543
yes it is OIA 11.1.1.5.0 version

Re: Problem while Ldap reader.

Posted: Mon Jul 23, 2012 9:06 am
by kubosj
I meant CloverETL Server version.

Re: Problem while Ldap reader.

Posted: Mon Mar 24, 2014 2:09 pm
by bahubba
Hi,

I am having this issue now with a third party version of CloverETL Server. I am using "Integrator Server" packaged with Oracle Endeca Information Discovery (OEID) 2.3.0. I believe the CloverETL Server version is actually 3.1.x.

I saw the ticket in the link from the first reply, but I'm not sure I understand what's going on in all of the comments and what the actual resolution is. Is there something I can do to get my version of CloverETL Server to recognize the LDAP Reader and Writer components, or was that ticket just to fix the bug in a separate release?

Re: Problem while Ldap reader.

Posted: Wed Mar 26, 2014 10:14 am
by imriskal
Dear bahubba,

As this issue releates to Endeca Data Integrator please do contact Oracle Endeca support in this matter directly. They need to be informed about this issue and will work with us directly if needed. Thank you for your cooperation!

Kind regards,

Re: Problem while Ldap reader.

Posted: Wed Mar 26, 2014 3:04 pm
by bahubba
Lubos,

That's the response I was expecting, but I appreciate the reply at least. I submitted a ticket with Oracle before posting here, but they're fairly slow to work through, so I was hoping to find a simple solution here if I could.

Re: Problem while Ldap reader.

Posted: Thu Apr 10, 2014 8:16 am
by kubosj
Dear bahubba,

We are sorry we can't help you in this matter. For OEM products we are trying to help directly with issues touching basic functionality of CloverETL like components setting, CTL2, performance, etc. As the OEM partner is allowed to change many things in CloverETL during bundling - like component existence, licensing, support for command line run, etc. - we are not able to answer such questions. This is why we are asking OEM customers to contact directly OEM partner.
Thank you for your understanding.