Archiving Feeds

This section provides an overview of archiving feed data and discusses how to archive scheduled feed data.

Scheduled feeds are published asynchronously and stored as messages in Integration Broker queues. The process of archiving feed data archives the messages stored in the Integration Broker queues used by scheduled feeds. You run a batch process to archive and delete the queue message data.

This section provides an overview of:

  • Feed archiving parameters.

  • Feed archiving options and logic.

Feed Archiving Parameters

The following parameters specified in the feed definition are used for archiving the Integration Broker queue messages:

  • Integration Broker Service Operation name

    For generic scheduled feeds, the service operation name is the value of the IB_OPERATIONNAME data source setting.

    For other scheduled feeds, the system uses the service operations listed in the Feed Service Operations grid on the Define Data Types page.

  • Integration Broker subqueue name, when applicable

    For generic scheduled feeds, no subqueue name exists.

    For other scheduled feeds, the Feed ID value is the sub queue name.

  • PTFP_FEED:UTILITY:Utility DSPARAMETER_MAXROW

    For scheduled feeds, you must define this parameter in the data source parameter for the data type.

    This parameter indicates the number of feed items that will appear to the user.

    • If the parameter value is PTFP_FEED:UTILITY:Utility SF_MAXROWOPTION_LATESTMSG, then only the latest message in the Integration Broker queue appears to the user.

    • If the parameter value is PTFP_FEED:UTILITY:Utility SF_MAXROWOPTION_ALLMSGS, then all the messages in the Integration Broker queue appear to the user.

    • The parameter can be a number, for example, 4, which indicates that only 4 items appear to the user.

  • PTFP_FEED:UTILITY:Utility DSPARAMETER_SF_MAXMINUTES

    For scheduled feeds, you must define this parameter in the data source parameter for the data type.

    This parameter tells the length of time for which the feed messages are valid in the Integration Broker queues.

    • If the parameter value is PTFP_FEED:UTILITY:Utility SF_MAXMINUTES_ALLMSGS, then all the messages appear to the user.

    • If the parameter value is a number, for example 100, then all the feed messages existing in the Integration Broker queue for fewer than 100 minutes appear to the user.

Feed Archiving Options and Logic

This table describes the feeds archiving options and logic:

Option Value

Description

Archiving Logic

0

Archive all messages that are not within the specified date and time range.

When DSPARAMETER_SF_MAXMINUTES is not SF_MAXMINUTES_ALLMSGS.

1

Archive all messages except latest 1 message per subqueue per language.

When DSPARAMETER_SF_MAXMINUTES is SF_MAXMINUTES_ALLMSGS and DSPARAMETER_MAXROW is SF_MAXROWOPTION_LATESTMSG.

2

Archive all messages except latest n messages per subqueue per language.

When DSPARAMETER_SF_MAXMINUTES is SF_MAXMINUTES_ALLMSGS and DSPARAMETER_MAXROW is some number. This number indicates the number of messages that should not be archived.

3

Archive nothing.

When DSPARAMETER_SF_MAXMINUTES is SF_MAXMINUTES_ALLMSGS and DSPARAMETER_MAXROW is SF_MAXROWOPTION_ALLMSGS.

Note: The feed archiving options are implicitly arrived at based on the feed definition. These cannot be specified when the PTIBFEEDARCH process runs.

Access the Run Feed Archive page (PeopleTools > Feeds > Archive Feed Data).

Image: Run Feed Archive page

This example illustrates the fields and controls on the Run Feed Archive page.

Run Feed Archive page

Click the Run button to access the PTIBFEEDARCH process:

Image: Process Scheduler Request page showing the PTIBFEEDARCH process

This example illustrates the fields and controls on the Process Scheduler Request page showing the PTIBFEEDARCH process.

Process Scheduler Request page showing the PTIBFEEDARCH process

Use the Run Feed Archive page to archive Integration Broker messages that are used by scheduled feeds. Archiving takes no parameters from the user; parameters for archiving come from the feed definitions themselves.

All scheduled feeds are archived simultaneously; you cannot selectively archive feeds. The process archives and deletes the feed data based on the Archive flag in the Integration Broker queue used in the service operations that published messages to Integration Broker queues. If the Archive flag is enabled, then the messages are archived and then deleted; otherwise, the messages are just deleted.

You can view archived Integration Broker messages by using the Service Operations Monitor. Look for asynchronous services with the Archive flag enabled.

Note: A scheduled feed can be archived only if the service operations involved in the scheduled feeds are listed in the Feed Service Operations grid on the Define Feed Data Types page.

Note: Feeds archiving logic is comparable to Integration Broker archiving logic. For a feed message to be archived, you must select the Archive check box on the Queue Definition page for the service operation. If you do not select the Archive check box, then the feeds archiving process deletes the feed messages and the messages do not appear on the Service Operation Monitor - Asynchronous Services page when the Archive check box is selected.

See Monitoring Asynchronous Service Operation Transactions.