Setting Up Time Schedules for Initiating OFTP Sessions

You can set up time schedules for initiating OFTP sessions.

About this task

For the general usage of the IBM® Sterling B2B Integrator Scheduler see Creating and Managing Schedules. For OFTP, keep the following in mind when using IBM Sterling B2B Integrator for OFTP sessions:

Procedure

  1. Create a business process that invokes the Odette FTP Adapter and passes all process data parameter to the adapter. (Only the PhysicalPartnerContract parameter is used)
  2. Type the name of the business process in the OFTP Physical Partner Contract field Initiator Business Process and type a IBM Sterling B2B Integrator user name in field Business Process User. Optionally, you may enter one or more comma separated Physical Partner Contract Group names in the Group Name List if you want to initiate OFTP sessions for a group of Physical Partner Contracts at the same point of time.
  3. Create a Time Schedule. From the Administrator menu, select Deployment > Schedules > Schedule a business process. For initiating an OFTP Session to Remote Partner B every hour (using Physical Partner Contract A_B_Init) and additionally to initiate an OFTP session for PPC Group "PPC_PARTNER_GROUP." In Associate BPs to Documents Service: Select BP and optional name/value pair, type the name of the business process to start (see template "oftpcheckformessages") and define following supported Name-Value-Pairs:

Results

Name Value
OFTPPPCName

The name of the Physical Partner Contract for which you want to initiate an OFTP session

OFTPPPCGroup The name of the Physical Partner Contract Group for which you want to initiate OFTP sessions.
OFTPActionType (Used for all PPCs and PPC Groups specified)

Conditional: If messages exist for the PPC or PPC group, initiate OFTP Session.

Unconditional: Always initiate OFTP Sessions, even if there are no messages to send. This is used to poll the Remote Partner for messages.

Time Schedules OFTP Session Requirements:

  • There must be at least one OFTPPPCName or OFTPPPCGroup Name-Value-Pair.
  • Both OFTPPPCName and OFTPPPCGroup Name-Value-Pairs can be repeated.
  • OFTPActionType is optional. It may be defined exactly once or not at all.
Note: After successfully testing the scenario you can set the persistence level of business process "oftpcheckformessages" to PERSIST_ON_ERROR to avoid persisting BP data if no OFTP session has to be started because no messages have to be sent. This helps to save system resources if the business process is often called.