Likewise, the concurrent processing out files for all products will be stored in a single common out file directory under the APPLCSF directory. This is the default value. Additionally, a directory named system will be created under the APPLCSF directory, and the log files and out files for the Internal Concurrent Manager will be stored in corresponding directories under the system directory.
Instead, the role is determined by the services that you set as enabled. These services specify the set of processes that will be started on each application tier node, and consequently the functions the node will perform.
In other words, there is no concept of a "Forms node", "Web node", and so on, as there is no direct association between installed files and the services that can be run on that machine.
This model enforces the three-tier architecture and simplifies tasks such as patching and upgrading. However, the Web Administration service group is an important exception, which can only be enabled on a single application tier node and must be enabled on one node. Currently, the following additional instructions apply to installing and activating application tier services: 1.
Be aware that when subsequently creating secondary managed nodes, Rapid Install will not run adstrtall. This failure of the post-install checks is expected. Application tier nodes have all services enabled by default, but you can customize the services enabled on a particular node.
Specify Web Entry Points In some specialized configurations, described below, you may need to set certain context variables according to your node deployment. Conditional Action: You will only need to perform these steps if your configuration falls into one of the categories mentioned. For example, installations that have multiple concurrent processing nodes or simply multiple web entry points may need to have the web entry point variables set to different values.
Similarly, when adding a new node to a group of existing nodes, the new node may need to use the existing web entry point or a new web entry point for example, in a DMZ configuration, when using load balancing; or when using a reverse proxy.
In such cases, the web entry point variables must be set in each application context file to point to the correct web entry point, which will typically be the URL used to access the application. The password specified here will also be used for the sys account.
The checkbox to change the default passwords for these accounts is automatically checked when this screen appears. Action: For improved security of your new system, Oracle recommends accepting this setting and changing the default passwords the new passwords must contain alphanumeric characters only. If you wish to retain the default passwords and not change them as recommended, you will need to uncheck the box. Conditional Action: If you wish to run Rapid Install in silent mode, for example to avoid having to provide user responses during an upgrade, you must retain the default passwords including the WLS Admin password.
This is because passwords cannot be passed on the command line in silent mode. At this stage, you have specified details for the database node and the primary application tier node. Rapid Install is no longer used to create multiple Application nodes. Waiting until after installation to add application tier nodes is a time-saving measure for the installation and patching process.
After you complete the Rapid Install run you will: 1. Add application tier nodes by cloning or creating a shared application tier file system. Additional Resources: When following this strategy of adding application tier nodes by cloning the primary application tier node, refer to My Oracle Support Knowledge Documents Rapid Install performs a series of system tests to validate the configuration specified.
The System Check Status screen checks port availability. The Validate System Configuration screen appears, to indicate whether various pre- install requirements for the installation have been met. The pre-install check screen then appears:. Port Uniqueness There are no duplicate defined ports for server processes.
File Space The specified file systems have sufficient space. Stage Area Check The stage area is valid. Mid Tiers Connectivity Application tier connectivity is working. File Systems The specified file systems exist and have correct privileges. System Utilities The required system utilities are available. The results of each test are labeled with icons. Click the tick to see details of the test performed. The configuration requires review. Click the!
Click Yes to continue, or No if you are going to resolve the issues. Rapid Install displays an alert if you continue without resolving the issues. Click the x to see the errors. If you can resolve an issue by altering the values provided on one of the wizard screens, click Back until you reach the.
Some tests must be resolved in the operating system. In that case, you may have to restart the Rapid Install wizard after the problem has been fixed.
Click No to review the iissues. When you have resolved any issues, click Next on the Validate System Configuration screen to continue with the installation. Important: For an upgrade with an existing Oracle home, when the database is down the following pre-checks will show a warning as they cannot be tested automatically.
You should manually ensure that the check results are correct. On the Component Installation Review screen, Rapid Install lists the components it will install, based on the system parameters you entered in the wizard. Click Next. Rapid Install now displays another alert dialog box asking you to verify that you are ready to begin the installation.
Click Yes. Check progress bars During an installation, Rapid Install displays a main progress bar and an individual progress bar. The main progress bar reports on the completion percentage of the installation as a whole. The individual progress bar reports on the progress of each individual step. Note: The installation is not complete until all the progress bars disappear from your screen.
Tests include database availability, correctly- configured environment files, and functioning listeners. Review the information from the tests Rapid Install has completed If there is an! If any of the checks fail, refer to the Rapid Install log files to determine the reason, and resolve each problem before continuing. When the errors are fixed, click Retry to perform the post-install validation again.
Click Next if there are no errors. Rapid Install informs you of the components that it installed on the Finish screen. To review the Post-install Checks screen, click Back. Instead, wait to log in until after you have applied the Release You specify basic configuration parameters, such as database type and name, top-level installation directory, and port increments. This type of installation contains by default a set of core Oracle E-Business Suite products.
You can easily register additional products according to your Oracle licensing agreement after the installation is complete, by using License Manager. Converting the character set may be time-consuming, and is best avoided if possible. Consider your character set requirements when using Express Installation. Default values are provided for all fields except Domain.
This example screen is for UNIX:. In the Database Type field, use the drop-down list to choose either a Vision Demo database or a fresh database.
On Windows as shown in the example above , enter the path to the UNIX Toolkit directory and Visual Studio directory, or click Browse and navigate to the desired path for each of these. In the Domain field, enter a value that produces a fully qualified domain name FQDN when combined with a host machine name. In the Base Directory field, enter the top-level directory path you want Rapid Install to use to create the derived mount points for the database node and all application tier nodes. Alternatively, click Browse and navigate to the desired path.
Start Installation Process Rapid Install displays the pre-install tests as it performs them. When it is complete,. If there is an exclamation mark! For example, if you see an exclamation mark beside File Space Check, clicking on it may display a screen showing an error due to insufficient file system free space.
Resolve any issues you need to fix, and then click OK to return to the Pre-install Checks screen. Click Yes to continue or No to stop the installation. If you click No, you must go back to the appropriate screen and re-enter the incorrect or incompatible parameter. Continue Installation The remaining screens in the Rapid Install flow for an Express installation are the same as for a standard installation. Installation in Silent Mode When you perform an installation using the Rapid Install wizard user interface, Rapid Install generates a configuration file that contains the details of the system-specific configuration parameters you entered in the wizard.
If you need to rerun Rapid Install, you can optionally use this configuration file to run Rapid Install in silent mode. In this mode you do not need to enter responses while Rapid Install is running. Instead, Rapid Install uses the previously entered parameters stored in the configuration file to complete the installation. Additionally, in silent mode Rapid Install sets all passwords, including the database account passwords and Oracle WebLogic Server admin password, to the default values.
Note: You cannot use silent mode the first time you run Rapid Install. You must enter the configuration parameters in the Rapid Install wizard to generate the configuration file that you can then use to run Rapid Install again in silent mode. What To Do Next After the Rapid Install run is complete, some additional finishing tasks are required for all users, and others are required for specific types of installation. Go to Finishing Tasks, page , and perform all the tasks that are applicable to your requirements.
This chapter describes how to use the specialized Rapid Install option to update the technology stack. Updating the Technology Stack Rapid Install offers a specialized option that allows you to replace selected technology stack executables in an existing instance, for example where executable files have been lost or become corrupted. Important: Before undertaking any of the procedures in this chapter, you should ensure you have a list of any patches that have been applied to the Oracle home in question.
After running the procedure, you should apply any missing patches to the newly created replacement Oracle home. The database name must be alphanumeric, must not exceed eight characters in length, must not start with a number, and must not include any spaces. Run AutoConfig with this context file.
Although this first run will fail because it needs a database up and running to succeed , it will generate the basic metadata that the database needs to start up. Replacing the OracleAS Remove the RapidWiz install stage area on both application tier file systems, fs1.
Detach the OracleAS Remove the OracleAS In the "Read Application Context File" field, enter the context file generated with adclonectx if required that matches the parameters of your OracleAS Note: You only have to enter the context file for fs1. The context file for fs2 is automatically filled in as you enter the fs1 path and file. The next screen is to confirm that this is the correct location of the OracleAS After a installation has completed successfully, run AutoConfig and then start the application tier services.
This step is platform-dependent. Do this for both fs1 and fs2. In the "Read Application Context File" field, enter the context file generated with adclonectx if required that matches the parameters of your Oracle Fusion Middleware installation, then click Next.
The next screen is to confirm that these are the correct locations for the Oracle Fusion Middleware Oracle homes. After the installation has completed successfully, run AutoConfig and then start the application tier services on the run edition file system. Certain tasks are necessary to finish all installations for Oracle E-Business Suite. After the release of the startCD, new required patches may have been discovered, so it is important to perform this step.
Doc ID: Required Action: Follow the instructions in Section 2. The AdminServer in turn brings up NodeManager. Applying Recommended Security Patches recommended The recommended security patches include the following: 1. Oracle highly recommends that you apply the latest critical patch update to your Oracle E-Business Suite environment.
Oracle highly recommends that you enable TLS. You must apply the prerequisite patch requirements to enable TLS. Apply all required patches and prerequisites to enable TLS. Applying Recommended Patches recommended Use Patch Wizard to generate a list of recommended patches for your environment and apply the list of recommended patches to your environment.
You access the Oracle. Enter a suitable username and password. You were required to specify your choice of password for this account on the Application User Information screen in Rapid Install. After entering the account name and password, click Login. From this page you can access responsibilities for any of the individual Oracle E-Business Suite products your organization has licensed.
Changing Default Passwords required Oracle recommends changing the default passwords for the accounts shown on the Application User Information screen. If you did not do so during the installation, you can still change the passwords once installation is complete. To maintain database security and restrict access to these accounts, you should change these passwords, ensuring that your choices meet your organization's security requirements.
You can use the utility adValidateEbssystemSchema. You should also change the default passwords for the Oracle E-Business Suite product accounts in your production and test databases. Cannot proceed with the deployment of EBS. Creation and deployment of E-Business Suite domain completed. EBS deployment failed! This variable has a default value of seconds. The new value needed will depend on the performance of the machine where the script is being run. Check for available memory and clear the cached memory.
Checking Database Tier Context Variables required In the database tier context file, check that the values of the context variables. If necessary, update the database tier context file to set these variables correctly. Running AutoConfig required AutoConfig is a tool that simplifies and standardizes configuration management tasks in an Oracle E-Business Suite environment.
A fresh install of Release If you are performing a new installation, you must create your own signature, and then use the adadmin utility to force regeneration of all JAR files. However, after the standard setup is complete, only a few users can be connected because of the connections used by the concurrent managers, AQ workers, and job queues.
Refer to this document when planning to update parameter settings to meet the specific requirements of your system. As the temporary files placed in this directory may contain sensitive information, it should have suitably restricted access, such as read and write access for the account that owns the database.
Finally, run AutoConfig to recreate the environment files. Implementing Product and Country-Specific Functionality conditional Depending on which products or country-specific functionality you plan to use in your installation, you may need to perform additional tasks or apply additional patches. Refer to the individual product or country-specific implementation manuals or user's guides for details. The JRE Plug-in is invoked when a user performs an operation that requires it, such as running a form.
If the JRE Plug-in has not already been installed, the browser prompts the user to download the required installation executable. Setting Up Printers required To register printers in the Printers form of Oracle E-Business Suite, the system administrator must know each printer's operating system name. To determine the names, do the following:. This account does not have access to network printing devices. To run reports using the concurrent manager, complete the following steps: 1. Log in to a user account that has administrative privileges.
In the Log in As section, select This Account, and enter the username and password used to start the concurrent manager. Using the Add Printer option, define a printer for the account that was used in Steps 2 and 3. Applying Application Tier Customizations conditional If your system requires customized forms, reports, programs, libraries, or other application files, then you can now apply all changes that you need for this release.
Scaling the environment is a post-install task. Now that the installation is complete, you can scale your environment according to production-level requirements by adding managed servers within an application tier node, adding application tier nodes, and adding database Oracle RAC nodes.
Adding Managed Servers By default, every application tier node contains only a single instance of the oacore, oafm, forms and forms-c4ws services. If more instances of a particular service are required on an application tier node, you can create new managed servers. Conditional Action: If you need to add additional managed servers in an application tier node, follow the instructions in section 4. When deploying multiple application tier nodes for an Oracle E-Business Suite environment, you can use a shared application tier file system or replicate the file system on every node in the environment.
Tip: Oracle highly recommends that you use a shared application tier file system. Examples include custom and third-party integrations, as well as integrations with other Oracle products such as Oracle Application Express.
If you plan to use external integrations that require updates to meet certification requirements with Oracle E-Business Suite Release Validate all external integrations once the necessary steps have been performed. The increase will in part depend on the products you have licensed and the additional features such as multiple languages or multiple organizations you configure in your installation.
Configuring Parallel Concurrent Processing conditional Parallel concurrent processing allows you to distribute concurrent managers across multiple nodes. Conditional Action: If you chose to enable load balancing for concurrent processing servers during the Rapid Install process, you must complete additional setup steps.
See Managing Parallel Concurrent Processing. The use of socket mode is also supported, however, and can be enabled by following the instructions in My Oracle Support Knowledge Document To use additional languages, you must first activate the additional languages via the License Manager utility, and then change the base language if required.
After this, the multilingual tables must be updated for the activated languages. After this, you should use the Translation Synchronization Patch Utility to synchronize the languages with the American English patch level.
This step is needed in case any American English patches were applied after Rapid Install was run. Setting Up Unicode Character Sets conditional Regardless of the languages installed, you may need to complete additional steps if you use a supported Unicode character set, such as AL32UTF8, in the database tier.
In addition, be aware that supplementary characters are not supported. If you customize seed data, your changes may be overwritten during an upgrade. This also applies to any changes to translations of seed data made using the globe icon. Completing Workflow Notification Mailer Configuration conditional Before you can send Oracle Workflow email notifications and Oracle Alert email alerts, you must complete the Workflow Notification Mailer configuration, using the Notification Mailer configuration wizard in Oracle Applications Manager.
In the Workflow System region, click the Notification Mailers status icon to navigate to the Service Components page for notification mailers. At this point, the Notification Mailers status icon should be showing the status Down. In the Service Components page, select the Workflow Notification Mailer service component and click the Edit button to navigate to the Notification Mailer configuration wizard.
If you want to enable inbound email processing, select the Inbound Processing parameter in the Inbound Email Account IMAP region, and enter the name of the inbound IMAP mail server, the username and password of the email account that the Notification Mailer uses to receive email messages, and the reply-to address of the email account that receives incoming messages, to which notification responses should be sent.
Return to the Service Components page, and verify that the status of the Workflow Notification Mailer service component is now Running. Optional Action: To convert your system to use public sector, education, or not-for-profit products after the installation is complete, use License Manager to register public sector or not-for-profit products.
Optimizing Performance Tuning conditional Review performance tuning recommendations to optimize your configuration for the specific requirements of your instance.
Backing Up Oracle E-Business Suite recommended After installation is complete, your operating system administrator should back up the Oracle E-Business Suite application tier product files, including the technology stack components. Your database administrator should back up the Oracle E-Business Suite database components. Subsequently, you should establish a backup policy that meets your organization's needs, balancing the overhead of carrying out the chosen backup type and frequency against the need to be able to recover from a variety of types of system failure.
The resulting backup and recovery procedures should be verified, then periodically tested to ensure continued applicability. Performing Secure Configuration This section applies to all users, regardless of which products are registered as active. At a minimum, Oracle recommends that you configure. Allowed JSPs feature. Tip: If you have any computers requiring direct access to the database that are not registered nodes in AutoConfig, such as OAM clients, then you must explicitly grant access.
Action: Regularly run the Security Check Scripts on your production instance to ensure that it is and continues to be in compliance with the recommendations in this document. Perform the following if you have upgraded to Release Update Pack Tip: After you apply Patch R C a mandatory post requisite for R C , your system will be locked down until. Consequently, if you use custom redirects and resources, such as JSPs and servlets, in your environment, then you must manually add these to your configuration files for allowed redirects and allowed resources, respectively.
This appendix contains details of the fields in the various screens of the Rapid Install wizard. Rapid Install Configuration Parameters This section lists and defines configuration parameters on the Database Install Information screen, the node-specific configuration information screens, and the Global Settings screen in the Rapid Install wizard. Rapid Install uses these values during an installation or upgrade to set up and configure your system.
Database Parameters This section lists and describes the values you enter on the database install information screen in the Rapid Install wizard. Rapid Install uses this information to set up the top- level directory and the subdirectories on the database node.
Base Install directory The top-level directory that Rapid Install uses to install the database. All subdirectories mount points associated with the database are derived from this directory. Oracle home The location of the 12cR1 database Oracle home, which contains files for running and maintaining the database. Application Tier Node Parameters This section lists and describes the fields on the application tier node screens in the Rapid Install wizard. You enter configuration details for these nodes one or more on the Primary Applications Node Configuration screen.
Additional Information: For more information about required platform- specific maintenance tools, refer to the Installation and Upgrade Notes for your platform listed in Operating System, page Set it to an active and authorized X Windows display, pointing to a machine that is always available to the instance.
Used for relinking executables and DLLs. Used for linking executables or DLLs. Base Install directory The top-level directory that Rapid Install uses to install the application tier node technology stack. All subdirectory names are derived from this directory. Also holds third-party Java files and other zip files. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:.
Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR Oracle USA, Inc.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. Pre-Installation Summary Click Install. Not applicable. Configure Domain Database page: Specify the database details for the database account that stores the PowerCenter domain configuration metadata.
Domain Configuration At the Configure Domain page, specify the domain details. Make sure that you select the Create Repository Service check box. You must specify the appropriate repository Code Page setting. PowerCenter Repository Configuration page: Specify the database details that you created for the Informatica repository.
PowerCenter Services Configuration page: The username here is the username for the Informatica repository for example, Administrator. The password here is the password for the Informatica repository for example, Administrator. Authentication Not applicable. Repository Configuration Not applicable. Post-Installation Summary Click Done. In the Properties tab, click Edit in the General properties area. Make sure that the OperatingMode value is Exclusive. Click OK.
Choose Actions, then Delete Contents. Select the Restore as new check box. Click OK to start the restore process. Change the OperatingMode value to Normal. If prompted, enter the repository username and password. Select the Integration Service. Display the Properties tab. In the Custom Properties area, click Edit.
Note : Always leave a space between the connection strings. Set this value if your data movement is from Unicode to Unicode. Notes JDK 1. For instructions, see Section 4. In the Domain Configuration section, on the Create or Join Domain page, select the Create New Domain radio button At the Configure Domain Database page, specify the database details for the domain configuration database. At the Configure Domain page, specify the domain details.
Complete the installation. Apply Service Pack 4. To define the Informatica Domains File path: Locate the file domains. Connection type Specify the type of database in which the DAC repository is stored. If you are using: Oracle OCI8 , use the tnsnames entry. Oracle Thin , use the instance name. SQL Server, use the database name. Database Port Specify the port number on which the database listens.
For example, for an Oracle database the default port is , or for a SQL Server database the default port is In the dialog box, click Yes to create the repository tables.
For a repository on Oracle or DB2 database, optionally specify a tablespace. Tip: Make a note of the Application names that you select. When you create data warehouse tables later in the configuration process, you might need to type in the names exactly as they are displayed here for more information, see Section 4.
System Imports all information contained in the DAC Setup view, except passwords for servers and database connections. Note: The import process typically takes between one and five hours, depending on the location of the database that stores the DAC repository, the speed of the network, and the number of applications selected in the Applications list on the Import dialog.
The Data Warehouse tab is active. Enter the details of the database in which you want to store the data warehouse. Field Description Database Type Read only Type of database, as specified by the 'Target data warehouse database platform' field on the Sources dialog see step 2. If the database type is DB2 , then check the Database check box. Container The name of the source business applications for which you want to create the data warehouse tables.
If you leave the Container field blank, the DAC creates a container by default for all of the following: The source business applications that you selected when you imported the seed data into the DAC metadata repository earlier for more information, see Section 4.
Any copies of those source system applications. Any additions made those source system applications. Any new source system applications that you have custom built. For example, you might do the following: Import the seed data for Oracle Add two data warehouse tables to 'My Oracle For example: If you want to deploy Oracle If you want to deploy Oracle Table Owner Valid database owner, username, or account that you set up to hold the data warehouse for more information, see Section 4.
Password Valid database user password for the database owner, username, or account that you specified in the Table Owner field for more information, see Section 4. Data Area Optional Tablespace where data warehouse tables are created. Is Unicode Specifies whether the data warehouse database is Unicode. The database must be set to support a Unicode schema for more information, see Section 4. Note: For Unicode environments, perform these procedures using a login that has the default character set UTF The domain should be set properly and the server port set as a custom property.
Otherwise, install Hibernate files following instructions in described in step 2 of Section 4. Note : If you use FTP to copy the zip file, use binary mode.
On the target machine, unzip the zip file. You must copy all jdbc drivers for the database platforms that host source s , Oracle Business Analytics Warehouse, and DAC repository databases: Oracle. Note : Do not copy the ojdbc Note : Do not copy the db2java. Click Yes to display the Server Configuration dialog.
Field Description Connection type Select the type of database that you are using to store the DAC metadata repository. Depending on what type you select, the connection details below change see Connection fields below.
Specify connection details for the database that stores the DAC metadata repository. If you select Oracle Thin , you are prompted below for the following information: Instance for example, mymachinename. Database Host fully qualified, for example, mymachine. Database Port for example, Password that is, for the above database account. If you select DB2, you are prompted below for a Connection string.
Table owner name The database table name or instance for example, DAC that you created to store the DAC repository for more information, see Section 4. Password The database or instance password for example, DAC. Note: The DAC repository details that you specify here must match the DAC repository details that you specified in the following tasks: - When you created a database to store the DAC repository for more information, see Section 4.
Enter 1 in the 'Please make your selection' prompt to enter repository connection information. Enter 2 to test the DAC repository connection. Enter 5 to save changes. Enter 6 to exit. Verifying that the DAC Server is able to use pmrep and pmcmd From a Windows command prompt, execute pmrep and then pmcmd.
Include the name of the file. For example:. Type Choose Informatica. For example, myhost. Login Informatica Repository user name who has appropriate privileges to execute workflows for example, Administrator. Password Informatica Repository user password. Maximum Sessions Maximum number of workflows that can be executed in parallel on the Informatica PowerCenter Integration Services service.
If the number of sessions is zero or is not specified, the DAC Server assigns the default value of Type Choose Repository. Server Port Port where the Repository Service connects for requests. The default port number is Login Informatica Repository user name that has appropriate privileges to execute workflows for example, Administrator.
Password Informatica Repository user password for example, Administrator. Display the Physical Data Sources tab. Do not change the default values. Connection Type Type of database. Enter the value appropriate for your database.
Table Owner Valid database user. Table Owner Password Valid database user password. Max Num Connections Maximum number of database connections this connection pool can contain. DB Host Machine name or instance where the database resides. For example, databasename.
Port Port number where the database listens for example is the default for an Oracle database. Priority Number used to generate dependencies when designing execution plans. Data Source Number Unique number assigned to the data source category so that the data can be identified in the data warehouse.
For example, the value '1' is used for Siebel data sources. Default Index Space Oracle specific Specifies the table space in which the DAC drops and creates indices against this database connection To use the default table space, leave this field blank. Choose Repository, then Add, to display the Add Repository dialog.
Choose Repository, then Connect, to display the Connect to Repository dialog. Use the Password field to specify the Administrator password for example, Administrator. If the Connection Settings area is not displayed, click More. Click OK to save the details and close the Add Domain dialog. Click Connect. For each database connection that you need to create, do the following: Click New to display the Select Subtype dialog, select the appropriate database type for example, Oracle , then click OK.
Click New to display the Connection Object Definition dialog, and enter the details. Click OK to save the details. User Name: Database user name. Password: Database user password.
Password: Database password. Select the default component setup type, Complete. The choices given are:. Must be installed on this machine before running this installer. The Administrator password must be a minimum of 6 characters and include at least one digit. Leave Cluster Account Information blank, because you are not running machines in a cluster for this installation. Overall system performance may be affected by this. To choose a different language, click the drop down box and select the desired language.
Summarizes the components to be installed the list shows the same components as Table 2 , and shows the installation location and size. Completion: At the end of the installation, choose Accept to restart the computer, or choose to restart at a later time. If you attempt to run Oracle BI without restarting your computer, several services may fail to work correctly.
The Java process in the OC4Jcomponent cannot be restarted automatically after you restart your computer. For more information about starting and stopping OC4J, refer to the file Readme. The initial configuration of Oracle Business Intelligence is made by the installer in accordance to your input during the installation process.
Otherwise, the Scheduler service fails to start and the Delivers component does not function. See Section 4. You can also configure the demonstration application deployed with the Basic installation. The Basic installation type installs a demonstration application that includes a repository paint. The paint. To administer or configure the repository, use the following procedure. If the User field is blank, type Administrator.
In the Password field, type Administrator. NOTE: The repository paint. The Administrator user password does not expire. Scheduler Job Manager The command line executable schconfig. The Scheduler works with all the supported databases for Oracle Business Intelligence. For the complete list of supported databases, see System Requirements and Supported Platforms.
Table 5 gives brief descriptions of the database tables used by Oracle Business Intelligence Scheduler. If usage tracking is enabled in NQSConfig.
A sample JavaScript is provided, which extracts information from the Usage Tracking files and loads them to a table in the relational database. You can either create a new database in which to store the tables or use an existing database. Create the database, or use an existing database. Use the appropriate procedure for your back-end database, as shown in Section 4. Section 4. Select the appropriate Database Type from the drop down list for example, Oracle 10g R1.
0コメント