This chapter contains the following sections:
Follow the steps on this page to deploy Oracle Identity Analytics to your application server.
Before You Begin-
You should have created the OIA schema on the database server and configured the rbacx.war to deploy in your environment. For details, see Chapter 3, "Configuring Your Oracle Identity Analytics Installation Prior to Deployment."
Verify that your JVM Maximum and Minimum Heap Size configuration meets the minimum values recommended for Oracle Identity Analytics. See Section 2.2.4, "Configuring JVM Options" for further information about these values.
These instructions are for a stand-alone (non-clustered) Oracle Identity Analytics deployment.
Note:
When running two or more applications in the same administrative domain (or cell), configure the application server so that the application class-loader takes precedence over the parent class-loader.
Follow the procedure in this section to deploy Oracle Identity Analytics on Tomcat. Before you begin, you should have already completed the procedures in Chapter 3, "Configuring Your Oracle Identity Analytics Installation Prior to Deployment."
Follow the procedure in this section to deploy Oracle Identity Analytics on WebSphere 7. Before you begin, you should have already completed the procedures in Chapter 3, "Configuring Your Oracle Identity Analytics Installation Prior to Deployment."
In a browser, open the WebSphere Administrative Console:
http://Hostname:Port-Number/ibm/console/
Choose Servers > Server Types > WebSphere Application Servers.
Choose your Server Name > Java and Process Management > Process Definition > Java Virtual Machine.
Specify the following value under Generic JVM Requirements, and save your changes.
-Xverify:none
Choose Servers > Server Types > WebSphere Application Servers.
Choose your Server Name > Web Container Settings > Web Container > Custom Properties.
Create a new custom property using the following parameters and save your changes.
Name: com.ibm.ws.webcontainer.invokefilterscompatibility
Value: true
Restart the application server.
In a browser, log in to the WebSphere Administrative Console.
http://Hostname:Port-Number/ibm/console/
Choose Application > New Application in the left panel.
Click New Enterprise Application.
Specify the path to the rbacx.war file and click Next.
If the rbacx.war file is located on the local system, type its complete path under Local File System.
If the file is on a remote machine, specify the path for the remote file system.
Select Detailed - Show me all installation options and parameters.
On the Choose to generate default bindings and mappings page keep the default configuration and click Next.
Click Continue on the Application Security Warning page.
The "Select Installation Options" page opens.
Complete the form:
To install the application to a location other than the default location, type the path in the Directory to Install Application field. For example, on UNIX systems:
/opt/IBM/Websphere/AppServer/installed Apps/Hostname
Verify that the following options are selected:
Precompile JavaServer Pages files
Distribute application
User binary configuration
Enter the name of the application in the Application Name field, and click Next.
The default application name is set to rbacx_war.
On the page "Map modules to servers," verify that the Oracle Identity Analytics application mapping is to the appropriate cluster/server and click Next.
The "Provide options to compile JSPs" page opens.
Make the following changes and click Next:
Select Web Module Oracle Identity Analytics.
Change JDK Source Level to 15.
On the Provide JSP reloading options for Web Modules page keep the default configuration.
On the Map shared libraries page, verify your settings and click Next.
On the Map shared library relationships page, verify your settings and click Next.
On the Map virtual hosts for Web modules page, verify that the Oracle Identity Analytics application mapping is set to the appropriate virtual host and click Next.
On the Map context roots for Web modules page, provide context root /rbacx and click Next.
Choose Applications > Application Types > WebSphere Enterprise Applications > rbacx > Manage Modules, and do the following:
Verify that the cluster/server mapping is correct.
Select Oracle Identity Analytics > Class loader order.
Under Class loader order, select Class loaded with local class loader first (parent last), and save your changes.
Note:
When running two or more applications in the same cell, it is important that you configure the application server such that the application class loader can override the parent and provide its own version of a class. For WebSphere, choose Class loaded with local class loader first (parent last), as documented above.
In a text editor, open the solr.xml file (RBACX_HOME/.indexes/solr.xml) and add persistent="false" in com.vaau.commons.search.searchengine.solr.templates.solr.xml.
Restart WebSphere.
Oracle Identity Analytics deployment on WebSphere is complete.
Note:
If the system is not writing messages to the System Log file when Oracle Identity Analytics is deployed on WebSphere, try the following:
Open the following file in a text editor:
$RBACX_WAR/META-INF/services/org.apache.commons.
logging.LogFactory
Replace the existing value with the following value and save your changes:
org.apache.commons.logging.impl.Log4jFactory
Follow the procedure in this section to deploy Oracle Identity Analytics on WebLogic. Before you begin, you should have already completed the procedures in Chapter 3, "Configuring Your Oracle Identity Analytics Installation Prior to Deployment."
To deploy Oracle Identity Analytics on WebLogic, you must first extract the .war file to a staging folder.
At the command line, navigate to $RBACX_HOME.
Note:
The $RBACX_HOME environment variable denotes the path to the directory to which you installed Oracle Identity Analytics.
Type the following commands at a command prompt to create a directory where the .war file should be exploded.
These steps require a JDK.
Windows:
C:\> mkdir rbacx
C:\> cd rbacx
C:\> jar -xvf ../rbacx.war
UNIX:
$ mkdir rbacx
$ cd rbacx
$ jar xvf ../rbacx.war
In a browser log in to the WebLogic administrative console:
http://Hostname:Port-Number/console/login/LoginForm.jsp
In the administration console, go to the left panel and click Lock & Edit, located under Change Center.
Click Deployments, located under Domain Structure.
Click Install, located in the main panel under Deployments.
The Install Application Assistant opens.
On the Locate Deployment To Install And Prepare For Deployment page, navigate to the rbacx directory created in step two and select the folder such that it lists the contents of rbacx.war.
Select the rbacx_staging directory and click Next.
Select the Install This Deployment As An Application option and click Next.
On the Optional Settings page, do the following:
Ensure that the deployment is named rbacx.
Under Security, select DDOnly: Use Only Roles And Policies That Are Defined In This Deployment.
Under Source Accessibility, select Use The Defaults Defined By The Deployment's Targets.
Click Next.
On the Review Your Choices And Click Finish page, click Yes, Take Me to the Deployments Configuration Screen.
Click Finish.
On the Settings for rbacx page, click Save.
Click Deployments in the left panel.
The Summary of Deployments panel opens.
A status of Active indicates that Oracle Identity Analytics has been successfully deployed.
Note:
When running two or more applications in the same application server administrative domain, configure the application server to allow the application to pick the appropriate JAR files from the application's libraries.
For WebLogic set the prefer-application-packages element in weblogic.xml as follows.
<weblogic-web-app xmlns="http://xmlns.oracle.com/weblogic/weblogic-web-app">
<container-descriptor>
<prefer-application-packages>
<package-name>javax.wsdl.*</package-name>
<!-- List the other package names from the library here-->
</prefer-application-packages>
</container-descriptor>
</weblogic-web-app>
Refer to your WebLogic documentation for further information.