Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 4 Adapter Service Options : Request-Response Invocation Service Tabs

Request-Response Invocation Service Tabs
This service is also called RPC (Remote Procedural Call) Client. The adapter receives a request from the Tuxedo application and sends the request through the TIBCO environment. When a response is returned from the TIBCO environment, the adapter sends the response back to the Tuxedo application.
You can configure parameters in the following tabs:
Configuration Tab
You can specify a name and select the transport type for a request-response 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.
RPC Client 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 named in. See Appendix C, Message Formats for more information.
a class named service name Reply is created under Schemas/classes/ Tuxedo/adapter instance name/service name. The class has a String data type attribute named out, which is provided by the Subscription, Request-Response or Request-Response Invocation services.
A class named service name Request is created with a binary data type attribute named in. This attribute has an extended property named length. Refer to Appendix C, Message Formats for more information.
A class named service name Reply is created with a binary data type attribute named out, which is provided by the Subscription, Request-Response and Request-Response Invocation services (in addition to the default field ErrorCode which appears for Subscription and Request-Response). This attribute has an extended property named length with a value of 10.
load balancing will be used. Multiple request-response invocation services will run in RVCMQ mode to process messages passed by the Rendezvous Adapter Agent.
After selecting Distributed Queue, a session called DefaultRVCMQSession is created. You may need to modify the parameters of this default session if needed.
An Endpoint called ClientAgentRvCmqSubscriber is automatically created upon the creation of the DefaultRVCMQSession session for this request-response invocation service. You can configure the subject name for this communication by clicking the ClientAgentRvCmqSubscriber Endpiont under Advanced > Session > DefaultRVCMQSession in the Project panel. Do not manually modify any other attributes 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 if you select FML32 in the Buffer Type drop-down list in the RPC Client Options Tab. 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 the request-response invocation service.
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.
Reply Header Reference
Browse and select the header file containing information about the fields to be included in the reply schema. The schema is created based on the FML32 header files that you have selected and is used for the request-response service.
The schema fields are created with names suffixed with _field ID. Irrespective of the type of the FML32 fields, the schema that is created is always of the string type. The classes that are created are stored in the tibco/public/class/ae/Tuxedo directory.
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 Request Schema View Tab and Reply Schema View Tab remain unchanged.
Request Schema View Tab
This tab is available only after you select FML32 in the Buffer Type drop-down list in the RPC Client Options Tab, specify the request and reply header references 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.
Reply Schema View Tab
This tab is available only after you select FML32 in the Buffer Type drop-down list in the RPC Client Options Tab, specify the request and reply header references in the Fetch Schema Tab, and click Apply.
This tab is similar to the Request Schema View Tab. You can set the sequence name for the fields that may occur more than once in a reply schema.
Schema Tab
The Schema tab is read only. The Request Schema Reference and Reply Schema Reference fields are updated automatically.
This is a reference to the request-response invocation service request schema that can be found in the AESchemas folder. Click to view the schema resource in the AESchemas folder.
Reply Schema Reference
This is a reference to the request-response invocation service reply schema that can be found in the AESchemas folder. Click the to view the schema resource in the AESchemas folder.
Note that the RPC class and the RPCClient_Closure class are automatically created when a request-response invocation service is created. Do not manually edit the classes.
Transport Tab
Message Transport options can be set for a request-response invocation service depending on the transport type selected in the Configuration Tab.
Click Apply to apply the changes before leaving this 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 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 Browse 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.
The adapter agent internally uses TIBCO Rendezvous with Reliable Quality of Service to communicate with the adapter in the Adapter Agent. An Endpoint called ClientAgentSubscriber is automatically created upon the creation of a request-response invocation service. You can specify the subject name for the communication. No other attributes of this Endpoint should be manually edited.
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.
The adapter agent internally uses TIBCO Rendezvous with Reliable Quality of Service to communicate with the adapter in the Adapter Agent. An Endpoint called ClientAgentSubscriber is automatically created upon the creation of a request-response invocation service. You can specify the subject name for the communication. No other attributes of this Endpoint should be manually edited.

Copyright © TIBCO Software Inc. All Rights Reserved