Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 4 Adapter Service Options : Publication Service Tabs

Publication Service Tabs
The publication service sends messages from a Tuxedo application to the applications configured for the TIBCO environment.
You can configure the parameters for the Publication service using the following tabs:
Configuration Tab
You can specify a name and select the transport type for a publication service in this tab. Click Apply to apply the changes before leaving this tab.
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.
The transport can be configured to use a trusted store and identity resource for use in SSL (Secure Sockets Layer) configurations. TIBCO Rendezvous sessions and JMS topics have an SSL configuration field which uses a dialog to perform 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 click Use SSL?. The SSL configuration options are explained in the online help associated with the session dialog. Click the question mark to display the online help.
Publisher Options Tab
After you are done with the configuration, click Apply to apply the changes before leaving this tab.
A class named service name Request is created under Schemas/classes/Tuxedo/adapter instance name/service name. The class has a String data type attribute namedin. See Appendix C, Message Formats for more information.
A class named service name Request is created with a binary data type attribute named in.
This field appears only if you select FML32 in the Buffer Type drop-down list. It is the target name of the Tuxedo event for which the adapter is listening, in order to trigger a publish.
This field is mandatory for the Event-based publication service. It is not required for Rendezvous Adapter Agent-based publication or JMS Adapter Agent-based publication services.
For an Event-based publisher, the EVENT_NAME field is a reserved FML32 field for the name of the event that is being posted on the Event Broker, set by the Tuxedo service or client.
It is the name of a queue space. The Oracle Tuxedo administrator creates the queue space, which contains a collection of queues. Each queue space is a resource manager(RM) instance.
Distributed Queue indicates that load balancing will be used for Rendezvous Adapter Agent-based publication services. Multiple publication services will run in the RVCMQ mode to process messages passed by the Rendezvous Adapter Agent.
After selecting Distributed Queue, a DefaultRVCMQSession session is created in the Project. You can modify the parameters of this default session if needed.
A PubAgentRvCmqSubscriber endpoint is automatically created upon the creation of the DefaultRVCMQSession session for the publication service. You can configure the subject name for this communication by clicking the PubAgentRvCmqSubscriber endpiont under Advanced > Session > DefaultRVCMQSession in the Project panel. Do not manually modify any other attribute of this Endpoint.
See TIBCO Rendezvous Concepts for details about RVCMQ.
Load Field Id Dynamically
This checkbox appears only if you select FML32 in the Buffer Type drop-down list. It specifies whether the Field IDs for the FML32 fields should be loaded dynamically at runtime. If unchecked, the Field ID values loaded from the header files are used.
Fetch Schema Tab
The Fetch Schema tab is available only after you select FML32 in the Buffer Type drop-down list in the Publisher Options tab and click Apply.
Click Apply to apply the changes before leaving this tab.
Browse and select the header file containing information about the fields to be included in the schema. The schema is created based on the FML32 header files that you have selected and is used for publishing.
If you made any changes to the header files, click the Refresh button to load the new schema. The sequence names that you have specified in the Publisher Schema View Tab remain unchanged.
The schema fields are created with names suffixed with _field ID. Irrespective of the type of the FML32 fields, the schema is always the string type. The classes that are created are stored in the tibco/public/class/ae/Tuxedo directory.
Publisher Schema View Tab
The Publisher Schema View tab is available only after you select FML32 in the Buffer Type drop-down list in the Publisher Options Tab, specify the request header reference in the Fetch Schema Tab, and click Apply.
You can configure the schema for the fields that occur multiple times. Different adapter service uses different schema.The schema is dependent on the Tuxedo communication paradigm(s) that are used
Click Apply to apply the changes before leaving this tab.
Enter the sequence name. This name groups fields that occur the same number of times. The sequence names can use ASCII alphanumeric characters. Additionally, the _, , %, @, ‘ ‘, |, /, ~, {’, ‘}, #, -, $ non-alphanumeric characters are the acceptable.
Schema Tab
The Schema tab is read only. Click the Go to referenced resources.. icon to view the schema in the AESchemas folder.
 
Transport Tab
Message Transport options can be set for a publication service depending on the transport type selected in the Configuration Tab.
Click Apply to apply the changes before leaving this tab.
Publisher subject. 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 that is different from the default in this field.
See TIBCO Rendezvous Concepts for information about specifying subject names.
When you create a service, TIBCO Designer creates a corresponding session resource in the Advanced > Sessions folder. The session resource displays in this field. If you have explicitly created a custom session of the same type, you can click the Browse icon to replace the autocreated session. Changing the session for a service is not recommended.
Endpoint Reference
It is an endpoint reference for the service. You do not need to edit this field. The endpoint points to the corresponding endpoint resource in the Advanced > Sessions folder. The endpoint resource is automatically created by TIBCO Designer.
Note that the adapter agent internally uses TIBCO Rendezvous with the Reliable quality of service to communicate with the adapter in the Adapter Agent. An Endpoint called PubAgentSubscriber is automatically created upon the creation of a Publication service. The subject name for this communication is configurable. No other attribute of this Endpoint should be manually edited.
The publisher destination. A service uses a default destination generated using the Domain and Deployment global variables, the adapter acronym, the adapter instance name and the service name. If you use this default destination, make sure the values for Domain and Deployment are not empty.
Alternatively, you can manually enter a destination in this field. The destination does not have to be predefined in the TIBCO Enterprise Message Service server. The destination can be static or dynamic.
See TIBCO Enterprise Message Service User’s Guide for information about destinations.
Connection Factory Type
See Connection Factory Type for a description of connection factory type.
When you create a service, TIBCO Designer creates a corresponding session resource in the Advanced > Sessions folder. The session resource displays in this field. If you have explicitly created a custom session of the same type, you can click the Browse icon to replace the autocreated session. Changing the session for a service is not recommended.
Endpoint Reference
It is an endpoint reference for the service. You do not need to edit this field. The endpoint points to the corresponding endpoint resource in the Advanced > Sessions folder. The endpoint resource is automatically created by TIBCO Designer.
Note that the adapter agent internally uses TIBCO Rendezvous with the Reliable quality of service to communicate with the adapter in the Adapter Agent. An Endpoint called PubAgentSubscriber is automatically created upon the creation of a Publication service. The subject name for this communication is configurable. No other attribute of this Endpoint should be manually edited.

Copyright © TIBCO Software Inc. All Rights Reserved