Bug 5257

feature requests for PowerClient C/S Deployment 17 September, 2020

Miguel Leeuwe
15 September, 2020
Product: PowerBuilder Category: PowerClient
Version: 2019 R3 Beta Build:
Classification: Enhancement Publishing: Public
Priority: P3
Status: Scheduling Reason:
Zhao Kai @Appeon 17 September, 2020
#7
Hi Miguel,

Thanks for your valuable suggestion. We'll transfer the enhancements to our product team for consideration.

Regards,
ZhaoKai
Miguel Leeuwe 17 September, 2020
#6
11 - Another thing missing is the possibility to set Version info, just like we do in a "normal" project.
Miguel Leeuwe 17 September, 2020
#5
Hi,
No it`s not possible to connect to our server from outside of our network. 
I think that might be my whole misconception of what a "remote" server is. I just want to use a server on our network. 
When specifying our server as "local" profile, it all works now!
So that problem is solved.
Regards
Zhao Kai @Appeon 17 September, 2020
#4
Hi Miguel,

Thanks for your quick update.
I created IIS FTP on Windows Server 2016 (10.0.14393) but did not reproduce the issue. Did you check the ‘Require explicit FTP over TLS/SSL’?  Is it possible to provide the IP and user/password for us to connect to your FTP?

Regards,
ZhaoKai
Miguel Leeuwe 16 September, 2020
#3
Hi,
Please see https://community.appeon.com/index.php/qna/q-a/pb2019-r3-beta-c-s-deploymen again, Julie has done some updates.

To comment on your comments: **

Some things need improvement / I'd like to have more information on:
1 - How do I configure a "remote Server"? I think I have to add FTP protocol/role, but some instructions for noobs would be nice. (or even better, powerbuilder setting IIS up so it would work on remote). Filezilla on same machine connects fine, but can't get it to work from PB.
// I did not reproduce the FTP issue, please provide the information below to us for more study, thanks.
1 The OS & IIS version.
2 Do you use IIS FTP?
3 The detailed error in PB.
** 1 Windows server 2016 (1607), IIS 10.0.14393.0
** 2 Yes
** 3 Error: Failed to connect to the Server.
** BTW: if I use the exact same settings and setup a POWERSERVER web config FTP profile, I DO get a successful connection on the same machine.

2 - Using "localhost" we have to disable any antivirus to deploy. Avast and Avira consider the code as BAD. No problem to deactivate the antivirus for deployment, but this IS a big problem for any clients connecting and trying to get the runtime of the application downloaded. Antivirus also jumps in and the only way to download on a client is by also deactivating the antivirus. I've also seen the 3001 (?) error still show up, even when no proxy is enabled for localhost.

// The cause of it should be that the file is unsigned so the antivirus blocks it. 
The PowerClient app executable file (and an XML file with the same name) will be generated under the same folder the PowerBuilder target (PBT) file resides. If you want to digitally sign the PowerClient app executable file, you can place the signature scripts in a file, name the file as appsign.cmd, and place this file in the same folder as the PowerClient app executable. PowerBuilder will sign the executable file for you by executing the scripts in appsign.cmd immediately after the executable file is generated and before it is deployed to the server.
Note:
If you intend to deploy to a local Web server, make sure you run PowerBuilder as administrator (administrator rights are required when transferring files to a local Web server).

Please refer to the article below for details.
https://docs.appeon.com/pb2019r3/whats_new/PowerClient.html
** I cannot sign the executable before it is generated by the deploy. Once the deploy is running it`s too late to sign anything. Anyway, it`s not an acceptable solution, even if it would be possible. Julie already mentioned that Appeon is mentioning false positives to Antivirus vendors.
** Yes I`m running as Administator

** Thank you very much, this is a great feature!
Zhao Kai @Appeon 16 September, 2020
#2
Hi Miguel,

Thanks for your valuable suggestion. We'll transfer the enhancements to our product team for consideration.

Please see my comments below for your issues.

Some things need improvement / I'd like to have more information on:
1 - How do I configure a "remote Server"? I think I have to add FTP protocol/role, but some instructions for noobs would be nice. (or even better, powerbuilder setting IIS up so it would work on remote). Filezilla on same machine connects fine, but can't get it to work from PB.

// I did not reproduce the FTP issue, please provide the information below to us for more study, thanks.
1 The OS & IIS version.
2 Do you use IIS FTP?
3 The detailed error in PB.


2 - Using "localhost" we have to disable any antivirus to deploy. Avast and Avira consider the code as BAD. No problem to deactivate the antivirus for deployment, but this IS a big problem for any clients connecting and trying to get the runtime of the application downloaded. Antivirus also jumps in and the only way to download on a client is by also deactivating the antivirus. I've also seen the 3001 (?) error still show up, even when no proxy is enabled for localhost.

// The cause of it should be that the file is unsigned so the antivirus blocks it. 
The PowerClient app executable file (and an XML file with the same name) will be generated under the same folder the PowerBuilder target (PBT) file resides. If you want to digitally sign the PowerClient app executable file, you can place the signature scripts in a file, name the file as appsign.cmd, and place this file in the same folder as the PowerClient app executable. PowerBuilder will sign the executable file for you by executing the scripts in appsign.cmd immediately after the executable file is generated and before it is deployed to the server.
Note:
If you intend to deploy to a local Web server, make sure you run PowerBuilder as administrator (administrator rights are required when transferring files to a local Web server).

Please refer to the article below for details.
https://docs.appeon.com/pb2019r3/whats_new/PowerClient.html


3 - How can I embed a Manifest when deploying this way?

// PowerBuilder 2019 R3 GA will support it. 


4 - I cannot run my applications anymore when "the server is down". This should be possible in my opinion, once you have done the initial download. It would give us the possibility to have the file server running while our customers are testing and we are still uploading new requirements or bugfixes, but once we've reached a stable situation, there'd be no more need to have the fileserver running. (Chris replied that we are still in an early stage and probably this will be possible in the future, I just comment it here so it's registered as a feature request).

//We will record it as a requirement in our CR pool, I will get back to you once we have a plan to support this feature.


5 - Some examples for registering OCX and DLLs would be nice. An example shows the use of regasm.exe, but not all clients have an available regasm. Can we somehow deploy a regasm.exe in the files section and then run it with the script? As Chris said, many companies won't allow you to simply deploy regasm. So my guess is that we'd have to generate reg files and import them.

// PowerBuilder 2019 R3 GA will support registering via the regasm method. Currently you can add the register command in the Preload event and deploy the regasm.exe but you need to write code to launch it. 


6 - We are using commandline parameters. How should I fit in a commandline parameter, now that there's already some in the shortcuts produced by the C/S deployment?
// The parameter configuration option will be added to the Project configuration page on the GA version. 
At present, the command line argument can be passed to a PowerClient application in the following way:
http://192.0.1.94:8080/MyTest?user=appeon&password=appeon 
This attaches the string "?arguments" to the end of the original application URL.


7 - At this point, when installing the user gets a shortcut on his desktop, but no entries in the start menu. (or maybe I'm not seeing well and the entries do show somewhere in a menu).

//We will record it as a requirement in our CR pool, I will get back to you once we have a plan to support this feature.


8 - It would be nice if the user could choose a folder where things get installed. It now all goes to ..\users\...\Appdata\....

//We will record it as a requirement in our CR pool, I will get back to you once we have a plan to support this feature.
It is not recommended that you modify the installation path because it might cause conflicts in a multi-user scenario.


9 - Make it possible to use a server on the internet / cloud, not only "on premises". 

// Do you mean deploy an application to the internet / cloud? You can use the remote server(FTP)method. PowerBuilder 2019 R3 GA will support packaging application, then you can package the application locally and distribute the packaged application to the internet / cloud to install it.


10 - Please don't make the 'old' way of deploying executables and pbd's /dll's obsolete. Not every customer will like this new way of installing the applications (mainly due to it being pretty slow when running an application for the first time and not always allowing access to a server or having to set one up).

// The 'old' way of deploying executables and pbd's /dll's won’t be obsolete. It has no interference with PowerClient.  


Regards,
ZhaoKai
Miguel Leeuwe 15 September, 2020
#1
Another request:
7 - At this point, when installing the user gets a shortcut on his desktop, but no entries in the start menu. (or maybe I'm not seeing well and the entries do show somewhere in a menu).
8 - It would be nice if the user could choose a folder where things get installed. It now all goes to ..\users\...\Appdata\....
9 - Make it possible to use a server on the internet / cloud, not only "on premises". 
10 - Please don't make the 'old' way of deploying executables and pbd's /dll's obsolete. Not every customer will like this new way of installing the applications (mainly due to it being pretty slow when running an application for the first time and not always allowing access to a server or having to set one up).

Thank you
Miguel Leeuwe 15 September, 2020
*Phenomenon:
Please see https://community.appeon.com/index.php/qna/q-a/pb2019-r3-beta-c-s-deployment

Some things need improvement / I'd like to have more information on:
1 - How do I configure a "remote Server"? I think I have to add FTP protocol/role, but some instructions for noobs would be nice. (or even better, powerbuilder setting IIS up so it would work on remote). Filezilla on same machine connects fine, but can't get it to work from PB.

2 - Using "localhost" we have to disable any antivirus to deploy. Avast and Avira consider the code as BAD. No problem to deactivate the antivirus for deployment, but this IS a big problem for any clients connecting and trying to get the runtime of the application downloaded. Antivirus also jumps in and the only way to download on a client is by also deactivating the antivirus. I've also seen the 3001 (?) error still show up, even when no proxy is enabled for localhost.

3 - How can I embed a Manifest when deploying this way?

4 - I cannot run my applications anymore when "the server is down". This should be possible in my opinion, once you have done the initial download. It would give us the possibility to have the file server running while our customers are testing and we are still uploading new requirements or bugfixes, but once we've reached a stable situation, there'd be no more need to have the fileserver running. (Chris replied that we are still in an early stage and probably this will be possible in the future, I just comment it here so it's registered as a feature request).

5 - Some examples for registering OCX and DLLs would be nice. An example shows the use of regasm.exe, but not all clients have an available regasm. Can we somehow deploy a regasm.exe in the files section and then run it with the script? As Chris said, many companies won't allow you to simply deploy regasm. So my guess is that we'd have to generate reg files and import them.

 6 - We are using commandline parameters. How should I fit in a commandline parameter, now that there's already some in the shortcuts produced by the C/S deployment?

Thank you,
regards,
MiguelL
*Reproduce Steps:


Remarks:
OS:
Windows 10
Platform:
64-bit
Database Type:
Database Version: