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 DBMS Requirements You need to know a variety of information pertaining to your target Progress/OpenEdge DBMS instance and database: The SQL Engine Capabilities at Startup (4GL, SQL, or Both) — 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. 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. 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. The Startup Mode (Sockets or Shared Memory) — The Progress instance must be running in sockets mode to support SQL-92 connections. Your Progress database server's TCP socket service name and/or port number Your Progress database server's hostname or IP address Whether your database queries fire 4GL triggers Whether your database queries involve Array fields Software Requirements Recommended and optimal deployment has the Enterprise Edition server components installed on the same machine as Progress itself, and there are no other software requirements. If you cannot install the Enterprise Edition server components on the Progress host, they must be installed on the same host as a Progress native client. At the time of writing, the SQL-92 Progress native client is called Progress® 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 Enterprise Edition server components must match the bit format of the local Progress components, not the OS. Configuration Requirements If you are installing on a machine with Progress® SQL-92 Client Access (not Progress itself), the Progress Client must be configured to connect to the remote Progress DBMS. 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. 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. For best results, the Enterprise Edition server components should be installed while logged in as the local Progress or Progress native client owner. All Progress-related environment variables should be set prior to installation. This is typically accomplished simply by logging in as the local Progress or Progress native client owner. Next... Proceed to Installation & Configuration