Adapter for PeopleSoft (Version 7.x) User Guide

Specifying supported business object definitions

Use the Supported Business Objects tab in Connector Configurator to specify the business objects that the connector will use. You must specify both generic business objects and application-specific business objects, and you must specify associations for the maps between the business objects.

For you to specify a supported business object, the business objects and their maps must exist in the system.

Note:
Some connectors require that certain business objects be specified as supported in order to perform event notification or additional configuration (using meta-objects) with their applications. For more information, see the Connector Development Guide for C++ or the Connector Development Guide for Java.

If ICS is your broker

To specify that a business object definition is supported by the connector, or to change the support settings for an existing business object definition, click the Supported Business Objects tab and use the following fields.

Business object name

To designate that a business object definition is supported by the connector, with System Manager running:

  1. Click an empty field in the Business Object Name list. A drop-down list displays, showing all the business object definitions that exist in the System Manager project.
  2. Click on a business object to add it.
  3. Set the Agent Support (described below) for the business object.
  4. In the File menu of the Connector Configurator window, click Save to Project. The revised connector definition, including designated support for the added business object definition, is saved to the project in System Manager.

To delete a business object from the supported list:

  1. To select a business object field, click the number to the left of the business object.
  2. From the Edit menu of the Connector Configurator window, click Delete Row. The business object is removed from the list display.
  3. From the File menu, click Save to Project.

Deleting a business object from the supported list changes the connector definition and makes the deleted business object unavailable for use in this implementation of this connector. It does not affect the connector code, nor does it remove the business object definition itself from System Manager.

Agent support

If a business object has Agent Support, the system will attempt to use that business object for delivering data to an application via the connector agent.

Typically, application-specific business objects for a connector are supported by that connector's agent, but generic business objects are not.

To indicate that the business object is supported by the connector agent, check the Agent Support box. The Connector Configurator window does not validate your Agent Support selections.

Maximum transaction level

The maximum transaction level for a connector is the highest transaction level that the connector supports.

For most connectors, Best Effort is the only possible choice, because most application APIs do not support the Stringent level.

You must restart the server for changes in transaction level to take effect.

If WMQI is your broker

The MQ message set files (*.set files) contain message set IDs that Connector Configurator requires for designating the connector's supported business objects. See Implementing Adapters with WebSphere MQ Integrator Broker for information about creating the MQ message set files.

Each time that you add business object definitions to the system, you must use Connector Configurator to designate those business objects as supported by the connector.

Important:
If the connector requires meta-objects, you must create message set files for each of them and load them into Connector Configurator, in the same manner as for business objects.

To specify supported business objects:

  1. Select the Supported Business Objects tab and click Load. The Open Message Set ID File(s) dialog box displays.
  2. Navigate to the directory where you have placed the message set file for the connector and select the appropriate message set file (*.set) or files.
  3. Click Open. The Business Object Name field displays the business object names contained in the *.set file. The numeric message set ID for each business object is listed in its corresponding Message Set ID field.
    Do not change the message set IDs. These names and numeric IDs are saved when you save the configuration file.
  4. When you add business objects to the configuration, you must load their message set files. If you attempt to load a message set that contains a business object name that already exists in the configuration, or if you attempt to load a message set file that contains a duplicate business object name, Connector Configurator detects the duplicate and displays the Load Results dialog box.
    The dialog box shows the business object name or names for which there are duplicates. For each duplicate name shown, click in the Message Set ID field, and select the Message Set ID that you wish to use.

If WAS is your broker

When WebSphere Application Server is selected as your broker type, Connector Configurator does not require message set IDs. The Supported Business Objects tab shows a Business Object Name column only for supported business objects.

If you are working in stand-alone mode (not connected to System Manager), you must enter the business object name manually.

If you have System Manager running, you can select the empty box under the Business Object Name column in the Supported Business Objects tab. A combo box appears with a list of the business objects available from the Integration Component Library project to which the connector belongs. Select the business object you want from this list.


[ Top of Page | Previous Page | Next Page | Table of Contents ]