If any of the prerequisite checks fail, then an error message appears in the bottom portion of the screen. Fix the error and click Retry to try again. If you want to ignore the error or warning messages and continue with the installation, click Continue. Click Abort to stop prerequisite checking for all components.
If you do not know the location of the directory, click Browse to locate the directory on your system. Do not specify any other Oracle home or choose to create a new one. In the Summary screen, review the summary information, and click Next to start the installation. You must apply Fusion Middleware platform patches. The patches are available for download as part of the Oracle Business Intelligence Applications You will run a script to apply the patches.
For installations on Windows, the perl script uses the WinZip utility to extract the contents of the individual patches. If WinZip is not installed on the machine, then you must use install 7-zip and update the script to use it as follows:.
In this procedure, before you run the Perl script, you will update the parameter input file to reflect the appropriate directory paths.
Download the following three parts from the Oracle Business Intelligence Applications You do not have to unzip the individual patches. Create a writable directory where logs and temporary patch files will be stored. Note: This script can be run from any location if Perl is set in the path variable. If Perl is not set in the path variable, run the script from the following location:.
Confirm that all patches have been applied successfully by reviewing the following log files in the directory specified by WORDIR:. Therefore, if you have WebLogic Server Also, the final patching report will show the WebLogic Server patches have failed. You can ignore the WebLogic Server patch failures. You configure the BI Domain by running the config. The BI Domain was configured as part of Section 3.
For information about the options in this screen, see Section A. You run the configApps. To configure components by running the configApps. On the Prerequisite Checks screen, after the prerequisite checks conclude with no errors, click Next. If an error message appears, fix the error and then click Retry to run the prerequisite check again recommended. Repeat this until all prerequisite checks conclude with no errors.
To stop the configuration process while you fix a prerequisite error, click Abort. To ignore an error or warning message, and continue with the configuration process, click Continue not recommended.
The configuration might not function normally if you continue without resolving the issue that caused an error or warning message during the prerequisite checks. The host name of the computer on which the WebLogic Server domain exists. This field is read-only. The value in this field is read-only and is the host name you specified in the Middleware Home field. The home directory for the domain associated with the Oracle Business Intelligence system.
The value in this field is read-only. The installer installs component configuration files and runtime processes in the Oracle Instance directory. Runtime components write to this directory only. The directory that you identify for the Oracle Instance can be located anywhere on your system, and does not need to be inside the Oracle Middleware Home.
The name of the Oracle Business Intelligence instance. By default, the location is based on the value in the Instance Home field. Note : Do not select the Indirect Spend Planning option.
This option is not supported. Note : Do not enter "Administrator," "Admin," "Sadmin," or "Supervisor" in upper case, lower case, or mixed case letters. These user names are reserved. Also, do not use the WebLogic Server administrator user name. Note these credentials because this user will be used to perform system setups and is the user that is used for communications between the Oracle BI Applications Configuration Manager and ODI.
The only supported database type is Oracle. Specify the type of database that hosts the Business Analytics Warehouse schema. Specify the type of database that hosts the ODI Repository schema. Specify the schema name for the ODI Repository schema. Select this option if you want Oracle Business Analytics Applications Suite installer to configure the ports for you. Select this option to use a configuration file to configure the ports.
Optionally, click Browse to specify a configuration file location. A sample configuration file named staticport. You can edit this file to specify the configuration settings for your environment.
On the Summary screen, click Save to save the settings for this configuration in a response file optional , and then click Configure to start the configuration process. On the Configuration Progress screen, you can monitor the progress of the software configuration and respond to errors, if any occur.
If a configuration task fails, an error message appears. To retry the task, click Retry. To continue with the next task, click Continue not recommended. To stop the installation and configuration process entirely, click Abort. On the Complete screen, click Save to save the settings for this installation in a response file optional , and then click Finish to exit the Oracle Business Intelligence Configuration Assistant.
You must now upgrade to WebLogic Server For instructions on downloading the Upgrade Installer and upgrading to WebLogic ODI Studio must be configured to use the appropriate security files for authentication. You must perform these steps on all installations of ODI Studio. Make sure that the odi.
System administrators must provide the ZIP file to developers as needed. The patches are available in the directory in which you extracted the Fusion Middleware Patches in step Section 3. Note : This sub-step is part of Section 3.
Set the environment to execute SQLPlus from this client installation. For Windows installations, the script required for this process is not currently available.
Without the application of the seed data updates, BI Applications Configuration Manager and Functional Setup Manager continue to function without loss of functionality. For example:. Execute the post script using the following command.
You must specify the arguments in the same order as they appear:. System administrators must provide this patch to developers who have installed ODI Studio on their machines. Select "Install a new instance". Select "Modify an existing instance". These files are used during the ETL process and will be configured by functional developers. You must perform the system setups in this section to complete integration of the Oracle BI Applications components and to ready the system for functional configurations and data loads.
In the Definition pane, for the Directory Schema and Directory Work Schema properties, specify the directory where you copied source files to in Section 3. Note : This user was created during the Section 3. This is the name given by the BI Applications System Administrator to a transactional system that serves as a source of data for BI Applications data load.
The source instance is important because functional setup tasks, and the setting of values for objects such as parameters and domain maps are performed in relation to a source instance.
Each source instance must have a unique Data Source Number. For PeopleSoft Enterprise sources only. In the Data Server Details window, select the appropriate data server for the source instance. Click Next. The Global value is required because the Oracle BI Applications interfaces are designed to use this value. Specify a name for the transactional OLTP database source database. Specify a name for the file system data server.
Specify the directory where you copied the source files in Section 3. The directory path must include the appropriate source-specific folder for your environment. Note: This column may be hidden. To view this column, click View , Columns , Show All. The setup data relating to offerings is made visible in Configuration Manager when you enable the offering.
By default, if you have multiple source instances and you enable an offering, the offering is enabled for all source instances. If an offering will not source from all source instances, then you can disable the source instances from which the offering will not source. Enabling an offering makes the setup data associated with that offering available in Configuration Manager. Oracle Business Intelligence is installed with a set of preferred currencies with pre-configured preferred currency names and preferred currency codes.
You can use the Manage Preferred Currencies dialog to edit the default currency display names. You edit preferred currency name values to change the currency labels that are displayed in all modules associated with BI dashboards. You must enable the languages that you want to deploy. You can also specify a Base Language. For example, if French is an enabled language and American English is the Base Language, there will be two rows, one for each language.
If French values are not available, then American English values will be substituted. Manage Business Analytics Warehouse Languages. Use this list to view the available languages, and enable the languages that you want to support. Use the Installed column to change the default value of 'Disabled' to 'Installed', which enables the selected language. The other table columns display read-only data. Use this option to specify the Base Language, which is marked with a blue dot.
You can only specify one Base Language. American English is the default Base Language. To select a different Base Language, select a record in the table, then click the Set Base Language icon. If the current Base Language record is selected, then this icon is grayed out. While there are other configurations that could be done at this time, we've completed the minimum configurations required to move to the next phase, which is to generate and execute a Domain Load Plan.
Load plans are the steps that execute a data load and are similar to execution plans in earlier, DAC-based versions of the BI Applications. The difference is that BI Applications This potentially reduces the amount of step pruning you need to do after the fact. There are also different types of load plans.
The Domain-Only Load Plan will run some targeted data extractions from the source system to assist with configurations for specific applications.
This stands in contrast to a Source Extract And Load Plan , which focuses on loading the facts and dimensions in the warehouse. In the next step you will build your first load plan, in this instance a domain load plan to extract data from the source system to support loading the Inventory Transactions fact table group within the Supply Chain and Order Management offering.
Then, when the Manage Load Plans page opens, click the green plus symbol to add a new load plan, and enter the following details to define the new domain load plan:.
This will create a custom load plan in ODI that is a subset of the master load plan based on the load plan type and fact groups we selected. This process will take a few minutes and can be monitored by clicking the blue circular arrows refresh symbol.
Once the generation is complete, as indicated in the Generation Status column by a green checkmark next to the black circular arrows symbol, you may proceed to the next step, which is actually executing the load plan. To execute the load plan, click the Execute button, signified by a green play button symbol in a white box, and select the following values when the Execute Load Plan dialog is shown:. This process will take several minutes depending on your system and can be monitored by clicking the blue circular arrows refresh symbol.
Once the execution is complete, as indicated in the Execution Status column by a large white checkmark in a green circle symbol, you may proceed to the next step. Functional Setup Manager operates much like Configuration Manager does for ODI: a faster, simpler way to get to the configuration you need to make. More often than not, Functional Setup Manager opens a window to a specific parameter screen in Configuration Manager that is required for a particular offering you are implementing.
Rather than hunt and peck through the many parameters in Configuration Manager, Functional Setup Manager notifies you that a parameter is important and takes you to the right place in Configuration Manager to configure it.
So really, it's a helper application to make sure you know exactly what you need to do, and that's an important distinction, because you technically don't have to use it if you know what you're doing.
So let's walk through the basics of Functional Setup Manager so you can see how it works. The first step, again performed through your Web browser, is to jump to Functional Setup Manager through Configuration Manager.
Then, click Configure Offerings ; here we will enable our licensed offering for implementation. Then, click Save and Close. Next we're going to create an implementation project for our enabled offering.
Or else it will fail Configuring ODI. Upgrade to Oracle weblogic server ODI Execute configApps. Or else it implicitly Call Config. Oracle Database All the Fusion Products need to be installed onto same Middleware Home.
You must perform the following procedures in the order as they appear…. Install JDK 1. Required to apply patches using Perl script. Install ODI Note: Avoid copying the files to a location with a long directory path.
0コメント