This chapter includes the following sections:
You can use Fusion Middleware Control and WebLogic Server Administration Console to manage the Oracle Business Intelligence system.
These Web-based tools support the most common system administration tasks for Oracle Business Intelligence. See Getting Started with Managing Oracle Business Intelligence.
Fusion Middleware Control enables you to manage system components by performing tasks such as monitoring status, starting and stopping processes, resolving issues, and configuring components. You can also manage some aspects of Java components. For example, you can monitor their status and start and stop them.
WebLogic Server Administration Console enables you to monitor status and configure security for Java components. See Introduction to Oracle Business Intelligence System Administration.
Locking Mechanism Enables Multiple Concurrent Administrators
With large deployments, you might have multiple administrators accessing the system concurrently to view the state of the system while other administrators might want to make configuration changes. Fusion Middleware Control and Oracle WebLogic Server prevent concurrent updates of the same configuration settings by multiple administrators by using a locking mechanism that enables only one administrator to make changes at any one time.
Note:
Multiple administrators using the same administrator account could unknowingly make concurrent updates of the same configuration settings. It is therefore recommended that multiple administrator users do not share the same administrator account.You can use Fusion Middleware Control to manage, monitor, and configure Oracle Business Intelligence system components (for example, the Oracle BI Server, Oracle BI Presentation Services, and Oracle BI Scheduler). You can also use Fusion Middleware Control to manage the Administration Server and Managed Servers.
This section contains the following topics:
To log in to Fusion Middleware Control, open a web browser and enter the Fusion Middleware Control URL.
Enter the URL in the following format:
http://hostname.domain:port/em
The port number is the number of the Administration Server, and the default port number is 9500.
Fusion Middleware Control is available only if the Administration Server is running, as described in Conditions for Starting the Oracle Business Intelligence System.
Note:
If you have the browser configured to send HTTP requests to a proxy server, then you might have to configure the browser to not send Administration Server HTTP requests to the proxy server. If the Administration Server is on the same computer as the browser, then ensure that requests that are sent to localhost or 127.0.0.1 are not sent to the proxy server.
Use this topic to display Oracle Business Intelligence pages that enable you to manage Oracle Business Intelligence system components.
The navigation tree enables you to navigate and select nodes within the BI domain that can be managed by Fusion Middleware Control.
Depending on the choices made during installation, the following domain components can be displayed as nodes in the navigation tree:
Application Deployments
The Application Deployments node shows all the applications that are deployed into the BI domain (for example, analytics, Oracle Business Intelligence for Microsoft Office, Oracle BI Publisher).
WebLogic Domain
These nodes display summary information for the WebLogic server. Select a node and click the Oracle WebLogic Server Administration Console menu option to display the WebLogic Server Administration Console, where you can administer Oracle WebLogic Server.
bidomain
This node represents the WebLogic server domain for Oracle Business Intelligence with an AdminServer node that contains the Administration Server and a bi_cluster node that contains Managed Servers (a single node cluster by default, for example, bi_server1). See About the Administration Server, Managed Servers, and System Components.
AdminServer
bi_cluster
Business Intelligence
biinstance
This node represents the Oracle Business Intelligence system components that can be managed using Fusion Middleware Control.
Select this node to display the Overview page and manage the system components.
Metadata Repositories
This node represents the Metadata Services (MDS) schema repositories that can be managed using Fusion Middleware Control.
There are several considerations to keep in mind when using Fusion Middleware Control with Oracle Business Intelligence.
Keep the following tips in mind as you use Fusion Middleware Control to manage Oracle Business Intelligence:
See Getting Started Managing Oracle Fusion Middleware in Administering Oracle Fusion Middleware.
You might want to have a user who can view information about Oracle Business Intelligence within Fusion Middleware Control but not make any changes. You can configure such a user by making him a member of the Monitors group. See Securing Resources Using Roles and Policies for Oracle WebLogic Server .
You might encounter display problems when using Internet Explorer 8 with Fusion Middleware Control. For example, scroll bars might be missing on the Log Messages tab of the Diagnostics page, even when the bars are required to see all the text.
To work around this issue, ensure that Compatibility View mode is turned off for the browser.
From the Tools menu, select Internet Options. On the Advanced tab in the Browsing section, ensure that Automatically recover from page layout errors with Compatibility View is not checked.
From the Tools menu, select Compatibility View Settings. Ensure that Display intranet sites in Compatibility View and Display all websites in Compatibility View are not checked.
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. |
Fusion Middleware Control See Using Fusion Middleware Control. Oracle recommends that you use this method. However, if a setting is not available, you can use a text editor. |
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. |
Text editor See Using a Text Editor. Oracle recommends that you use this method when a setting is not available in Fusion Middleware Control Oracle Business Intelligence pages. |
Change values in a configuration text file using a text editor. |
Make more complex configuration changes using a scripting tool. |
WebLogic Scripting Tool (WLST) See Using the WebLogic Scripting Tool (WLST). Oracle recommends that you use this method when instructed by the documentation. |
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.
You use the Oracle WebLogic Server Administration Console to manage Oracle Business Intelligence Java components.
You display Oracle WebLogic Server Administration Console, using the following methods:
Clicking a link on the WebLogic Domain menu in Fusion Middleware Control
Entering a URL into a web browser window
The Oracle WebLogic Server Administration Console is available only if the Administration Server for WebLogic Server is running. See About Managing Oracle Business Intelligence Processes.
If the Administration Server for WebLogic Server is not running, start it.
Display the Oracle WebLogic Server Administration Console using the following methods:
Clicking a link on the Overview page in Fusion Middleware Control:
Display Fusion Middleware Control.
Click the Oracle WebLogic Server Administration Console link in the WebLogic Domain menu.
The Oracle WebLogic Server Administration Console login page is displayed.
Using a URL in a web browser window:
Start a web browser.
Enter the following URL into the browser:
http://<hostname>:<port>/console/
For example, http://example.com:9500/console/
where hostname
is the DNS name or IP address of the Administration Server and port
is the listen port on which the Administration Server is listening for requests (port 9500 by default). If you have configured a domain-wide Administration port, then use that port number. If you configured the Administration Server to use Secure Sockets Layer (SSL), then you must add the letter 's' after http as follows:
https://<hostname>:9500/console/
The preceding URL example uses SSL.
The Oracle WebLogic Server Administration Console login page is displayed.
Enter the system administrator user name and password and click Login.
This systemwide administration user name and password was specified during the installation process, and you can use it to log in to WebLogic Server Administration Console, Fusion Middleware Control, and Oracle Business Intelligence. Alternatively, enter a user name that belongs to one of the following security groups:
Administrators
Operators
Deployers
Monitors
These groups provide various levels of access to system administration functions in the Oracle WebLogic Server Administration Console.
Using the security system, you can add to or delete users from one of these groups to provide controlled access to the Console.
If you have the browser configured to send HTTP requests to a proxy server, then you might have to configure the browser to not send Administration Server HTTP requests to the proxy. If the Administration Server is on the same computer as the browser, then ensure that requests sent to localhost or 127.0.0.1 are not sent to the proxy.
In Oracle WebLogic Server Administration Console you select the bi domain, as shown in the figure below.
You can monitor and manage Oracle Business Intelligence Java components from this page.
Note:
For more information on using the Oracle WebLogic Server Administration Console, see the Oracle WebLogic Server Administration Console Online Help system. That Help system describes how to use the console to override the context root for a deployed web application. Changing any context root for Oracle Business Intelligence is not supported, because many context roots are used for internal links and end-user end points.