Copyright © TIBCO Software Inc. All Rights Reserved

Publishing Messages

This section explains the following:

•	Configuring Timers for Publication Services

•	Publishing Messages in Sequence

•	Publishing Duplicate Events

•	Publishing Deleted Entries with the Same Names and Values as the Search Filter

•	Publishing Deleted Entries in Microsoft Active Directory and Microsoft Active Directory Application Mode

•	Publishing Deleted Entries in Oracle Internet Directory and OpenLDAP Server

•	Publishing Messages When Adapter is Not Running

Configuring Timers for Publication Services

You can configure the polling interval for the publication service. To do so, in TIBCO Designer, navigate to the adapter_instance_name > Advanced > Timers folder, and select the timer that was created when you added a publication service. On the Configuration tab, specify the polling interval in the Interval (milliseconds) text box. This will determine the interval at which the service will poll the LDAP server. For more details on configuring timers, see TIBCO Designer Palette Reference.

Publishing Messages in Sequence

You can use the adapter’s publication service to publish messages in sequence.

The publication service of the adapter can behave in one of the following ways:

•	If the adapter is running, all changes that are being made will be published in sequence.

•	If the adapter is not running and if a number of changes have been made on a particular entry, when the adapter is started, the publication service will publish only the most recent change.

Publishing Duplicate Events

During publishing of messages, the server first returns the entries that match the search criteria of the adapter. However, unlike in an ordinary search, the server keeps the search active until you disconnect from the server. If an entry is changed and the changed data matches the search criteria, the server will publish the modified entry. Therefore, if an entry is changed twice, and both changes match the search criteria when the adapter is running, the LDAP server will publish both changes.

For entries that are changed when the adapter is not running, the adapter does not fetch all the changes that were made. It only retrieves messages that match the search criteria that were modified after the adapter stopped, that is, after the timestamp of the last modification that was received by the adapter when it was running.

Therefore, the adapter cannot publish duplicate changes, if the changes were made when the adapter was not running.

Publishing Deleted Entries with the Same Names and Values as the Search Filter

If entries deleted have the same names and values as the search filter defined in the Filter field in the Schema View, the publication service will not publish these entries. This is because LDAP servers do not record the deleted attributes.

Publishing Deleted Entries in Microsoft Active Directory and Microsoft Active Directory Application Mode

An entry deleted from a Microsoft Active Directory and Microsoft Active Directory Application Mode server is published only with its leaf node and base DN. All the non-leaf nodes, except the base DN, will not be published. For example, after deleting an entry with "cn=Anne Smith, ou=Server Development, dc=TIBCO, dc=com" as its full DN, the publication service will publish only "cn=Anne Smith, dc=TIBCO, dc=com" for the deleted entry. This is because the adapter retrieves the deleted entry’s information from Microsoft Active Directory’s deleted objects container, which only records the leaf node and base DN of the deleted entry, without all the other non-leaf nodes.

Publishing Deleted Entries in Oracle Internet Directory and OpenLDAP Server

Entries deleted from an Oracle Internet Directory or OpenLDAP are all published, regardless of whether or not they are of the Objectclasses configured in the Schema View tab. This is because Oracle Internet Directory and OpenLDAP do not return the deleted schema at the end of a DELETE operation. Thus, the publication service will publish all DELETE messages ignoring the Objectclasses selected in the Schema View tab of the publication service.

Publishing Messages When Adapter is Not Running

The adapter supports persistent publication of the changes on an LDAP server if the adapter was not running when the changes took place on the LDAP server. This mechanism provides a maximum level of redundancy and a once-and-only-once guarantee of message delivery, irrespective of the adapter connection failure.

This functionality is available for Microsoft Active Directory, Microsoft Active Directory Application Mode, and Oracle Internet Directory. Microsoft Active Directory and Microsoft Active Directory Application Mode has a limitation of keeping track of the ADD operation on an entry which is later deleted. If an entry is added and deleted when the adapter is not running, the publication service will publish only the DELETE operation after the adapter restores its connection with the LDAP server.

Copyright © TIBCO Software Inc. All Rights Reserved