This chapter discusses how to perform diagnostic testing for the Oracle Mobile Application Foundation and the Oracle Mobile Field Service Store and Forward applications.
This chapter covers the following topics:
Diagnostic testing can be done for the Oracle Mobile Application Foundation and the Oracle Mobile Field Service Store and Forward applications. This chapter describes how to run these diagnostics. After your initial implementation, you should run the entire set of pre-seeded diagnostic tests to verify that the implementation has been successful. Subsequently, the tests can be run whenever a problem arises.
Please refer to the Oracle Applications CRM System Administrator's Guide or the online help for the CRM System Administrator Console for instructions on how to use the Oracle Diagnostics for Applications user interface.
Running Pre-Seeded Tests
Use the following procedure to run the pre-seeded Oracle Mobile Application Foundation diagnostic tests:
Steps
Log in to the CRM System Administrator Console as a system administrator.
Click the Diagnostics tab.
Select CRM Gateway for Mobile Services from the Application drop-down list.
Click Advanced.
You can run any of the following pre-seeded tests.
The following table lists diagnostic tests, their descriptions, and associated symptoms and resolutions.
| Test | Description | Symptom | Resolution |
|---|---|---|---|
| Oracle Lite Setup | Checks if the Oracle10g Lite version installed is correct. Checks if the database access permissions for the Oracle10g Lite schema are set properly. | An error occurs while applying mobile application patches. | Review the diagnostic report and schedule or install/apply the correct Oracle10g Lite patches. |
| Mobile Concurrent Program Setup | Checks if all the mobile concurrent programs are working. | Changes from the mobile client are not applied to the enterprise system. Users are not able to synchronize. They might get invalid username/password errors. Many mobile application concurrent programs are not working. |
Review the diagnostic report and schedule or run the concurrent program to apply changes. |
| Mobile User Hook Registration | Checks if mobile applications register vertical user hooks properly and the execute flag is set to run. | Changes on JTF Notes, CS Counter, or CSI Item Instance on the enterprise do not synchronize to the mobile device. | Reapply the JTM patch to register and set up the execute flag to run. |
| Mobile Framework Setup | This test verifies the Configuration Setup for the mobile framework. | Application publishes incorrectly or synchronization fails. | Change the scripts and republish the application. |
| Mobile Application Upgrade History | This report shows the status of mobile application upgrades. | Upgrades fail. | Republish the application. |
| User Summary | This test shows the User Status Summary. | Users are not created properly. | Look at the test results and rerun the MANAGES MOBILE USER concurrent program. |
| User Detail | This test provides detailed information about a specified mobile user. | Need to investigate user history. | View user history and take appropriate action. |
Run diagnostic tests to ensure that the install and operation of the Oracle Mobile Field Service Store and Forward applications is correct.
Steps
Complete the following steps to access the diagnostic screens of the enterprise application:
Log in to the CRM System Administrator Console as a system administrator.
Click the Diagnostics tab.
Depending on your mobile computer device, select either Oracle Field Service/Palm or Oracle Field Service/Laptop from the Application drop-down list.
Note: The Oracle Field Service/Palm responsibility is used for the Oracle Mobile Field Service/Pocket PC application.
The Diagnostics application displays the Test Summary table and a table showing any failures in the past week.
Click the Advanced tab.
In the Advanced tab, enter the parameters for the test that you want to run. From the Basic tab, you can run all non-parameter tests for the application.
Refer to the Oracle Applications CRM System Administrator's Guide or the online help system to learn how to use the Diagnostics Framework user interface.
The client-side tests run automatically on the mobile computer device when you open an Oracle Mobile Field Service Store and Forward application. You can also run these tests any time to verify the correct setup of the Oracle Mobile Field Service Store and Forward application.
The following table lists diagnostic tests, test descriptions, observed symptoms, and proposed resolutions for Oracle Mobile Field Service Store and Forward - Laptop:
| Test for Oracle Mobile Field Service Store and Forward - Laptop | Location | Problem | Resolution |
|---|---|---|---|
| JTM Master Concurrent Program | Backend | Are the concurrent programs running? | Provides detailed diagnostic information about the JTM Master Concurrent Program. If necessary, it tells system administrators which settings should be modified. |
| Environment Setup | Backend | Is the environment correct? | Provides support for debugging the configuration of Oracle9i Lite. It enables the administrator to check if the recommended settings are followed correctly. It also helps in identifying common issues with external authentication, installation manager, profile option values, and so on. |
The following table lists diagnostic tests, test descriptions, observed symptoms, and proposed resolutions for Oracle Mobile Field Service Store and Forward - Pocket PC:
| Test for Oracle Mobile Field Service Store and Forward - Pocket PC | Location | Problem | Resolution |
|---|---|---|---|
| Responsibility | Backend | User may not have proper responsibility. | Assign proper responsibilities. |
| Profile values | Backend | Profile values for Field Service Palm are not set. | Set profile values. |
| User Hooks Registration | Backend | Hooks registration is not done. | Contact your Oracle technical support representative. |
| Check Concurrent Program | Backend | All required concurrent programs might not be running. | Make sure that the concurrent programs are running. |
| JTM Concurrent Program registration | Backend | For JTM Concurrent Program APIs are not registered. | Contact your Oracle technical support representative. |
| JTM Master Concurrent Program | Backend | Are the concurrent programs running? | Provides detailed diagnostic information about the JTM Master Concurrent Program. If necessary, it tells system administrators which settings should be modified. |
| Environment Setup | Backend | Is the environment correct? | Provides support for debugging the configuration of Oracle9i Lite. It enables the administrator to check if the recommended settings are followed correctly. It also helps in identifying common issues with external authentication, installation manager, profile option values, and so on. |
| Task diagnostic | Backend | Task is assigned incorrectly. | Assign task correctly. |
| Check required list of values | Backend | List of values are empty. | Create all list of values. |
This section describes how to configure debug logging for troubleshooting problems with mobile operations.
Oracle Mobile Field Service Store and Forward applications use the CRM Technical Foundation logging framework to log messages to a central repository that is shared by both the database and the middle tier servers. Each log message belongs to one of the following severities:
Statement
Procedure
Event
Exception
Error
Unexpected
UI screens give system administrators convenient and simple controls for configuring and viewing the logs. Refer to the Oracle Applications CRM System Administrator's Guide or the online help for the CRM System Administrator Console to learn how to use the logging screens.
Steps
Complete the following steps to configure logging for all modules:
Log in to the CRM System Administrator Console as a system administrator.
Navigate to Setting > System > Debug Logging > Configuration.
Set the following values:
Enabled = ON
Level = Statement
Repository = Database
Module filter = include string csm%, asg%, jtm%
Click Update to save the values.
Bounce Apache (the middle-tier server).
Note: Turn the logger off after you finish troubleshooting. This changes the values of the above fields back to their original values. Logging at this level of detail consumes resources and could impact the performance of your system.
In addition to these logs, you can use the Oracle10g Lite mobile server logging facility to troubleshoot problems with user synchronizations. Refer to the Oracle10g Lite Mobile Server Administration Guide for more details.
This section describes the most common issues encountered in the implementation of the Oracle Mobile Field Service Store and Forward applications.
Viewing Items Stocked in a Subinventory
Problem
Trackable items that have been stocked in a subinventory are not displayed in the inventory list of the application.
Resolution
This may be a replication issue. Please check that the installed base instances have been created for the stocked items in the back of the database. If the instances do exist but the items still do not display on the laptop, please contact Oracle Support.