Create the Rapid or Classic EBS application

Configure the EBS SSO Agent (Rapid) application

The following steps describe how to configure an EBS Rapid Application.

1. In the Essential pane enter:

   Field	Value
   Label	The name of the application, as shown in your Okta tenant.
   Public Domain	The externally facing URL of the EBS application. This must be the same value entered in step 7 of Enable Oracle E-Business Suite for single sign-on. For example: https://ebs-external.example.com
   Protected Web Resource	The URL and port combination of the Oracle EBS Implementation being protected. Always end the protected resource URL with a forward slash (/). See Configure load balancing. For example: http://ebs-internal.example.com:8000/
   Post Login URL	URL of the EBS server. This must be the hostname and port of the back-end EBS server and not the external name used in Public Domain. For example: https://ebs-internal.example.com:8000/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE
   Group	The group containing users who can access the EBS instance.

All apps, including the Access Gateway Admin UI console app, require a self-signed or signed certificate.

Include signed certificates wherever you terminate SSL. You can terminate SSL at Access Gateway or any other network component, like a load balancer.

If you terminate SSL at a load balancer, on the Access Gateway Admin UI console app, you also need to use a certificate that is trusted by the load balancer.

If you terminate SSL on the Access Gateway Admin UI console application, you must use a signed certificate, which must be on the Access Gateway node and be associated with the Access Gateway Admin UI console application.

• See Certificate use for details about certificates.
• See Certificate management for a task flow for obtaining and assigning certificates.
2. Expand the Certificates tab.

   By default, when you create the app, the system generates a self-signed wildcard certificate and assigns it to the app.

3. Optional. Click Generate self-signed certificate. A self-signed certificate is created and automatically assigned to the app.
4. Optional. Select an existing certificate from the list. Use the Search field to narrow the set of certificates by common name. Use the page forward and backward arrows to navigate through the list.

5. Click Next.The Application Configuration pane displays.

6. In the Application configuration pane enter/verify:

   Field	Value
   EBS Service Account	The EBS username from the configuration section. For example, OAGSSOUSER.
   EBS Service Account Password	Password associated with EBS Service Account.
   EBS User Identified	Either USER_NAME or EMAIL_ADDRESS.
   DBC File Contents	DBC file contents as provided by the Oracle EBS Administrator or the value from section Register Okta Access Gateway With Oracle E-Business Suite.

7. Click Not validated when complete.
   
   If all values are entered correctly, the Not Validated button will change to Validated.
   
8. Click Next.

9. In the Attributes tab verify the following three attributes:

   See Application attributes for detailed information on the attribute options.

   Data Source	Field	Type	Name
   IDP	User profile field that represents the EBS user name. It can be data static and a fixed value for testing. EBS only supports user name values in upper case.	Header	EBS_USER
   static	Auth Context	Header	REMOTE_IP
   static	Auth Context	Header	SESSION_ID

10. Click Done when complete.

Configure load balancing

1. Expand the Protected Web Resource tab.
2. 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.

3. Choose either HTTP or HTTPS as the URL scheme. Each protected web resource that you add inherits this scheme.
4. Optional. Enable and specify Host Header value.
5. Complete the following steps to add a host, repeat as required:
   1. Click Add protected web resource.
   2. Enter a fully qualified hostname:port combination (for example, https://backendserver1.atko.com:7001).
   3. 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.

   4. Click Okay.

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

   1. Enable Load Balancer Health Check.
   2. Click Edit to modify health check settings.
   3. Modify settings as required.

      Field	Value	Default
      Path	The URI path to the resource used in health check.	/
      Method	The HTTP method used.	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

   4. Click Save to save changes or click Cancel to exit without saving.