This HTML5 document contains 36 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
n30http://data.openlinksw.com/oplweb/
n7https://www.openlinksw.com/about/id/entity/urn/howto:
n21http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierProgressPre-installationGuideStep7#
n15http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierProgressPre-installationGuideStep2#
n23http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierProgressPre-installationGuideStep10#
n8http://www.openlinksw.com/about/id/entity/urn/data:opl:web:seo:mdata:
n19http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierProgressPre-installationGuideStep9#
wdrshttp://www.w3.org/2007/05/powder-s#
n11http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierProgressPre-installationGuideStep4#
n14https://www.openlinksw.com/about/id/entity/urn/mdata:websites:google:uda:howto:
oplsofthttp://www.openlinksw.com/ontology/software#
schemahttp://schema.org/
n25https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/data/turtle/general/
n31http://wikis.openlinksw.com/UdaWikiWeb/
n12https://www.openlinksw.com/about/id/entity/urn/data:openlink:
n20http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierProgressPre-installationGuideStep6#
n5http://data.openlinksw.com/oplweb/dbms_family/Progress#
n28https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
n9http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierProgressPre-installationGuideStep1#
n24http://data.openlinksw.com/oplweb/opsys_family/Windows#
n26https://www.openlinksw.com/about/id/entity/urn/mdata:websites:google:
n18http://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
n27http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierRequestBrokerInstallationGuide#
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n17http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierProgressPre-installationGuideStep8#
n16http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierProgressPre-installationGuideStep3#
n2http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierProgressPre-installationGuide#
n22https://www.openlinksw.com/about/id/entity/urn/data:opl:web:seo:mdata:
n10http://data.openlinksw.com/oplweb/product_format/mt#
xsdhhttp://www.w3.org/2001/XMLSchema#
n13http://data.openlinksw.com/oplweb/uda/howto/WindowsMulti-TierProgressPre-installationGuideStep5#
n29https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/uda2.openlinksw.com/data/turtle/general/

Statements

Subject Item
n2:this
schema:description
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
wdrs:describedby
n7:island n8:offers n12:websites n14:seo n18:uda-howtos-seo.ttl n22:webs n12:products n25:uda-howtos.ttl n26:seo n28:uda-howtos-qa.ttl n28:uda-howtos.ttl n29:UDAHowAndStepByGuides.ttl
schema:name
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
oplsoft:hasDatabaseFamily
n5:this n30:Progress
oplsoft:hasOperatingSystemFamily
n24:this
schema:category
Pre-installation Guide
schema:relatedLink
n27:this n31:PreInstallServerWin32PRS
schema:genre
n10:this
schema:text
<ol> <li>You need to know a variety of information pertaining to your target Progress/OpenEdge DBMS instance and database: <ul> <li><strong>The SQL Engine Capabilities at Startup (4GL, SQL, or Both):</strong> <ul> <li>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.</li> <li>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.</li> <li>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.</li> </ul> </li> <li><strong>The Startup Mode (Sockets or Shared Memory):</strong> The Progress instance must be running in sockets mode to support SQL-92 connections.</li> <li><strong>Your Progress database server's TCP socket service name and/or port number:</strong> Specify the TCP socket service name and/or port number used by your Progress database server.</li> <li><strong>Your Progress database server's hostname or IP address:</strong> Provide the hostname or IP address of the server where your Progress database is located.</li> <li><strong>Whether your database queries fire 4GL triggers:</strong> Determine whether your database queries trigger 4GL events.</li> <li><strong>Whether your database queries involve Array fields:</strong> Identify if your database queries involve Array fields.</li> </ul> </li> <li>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.</li> <li>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.</li> <li>At the time of writing, the SQL-92 Progress native client is called <strong>Progress® SQL-92 Client Access</strong>. 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.</li> <li>If you are installing on a machine with <strong>Progress® SQL-92 Client Access</strong> (not Progress itself), the Progress Client must be configured to connect to the remote Progress DBMS.</li> <li>You must know whether TCP ports <strong>5000</strong> and <strong>8000</strong> 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.</li> <li>The local <code>/etc/services</code> 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.</li> <li>For best results, the Multi-Tier server components should be installed while logged in as the local Progress or Progress native client owner.</li> </ol> <ol> <li>You need to know a variety of information pertaining to your target Progress/OpenEdge DBMS instance and database: <ul> <li><strong>The SQL Engine Capabilities at Startup (4GL, SQL, or Both):</strong> <ul> <li>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.</li> <li>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.</li> <li>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.</li> </ul> </li> <li><strong>The Startup Mode (Sockets or Shared Memory):</strong> The Progress instance must be running in sockets mode to support SQL-92 connections.</li> <li><strong>Your Progress database server's TCP socket service name and/or port number:</strong> Specify the TCP socket service name and/or port number used by your Progress database server.</li> <li><strong>Your Progress database server's hostname or IP address:</strong> Provide the hostname or IP address of the server where your Progress database is located.</li> <li><strong>Whether your database queries fire 4GL triggers:</strong> Determine whether your database queries trigger 4GL events.</li> <li><strong>Whether your database queries involve Array fields:</strong> Identify if your database queries involve Array fields.</li> </ul> </li> <li>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.</li> <li>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.</li> <li>At the time of writing, the SQL-92 Progress native client is called <strong>Progress® SQL-92 Client Access</strong>. 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.</li> <li>If you are installing on a machine with <strong>Progress® SQL-92 Client Access</strong> (not Progress itself), the Progress Client must be configured to connect to the remote Progress DBMS.</li> <li>You must know whether TCP ports <strong>5000</strong> and <strong>8000</strong> 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.</li> <li>The local <code>/etc/services</code> 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.</li> <li>For best results, the Multi-Tier server components should be installed while logged in as the local Progress or Progress native client owner.</li> </ol> <ol> <li>You need to know a variety of information pertaining to your target Progress/OpenEdge DBMS instance and database: <ul> <li><strong>The SQL Engine Capabilities at Startup (4GL, SQL, or Both):</strong> <ul> <li>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.</li> <li>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.</li> <li>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.</li> </ul> </li> <li><strong>The Startup Mode (Sockets or Shared Memory):</strong> The Progress instance must be running in sockets mode to support SQL-92 connections.</li> <li><strong>Your Progress database server's TCP socket service name and/or port number:</strong> Specify the TCP socket service name and/or port number used by your Progress database server.</li> <li><strong>Your Progress database server's hostname or IP address:</strong> Provide the hostname or IP address of the server where your Progress database is located.</li> <li><strong>Whether your database queries fire 4GL triggers:</strong> Determine whether your database queries trigger 4GL events.</li> <li><strong>Whether your database queries involve Array fields:</strong> Identify if your database queries involve Array fields.</li> </ul> </li> <li>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.</li> <li>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.</li> <li>At the time of writing, the SQL-92 Progress native client is called <strong>Progress® SQL-92 Client Access</strong>. 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.</li> <li>If you are installing on a machine with <strong>Progress® SQL-92 Client Access</strong> (not Progress itself), the Progress Client must be configured to connect to the remote Progress DBMS.</li> <li>You must know whether TCP ports <strong>5000</strong> and <strong>8000</strong> 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.</li> <li>The local <code>/etc/services</code> 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.</li> <li>For best results, the Multi-Tier server components should be installed while logged in as the local Progress or Progress native client owner.</li> </ol> <ol> <li>You need to know a variety of information pertaining to your target Progress/OpenEdge DBMS instance and database: <ul> <li><strong>The SQL Engine Capabilities at Startup (4GL, SQL, or Both):</strong> <ul> <li>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.</li> <li>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.</li> <li>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.</li> </ul> </li> <li><strong>The Startup Mode (Sockets or Shared Memory):</strong> The Progress instance must be running in sockets mode to support SQL-92 connections.</li> <li><strong>Your Progress database server's TCP socket service name and/or port number:</strong> Specify the TCP socket service name and/or port number used by your Progress database server.</li> <li><strong>Your Progress database server's hostname or IP address:</strong> Provide the hostname or IP address of the server where your Progress database is located.</li> <li><strong>Whether your database queries fire 4GL triggers:</strong> Determine whether your database queries trigger 4GL events.</li> <li><strong>Whether your database queries involve Array fields:</strong> Identify if your database queries involve Array fields.</li> </ul> </li> <li>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.</li> <li>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.</li> <li>At the time of writing, the SQL-92 Progress native client is called <strong>Progress® SQL-92 Client Access</strong>. 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.</li> <li>If you are installing on a machine with <strong>Progress® SQL-92 Client Access</strong> (not Progress itself), the Progress Client must be configured to connect to the remote Progress DBMS.</li> <li>You must know whether TCP ports <strong>5000</strong> and <strong>8000</strong> 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.</li> <li>The local <code>/etc/services</code> 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.</li> <li>For best results, the Multi-Tier server components should be installed while logged in as the local Progress or Progress native client owner.</li> </ol>
rdf:type
schema:HowTo
schema:step
n9:this n11:this n13:this n15:this n16:this n17:this n19:this n20:this n21:this n23:this