JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Identity Analytics Installation and Upgrade Guide 11g Release 1
search filter icon
search icon

Document Information

Preface

Part I Compatibility Matrix

1.  Oracle Identity Analytics 11gR1 Compatibility Matrix

Part II Installing Oracle Identity Analytics

2.  Preparing to Install Oracle Identity Analytics

3.  Installing Oracle Identity Analytics

4.  Deploying Oracle Identity Analytics

Deploying on Tomcat

To Deploy Oracle Identity Analytics on Tomcat

Deploying on WebSphere

To Configure WebSphere to Run Oracle Identity Analytics

To Deploy Oracle Identity Analytics on WebSphere

Deploying on WebLogic

To Deploy Oracle Identity Analytics on WebLogic

Deploying on GlassFish

To Deploy Oracle Identity Analytics on GlassFish

5.  Verifying the Oracle Identity Analytics Installation

Part III Upgrading Oracle Identity Analytics

6.  Overview of the Upgrade Process

7.  Preparing to Upgrade Oracle Identity Analytics

8.  Upgrading Oracle Identity Analytics in a Test Environment

9.  Upgrading Oracle Identity Analytics in a Production Environment

Deploying on WebLogic

Follow the procedure in this section to deploy Oracle Identity Analytics on WebLogic. Before you begin, you should have already completed the procedures in the Chapter 3, Installing Oracle Identity Analytics chapter.

To Deploy Oracle Identity Analytics on WebLogic

To deploy Oracle Identity Analytics on WebLogic, you must first extract the .war file to a staging folder.

  1. 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.


  1. Type the following commands at a command prompt to create a directory where the .war file would be exploded.

    These steps require a JDK.

    • Windows:

      C:\> mkdir rbacx_staging

      C:\> cd rbacx_staging

      C:\> jar -xvf ../rbacx.war

    • UNIX:

      $ mkdir rbacx_staging

      $ cd rbacx_staging

      $ jar -xvf ../rbacx.war

  2. In a browser log in to the WebLogic administrative console:

    http://Hostname:Port-Number/console/login/LoginForm.jsp

  3. In the administration console, go to the left panel and click Lock & Edit, located under Change Center.

  4. Click Deployments, located under Domain Structure.

  5. Click Install, located in the main panel under Deployments.

    The Install Application Assistant opens.

  6. On the Locate Deployment To Install And Prepare For Deployment page, navigate to the rbacx_staging directory created in step two and select the folder such that it lists the contents of rbacx.war.

  7. Select rbacx, and click Next.

  8. Select the Install This Deployment As An Application option and click Next.

  9. On the Optional Settings page, do the following:

    1. Ensure that the deployment is named rbacx.

    2. Under Security, select DDOnly: Use Only Roles And Policies That Are Defined In This Deployment.

    3. Under Source Accessibility, select Use The Defaults Defined By The Deployment's Targets.

    4. Click Next.

  10. On the Review Your Choices And Click Finish page, select Yes, Take Me To The Deployments Configuration Screen.

  11. Review the settings for the deployment, then click Next.

  12. Click Deployments in the left panel.

    The Summary of Deployments panel opens.

  13. Select rbacx, then click Start > Servicing All Requests.

    Select Yes to start the deployment.

A status of Start Running indicates that Oracle Identity Analytics has been successfully deployed.


Note - If a 'Session Error' alert box is observed when accessing Oracle Identity Analytics, follow these steps.

  1. Locate dwr-context.xml file within /WEB-INF directory of exploded rbacx.war file.

  2. Replace <dwr:controller debug="true" id="dwrController"/> with the following

    <dwr:controller debug="true" id="dwrController">
            <dwr:config-param name="allowScriptTagRemoting" value="false"/>
            <dwr:config-param name="crossDomainSessionSecurity" value="false"/>
    </dwr:controller>
    • If the lines exist, change the value of allowScriptTagRemoting and crossDomainSessionSecurity to false.