You can run two or more different integration events at a time. You cannot run an integration event that is already running, and you cannot reinitialize while an integration event is currently running in your login partition.

Integration events run on the logical node defined in the MessageConfiguration.table file(s) for a partition. You can view, run, reinitialize, and stop integration events on all partitions for which you have permission.

In the default configuration, the permissions required to view, run, and reinitialize integration events are defined in the workspace configuration files. Permissions can be customized. For more information, see the Ariba Buyer Administrator Customization Guide.

If no integration events are listed for a partition, it may be that the TIBCO Process Manager (TPM) is not running, or that the channels used by integration events in that partition are disabled (the System.Messaging.Channels. channelname.DisableChannel parameter is set to true in the config/Parameters.table file).

1. View a list of integration events for a partition. By default, no partition is selected.
• Select a partition from the pull-down menu to view a list of integration events for that partition.
• To sort integration events by name or status, click a column header. Click the header again to change the sort order, as indicated by the arrow.
• If available, click the Table Options icon, located in the row above the column headers, to display commands that control the display of data in the table. For example, you can hide or show columns of data; group data; or export data to Excel.
2. Run an integration event and view its status.
   • To view details, errors, and the history of past runs, click the status of an integration event. The status Completed (*) indicates a run was completed with warnings. Click View to see error details, if any.
   • Click Run to run an integration event. Then click OK, or click Cancel to return to the previous page without running the integration event. The Run button is hidden while an integration event is running.
   • To update the status, click Refresh Status. The status In Process indicates a run is in progress.
   • A log message is created in the database audit log when an integration event is run.
3. Reinitialize integration events for all partitions.
   • Select a partition from the pull-down menu and then click Reinitialize. A request is sent to reload the MessageConfiguration.table file(s) for all partitions and the MessageDefinition.table file(s) for all variants. The file(s) are validated, and any error messages are saved to the main log file(s) (for example, AribaBuyernodenameLog.txt in Ariba Buyer, where nodename is the name of an Ariba Buyer logical node; and ACMnodenameLog.txt in Ariba Category Management).
   • The reply with the updated list of integration events may take time. If no updated list is displayed, click Refresh Status periodically until the list is available.
   • Integration events are also reinitialized when you restart your Ariba Spend Management application.
   • Reinitializing integration events stops all integration events that are currently running in other partitions.
4. Stop an integration event that is currently running on a partition.
   • In Ariba Buyer, you can stop an integration event that is currently running on a specific partition on the TIBCO or file channels using the command-line administration tool servermonitor -stopevent option. For more information, see the Ariba Buyer Configuration Guide.