No data is retrieved into the DataWindow when running the Web application.
Cause A: If you are using the SAP ASA/SQL Anywhere database, a possible reason is that the SAP ASA/SQL Anywhere version specified in the Transaction object is different from what is specified in the data source. The application cannot find DataWindow objects and fails to retrieve any data from the database.
Solution A: For SAP ASA/SQL Anywhere, version 7.xx, 8.xx, and 9.xx are supported. Appeon 6.x supports both dynamically mapping the Transaction object to the data source in scripts, and statically specifying the data source in AEM. The user has to set the correct SAP ASA/SQL Anywhere version in DBParm or select the correct SAP SQL ASA/Anywhere version in AEM.
Cause B: If you are using the ASE database and find the following information in the Appeon log, "Failed to retrieve datastore... Produced the following error: Select error: Stored procedure '...' may be run only in unchained transaction mode. The 'SET CHAINED OFF' command will cause the current session to use unchained transaction mode.", a likely cause is that the connection mode (chained or unchained) set up by the JDBC driver is not the same as the mode of the stored procedure (chained or unchained).
Solution B: You can modify the PowerBuilder source code using any of the following workarounds to fix the problem.
-
Execute "SET CHAINED OFF" before running stored procedures
-
Execute "connection.setAutoCommit(true)" before running stored procedures
-
Change the AutoCommit property to true before running each stored procedure
-
Use the "sp_procxmode <procname>, anymode" command to set the stored procedure to run in chained or unchained mode.
Cause C: There are various factors that may cause this problem. Some examples include; running an incompatible PowerBuilder version with Appeon, data sources, not running or incorrectly configured, and missing INI files.
Solution C-1: If the application uses an INI file, verify the INI file is added to the Appeon Developer application profile before deployment. Add the necessary INI file and redeploy the application.
Solution C-2: If the problem is occurring with an Appeon provided demo application:
-
Verify that the PowerBuilder version meets the requirements specified in Installation Guide for Appeon for PowerBuilder.
-
Verify that appeondb is running - a SQL Anywhere icon with the hover text "Appeondb" displays in the Windows Task Bar.
-
Verify that EAServer has been started.
-
Login to EAServer using EAServer Manager and verify that you can ping both the "appeondb" and "appeonsample" data sources successfully. If the data sources cannot be pinged successfully, refer to Fail to ping appeondb data source and Fail to ping appeonsample data source for troubleshooting tips.
-
Verify that "<data-cache>appeondb</data-cache>" exists in %JAGUAR%\appeon\repository\%instancename%\config\server-config.xml (Windows) or $JAGUAR/appeon/repository/$instancename$/config/server-config.xml (UNIX).
Solution C-3: If the problem is occurring with all applications except the Appeon demo applications, check the following:
-
Verify that the PowerBuilder version meets the requirements specified in Installation Guide for Appeon for PowerBuilder.
-
Verify that the database used for your application is running correctly.
-
Verify that EAServer is running.
-
Log in EAServer using EAServer Manager and verify that pinging the data source is successful. If pinging the data source fails, perform the following steps (see Appeon Server Configuration Guide for J2EE for detailed instructions):
-
Verify the data source properties are correctly configured especially the server name, username and password used to connect to the database.
-
Make sure the JDBC radio button is checked in the Driver tab of the Data Source Properties
-
Make sure that the driver string is entered correctly. The string is case sensitive.
-
Make sure that the "enable cache-by-name access" option is checked in the Cache tab.
-
For an Oracle database, you may need to add the data source property com.sybase.jaguar.conncache.check and have it set to select 1 from dual.
-
If using a data source with the iAnywhere JDBC driver, refer to the section called “Data source parameters for SAP ASA/SQL Anywhere” in Appeon Server Configuration Guide for J2EE and double-check the settings created.
-
Verify the Transaction Object settings in Appeon Enterprise Manager are correct. For detailed instructions on setting up AEM, refer to Appeon Server Configuration Guide for .NET or Appeon Server Configuration Guide for J2EE.
-
Make sure that the application has been added into the application list displayed in AEM Console > Application > Transactions > Transaction Objects.
-
Make sure that the application has the correct transaction object name(s) listed, and the correct transaction object name(s) mapped to the correct data source(s). The transaction object name is case sensitive.
