You configure the Oracle Business Intelligence system settings by changing values stored in domain-specific locations related to either functional behavior (for example, cache, thresholds), or environmental settings (for example, host names, ports, files or metadata locations).
You can use the following methods:
The table below shows which method to use when configuring Oracle Business Intelligence system settings. Each method updates settings in specific configuration files.
What Do You Want to Do? | What Methods Can You Use? | How Are Updates Made? |
---|---|---|
Change common configuration settings in an easy to use user interface. |
|
Change values in specific Oracle Business Intelligence configuration pages in Fusion Middleware Control. For example, to enable the BI Server cache, you click the Cache Enabled check box (select/clear) in the Performance tab of the Configuration page. |
Change configuration settings by manually editing a file. |
|
Change values in a configuration text file using a text editor. |
Make more complex configuration changes using a scripting tool. |
|
Make configuration changes by running commands using the WLST scripting tool. |
You can use Fusion Middleware Control to update specific Oracle Business Intelligence configuration settings.
Configuration settings you can change include performance settings, dashboard and analysis default presentation settings, and mail server settings used by agents.
If an Oracle Business Intelligence configuration setting is not available in Fusion Middleware Control, you can use a text editor to update the setting in a configuration file. See Configuring Oracle Business Intelligence System Settings.
You can use a text editor to add or change a setting in a configuration file.
You would use text editor for the system configuration settings that are not available in Fusion Middleware Control.
Use the following procedure to update configuration files using a text editor.
Oracle provides WebLogic Scripting Tool (WLST) scripts to perform Oracle Business Intelligence WebLogic configuration tasks. For example, to create a domain during installation, or to add a machine for high availability.
You run WLST scripts commands from the following location:
ORACLE_HOME/oracle_common/common/bin/wlst.sh (wlst.cmd on Windows)
You can configure Oracle Business Intelligence system settings in online (system processes running) or offline (system processes stopped) mode. The following sections describe the different conditions that apply when making online and offline configuration changes.
All offline configuration changes must be made on the master host, except those relating to node managers, and all Oracle BI EE processes must be stopped first.
To consume offline changes you must start the Administration server, Managed servers, and then system components (in that order). This is the general requirement for any configuration change as the command to start the managed server is the only process that replicates the configuration, from a running Administration Server.
Assumptions and pre-requisites:
You must have file system (offline) or Weblogic Administrator (online) permissions
When you start component(s) offline, the Administration server and node managers must be started first, see Starting Oracle Business Intelligence Component Processes in a Domain
Running WLST Offline
You run WLST scripts commands from the following location:
ORACLE_HOME/oracle_common/common/bin/wlst.sh
Before issuing offline commands you must select a domain using the readDomain(DOMAIN_HOME) command.
For example:
readDomain('/u01/bi')
After you have issued your offline commands you must commit the changes using the updateDomain() command.
For example:
updateDomain('/u01/bi')
De-select the domain using the closeDomain() command.
For example:
closeDomain('/u01/bi')
If you make a mistake or decide to abandon changes, you should use the closeDomain() command without using the updateDomain() command.
You can make online configuration changes from any computer where you have access to the Administration Server domain mbeans.
Assumptions and pre-requisites:
You must have Weblogic Administrator permissions.
The Administration Server must be running.
After making changes, you must restart the affected BI component(s), see Starting Oracle Business Intelligence Component Processes in a Domain.
Running WLST Online
You run WLST script commands from the following location:
ORACLE_HOME/oracle_common/common/bin/wlst.sh
Connect to Administration Server by issuing the following command:
./wlst.sh connect(<username>, <password>, <connect string>)
For example,
./wlst.sh connect('weblogic', 'mypassword', 't3://localhost:9500')
You must enter edit tree and start an edit session by issuing edit() and startEdit() commands before issuing commands.
Use the save() command to save all changes made during the edit session.
Use the activate() command to commit your changes.
If you attempt to issue a command outside an edit session, the command will fail and display a help message.
If you make a mistake or decide to abandon changes then you must use the undo() or cancelEdit() command.
After you install and configure Oracle Business Intelligence, you might need to update the JDK for the instance; for example, if an update is required per the policy of your organization.
Before deciding to update the JDK, ensure that you consider an appropriate version, as described in the system requirements and certification documentation. See System Requirements and Certification.
For information on installing with a specific JDK, see Installing and Configuring Oracle Business Intelligence.