1. Michael Turton
  2. PowerServer 2020 or older (Obsolete)
  3. Tuesday, 6 July 2021 13:23 PM UTC

A thick client Powerbuilder 2019 application using an Oracle 12g database and client consisting of several modules is being tested for feasibility to run as a Web application using PowerServer 2020.   However the first module which connects to the database and presents a login page to the user is not being displayed when running. 

There were 5 "Must Modify" unsupported features that have been worked around.  The deployment showed no errors.  Run loads a blank web page though.   There are no errors.  All template and library files load OK just the resulting page is empty of content.   

This (and the other) modules use an ini file that contains various settings for use by the application.   Let's call it Jane.ini.  This ini file is writable and the application modules will record variable data in it such as the window positions and size and site locations.  I believe ini files are deployed to the web server as xml files.   I think it is the ini file that is maybe the issue here.  The ini is referenced in the PowerServer deployment profile.   There are some xmls in the Config folder for the application on the web server (e.g. pb.xml, <appname>.xml) but none are named as per the writable ini file i.e. there is no Jane.xml. 

Can PowerServer web apps write to deployed ini files?  Is this the likely issue?  Can you suggest any logs or diagnostics I can run to determine the issue here?

Thanks!

 

Who is viewing this page
Michael Turton Accepted Answer Pending Moderation
  1. Wednesday, 7 July 2021 15:14 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

I couldn't see .dat (in the meta folder) on the IIS mime types so I have added that and created a mapping for it and restarted IIS.   Still shows blank though.

Comment
There are no comments made yet.
Michael Turton Accepted Answer Pending Moderation
  1. Wednesday, 7 July 2021 08:42 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Hi Mike and ZhaoKai,

thanks for responding.  I am not using 10X compression or merge in the PS deployment.  I had already tried the Run after download tip to check if all file types were being downloaded but there were no issues displayed  (see attached) unless it is hanging before d/ling all files?   I will do a manual check of file types already mapped on IIS to see if any are not there.

Thanks,

Michael

 

 

Attachments (1)
Comment
  1. Michael Turton
  2. Friday, 9 July 2021 10:26 AM UTC
Thanks Zhao I will give the debugging a try.
  1. Helpful
  1. Michael Turton
  2. Thursday, 22 July 2021 09:54 AM UTC
Hi Zhoa,

I have got hold of Microsoft Script Debugger and installed and tried with PowerServer Toolkit debugger. There are no errors as such - the calling application script gets as far as the Open(w_login) and hangs. The debugger shows that a super call::open; has been put by the deployment process at the top of the w_login window but it is not getting there. There is a >>> on the next line (which happen to be a comment) - is this implying the whole w_login.open() code is unsupported? I tried creating an empty w_test window and opening that from the calling application script instead but even this doesn't open.



Thanks,

Michael
  1. Helpful
  1. Michael Turton
  2. Friday, 23 July 2021 15:17 PM UTC
(I will raise a support case as suggested with logs)
  1. Helpful
There are no comments made yet.
Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 7 July 2021 02:50 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 3

Hi Michael,

As Mike mentioned, If you use compression in the deployment (the 10x compression ), the application files might not be downloaded which is caused by the IIS configuration, please refer to the article below to solve it.
https://docs.appeon.com/ps2020/appeon_troubleshooting_guide/IE_shows_done_status_and_then_stays_blank.html

For the ini issue, the ini file’s content will be downloaded to ini.xml in the application folder on the client machine by default when it needs to use it, for example, C:\Users\appeon\AppData\Roaming\appeon\172.16.8.10_800_Dotnet_ps2020\plugin\ini.xml.
So, please do not use fileexists to judge if the ini file exists or not, please refer to the article below for details.
https://support.appeon.com/index.php?/Knowledgebase/Article/View/158/0/about-ini-files-in-appeon
https://support.appeon.com/index.php?/Knowledgebase/Article/View/97/7/it-is-failing-when-the-appeon-web-application-tries-fileexists-for-ini-file

For the unsupported features, please try refer to article below to work around them.
https://docs.appeon.com/ps2020/workarounds_and_api_guide/Workarounds_for_Unsupported_Features.html

Regards,
ZhaoKai

Comment
There are no comments made yet.
mike S Accepted Answer Pending Moderation
  1. Tuesday, 6 July 2021 14:10 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 4

did you configure the web server completely?  If you use compression in the deployment (the 10x compression ), then you must configure the IIS server to know how to handle those compressed files:

Add MODULE mappings (Handler Mapping ) for F#### files. (see Appeon PowerServer 2020 Readme.mht ) for instructions.  

  • Request path: f*
  • Module: StaticFileModule, DefaultDocumentModule, DirectoryListingModule
  • Name: v (you can put whatever name you want here, as long as it does not conflict with an already existing mapping.)
  1. Then click the Request Restrictions button; in the Mapping tab, check the invoke handler only if box and select File or folder, and in the Access tab, select Read.

 

then you must restart IIS

 

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.