On the Channel Info tab, specify a unique identifier for the channel and adjust the values for the Max Threads and Timeout fields as needed to optimize data-transfer performance, particularly if large numbers of records need to be provisioned at the target site. The Max Threads and Timeout settings apply to the phase of provisioning when PingFederate is pushing updates to the provisioning target.

The Max Threads setting determines how many threads PingFederate can use to send updates to the target. Using multiple threads should let PingFederate finish this provisioning phase faster. There is no particular order in which PingFederate processes updates. Each thread pulls the user and group update operations from a queue. As soon as a thread finishes one operation, it pulls another operation from the queue. Eventually there will be no more operations in the queue, so all threads will finish at close to the same time, but not exactly.

The Timeout setting determines how long PingFederate has to update a record. If PingFederate takes too long to update a record, it moves to the next record. During the next provisioning cycle, PingFederate will try again to update the skipped record.

Screen capture illustrating the Channel Info tab in the PingFederate administrative console.
  1. Go to Applications > Integration > SP Connection > Configure Channels > Channel. In the Channel Name field, enter a channel name.

    If you are copying a channel, you must enter a new value in this field.

  2. Optional: Update the values for the Max Threads and Timeout fields.

    The Timeout value applies only when the Max Threads value allows multiple threads.

  3. Click Next.