Test a JD Edwards-based app

Testing a JD Edwards app involves validating app headers, validating policy, and running other general tests. Simulation allows you to validate header fields and policy execution. Always perform complete testing to validate that the app is behaving as expected for all URIs.

Configure the app for header or policy simulation testing

This task is optional.

  1. Go to the Access Gateway Admin UI console.
  2. From the Topology tab or the Applications tab, open the app.
  3. Click the Settings pane.
  4. Expand the Essentials tab.
  5. Note the current value of Protected Web Resource.
  6. Copy and save the value of the Protected Web Resource field in a secure location. You need this value when you turn debug mode off.
  7. Change the Protected Web Resource field to one of these values:
    ValueBehavior
    http://header.service.spgwThis displays information about the header, cookie, session, and other information.
    http://policy.service.spgwThis displays information about the app policy.
  8. Clear the Customize checkbox to disable the post-login URL.
  9. Expand the Advanced tab.
  10. Enable Debug mode. When you enable Debug mode, ensure that the downloadable log file has also been set to the Debug level. App debug events aren't visible in downloadable log files unless you configure them to emit debug-level log events. See Manage log verbosity
  11. Click Done.

    When debugging header-based apps, test attributes with static known good values. For example, change dynamic IdP-based fields to static ones with known good values. When debugging policy-based apps, test with no policy or an open policy first.

Configure Access Gateway for debug display and monitoring

You can configure Access Gateway Management console to generate a running display of all system log messages.

  1. Open a terminal and use Secure Shell (SSH) to connect to the Access Gateway Management console.
  2. Enter 4 - Monitoring.
  3. Enter 2 - Enable Debug.
  4. Enter 1 - Monitor logs. This starts the running display of all log messages.
  5. Return to the Access Gateway Admin UI console console. You can test your app and examine the results in the running logs.
  6. Enter Ctrl-c to exit the log display.

See Monitor for details about monitoring, including a list of available commands.

The debug logging level rapidly generates log messages. Always disable debug logging when you've finished examining logging. Otherwise, you may run out of disk space.

Header and policy simulation testing

Header and policy simulation testing involves temporarily replacing the Protected Web resource field in an app and then testing various target URLs. You evaluate whether the headers and policies return the expected result.

  1. Configure the app for header or policy simulation testing.
  2. Connect to the Access Gateway Management console and begin monitoring. See Troubleshoot apps.
  3. Select the Applications tab.
  4. On the row containing the app, click Go to application SP Initiated.
  5. Examine the header or policy information.
  6. Repeat these steps for each protected URI.
  7. When complete, disable debugging.

Use production URLs in complete app testing

  1. Click the Applications tab.
  2. On the row that contains the app, click Go to application SP Initiated.
  3. Click Go to application IDP Initiated to run the tests.
  4. Repeat testing using each specialized policy URI.
  5. Disable debugging when you're finished.

Disable debug mode

Display debug statements at the command line

  1. Go to the Access Gateway Management console.
  2. Enter [Ctrl]-[c] to exit the log display.
  3. Enter 3 - Disable debug.
  4. Exit the command-line console.

App debug is enabled

  1. Go to the Access Gateway Admin UI console
  2. Go to the app you're testing.
  3. Expand the Setting tab.
  4. Expand the Essentials tab.
  5. Return the Protected Web Resource field back to its original value.
  6. Expand the Advanced tab.
  7. Set the Debug toggle to Disable.
  8. Save your changes.