Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

LDAP Search object

Avatar

19-10-2005

Someone can explain how to use this standard component?



I'm trying to use it in a demo workflow, but I can't insert the base DN in

the Settings Tab and so I can't say what are the attributes I'm interested

in.

Also, how can I insert the parameters for the bindings? Does it use the

parameters from Adobe LiveCycle platform settings?



Thanks,

Alessio

Replies

Avatar

19-10-2005

OK...I solved the problems related to the base DN and other options setup.

But, my workflow is always stalled after the first user compile the form.



What I am trying to do is quite simple.

1° user compile a form inserting a userid.

Then I have to do a LDAP search with this component in order to extract from

the LDAP the email of the user inserted in the form.



I do this. And I think it works. But at this point the process always

stalled, because of course there isn't an action following LDAP Search.

I try to insert a User Action, in which appears another form that displays

userid and email, but the process stalled before arriving this point.



Any suggestion?



Thanks,

Alessio

Avatar

Avatar
Boost 5
Level 9
HowardTreisman
Level 9

Likes

5 likes

Total Posts

936 posts

Correct Reply

9 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 5
Affirm 3
View profile

Avatar
Boost 5
Level 9
HowardTreisman
Level 9

Likes

5 likes

Total Posts

936 posts

Correct Reply

9 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 5
Affirm 3
View profile
HowardTreisman
Level 9

19-10-2005

Hi



A couple of suggestions:

1. Please send the exception that was reported when the process stalled.

2. Please download the VariableLogger QPAC from http://www.avoka.com/avoka/qpac_library.shtml - this will enable you to easily see what the values of your process variables are after running the LDAP qpac.

3. You may want to use a simpler QPAC to do what you need - we have one called LookupUser that's much easier to use than the LDAP one. It's not available for download yet, because it's only in Beta, but I'd be happy to send it to you. Send me an email at htreisman@avoka.com if you'd like a copy.



Howard



Howard Treisman

Avoka Technologies

Specializing in Custom QPAC development and LiveCycle Solutions

http://www.avoka.com/avoka/qpac_library.shtml

Avatar

16-11-2005

One More query on LDAP QPAC.



Is it possible to search email and display name of process creator ??

We tried to use forn variable "creator_id" but how to use this we are not able to understand.

Avatar

Avatar
Boost 5
Level 9
HowardTreisman
Level 9

Likes

5 likes

Total Posts

936 posts

Correct Reply

9 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 5
Affirm 3
View profile

Avatar
Boost 5
Level 9
HowardTreisman
Level 9

Likes

5 likes

Total Posts

936 posts

Correct Reply

9 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 5
Affirm 3
View profile
HowardTreisman
Level 9

16-11-2005

Hi



The creator_id is an internal workflow id that does not exist in LDAP, so you can't use the LDAP QPAC to look it up.

You CAN use the LookupUser QPAC we've developed.

You can download a beta from http://www.avoka.com/betaqpacs/

This will return the email address, login id, and lots of other details about the designated user.



Howard



Howard Treisman

Avoka Technologies

Specializing in Custom QPAC development and LiveCycle Solutions

http://www.avoka.com/avoka/qpac_library.shtml

Avatar

Avatar
Boost 5
Level 9
HowardTreisman
Level 9

Likes

5 likes

Total Posts

936 posts

Correct Reply

9 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 5
Affirm 3
View profile

Avatar
Boost 5
Level 9
HowardTreisman
Level 9

Likes

5 likes

Total Posts

936 posts

Correct Reply

9 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 5
Affirm 3
View profile
HowardTreisman
Level 9

16-11-2005

PS "creator_id" is not a form variable. It's a process variable, or more correctly, a process-instance variable. (Picky, picky...:-)

Avatar

16-11-2005

Hellow Howard,



We know that "creator_id" is a form variable and using that in SQL Qpac we can find the details of person who is initiating the workflow.



I am having your "Lookupuser" QPAC can you tell me how we can find the person detail who is initiating the Workflow using that QPAC

Avatar

Avatar
Boost 5
Level 9
HowardTreisman
Level 9

Likes

5 likes

Total Posts

936 posts

Correct Reply

9 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 5
Affirm 3
View profile

Avatar
Boost 5
Level 9
HowardTreisman
Level 9

Likes

5 likes

Total Posts

936 posts

Correct Reply

9 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 5
Affirm 3
View profile
HowardTreisman
Level 9

17-11-2005

Hi

(This is from memory, I don't have the QPAC installed on this machine, so I'm not 100% sure this is correct, but it should be very close.)

Inputs tab:

Type: Auto

Any User Identifier: {$/process_data/creator_id$}

(Or you could use PrincipalId for a more efficient search)



Output tab:

Select any of the outputs you want, and place it into a variable. All the variables expect string types, except Found and User Is Current, which are booleans (or numeric).

The UID String is the name that the user logs into FM or adminui with.



Howard



Howard Treisman

Avoka Technologies

Specializing in Custom QPAC development and LiveCycle Solutions

http://www.avoka.com/avoka/qpac_library.shtml

Avatar

20-11-2005

Hello,<br /><br />I have also been attempting to use the LDAP QPAC that is included with the SDK. I have added it to a demo process, configured all the properties in the dialog and ran the test. The test comes back with what I would expect. No errors. <br /><br />My simple search is just looking for the department of a user in my Active Directory. The test does return back the correct department and a row count of 1. This is all good. But...<br /><br />When I attempt to run the process from Form Manager, the process stalls every time on the LDAP search action. When I look up details on the stalled action this is the first few lines of the error I get. <br /><br />****************************************************************<br /><br />javax.naming.NoInitialContextException: Cannot instantiate class: [Root exception is java.lang.ClassNotFoundException: ]<br /> at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)<br /> at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)<br /> at javax.naming.InitialContext.init(InitialContext.java:223)<br /> at javax.naming.InitialContext.<init>(InitialContext.java:197)<br /> at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:82)<br /> at com.avoka.workflow.qpac.ldap.LdapBroker.<init>(LdapBroker.java:84)<br /> at com.avoka.workflow.qpac.ldap.LdapService.execute(LdapService.java:88)<br /> at com.adobe.workflow.engine.PEUtil.executeAction(PEUtil.java:184)<br /><br />****************************************************************<br /><br />Has anyone had any success with this QPAC?<br /><br />Thanks<br /><br />Pete

Avatar

20-11-2005

I have found success. I added the following to the deployment settings for the LDAP search QPAC.



Inital_context_factory: com.sun.jndi.ldap.LdapCtxFactory

provider_URL: ldap://localhost:389

UserName: Admin

Password: *******

Other_Properties: [left blank]



Pete L