![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
For a newly created adapter project, create a PeopleSoft Adapter Configuration and configure it to perform tasks.
1. Click the newly created project, for example TIB_PS_Adapter, in the Project Explorer Panel, and then select File > New > Adapter Resources... from the Menu. The Create New Adapters Resource dialog appears, as shown in Figure 49.Figure 49 Create New Adapters Resource Dialog
2. Expand the Configurations folder and select PeopleSoft Adapter. Click the Next button to open the PeopleSoft Adapter Configuration dialog.
3. Enter or select the parent folder for the newly created configuration file and enter the configuration file name in the File name field. The default configuration file name is PeopleSoftAdapterConfiguration.adpsft8model.
4. Click the Finish button to close the dialog.
5. Double-click the configuration file under the adapter project folder in the Project Explorer Panel. The Editor Panel appears on the right with the configuration tabs.The Configuration tab provides options to modify basic configuration information, as shown in Figure 50.Figure 50 Configuration Tab
Table 7 Configuration Parameters See Guidelines for Choosing an Instance Name for more information. Reconnection Attempts The total number of reconnection attempts to make before the runtime adapter or adapter service is stopped. The default value of -1 means reconnection attempts will continue indefinitely. Connection Configuration PeopleSoft Connection Shared Resource for how to define a connection configuration. The options for a connection configuration are listed in Table 6.
• An instance 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.
• An instance name must be unique with respect to other adapter instances for the same adapter in the project. The same instance name can be used to name an adapter instance for a different adapter in the same project. For example, a PeopleSoft adapter instance named TEST and a Siebel adapter instance named TEST can coexist in the same project.
• Each instance name must be unique per adapter within a project even if each instance is defined in a different folder. That is, configuring same-named adapter instances in different folders will not make their names unique.When you create an Adapter Service Engine instance, several resources are automatically created for it. The names of these resources derive from the name of the instance they belong to. Changing the adapter instance name results in an automatic regeneration of the resources names. If you manually modify any resource name, that particular name will not be automatically regenerated next time you rename the adapter instance.The Adapter Options tab provides options to modify base configuration information and monitoring information, as shown in Figure 51.Figure 51 Adapter Options Tab
Table 8 Adapter Options Parameters Language Encoding This is how often an adapter with a publication service checks the publishing table (TIB_CI_MQUEUE) for new rows.The default setting is 5000, or once every five seconds. Number of Threads Enable Standard MicroAgent Standard MicroAgent Name The name for the standard microagent that will be registered with the TIBCO Hawk system. In most cases the default value is used. Standard MicroAgent Timeout (ms) Enable Class MicroAgent Check this checkbox to enable instance or class specific standard TIBCO Hawk Microagent. Class MicroAgent Name The name for the class microagent that will be registered with the TIBCO Hawk system. In most cases the default value is used. Class MicroAgent Timeout (ms) Default MicroAgent Session (Read only) The value of this field is set to HawkSession.The Adapter Service tab provides options for adding and configuring the following adapter services, as shown in Figure 52.Figure 52 Adapter Services Tab
1. Click the Add Service Name button to add a desired service into the All PeopleSoft Adapter Services pane. The parameter configuration panes appear in the 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. A service name cannot use substitution variables. The AESchema that is automatically generated from the selected PeopleSoft Business Object when the adapter configuration is saved. Class Reference From BO Convert PeopleSoft Business Objects into AESchemas. Click Browse in the drop-down list to select a business object child from any of the previously imported BOs.Refer to Converting Business Objects into AESchemas for details. Publish Current Record Note: The Adapter Service Engine will consider a record as Effective Dated if the effective date field in that record starts with EFFDT. 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.
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. A service name cannot use substitution variables. The AESchema that is automatically generated from the selected PeopleSoft Business Object when the adapter configuration is saved. Class Reference From BO Convert PeopleSoft Business Objects into AESchemas. Click Browse in the drop-down list to select a business object child from any of the previously imported BOs.Refer to Converting Business Objects into AESchemas for details. This column shows a field name if the schema attribute is a field, or shows a record name if the schema attribute is a record.Expand folders in this column to display the PROPERTIES fields. When the Adapter Service Engine publishes data, the governing schema puts data only in the PROPERTIES node.
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. A service name cannot use substitution variables. The AESchema that is automatically generated from the selected PeopleSoft Business Object when the adapter configuration is saved. Class Reference From BO Convert PeopleSoft Business Objects into AESchemas. Click Browse in the drop-down list to select a business object child from any of the previously imported BOs.Refer to Converting Business Objects into AESchemas for details. This column shows a field name if the schema attribute is a field, or shows a record name if the schema attribute is a record.Expand folders in this column to display the PROPERTIES fields. When the Adapter Service Engine publishes data, the governing schema puts data only in the PROPERTIES node.
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. A service name cannot use substitution variables. The AESchema that is automatically generated from the selected PeopleSoft Business Object when the adapter configuration is saved. Convert PeopleSoft Business Objects into AESchemas. Click Browse in the drop-down list to select a business object child from any of the previously imported BOs.Refer to Converting Business Objects into AESchemas for details. Enter the subject on which the Adapter Service Engine should subscribe for messages from PeopleSoft. The Subscriber Subject should be the same as the one mentioned in Defining Nodes. Connection Factory Type The Connection Factory Type mentioned here should be the same as that mentioned in the Node definition in PeopleSoft. Refer to Defining Nodes.
• QUEUE: A message sent to a queue is consumed by one and only one receiver. Each message has only one receiver though multiple receivers may connect to the queue. The first receiver to access the queue gets the message. The other receivers do not. This messaging model is known as point-to-point.
• TOPIC: A message published to a topic is broadcast to one or more subscribers. All messages published to the topic are received by all services that have subscribed to the topic. This messaging model is known as publish-subscribe.
• PERSISTENT: In general, a message marked persistent will be available to a JMS client even if the JMS server goes down.
• NON_PERSISTENT: A message marked non-persistent will not be available to a JMS client if the JMS server goes down. The port at which the Adapter Service Engine waits for HTTP messages. By default, the adapter listens at port 2002 for IB messages. This column shows a field name if the schema attribute is a field, or shows a record name if the schema attribute is a record.Expand folders in this column to display the PROPERTIES fields. When the Adapter Service Engine publishes data, the governing schema puts data only in the PROPERTIES node. This column applies only if a field is shown. The values are TIBCO field types and not PeopleSoft field types.
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. A service name cannot use substitution variables. The AESchema that is automatically generated from the selected PeopleSoft Business Object when the adapter configuration is saved. Convert PeopleSoft Business Objects into AESchemas. Click Browse in the drop-down list to select a business object child from any of the previously imported BOs.Refer to Converting Business Objects into AESchemas for details. Enter the subject on which the Adapter Service Engine should subscribe for messages from PeopleSoft. The Subscriber Subject should be the same as the one mentioned in Defining Nodes. Connection Factory Type The Connection Factory Type mentioned here should be the same as that mentioned in the Node definition in PeopleSoft. Refer to Defining Nodes.
• QUEUE: A message sent to a queue is consumed by one and only one receiver. Each message has only one receiver though multiple receivers may connect to the queue. The first receiver to access the queue gets the message. The other receivers do not. This messaging model is known as point-to-point.
• TOPIC: A message published to a topic is broadcast to one or more subscribers. All messages published to the topic are received by all services that have subscribed to the topic. This messaging model is known as publish-subscribe.
• PERSISTENT: In general, a message marked persistent will be available to a JMS client even if the JMS server goes down.
• NON_PERSISTENT: A message marked non-persistent will not be available to a JMS client if the JMS server goes down. The name of the Requesting Node. The Requesting Node mentioned in the Node definition in PeopleSoft should be the same as the one mentioned here. Refer to Defining Nodes. The Node Password. It is the same as the Password specified in the Node definition in PeopleSoft. Refer to Defining Nodes. The name of the Requesting Node. The Requesting Node mentioned in the Node definition in PeopleSoft should be the same as the one mentioned here. Refer to Defining Nodes. The Node Password. It is the same as the Password specified in the Node definition in PeopleSoft. Refer to Defining Nodes. The HTTP Listening Connector accepts compressed and based64-encoded data. All subscribed messages are written to this URL. By default, the adapter listens to IB Messages on port 2002. This column shows a field name if the schema attribute is a field, or shows a record name if the schema attribute is a record.Expand folders in this column to display the PROPERTIES fields. When the Adapter Service Engine publishes data, the governing schema puts data only in the PROPERTIES node. This column applies only if a field is shown. The values are TIBCO field types and not PeopleSoft field types.
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. A service name cannot use substitution variables. The AESchema that is automatically generated from the selected PeopleSoft Business Object when the adapter configuration is saved. Convert PeopleSoft Business Objects into AESchemas. Click Browse in the drop-down list to select a business object child from any of the previously imported BOs.Refer to Converting Business Objects into AESchemas for details. Enter the subject on which the Adapter Service Engine should subscribe for messages from PeopleSoft. The Subscriber Subject should be the same as the one mentioned in Defining Nodes. Connection Factory Type The Connection Factory Type mentioned here should be the same as that mentioned in the Node definition in PeopleSoft. Refer to Defining Nodes.
• QUEUE: A message sent to a queue is consumed by one and only one receiver. Each message has only one receiver though multiple receivers may connect to the queue. The first receiver to access the queue gets the message. The other receivers do not. This messaging model is known as point-to-point.
• TOPIC: A message published to a topic is broadcast to one or more subscribers. All messages published to the topic are received by all services that have subscribed to the topic. This messaging model is known as publish-subscribe.
• PERSISTENT: In general, a message marked persistent will be available to a JMS client even if the JMS server goes down.
• NON_PERSISTENT: A message marked non-persistent will not be available to a JMS client if the JMS server goes down. The port at which the Adapter Service Engine waits for HTTP messages. By default, the adapter listens at port 2002 for IB messages. This column shows a field name if the schema attribute is a field, or shows a record name if the schema attribute is a record.Expand folders in this column to display the PROPERTIES fields. When the Adapter Service Engine publishes data, the governing schema puts data only in the PROPERTIES node. This column applies only if a field is shown. The values are TIBCO field types and not PeopleSoft field types. The Log Sinks tab specify the output destination (sinks) for the trace messages and set the tracing level for the roles selected, as shown in Figure 53.Figure 53 Log Sinks Tab
1. Click the Add Sink Type button to add a desired sink into the All Log Sinks pane. The parameter configuration panes appear in the tab.
Table 15 Log Sink Configuration Parameters Trace messages from the selected level(s) will be collected in the configured log sinks. You can configure what levels of trace messages you want logged. Log Info Messages Log Debug Messages This trace level is reserved and should not be enabled unless requested by the TIBCO Support. This trace level writes a lot of information to the log file and significantly reduces the speed of the Adapter Service Engine. Log Warning Messages Log Error Messages If checked, traces are added to the existing file at startup. If unchecked, the existing file is overwritten at startup if one of the same name exists. Only true and false are legal values. The Hawk sink uses the Hawk session, created and used by the Adapter Service Engine for monitoring purposes, to send tracing messages to the TIBCO Hawk monitor or Display. Click Browse from the drop-down list to select one of the previously defined sessions.
2. Click the Remove Sink button to remove the sink.
2. Click the Add Log Sink Role button to add additional roles. You can add debug, error, warning, or informational roles to sinks by selecting the corresponding roles from the Role drop-down list.
2. Click the Remove Log Sink Role button to remove the role.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |