This article describes the various options available under System Configuration. System Configuration is located under Settings.


  • Welcome Message: Custom message displayed on the InfoBurst login screen 
  • Macro Concatenation Character: Character used to concatenate InfoBurst function macros (TBD) 
  • Macro Delimiter Character:Character used to delimit InfoBurst system macros 
    • Default: [ ] 
    • Supported Characters: [ ] ( ) { } < > 
  • Verify network paths against registered paths: A Network Share must be registered before it can be used in a delivery. Uncheck this option to allow users to define their own network path (not recommended). 
  • Enable SSL: Enable SSL for InfoBurst Platform communications (see SSL) 
  • WebI parameter LOV validation for XI3 and newer:Control how or if values passed to BusinessObjects document parameters are validated against the default BusinessObjects list of values (LOV)
    • Abort (default): Abort if parameter value does not match default LOV
    • Continue: Detect if parameter value does not match default LOV, return informational message and continue processing
    • Off: Disable validation


Control how users authenticate to the InfoBurst Platform

  • Authentication Mode:Select authentication mode
  • Active Directory Synchronization: Synchronize Active Directory groups with InfoBurst (see Authentication Management > Active Directory Synchronization)
    • Select green plus icon to select an Active Directory group
    • Synchronize every: Set synchronization frequency
    • Select green arrows icon to force synchronization
  • Enable user credentials pass thru for network authentication: Option to pass user credentials or NTUser for network delivery authentication (not recommended)
    • Use the following for username:
      • Username: Pass InfoBurst username and password as network credentials
      • NTUser: Pass NTUser as username and Infoburst user password as network credentials
    • This option only applies when Verify network paths against registered paths (see General above) is disabled. We recommend leaving Verify network paths against registered paths enabled where the InfoBurst service account is used for all network share deliveries (see Installation > Post-Installation > Service Account).
  • Mobile Authentication: Select a mobile authentication source (see Authentication Management > Mobile Authentication)

Parameter Alias

Bursting parameters can be aliased to simplify parameter reference. A document parameter is defined as either a prompt or filter.

Create an Alias

If no aliases exist:

  • Enter a Name under Alias Details
  • Select the parameter to be aliased from dropdown menu
  • Select the green plus button to add the parameter to list of aliased parameters
  • Select the Add to add the parameter alias

If one or more aliases exist:

  • Select the green/yellow plus button below Select an alias to create another alias

Parameter Alias
  • Select 1013_003.png
  • Start typing a parameter name and a list of similar parameter names will be displayed
  • Select the parameter to alias
  • Select the green plus button to add the parameter to the alias list
  • Select Save

Report Variable (Filter) Alias
  • Select 1013_004.png
  • Enter the report variable name
  • Select the green plus button to add the report variable to the alias list
  • Select Save

  • Document contains parameter Enter value(s) for State:. You want to reference the parameter value in a file name using a macro. Create parameter alias state then reference the alias instead of the original parameter name ([=Enter value(s) for State:] > [=state]).
  • Parameters across multiple documents reference the same report variable (object) but with different parameter names (Enter value(s) for State:,Enter State:, etc.). Create a single alias and reference multiple parameters.

Burst Options

Configure various global Burst options.

Default Document Processing Mode

A specific BusinessObjects server can be assigned to process a document. Set default processing mode for all BusinessObjects documents. Processing Mode can also be controlled per-document at the burst level.

  • Server Instance (Adaptive Job Server=Web Intelligence, Desktop Intelligence Job Server=Desktop Intelligence XI3 only, Crystal Reports Processing Server=Crystal Reports)
  • Server On Demand (Adaptive Processing Server=Web Intelligence, Desktop Intelligence Processing Server=Desktop Intelligence XI3 only, Crystal Reports Processing Server=Crystal Reports)

AES Encryption

Select Use AES encryption for all generated zip archives to enforce AES encryption on any delivery that uses a ZIP file. Select Encryption Level to set level of AES encryption (128,192,256).

Burst Alerts

Define a user group to receive notification of one or more Burst failures

  • Alert Mode: Select a mode
    • None: Disable all burst alerts
    • All: Selected group(s) will receive alerts for all bursts in the system
    • Selected: Selected group(s) will receive alerts for selected burst(s)
  • Bursts to alert on: Select the green plus button and select a burst
  • Alert Groups: Select alert group

XDC Options

Configure various global XDC options.

  • Error Message Mode: Select the detail level of error messages returned to a dashboard when an XDC is requested
  • XDC Alerts:Define a user group to receive notification of one or more XDC failures
    • Alert Mode:Select a mode
      • None: Disable all XDC alerts
      • All: Selected group(s) will receive alerts for all XDCs in the system
      • Selected: Selected group(s) will receive alerts for selected XDC(s)
    • XDCs to alert on: Select the green plus button and select an XDC
    • Alert Groups: Select alert group


Configure a mail server to be used for deliveries and notifications.

  • From Address: Specify a From address in messages sent from InfoBurst. From address will receive email bounce backs and recipient replies. The default 'dummy' email address is and should be changed upon initial configuration.
  • Primary Server:Specify the address of a mail server (SMTP) to which InfoBurst will relay messages
    • The server hosting the InfoBurst Platform may require permission before relay requests are accepted by the mail server. Consult your mail server administrator.
  • Backup Server (optional): Specify a backup mail server to be used when/if the primary mail server us unavailable
  • Send Test Email: Sends a test message to the requesting user to confirm successful mail server communication.  Requesting user must have an email address defined in the user's profile.
  • Email Server Authentication:If the mail server (SMTP) requires authentication, then use the process below to configure a mail server username and password:
    • Open a command prompt (Run as administrator)
    • Change directory to the application root folder (default = C:\Program Files (x86)\InfoSol\InfoBurstPlatform)
    • Enter IBConfig EmailServerAuthUser <USERNAME>
    • Enter IBConfig EmailServerAuthPassword <PASSWORD>
    • Enter IBConfig to confirm the change
    • Restart the InfoBurstPlatform service

Priority Queue

The Priority Queue exists separate from Platform Queues and is designed for schedules that must run, regardless of queue lengths in existing platform queues. The default priority queue length is 5. This value can be modified.

Add a Schedule

  • Select the green plus button
  • Select a schedule

Adjust Queue Length

There are two queues that comprise the Priority Queue. Both must be modified with the same value.
  • Log into the Command Shell 
  • Enter Set Config MaxPriorityDeliver="<Queue_Length>" 
  • Enter Set Config MaxPriorityGenerate="<Queue_Length>" 
  • Enter List Config to confirm changes


Please review the processing capabilities of your BusinessObjects environment with your BusinessObjects administrator before adding schedules to the Priority Queue or altering the queue length. General BusinessObjects processing guidelines are for users, not for the use of a programmatic interface leveraging BusinessObjects. InfoBurst can and will put more load on a BusinessObjects environment than interactive users ever could.

If you decide to use the Priority Queue, ensure your BusinessObjects environment can accommodate requests from both the Platform Queues and Priority Queue.

If you increase the queue limits and BusinessObjects errors start occurring, it is most likely because the BusinessObjects environment is not configured properly to scale. Should errors occur, reduce the queue and discuss with your BusinessObjects administrator. InfoSol provides consulting regarding BusinessObjects scalability.