5 replies to this topic

[Shaun Rudland]

G'Day Everyone,

We're in the process of upgrading Oracle, and as such we need to upgrade PRO-IV. Unfortunately Oracle 9.2 won't run on our current development box, and we have no budget to either upgrade or change the hardware. Therefore we're looking to install a development version on one of our Test/Migration UNIX boxes, which currently has a run-time installation.

Question:

What are the implications of running both development and run-time versions of PRO-IV 5.5 on the same box ? I'm thinking specifically of licensing issues, but any other information people may have would be gratefully received.

I know that this is a question that should probably be addressed directly to PRO-IV, but as they only have a third-party presence in Australia, it is far easier and quicker for me to do this here. Oh, and please, no agents.

Regards

Shaun

[Donald Miller]

Hi Shaun

I asked Pro IV about running development and runtime only environments on the same machine. I think they said that it was possible but since I only had a development licence I'd need to purchase a run time licence. I couldn't justify the extra cost and set up another development environment. I'm on Windows.

I maybe depends on how large your development licence is.

[Cleve Haynes]

There is no problem running both on the same machine. It's just a matter of entering more keys in the ProIV build (that updates /etc/pro4.ini). Then set the run type you want for a particular user session or environment using PRORUNTYPE=RUN or PRORUNTYPE=DEV.

Am I missing the question here? Or are talking about using your dev system on the RUN box without using DEV keys? That's fine, as long as you're not doing development (which, I believe can be done but would violate your licence agreement with ProIV.)

Cleve

[Shaun Rudland]

G'Day Cleve,

Am I missing the question here? Or are talking about using your dev system on the RUN box without using DEV keys?

No, we want a Development environment and a Runtime environment on the same box. Do we purchase a combined licence for the box (if such a beast exists) or do we purchase seperate licences ? I'm guessing from your reply that seperate licences is the answer.

Neither myself, nor the client, wish to violate any agreements with PRO-IV; it's got to be pucker all the way.

Regards

Shaun

[Rob Donovan]

Hi Shaun,

We do this....

All our BAs have runtime licenses and all the Developers have dev licences, all on the one box.

You need to have separate keys from ProIV to be licensed correctly, and then you just set PRORUNTYPE in Unix to DEV or RUN depending on what you want...

Rob D.

[Rob Donovan]

Hi,

This reply is from Donald Miller, he cant post it because there are some problems with him posting from his PC...




Use the Pro IV Import/Export routines to load functions, files and global logic's into the new development area. If the current development environment is copied over to the new one then the Forms Designer link will be incorrect and there may be other problems also.

To create a runtime system manually you only need to perform the following steps.

1) Create a new directory for the runtime system

2) Ensure no PROIV sessions are active

3) Start an MSDOS command prompt

4) Change directory to the name specified in point 1. using cd /d if necessary

5) type ..\PROIV DIRECTORY\isin32 ..\PROIV DIRECTORY\rbase.out using cd /d if necessary

6) See Below for the ini file set up : Now amend PROIV DIRECTORY\loopback.ini file and change the PROPATH and PRODATA to the directory specified in point 1.

7) Logon into the area and import your application via $XFR

Note that a runtime environment can only be supported if you already have a set of runtime software keys.



To create a development system manually you only need to perform the following steps.

1) Create a new directory for the development system

2) Ensure no PROIV sessions are active

3) Start an MSDOS command prompt

4) Change directory to the name specified in point 1. cd /d

5) type \isin32 \dbase.out

6) type \isin32 \studio.out *1

7) type \isin32 \vip.out *2

8) type \isin32 \pr4demo.out *3

9) See Below for the ini file set up :Now amend \loopback.ini file and change the PROPATH and PRODATA to the directory specified in point 1.

10) Logon into the area and import your application via $XFR



*1 This is for Developer Studio

*2 This is for VIP

*3 This is for the Demo Functions (requires VIP)



Another way is to perform an additional PROIV installation. The disadvantage of this is that more files are copied than are needed and it also becomes harder to maintain.



· Does having previous versions of Pro IV resident on the same drive have an impact on the new version ? (1.5, 4.0)

· No, however if you should install anther PROIV version then this will effect the current one. Forms Designer is only designed to be installed once and it will only work with a predefined kernel and one set of bootstraps, VIP and Studio.



· If I select the Sample Demo to be installed and then after installation re-set the PRODATA path to access my applications data will the sample still operate ? If not are there some parameter settings I can change to allow both systems to operate and reside within the same installation ? If there are no settings how do I set up multiple Pro IV installations - one for my application and one for the Demo system ?

· (You cannot have both systems up and running at the same time, however changing the PROPATH and PRODATA in the loopback.ini will allow you to go to a different bootstrap area.) However, rather than editing the locale.ini file to change the PROPATH and PRODATA directories you should create separate ini files for each set of bootstraps containing only the necessary environment settings. See below for the server settings recommended.


Painter.exe should be able to be run. Confirm the DLL versions being used via Help and About Forms Designer.

PROIV can be installed with the following installation options on Windows :-

Client - All Microsoft supported Windows Platforms

The PROIV MFC Client is used to connect to a PROIV workstation or PROIV Server running on the local machine or another machine on the network.

Workstation - All Microsoft supported Windows Platforms

The PROIV workstation version includes the PROIV MFC Client and a set of PROIV bootstraps that allow a user to create PROIV applications. A workstation version only allows one set of boots area (i.e. your PROIV application) to be active at one time.


Server - All Microsoft supported Windows servers (i.e. Windows NT, Windows 2000 and Windows 2003)


The PROIV Server includes the PROIV MFC Client and installs a set of PROIV bootstraps that allow the user to create their PROIV application. The user is not limited to one set of bootstraps and therefore can have a live and test area running at the same time.

Recommended settings for the ini files for the Server version :

pro4.ini
[ENVIRONMENT]
;common/default settings, e.g.

PROTERM=GUIDEV
GUI=Y
PRORUNTYPE=DEV
PROTEMP=C:\TEMP
CDATE_50=Y
DATE_SC_50=Y
PROPATH=C:\PRO55\BOOTS
PRODATA=C:\PRO55\BOOTS

[USER DEFAULT]

PROIVOPER=SYS
PROIVCODIV=PTI

[USER TEST]

INIPATH=C:\PRO55\TEST.INI

[USER DEV1]

INIPATH=C:\PRO55\DEV1.INI

[USER DEV2]

INIPATH=C:\PRO55\DEV2.INI


test.ini
[ENVIRONMENT]
PROPATH=C:\PRO55\TEST
PRODATA=C:\PRO55\DATA
PRORUNTYPE=RUN
PROTERM=GUICLR

dev1.ini
[ENVIRONMENT]
PROPATH=C:\PRO55\DEV1
PRODATA=C:\PRO55\DATA
PRORUNTYPE=DEV

dev2.ini
[ENVIRONMENT]
PROPATH=C:\PRO55\DEV2
PRODATA=C:\PRO55\DATA
PRORUNTYPE=DEV


Separate piv files can be set up to connect to each of the separate bootstrap environments
If no name is specified for the user name on the Host tab in the piv file then a transparent logon would occur
Alternatively the user name should be set to the same name as the appropriate USER section in the pro4.ini file.

Donald Miller