Datawindow object missing in Client Browser when deployed in Remote Appeon Server

[T L Sreedharan]

Hi,

I am a new Appeon Developer

We are in the process of making our PB 12.5 Client server application work on Web Browser using Appeon Tool. While we deploy PB Application to Appeon Server (IIS Web server) installed on my local pc where PowerBuilder is installed and run the Application in IE locally I see no issues & everything works fine. I am able to see the datawindow objects & other objects just like the CS application.

But if I deploy the Application to Remote Appeon Server(IIS Web Server( and run the application from the local IE or in remote pc, Datawindow objects goes missing. I could only see a Blank Datawindow Control.

Appreciate your help in this regard
Sree

[katt...@appeon.com]

Hi Sree,

Did you run into any error when deploying the application? Please try the solution below to see if it can fix the issue. If it cannot fix the issue, then please provide us the appeonserver.log and appeonerror.log files to do further research, here is the article stating how you can get these log files: http://support.appeon.com/index.php?/Knowledgebase/Article/View/50/11/what-you-can-provide-to-us-for-further-debugging-when-you-run-into-the-appeon-server-related-issues.

Step 1: Adjust the value of the following parameters in the AppeonDev.ini file (located under C:\Program Files\Appeon\Developer2013\ and will be copied to the "bin" folder of application package by Appeon Package Wizard):

[DeployConfig]
BatchDWSynLen= 10000000
BatchDWSynNum= 200
BatchDWSqlNum= 500
BatchESqlNum=500

BatchDWSynLen specifies the length (in byte) of the DataWindow syntax, which when reached the deployment tool will commit to Appeon Server at one time.

BatchDWSynNum specifies the number of DataWindow syntax, which when reached the deployment tool will commit to Appeon Server at one time.

BatchDWSqlNum specifies the number of DataWindow SQL, which when reached the deployment tool will commit to Appeon Server at one time.

BatchESqlNum specifies the number of embedded SQL, which when reached the deployment tool will commit to Appeon Server at one time.

By increasing the value of the above parameters (typically, BatchDWSqlNum and BatchESqlNum) according to the number of DataWindow SQL and embedded SQL used in your application, this will reduce the server calls so it eliminates the chance of failing to commit certain syntax. If you have no idea of the number of DataWindow SQL and embedded SQL, you can increment the value by 200 each time and then full deploy the application to see if this error disappears.

Step 2: Modify the IIS web.config xml file.

Go to C:\Inetpub\wwwroot\appeon\AEM, and add the following code to the web.config XML file. By default, the value of the Execution Timeout is 100 seconds, and the value of the Max Request Length is 4096K. You can use larger values for these two properties according to the specific needs.

..............

<system.web>

<httpRuntime executionTimeout="30000" maxRequestLength = "102400" />
<httpHandlers>

...............

Step 3: Restart the IIS server to make this change take effect.

BTW, please use the Appeon Developer to deploy application to the remote Appeon server/web server, but not copy files to Appeon server manually.
https://support.appeon.com/index.php?/Knowledgebase/Article/View/150/7/appeon-developer-deployment-processarchitecture-and-why-users-cannot-copy-files-to-appeon-server-manually


Thanks,
Appeon Support Team

[T L Sreedharan]

Hi,

Thanks so much for the solution,

I tried to set the Execution Time in the Webcofig xml , But when I restart the AEM I get this error in the AEM Page launch page in browser

*****************************************************************************
Server Error in '/Servlet' Application.
--------------------------------------------------------------------------------

Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Unrecognized element 'httpRuntime'.

Source Error:


Line 114: <add verb="*" path="aemdispatcher.aspx" type="Appeon.AEM.Dispatcher.AEMDispatcher, Server" />
Line 115: <add verb="*" path="monitordispatcher.aspx" type="Appeon.AEM.Dispatcher.MonitorDispatcher, Server" />
Line 116: <httpRuntime executionTimeout="30000" maxRequestLength = "102400" />
Line 117: </httpHandlers>
Line 118: <!-- Dynamically debugging compilation

Source File: C:\inetpub\wwwroot\Appeon\AEM\web.config Line: 116

********************************************************************

By the way I noticed that .dat files are not getting downloaded to the client browser for some reason. I tried setting the MIME & Handler Mapping but no use. Still investigating. I still keep getting a message that following .dat files could not be downloaded. I cleared the downloaded application files from c:\users\Appdata\Roaming\Appeon\ folder and run the Url in the browser, It prompts me to run after downloads. Then after downloading it throws an popup saying .dat files(All datawindow files in Meta folder) could not be downloaded


Let me know how I can make the .dat files download it to client pc from remote server

Appreciate your help

Thanks
Sree

[T L Sreedharan]

Hi,

Thanks a lot, I figured it out now

Its the IIS Web server URL Scan that is rejected the .dat files from downloading to the client web browser.

I now removed the ULRSCAN in the IIS->Web Hosting web site->Properties->ISAPI Filter-> URLscan & reset the ISS using iisreset command in command prompt.

Now the Datawindows are downloaded and application works fine

Once again Thanks
Sree