Skip to main content

Oracle WebLogic 12.1.3 - Cantara Server Installation

Make sure you have done the following before deploying the Cantara Access Server:

To deploy an instance of the Cantara Server
  1. Log in to the WebLogic Server Administration Console.

    Make sure the Oracle WebLogic Server Instance that you are deploying to is not running during the deployment.

  2. Go to the Change Center and click Lock & Edit.
  3. In the left pane of the Console, select Deployments.
  4. In the right pane, click Install.
  5. Browse to the Cantara Access Server application install path as shown in the following image:

    Change Context Root

    If you want to change the context root you can do so in the WEB-INF/weblogic.xml located in the installation directory. The default context root is /cantara.

  6. Accept the default for the Install this deployment as an application option, and click Next.
  7. Select the WebLogic Server instance you want to deploy to, and click Next.

  8. We recommended you select the I will make the deployment accessible from the following location option. Doing so will make the process of backing up or deploying updates simpler because the location of the installation is easy to maintain.
  9. Click Finish, and then click Activate changes located at the top left of the console.

  10. If the deployment is successful you will see the Cantara Access Server in the list of deployments with its state set to New.
  11. You can now start the WebLogic Server instance. Once the server instance starts, the deployment state will change to Prepared.
  12. Select the deployment and click on the Start -> Servicing all requests option.
  13. The state of the deployment should now change to Active. If the deployment fails to start correctly, check the appropriate WebLogic logs for deployment errors.

Validate Deployment

If you open a browser window to the base URL of the Cantara Access Server deployment you can confirm that the deployment has completed successfully.

 

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.