Mailing-List: contact users-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@directory.apache.org
From: Mike Davis <mdavis@rez1.com>
To: <users@directory.apache.org>,
	"s_humbi" <s_humbi@yahoo.com>
References: <F3CBC3F58409A043B35FC3F043E26E2BC89168@MX304CL01.corp.emc.com> <41a09471-643c-f924-7ed1-6833876e77d9@gmail.com> <080201d27d74$18d164a0$4a742de0$@rez1.com> <CAB3ntOu-QzVXX08fO9Q2VSKZzkeYEiOC4+DdWjiq2=SR2R9s=w@mail.gmail.com> <68d90bd1-5990-6547-dc05-efd4f703b52c@gmail.com> <1726711339.4276068.1486461378855@mail.yahoo.com>
In-Reply-To: <1726711339.4276068.1486461378855@mail.yahoo.com>
Subject: RE: Exploring triggers
Date: Tue, 7 Feb 2017 15:00:57 -0500 (EST)
Message-ID: <0a2901d2817c$e5b6dca0$b12495e0$@rez1.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Thread-Index: e8GJwsemayaV6g6YngauFKvDSAFGuw==
Content-Language: en-us
Thread-Topic: Exploring triggers
Content-Transfer-Encoding: quoted-printable
archived-at: Tue, 07 Feb 2017 20:01:10 -0000

Do you have an example of a working trigger that actually alters things o=
n=20
the LDAP server? That's where I got hung up. I did much like you did, but=
=20
what I really wanted was to alter an entry when the trigger fired.

I didn't have any issues with the trigger subentries disappearing. Your=20
process reads a lot like mine. What version of Apache DS are you running?=
=20
Maybe there was a change between your version and mine?

-----Original Message-----
From: s_humbi [mailto:s_humbi@yahoo.com.INVALID]
Sent: Tuesday, February 07, 2017 4:56 AM
To: users@directory.apache.org
Subject: Re: Exploring triggers

I was playing around a little bit with triggers and stored procedures.

For me (as beginner) almost everything worked fine, except this big probl=
em=20
(don't know if it is a bug or if i did something wrong):
If you restart the server, the attribute triggerExecutionSubentry in the=20
subentry gets lost...
[10:52:14] WARN=20
[org.apache.directory.server.core.trigger.TriggerSpecCache] - Found=20
triggerExecutionSubentry 'cn=3Dtrigger,dc=3Dds,dc=3Dtest,dc=3Dnet' withou=
t any=20
prescriptiveTriggerSpecification


This is what i found out (without warranty, comments/imporovements welcom=
e).=20
Maybe it helps a little bit.

Approach:

1    Implementing Stored Procedure
2    Adding entry for Stored Procedure
3    Adding the trigger as Attritbute (trigger for one Entry only)
4    Or adding Triggers for more Entries, e.g. (Sub)-Tree
5    Activate and deactivate Triggers


More docs:
http://joacim.breiler.com/apacheds/ch09s02.html#Planned%20New%20Features%=
20for%20Triggers
http://people.apache.org/~ersiner/ldapcon.2007/LDAPcon.2007_LDAP.Stored.P=
rocedures.and.Triggers.in.ApacheDS_by.Ersin.Er_Paper.pdf


1    Implementing the Stored Procedure

Stored Prodedure are simple POJO with one or more public static methods=20
(later called by the trigger).

Example:

package com.test;

import java.util.ArrayList;
import org.apache.directory.api.ldap.model.entry.Entry;
import org.apache.directory.api.ldap.model.entry.Modification;

public class TestTriggerInterceptor {

    public static void helloTrigger(Entry oldEntry, ArrayList<Modificatio=
n>=20
mods ) {
        System.out.println("Entry found: " + oldEntry.getDn());

        for (Modification modification : mods) {
            System.out.println(modification.getOperation()
                       + " "
                       + modification.getAttribute());
        }
    }
}


2    Adding Stored Procedures

Adding a new ou for triggers, for example: ou=3DStored Procedures,ou=3Dsy=
stem

Adding a new entry (=3DStoredProcedure) for saving the StoredProcedure=20
(ObjectClass  javaStoredProcUnit)

Example:

DN: storedProcUnitName=3Dcom.test.TestTriggerInterceptor,ou=3DStored=20
Procedures,ou=3Dsystem

Definition LDAP Stored Procedure:

=E2=80=A2    ObjectClass: javaStoredProcUnit and storedProcUnit

=E2=80=A2    storedProcUnitName: complete classname, e.g.=20
com.test.TestTriggerInterceptor =E2=80=A2    storedProcLangId: always =E2=
=80=9CJava=E2=80=9D
=E2=80=A2    javaByteCode: Upload byte-code with ds-studio (the .class - =
File)


3    Adding the trigger as Attritbute  for one Entry only:

Adding the attribut entryTriggerSpecification in the entry.

The Value of the Attribute entryTriggerSpecification is the trigger,=20
example:
AFTER Modify CALL "com.test.TestTriggerInterceptor:helloTrigger" ($oldEnt=
ry,=20
$modification);

-->    helloTrigger is the public static Method, we implemented above

Possible Triggers:
=E2=80=A2    AFTER Modify CALL
=E2=80=A2    AFTER Add CALL =E2=80=A6
=E2=80=A2    AFTER Delete CALL =E2=80=A6
=E2=80=A2    AFTER ModifyDN CALL =E2=80=A6


Some possible parameters for the trigger:
(found in org.apache.directory.api.ldap.trigger.StoredProcedureParameter)=
:

Modify_OBJECT( "$object" )
Modify_MODIFICATION( "$modification" )
Modify_OLD_ENTRY( "$oldEntry" )
Modify_NEW_ENTRY( "$newEntry" )
Add_ENTRY( "$entry" )
Add_ATTRIBUTES( "$attributes" )
Delete_NAME( "$name" )
Delete_DELETED_ENTRY( "$deletedEntry" )
ModifyDN_ENTRY( "$entry" )
ModifyDN_NEW_RDN( "$newrdn" )
ModifyDN_DELETE_OLD_RDN( "$deleteoldrdn" ) ModifyDN_NEW_SUPERIOR(=20
"$newSuperior" ) ModifyDN_OLD_RDN( "$oldRDN" ) ModifyDN_OLD_SUPERIOR_DN(=20
"$oldRDN" ) ModifyDN_NEW_DN( "$oldRDN" )

Examples for static mehtods and trigger attribute entryTriggerSpecificati=
on:

Static method: public static void changeTrigger(Entry entry,=20
ArrayList<Modification> mods ) { =E2=80=A6 }
Trigger:       AFTER Modify CALL "com.test.TriggerInterceptor:changeTrigg=
er"=20
($oldEntry, $modification);

Static method: public static void addTrigger(Dn newEntryDn, Entry addEntr=
y )=20
{ =E2=80=A6 }
Trigger:       AFTER Add CALL "com.test.TriggerInterceptor:addTrigger"=20
($entry, $attributes );

Static method: public static void deleteTrigger(Entry deleteEntry) { =E2=80=
=A6 }
Trigger:       AFTER Delete CALL "=20
com.test.TriggerInterceptor:deleteTrigger" ($deletedEntry);


4    Adding  Triggers for more Entries, e.g. (Sub)-Tree
First: Adding an  Administrative Area for Triggers

--> adding new attribute  administrativeRole  with the Value
--> triggerExecutionSpecificArea (didn't tries
--> triggerExecutionInnerArea, don't what this is for)

Then:  adding a trigger-subentry (objectClass: triggerExecutionSubentry a=
nd=20
subentry)
Then:  adding a prescriptiveTriggerSpecification attribute to the subentr=
y.

The value for prescriptiveTriggerSpecification is again the trigger,  for=
=20
Example:
AFTER Modify CALL "com.test.TriggerInterceptor:changeTrigger" ($oldEntry,=
=20
$modification);

This approach does not work any more for me. When i restart my server, i =
can=20
see the following log-Entry, when the server restarts:
[10:52:14] WARN=20
[org.apache.directory.server.core.trigger.TriggerSpecCache] - Found=20
triggerExecutionSubentry 'cn=3Dtrigger,dc=3Dds,dc=3Dtest,dc=3Dnet' withou=
t any=20
prescriptiveTriggerSpecification

--> the subentry has definitely the attribute=20
prescriptiveTriggerSpecification, i don't know how to solve ...


5    Activate and deactivate Triggers

Setting the attribut ads-enabled to TRUE/FALSE:

DN:=20
ads-interceptorId=3DtriggerInterceptor,ou=3Dinterceptors,ads-directorySer=
viceId=3Ddefault,ou=3Dconfig

    Emmanuel L=C3=A9charny <elecharny@gmail.com> schrieb am 9:35 Freitag,=
=20
3.Februar 2017:


Le 03/02/2017 =C3=A0 09:14, Jim Willeke a =C3=A9crit :
> BTW: eDirectory has had LDAP Event Services which allows a client or a
> server process to register for events and take an action.
>
> https://www.novell.com/documentation/developer/ldapover/ldap_enu/data/
> ag7bleo.html

It's a slightly different system, AFAIU. events are sent to the client fo=
r=20
it to act. In ApacheDS, it's really a way to configure the server to do=20
something when a specific update occurs.

--=20

Emmanuel Lecharny

Symas.com
directory.apache.org