Adding a Default Header or Footer to New Analyses Preventing Auto-Previewing of Results

18-24 System Administrators Guide for Oracle Business Intelligence Enterprise Edition SQL command then a user logging in using l_fr French locale, then the write-back template messages should exist in appropriate language directories. ■ The write-back template files can have any name of your choosing, because the system reads all XML files in the CustomMessages folder. To ensure that write back works correctly, include in the WebMessage element of the file the name of the SQL template that you specified when you created the write-back table. You can have multiple WebMessage elements in one file, with each element specifying one SQL template. The following example shows the specification of the SQL template that is called SetQuotaUseID. WebMessage name=SetQuotaUseID

18.7.3.3 Example: Write-Back Template

A write-back template might resemble this example: ?xml version=1.0 encoding=utf-8 ? WebMessageTables xmlns:sawm=com.siebel.analytics.webmessagev1 WebMessageTable lang=en-us system=WriteBack table=Messages WebMessage name=SetQuotaUseID XML writeBack connectionPool=Supplier insertINSERT INTO regiontypequota VALUES{c0},{c1},{c2},{c3},{c4}insert updateUPDATE regiontypequota SET Dollars={c4} WHERE YR={c0} AND Quarter={c1} AND Region={c2} AND ItemType={c3}update writeBack XML WebMessage WebMessage name=SetQuota XML writeBack connectionPool=Supplier insertINSERT INTO regiontypequota VALUES1,2,3,4,5insert updateUPDATE regiontypequota SET Dollars=5 WHERE YR=1 AND Quarter=2 AND Region=3 AND ItemType=4update writeBack XML WebMessage WebMessageTable WebMessageTables 19 Configuring and Managing Agents 19-1 19 Configuring and Managing Agents If your organization licensed Oracle BI Delivers and if you have the appropriate privileges, then you can use the agents functionality as part of a default installation with no additional configuration. This chapter describes how agents are used, what affects agents, about advanced configuration settings that affect agents, managing device types for agents, and monitoring agent sessions. For information about using agents, see Delivering Content in Oracle Fusion Middleware Users Guide for Oracle Business Intelligence Enterprise Edition. This chapter includes the following topics: ■ Section 19.1, How Are Agents Used? ■ Section 19.2, How Do Antivirus Software and Privileges Affect Agents? ■ Section 19.3, Configuring Settings That Affect Agents ■ Section 19.4, Managing Device Types for Agents ■ Section 19.5, Monitoring Active Agent Sessions 19.1 How Are Agents Used? Agents deliver targeted analytics to users based on a combination of schedule and trigger event. Delivery can be by a variety of routes, for example to Dashboard Alerts or to e-mail. To create an agent, Oracle Business Intelligence users with the Create Agent privilege define the operations that the agent is to perform. Oracle BI Presentation Services packages information such as priority, delivery devices, and user, into a job, and tells Oracle BI Scheduler when to execute the job. For information, see What is Oracle BI Scheduler? in Oracle Fusion Middleware Scheduling Jobs Guide for Oracle Business Intelligence Enterprise Edition Note: If you are migrating an Oracle Business Intelligence environment to a new system, then ensure that you also migrate the Oracle Business Intelligence repository file, the Oracle BI Presentation Catalog, and the Oracle BI Scheduler tables. The Oracle BI Scheduler tables are required for agents. See Section 8.5.6, Diagnosing Issues with Agents for information about diagnostics and log files for agents.