After disussing about the features supported by LDAPBC ,just thought of describing some features in detail for a better understanding , lets start with the search and search referral feature implemented by the LDAPBC in addition to the add , update , delete.Search can be performed for an entry in a specified OU with a specific DN , once you find the entry we can fetch the required attribute and its value.OU is the Organization Unit DN is the Distinguished Name.Lets have a look at the structure first in the below image.
In the above image , Say we are searching for the person whose uid is scarter we have to search under ou=mostral,dc=stc,dc=com
.Lets do the same with our LDAPBC
What all it needs is Netbeans installation with design time plugins for ldap , and a Glassfish Application server with JBI environment and LDAP binding component installed.
Creating Search Sample Project
-
Create a new BPEL project
-
Create two WSDL Documents, one defining inbound http soap trigger and one defining outbound LDAP Binding Component
-
LDAP wsdl can be created using the Wsdl from LDAPserver or Wsdl from LDIF file options available in the wizard.
Wsdl from LDAP server
In the above image we can set the search filter , ie if (inetOrgPerson.uid )= = ?? please fetch me the roomNumber , Now the input for the uid will be provided from the http soap wsdl ,and the response will be routed to the soap reply.
4 Create a BPEL project , to orchestrate
5. Build the BPEL module to create the Service Unit.
6.Create the Composite Application
7.Add the created BPEL Module to the Composite Application
8.Build the Composite Application to the Service Assembly
9 Deploy the Composite Application
10 Now trigger the soap test case with the following input for the below output
Output file
Now what is search referral feature ?? when you try out the search feature you have the provision to search in only one instance of an ldap server , where as using search referral you can configure your ldap server for a referral to some other ldap server , and once you perform a search in the first server and fail to locate it , it automatically searches in the referred server and gets you the value.Thats not it yet ,we have an option in the xsd to configure whether you want to follow and go to the referred server for searching or ignore going to the referred server , or throw an exception that the entry is not found and restrict the search to the first ldap server.Seems to be interesting right ,lets try out how to configure the server
The above is the configuration for a DSEE serve using command line.
Now in the xsd you have to just mention the referral default to follow such that the search will automatically follow the second ldapserver.
<xsd:element name="referral" type="xsd:string" default="follow"></xsd:element>
Rest of the process is as same as the above search project.
Try out these features using LDAP BC and please let us know your feedback on the blog as well as the BC.