Add an Oracle Agile PLM Application

The purpose of this tutorial is to walk through the process of setting up an Oracle Agile PLM application through the Access Gateway AdminAn abbreviation of administrator. This is the individual(s) who have access to the Okta Administrator Dashboard. They control the provisioning and deprovisioning of end users, the assigning of apps, the resetting of passwords, and the overall end user experience. Only administrators have the Administration button on the upper right side of the My Applications page. Console.

Oracle Forms Architecture

Before You Begin

 

Create the Application in Access Gateway

  1. Navigate to your Access Gateway InstanceAn instance, or computer instance, is a virtual machine (VM) or individual physical computer, used to host a software appliance..

  2. In the Access Gateway Admin UI, sign in as an administrator.

  3. Click the Applications tab.

    Select applications tab

  4. Click +Add to add a new application.

    Click Add.

  5. Select the Oracle WebLogic option from the left column menu, and click Create.

    Select Oracle Agile PLM app and click create.

    The New Protected Application wizard will start and display the Essentials pane for the application being added.

  6. In the Essentials pane specify the following:

    Field Value
    Label A name for the application such as "Oracle Agile PLM"
    Public Domain A fully qualified host name such as <yourexteralname>.<your domainA domain is an attribute of an Okta organization. Okta uses a fully-qualified domain name, meaning it always includes the top-level domain (.com, .eu, etc.), but does not include the protocol (https).>.
    In the example provided this would be agile-app.externalexample.com.
    Protected Web Resource

    The URL of the internal, protected, application.
    In the example provided this would be agile-app.internalexample.com:<port>/<path>
    Where:

    • port - the port Oracle Forms is listening on for http requests.
    • path - represents the path to the application.
    Group Enter the group containing the users who should have access to the application.

    Post Login URL

    Enter or modify the post login URL. By default, this field is enabled and contains value:
    agile-app.externalexample.com/Agile

    Description [optional] An appropriate description for your application.
  7. The Attributes page provides a list of attributes that will be passed into the application as header fields.
    Datasource

    Value

    NAME
    idp

    login

    REMOTE-USER

    Use the edit () to modify the name and other values associated with this attribute as required.
    Add or modify any required attributes, and click Next.
    For more information on the attribute options, see Application attributes.
    The Policies pane appears.

  8. Leave all policies unchanged and click Done.
    For more information on Application policies see About application policy and Manage application policy .

Test the Application

The following steps assign the application to a test account and then execute the application to verify basic functionality.

Assign the application

  1. Login to your Okta tenant as administrator.

  2. Select Application > Applications.

  3. Click the name of the newly added header application.

  4. Select the Assignments tab.

  5. Select Assign > Assign To People.

  6. Select an appropriate user and click Assign.

    Info

    Note

    Testing is typically initially done using the same user who is associated with administering Access Gateway

  7. Click Done.

Execute the Application

  1. Return to the Access Gateway admin console.

  2. On the row representing the newly added app, select one of Goto application > IDP Initiated or Goto application > SPAn acronym for service provider. Generally, an SP is a company, usually providing organizations with communications, storage, processing, and a host of other services. Within Okta, it is any website that accepts SAML responses as a way of signing in users, and has the ability to redirect a user to an IdP (e.g., Okta) to begin the authentication process. Initiated.

  3. Verify the resulting page displays as expected.
  4. Close the results page.

See Also

Top