Use the Pro2-6.1.bin file to install Pro2 and configure a standard instance of the Pro2 web user interface, or an Enterprise View instance, on your Linux machine.

Install Pro2

Use the following procedure to install Pro2 for Linux standard or Enterprise View:

  1. Locate and execute either the Pro2-6.1-ent.bin file for Enterprise View, or the Pro2-6.1.bin file for standard.
  2. In the Pro2 installer, click Next to start the installation process.
  3. Specify the install folder path. For example, USER_INSTALL_DIR=/largedisk/<user>/pro2inst.
  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, OE_INSTALL_DIR=/largedisk/<user>/120/linuxx86_64/build/dlc.

  5. On the PAS Ports screen, enter the port information for your PAS for OpenEdge instance and designate the instance name. For example:
    HTTP Port 9991
    HTTPS Port 9992
    Shut Down Port 9993
    Instance Name Pro2Web
  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. When completed, click Done.

Create a Pro2 database​

The repl and replperf database instances contain the replication statistics data that is displayed on the Dashboard tab of the Pro2 web user interface.

Use the following procedure to create a Pro2 database:

  1. Start a Proenv session.
  2. From the Proenv window go to the Pro2 folder > db
    Note: Check the directory of the db folder to view the database instances.
  3. Create an empty pro2ent database instance by entering the prodb pro2 emptycommand.
  4. Load the required table definitions in the pro2ent database by entering the prowin pro2 -1. The Procedure Editor window appears.
  5. Navigate to Tools > Data Administration.
  6. In the Data Administration window, navigate to Admin > Load Data and Definitions > Data Definitions (.df file)….
  7. In the Load Data Definitions window, load the pro2.df file and click OK.
    Note: The pro2.df file is located in <Pro2 folder>/db.
  8. Start the pro2ent database by typing: Proserve pro2

Update replProc.pf

In the pro2 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 will display tables.

Start a PASOE instance

Now that the pro2ent database is set up successfully, start the PAS instance and log in to the Pro2 web application.

  1. Start a Proenv session.
  2. Navigate to the Pro2 folder where you installed Pro2
  3. Type Pro2LAN\bin\tcman.sh env
  4. TypePro2LAN\bin\tcman.sh start
  5. To check if the instance has started successfully, type Pro2LAN\bin\tcman.sh env. The server running section shows a number if the instance has started.
  6. Open any browser and log in at localhost:9991/pro2/static/
  7. Use the default credentials.

Setup the Pro2 environment

Before using the Pro2 web interface, you must set up basic configuration by loading the default configuration file. The configuration file consists of all the default properties and records which are necessary to set up the Pro2 environment.

Use the following procedure to load the configuration file:

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

If you have been using the Pro2-6.1-ent.bin file to set up Enterprise View on your Linux machine, use the following procedures to finish the Enterprise View configuration process.

Join your Pro2 instances to Enterprise View

After the configuration file is successfully uploaded, your instance of 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 husk of a dashboard to one that is full of meaningful data from across all of your Pro2 instances.
Note: A Pro2 instance can not be Joined to more than one Enterprise View instance.
Use the following procedure 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 screen, enter:
    1. Instance name

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

    2. Instance Abbreviation

      As with the instance name, the instance abbreviation would also be designated 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) Test your connection to the application server with 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 together. Alternately, you can save your work and come back to it later by using the Save button.
Note: It takes a few minutes for the instances to connect. Go get a hot drink and refresh yourself.

Schedule an Enterprise Push job

After the connection between your Enterprise View Instance and your other Pro2 Instances are established, you might notice that there's no data flowing between them. Don't worry, your instance just need a little push to get things moving. By scheduling an Enterprise Push job, you instruct 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.

Use the following procedure 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 screen, select New.
  3. On the Create Scheduled Jobs screen, click on the Type drop-down 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 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. If you so desire, 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 kick-start the scheduled Enterprise Push job by starting 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.sh file.
  3. Navigate back to the Pro2 instances web UI and confirm that the job completed successfully.

Your Enterprise View instance is now set up, and data will begin to populate the dashboard.