Skip to main content

Configuring parallel listing

By default, Bravura Security Fabric runs user listing in parallel for faster processing. To configure or disable parallel listing:

  1. From the Manage the system (PSA) module, click Maintenance > Options.

  2. Set UPDATE SYSTEM AGENT COUNT to the number (1 or higher) of connectors you want to run concurrently. Default is 50.

  3. Click Update.

When parallel listing is enabled, you can configure a priority sequence to determine in what order listing operations are performed on the target systems; for example, you can have target systems with larger numbers of users listed first. To do this:

  1. From the Manage the system (PSA) module, click Maintenance > Auto discovery > Connector execution order.

  2. Drag and drop one of the double direction arrows in the Target system description field to change the target systems’ order in the list.

  3. Click Update.

    You can also configure this list by entering a colon-separated list in the AGENTORDER HOST LIST variable in the Manage the system > Maintenance > System variables menu.

The Connector execution order interacts with UPDATE SYSTEM AGENT COUNT in the following way:

  1. Target systems that have a sequence number are placed into the parallel queue until it reaches the maximum number specified by UPDATE SYSTEM AGENT COUNT.

  2. The connectors in the queue are all started simultaneously.

  3. Once a connector in the parallel queue finishes, the next connector (specified by sequence number) is placed in the queue and executed.

  4. Auto discovery (the psupdate process) places all unsequenced (unsorted) target systems into the queue and executes them in parallel, as long as the UPDATE SYSTEM AGENT COUNT allows it; they are not executed in a preset order since they lack a sequence number.

    Sequenced (ordered) targets are listed one after the other, in the configured sequence. There is no guarantee that they will start first or last among all targets, only that they will be listed in the configured order. Loading of the list files via the Discovery service (iddiscover) happens for each target after it is successfully listed. Merging their data in the backend database, and any object association, happens for all targets at once, regardless of whether they are sorted or listed in parallel.

In this section: