deploying application?
- Thread starter jaffar
- Start date
The thing is there's a lot of ways to deploy. It depends on all sorts of things about the configuration of the machine and the network. It's not a case of "This is how to do it", rather a case of deciding what is best for you. Without going into some depth about your systems I doubt you'll be able to get a huge amount of help (although RealHeavyDude will probably do his best - he's like that! 
)
)
RealHeavyDude
Well-Known Member
I'll try ...
Basically you need two things ( assuming that we are talking about an application that is based on the classic GUI ):
The Progress installation
Most likely you will need to install at least the client networking license from Progress. That will give you the prowin32.exe which is the AVM ( ABL virtual machine ) on which your application will run. During the installation you will be asked some things. The most important ones are things like languages and code pages. Based on you choices some files in the installation directory will be customized - most prominently the startup.pf. I always recommend to do a full installation because otherwise you might end up missing things like the ODBC/JDBC drivers.
You need to gather all the relevant information before you begin with the installation. I strongly recommend you to read the installation guide to get an idea.
Your application:
Most likely your application will consist of a buch of .r files spread over a directory tree, an ini file which contains the DLC, PROPATH setting and other stuff related to your application, and, a start parameter file that contains customized start parameters for your application.
Unless your applications contains third party software that need to be installed ( like special OCX controls ) all these files are just copied into the correct directory on the target system.
Next you create the short cut pointing to the prowin32.exe and a usually a working directory set to the root of the directory tree I've mentioned above and you're done.
This how your short cut _COULD_ look like:
The -basekey "INI" is responsible for telling the AVM not to look into the registry but relative to your PROPATH in the file system instead -which is what I prefer personally ( I think the Windows registry is a dump for each and everything ... ).
Disclaimer: Everything I told you is typical usage. You need to customize these so that all these suits your needs.
Heavy Regards, RealHeavyDude.
Basically you need two things ( assuming that we are talking about an application that is based on the classic GUI ):
The Progress installation
Most likely you will need to install at least the client networking license from Progress. That will give you the prowin32.exe which is the AVM ( ABL virtual machine ) on which your application will run. During the installation you will be asked some things. The most important ones are things like languages and code pages. Based on you choices some files in the installation directory will be customized - most prominently the startup.pf. I always recommend to do a full installation because otherwise you might end up missing things like the ODBC/JDBC drivers.
You need to gather all the relevant information before you begin with the installation. I strongly recommend you to read the installation guide to get an idea.
Your application:
Most likely your application will consist of a buch of .r files spread over a directory tree, an ini file which contains the DLC, PROPATH setting and other stuff related to your application, and, a start parameter file that contains customized start parameters for your application.
Unless your applications contains third party software that need to be installed ( like special OCX controls ) all these files are just copied into the correct directory on the target system.
Next you create the short cut pointing to the prowin32.exe and a usually a working directory set to the root of the directory tree I've mentioned above and you're done.
This how your short cut _COULD_ look like:
The -basekey "INI" is responsible for telling the AVM not to look into the registry but relative to your PROPATH in the file system instead -which is what I prefer personally ( I think the Windows registry is a dump for each and everything ... ).
Disclaimer: Everything I told you is typical usage. You need to customize these so that all these suits your needs.
Heavy Regards, RealHeavyDude.
Thanks RHD - knew I could rely on you 
Another thing to consider is whether or not you want to use procedure libraries. A procedure library is a bit like a .dll file in that it is a single file containing a library of .r files. It saves you having to deploy hundreds of small files all the time. We tend to work on the basis of a library.pl that contains the last major release, and a patch.pl that contains anything that has changed since the release. If handled well this should make maintenance a lot easier in the long run.
Another thing to consider is whether or not you want to use procedure libraries. A procedure library is a bit like a .dll file in that it is a single file containing a library of .r files. It saves you having to deploy hundreds of small files all the time. We tend to work on the basis of a library.pl that contains the last major release, and a patch.pl that contains anything that has changed since the release. If handled well this should make maintenance a lot easier in the long run.
Thanks RHD, I got what you said and i had done the same but one thing i am not getting how to deploy the same in the client machine which doesn't have progress installed...
Is there any progress kit which supports only execution process not development,so that in client machine only compiler & server should exists not at all any developement tools..
I hope u understand what i am saying
Is there any progress kit which supports only execution process not development,so that in client machine only compiler & server should exists not at all any developement tools..
I hope u understand what i am saying
RealHeavyDude
Well-Known Member
If you need a compiler on the client machine then you must have a development product installed. Full stop. At least you would need the "4GL Development" license. But why would you need a compiler on the client machine? Is it that you want to deploy source code?
As an alternative, if your application does not access a database directly but connects only to an AppServer ( thin client ) instead you could install the WebClient product which is free of charge. In reality it is the same as the prowin32.exe that comes with the Client Networking sans the functionality to access a database.
Heavy Regards, RealHeavyDude.
As an alternative, if your application does not access a database directly but connects only to an AppServer ( thin client ) instead you could install the WebClient product which is free of charge. In reality it is the same as the prowin32.exe that comes with the Client Networking sans the functionality to access a database.
Heavy Regards, RealHeavyDude.