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 named in. 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.
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.
|
|
|
|
|
|
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.
|
|
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.
|
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.
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.
The Schema tab is read only. Click the Go to referenced resources.. icon to view the schema in the
AESchemas folder.
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.
|
|
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.
See TIBCO Enterprise Message Service User’s Guide for information about destinations.
|
|
|
|
|
|
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.
|
|
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.
|