The Pro2 Enterprise View is designed for easy installation, set up, and integration with your existing Pro2 instances.

To set up Pro2 Enterprise View:

  1. Install Enterprise View.
  2. Create a Pro2 Enterprise View database.​
  3. Update the replProc.pf file.
  4. Start a PAS for OpenEdge instance.
  5. Set up your Pro2 Enterprise environment.
  6. Join your Pro2 instances to Enterprise View
  7. Schedule an Enterprise View push job.
  8. Start the job runner.

Install Enterprise View

Note:
  • The supported Java version is Java 11 and Java 17.
  • All installation files are provided to you by your Progress representative.

On Linux

To silently install Pro2 Enterprise View on a Linux machine:
  1. Copy the response.properties.example file from C:\Progress\Pro2\Docs\response.properties.example to your Linux machine.
  2. Choose the Pro2 root folder by updating USER_INSTALL_DIR path in response.properties.example.
  3. Choose the OpenEdge install location by updating the OE_INSTALL_DIR path in response.properties.example.
  4. Update PAS for OpenEdge instance name and ports in response.properties.example.
  5. Locate the Pro2-ent.bin file and run the following command from the command prompt:
    sh ./Pro2-ent.bin -i Silent -f response.properties.example
    There can be a numeric value in the file name that indicates the version of Pro2, for example, Pro2-6.5.0-ent.bin.
    Note: Starting with Pro2 6.5.2, after locating the Pro2-ent.bin file, run the following command from the command prompt:
    sh ./Pro2-ent.bin LAX_VM "/<JAVA_HOME>/bin/java" -i Silent -f response.properties.example

On Windows

To install Pro2 Enterprise View on a Windows machine:

  1. Locate and execute the Pro2-ent.exe file.

    There can be a numeric value in the file name that indicates the version of Pro2, for example, Pro2-6.5.0-ent.exe.

    Note: Starting with Pro2 6.5.2, after locating the Pro2-ent.exe file, run the following command from the command prompt:
    Pro2-ent.exe LAX_VM "C:\<JAVA_HOME>\bin\java.exe"
  2. In the Pro2 Enterprise installation wizard, click Next.
  3. Specify the installation folder path as C:\Progress\Pro2ent.
  4. In the Choose OpenEdge window, specify the path, or select Choose to browse and set the OpenEdge home directory.

    The directory is based on the version of OpenEdge that is installed on your machine, for example, C:\122\dlc.

  5. On the PAS Ports window, enter the port information for your PAS for OpenEdge instance, and designate the instance name.
  6. Click Next and review the options you chose for this installation in the Pre-Installation Summary page.
  7. Click Install to continue with the installation process.
  8. Click Done.

Create a Pro2 Enterprise View database

Similar to a standard Pro2 replication (repl) database, the Pro2 Enterprise View, or pro2ent, database is an internal database that exists on the machine where Enterprise View is installed. All reports and metrics from the Pro2 instances that you joined to Enterprise View are aggregated to this database, where it is then pushed to the Pro2 web user interface.

To Create a pro2ent database:

  1. Start a Proenv session.
  2. Navigate to the Pro2 folder from the Proenv window. Type cd followed by name of the folder where you installed Pro2 Enterprise View, for example, cd Pro2ent.
  3. Type cd db to navigate to the database folder of Pro2.
    Note: Check the directory of the db folder to view the database instances. Type dir after navigating to the database folder.
  4. Create an empty pro2ent database instance by typing prodb pro2ent empty.
  5. Load the required table definitions in the pro2ent database by typing prowin pro2ent -1.

    The Procedure Editor window appears.

  6. Navigate to Tools > Data Administration.
  7. In the Data Administration window, navigate to Admin > Load Data and Definitions > Data Definitions (.df file).
  8. In the Load Data Definitions window, load the pro2ent.df file and click OK.
    Note: The pro2ent.df file is located in Pro2ent folder/db.
  9. Start the pro2ent database by typing: Proserve pro2ent

Update replProc.pf

In the pro2ent database, you must add the connection details to the replProc.pf file. This connects the database to your PAS for OpenEdge instance, and by extension, makes it available to be connected to your other Pro2 instances.

  1. Navigate to the Pro2ent folder.
  2. Add the pro2ent database connection details to the Pro2_HOME\bprepl_ent\Scripts\replProc.pf file to connect the replication threads and PAS for OpenEdge instance to the Pro2ent database.
  3. Navigate to the bprepl_ent\Scripts folder, and open the replProc.pf file. Add the complete path of the database in the file and click Save.
  4. To test the Pro2ent database connections, open the Procedure Editor from the bprepl_ent\Scripts folder and navigate to Tools > Data Dictionary. If the connection is successful, the Tables section displays tables.

Start a PAS for OpenEdge instance

Now that the pro2ent database is set up, start the PAS for OpenEdge instance and log in to the Pro2 web application:

  1. Start a Proenv session.
  2. Navigate to the Pro2 folder by entering cd followed by name of the folder where you installed Pro2, for example, cd Pro2ent.
  3. Type Pro2ent\bin\tcman.bat env.
  4. Type Pro2ent\bin\tcman.bat start.
  5. To verify that the instance started successfully, type Pro2ent\bin\tcman.bat env. The Server Running section shows a number if the instance started.
  6. Open any browser and log in at localhost:9991/pro2/static/ with the default credentials.

Set up the Pro2 Enterprise environment

Before you connect your Pro2 instances with your Enterprise View instance, you must set up a basic environment by loading the configuration file. The configuration file consists of all the properties and records that are necessary to set up the Pro2 Enterprise environment.

To load the configuration file:

  1. In the Pro2 web interface, navigate to Settings > Tools > Load Configuration.
  2. Click Select Files and load the replentbasev610.ini file from the Pro2 folder. The replentbasev610.ini file is the Pro2 configuration file.
  3. Click Submit.

Join your Pro2 instances to Pro2 Enterprise View

After the configuration file is successfully uploaded, your instance of the Pro2 Enterprise View is ready to be joined with your other instances of Pro2. In this phase of the set-up process, you transform Enterprise View from an empty dashboard to one that is full of meaningful data from across all of your Pro2 instances.
Note: A Pro2 instance cannot be joined to more than one Enterprise View instance.
To join your Pro2 instances:
  1. From an instance of Pro2 that is not joined with Enterprise View, navigate to the side menu and select Settings > Enterprise > Join.
  2. On the Join Enterprise window, enter:
    1. Instance name

      The instance name is designated at the time of installation and setup of that instance.

    2. Instance Abbreviation

      The instance abbreviation is determined at the time of installation and setup of that instance. The abbreviation is limited to two characters.

    3. Enterprise Application Server Name

      This is the same application server that is associated with your Enterprise View instance, for example, ent.

    4. Enterprise Host Name

      This is the same host name that is associated with your Enterprise View instance, for example, localhost.

    5. Enterprise Application Server Port Number

      The port number associated with your enterprise application server.

  3. (Optional) To test your connection to the application server, click the Application Server Test Connection button. If the test is unsuccessful, ensure that the instance information is correct and try again.
  4. Select Join to connect the Pro2 and Enterprise View instances. You can save your work and come back to it later by clicking the Save button.
Note: It takes a few minutes for the instances to connect.

Schedule an Enterprise Push job

After the connection between your Enterprise View instance and your other Pro2 instances are established, data is not automatically transferred between them. You must schedule an Enterprise push job. Your Pro2 instance to push data, metrics, and reports from an instance to the Enterprise View instance. This is how the Enterprise View instance stays up to date with all of your mission-critical replications.

To Schedule an Enterprise Push job:
  1. From an instance of Pro2 that is joined with Enterprise View, navigate to the side menu, and select Actions > Jobs > Scheduled Jobs.
  2. On the Scheduled jobs window, select New.
  3. On the Create Scheduled Jobs window, click on the Type drop-down list and select Enterprise Push.
  4. (Optional) Enter a description for the job. Entering a description can help you differentiate various jobs of the same type from one another.
  5. Under the Settings section, set how frequently the data is to be pushed to your Enterprise View instance. It is a best practice to schedule the pushes to occur frequently. To support this:
    1. Select Daily.
    2. Enter the Start Date and Start Time for when you want the job to begin, such as the current date and time.
    3. You can set the End Date and End Time for the job. This, however, stops the flow of data from your Pro2 instance to your Enterprise View instance and is not recommended. To run the job indefinitely, do not enter an End Date or an End Time.
    4. Set the Repeat task every to 1 minute.
  6. Click Save.

Start the job runner

For the last step of the Enterprise View setup process, you must start the job runner.

To start the job runner and initiate the scheduled Enterprise Push job, use the following procedure:
  1. On the machine where you have the Pro2 instance for which you have scheduled the job, navigate to the Pro2 Scripts folder, for example C:\Pro2\bprepl\Scripts.
  2. Select and execute the jobrunner.bat file.
  3. Navigate back to the Pro2 instances web interface and confirm that the job completed successfully.

Your Enterprise View instance is now set up, and data will begin to populate the dashboard. Repeat phases 6, 7, and 8 for each of your Pro2 instances that you want to join to your Enterprise View dashboard.