Magne Johansen (Kriminalomsorgsdirektoratet) asked a question.

November 28, 2025 at 11:06 AM
Upgrade from Pro2 5.5 to Pro2 6.5

First of all, where can I find the documentation for Pro2 6.5?

 

Important: do not use java newer than OpenJDK17_0_11+9.. maybe OpenJDK17_0_12 could work..

I tried: OpenJDK17_0_16 and that gave me ESAML problems

 

Install Pro2:

set environment:

SET JAVA_TOOL_OPTIONS=-Djdk.util.zip.disableZip64ExtraFieldValidation=true

Pro2-6.5.2.exe LAX_VM <path2installedjava>\bin\java.exe

 

Steps:

  • download Pro2 6.5
  • Install Pro2
  • Create a new pro2 db
  • make a delta between pro2 and repl, and load that into repl
  • build and compile triggers..etc.
  • ..

how to setup the instance, and then what next?

 

Would love to have documentation :-)

  • 6 answers
  • 120 views
Kunal Berlia likes this.

  • Geir Otto Olsen (THInc Consulting AS)

    Hi, could you explain for me what the setup would look like when we have the following:

     

    Progress:

    dbA,dbB, replShared, one sql dataserver schA for dbA and one sql dataserver schB for dbB

     

    SQL

    repldbA,repldbB

     

    So we replicate two Progress databases, and we have one shared Repl database, and two dataserverSchema databases, one for dbA and one for dbB. We replicate to SQL.

     

    After reading the documentation, I would like to understand the new setting in Pro2 6.5. What is the new Pro2 database? It seems like there is a new database Pro2.db and also a repl.db. Could you explain the setup?

     

    This is how it looks like today:

    imageOne client connects to application A that connects to both dbA and replShared. And the same for another client that connects to application B, that connects to dbB and replShared.

     

    There is a service that runs the replicaitonBroker (RunReplProc.p), that is connected to dbA,dbB and replShared.

    There is also a client that runs ".... -pf bprepl\Scripts\replproc.pf -p bprepl\bpadmin.w" that we use for looking at the setup/queues etc.

     

    This is how we run it on Pro2 5.5. I wonder if you could explain how this would look like in Pro2 6.5?

     

    I believe that the pasoe instance is equal to the client, and is connected to the same.

    Will we also have a service doing the same as we did for Pro2 5.5?

     

    documentation: (upgrade Pro2 5.5.x to 6.4)

    • Installing and configuring Pro2 6.4 or later versions.
    • Importing your 5.5 properties file and table mapping.

     

    Why would I or why would I not consider loading the Pro2 5.5 ? After saving the configuration file, it is nothing in there that is added by us, as far as I can see, so it seems to be better using the new configuration...

     

    After creating the two databases, and added an instance called Pro2Web, I wounder how to start it.

     

    I followed the documentation to point # 6:

    Open any browser and log in at localhost:port number/pro2/static/ using the default credentials.

     

    I have started the Pro2Web, and it is running, but where comes the application into action here?

    imageIn the installed application we have PASOE/Instance/PASOEcontent... but nowhere in the documentation could I find that I should copy/import/deploy this?

     

    I need to add a support call for this...

     

     

     

     

     

    • Talha Masood (Progress Software)

       

      Hi @Geir Otto Olsen (THInc Consulting AS)​,

       

      A new database Pro2.db, was introduced for capturing configuration and management. repl.db still exists for replication control.

      PASOE Instance acts as the web-based admin interface (Pro2Web).

       

      Importing v5.5 properties file and table mapping , will import properties and mapping from 5.5 into 6.5. However, if your old config doesn’t have customizations, starting fresh in v6.5 is cleaner.

      After creating Pro2.db and repl.db and adding an instance called Pro2Web:

      • Start PASOE instance.
      • Access via browser: http://localhost:<port>/pro2/static/ using default credentials.
      • If the Pro2 Login UI doesn't show up, check the PASOE agent log for any errors. Mostly, config errors are the cause in these scenarios.

       

      Note:

      • PASOE hosts the Pro2 web app.
      • You do not need to copy or deploy application files manually, the installer handles this.

      Let me know if you have further questions.

       

      Thanks,

      Talha

      • Geir Otto Olsen (THInc Consulting AS)

        Hi Talha, thanks for answering !

        My understanding of pasoe and the instances, is that it should have pro2 as a directory under webapps. After running the createInst.bat (which is creating the instance) I am not able to see another step for creating the webapp... so either I have not understood the installation (happens), or there is something missing.

         

        My pasoe instances is placed here: d:\pasoe\Pas2Web and I assume that pro2 should be located under webapps\pro2, but there is nothing, so there has to be a step I have forgotten.

         

        PS! I have added a support case on this issue..

  • Geir Otto Olsen (THInc Consulting AS)

    I ran the two other scripts, and had to compile everything under pro2, then I was able to login as well.. learning by testing... very nice installation documents!

  • Geir Otto Olsen (THInc Consulting AS)

    When trying to import .ini file....

    image2025-12-01T16:13:32.203+0100 015088 009392 1 AS-10 pro2:r:0000005f -- (Procedure: 'callForData bprepl/PRO2_REST/DataProcReq.p' Line:228) DATAPROCREQ: DataProcReq called for System/watchboxes with the parameters [ ? ]

    2025-12-01T16:13:32.203+0100 015088 011372 1 AS-4 pro2:r:0000005e -- (Procedure: 'callForData bprepl/PRO2_REST/DataProcReq.p' Line:228) DATAPROCREQ: DataProcReq called for System/getJobStat with the parameters [ ? ]

    2025-12-01T16:13:32.204+0100 015088 011372 1 AS-4 pro2:r:0000005e -- This version of PROGRESS does not allow compiles. (471)

    2025-12-01T16:13:32.204+0100 015088 011372 1 AS-4 pro2:r:0000005e -- R-code file not located for "bprepl/repl_pro2dbtrigs/wpro2_Repl_ThreadControl.t". (473)

     

    I connected using my developer, and did a compile of bprepl/repl_pro2dbtrigs/*.t and then I could continue...