Copyright © TIBCO Software Inc. All Rights Reserved

Publication Service Fields

The following tabs are available:

•	Configuration Tab

•	Transport Tab

•	Schema View Tab

•	Schema Tab

The publication service supports the following LDAP operations:

INSERT, UPDATE, DELETE, and MODIFY DN. Changes made through the INSERT, UPDATE, DELETE, and MODIFY DN operations on the LDAP server are picked up by the adapter and published.

Configuration Tab

The Configuration tab contains the fields listed in Table 9, Field Description of Configuration Tab.

Table 9 Field Description of Configuration Tab  

Field	Description
Name	You can use the default name or replace it with a name of your choice. • A service name must use alphanumeric characters. An underscore (_) character can be used. The entire instance name must be less than 80 characters. The space character cannot be used in an instance name. • A service name cannot use global variables.
Description	Provide information about the service that you want stored in the project. The field is optional.
Transport Type	Select the transport to be used by the runtime adapter, JMS or TIBCO Rendezvous. After selecting the transport, the transport-specific configuration fields display. The transport can be configured to use a trusted store and identity resource for SSL (Secure Sockets Layer) configurations. TIBCO Rendezvous sessions and JMS topics have an SSL configuration field that provides a dialog for SSL configuration. To enable and configure SSL, in the Project panel, expand the Advanced folder, then expand the Sessions folder. Select the TIBCO Rendezvous session or JMS topic and check the Use SSL? checkbox. The SSL configuration options are explained in the online help associated with the session dialog. Click the question mark to display the online help.

Transport Tab

The Transport tab contains the fields listed in Table 10, Field Description of Transport Tab (Sheet 1 of 4):

Table 10 Field Description of Transport Tab

Field	Description
Message Subject	This field displays only if TIBCO Rendezvous is selected in the Transport Type drop-down list (under the Configuration tab). By default, a service uses a message subject that is generated using the Domain and Deployment global variables, the adapter acronym, the adapter instance name and the service name. If you use this default subject, make sure the values for Domain and Deployment are not empty. You can type a TIBCO Rendezvous subject name different from the default in this field. See TIBCO Rendezvous Concepts for information about specifying subject names.
Destination	This field displays only if JMS is selected in the Transport Type drop-down list (under the Configuration tab). By default, a service uses a dynamic destination that is generated using the Domain and Deployment global variables, the adapter acronym, the adapter instance name, and the service name. If you use this default dynamic destination, make sure the values for Domain and Deployment are not empty. You can override the default dynamic destination by specifying the static destination in this field. The static destination must be defined on the JMS server before it can be used by the runtime adapter. See TIBCO Enterprise Message Service User’s Guide for information about destinations.
Reply Message Subject	This field is not applicable to TIBCO ActiveMatrix Adapter for LDAP.
Reply Destination	This field is not applicable to TIBCO ActiveMatrix Adapter for LDAP.
Quality of Service	If TIBCO Rendezvous is selected as the transport type, select: • Certified Guarantees that every certified message reaches its intended recipient in the order sent. The message can be sent across network boundaries, and if a network fails, delivery attempts continue until delivery succeeds or until the message's time limit expires. This is often called certified message delivery. If certified message delivery is used, data is stored in a ledger file. The size of the ledger depends on several factors, the most important of which is the retention rate of stored data. That is, the ledger grows fastest in response to the cumulative length of undeliverable messages. You must ensure that sufficient disk space is available for the expected size of the ledger. • Reliable Ensures that each multicast or broadcast message is received as long as the physical network and packet recipients are working, and that the loss of a message is detected. This choice can compensate for brief network failures because it can retransmit a message on request if the first attempt failed. This choice is appropriate when message delivery is expected but some loss can be tolerated.
Wire Format	Services must use the same wire format to exchange data. • ActiveEnterprise Message (TIBCO Rendezvous only) Control information for validation is sent in the message. If no control information is included, an exception is returned to the subscriber. ActiveEnterprise standard wire format provides class information and packing rules for the TIBCO Adapter SDK set of data types. This format allows ActiveEnterprise components to perform extra validation on messages sent or received. See TIBCO Adapter SDK Programmer’s Guide for details about the control information generated and sent with ActiveEnterprise messages. • XML Message (TIBCO Rendezvous and JMS) The XML Message wire format conforms to specifically constructed and fully compliant XML Schema (XSD) based on the existing definition of the ActiveEnterprise schema.
Connection Factory Type	• Topic (JMS only) A message published to a topic is broadcast to one or more subscribers. All messages published to the topic are received by all services that have subscribed to the topic. This messaging model is known as publish-subscribe. • Queue (JMS only) A message sent to a queue is consumed by one and only one receiver. Each message has only one receiver though multiple receivers may connect to the queue. The first receiver to access the queue gets the message. The other receivers do not. This messaging model is known as point-to-point.
Delivery Mode	• Persistent (JMS only) In general, a message marked persistent will be available to a JMS client even if the JMS server goes down. • Non‑persistent (JMS only) A message marked non-persistent will not be available to a JMS client if the JMS server goes down. Messages sent with the persistent delivery mode are always written to persistent storage, except when they are published to a topic that has no durable subscribers. When a topic has no durable subscribers, there are no subscribers that need messages resent in the event of a server failure. Therefore, messages do not need to be saved, and performance is improved because disk I/O is not required.
Session Reference	Every adapter can have one or more sessions configured for it. Sessions encapsulate stateful connections to TIBCO Rendezvous and other messaging sources. The session object shown in this field is initially supplied by the adapter, depending on the Quality of Service selected. You can change the session by browsing for it in the project panel.
Endpoint Reference	You can drag a different endpoint, browse for another endpoint resource, go to the referenced endpoint to edit its properties or delete the endpoint. Endpoint reference objects are explained in TIBCO Designer Palette Reference.

The semantics for these fields are more complex than the explanation given here. See TIBCO Enterprise Message Service User’s Guide for more information.

Typically, a publication service will publish INSERT, UPDATE, DELETE, and MODIFY DN operations. For the publication service on the Active Directory server, a MODIFY DN operation on any monitored entry is published as UPDATE and not as MODIFY DN. The adapter supports persistent publisher services. Therefore, the adapter will be able to publish changes that occurred on the LDAP server even when the adapter was not running. However, if the adapter is not running when the changes take place on the LDAP server, only INSERT and UPDATE operations will be published. MODIFY DN operations will be published as UPDATE while DELETE operations (for Oracle Directory Server Enterprise Edition and eDirectory) will not be published at all. This is because the deleted entries no longer exist on the LDAP server and information on deleted entries is also no longer available.

Schema View Tab

The Schema View tab contains the fields listed in Table 11, Field Description of Schema View Tab (Sheet 1 of 3).

Table 11 Field Description of Schema View Tab

Field	Description
Base DN	Displays the selected Base DN (Distinguished Name) of a specified node. To display the Base DN, click the Browse DIT... button and then select the required node from the DIT. When the length of an object class name that is fetched from the Base DN field exceeds 128 characters, the ActiveEnterprise schema created with this name affects the runtime functionality. When you click the Apply button, a dialog box (Figure 12) is displayed that prompts you to enter a shorter name that can be stored in the schema. The name you enter must be unique and less than 128 characters. If the service has been configured with a long schema name, the dialog box will not display if a service has already been configured for the same object class.
Select Object Classes From	There are two methods you can use to select an object class: • Sample Entry — You can specify a sample entry so that the object class for that entry is populated in the Objectclasses field. • LDAP Schema — You can specify an object class by selecting it from the ldap schema on the LDAP server.
Sample Entry	This field is available only if you select the Sample Entry radio button for the Select Object Classes From field. In your LDAP server, you can specify an entry from the schema you will use for this service. The service will only handle entries with identical object classes. To specify a sample entry for the schema, click the Browse DIT... button and then select the required node from the DIT. This generates the class reference needed for the service, in the Objectclasses field.
LDAP Schema Classes	This field is available only if you select the LDAP Schema radio button for the Select Object Classes From field. To select the LDAP schema classes for the service, click the Browse Schema... button and select the object classes from the Available Objectclasses list. This generates the class reference needed for the service, in the Objectclasses field.
Maximum Number Of Entries	Click the Browse DIT... button for the Base DN or Sample Entry fields to access the Maximum Number of Entries field. This field is available in the Select Base DN and Select Sample Entry for Schema dialog boxes. Specify the maximum number of entries that you want to restrict the service to. The DIT expands only if the number of entries is equal to, or less than the value you specify. You cannot specify a value greater than 50000 as the maximum number of entries. If you need to select a node within a subtree that has more than 50000 entries, you must specify the DN, in the DN (Base DN/Sample Entry) box. You may come across the following exceptions : The size of the result exceeds server specific limit and The Number of Descendants for this Node are more than the requested number. Additionally, if you are using Oracle Directory Server Enterprise Edition, you may come across the exception: The administrative limit on the maximum number of entries to return was exceeded. To proceed, you will need to log on to the server and change the value for the search size limit: • For Oracle Directory Server Enterprise Edition, click the Configuration tab. Select Database Settings and click the LDBM Plugin Settings tab. Change the value of the Look-through Limit entry. While you are in the Configuration tab, select the root of the tree, and click the Performance tab. Change the value for the Size Limit entry too. For further details, see the documentation shipped with the server you are using.
Objectclasses	Displays the object class of the entry specified in the Base DN, or Sample Entry fields, if these have been specified. Otherwise, the value from the LDAP Schema Classes field is displayed. You cannot edit this field.
Handle Any Subset of Configured Object Classes	This field is available if a composite object class is displayed in the Objectclass field. Although the adapter is configured for a composite object class, all combinations of the object class are supported. Therefore, if you select the check box, changes made to any attribute of an entry belonging to any subset of the configured object class will be published by the service. This field is not visible when the adapter instance is configured for the Microsoft Active Directory server.
Filter	You can specify a filter option in this field. Only entries that conform to the specified filter and are available on the LDAP server at runtime will be published. Previous deleted entries will not be published, even if they conform to the specified filter. The adapter supports LDAP V3 filters. The conditions used to specify a filter should be syntactically accurate. If the filter specified has an incorrect syntax, the following message is displayed: Syntax of the filter is not valid. Please ensure that you enter a valid LDAP filter. If the filter syntax is correct but no entries match the filter specifications, the following warning is displayed: No results are found on the LDAP server with the given filter. Please ensure that filter is semantically correct. This means that at the time of configuration, no entries match the filter, but the entries may be present at runtime.

Figure 12 Lengthy Schema Name

Schema Tab

The Schema tab contains the fields listed in Table 12, Field Description of Schema Tab.

Table 12 Field Description of Schema Tab

Field	Description
Class Reference	Displays the reference to the ActiveEnterprise schema that corresponds to the object class that was configured under the Schema View tab.

Copyright © TIBCO Software Inc. All Rights Reserved