Use Font Awesome how you want: via our CDN, Download Font Awesome to host yourself, or install the latest via npm. We've got component packages and CSS-processors too. With Way More on the Way! We're not done yet. Native app support, more category packs, desktop subsetter, duotone icons, and more are in the hopper.
![]() ![]()
This document is intended for use in conjunction with the various Oracle Fusion Middleware product installation guides and the Oracle Fusion Middleware 12c Release 1 Certifications.Consider the following pre-installation workflow: Task 1 Find Out What is CertifiedThe Oracle Fusion Middleware 12c Release 1 Certifications can be found in the table on the page. Find the.xls document that includes your products.Oracle has tested and verified the performance of your product on all certified systems and environments; whenever new certifications occur, they are added to the proper certification document right away. New certifications can occur at any time, and for this reason the certification documents are kept outside of the documentation libraries and are available on Oracle Technology Network. If you use My Oracle Support, you can reference My Oracle Support Certifications, which is a self-service certification application which provides a structured display of most common certification data.
Go to refer to the Certifications tab. Task 2 Verify the Requirements of the CertificationThis document should be used to verify that the requirements of the certification are met. For example, if the certification document indicates that your product is certified for installation on 32-Bit Oracle Linux 5, this document should be used to verify that your Oracle Linux 5 system has met the required minimum specifications, like disk space, available memory, specific platform packages and patches, and other operating system-specific items. This document is updated as needed and therefore also resides outside of the documentation libraries and is available on Oracle Technology Network. Task 3 Install Your SoftwareAfter you have verified that your environment meets the requirements specified in both the certification documents and system requirements, you are ready to begin your installation.Your product installation guides contain the step-by-step instructions to get your product physically installed and configured on your system. These guides are available only from the documentation library and therefore are not updated unless there is a subsequent product release.
Both the certification and system requirement documents can be updated multiple times in between product releases, depending on whether or not new information is available. Most Fusion Middleware products are available as platform-generic distributions in.jar file format. These distributions do not include a JDK. To run the installer in a.jar distribution, you must have a certified the JDK already installed on your system.Some products (for example, Oracle HTTP Server) have a.bin (for UNIX operating systems) or.exe (for Windows operating systems) installer; in these cases, a platform-specific JDK is included with the distribution and you do not need to install a JDK separately.
However, it may be recommended that you upgrade this JDK to a more recent version, depending on the JDK versions that are certified.At the time this document was published, the certified JDK was jdk1.8.0101. For information about the latest certified JDKs, refer to the certification document for your software version on the page for certified JDKs. Note:For the purposes of this document, memory requirements fall into two categories: physical memory (the amount of physical RAM installed on host) and the minimum available memory, which includes swap space in addition to the physical memory.The memory requirements listed here are minimum requirements; the actual required memory will vary, depending upon the number of Managed Servers and the number of Oracle Fusion Middleware products you configure in the domains on each host.
For some guidelines about determining the amount of memory required for a specific deployment, see.If you plan to install and configure a database instance on the same server, you should add at least an additional 2 GB of physical and 2 GB of available memory. For more information about memory requirements for the database, see the documentation for your database software version.
Oracle Fusion Middleware installations vary widely in terms of how the Oracle WebLogic Server domains that support them are configured. For example, in some highly available production environments, you might have several Managed Servers running on a each host. On the other hand, a single Administration Server, configured in a supported compact domain configuration is adequate for some development purposes.To estimate the amount of required memory required to run Oracle Fusion Middleware 12 c in a particular deployment configuration, you can consider the amount of memory required by the operating system and other software, and then add a set amount of memory that will be required for each Java Virtual Machine (JVM) that you plan to configure on the host. In a production environment, Oracle recommends as a best practice that you target products and services to specific Managed Servers and clusters, based on the resources required by the products and services.For example, in a typical enterprise deployment of Oracle SOA Suite, you target Oracle Web Services Manager (OWSM) to one cluster and Oracle SOA Suite to another cluster. This can result in a domain with multiple Managed Servers on each host. As you add additional managed clusters, the memory requirements increase.For example, if you are planning to configure a Oracle WebLogic Server domain with an Administration Server and two Managed Servers, then you could use the following formula to determine the minimum required available memory: 3 GB for the operating system and other software3 GB for the Admin Server+ 6 GB for the two Managed Servers-12 GB.
The installation program uses a temporary directory into which it extracts the files that are needed to install the software on the target system. During the installation process, your temporary directory must contain sufficient space to accommodate the compressed Java Run-time Environment (JRE) bundled with the installation program and an uncompressed copy of the JRE that is expanded into the temporary directory.
The extracted files are deleted from the temporary directory after the installation process. The files in the temporary directory require approximately 2.5 times the space that is ultimately required for the installation.By default, the installation program uses the following temporary directories:.Windows platforms—directory referenced by the TMP system variable.UNIX platforms—system-dependent temporary directory. Table 1-2 Oracle Universal Installer Startup Requirements CategoryAccepted or Minimum ValuesPlatformsFor a complete list of supported platforms, refer to Oracle Fusion Middleware Supported System Configurations page, as described in.CPU SpeedAt least 300MHz.MonitorAt least 256 colors (this is a requirement for the graphical mode installer only).Swap SpaceAt least 512MB.JDKSee for more information about JDK verification on your system.Temp SpaceAt least 300MB.Note that the temporary space noted here is in addition to the temporary space required for installer extraction as mentioned in. Note:Always refer to the appropriate certification document for your release on the page for the latest certification information.In some cases, additional database certifications may be added before RCU is updated.
When you run RCU, you may receive a warning that the database on which you are installing the schemas is not supported; as long as the database version is listed in the certification document, you can safely ignore this warning.Database is installed with Oracle JVM enabled. Refer to your database documentation for information about how to do this.Character set is AL32UTF8.If your database does not use the AL32UTF8 character set, you will see the following warning when running RCU: The database you are connecting is with non-AL32UTF8 character set.
Oracle strongly recommends using AL32UTF8 as the database character set.You can ignore this warning and continue using RCU.The following database parameters are set as specified. Table 1-6 Oracle Data Integrator Requirements ResourceRecommended Minimum ValueCPUPentium IV 2 GHz or fasterAvailable Memory3 GB of RAM for one agent.For environments with no WebLogic server, the amount of memory you want to allocate to each agent is set by the ODIMAXHEAP parameter in the DOMAINHOME /bin/setODIDomainEnv.sh bat script. The MDS data source in WebCenter Content User Interface cannot work with XA drivers only.However, by default, the driver Oracle's DB2 XA (Type 4XA) Versions:7.x and later is selected in the JDBC Datasources screen in the Configuration Wizard. However, multi data source is not certified with the DB2 XA driver.You must select the non-XA Driver, Oracle's DB2 Driver (Type 4) Versions:7.x and later for WebCenter Content User Interface to work properly.See the 12 c (12.2.1.2)certification document on the page for the latest information on certified databases. To ensure that both forward lookup (find the IP address given the hostname) and reverse lookup (finding the hostname given the IP address) return the same results, make sure your /etc/hosts file is formatted correctly using the following guidelines:.The host name may contain only alphanumeric characters, hyphen, and period. The name must begin with an alphabetic character and end with an alphanumeric character.Host names should be specified as fully qualified host names (host name with the appended domain name).Lines cannot start with a blank space or tab character, but fields may be separated by any number of space or tab characters.Comments are allowed and designated by a pound sign (#) preceding the comment text.Trailing blank and tab characters are allowed.Blank line entries are allowed.Only one host entry per line is allowed.
Oracle Fusion Middleware supports Internet Protocol Version 4 (IPv4) and Internet Protocol Version 6 (IPv6.) Among other features, IPv6 supports a larger address space (128 bits) than IPv4 (32 bits), providing an exponential increase in the number of computers that can be addressable on the Web.An IPv6 address is expressed as 8 groups of 4 hexadecimal digits. For example: 2001:0db8:85a3:08d3:1319:8a2e:0370:7334This section contains the following additional topics to help you understand IPv6 in Oracle Fusion Middleware.
Describes support for IPv6 by Oracle Fusion Middleware components:.The column IPv6 Only shows whether a component supports using IPv6 only for all communication.The column Dual Stack shows whether a component supports using both IPv6 and IPv4 for communication. For example, some components do not support using IPv6 only, because some of the communication is with the Oracle Database, which supports IPv4, not IPv6. Those components support dual stack, allowing for IPv6 communication with other components.
Table 1-12 IPv6 Support in Oracle Fusion Middleware ComponentIPv6 OnlyDual StackCommentsOracle Application Development FrameworkYesYesNone.Oracle HTTP ServerYesYesTo configure Oracle HTTP Server for IPv6, see in Oracle Fusion Middleware AdministeringOracle Fusion Middleware.Oracle WebLogic ServerYesYesThe Oracle WebLogic Server Web Server plug-ins support IPv6, beginning with the 11 g release.Oracle Data IntegratorNoYesRequires a dual stack because Oracle Database requires IPv4 addresses. The Agent requires IPv4 addresses.
The Oracle Data Integrator server can be on a dual-stack host. Dynamic Host Configuration Protocol (DHCP) assigns dynamic IP addresses on a network.
Dynamic addressing allows a computer to have a different IP address each time it connects to the network. In some cases, the IP address can change while the computer is still connected. You can have a mixture of static and dynamic IP addressing in a DHCP system.In a DHCP setup, the software tracks IP addresses, which simplifies network administration.
This lets you add a new computer to the network without having to manually assign that computer a unique IP address. However, before installing Oracle Database onto a computer that uses the DHCP protocol, you must install a loopback adapter to assign a static, non-routable IP address to that computer.If you are installing your Oracle Fusion Middleware products on a DHCP host, refer to your operating system documentation for instructions on how to properly configure a loopback adapter. You can install your Oracle Fusion Middleware product on a multihomed computer. A multihomed computer is associated with multiple IP addresses.
This is typically achieved by having multiple network cards on the computer. Each IP address is associated with a host name; additionally, you can set up aliases for each hostname.The installer picks up the fully qualified domain name from the first entry in /etc/hosts (on UNIX operating systems) or%SYSTEMROOT%system32driversetchosts (on Windows operating systems) file. So if your file looks like the following (IPv4 example shown below): 127.0.0.1 localhost.localdomain localhost10.1.1.1 examplehost1.example.com examplehost110.2.2.2 examplehost2.example.com examplehost2examplehost1.example.com would be picked for configuration.For specific network configuration of a system component, refer to the individual component's configuration documentation.In any situation where you change any combination of the host name, domain name, or IP address of a host, you also change the information for your Oracle Fusion Middleware components. See in Oracle Fusion Middleware AdministeringOracle Fusion Middleware for more information about additional steps that need to be performed. This section contains system requirement information for UNIX operating systems.In some cases, a particular platform may be de-supported for use with Oracle Fusion Middleware products.
While this particular platform's requirements may remain in this document for legacy purposes, it would no longer be listed in the certification information and would no longer be considered a 'certified' platform.For more information, see.All packages listed are minimum versions.The following topics are covered in this section. To check your current locale settings, use the locale command on your system. Below is an example: localeLANG=enUS.UTF-8LCCTYPE=enUS.UTF-8LCNUMERIC=enUS.UTF-8LCTIME=enUS.UTF-8LCCOLLATE=enUS.UTF-8LCMONETARY=enUS.UTF-8LCMESSAGES=LCPAPER='POSIX'LCNAME='POSIX'LCADDRESS='POSIX'LCTELEPHONE='POSIX'LCMEASUREMENT='POSIX'LCIDENTIFICATION='POSIX'LCALL=If the operating system is configured to use a non-UTF-8 encoding, Oracle SOA Suite components may function in an unexpected way. For example, a non-ASCII file name can make the file inaccessible and cause an error. Oracle does not support problems caused by operating system constraints.In a design-time environment, if you are using Oracle JDeveloper, select Tools - Preferences - Environment - Encoding - UTF-8 to enable Unicode support. Table 1-18 IBM AIX Operating System Requirements ProcessorOperating System VersionRequired PackagesPOWER7.1 (Update 1)bos.adt.basebos.adt.libbos.adt.libmbos.perf.libperfstatbos.perf.perfstatbos.perf.proctoolsrsct.basic.rtersct.compat.clients.rtexlC.aix61.rte (version 12.1.0.1+)xlC.rte (version 12.1.0.1+)POWER7.2bos.adt.base 7.2.0.0bos.adt.lib 7.2.0.0bos.adt.libm 7.2.0.0bos.perf.libperfstat 7.2.0.0bos.perf.perfstat 7.2.0.0bos.perf.proctools 7.2.0.0rsct.basic.rte 3.2.1.0rsct.compat.clients.rte 3.2.1.0xlC.aix61.rte 13.1.2.0xlC.rte 13.1.2.0.
This includes:.Oracle HTTP Server.Oracle Traffic Director.Forms and Reports.OBIEEOn the Windows platform, these components require the Microsoft Visual C run-time libraries to be installed on the system.If these libraries are not installed on your Windows operating system, then you will receive an error during the prerequisite check phase of these components.To meet this system requirement, download the correct version of Visual C Redistributable for Visual Studio by referring to below.You can download the software from. ProblemRecommendationExpected resultActual ResultThis Oracle software was not certified on the current operating system at the time it was made generally available. It may have been certified following general availability.Check the Supported System Configurations Guide (for further details. If your operating system is certified, check the System Requirements Guide (to verify your system configuration. If the system meets the required configuration, press 'Next' if you wish to continue.One of 6.2, 6.310.0This Oracle software is not certified on the current operating system.Make sure you are installing the software on the correct platform.One of 6.0, 6.1, 6.2, 6.310.0Ignore these warnings and proceed with the installation by clicking Next. On Oracle databases, the MDS database user created by Repository Creation Utility (RCU) requires EXECUTE privilege on DBMSOUTPUT, DBMSSTATS, and DBMSLOB.
When you create a metadata repository using RCU, if PUBLIC does not have EXECUTE privilege on DBMSOUTPUT and DBMSSTATS, the RCU user must have the privilege to grant EXECUTE privilege on DBMSOUTPUT and DBMSSTAT to the MDS user. The RCU user must have the privilege to grant EXECUTE privilege on DBMSLOB to the MDS user.To ensure that you have the correct privileges, login to RCU as a SYSDBA or as a DBA user who has EXECUTE privilege with GRANT OPTION on DBMSOUTPUT and DBMSLOB.
Note the following about using SQL Server as the database for MDS:.To create a metadata repository in SQL Server, set READCOMMITTEDSNAPSHOT to ON for the hosting database. This enables the needed row versioning support. Use the following SQL command ALTER DATABASE, as in the following example: ALTER DATABASE mds SET READCOMMITTEDSNAPSHOT ON.Use case-sensitive collation to support the case-sensitive semantics in the metadata repository.
For example, if Latin1General is used, select the SQLLatin1GeneralCP1CSAS collation using the following SQL command: ALTER DATABASE mds COLLATE SQLLatin1GeneralCP1CSASIn many cases, this command will run successfully. However, the command might fail and generate error messages concerning functions, primary keys, constraints, or indexes. This can be caused if the database already has collation aware objects. In this case, SQL Server does not allow you to change the collation at the database level. In this case, the alternative is to create a new database with the expected collation for MDS to use.There are some minor differences between an Oracle schema and a SQL Server schema. The length of the certain text fields are shorter for a SQL Server schema. For example, the full path name of the metadata in SQL Server is limited to 400 characters.
Note the following about using DB2 as the database for MDS:.DB2 9.7 or later must be used for MDS repository to work properly.Make sure that CURCOMMIT is set to ON, which is the default value for a newly installed DB2 9.7 database. This setting can be verified using following DB2 command: db2 connect to yourdatabase user adminuserdb2 'get db cfg' grep -I commitCurently Committed (CURCOMMIT) = ON.Set the lock timeout parameter of the database to a low value. Unlike Oracle databases, with DB2, if one user is updating a row, under some conditions, another user may be blocked when updating a different row and must wait until the transaction is committed or rolled back by the first user. To facilitate better concurrency, do not specify -1, which sets the lock timeout to infinity.To query the lock timeout value for your DB2 database, use the following command: db2 'get database config for databasealias' grep -i timeoutIf the value is too high, change it. For example, to change the lock timeout value to 180 seconds, use the following command: db2 'update database config for databasealias using locktimeout 180'Choose a proper value for the locktimeout parameter. If a large value is used, it will affect system throughput, since the transaction has to wait a very long time before giving up. If the value is set too small, users will see many timeout exceptions if the database is processing many long running transactions.Set the DB2 registry variables DB2EVALUNCOMMITTED, DB2SKIPINSERTED, and DB2SJIPDELETED to OFF to avoid deadlock and locking issues.
By default, they are set to OFF. To view the current registry variables setting, use the db2set -all command.If they are not set to OFF, use the following commands: db2set DB2EVALUNCOMMITTED=OFFdb2set DB2SKIPINSERTED=OFFdb2set DB2SKIPDELETED=OFFThen, restart the database server using the using db2stop and db2start commands.DB2 may escalate a row lock to a table lock due to memory stress or lock usage. As the result, a user's transaction may be rolled back as a victim of deadlock or lock timeout. To reduce lock escalation, you can increase the size of the MAXLOCKS and LOCKLIST configuration parameters. Use the following commands: db2 'update database config for databasealias using locklist value'db2 'update database config for databasealias using maxlocks value'The recommended value for MAXLOCKS is 20, and the recommended value for LOCKLIST is 70000. You should set appropriate values based on your environment and usage.The isolation level must be set to Currently Committed.
To verify the setting, use the following command: db2 'get database config for databasealias' grep -i commitTo set the isolation level to Currently Committed, use the following command: db2 'update database config for databasealias using CURCOMMIT ON'.If the database transaction log is often full, increase the database configuration parameter to allow for a larger log file. A larger log file requires more space, but it reduces the need for applications to retry the operation. You should set the log file size to at least 10000 and the number of primary log files to at least 50. Use the following commands: db2 'update database config for databasealias using LOGFILSIZ 10000'db2 'update database config for databasealias using LOGPRIMARY 50'.If the IBM DB2 JCC driver is chosen for the data source, the progressiveStreaming=2 property must be added to the property list of the data source. In effect, progressive streaming will be disabled. Without this property setting, MDS may run into issues in accessing document contents saved in a large object (LOB) column in the MDS repository. This software and related documentation are provided under a licenseagreement containing restrictions on use and disclosure and are protected byintellectual property laws.
Except as expressly permitted in your license agreement orallowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,transmit, distribute, exhibit, perform, publish, or display any part, in any form, or byany means. Reverse engineering, disassembly, or decompilation of this software, unlessrequired by law for interoperability, is prohibited.The information contained herein is subject to change without noticeand is not warranted to be error-free. If you find any errors, please report them to usin writing. If this is software or related documentation that is delivered to theU.S. Government or anyone licensing it on behalf of the U.S. Government, then thefollowing notice is applicable:U.S.
GOVERNMENT END USERS: Oracle programs, including any operatingsystem, integrated software, any programs installed on the hardware, and/ordocumentation, delivered to U.S. Government end users are 'commercial computer software'pursuant to the applicable Federal Acquisition Regulation and agency-specificsupplemental regulations. As such, use, duplication, disclosure, modification, andadaptation of the programs, including any operating system, integrated software, anyprograms installed on the hardware, and/or documentation, shall be subject to licenseterms and license restrictions applicable to the programs. No other rights are grantedto the U.S. This software or hardware is developed for general use in a variety ofinformation management applications.
![]()
It is not developed or intended for use in anyinherently dangerous applications, including applications that may create a risk ofpersonal injury. If you use this software or hardware in dangerous applications, thenyou shall be responsible to take all appropriate fail-safe, backup, redundancy, andother measures to ensure its safe use. Oracle Corporation and its affiliates disclaimany liability for any damages caused by use of this software or hardware in dangerousapplications.
Oracle and Java are registered trademarks of Oracle and/or itsaffiliates. Other names may be trademarks of their respective owners.Intel and Intel Xeon are trademarks or registered trademarks of IntelCorporation. All SPARC trademarks are used under license and are trademarks orregistered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and theAMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIXis a registered trademark of The Open Group. This software or hardware and documentation may provide access to orinformation about content, products, and services from third parties.
Oracle Corporationand its affiliates are not responsible for and expressly disclaim all warranties of anykind with respect to third-party content, products, and services unless otherwise setforth in an applicable agreement between you and Oracle. Oracle Corporation and itsaffiliates will not be responsible for any loss, costs, or damages incurred due to youraccess to or use of third-party content, products, or services, except as set forth inan applicable agreement between you and Oracle.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |