Applicable Versions: 4.5 onwards


DataPA OpenAnalytics can be installed as a Client on a user's PC and on a Server ( to run DataPA Enterprise). The following notes explain the steps required to upgrade DataPA OpenAnalytics to the latest version.


The latest version and accompanying Release Notes for DataPA OpenAnalytics are available at http://www.datapa.com/downloadoa-access


Client Install ( for Users PC's)

  1. Download the latest version from the DataPA Website.
  2. Run the setup.exe, at the "Setup Type" screen select "Custom".
  3. On the next screen "Custom Setup", ensure that "DataPA Enterprise" and "DataPA Developer are unchecked"


Server Install ( for DataPA Enterprise)

  1. Download the latest version from the DataPA Website.
  2. Run the setup.exe, at the "Setup Type" screen select "Custom" and go to step 3 or select "Complete" and skip step 3.
  3. On the next screen "Custom Setup", ensure "DataPA Enterprise" and all it's child features are checked.


AppServer Updates


When DataPA OpenAnalytics is updated, it is always advisable to ensure any OpenEdge AppServers the client will connect to have the Procedure Library distributed with the install. The DataPA Procedure Library is added to the ProPath of the AppServers used by DataPA OpenAnalytics. 


By default, the installer will place the DataPA Procedure library in directory C:\Program Files\DataPA\ProgSrc\. If you have chosen to install DataPA OpenAnalytics in an alternative directory, the procedure libraries will be located in [INSTALLDIR]\ProgSrc.


The table below details which procedure library you should use depending on which version of OpenEdge you have installed.


AppServer Version

32 Bit
64 Bit
9.1D

datapa.pl

N/A

9.1E

datapa.pl

N/A

10.0A

datapa10.pl

datapa10_64.pl

10.0B

datapa10.pl

datapa10_64.pl

10.1A

datapa10.pl

datapa10_64.pl

10.1B

datapa101B.pl

datapa101B_64.pl

10.1C

datapa101B.pl

datapa101B_64.pl

10.2A

datapa101B.pl

datapa101B_64.pl

10.2B

datapa101B.pl

datapa101B_64.pl

11.0

datapa111.pl

datapa111.pl

11.1

datapa111.pl

datapa111.pl

11.2

datapa111.pl

datapa111.pl

11.3

datapa111.pl

datapa111.pl

11.4

datapa111.pl

datapa111.pl

11.5

datapa111.pl

datapa111.pl

11.6datapa111.pldatapa111.pl

 

If any Appservers are located on different server to the machine where the DataPA Enterprise is installed, it will be necessary to find the Appservers that need to be updated, then copying the new procedure library to these appservers. If you are using ftp to copy the file, make sure you use a binary copy.


If you are unsure whether or not you are using OpenEdge AppServers, or their location you can look up this information in the connection details dialog of the systems configured in the Analytics Engine.


Once know the machine where your OpenEdge AppServer is located, follow the steps below for the relevant version of Progress/OpenEdge to find the location of the procedure library for that AppServer

 

Windows 
Windows 
Windows  and UNIX
Progress Explorer
(for Progress/OpenEdge Version 10 and earlier)
OpenEdge Explorer
( for OpenEdge Version 11 and later)
CommandLine
All versions
Open Progress Explorer
connect to Hostname
Enter http://Hostname:port in a browser to open the OpenEdge Explorer webpage.
(where hostname is the name of the machine or localhost if you are on the local machine, and port is the port number the OpenEdge admin server is running on, 9090 by default, i.e http://localhost:9090)
log on to server, locate the ubroker.properties file
By default this is located in the windows folder <%DLC%>\properties or in the UNIX <%DLC%>/properties
Select "AppServer" in treeview, then select the AppServer you want to changeOn the initial Resources page is a list of AppServers, click on the Appserver of interest.
search for the [UBroker.AS.Appservername] section, where AppServerName is the name of the Appserver you are looking for. 
Open Properties, Agent Section, General Tab On the Main AppServer Page click on "Configuration" in the Command and control section
Within the AS.AppServerName section   there is a "PROPATH" line, on that line is a path to the DataPA Procedure Library,  
Look at the Propath statement for the path containing one of the procedure libraries listed above (datapa?.pl)
 
The Appserver details will be displayed, Click on the Agent Tab. The PROPATH is in the the Gerneral section.
Look at the Propath statement for the path containing one of the procedure libraries listed above (datapa?.pl)
Look at the Propath statement for the path containing one of the procedure libraries listed above (datapa?.pl)
You now have the location of the DataPA Procedure Library. Copy the new procedure Library to this location. If you are copying to a Unix machine ensure you use binary copy to transfer the procedure libraries
 
You now have the location of the DataPA Procedure Library. Copy the new procedure Library to this location. If you are copying to a Unix machine ensure you use binary copy to transfer the procedure libraries
You now have the location of the DataPA Procedure Library. Copy the new procedure Library to this location. If you are copying to a Unix machine ensure you use binary copy to transfer the procedure libraries
Stop the Appserver, select stop by performing a right-click on the AppserverName
Stop the Appserver using the Stop button on the Appserver resources pageUse the command:
proadsv -stop -name AppServerName
Start the Appserver select Start by  performing a right-click on the AppserverName
Start the Appserver using the Start button on the Appserver resources pageStart the apppserver with
proadsv -start -name AppServerName


Note: If you have more that one AppServer this process may have to be repeated. If the location of the procedure library is the same for several AppServers, the file should be copied in place , but All the AppServers will have to be stopped and restarted to pick up the latest version.