This chapter contains the following sections:
Complete the steps in this chapter prior to beginning the steps in Chapter 3, "Configuring Your Oracle Identity Analytics Installation Prior to Deployment."
Oracle Identity Analytics is a Java™ 2 Platform, Enterprise Edition (J2EE platform) web application. The J2EE platform consists of a set of industry-standard services, APIs, and protocols that provide the functionality for developing multitiered, web-based, enterprise applications. The Oracle Identity Analytics system architecture is distributed across three logical tiers:
The presentation tier
The logic tier
The data tier
The Oracle Identity Analytics application resides on an application server and the Oracle Identity Analytics central repository of application data resides on a database server.
For a list of supported application servers, see the platform certification matrix.
You can deploy Oracle Identity Analytics on any supported application server.
If deploying to Oracle WebLogic Server, you need to create a domain. Refer to the Oracle WebLogic Server documentation for details.
The application server should be configured to use the same locale or encoding as the database and the Java Virtual Machine (JVM™ installation).
Inconsistent encodings can introduce certain globalization issues, such as the incorrect handling of multibyte characters. In globalized environments, UTF-8 should be implemented on all products.
Refer to your application server documentation for information about setting the locale and encoding.
A Java Virtual Machine (JVM) is required to run the Java classes that perform actions within Oracle Identity Analytics. To configure Oracle Identity Analytics for deployment you will need at least a version 5.0 JDK™. To run Oracle Identity Analytics on your application server at least a version 5.0 JDK™ or JRE™ is required. If integrating Oracle Identity Analytics and Oracle Identity Manager, both servers need to run the same version of the JDK or JRE.
Tip:
Many application servers include JDK software bundled with their installation. The JDK version that is shipped with the application server is always preferred to any other JDK installed on your server.
The JVM software should be configured to use the same locale or encoding as the application server and the database.
Refer to your application server's documentation for information about configuring JVM options.
You should determine your memory need and set values in your application server's JVM accordingly. The recommended memory settings are as follows:
-Xmx2048m -Xms2048m
Note:
For a 32-bit system, a Java heap size exceeding 1536 MB is not recommended.
Depending on your specific implementation, you might need to increase these recommended values if you face performance issues with the web interface.
IPv4 is required by Oracle Identity Analytics for network communication. Add the following JVM option to enforce the IPv4 preference over IPv6:
-Djava.net.preferIPv4Stack=true
Also, ensure that your OS is configured to use IPv4. Refer to your operating system documentation for instructions about how to enable the IPv4 stack.
Set the following environment variables on your application server(s) in preparation for deployment.
Before deploying Oracle Identity Analytics you need to configure the RBACX_HOME environment variable. The RBACX_HOME variable should be permanently set to the directory where you will deploy Oracle Identity Analytics. To create a permanent environment variable, refer to your operating system documentation for instructions.
Note:
A permanent $RBACX_HOME environment variable should be created under the application server's owner profile. Oracle Identity Analytics deployment will fail if RBACX_HOME is declared in a profile inaccessible by the application server.
For a clustered deployment, the $RBACX_HOME environment variable needs to be created on every cluster member.
If your database is installed on the same machine on which you will deploy Oracle Identity Analytics, create an environment variable that maps to your database installation directory. For example, if you are using Oracle Database, create a permanent $ORACLE_HOME environment variable and map it to your Oracle installation directory.