Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved Re: Runtime installation folder - 64 bit & 32 bit

  1. How-to
0
Votes
Undo
  1. Sivaprakash BKR
    Sivaprakash BKR
  2. PowerBuilder
  3. Tuesday, 27 July 2021 05:55 AM UTC

Hello,

PB 2019 R3

We copy all PBDs, Exe file in a folder in the server machine and create a short-cut of that exe in every client machine.  In this scenario, where to install (which folder is better) the runtime files ?

Run time files defaults to 

64 bit:   C:\Program Files (x86)\Appeon\PowerBuilder Runtime Packager\
32 bit:   C:\Program Files\Appeon\PowerBuilder Runtime Packager\

If we have both 64 bit and 32 bit windows in client computers and the exe link is in server (short-cut is there in client machine), default folder suggested by Appeon doesn't work.  

In our scenario, server is 64 bit Windows Server 2012 R2 and the runtime installs inside C:\Program Files (x86)\Appeon\PowerBuilder Runtime Packager\ folder.   And corresponding XML file points to runtime to that folder.  If we make a shortcut of the EXE in a client machine, which got 32 bit Win 7, application searches for run time in the folder C:\Program Files (x86)\Appeon\PowerBuilder Runtime Packager\  which doesn't exists !

Would like to know how you (experts) resolve this issue ? Or what's the best suggested method ?

Happiness Always
BKR Sivaprakash

  1. PowerBuilder (Appeon)
PowerBuilder 17 with Sybase DB ASE Error
Regarding Object menu
Responses (4)
Sivaprakash BKR
Sivaprakash BKR Accepted Answer Pending Moderation
  1. Friday, 30 July 2021 07:04 AM UTC
  2. PowerBuilder
  3. # 1

Thanks Mike, Armeen, Rene Ullrich.

1.  Currently we decided to retain the XML file. [ we can have more runtime versions available in future, which this XML file could solve ]
2.  We installed runtime files in C:\Appeon\PowerBuilder Runtime Packager\

With this we could install runtime in every client computers and give the application shortcut from the server computer.

 

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 30 July 2021 14:52 PM UTC
Glad to hear you have working solution!
  1. Helpful
There are no comments made yet.
René Ullrich
René Ullrich Accepted Answer Pending Moderation
  1. Thursday, 29 July 2021 10:11 AM UTC
  2. PowerBuilder
  3. # 2

How about this:

Don't deploy the XML file that refers to the runtime location. On client machine put the runtime location to PATH variable instead so the application can find the DLLs.

If you don't want to change the PATH permanently you could also create a small CMD script that (temporary) adds the runtime location to PATH and starts the EXE.

 

Comment
Sivaprakash BKR
  1. Sivaprakash BKR
  2. Thursday, 29 July 2021 10:45 AM UTC
Thanks, Rene Ullrich,

Is that XML file an optional one? I'm not aware of that. I'll try.
  1. Helpful
René Ullrich
  1. René Ullrich
  2. Thursday, 29 July 2021 10:48 AM UTC
Yes, if XML file doesn't exists PB looks for the files like in previous versions.
  1. Helpful
mike S
  1. mike S
  2. Thursday, 29 July 2021 13:48 PM UTC
if everything is in the same directory, then you don't do anything with the path and you don't need the xml file.
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 29 July 2021 07:02 AM UTC
  2. PowerBuilder
  3. # 3

Why don’t you use PowerClient?  It manages everything for you… app deployment, runtime deployment, matching bitness, updates, encrypting source code, verifying app integrity, etc.  https://www.appeon.com/products/power-client

 

Comment
Sivaprakash BKR
  1. Sivaprakash BKR
  2. Thursday, 29 July 2021 07:39 AM UTC
Armeen,

We also trying with Powerclient. Seems this will install the application in every clients' machine.

Currently, we update the database also with every release and we are not sure how this will be taken care of. We need to try with that one.
  1. Helpful
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Tuesday, 27 July 2021 13:59 PM UTC
  2. PowerBuilder
  3. # 4

put everything in same directory ( dlls with the exe and pbd) on the local machine.

Comment
Sivaprakash BKR
  1. Sivaprakash BKR
  2. Thursday, 29 July 2021 06:50 AM UTC
Thanks, Mike,

That won't work in my scenario. Say there are 5 computers among one is server. I install my application on the server computer, create a short-cut of the exe file from the server folder in all other 4 computers.

PB 2019 R3 got an XML file, which contains the folder where the runtime files are stored. It points to C:\Program Files (x86)\Appeon\\PowerBuilder Runtime Packager\Runtime 19.2.0.2703 folder (if I go with the suggested folder by Appeon). [ Server OS is 64 bit ]

Now in the clients' machines, there are no Exe's or PBDs but only a short-cut placed from the server. When running the program by clicking the shortcut, it takes the path of the run time from the XML file available in that folder. It works perfectly if the client machine also got a 64bit OS, as the runtime will be available in the same folder as stored in the XML file.

Say if the client machine is 32 bit os, that folder won't be there in that particular client machine.



As suggested by you, if I put all the runtime files in the same folder where Exe and PBD are available, then what will be there in the XML file. something like this E:\folder, if the application is installed in that folder?

Now in the client machine, we need to have the runtime files in that E:\folder, isn't it? Say what happens if that particular machine doesn't have an E: drive?.



  1. Helpful
mike S
  1. mike S
  2. Thursday, 29 July 2021 13:45 PM UTC
if everything is in the same folder, then you do NOT need the xml file.
  1. Helpful
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.