![]() |
Copyright © Cloud Software Group, Inc. All Rights Reserved |
For the Message Publication service to work, the PeopleCode provided with the installation needs to be copied in the SavePostChange event of the component from which the data has to be published out.
The name of the Message stored in the PeopleSoft database. It matches the Message Name and is automatically filled in by TIBCO Designer. Check this checkbox to publish the current record (for Effective Dated records only).Note: The adapter will consider a record as Effective Dated if the effective date field in that record starts with EFFDT. Available only for the JMS transport. It can be Uncompressed or Compressed. See Compressing JMS Messages for details. 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 Persistent or Non-Persistent. 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 or Reliable. 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.In the Schema tab you can view all elements.To view schema elements, click on the folders to expand them. It is not necessary to click the Apply button.
Note: The values are TIBCO field-types and not PeopleSoft field-types.
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 Persistent or Non-Persistent. See Delivery Mode for details. Available only for the HTTP transport. The port at which the adapter waits for HTTP messages. By default, the adapter listens at port 2002 for IB messages.
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 Message Publication 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 Message schema from PeopleSoft to TIBCO Designer.
![]() |
Copyright © Cloud Software Group, Inc. All Rights Reserved |