Diagnostics and Troubleshooting

Overview

This chapter describes how to enable logging and diagnostics features as well as how to troubleshoot possible issues from the mobile client and the server. It includes the following sections:

Note: The logging and diagnostics information described in this chapter does not apply to Oracle Field Service for EBS and Oracle Mobile SCM for EBS (MSCA).

Enabling Logging for Oracle Approvals for EBS, Oracle Self-Service HR for EBS, and Oracle Timecards for EBS

Oracle Approvals for EBS, Oracle Self-Service HR for EBS, and Oracle Timecards for EBS use the server logging and REST service auditing features to troubleshoot or diagnostic issues if occur during the service invocation while using the apps:

Note: Oracle Approvals for EBS, Oracle Self-Service HR for EBS, and Oracle Timecards for EBS do not use the client logging feature.

The troubleshooting tips described in later in this chapter does not apply to these three apps.

Enabling Server Logging

Oracle E-Business Suite mobile apps use the common logging and diagnostics features in Oracle E-Business Suite to enable the logging for REST services used by mobile apps. Once these features are enabled for Oracle E-Business Suite applications, administrators can use the log messages to diagnose and troubleshoot potential issues on the Oracle E-Business Suite server.

If a mobile app user reports a problem, an administrator can set the following Oracle Application Object Library (FND) profile options for that user to enable logging, control the logging level, and set the module for which logs are recorded. These profile options are also used if app users need to upload their client log files to the server.

Note: Use the app-specific REST service module names to set the FND: Debug Log Module profile option. These module names are listed in Appendix D: Mobile App Module Names.

For information on enabling the logging and diagnostics features, refer to the Oracle E-Business Suite Maintenance Guide.

Retrieving Server Logs

To retrieve the server logs recorded for your mobile app, perform the following steps:

  1. Log in to Oracle E-Business Suite as the SYSADMIN user. Select the System Administrator (or System Administration) responsibility and choose the Oracle Applications Manager link and then the Logs link from the navigation menu.

  2. In the Search System Logs page, click the Advanced Search button.

  3. Enter the following information in the Advanced Search region:

    • User: Enter the mobile app user name.

    • Module: Enter the REST service module name of the mobile app.

  4. Run the search to retrieve and download the desired server logs.

Enabling REST Service Auditing

Perform the following steps to enable auditing for REST service request and response payloads during the service invocation for Oracle E-Business Suite mobile apps:

Note: The REST service payloads can be logged for auditing only when the server logging is also enabled.

If the REST service auditing feature is not required, you can choose to enable the server logging only. See Enabling Server Logging.

  1. Set the FND: OA Framework REST Service Audit Enabled (FND_OAF_REST_LOG_ENABLED) profile option to Yes.

    This enables the REST service auditing feature. The default value is No.

  2. Set the following server logging profile options for the app users:

    • FND: Debug Log Enabled (AFLOG_ENABLED)

      Set this profile option to Yes to enable the debug logging.

    • FND: Debug Log Module (AFLOG_MODULE)

      Set this profile option to fnd.framework.rest.Auditing%, <other REST service modules as applicable>

      For example, to obtain logs for the Oracle Mobile Approvals for Oracle E-Business Suite app, set the profile option to the following: fnd.framework.rest.Auditing%, fnd.wf.worklist%

      To retrieve logs for auditing, follow the steps described earlier in Enabling Server Logging. However, use fnd.framework.rest.Auditing as the Module name instead of the module name of the app, along with the app user name as the search criteria to locate the logs.

    • FND: Debug Log Level (AFLOG_LEVEL)

      Set this profile option to at least the EVENT level in order for the auditing feature to work.

    If you want to use both logs and auditing to troubleshoot an issue with the underlying REST services, set the FND: Debug Log Level profile option to STATEMENT and set the FND: Debug Log Module profile option as described in this section.

Enabling Logging and Diagnostics for Oracle Maintenance for EBS

Oracle Maintenance for EBS uses the server logging, client logging, and REST auditing features to help troubleshoot any issues if occur.

Additionally, this section includes the following troubleshooting information on potential problem symptoms and corresponding solutions.

Enabling Server Logging

Oracle Maintenance for EBS uses the same server logging feature, described earlier for Oracle Approvals for EBS, Oracle Self-Service HR for EBS, and Oracle Timecards for EBS.

If a user of the Oracle Maintenance for EBS app reports a problem, an administrator can set the following profile options for that user to enable logging, control the logging level, and set the module for which logs are recorded. These profile options are also used if app users need to upload their client log files to the server.

For more information on how to enable server logging, see Enabling Server Logging.

Enabling REST Service Auditing

Similar to enabling REST service auditing information explained earlier, Oracle Maintenance for EBS needs to enable the auditing feature for REST service request and response payloads during the service invocation.

For more information on how to enable REST service auditing, see Enabling REST Service Auditing.

Enabling Client Logging

If a user of Oracle E-Business Suite mobile apps reports a problem when using the app, and Oracle Support requests client logs, the following profile options set on the server for the server logging are also required for the client logging. These profile options enable the log upload service invoked by the mobile app to provide the upload feature.

Note that the same logging profile options are used to enable the server and client logging, as well as the REST service auditing. It is recommended that you use the following sequence when troubleshooting both server and client code at the same time.

  1. Turn on the server logging to obtain log statements written by REST services. For information on setting profile options for server logging, see Enabling Server Logging.

  2. Direct the app user to turn on diagnostics logging on the mobile client.

  3. Direct the app user to reproduce the issue that invokes the REST services.

    Log statements from the REST services should be recorded. However, the server cannot receive the client log file at this point.

  4. Set the profile options as described in this section for the user to receive the client log file.

    The client and server logging can happen at the same time when an issue is being reproduced. However, to upload the log file, the profile options should be changed to receive the log file after the issue is reproduced.

  5. Request the mobile app user to upload the log file from the mobile client to the server.

  6. Retrieve the REST service log statements based on the profile options set in step 1.

  7. Retrieve the mobile client log file uploaded based on profile options set in step 4.

Uploading Client Logs to the Oracle E-Business Suite Server

If mobile app users can access to the app, direct the users to perform the following steps to collect the logs from the mobile client:

  1. In the navigation menu of the mobile app, tap Settings and then the Diagnostics.

    On iOS: Settings Screen

    the picture is described in the document text

    In the Diagnostics screen, enable the client logging feature by turning on the Logging option.

  2. Return to the navigation menu and reproduce the reported issue.

  3. In the menu, tap Settings and then the Diagnostics again.

  4. In the Diagnostics screen, tap the Upload icon on the top right corner. This displays the upload screen where app users can upload the log files recorded for the app to the Oracle E-Business Suite server.

    On iOS: Diagnostics Screen with the Upload Icon Highlighted

    the picture is described in the document text

  5. You can then download the uploaded log files from the Oracle E-Business Suite server.

    To retrieve client logs, follow the steps described in Enabling Server Logging. However, use the following search criteria to locate the client logs:

    • User: Enter the mobile app user name.

    • Module: Enter your Application Bundle Id com.oracle.ebs.scm.eam.Maintenance as the Module name.

      For information on Application Bundle Id for each mobile app, see Appendix C: Application Definition Metadata.

Please note that if the FND: Diagnostics profile option is enabled for a user, the complete error stack from the service invocation failure appears. Otherwise, only a simple error message is shown instead.

Retrieving Client Logs Directly From Android Mobile Devices

If mobile app users are unable to access or log in to the app, the users will not be able to upload the logs to the server from the mobile client. In this situation, direct the Android users to retrieve client logs directly from their mobile devices instead.

Note: The option of retrieving client logs directly from iOS devices is not available.

  1. Use a file browser app on Android. For example, My Files, ES File Explorer.

  2. Look for files that start with the app name. For example, Maintenance.txt, Maintenance_bak.txt.

  3. Attach these files to an email through your preferred email app and upload to Oracle Support.

Troubleshooting Tips

This section includes the following troubleshooting information on potential problem symptoms and corresponding solutions.

For information about each app's definition metadata that may help identify the app in various troubleshooting processes, see Appendix C: Application Definition Metadata.

If you contact Oracle Support about an app, specify the associated product name for that app. See Appendix E: Associated Products in My Oracle Support.

Troubleshooting Tips on the Mobile Client

This section describes the troubleshooting tips on the mobile client. It includes the following topics:

Directing Users to Obtain Connection Details and Download Updates from the Server

When trying to diagnose and troubleshoot issues encountered on the mobile client, you can direct users to obtain the server connection details from their mobile devices and check if any new updates from the server are required.

Perform the following steps to obtain the connection details and initiate server updates:

  1. In the navigation menu of the mobile app, tap Settings and then Connection Details. The Connection Details screen appears.

  2. The Connection Details screen displays the server URL field and the Server Configuration region.

    • Server URL field: This is the URL value entered by the mobile user during the initial launch of the app. This value is retrieved from the local database in the device.

      If the mobile user wants to reconfigure the app to a different Oracle E-Business Suite instance after the initial setup is complete, the user can change the server URL value by tapping the Change URL button, as shown on the left. The app displays the device's Settings screen where the user can update the server URL directly.

      Note: When a user reconfigures an app from one Oracle E-Business Suite instance to another, the local preferences are completely removed. After the configuration, the user is required to set the preferences again.

      On iOS: Connection Details Screen with the "Change URL" Button

      the picture is described in the document text

      Note: Administrators can preconfigure the server URL and also determine if users can change the default URL value. If the server URL is preconfigured and users are not allowed to change the value, then Change URL will not be displayed. Instead, "Your administrator has configured the app to connect to this server URL. You cannot change this setting." message appears, as shown on the right.

      For information on preconfiguring server URL, see Setup Tasks for Deploying Mobile Apps with Enterprise Mobility Management Solutions.

      The user can navigate to the device's Settings screen to change the server URL if desired:

      • From the iOS device's Settings screen, tap Settings, then App Name, and then Server URL.

      • From the Android devices with the app open, tap Settings, then Settings or Preferences, and then Server URL.

    • Server Configuration region: This region displays the parameter values in the configuration file downloaded from the server.

      • Last Updated: The date and time when the app was last updated.

      • Service Version: The internal version of the mobile services used by the app, obtained from the app's definition metadata. For example, 1.0.0.

      • Authentication Type: The selected authentication type is displayed.

      • Session Timeout: The number of seconds that a user can remain logged in to the app.

      • Idle Timeout: The number of seconds that the app can remain idle.

      • Service Endpoint: The value used to invoke Oracle E-Business Suite services. This value can either be the same as the server URL entered by the user, or a dedicated web entry point for this app.

  3. Direct users to check if any new updates from the server are required for the app.

    Oracle E-Business Suite mobile apps automatically download the mobile app configuration updates from the Oracle E-Business Suite server. Users no longer need to initiate a download manually within an app. Instead, each app periodically checks for updates (once every five times the app is restarted) and downloads them to synchronize with the configuration details defined on the Oracle E-Business Suite server. However, if required, users can still initiate the manual update by tapping the Sync icon as in the previous releases.

    Direct users to follow the instructions on the mobile device to continue the updates from the server. For example, a user must restart the app to apply the updates if either one of the following attributes from the server is different from the value in the device:

    • service endpoint

    • authentication type

    If only the timeout values need to be updated, the user can choose to continue using the app without restarting it immediately. In this case the updates will be applied the next time the app is launched.

Troubleshooting Tips for Oracle E-Business Suite Mobile Apps

The following table lists common issues that might occur while using Oracle E-Business Suite mobile apps as well as the corresponding solutions.

Troubleshooting Tips on the Mobile Client
Issue Tip
When a user enters a server URL in a mobile device using HTTPS, if the TLS certificate is untrusted and cannot be recognized by the mobile app, the following error message may appear:
"Unable to connect to the Oracle E-Business Suite server. Please enter a valid server URL."		 Ensure that your mobile app can perform a successful TLS handshake with the Oracle E-Business Suite TLS endpoint.

  1. Validate that the JDK 8 client can connect to the Oracle E-Business Suite TLS endpoint.

  2. Validate that the Oracle E-Business Suite TLS endpoint presents the complete certificate chain.
After a user enters valid user credentials in the standard login screen, the app displays the loading indicator for a few seconds and then redirects the user back to the login screen. Ensure that the server URL used by the user to configure the app matches the Oracle E-Business Suite web entry URL. Otherwise, Oracle E-Business Suite server might reject the REST requests from the mobile app which will result in redirecting the user to the login screen.
When a user initiates the check for updates process by tapping Settings from the mobile app navigation menu, then tapping Connection Details, and then tapping the Sync icon in the Connection Details screen, the user is redirected to the login screen. After logging in to the app, the user is taken to the default landing screen.
The same issue also occurs if a user tries to navigate to a different feature after the app has idle timed out, the user is redirected to the login screen. After the user logs in to the app, instead of taking the user to the desired screen before the timeout, the app redirects the user to the default landing screen.		 To resolve the issue, apply Patch 22046560:R12.FND.C.
It is recommended that you apply this patch after the corresponding consolidated product family patch for your app to avoid the issue.
After a user enters valid user credentials in the standard login screen after the configuration screen, the following error occurs:
The login server is not reachable.		 The cause of the issue could be either that the HTTP server is down or the login server was not installed or set up correctly during the installation of the appropriate patch on your Oracle E-Business Suite server.
The URL for the login server used by mobile apps is in the following format: http(s)://<hostname>:<port>/OA_HTML/RF.jsp?function_id=mLogin
Please note that this is not a URL that the app users would enter or edit. It is constructed during the app setup and loaded to the mobile app through the configuration file. If this URL value is invalid in the configuration file, the users will not be able to log in to Oracle E-Business Suite.
Before allowing users to connect to Oracle E-Business Suite from mobile apps, ensure the right login server URL is set up in the configuration file, as described in Validating the Configuration.
Additionally, you can test the login server URL by copying the URL and pasting it in a web browser. A pop-up window should appear for user name and password. After you successfully enter valid user credentials, an XML response should appear with the following elements: accessToken, accessTokenName, ebsVersion, and userName.

Note: When an app user is authenticated, the mLogin REST service creates an Oracle E-Business Suite session for that user along with an XML response with authentication token (cookie) which uniquely identifies that session. To secure each user session, a profile option "FND: Authn Service Token Scope (FND_AUTHN_SRVC_TOKEN_SCOPE)" is introduced in the January 2023 Critical Patch Update with the default value "Header Only" at the Site level. This default value sets the ICX cookie only in the response header of the mLogin REST service, and will not return the cookie details in the response payload. If you have custom code that calls the mLogin REST service and requires the cookie details in the response payload, then you can optionally change the value to "Header and Body". In this case, the mLogin service sets the ICX cookie in the header and also returns the cookie name and value in the payload.
A mobile user fails to log in to an app. When an administrator tests the standalone mLogin REST service by entering the URL http(s)://<hostname>:<port>OA_HTML/RF.jsp?function_id=mLogin or tests the configuration service URL http(s)://<hostname>:<port>OA_HTML/RF.jsp?function_id=mConfig&bundleId=<application bundle id>&file=ebs-mobile-config.xml, one of the following errors occurs:
Resource/rest NOT found
or
HTTP 500 Internal server error		 Perform the following steps to resolve the issue:

  1. Verify if AOLJRestServlet exists by locating the servlet in the $OA_HTML/WEB-INF/web.xml file.

  2. If AOLJRestServlet does not exist, then verify if the app uses a custom template.

    • If a custom template is used, the custom template must be synchronized with the seeded templates. See Section 4.2: Implementing AutoConfig Customizations, My Oracle Support Knowledge Document 387859.1.

    • If a custom template is not used, continue to the next step.

  3. Run AutoConfig and ensure there is no error.

  4. Stop and restart the application tier server and then verify the issue.
After a user enters user credentials in the standard login screen after the configuration screen, the following error occurs:
Invalid username/password. If the problem persists, please contact your system administrator		 To resolve the issue, ensure that the user enters a valid user name and password. Verify the user name is still valid in the system and reset the password if required.
After a user enters valid user credentials in the standard login screen after the configuration screen, the following error occurs:
One or more parameters downloaded from the server are invalid.
The same error can also occur after the user initiates the check for updates process by tapping Settings from the mobile app navigation menu, then tapping Connection Details and then tapping the Sync icon in the Connection Details screen.		 This is due to invalid configuration data, such as invalid service endpoint, in the downloaded configuration file.
To resolve the issue, ensure that a valid service endpoint is specified in the Configure Mobile Applications page while setting up the mobile app.
After a user enters valid user credentials in the standard login screen after the configuration screen, the following error occurs:
An error occurred when downloading updates from the server.
The same error can also occur after the user initiates the check for updates process as described above.		 To resolve the issue, ensure that there is no server or network connection issue.
A mobile user may find that the date and time information in the mobile device is different from that in the desktop pages. This difference occurs because the mobile app displays the time zone and date and time information based on the settings specified in the mobile client's Settings screen. Tap Settings, then General, and then Date & Time in the iOS mobile Settings screen or tap Settings and then Date & Time in the Android Settings screen to set your preferences.
After modifying the Server URL through the iOS mobile Settings screen (tap Settings, then App Name, and then Server URL) or the Android device's Settings screen (tap Settings, then Settings or Preferences, and then Server URL), the user closes and restarts the app. The app displays the page with the message "The server URL has changed.", but the Server URL field is blank. If the user removed the previous URL in the device settings but did not enter a new URL, then no value is shown for the Server URL field.
During the initial configuration of an app, after a mobile user enters a server URL and taps Get Started, the following error message appears:
Please enter a valid URL.		 Ensure the server URL is valid by performing the following steps:

  1. Check if the user has entered http:// or https:// as appropriate for accessing your Oracle E-Business Suite server.

  2. Make sure that the user has entered the correct host name and domain.

  3. Make sure that the port number if used is valid.
During the initial configuration of an app, after a mobile user enters a server URL and taps Get Started, the following error message appears:
This mobile application is not currently configured on this server.		 This message appears because the required Oracle E-Business Suite Mobile Foundation patches have not been applied on the Oracle E-Business Suite server to which the app is connecting.
Apply the patches described in Applying Server-Side Patches for Oracle Maintenance for EBS in order for the user to proceed through the page where the server URL value is entered.
After a user enters valid user credentials in the standard login screen after the configuration screen, the following error occurs:
Configuration Error - This mobile application is not currently enabled on this server. Please close the application.		 The app may be already configured but the status is set to "Disabled".
In order for the apps to successfully access the configuration files, set the status of the app to "Enabled". For information on configuring Oracle E-Business Suite mobile apps, see Configuring the Mobile Apps on the Oracle E-Business Suite Server.
After entering a new server URL through the Connection Details page in Oracle E-Business Suite Mobile Foundation Release 3.0 or later releases, or through the mobile Settings screen (tap Settings, then App Name, and then Server URL from the iOS Settings screen or tap Settings, then Settings or Preferences, and then Server URL from the Android Settings screen), the user returns to the app. The app still connects to the previous Oracle E-Business Suite instance. After changing the server URL, the user must restart the app to initiate the reconfiguration flow.
After a user enters valid user credentials in the standard login screen after the configuration screen, the following error occurs:
Configuration Error - This mobile application is not currently configured on this server. Please close the application.		 This error indicates that the app's status is "Not Configured". This means the administrator has not yet configured the app with appropriate configuration parameters or has not completed a mandatory setup required to use the mobile app.
For information on setting the configuration parameters for your mobile app, see Configuring the Mobile Apps on the Oracle E-Business Suite Server.

Troubleshooting Tips on the Oracle E-Business Suite Server

This section describes the troubleshooting tips on the Oracle E-Business Suite server. It includes the following topics:

Troubleshooting Tips on the Oracle E-Business Suite Server

The following table describes common issues that might occur on the Oracle E-Business Suite server as well as the corresponding solutions.

Troubleshooting Tips on the Oracle E-Business Suite Server
Issue Tip
If administrators preconfigure Server URL in an Enterprise Mobility Management (EMM) console through the Server_URL property or in ebs.properties when EMM is not used, after an app user launches the app, the following error may appear:
Unable to connect to the Oracle E-Business Suite server. The server URL may be invalid.		 To resolve this issue, perform the following steps to verify the preconfigured Server URL in ebs.properties or an EMM console to make sure:

  • This preconfigured URL has a valid format: http(s)://<host>:<port>

  • Enter the URL in a web browser and make sure that you are able to access the Oracle E-Business Suite home page successfully.

  • From a web browser, invoke the login service as http(s)://<host>:<port>/OA_HTML/RF.jsp?function_id=mLogin and verify that it prompts for user name and password.
After applying the appropriate patch for your Oracle E-Business Suite release, the Mobile Applications Manager responsibility is still not visible for SYSADMIN user by default. Perform the following steps to resolve the issue:

  1. Make sure the concurrent manager is running.

  2. Submit a concurrent request for the "Workflow Directory Services User/Role Validation" concurrent program (FNDWFDSURV).

    Ensure that you set the "Add missing user/role assignments" parameter to Yes. You can leave the other parameters set to the default values.

  3. Submit a concurrent request for the "Compile Security" concurrent program.
Users need to access the Mobile Applications Manager responsibility. The SYSADMIN user is granted the Mobile Applications Manager responsibility by default.
The SYSADMIN user can assign the responsibility to other users through the "Mobile Application Administrator" user role in User Management.
After you select the Mobile Applications Manager responsibility and the Applications link from the navigation menu and perform a search in the Search Mobile Applications page, no mobile applications are listed in the search result table. Ensure all the prerequisite patches required for your mobile apps are applied. If the desired applications still do not appear in the search result table, contact Oracle Support.
A configuration parameter such as Timeout was modified on the server and the configuration file is regenerated. The current app users do not have the parameters updated. To resolve this issue, a mobile user can initiate the server updates from the mobile device. See Directing Users to Obtain Connection Details and Download Updates from the Server.

Troubleshooting Tips on Configuring Apps With the Apps SSO Login Authentication Type

This section describes the troubleshooting tips that are particularly related to configure mobile apps with the Apps SSO Login (previously known as "Web SSO") authentication type.

For information about configuring apps with the Apps SSO Login authentication type, see:

Troubleshooting Tips

Perform the following tasks to validate and troubleshoot potential issues for configuring mobile apps with the Apps SSO Login type:

  1. Verify prerequisite configuration for Oracle E-Business Suite, Oracle Access Manager (OAM), and Oracle Directory Services integration

    1. Navigate to the application login page through a web browser. Verify the login redirects to Oracle Access Manager as configured during the Oracle E-Business Suite integration with Oracle Access Manager, and the same LDAP user that will be using a mobile app can log in successfully to Oracle E-Business Suite framework based applications.

    2. Verify after successful login and rendering of the Oracle E-Business Suite Home page, the user has Oracle E-Business Suite responsibilities assigned.

    3. Ensure the administrator has configured the specific configuration tasks, as described in Setup Tasks for Oracle Maintenance for EBS.

  2. Test the configured "SSO Login URL", "SSO Login Success URL", and "SSO Logout URL" parameters

    1. Navigate to the configured SSO Login URL through a web browser. After the login, the browser should return a protected page successfully (Status 200 OK). The URL for this page must be the same as the configured SSO Login Success URL.

      Note: The "SSO Login URL" and "SSO Login Success URL" parameters relate to each other. The values of these two parameters can be the same.

      Do not configure a URL, such as http://<hostname>:<port>/OA_HTML/AppsLogin, as the SSO Login URL because this page would unnecessarily redirect to the Oracle E-Business Suite Home page after the login. Use the default SSO Login URL http://<hostname>:<port>/accessgate/login/sso instead.

    2. Navigate to the configured SSO Login URL through a web browser. For example, http://<hostname>:<port>/accessgate/login/sso.

      Note: When you test the login/sso or login/apps (as described later in step 3 for "EBS Session Service") service standalone from a web browser, it is recommended sending the X-Ebs-Wep request parameter that is supported in Oracle E-Business Suite AccessGate (EAG) 1.3.2.1 and above with Oracle E-Business Suite web entry URL (http(s)://<hostname>:<port>).

      If EAG does not receive this parameter, the login/apps service may fail and an "Initialization failed -1" error is captured in EAG logs. In this situation, ensure you pass this X-Ebs-Wep request parameter while testing the service standalone from a browser.

      Expected result: Redirect to the OAM login page. Login successful after specifying the LDAP user name and password.

      After the login, the resource http://<hostname>:<port>/accessgate/login/sso shows with no error message. This resource must be the configured "SSO Login Success URL" parameter value.

      Note: The "SSO Login URL" and "SSO Login Success URL" parameter values can be the same.

      The browser shows a blank page successfully.

    3. Navigate to the configured SSO Logout URL. For example, http://<hostname>:<port>/accessgate/logout/sso.

      Expected result: User logged out successfully.

    4. Perform the same tests using your mobile device browser.

  3. Test the configured "EBS Session Service" parameter

    1. Navigate to the configured EBS Session Service through a web browser. For example, http://<hostname>:<port>/accessgate/login/apps.

      Expected result: Redirect to the OAM login page. Login successful after specifying the LDAP user name and password.

      After the login, the browser returns an xml file containing an access token and the user name for the user that just logged in. For example:

      <response>
<data>
<accessToken>xxxxxxxxxxxxxxxxxxxxxxxxxx</accessToken>
<accessTokenName>emsxxxxx</accessTokenName>
<ebsVersion>12.2.5</ebsVersion>
<userName>xxxxx</userName>
</data>
</response>

    2. Perform the same test using your mobile device browser.

  4. Collect HTTP header traces and logs

    1. Collect HTTP Header traces during the implementation of the above test points.

    2. Collect log files for Oracle E-Business Suite AccessGate, Oracle E-Business Suite oacore, and the OAM server.

      Refer to My Oracle Support Knowledge Document 1077460.1, Troubleshooting Oracle Access Manager and Oracle E-Business Suite AccessGate, on how to generate Oracle E-Business Suite AccessGate logs.