This chapter contains the following topics:
Login Fails After User Launches the Mobile Enterprise Application
If the login fails after a mobile user launches the mobile enterprise application and enters the URL to connect to the server:
Make sure the mobile user has the correct URL. See Deploying and Managing the AIS Server through Server Manager in this guide for more information.
Make sure the AIS Server is up and running on the port specified in the deployment settings in Server Manager.
If the AIS Server is running, perform the following test to confirm that it is responding to requests:
In Server Manager, access the AIS Server instance.
Click the Test Connection link.
The resulting page shows the environment, role, and HTML Server.
Verify the settings in the resulting page against the settings for the AIS Server in Server Manager. If the settings are not in synch, correct any of the settings in Server Manager, test the connection, and then restart the AIS Server instance.
Make sure the HTML Server setting for the Allowed Hosts is configured properly. See Configuring the Allowed Hosts Setting for the EnterpriseOne HTML Server in this guide for more information.
Depending on the configuration of the AIS server that supports your organization's mobile applications, you might be required to sign into VPN on your mobile device before you can sign into a mobile application. Contact your system administrator to determine if this step is required.
Application Not Compatible with Server Error Message
After logging in, the following message appears:
"This application is not compatible with the server you are connected to."
The user will not be able to continue using the application. The administrator must upgrade the EnterpriseOne Tools release to a compatible level for the application.
For a list of the EnterpriseOne mobile enterprise applications and the minimum EnterpriseOne Tools release required to run them, see the following document on My Oracle Support (login required):
Information Center for JD Edwards EnterpriseOne Mobile Applications (Doc ID 1637232.2)
https://support.oracle.com/epmos/faces/DocumentDisplay?id=1637232.2
Data Dictionary Item with Global Override Causes Mobile Enterprise Application to Not Work as Desired
If a mobile enterprise application references a data dictionary (DD) item in EnterpriseOne, and the customer has updated the DD item in EnterpriseOne with a global override of the DD item description, the mobile enterprise application will throw a null pointer exception or an undefined error. The result is that the mobile enterprise application will not receive values from EnterpriseOne and the application will not work as desired.
A global override of the DD item description overrides a data item's row description and is not specific to any language or Jargon Code (system code). To fix this issue, in EnterpriseOne, remove the global override of the description and specify description overrides only for a specific language or Jargon Code. See "Understanding Jargon and Alternate Language Terms" in the JD Edwards EnterpriseOne Tools Data Dictionary Guide for more information.
Unable to View Data or Application Features
If login is successful, but users cannot see data or application features:
Make sure mobile users have the proper security permissions to access the EnterpriseOne mobile enterprise application.
Make sure mobile users have the proper security permissions to access the EnterpriseOne application used by the mobile enterprise application.
Make sure mobile users have the proper security permissions to access the data in the EnterpriseOne base application. If row security is defined that prevents users from seeing certain data in the base EnterpriseOne application, mobile users will not be able to see the data in the mobile enterprise application.
See the following topics in this guide for more information:
Setting Up Security for EnterpriseOne Mobile Enterprise Applications
Setting Up Security for Base EnterpriseOne Applications Used by Mobile Enterprise Applications
Unable to Work with Attachments
If you cannot work with media object attachments in a mobile enterprise application that supports attachments, you need to make sure that media object attachments are properly configured in the base EnterpriseOne application. Refer to the applicable base EnterpriseOne application documentation for more information. Use the following link to access the JD Edwards EnterpriseOne Applications Documentation Library: