Navigating the Web Intelligence Process Flows

This process flow describes the process when you schedule a Web Intelligence document from a web client.

Setting a schedule for Web Intelligence document

This process flow describes a previously scheduled Web Intelligence document running at a scheduled time.

1. The Central Management Server (CMS) checks the CMS system database to determine if a Web Intelligence document is scheduled to run.
2. When the scheduled time arrives, the CMS locates an available Web Intelligence Scheduling Service running on an Adaptive Job Server. The CMS sends the schedule request and all information about the request to the Web Intelligence Scheduling Service.
3. The Web Intelligence Scheduling Service locates an available Web Intelligence Processing Server based on the Maximum Connections value configured on each Web Intelligence Processing Server.
4. The Web Intelligence Processing Server determines the location of the Input File Repository Server (FRRS), that houses the document, and the universe metalayer file, on which the document is based. the Web Intelligence Processing Server then requests the document from the Input FRS. the Input FRS locates the Web Intelligence document, as well as the universal file on which the document is based, and then streams them to the Web Intelligence Processing Server.
   Note

   This step also requires communication with the CMS to locate the required server and objects.
5. The Web Intelligence document is placed in a temporary directory on the Web Intelligence Processing Server. The Web intelligence Processing Server opens the document in memory, and QT.dll generates the SQL from the universe on which the document is based. The Connection Server libraries included in the Web Intelligence Processing Server connect to the data source. The query data passes through QT.dll back to the Report Engine in the Web Intelligence Processing Server where the document is processed. A new successful instance is created.
6. The Web Intelligence Processing Server uploads the document instance to the Output FRS.
   Note

   This step also requires communication with the CMS to locate the required server and objects.
7. The Web Intelligence Processing Server notifies the Web Intelligence Scheduling Service (on the Adaptive Job Server) that the documentation creation is completed. If the document is scheduled to go to a destination (file system, FTP, SFTP, SMTP, or Inbox), the Adaptive Job Server retrieves the processed document from the output FRS and delivers it to the specified destination(s). Assume that this is not the case in this example.
8. The Web Intelligence Scheduling Service updates the CMS with the job status.
9. The CMS updates the job status in its memory, and then writes the instance information to the CMS system database.

The process flow when viewing a Web Intelligence varies depending on:

• Contents of cache
  • Universes
  • Documents
• Type of request
  • On demand
  • Instance
• Relevant configuration of the servers
  • Time-out settings
    • Idle connection
    • Idle job
    • Security cache
    • On demand data
  • Shared Data allowed

When you view a Web Intelligence document on demand, the following link describes the process:

Viewing Web Intelligence on demand