Create the Oracle Demantra app
This topic describes how to create the Oracle Demantra app in Access Gateway.
- Sign in to the Access Gateway Admin UI console.
- Click the Applications tab.
- Click +Add.
-
Select the Oracle Demantra option from the left column menu, and then click Create.
The New Protected Application wizard starts and displays the Essentials pane for the app you're adding.
-
In the Essentials pane, configure the following options:
Field Value Label Enter a name for the app, like Oracle Demantra. Public Domain Enter a fully qualified host name, like <yourexternalname>.<your domain>. In this example the host name is demantra-app.externalexample.com. Protected Web Resource Enter the URL of the internal, protected app and the port and the path, as in this example: demantra-app.internalexample.com:<port>/<path>.
- port: Enter the port that Oracle Forms listens to for HTTP requests.
- path: Enter the path to the app.
Group Enter the name of the group that contains the users who are granted access to the app. Post Login URL
Enter or modify the post-login URL. By default this field is enabled and contains this URL: https://demantra-app.externalaexample.com/workspace/.
Description Optional. Enter an appropriate description for your app.
Configure load balancing
Only use Access Gateway as the load balancer. 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 the Edit
icon to modify an entry in the table, or click the Delete
icon 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 enter the Host Header value.
- Complete the following steps to add a host. Repeat these steps as required:
- Click Add protected web resource.
- Enter a fully qualified hostname:port combination, like 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 are routed to this host. For example, two hosts of weights 2:1 result in requests being routed approximately 66% to the host weighted 2 and approximately 33% to the host weighted 1.
- Click Okay.
-
Optional. Configure health checks. They 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 the settings as required.
Field Value Default
Path The URI path to the resource used in the health check. / Method The HTTP method used in the health check. Always GET Status code The HTTP status code used to determine health. 200 Interval The interval between health checks in seconds. 10 Request timeout The health check request timeout in seconds. 1 Healthy threshold The number of requests that must succeed before a host is considered healthy. 3 Unhealthy threshold The number of requests that must fail before a host is considered unhealthy. 3 - Click Save.