Summary


This article describes alternate methods for executing a Burst, including scripting and execution using a third-party scheduler.


IBExec


Execute a Burst where the Burst is submitted to the InfoBurst Platform runtime for execution and therefore will abide by platform queues and Burst generation mode.


1118_001.png

  • Executable: IBExec.exe
  • Location: Application root folder (default = C:\Program Files (x86)\InfoSol\InfoBurstPlatform)
  • Syntax: IBExec <Username> <Password> <Burst_ID/Path>
  • Examples:
    • IBExec admin admin "\Bursts\Burst 1"
    • IBExec admin admin 345
  • Log: Runtime log is retained as Burst Activity Log
  • Status:
    • No status is returned
    • Status can be viewed in the Burst Activity Log
    • LOGID is returned and can be used to query burst status from InfoBurst repository table IBT_RTS (column = Status, Success = 4, Failure = 5)

 IBRun


Execute a Burst where the burst is not submitted to the InfoBurst Platform runtime for execution and therefore will not abide by platform queues and Burst generation mode. Generation mode will be sequential.


1118_002.png


1118_003.png

  • Executable: IBRun.exe
  • Location: Application root folder (default = C:\Program Files (x86)\InfoSol\InfoBurstPlatform) 
  • Syntax: IBRun <Username> <Password> <Burst_ID/Path> -keepwork
    • -KeepWork: Optional argument that retains temporary runtime folders and files in the _RTS folder in the application root folder
  • Examples:
    • IBRun admin admin "\Bursts\Burst 1"
    • IBRun admin admin 345 -KeepWork
  • Log:
    • Runtime log is returned and displayed via command window
    • RTSLogID is returned and individual log file with that ID is saved in the application root (example = C:\Program Files (x86)\InfoSol\InfoBurstPlatform\ibrun_33728.log)
    • Runtime log is retained as Burst Activity Log
  • Status:
    • Process Exit Code is returned (Success = 0, Failure = -1)
    • Status can be viewed in the Burst Activity Log
    • RTSLogID is returned and can be used to query Burst status from InfoBurst repository table IBT_RTS (column = Status, Success = 4, Failure = 5)

 IBRemote


Execute a Burst from a remote server where the Burst is submitted to the InfoBurst Platform runtime for execution and therefore will abide by platform queues and burst generation mode.


  • Executable: IBRemote.exe
  • Location: Application root folder (default = C:\Program Files (x86)\InfoSol\InfoBurstPlatform) 
  • Copy contents to remote server
    • Remote server must have Microsoft .NET Framework 4.6
  • Syntax: IBRemote <IB_Server> <IB_Rest_Port> <Username> <Password> <Burst_ID>
  • Example:
    • IBRemote ibprod 8551 admin admin 19481
  • Log: Runtime log is retained as Burst Activity Log
  • Status:
    • No status is returned
    • Status can be viewed in the Burst Activity Log
    • RTSLogID is returned and can be used to query Burst status from InfoBurst repository table IBT_RTS (column = Status, Success = 4, Failure = 5)

 Command Shell


Execute a Burst using the Command Shell where the Burst is submitted to the InfoBurst runtime for execution and therefore will abide by platform queues and burst generation mode. Command Shell Burst execution can be scripted.


1118_005.png

  • Syntax: exec burst <Burst_ID>
  • Options:
    • to (email resulting Activity Log to user)
    • wait burst (issued as separate command following exec command)
  • Examples:
    • exec burst 19481
    • exec burst 19481 to=bryan@infoburst.net

Script Example

See Command Shell for additional scripting information

 

connect
get token user=admin password=admin
exec burst 19481
exit

 

URL (REST API)


Execute a Burst via URL from a browser where the Burst is submitted to the InfoBurst runtime for execution and therefore will abide by platform queues and burst generation mode.


1118_006.png

  • Syntax: http://<IB_Server>:8551/infoburst/rest/exec/burst/<Burst_ID>
  • Log: Runtime log is retained as Burst Activity Log
  • Status:
    • No status is returned
    • Status can be viewed in the Burst Activity Log
    • RTSLogID is returned and can be used to query Burst status from InfoBurst repository table IBT_RTS (column = Status, Success = 4, Failure = 5)