"Pre-Installation Requirements for the Enterprise Edition (Multi-Tier) Request Broker and Database Agent(s) for Progress/OpenEdge 9.x, 10.x, and later (SQL-92), for Windows" . . . . . "
    \n
  1. You need to know a variety of information pertaining to your target Progress/OpenEdge DBMS instance and database:\n
      \n
    • The SQL Engine Capabilities at Startup (4GL, SQL, or Both):\n
        \n
      • Progress 8.x and earlier only support 4GL, also referred to as SQL-89 mode. Our SQL-92 Agents cannot be used with Progress 8.x or earlier.
        • \n
      • Progress 9.x has a hybrid engine and supports both 4GL and SQL by default, but may be restricted to either at launch. Check the Progress 9.x log file to see what your engine is doing. The Progress instance must be running with SQL support for SQL-92 connections.
        • \n
      • Progress OpenEdge 10.x and later only support SQL, also referred to as SQL-92 mode. Our SQL-89 Agents cannot be used with Progress OpenEdge 10.x or later.
        • \n
      \n
      • \n
    • The Startup Mode (Sockets or Shared Memory): The Progress instance must be running in sockets mode to support SQL-92 connections.
      • \n
    • Your Progress database server's TCP socket service name and/or port number: Specify the TCP socket service name and/or port number used by your Progress database server.
      • \n
    • Your Progress database server's hostname or IP address: Provide the hostname or IP address of the server where your Progress database is located.
      • \n
    • Whether your database queries fire 4GL triggers: Determine whether your database queries trigger 4GL events.
      • \n
    • Whether your database queries involve Array fields: Identify if your database queries involve Array fields.
      • \n
    \n
    2. \n
  2. Recommended and optimal deployment has the Multi-Tier server components installed on the same machine as Progress itself, and there are no other software requirements.
    3. \n
  3. If you cannot install the Multi-Tier server components on the Progress host, they must be installed on the same host as a Progress native client.
    4. \n
  4. At the time of writing, the SQL-92 Progress native client is called Progress\u00AE SQL-92 Client Access. Product names may vary over time. You must know whether the local Progress components are 32-bit or 64-bit. The Multi-Tier server components must match the bit format of the local Progress components, not the OS.
    5. \n
  5. If you are installing on a machine with Progress\u00AE SQL-92 Client Access (not Progress itself), the Progress Client must be configured to connect to the remote Progress DBMS.
    6. \n
  6. You must know whether TCP ports 5000 and 8000 are already in use on the Broker host. These ports are the defaults used by our Request Broker and Web-based Admin Assistant. If other services are using these, you will need to assign different (unused) ports to the new services during installation.
    7. \n
  7. The local /etc/services file should include the Progress service definition; if not, the Progress socket service must be specified by port number, not name, in all our configuration, whether server-side or client-side.
    8. \n
  8. For best results, the Multi-Tier server components should be installed while logged in as the local Progress or Progress native client owner.
    9. \n
" . . . . . . . "Pre-Installation Requirements for the Enterprise Edition (Multi-Tier) Request Broker and Database Agent(s) for Progress/OpenEdge 9.x, 10.x, and later (SQL-92), for Windows" . . . . . . . . "
    \n
  1. You need to know a variety of information pertaining to your target Progress/OpenEdge DBMS instance and database:\n
      \n
    • The SQL Engine Capabilities at Startup (4GL, SQL, or Both):\n
        \n
      • Progress 8.x and earlier only support 4GL, also referred to as SQL-89 mode. Our SQL-92 Agents cannot be used with Progress 8.x or earlier.
        • \n
      • Progress 9.x has a hybrid engine and supports both 4GL and SQL by default, but may be restricted to either at launch. Check the Progress 9.x log file to see what your engine is doing. The Progress instance must be running with SQL support for SQL-92 connections.
        • \n
      • Progress OpenEdge 10.x and later only support SQL, also referred to as SQL-92 mode. Our SQL-89 Agents cannot be used with Progress OpenEdge 10.x or later.
        • \n
      \n
      • \n
    • The Startup Mode (Sockets or Shared Memory): The Progress instance must be running in sockets mode to support SQL-92 connections.
      • \n
    • Your Progress database server's TCP socket service name and/or port number: Specify the TCP socket service name and/or port number used by your Progress database server.
      • \n
    • Your Progress database server's hostname or IP address: Provide the hostname or IP address of the server where your Progress database is located.
      • \n
    • Whether your database queries fire 4GL triggers: Determine whether your database queries trigger 4GL events.
      • \n
    • Whether your database queries involve Array fields: Identify if your database queries involve Array fields.
      • \n
    \n
    2. \n
  2. Recommended and optimal deployment has the Multi-Tier server components installed on the same machine as Progress itself, and there are no other software requirements.
    3. \n
  3. If you cannot install the Multi-Tier server components on the Progress host, they must be installed on the same host as a Progress native client.
    4. \n
  4. At the time of writing, the SQL-92 Progress native client is called Progress\u00C2\u00AE SQL-92 Client Access. Product names may vary over time. You must know whether the local Progress components are 32-bit or 64-bit. The Multi-Tier server components must match the bit format of the local Progress components, not the OS.
    5. \n
  5. If you are installing on a machine with Progress\u00C2\u00AE SQL-92 Client Access (not Progress itself), the Progress Client must be configured to connect to the remote Progress DBMS.
    6. \n
  6. You must know whether TCP ports 5000 and 8000 are already in use on the Broker host. These ports are the defaults used by our Request Broker and Web-based Admin Assistant. If other services are using these, you will need to assign different (unused) ports to the new services during installation.
    7. \n
  7. The local /etc/services file should include the Progress service definition; if not, the Progress socket service must be specified by port number, not name, in all our configuration, whether server-side or client-side.
    8. \n
  8. For best results, the Multi-Tier server components should be installed while logged in as the local Progress or Progress native client owner.
    9. \n
" . "
    \r\n
  1. You need to know a variety of information pertaining to your target Progress/OpenEdge DBMS instance and database:\r\n
      \r\n
    • The SQL Engine Capabilities at Startup (4GL, SQL, or Both):\r\n
        \r\n
      • Progress 8.x and earlier only support 4GL, also referred to as SQL-89 mode. Our SQL-92 Agents cannot be used with Progress 8.x or earlier.
        • \r\n
      • Progress 9.x has a hybrid engine and supports both 4GL and SQL by default, but may be restricted to either at launch. Check the Progress 9.x log file to see what your engine is doing. The Progress instance must be running with SQL support for SQL-92 connections.
        • \r\n
      • Progress OpenEdge 10.x and later only support SQL, also referred to as SQL-92 mode. Our SQL-89 Agents cannot be used with Progress OpenEdge 10.x or later.
        • \r\n
      \r\n
      • \r\n
    • The Startup Mode (Sockets or Shared Memory): The Progress instance must be running in sockets mode to support SQL-92 connections.
      • \r\n
    • Your Progress database server's TCP socket service name and/or port number: Specify the TCP socket service name and/or port number used by your Progress database server.
      • \r\n
    • Your Progress database server's hostname or IP address: Provide the hostname or IP address of the server where your Progress database is located.
      • \r\n
    • Whether your database queries fire 4GL triggers: Determine whether your database queries trigger 4GL events.
      • \r\n
    • Whether your database queries involve Array fields: Identify if your database queries involve Array fields.
      • \r\n
    \r\n
    2. \r\n
  2. Recommended and optimal deployment has the Multi-Tier server components installed on the same machine as Progress itself, and there are no other software requirements.
    3. \r\n
  3. If you cannot install the Multi-Tier server components on the Progress host, they must be installed on the same host as a Progress native client.
    4. \r\n
  4. At the time of writing, the SQL-92 Progress native client is called Progress\u00AE SQL-92 Client Access. Product names may vary over time. You must know whether the local Progress components are 32-bit or 64-bit. The Multi-Tier server components must match the bit format of the local Progress components, not the OS.
    5. \r\n
  5. If you are installing on a machine with Progress\u00AE SQL-92 Client Access (not Progress itself), the Progress Client must be configured to connect to the remote Progress DBMS.
    6. \r\n
  6. You must know whether TCP ports 5000 and 8000 are already in use on the Broker host. These ports are the defaults used by our Request Broker and Web-based Admin Assistant. If other services are using these, you will need to assign different (unused) ports to the new services during installation.
    7. \r\n
  7. The local /etc/services file should include the Progress service definition; if not, the Progress socket service must be specified by port number, not name, in all our configuration, whether server-side or client-side.
    8. \r\n
  8. For best results, the Multi-Tier server components should be installed while logged in as the local Progress or Progress native client owner.
    9. \r\n
" . . . . . . "
    \r\n
  1. You need to know a variety of information pertaining to your target Progress/OpenEdge DBMS instance and database:\r\n
      \r\n
    • The SQL Engine Capabilities at Startup (4GL, SQL, or Both):\r\n
        \r\n
      • Progress 8.x and earlier only support 4GL, also referred to as SQL-89 mode. Our SQL-92 Agents cannot be used with Progress 8.x or earlier.
        • \r\n
      • Progress 9.x has a hybrid engine and supports both 4GL and SQL by default, but may be restricted to either at launch. Check the Progress 9.x log file to see what your engine is doing. The Progress instance must be running with SQL support for SQL-92 connections.
        • \r\n
      • Progress OpenEdge 10.x and later only support SQL, also referred to as SQL-92 mode. Our SQL-89 Agents cannot be used with Progress OpenEdge 10.x or later.
        • \r\n
      \r\n
      • \r\n
    • The Startup Mode (Sockets or Shared Memory): The Progress instance must be running in sockets mode to support SQL-92 connections.
      • \r\n
    • Your Progress database server's TCP socket service name and/or port number: Specify the TCP socket service name and/or port number used by your Progress database server.
      • \r\n
    • Your Progress database server's hostname or IP address: Provide the hostname or IP address of the server where your Progress database is located.
      • \r\n
    • Whether your database queries fire 4GL triggers: Determine whether your database queries trigger 4GL events.
      • \r\n
    • Whether your database queries involve Array fields: Identify if your database queries involve Array fields.
      • \r\n
    \r\n
    2. \r\n
  2. Recommended and optimal deployment has the Multi-Tier server components installed on the same machine as Progress itself, and there are no other software requirements.
    3. \r\n
  3. If you cannot install the Multi-Tier server components on the Progress host, they must be installed on the same host as a Progress native client.
    4. \r\n
  4. At the time of writing, the SQL-92 Progress native client is called Progress\u00C2\u00AE SQL-92 Client Access. Product names may vary over time. You must know whether the local Progress components are 32-bit or 64-bit. The Multi-Tier server components must match the bit format of the local Progress components, not the OS.
    5. \r\n
  5. If you are installing on a machine with Progress\u00C2\u00AE SQL-92 Client Access (not Progress itself), the Progress Client must be configured to connect to the remote Progress DBMS.
    6. \r\n
  6. You must know whether TCP ports 5000 and 8000 are already in use on the Broker host. These ports are the defaults used by our Request Broker and Web-based Admin Assistant. If other services are using these, you will need to assign different (unused) ports to the new services during installation.
    7. \r\n
  7. The local /etc/services file should include the Progress service definition; if not, the Progress socket service must be specified by port number, not name, in all our configuration, whether server-side or client-side.
    8. \r\n
  8. For best results, the Multi-Tier server components should be installed while logged in as the local Progress or Progress native client owner.
    9. \r\n
" . . . "Pre-installation Guide" . . . . . .