Hi Santosh,
I had a similar problem sometime back with CX LDAP endpoint. The constraint is, Connector can be built over 1 STRUC OC with multiple AUX OCs.
However, still there are two options with you:
Option 1: Two Connectors
Create two CX JDAP custom connectors. Once created, create their separate Account Templates. While provisioning, single Provisioning Role can be attached with these two separate Account Templates. Connector will make separate entries for CRUD operation but in single application.
Pros: Clean solution and easy to maintain.
Cons: Explore & Correlate (E/C) operations have to handled in a well planned manner
Option 2: Operation Bindings (OB)
Create only single connector with any 1 STRUC OC which has max no. of attrs. For updating to other attrs, OB needs to be used which is nothing but JavaScripts using JNDI code. JS can make entries and do CRUD operations in LDAP. Business logic has to be written for that.
Pros: Single Connector, no problem with E/C operations
Cons: Development code needs to maintained and certified everytime change/upgrade happens
Hope that helps.
Regards,
Sumeet