Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Chapter 5 Configuring Adapter Services : CI Publication Service

CI Publication Service
When running as a CI Publication Service, the adapter uses PeopleCode embedded in a TIBCO page to persist data entered by PeopleSoft users into a queue table. The runtime CI Publication Service polls that queue table. If an unprocessed event is found, it sends the message out to the TIBCO environment and stamps the queue entry as processed.
For a CI Publication Service to work, a shadow page (formerly “panel”) named TIB_CI_ADAPTER_WRK must be embedded in any component that will be published. For instructions on how to do this, see CI Publication Service.
Configuration Options
Configure a CI Publication Service under the following tabs in the Configuration Panel.
Configuration Tab
The Configuration tab contains the following fields:
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.
TIBCO Designer automatically supplies this name when you click the Fetch Interface… button and select a Component Interface. When starting the adapter, it uses this name to find the Component Interface in PeopleSoft. You can enter a partial string in this field to filter the Component Interfaces that are presented in the drop-down list when you click the Fetch Interface… button.
For example, entering p would narrow the drop-down list to only Component Interface names beginning with p.
Note: After saving the configuration settings to the PeopleSoft database if you modify the Publish on settings, you must once again click the Apply button, and then click the Get Schema button, and finally click the Save To PeopleSoft button.
Add mode allows the input of new records, for example a new PRODUCT.
Update mode is used to view current data and modify future data.
Update all is used to view history, current and future data but only modify future data.
Correction is used to view history, current and future data, and correct all records.
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 Persistent or Non-Persistent. See Delivery Mode for details.
Available only for the Rendezvous transport. It can be Certified or Reliable. Reform to 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.
Save To PeopleSoft
Click the Save To PeopleSoft button to save the configuration to the PeopleSoft application server.
Get Schema
Click the Get Schema button to list the fields of the fetched schema in the Schema Tab.
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.
Schema Tab
In the Schema tab you can view all elements but change only the trigger and runtime input settings, as shown in Figure 26.
Figure 26 CI Publication Service - Schema Tab
To view schema elements, click on the folders to expand them. It is not necessary to click the Apply button.
To change the trigger setting, follow these steps:
1.
Expand the PROPERTIES folder until the Trigger column is populated.
2.
Check or uncheck the Trigger checkbox required. If checked, an update to this field will trigger a publish.
3.
Check or uncheck the Runtime Input checkbox. If checked, this field will be included in the runtime input.
4.
Click the Apply button, and then click the Save To PeopleSoft button in the Configuration tab.
The Schema tab contains the following fields:
Note: The values are TIBCO field-types and not PeopleSoft field-types.
Note: The values are TIBCO field-types and not PeopleSoft field-types.
Note: The key fields are always included in the runtime input.
Advanced Tab
The Advanced tab contains the following fields:
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.
Configuration Task Sequence
To configure a CI Publication Service, follow these steps:
1.
2.
Click Adapter Services in the project panel.
3.
Drag a CI Publication Service icon to the Design Panel.
4.
Specify options in the Configuration tab. See Configuration Options for more information.
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.
Enter the name for the Component Interface and click the fetch interface button to fetch the component interface.
7.
Click the Get Schema button. This downloads the Component Interface schema from PeopleSoft to TIBCO Designer.
8.
Click the Save to PeopleSoft button. This will save the details required in the PeopleSoft database to trigger the Publication Service.
9.
 
TIBCO_HOME\adapter\adpsft8\version_number\scripts
Locate the SQL script in the scripts directory and run it to delete the entry in the PeopleSoft database. The name of the script file is Component Interface Name_Adapter Configuration Name.sql. For example, if an adapter configuration called pub, created for the Component Interface ACTIVITY, is deleted, the .sql file generated will be named ACTIVITY_pub.sql.
 

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved