This chapter discusses the mechanisms used for the administration and troubleshooting of Oracle Mobile Field Service - Wireless and Voice.
This chapter covers the following topics:
Administrators can verify Mobile Field Service - Wireless user setup and other system level settings by using the Mobile Field Service Wireless and Voice Debug page.
A simple HTML page.
A quick tool for System Administrators to provide required information while logging a TAR.
Various debugging information displayed in a well formatted manner.
The Debug page contains the following:
User and profile information.
Basic user information.
Basic user information such as, user name, resource ID, wireless responsibility ID and name, and default subinventory.
Profile values for the user.
Profile values used in the Mobile Field Service - Wireless and Voice applications for the logged in user.
Task and service request information.
Service request data related to the task.
Useful information for the service request related to a given task number.
Task details.
Brief details of the given task number.
Contact, Task Assignment, and Task Status details.
Related information for the task number.
Environmental information.
Middle tier and database information.
Technical information about the middle tier and database such as, JRE, OJSP compiler, JDBC driver, and database versions.
Java classpath entries.
All the classpath entries.
JDBC connections pool and invalid database objects.
JDBC connection pool status in terms of total available connections, used and free connections.
List of any CSF invalid database objects.
File versions.
JSP and Java file versions.
File versions of Field Service Wireless JSP and Java files.
To access the Debug page use this procedure:
Enter the following URL in any web browser: http://{host}:{port}/OA_HTML/csfwDebugValues.jsp
Login in with user for which you want to view the user and profile information.
Provide task number for which you want to view the task and service request information.
Provide the profile name apart from profiles displayed under "User & Profile Information", to view the profile values for the logged in user.
Note: This activity applies only if Oracle iAS Wireless Server is implemented for Oracle Mobile Field Service - Voice.
In the case where the user receives "Service Error", the administrator can check for the error details in the Oracle AS Wireless Server log file.
The log file is located at: $WIRELESS_OH/wireless/logs/log.xml
Important: Make sure you truncate this log file periodically to avoid any performance issues.
Note: This activity applies only if Oracle iAS Wireless Server is implemented for Oracle Mobile Field Service - Voice.
The Oracle AS Wireless server acts as a virtual browser between the Oracle E-Business Suite and the end user device. To log the entire HTTP traffic between Oracle AS Wireless and the back-end application you have to modify the $WIRELESS_OH/opmn/conf/opmn.xml file and add the following in the start section for OC4J_Wireless:
-DHTTPClient.log.mask=-1 -DHTTPClient.log.file=$ORACLE_HOME/wireless/logs/http.log
For example, after the change, that section will look something like this:
<category id="start-parameters">
<data id="java-options"value="-server
-Djava.security.policy=$ORACLE_HOME/j2ee/OC4J_Wireless/config/java2.policy
-Djava.awt.headless=true -Xmx256m -Djava.awt.headless=true
-Doracle.wireless.oraclehome=$ORACLE_HOME
-Doracle.wireless.home=$ORACLE_HOME -DHTTPClient.log.mask=-1
-DHTTPClient.log.file=$ORACLE_HOME/wireless/logs/http.log"/>
<data id="oc4j-options" value="-properties
-userThreads"/>
</category>
Important: Do not modify the opmn.xml directly. You need to use the EM web GUI.
After the change you have to restart the OCJ4_Wireless process. If you have configured it correctly you should see a new file $WIRELESS_OH/wireless/logs/http.log immediately after OCJ4_Wireless comes up.
Note: You should remove/comment these lines from opmn.xml file and restart OCJ4_Wireless process after you complete the debugging process.
This table lists some of the issues that may occur when implementing Oracle Mobile Field Service - Wireless and the recommended solution:
| Issue | Solution |
|---|---|
| Not getting Signature Capture control for Microsoft Windows Mobile 6.0. | In the device, make sure that you have installed the Signature Capture plugin for the right CPU type. Also make sure that you have added a valid User-Agent name for the Device Metadata. For more information, see OracleMy Oracle Support. |