![]() |
Copyright © Cloud Software Group, Inc. All Rights Reserved |
The name of the Component Interface stored in the PeopleSoft database. It matches the Component Interface Name and is automatically filled in by TIBCO Designer. For example, entering p would narrow the drop-down list to only Component Interface names beginning with p. Available only for the JMS transport. It can be Topic or Queue. See Connection Factory Type for details. Available only for the JMS transport. It can be Durable or Non Durable. See Delivery Mode for details. Services must use the same wire format to exchange data. It is XML Message. See Wire Format for details. Available only for the Rendezvous transport. It can be Certified, Reliable or Distributed Queue. See Quality of Service for details. Services must use the same wire format to exchange data. It can be XML Message or ActiveEnterprise Message. See Wire Format for details.If you have changed any configuration, either on the service level or on the instance level, click the Get Schema button to ensure that the modification is reflected in the service at runtime.To change the Direction, follow these steps:
1. Expand the required folder until the Direction column is populated.
3. Click the Apply button.
Note: The values are TIBCO field-types and not PeopleSoft field-types. The valid values for Direction are:
• In — This field is read from the incoming request but not set in the outgoing reply. Indicates the PROPERTIES field is used as an input field.
• Out — This field is not read from the incoming request but set in the outgoing reply. Indicates the PROPERTIES field is used as an output field.
• InOut — This field is read from the incoming request and set in the outgoing reply. Indicates the PROPERTIES field is used in both directions. When a field direction is INOUT, the field value is used in the request sent to PeopleSoft as well as retrieved from PeopleSoft and sent back to the request as part of the reply. Note: The values are TIBCO field-types and not PeopleSoft field-types. Note: The key fields are always included in the runtime input.The input data received by the Request-Response Service contains a field called operation code (OPRN_CODE) if the Component Interface associated with the service contains records that are level 1 and above. The value in the operation code field determines the mode of update carried out on child records in the target PeopleSoft database. The values that can be specified in the input data for OPRN_CODE are:
• I — If the incoming row(s) is present insert it.
• U — If the incoming row(s) is present update it.
• R — Replace existing row(s) with the incoming row(s).
• D — If the incoming row(s) is present delete it.
• Null — If no operation code is specified an update is carried out.See Implementation of Keys in the TIBCO Adapter for PeopleSoft for more information on the operation codes.
Available only for the JMS transport.By default, a dynamic destination 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, ensure that 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 EMS server before it can be used by the runtime adapter. See the TIBCO Enterprise Message Service User’s Guide for information about destinations. Available only for the Rendezvous transport.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.
1. In the Project Panel, expand the adapter instance folder (by default, PeopleSoftAdapterConfiguration).
2. Click Adapter Services in the project panel.
3. Drag a Request-Response Service icon to the Design Panel.
4.
5. Click the Apply button. This generates a unique endpoint with a TIBCO Rendezvous subject name. The adapter automatically enters this information in the Advanced tab.
Rendezvous is selected as the default Transport Type. If you select JMS as the Transport Type, a unique endpoint with the destination name will be generated.
6. Click the Get Schema button. This downloads the Component Interface schema from PeopleSoft to TIBCO Designer.
7. Click the Apply button.
![]() |
Copyright © Cloud Software Group, Inc. All Rights Reserved |