Test a JD Edwards based application
Testing a JD Edwards application involves validating application headers, validating policy and overall testing. Testing using header and policy simulation allows you to validate header fields and policy execution if required.
Complete testing should always be performed to validate that the application is behaving as expected for all URIs.
- [Optional] Configure application for simulation testing - Configure the application for either header or policy simulation testing.
- Configure Access Gateway for debug and monitoring - Optionally, configure Access Gateway for debug display and monitoring of generated debug statements.
- Simulation testing - Perform header or policy simulation testing.
- Completed application testing - Perform normal application testing using production URLs.
- Disable Debug - Disable debug after testing.
To configure an application for
- Navigate to the Access Gateway Admin UI console
- From the Topology tab or the Applications tab, open the application.
- Select the Settings pane.
- Expand the Essentials sub tab.
- Note the current value of Protected Web Resource.
- Change the Protected Web Resource field to:
Value Behavior https://header.service.spgw When running a test, results in the display of information related to the header, cookie, session, and other information. https://policy.service.spgw When running a test, results in the display information related to application policy.
Copy and save the original back end Protected Web Resource value.
- Expand the Advanced sub-tab.
- Set the Debug toggle to Enable.
When enabling Debug mode, ensure that the download log has also been set to level debug. Application debug events aren't visible in downloadable logs unless download logs are also configured to emit Debug level log events.
See Manage log verbosity
- Click Done.
When debugging header based applications: Consider testing attributes with static known good values. For example, change dynamic IDP based fields to static with known good values.
When debugging policy based applications: Test with no policy or open policy first.
The Access Gateway Management console can be used to provide a running display of all system log messages. In this optional section we enable debug and monitor Access Gateway using this functionality.
- Open a terminal window and connect to the Access Gateway Management console.
- Enter 4 - Monitor.
- Enter 2 - Enable debug.
- Enter 1 - Monitor logs.
The AccessAccess Gateway Management console will then begin displaying log messages.
Header and policy simulation testing involves temporarily replacing the Protected Web resource field in an application and then testing various target URLs, evaluating whether the headers and policies return the expected result.
To test an application using header or policy simulation:
- Configure the application for header or policy simulation testing as described in the [Optional] Configure application for simulation testing section.
- Connect to the Access Gateway Management console and begin monitoring.
For details see the monitoring section in Troubleshooting Applications.
- Select the Applications tab.
- On the row containing the application, click Goto application > SP Initiated.
- Examine the header or policy information returned.
- Repeat for each protected URI.
- When complete disable debugging as described in the Disable debug section.
Completed application testing as required.
- The Applications tab, on the row containing the application, click Goto application > SP Initiated.
- Repeat testing using Goto application > IDP Initiated.
- Repeat testing using each specialized policy URI.
- If required, disable debugging.
If displaying debug statements at the command line:
- Return to the Access Gateway Management console.
- Enter [ctrl][c] to exit the log display.
- Enter 3 - Disable debug.
- Exit the command line console
If application debug is enabled:
- Return to the Access Gateway Admin UI console
- Navigate to the application being tested
- Expand the Setting sub tab.
- Expand the Essentials sub tab.
- Return the Protected Web Resource field back to its original value.
- Expand the Advanced sub tab.
- Set the Debug toggle to Disable.
- Save your changes.