PK
JwEoa, mimetypeapplication/epub+zipPK JwE iTunesMetadata.plisto
This chapter describes how configure and manage agents in Oracle Business Intelligence. If your organization licenses 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. For information about using agents, see "Delivering Content" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition.
This chapter includes the following sections:
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.7, "Diagnosing Issues with Agents" for information about diagnostics and log files for agents. |
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 email.
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
This section provides the following information about agents:
Some antivirus software programs, such as Norton AntiVirus, enable a script-blocking feature, which tries to block all calls made by scripts to system objects (such as the Windows file system object) that the antivirus software deems unsafe.
If you start a script as part of post-agent processing, then this antivirus feature might cause unexpected results. If you run antivirus software with a script-blocking feature on the computer where Oracle BI Scheduler is installed, then disable the script-blocking feature to prevent the software from unexpectedly blocking agent script calls.
You access the privilege settings for agents in the Delivers section of the Manage Privileges page in Oracle BI Presentation Services Administration.
To create an agent, users must be granted the Create Agent privilege. To enable users with the Publish Agents for Subscription privilege, which provides the ability to change or to delete an agent, you must grant them the Modify permission to the shared agent objects and child objects in the Oracle BI Presentation Catalog. For information, see "Managing Presentation Services Privileges" in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.
Note: If the Oracle BI Server is configured to authenticate users through database logons, then impersonation is permitted until the number of associated variables exceeds one (for example, when session variables other than USER are associated with the initialization block). If the number of associated variables exceeds one, then the impersonated user does not have the password to log in to the database and to fill the other session variables. Agents work with database authentication, if only the initialization block that is set up for authentication in the Oracle BI Administration Tool uses a connection pool with pass-through login. That connection pool cannot be used for any other initialization block or request. For information about user authentication options, see Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition. For information about pass-through login, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition. |
You configure settings for agents by changing values for Oracle BI Presentation Services or Oracle BI Scheduler. You configure delivery options for agents using the SA System subject area. This section contains the following topics:
Section 20.3.1, "Manually Configuring Presentation Services Settings that Affect Agents"
Section 20.3.2, "Manually Changing Additional Scheduler Settings that Affect Agents"
Section 20.3.3, "What Additional Scheduler Configuration Settings Affect Agents?"
Use various elements in the instanceconfig.xml file for Presentation Services to change these settings. You must apply changes to both the primary and secondary scheduler's instanceconfig.xml in a cluster.
Before you begin this procedure, ensure that you are familiar with the information in Section 3.4, "Using a Text Editor to Update Configuration Settings."
To manually edit Presentation Services settings that affect agents:
Open the Presentation Services instanceconfig.xml file for editing, as described in Section 3.6, "Where Are Configuration Files Located?"
Locate the section in which you must add the elements that are described in Table 20-1.
Include the elements and their ancestor elements as appropriate, as shown in the following example:
<ServerInstance> <Alerts> <Enabled>false</Enabled> <DefaultDeliveryFormat>pdf</DefaultDeliveryFormat> </Alerts> </ServerInstance>
Save your changes and close the file.
Restart Presentation Services.
Table 20-1 Presentation Services Settings That Affect Agents
Element | Description | Default Value |
---|---|---|
Enabled |
Specifies whether Oracle BI Delivers is enabled. Possible values are true or false. Delivers is an optional component of Presentation Services that is enabled by default for organizations that have purchased the appropriate license. You use the Delivers component to create agents. |
true |
DefaultDeliveryFormat |
Specifies the default format for sending emailed reports through an agent. For example, a content designer can create an agent to send a report every day to a development team to share how many bugs have been fixed in the past day. When the content designer creates the agent, he can specify the format of the email. As the administrator, you can specify the default format that is used for such emails, using one of the following values: html excel text |
html |
In addition to the scheduler settings that you can change in Fusion Middleware Control, you can change other settings manually. Use various elements in the instanceconfig.xml file to change these settings. You must apply changes to both the primary and secondary scheduler's instanceconfig.xml in a cluster.
Before you begin this procedure, ensure that you are familiar with the information in Section 3.4, "Using a Text Editor to Update Configuration Settings."
To manually change additional Oracle BI Scheduler settings that affect agents:
Open the Oracle BI Scheduler version of the instanceconfig.xml file for editing, as described in Section 3.6, "Where Are Configuration Files Located?"
Locate the sections in which you must add or update the elements that are described in Section 20.3.3, "What Additional Scheduler Configuration Settings Affect Agents?"
Include the elements and their ancestor elements as appropriate. The entry for Log_Dir is shown in the following example:
<xs:element name="Log_Dir" type="xs:string" default="ibots" minOccurs="0"> <xs:annotation> <xs:documentation xml:lang="en"> The directory where Agent logs are stored. </xs:documentation> </xs:annotation> </xs:element>
Note: You cannot specify values for user name and password in the instanceconfig.xml file. Instead you specify values in Fusion Middleware Control that are stored securely within the central credentials wallet, along with all other user names and passwords. |
Save your changes and close the file.
Restart Oracle Business Intelligence.
You can change the following additional Oracle BI Scheduler configuration settings that affect agents:
Section 20.3.3.1, "General Scheduler Configuration Settings that Affect Agents"
Section 20.3.3.2, "Email Scheduler Configuration Settings that Affect Agents"
General configuration settings include access to, and configuration of, the Scheduler back-end database, some behavior settings, and settings for secure sockets and clustering configuration. Table 20-2 describes the settings.
Table 20-2 General Scheduler Configuration Settings that Affect Agents
Element | Description | Default Value |
---|---|---|
Specifies the amount of time in minutes that a connection to the data source remains open after an operation completes. During this time, new operations use this connection rather than open a new one, up to the number specified for Maximum Connections. The time is reset after each completed connection request. Specify a value of 1 or greater. |
60 | |
Specifies the maximum number of database connections that Oracle BI Scheduler can open concurrently. Specify a value of 1 or greater. When this limit is reached, the connection request waits until a connection becomes available. |
5 | |
Specifies the name of a database table used to store information about scheduled jobs. Note: For information about modifying the database table names, see "Changing Oracle BI Scheduler Table Names" in Oracle Fusion Middleware Scheduling Jobs Guide for Oracle Business Intelligence Enterprise Edition and see Oracle Business Intelligence Applications Installation and Configuration Guide. |
S_NQ_JOB | |
TABLE_INSTANCES |
Specifies the name of a database table used to store information about job instances. |
S_NQ_INSTANCE |
TABLE_PARAMS |
Specifies the name of a database table used to store information about job parameters. |
S_NQ_JOB_PARAM |
TABLE_ERRMSGS |
Specifies the name of a database table used to store information about job instances that do not complete successfully. |
S_NQ_ERR_MSG |
Refers to the path where Oracle BI Scheduler-created job scripts are stored. In general, do not add or remove scripts from this directory. By default, this field is set to ORACLE_INSTANCE\bifoundation\OracleBISchedulerComponent\coreapplication_obischn\scripts\scheduler, for example D:\OBI11g\instances\instance1\bifoundation\OracleBISchedulerComponent\coreapplication_obisch1\scripts\scheduler. |
scripts\scheduler | |
Specifies the path where user-created job scripts (not agents) are stored. If a file name is entered in the Script field when adding or modifying a job, then Oracle BI Scheduler examines the contents of this directory for the specified file. However, if a full path is given in the Script field, then this directory is not examined. By default, this field is set to ORACLE_INSTANCE\bifoundation\OracleBISchedulerComponent\coreapplication_obischn\scripts\common, for example D:\OBI11g\instances\instance1\bifoundation\OracleBISchedulerComponent\coreapplication_obisch1\scripts\common. |
scripts\common | |
Specifies the path where temporary files are stored during Oracle BI Scheduler execution. |
No default value | |
Used in the database gateways. Specifies the maximum size in bytes of a bulk fetch page for retrieving data from a data source. |
33,792 | |
Occasionally you might set up the Scheduler to point to a database using a generic protocol like ODBC. This is usually done when the Target Type is not specified. When this happens, and a SQL statement fails, you must be able to determine which statement failed. Turning this setting on places the SQL statements in the Scheduler log file. Do not set this to TRUE in production mode as the overhead for this is quite high. |
false | |
Specifies the port number for the server. Defaults to the Oracle BI Scheduler port number. |
The port number set for the Scheduler. | |
Specifies the number of days after which old job instances are deleted from the back-end database automatically. To prevent old job instances from being deleted automatically, set the value to 0 (zero). |
7 | |
Specifies the number of minutes in which Oracle BI Scheduler updates the tables and flags the affected rows as deleted. Note: Oracle BI Scheduler does not actually issue SQL DELETE statements when jobs or instances are removed, instead rows are flagged for deletion. After every X minutes (where X is defined as the value of this field), the actual SQL DELETE statements are issued. |
60 | |
Specifies the minimum number of multiple threads in the Oracle BI Scheduler thread pool that executes jobs at runtime. |
1 | |
Specifies the maximum number of multiple threads in the Oracle BI Scheduler thread pool that executes jobs at runtime. |
100 | |
Specifies that no jobs are executed when Oracle BI Scheduler starts. While Oracle BI Scheduler pauses, users can add, modify, and remove jobs. However, no jobs execute. From the Service Management menu, select Continue Scheduling to continue with regular execution. |
false | |
Specifies the SSL Certificate File Path. This setting supports SSL. |
No default value | |
Specifies the SSL Certificate Private Key File. This setting supports SSL. |
No default value | |
Specifies the SSL File Containing Passphrase. This setting supports SSL. |
No default value | |
PassphraseProgramName |
Specifies the SSL Program Producing Passphrase. This setting supports SSL. |
No default value |
Specifies the SSL Certificate Verification Depth. |
No default value | |
Specifies the CA Certificate Directory. This setting supports SSL. |
No default value | |
Specifies the CA Certificate File. This setting supports SSL. |
No default value | |
Specifies the SSL Trusted Peer DNs. |
No default value | |
VerifyPeer |
Specifies whether to verify the peer. This setting supports SSL. |
false |
Specifies the Cipher List. This setting supports SSL. |
No default value | |
Specifies the port used for interprocess communication between the script processes and the Oracle BI Scheduler process. This port accepts connections only from the same computer on which Oracle BI Scheduler is running. |
9707 |
Table 20-3 Email Scheduler Configuration Settings that Affect Agents
Element | Description | Default Value |
---|---|---|
SmtpCipherList |
Specifies the list of ciphers that match the cipher suite name that the SMTP server supports. For example, RSA+RC4+SHA. For information, see "Advanced SSL Configuration Options" in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition. |
No default value |
UseStartTLS |
Ignored unless UseSSL is true. If UseStartTls is true, then use the STARTTLS option (RFC 2487) for the SMTP session. Initial connection is through an unsecured link, usually port 25. The connection is then promoted to a secure link using the STARTTLS SMTP command. If UseStartTls is false, then a secured connection is created immediately, before the SMTP protocol is started. This is also known as SMTPS. SMTPS typically uses port 465. |
true |
Agents are functionally a combination of data that is stored in Oracle BI Presentation Services and Oracle BI Scheduler. The elements in the Scheduler instanceconfig.xml file describe the behavior of all agents that run on a specific Oracle BI Scheduler. Table 20-4 describes each agent configuration element.
Table 20-4 Agent Scheduler Configuration Settings
Element | Description | Default Value |
---|---|---|
Agents can create log files if exceptional error conditions occur. Log_Dir specifies the directory where these files are saved. The directory must be accessible to the Oracle BI Scheduler server. In Windows, the default installation runs the service as a system account, which prevents Oracle BI Scheduler from writing to or reading from network directories. If you put script files on network shares, or your scripts access network shares, then Oracle BI Scheduler must be run as a network user. For example: For information about log files, see Section 8.5.7, "Diagnosing Issues with Agents." |
ibots | |
Specifies the number of days after which old agent logs are deleted automatically. To prevent old logs from being deleted automatically, set the value to 0 (zero). |
7 | |
A web or mail server that has too many people logged on might reject new connections, including connections from Oracle BI Scheduler. To cope with such overload, an agent retries the connection. This element sets the maximum number of retries to obtain global information about what to deliver and to whom before the agent gives up. If you set this value to 0 (zero), then no retries are attempted. |
2 | |
Specifies the minimum number of seconds that the agent randomly sleeps after its connection is refused before it attempts to reconnect to the server to obtain global information about what to deliver and to whom. |
3 | |
Specifies the maximum number of seconds that the agent randomly sleeps after its connection is refused before it attempts to reconnect to the server to obtain global information about what to deliver and to whom. |
10 | |
After an agent has received the global information, it issues a series of unique requests to the server for each user. This element specifies the number of times Oracle BI Scheduler retries its attempts to connect to the server to issue these requests. If you set this value to 0 (zero), then no retries are attempted. |
3 | |
Specifies the minimum number of seconds that the agent randomly sleeps after its connection is refused before it attempts to reconnect to the server to issue requests. |
2 | |
Specifies the maximum number of seconds that the agent randomly sleeps after its connection is refused before it attempts to reconnect to the server to issue requests. |
10 | |
After a unique request has executed, the agent tries to deliver the results to specified devices. This specifies the number of times that Oracle BI Scheduler attempts to retry to connect to the server to deliver the results. If you set this value to 0 (zero), then no retries are attempted. |
4 | |
Specifies the minimum number of seconds that the agent randomly sleeps after its connection is refused before it attempts to reconnect to the server to deliver results. |
5 | |
Specifies the maximum number of seconds that the agent randomly sleeps after its connection is refused before it attempts to reconnect to the server to deliver results. |
10 | |
When agents are chained, this value governs the size of filters passed between agents. When you pass a filter to another agent in a chain, Oracle BI Scheduler creates a union of the result sets for the Conditional Report for each personalized recipient. This report can grow very large in some cases (1000 users with 100 unique rows each with ten columns per report = 1,000,000 column values in the filter). The Oracle Business Intelligence servers might not be able to handle such a large filter, so this element specifies the maximum number of rows*columns in the filter. |
10,000 | |
Debug |
Debug Enabled. Set this element to have Oracle BI Scheduler generate a log file for each agent. This log file has useful logging messages when trying to diagnose a problem. This log file is stored in ORACLE_INSTANCE\diagnostics\logs\OracleBISchedulerComponent\coreapplication_obischn. A new log file named Agent-<Job number>-<Instance number>.log is created for each job instance. The Job Manager can also be used to override the Debug setting for an individual job. For more information, see Section 8.5.7, "Diagnosing Issues with Agents." |
false |
Set this element to true to generate an error log file for each agent. This log file is created only when an agent execution encounters errors and contains only error messages. The file is stored in ORACLE_INSTANCE\diagnostics\logs\OracleBISchedulerComponent\coreapplication_obischn. |
true |
Delivery options (that is, delivery devices and delivery profiles) determine how the contents of agents are delivered to users. Delivery options can be configured by users, in the LDAP server (for email addresses), or in the SA System subject area. See "Setting Up the SA System Subject Area" in Oracle Fusion Middleware Scheduling Jobs Guide for Oracle Business Intelligence Enterprise Edition for information.
You can use different device types from such categories as mobile phones and pagers to deliver the content of agents to users. You can create, view, edit, and delete device types for a device category. Many device types are provided automatically. You can add types that are required for your users.
Note: You can only view system-seeded device types (such as AT&T Wireless); you cannot edit or delete them. |
The capability to manage device types is available to users who have the Manage Device Types privilege. For information about privileges, see "Managing Presentation Services Privileges" in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition.
To create a device type:
Log in to Oracle Business Intelligence.
In the global header, click Administration.
Click the Manage Device Types link to display the Manage Device Types page.
Click the Create New Device Type link.
Complete the Create New Device Type dialog, and click OK.
Click Create Device Type to return to the Manage Device Types screen.
To view or edit a device type:
In the global header, click Administration.
Click the Manage Device Types link.
Click the Edit button for the appropriate device type.
Complete the Edit Device Type dialog, and click OK.
To delete a device type:
In the global header, click Administration.
Click the Manage Device Types link.
Click the Delete button for the device type to delete.
A confirmation box is displayed.
Click OK to confirm the deletion.
For more information about the Administration page in Oracle Business Intelligence, see "Administration page" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition.
Using the Manage Agent Sessions page in Oracle BI Presentation Services Administration, you monitor currently active agent sessions that are triggered by Oracle BI Scheduler. For example, you can see a list of active agents per session.
When one or more agent sessions are active, information about each agent session is displayed, such as the job identifier and the instance identifier that are assigned to the agent session by the Oracle BI Scheduler. Expanding the agent session shows the individual agents (one agent, or multiple agents if they are chained). The state of the agent is either Created, Populated, or Conditional Request Resolved.
Expanding a specific agent in a particular session shows the recipients for the agent and their type, such as the Engineering recipients defined in a group, or individual users. When the recipient is a group, the individual members of the group are not listed.
Note: When agents are chained, the recipient list is depends on the parent agent. The recipients are shown for the parent agent definition only, and not for the actual execution of chained agents. |
To view information about active agent sessions:
In the global header, click Administration.
Click the Manage Agent Sessions link to display the Manage Agent Sessions page and do one of the following:
To sort agent sessions by their values in a particular column, click the Sort button for that column.
Re-sorting the list causes the page to refresh so the number of active agent sessions might increase or decrease as a result.
To view more information about an agent session or about agents within a particular session, click the Expand button.
To view the definition of an individual agent, click its link.
For more information about the Administration page in Oracle Business Intelligence, see "Administration page" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition.
This chapter describes how to manage usage tracking for Oracle Business Intelligence. The Oracle BI Server supports the collection of usage tracking data. When usage tracking is enabled, the Oracle BI Server collects usage tracking data for each query and inserts it directly to a database table.
Note: The Oracle BI Summary Advisor feature works in conjunction with the usage tracking feature. Summary Advisor only works with direct insertion usage tracking. Oracle BI Summary Advisor is only available when you are running Oracle Business Intelligence on the Oracle Exalytics Machine. See "Using Oracle BI Summary Advisor to Identify Query Candidates for Aggregation" in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition for more information about the Summary Advisor feature. |
This chapter includes the following sections:
The Oracle BI Server supports the accumulation of usage tracking statistics that can be used in a variety of ways such as database optimization, aggregation strategies, or billing users or departments based on the resources that they consume. The BI Server tracks usage at the detailed query level.
When you enable usage tracking, statistics for every query are inserted into a database table or are written to a usage tracking log file. If you use direct insertion, then the BI Server directly inserts the usage tracking data into a relational database table. It is recommended that you use direct insertion to write statistics to a database table.
When the BI Server starts, it validates the column names in the metadata against the list of valid columns in the usage tracking table. The following events occur:
Column names. If there is a mismatch between the columns in the database table and the columns in the metadata, then it results in a database error on insert.
Varchar length. If the length in the metadata and the set length in the table do not match, then an error is written to the nqserver.log file and usage tracking is disabled.
Note: A sample usage tracking repository model is provided with the Oracle Business Intelligence installation at: ORACLE_INSTANCE\bifoundation\admin\provisioning\OracleBIServerComponent\usage_tracking.rpd. This path applies to Oracle BI EE 11.1.1.7.10 and later versions, but does not apply to earlier versions. To use the sample usage tracking repository, you modify the connection pool to point to your database, then merge the usage tracking repository with your existing repository. |
Direct insertion is the recommended method for setting up usage tracking. This section describes how to set up direct insertion, and contains the following topics:
Before you can use direct insertion usage tracking, you must set up a database to store the usage tracking statistics. You must run the Repository Creation Utility (RCU) on the target database to create the required statistics schemas.
Typically, you use the database you installed for use with Oracle Business Intelligence as the statistics database because this database already has the RCU-created schemas. The RCU-created table names for usage tracking are S_NQ_ACCT
and S_NQ_DB_ACCT
. See Section 9.3, "Description of the Usage Tracking Data" for more information about these tables.
You also need to import the database into the Physical layer of the Oracle BI repository.
To set up the usage tracking statistics database:
Run the Repository Creation Utility on an external database of your choice. You can skip this step if you choose to use the database you installed for use with Oracle Business Intelligence for usage tracking statistics, because this database has the RCU-created tables already.
Open the Administration Tool and import the database into the Physical layer. See Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition for more information.
Save and close the repository.
Use Fusion Middleware Control to upload the repository and make it available for queries. See Section 10.2, "Using Fusion Middleware Control to Upload a Repository and Set the Oracle BI Presentation Catalog Location" for more information.
To set up direct insertion for new (non-upgraded) installations, use the System MBean Browser in Fusion Middleware Control.
To set up direct insertion usage tracking using the System MBean Browser:
Display the Fusion Middleware Control MBean Browser.
For information, see Section 2.4.2, "Displaying the Fusion Middleware Control MBean Browser."
Expand Application Defined MBeans, then expand oracle.biee.admin, then expand Domain: bifoundation_domain.
Lock the domain, as follows:
Expand BIDomain and select the BIDomain MBean where group=Service.
Display the Operations tab.
Click the lock link.
Expand BIDomain.BIInstance.ServerConfiguration, then select the BIDomain.BIInstance.ServerConfiguration MBean.
Ensure that the UsageTrackingCentrallyManaged attribute is set to true. When UsageTrackingCentrallyManaged is set to false, the following parameters are managed using the NQSConfig.INI file on each Oracle BI Server computer rather than the System MBean Browser:
SummaryAdvisorTableName
SummaryStatisticsLogging
UsageTrackingConnectionPool
UsageTrackingDirectInsert
UsageTrackingEnabled
UsageTrackingPhysicalTableName
Set the UsageTrackingEnabled attribute to true to enable usage tracking.
Set the UsageTrackingDirectInsert attribute to true to enable direct insertion.
Set the UsageTrackingPhysicalTableName attribute to the name of the fully-qualified database table for collecting query statistic information, as it appears in the Physical layer of the Oracle BI repository. For example:
"My_DB"."DEV_BIPLATFORM"."S_NQ_ACCT"
Set the UsageTrackingConnectionPool attribute to the name of the fully-qualified connection pool for the query statistics database, as it appears in the Physical layer of the Oracle BI repository. For example:
"My_DB"."Usage Connection Pool"
Note: For Usage Tracking insertions to succeed, the connection pool must be configured with a user ID that has write access to the back-end database. Also, it is recommended that the connectivity type supports international data. |
After applying your changes, release the lock on the domain, as follows:
Return to the BIDomain MBean where group=Service under oracle.biee.admin, Domain:bifoundation_domain, BIDomain.
Display the Operations tab.
Click one of the commit operations.
Go to the Oracle Business Intelligence Overview page and click Restart.
For upgrading customers, the usage tracking parameters are not centrally managed by default. You can set UsageTrackingCentrallyManaged to true as described in the previous procedure, and use the System MBean Browser to update the parameters, or you can manage the usage tracking parameters using NQSConfig.INI.
To enable direct insertion usage tracking in NQSConfig.INI when central management is disabled for these parameters, follow these steps:
On the Oracle BI Server computer, open the NQSConfig.INI file in a text editor. You can find this file at:
ORACLE_INSTANCE/config/OracleBIServerComponent/coreapplication_obisn
Make a backup copy of the file before editing.
In the [USAGE_TRACKING] section, update the following parameters:
Set ENABLE
to YES
.
Set DIRECT_INSERT
to YES
.
Set PHYSICAL_TABLE_NAME
to the name of the fully-qualified database table for collecting query statistic information, as it appears in the Physical layer of the Oracle BI repository. For example:
PHYSICAL_TABLE_NAME = "My_DB"."DEV_BIPLATFORM"."S_NQ_ACCT";
Set CONNECTION_POOL
to the name of the fully-qualified connection pool for the query statistics database, as it appears in the Physical layer of the Oracle BI repository. For example:
CONNECTION_POOL = "My_DB"."Usage Connection Pool";
Note: For Usage Tracking insertions to succeed, the connection pool must be configured with a user ID that has write access to the back-end database. Also, it is recommended that the connectivity type supports international data. |
Save and close the file.
Restart the Oracle BI Server.
If you have multiple Oracle BI Server instances, then repeat these steps in each NQSConfig.INI file for all Oracle BI Server instances.
In addition to the setup parameters described previously, you can also update the following optional parameters in the Usage Tracking section of the NQSConfig.INI file:
BUFFER_SIZE. This parameter indicates how much memory the BI Server allocates for buffering the insert statements. Such a buffer lets the BI Server submit multiple insert statements as part of a single transaction, improving Usage Tracking insert throughput. It also means that ordinary analyses do not have to wait on Usage Tracking insertions, which improves average query response time. You might want to adjust this value based on available memory and memory utilization on the server computer.
BUFFER_TIME_LIMIT_SECONDS. This parameter indicates the maximum amount of time that an insert statement remains in the buffer before the Usage Tracking subsystem attempts to issue it. This time limit ensures that the BI Server issues the insert statements quickly, even during periods of extended quiescence.
NUM_INSERT_THREADS. This parameter indicates the number of threads that remove insert statements from the buffer and issue them to the Usage Tracking database. Assuming separate connection pools for readers and inserters, the number of insert threads typically equals the Maximum Connections setting in the connection pool.
MAX_INSERTS_PER_TRANSACTION. This parameter indicates the maximum number of insert statements that the Usage Tracking subsystem attempts to issue as part of a single transaction. The larger this number, the greater potential throughput for UsageMarathon Tracking inserts. However, a larger number also increases the likelihood of transactions failing due to deadlocks. A small value for BUFFER_TIME_LIMIT_SECONDS
can limit the number of inserts per transaction.
See Appendix A, "NQSConfig.INI File Configuration Settings" for additional information about the usage tracking configuration parameters.
Table 9-1 describes each column in the S_NQ_ACCT
usage tracking table. Where appropriate, the data type and length is also included.
As you review the descriptions in Table 9-1, you might assume that certain of the time-related columns can be added or subtracted to equal exact values. For example, you might assume that TOTAL_TIME_SEC is equal to END_TS minus START_TS. The following list explains why the columns do not provide such exact values:
The various processes run in parallel and their speed depends on the load on the BI Server and on database performance. The server-based operations might be either light or intensive.
If all connections are full, then the query enters a queue and waits to be processed. The timing depends on the load and configuration of the BI Server.
Table 9-1 Usage Tracking Data in S_NQ_ACCT
Column | Description |
---|---|
CACHE_IND_FLG |
Default is N. Y indicates a cache hit for the query; N indicates a cache miss. |
COMPILE_TIME_SEC |
The time in seconds that is required to compile the query. The number for COMPILE_TIME_SEC is included in TOTAL_TIME_SEC, as described in this table. |
CUM_DB_TIME_SEC |
The total amount of time in seconds that the BI Server waited for back-end physical databases on behalf of a logical query. |
CUM_NUM_DB_ROW |
The total number of rows that are returned by the back-end databases. |
END_DT |
The date the logical query was completed. |
END_HOUR_MIN |
The hour and minute the logical query was completed. |
END_TS |
The date and time the logical query finished. The start and end timestamps also reflect any time that the query spent waiting for resources to become available. Note: If the user submitting the query navigates away from the page before the query finishes, then the final fetch never happens, and a timeout value of 3600 is recorded. However, if the user navigates back to the page before the timeout, then the fetch completes at that time, and this is recorded as the end_ts time. |
ERROR_TEXT |
Default is Null. Varchar(250) Error message from the back-end database. This column is only applicable if the |
ID |
The unique row ID. |
NODE_ID |
Concatenates <hostname>:<instance_name>:<component_name> where <instance_name>:<component_name> can be overridden by the environment variables INSTANCE_NAME and COMPONENT_NAME. For example, examplehost:instance1:coreapplication_obis1. Default value of INSTANCE_NAME is instance1, and default value of COMPONENT_NAME is coreapplication_obis1. |
NUM_CACHE_HITS |
Indicates the number of times that the cache result returned for the query. NUM_CACHE_HITS is a 32-bit integer (or a 10-digit integer). Default is Null. |
NUM_CACHE_INSERTED |
Indicates the number of times that the query generated a cache entry. Default is Null. NUM_CACHE_INSERTED is a 32-bit integer (or a 10-digit integer). |
NUM_DB_QUERY |
The number of queries that were submitted to back-end databases to satisfy the logical query request. For successful queries (SuccessFlag = 0) this number is 1 or greater. |
PRESENTATION_NAME |
Default is Null. Varchar(128) The name of the Oracle BI Presentation Catalog. |
QUERY_BLOB |
Contains the entire logical SQL statement without any truncation. The QUERY_BLOB column is a long character string. |
QUERY_KEY |
Default is Null. Varchar(128). An MD5 hash key that is generated by Oracle Business Intelligence from the logical SQL statement. |
QUERY_SRC_CD |
The source of the request. Values that can be inserted, for example: An analysis, or any export operation inserts 'Report'. Using the 'Value' drop down in a filter dialog, or using a dashboard prompt inserts 'ValuePrompt'. Agent to seed analytics server cache inserts 'Seed'. Online Admin Tool physical table or column row count, or view data inserts 'NULL'. |
QUERY_TEXT |
Varchar(1024). The SQL statement that was submitted for the query. You can change the length of this column (using the ALTER TABLE command), but note that the text that is written into this column is always truncated to the size that is defined in the physical layer. It is the responsibility of the repository administrator not to set the length of this column to a value greater than the maximum query length that is supported by the back-end physical database. For example, Oracle Databases enable a maximum Varchar of 4000, but Oracle Databases truncate to 4000 bytes, not 4000 characters. Hence, if you use a multibyte character set, the actual maximum string size has a varying number of characters, depending on the character set and characters used. |
REPOSITORY_NAME |
The name of the repository that the query accesses. |
ROW_COUNT |
The number of rows that are returned to the query client. Note: When a large amount of data is returned from a query, this column is not populated until the user displays all of the data. |
IMPERSONATOR_USER_NAME |
Default is None. Varchar(128). The user name of the impersonated user. If the request is not run as an impersonated user, then the value is 'None'. |
SAW_DASHBOARD |
The path name of the dashboard. If the query was not submitted through a dashboard, then the value is NULL. |
SAW_DASHBOARD_PG |
Default is Null. Varchar(150) The page name in the dashboard. If the request is not a dashboard request, then the value is NULL. |
SAW_SRC_PATH |
The path name in the Oracle BI Presentation Catalog for the analysis. |
START_DT |
The date that the logical query was submitted. |
START_HOUR_MIN |
The hour and minute that the logical query was submitted. |
START_TS |
The date and time that the logical query was submitted. |
SUBJECT_AREA_NAME |
The name of the business model that is being accessed. |
SUCCESS_FLG |
The completion status of the query, as defined in the following list:
|
TOTAL_TIME_SEC |
The time in seconds that the BI Server spent working on the query while the client waited for responses to its analyses. TOTAL_TIME_SEC includes the time for COMPILE_TIME_SEC. This setting is the same as the Response time in the nqquery.log file, as described in Section 8.4.1.1, "Setting the Query Logging Level." |
USER_NAME |
The name of the user who submitted the query. |
Table 9-2 describes the S_NQ_DB_ACCT
table, which supplements the usage tracking table by providing the physical SQL information for the logical queries stored in S_NQ_ACCT
. S_NQ_DB_ACCT
has a foreign key relationship back to S_NQ_ACCT
.
Table 9-2 Usage Tracking Data in S_NQ_DB_ACCT
Column | Description |
---|---|
END_DT |
The date the physical query was completed. |
END_HOUR_MIN |
The hour and minute the physical query was completed. |
END_TS |
The date and time the physical query finished. The start and end timestamps also reflect any time that the query spent waiting for resources to become available. |
ID |
The unique row ID. |
LOGICAL_QUERY_ID |
Varchar2(50). Refers to the logical query in the S_NQ_ACCT table. |
QUERY_BLOB |
Contains the entire physical SQL statement without any truncation. The QUERY_BLOB column is a long character string. |
QUERY_TEXT |
Varchar(1024). The SQL statement that was submitted for the query. |
ROW_COUNT |
The number of rows that are returned to the query client. |
TIME_SEC |
The physical query execution time. |
START_DT |
The date that the physical query was submitted. |
START_HOUR_MIN |
The hour and minute that the physical query was submitted. |
START_TS |
The date and time that the physical query was submitted. |
This chapter introduces system administration in Oracle Business Intelligence, explains what a system administrator does; describes where to get started with typical system administration tasks; describes the Oracle Business Intelligence architecture; lists the tools that can help you complete system administration tasks, and provides links to system requirements and certification information.
This chapter includes the following sections:
Section 1.1, "What Are the Oracle Business Intelligence System Administration Tasks?"
Section 1.2, "Getting Started with Managing Oracle Business Intelligence"
Section 1.3, "What Is the Oracle Business Intelligence System Logical Architecture?"
Section 1.4, "What System Administration Tools Manage Oracle Business Intelligence?"
Administering an Oracle Business Intelligence system involves the following tasks:
Configuring a system for deployment after installation
Configuring metadata and content, general preferences, and default system settings.
Starting and stopping the system when required
Bringing the system up and down during system maintenance tasks.
Configuring security
Securing access to the Oracle Business Intelligence system, metadata, and data, configuring Secure Sockets Layer (SSL) and Single Sign-On (SSO), and integration with identity management systems.
Scaling out and configuring for high availability
Configuring the Oracle Business Intelligence system for linear scale-out and identifying and removing single points of failure.
Managing performance and availability
Monitoring service levels and tuning performance.
Managing and resolving issues
Diagnosing errors and establishing resolutions.
Moving a system from test to production
Managing the steps for moving from a test to a production environment.
Backing up and recovering data
Preparing for and recovering from unexpected events.
For more information about these tasks, see Section 1.2, "Getting Started with Managing Oracle Business Intelligence."
Use this section to identify a task to complete, then click the corresponding link to display the appropriate content.
Table 1-1 describes the typical system administration tasks that you perform in Oracle Business Intelligence and indicates where to find related information.
Table 1-1 Oracle Business Intelligence System Administration Tasks
System Administration Task | More Information |
---|---|
Learning about Oracle Business Intelligence system administration |
For more information, see the topics in this section. Contains information about the system architecture, components, tools, links to other related topics, and certification information. |
Viewing Oracle Business Intelligence status |
Also contains information about using Fusion Middleware Control and using WebLogic Server Administration Console. |
Configuring Oracle Business Intelligence |
Chapter 3, "Configuring the Oracle Business Intelligence System" Contains information about the available methods for updating configuration settings and where configuration files are located. |
Starting and stopping Oracle Business Intelligence |
Chapter 4, "Starting and Stopping Oracle Business Intelligence" Contains various topics on starting and stopping components, in addition to troubleshooting information. |
Managing availability and capacity |
Part III, "Scaling and Deploying for High Availability and Performance" Contains chapters about scaling the environment, deploying for high availability, performance tuning, and query caching. |
Diagnosing problems and resolving issues |
Contains chapters about diagnosing and resolving issues and about usage tracking. |
Configuring Oracle Business Intelligence |
Part V, "Configuring Oracle Business Intelligence" Contains chapters about required configuration such as configuring repositories and connections to external systems. |
Modifying advanced configuration settings |
Part VI, "Advanced Configuration Settings" Contains chapters about advanced and optional configuration settings for features such as analyses, dashboards, and maps. |
Configuring Oracle BI Scheduler |
For more information, see Oracle Fusion Middleware Scheduling Jobs Guide for Oracle Business Intelligence Enterprise Edition |
Automating management of an Oracle Business Intelligence system |
Part VII, "Automating Management of Oracle Business Intelligence" Describes the Oracle BI Systems Management API. |
Managing the life cycle. |
Part VIII, "Managing the Life Cycle" Contains chapters about life cycle management tasks such as patching, moving between environments, and backup and recovery. |
Using Essbase with Oracle Business Intelligence |
Part IX, "Using Oracle Essbase With Oracle Business Intelligence" Contains a chapter about using Essbase when it is installed with Oracle Business Intelligence. |
Securing the system |
|
The Oracle Business Intelligence system logical architecture comprises a single integrated set of manageable components called the Oracle BI domain which can be installed and configured to work together on a single host or can be clustered across multiple hosts for performance and availability.
Note: You can improve the performance of your production system by using a web server with Oracle Business Intelligence, such as Oracle HTTP Server or Apache HTTP Server. A web server is not included by default in the Oracle Business Intelligence installer and is not part of the Oracle Business Intelligence system logical architecture. You must install and configure a web server separately. |
You can install Oracle Business Intelligence on a single host using either an Enterprise Install type or a Simple Install type. The architecture differs slightly depending on install type, as described in the following sections.
See "Installation Types" in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence for more information.
In an Enterprise Install type, the following components are installed in the Oracle BI Domain on the single host. The BI Domain consists of Java components that are deployed into one or more Java EE (JEE) containers within a single WebLogic server domain; system (non-JEE) components and processes; and required configuration files, metadata repositories, and infrastructure.
Java Components — Deployed as JEE applications to service SOAP, HTTP, and other forms of requests.
For more information, see Section 1.3.3, "About Java Components and System Components for Oracle Business Intelligence."
Administration Server — Deployed as a JEE container that runs in a dedicated Java virtual machine that contains Java components for administering the system. These components include Oracle WebLogic Server Administration Console, Oracle Fusion Middleware Control, and JMX MBeans.
For more information, see Section 1.3.4, "What Is the Administration Server?"
Managed Server — Deployed as a JEE container that runs in a dedicated Java virtual machine that provides the runtime environment for the Java-based services and applications within the system. These services and applications include BI Publisher and Oracle Real-Time Decisions.
An Oracle BI domain contains one or more Managed Servers that are distributed across one or more host computers.
Node Manager — Provides process management services for the Administration Server and Managed Server processes.
For more information, see Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server.
System Components — Deployed as server processes and provide the core services that enable Oracle Business Intelligence, including OPMN. OPMN (Oracle Process Manager and Notification server) maintains the Oracle Business Intelligence system component processes.
For more information, see Section 1.3.3, "About Java Components and System Components for Oracle Business Intelligence." For more information about OPMN, see Section 1.4.3, "Oracle Process Manager and Notification Server (OPMN) Tool."
Other Domain Contents — Includes all the necessary software, metadata, configuration files, RPD files, Oracle BI Presentation Catalog, and connection and database configuration information that are required to run an Oracle Business Intelligence system.
Figure 1-1 illustrates the Oracle Business Intelligence system architecture on a single host for an Enterprise Install type.
The architecture for the Simple Install type is similar to that of the Enterprise Install type, with the differences that are outlined in the following list:
The Node Manager is not installed.
All components that are part of the Managed Server in an Enterprise Install type are instead part of the Administration Server. The Managed Server is not installed.
Figure 1-2 illustrates the Oracle Business Intelligence system architecture on a single host for a Simple Install type.
If you perform an Enterprise Installation, then Oracle Business Intelligence can be installed and configured on multiple hosts. Figure 1-3 illustrates the system architecture on two hosts.
In Figure 1-3, the Java components (WebLogic server domain) and the system components (BI instance) are clustered on each host as part of the single BI domain. The Administration Server exists on both hosts, but is only active on one host (in this example, Host 1).
The Oracle Business Intelligence Java and system components are described in the following sections:
For more information, see Oracle Fusion Middleware Administrator's Guide.
For information about the Essbase components installed with Oracle Business Intelligence, see Section 27.4.1, "Installing Essbase and Associated Components in a New Installation of Oracle Business Intelligence".
Java components are deployed as one or more Java EE applications and are described in the following list:
Administrative Components — Oracle WebLogic Server Administration Console, Fusion Middleware Control, and JMX MBeans for managing all configuration and runtime settings for Oracle Business Intelligence.
Oracle BI Publisher — This component provides an enterprise reporting solution for authoring, managing, and delivering all types of highly formatted documents to employees, customers, and suppliers.
Oracle BI for Microsoft Office — This component provides the integration between Oracle Business Intelligence and Microsoft Office products.
Oracle BI Action Services — This component provides the dedicated web services that are required by the Action Framework and that enable an administrator to manually configure which web service directories can be browsed by users when they create actions.
Oracle BI Composer — This component provides a simple-to-use wizard that enables you to quickly and easily create, edit, or view analyses without the complexities of the Analysis editor.
Oracle Real-Time Decisions (Oracle RTD) — This component provides enterprise analytics software solutions that enable companies to make better decisions in real time at key, high-value points in operational business processes.
Oracle BI Security Services — This component provides dedicated web services that enable the integration of the Oracle BI Server with the Oracle Fusion Middleware security platform.
Oracle BI SOA Services — This component provides dedicated web services for objects in the Oracle BI Presentation Catalog, to invoke analyses, agents, and conditions. These services make it easy to invoke Oracle Business Intelligence functionality from Business Process Execution Language (BPEL) processes.
Oracle BI Presentation Services Plug-in — This component is a JEE application that routes HTTP and SOAP requests to Oracle BI Presentation Services.
System components are deployed as non-JEE components, such as processes and services written in C++ and J2SE, and are described in the following list:
Oracle BI Server — This component provides the query and data access capabilities at the heart of Oracle Business Intelligence and provides services for accessing and managing the enterprise semantic model (stored in a file with an .RPD extension).
Oracle BI Presentation Services — This component provides the framework and interface for the presentation of business intelligence data to web clients. It maintains an Oracle BI Presentation Catalog service on the file system for the customization of this presentation framework.
Oracle BI Scheduler — This component provides extensible scheduling for analyses to be delivered to users at specified times. (Oracle BI Publisher has its own scheduler.)
Oracle BI JavaHost — This component provides component services that enable Oracle BI Presentation Services to support various components such as Java tasks for Oracle BI Scheduler, Oracle BI Publisher, and graph generation. It also enables Oracle BI Server query access to Hyperion Financial Management and Oracle OLAP data sources.
Oracle BI Cluster Controller — This component distributes requests to the BI Server, ensuring requests are evenly load-balanced across all BI Server process instances in the BI domain.
The Administration Server contains the administrative components that enable administration of a single or multinode (that is, distributed) BI domain, as described in the following list:
For Enterprise and Simple Install types, the Administration Server contains the following components:
JMX MBeans — Java components that provide programmatic access for managing a BI domain.
Fusion Middleware Control — An administrative user interface that is used to manage the BI domain.
WebLogic Server Administration Console — An administrative user interface that provides advanced management for WebLogic, JEE components, and security.
For Simple Install types, the Administration Server also contains the components that comprise the Managed Server in an Enterprise Install type, such as Action Services and Oracle BI Publisher.
The following sections describe system administration tools that are available to help you to manage Oracle Business Intelligence. Table 1-2 outlines the tools and their purpose.
Table 1-2 System Administration Tools for Oracle Business Intelligence
Section | Tool | Purpose |
---|---|---|
|
Fusion Middleware Control |
Monitor, manage, and configure system components for Oracle Business Intelligence. |
|
Oracle WebLogic Server Administration Console |
Monitor and manage JEE Java components for Oracle Business Intelligence. |
|
Oracle Process Manager and Notification Server (OPMN) |
Manage system components for Oracle Business Intelligence (for advanced users). |
|
Oracle WebLogic Scripting Tool (WLST) |
Programmatically administer Oracle Business Intelligence. |
|
Oracle BI Administration Tool |
Manage the metadata repository for Oracle Business Intelligence. |
|
Job Manager |
Manage the Oracle BI Scheduler |
Fusion Middleware Control is a browser-based tool and the recommended method for monitoring, managing, and configuring Oracle Business Intelligence components.
Fusion Middleware Control is used principally for managing the system components of a BI domain and provides support for the following:
Starting, stopping, and restarting all system components and Managed Servers
Configuring preferences and defaults
Scaling out of system components
Providing high availability configuration and status of system components
Managing performance and monitoring system metrics
Performing diagnostics and logging
Fusion Middleware Control also provides access to Oracle WebLogic Server Administration Console, where you monitor and manage Oracle Business Intelligence Java components.
Fusion Middleware Control is available only if the Administration Server is running, as described in Section 4.2, "Starting the Oracle Business Intelligence System."
For more information, see Chapter 2, "Managing Oracle Business Intelligence."
Oracle WebLogic Server is a Java EE application server that supports the deployment of Oracle Business Intelligence Java components in a robust, secure, highly available, and scalable environment.
For more information, see Chapter 2, "Managing Oracle Business Intelligence."
Oracle WebLogic Server Administration Console enables you to monitor and manage a WebLogic Server domain. Its capabilities include the following:
Monitoring the health and performance of JEE servers
Configuring WebLogic server domains
Stopping and starting JEE servers
Viewing JEE server logs
Managing user populations in the LDAP Server of the Oracle WebLogic Server
For more information, see Oracle Technology Network at the following location:
OPMN is a process management tool that manages the Oracle Business Intelligence system components. OPMN supports both local and distributed process management, automatic process recycling, and the communication of process state (up, down, starting, and stopping). OPMN detects process unavailability and automatically restarts processes).
Note: Fusion Middleware Control is the recommended approach for starting, stopping, and viewing the status of components. However, following a restart on Linux you must use the opmnctl start, or startall command. OPMN is suitable only for advanced users. |
OPMN provides the following functionality to manage the Oracle Business Intelligence system components:
A command-line interface for advanced users to control Oracle Fusion Middleware components.
For information, see Section 4.5, "Alternative Methods for Starting and Stopping System Components."
Automatic restart of processes when they become unresponsive or terminate unexpectedly.
An integrated way to manage Oracle Fusion Middleware components.
The Oracle WebLogic Scripting Tool (WLST) is a command-line scripting environment (for advanced administrator use), which enables you to programmatically administer Oracle Business Intelligence. The WLST scripting environment is based on the Java scripting interpreter Jython. You can use this tool interactively on the command line, in batch scripts that are supplied in a file (Script Mode, where scripts invoke a sequence of WLST commands without requiring your input), or embedded in Java code. You can extend the WebLogic scripting language by following the Jython language syntax.
For more information, see:
The Oracle BI Administration Tool enables you to manage the metadata repository. For information, see Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.
The Job Manager is a Windows tool that is the interface with the Oracle BI Scheduler. Through Job Manager, you can connect to, start and stop the Oracle BI Scheduler, add and manage jobs, and manage job instances. For information, see Oracle Fusion Middleware Scheduling Jobs Guide for Oracle Business Intelligence Enterprise Edition.
By default, Oracle Business Intelligence is configured with a simplified "Sample Application." This application is often referred to as "SampleApp Lite."
You can also download and configure a more robust sample application. Instructions for this configuration are available at the following location:
http://www.oracle.com/technetwork/middleware/bi-foundation/obiee-samples-167534.html
See "About the SampleApp.rpd Demonstration Repository" in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition for information about the sample repository that is provided with Oracle Business Intelligence.
This guide assumes that Oracle BI EE and BI Publisher have been installed and configured to run as fully integrated components at your organization. If this is not the case, then some mentions of BI Publisher in this guide might not be applicable to you. For information about running BI Publisher, see Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Publisher.
Some topics that might be of interest to system administrators are covered in other guides. Table 1-3 lists these topics and indicates where to go for more information.
Table 1-3 Topics Covered in Other Guides
Topic | Where to Go for More Information |
---|---|
Section 1.8, "System Requirements and Certification" | |
Oracle Fusion Middleware Scheduling Jobs Guide for Oracle Business Intelligence Enterprise Edition | |
| |
Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition | |
Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence | |
Configuring comments and status overrides in Oracle Scorecard and Strategy Management |
|
Converting Oracle Business Intelligence proprietary metadata to an XML file and importing the metadata into your Oracle or IBM DB2 database |
|
Propagating UI hints (labels and tooltips) from an ADF data source to display in Oracle BI Answers |
|
Using IBM WebSphere as the application server |
Oracle Fusion Middleware Third-Party Application Server Guide |
Refer to the system requirements and certification documentation for information about hardware and software requirements, platforms, databases, and other information. Both of these documents are available on Oracle Technology Network (OTN).
The system requirements document covers information such as hardware and software requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-requirements-100147.html
The certification document covers supported installation types, platforms, operating systems, databases, JDKs, and third-party products:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html