Create the Oracle WebCenter application
During this task we will create the Oracle WebCenter application in Access Gateway.
- Sign in to the Access Gateway Admin UI console.
Click the Applications tab.
Select the Oracle WebCenter option from the left column menu, and click Create.
The New Protected Application wizard will start and display the Essentials pane for the application being added.
In the Essentials pane specify the following:
Field Value Label A name for the application. Public Domain A fully qualified host name such as <yourexternalname>.<your domain>.
In the example provided this would be webcenter.externalexample.com.
Protected Web Resource
The URL of the internal protected application.
In the example provided this would be webcenter.internalexample.com:<port>/<path>
- port - the port WebCenter is listening on for HTTP requests.
- path - represents the path to the application.
See also Configure load balancing.
Group Enter the group containing the users who should have access to the application. Description Optional. An appropriate description for your application.
Available since Access Gateway version 2022.2.3
Okta recommends that whenever possible load balancers and Access Gateway as a load balancer be implemented.
See Load balancing.
- Expand the Protected Web Resource tab.
- Enable Load Balancing By Access Gateway.
A table of hostnames and weights representing the target load balancing instances appears. This table is initially empty. Click edit to modify an entry in the table, or click delete to delete an entry.
- Choose either HTTP or HTTPS as the URL scheme. Each protected web resource that you add inherits this scheme.
- Optional. Enable and specify Host Header value.
- Complete the following steps to add a host, repeat as required:
- Click Add protected web resource.
- Enter a fully qualified hostname:port combination (for example, https://backendserver1.atko.com:7001).
- Enter a weight from 1 to 100. Enter 0 to specify that a host is disabled.
Weights represent the percentage of requests that will be routed to this host.
For example, two hosts of weights 2:1 would result in requests being routed ~66% to the host weighted 2 and ~33% to the host weighted 1.
- Click Okay.
Optional. Configure health checks, which use GET operations to confirm that back-end resources are functional.
New requests aren't routed to resources that have been labeled unhealthy by the health checks.
- Enable Load Balancer Health Check.
- Click Edit to modify health check settings.
- Modify settings as required.
Path URI to resource used in health check. / Method HTTP method used. Always GET Status code HTTP status code used to determine health. 200 Interval Interval between health checks in seconds. 10 Request timeout Health check request timeout in seconds. 1 Healthy threshold Number of successful requests before a host is considered healthy. 3 Unhealthy threshold Number of failed requests before a host is considered unhealthy. 3
- Click Save to save changes or click Cancel to exit without saving.