HTML Microdata document

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

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

Namespace Prefixes

Prefix	IRI
n26	https://www.openlinksw.com/about/id/entity/urn/howto:
n20	http://data.openlinksw.com/oplweb/opsys_family/
n23	http://data.openlinksw.com/oplweb/uda/howto/GenericLinuxMulti-TierRequestBrokerInstallationGuideStep8#
n2	http://data.openlinksw.com/oplweb/uda/howto/GenericLinuxMulti-TierRequestBrokerInstallationGuide#
n18	http://data.openlinksw.com/oplweb/uda/howto/GenericLinuxMulti-TierRequestBrokerInstallationGuideStep5#
n5	http://www.openlinksw.com/about/id/entity/urn/data:opl:web:seo:mdata:
n7	http://data.openlinksw.com/oplweb/uda/howto/GenericLinuxMulti-TierRequestBrokerInstallationGuideStep2#
oplsoft	http://www.openlinksw.com/ontology/software#
n27	https://www.openlinksw.com/about/id/entity/urn/mdata:websites:google:uda:howto:
wdrs	http://www.w3.org/2007/05/powder-s#
schema	http://schema.org/
n14	https://www.openlinksw.com/about/id/entity/urn/data:openlink:
n21	https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/data/turtle/general/
n11	http://wikis.openlinksw.com/UdaWikiWeb/
n15	http://data.openlinksw.com/oplweb/uda/howto/GenericLinuxMulti-TierRequestBrokerInstallationGuideStep7#
n8	https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
n16	http://data.openlinksw.com/oplweb/uda/howto/GenericLinuxMulti-TierRequestBrokerInstallationGuideStep4#
n17	https://www.openlinksw.com/about/id/entity/urn/mdata:websites:google:
n28	http://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
n12	http://data.openlinksw.com/oplweb/uda/howto/GenericLinuxMulti-TierRequestBrokerInstallationGuideStep1#
rdf	http://www.w3.org/1999/02/22-rdf-syntax-ns#
n22	http://data.openlinksw.com/oplweb/uda/howto/GenericLinuxMulti-TierRequestBrokerInstallationGuideStep10#
n24	http://data.openlinksw.com/oplweb/uda/howto/GenericLinuxMulti-TierRequestBrokerInstallationGuideStep9#
n4	https://www.openlinksw.com/about/id/entity/urn/data:opl:web:seo:mdata:
n9	http://data.openlinksw.com/oplweb/product_format/mt#
xsdh	http://www.w3.org/2001/XMLSchema#
n13	http://data.openlinksw.com/oplweb/uda/howto/GenericLinuxMulti-TierRequestBrokerInstallationGuideStep6#
n10	http://data.openlinksw.com/oplweb/uda/howto/GenericLinuxMulti-TierRequestBrokerInstallationGuideStep3#
n25	https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/uda2.openlinksw.com/data/turtle/general/

Statements

Subject Item: n2:this
schema:description: Installation of the Multi-Tier "Enterprise" Edition Server Components, on Unix-like OS OpenLink Multi-Tier Server Components Installation Installation of the Multi-Tier "Enterprise" Edition Server Components, on Linux or Unix-like OS
wdrs:describedby: n4:webs n5:offers n8:uda-howtos-qa.ttl n14:products n17:seo n21:uda-howtos.ttl n25:UDAHowAndStepByGuides.ttl n26:island n14:websites n27:seo n8:uda-howtos.ttl n28:uda-howtos-seo.ttl
schema:name: OpenLink Multi-Tier Server Components Installation Installation of the Multi-Tier "Enterprise" Edition Server Components, on Unix-like OS Installation of the Multi-Tier "Enterprise" Edition Server Components, on Linux or Unix-like OS
oplsoft:hasOperatingSystemFamily: n20:GenericLinux
schema:category: Installation Guide
schema:relatedLink: n11:InstallClientUNIX n11:InstallServerUNIX
schema:genre: n9:this
schema:text: <ol> <li> Log in to your Unix or Linux server machine, and Create and/or navigate to the intended OpenLink installation directory, e.g., <code>mkdir /opt/openlink</code> <code>cd /opt/openlink</code> Note: cd into the installation directory. </li> <li> The installation files ship as an installation shell script, a driver <code>.taz</code> archive, and an optional administrator <code>.taz</code> file. Download these documents using binary-preserving methods (e.g., ftp in BIN mode, or scp), and place them in your installation folder. </li> <li> Run the following command to start the installation: <pre><code>sh install.sh</code></pre> You must choose a TCP port at which the OpenLink Request Broker will listen for requests. The default is 5000. You will need to know this port number and the Broker host's IP address or hostname when configuring ODBC Data Source Names (DSNs). You must choose a TCP port at which the OpenLink Request Broker's HTTP-based Admin Assistant will listen for requests. The default is 8000. You will need to know this port number and the Broker host's IP address or hostname to access your Admistrator in a Web browser. The URL will look like this: <code>http://broker-host.example.com:8000/</code> </li> <li> Additional Configuration Parameters: <ul> <li> Log file? enables you to specify the name and location of the OpenLink Request Broker's HTTP-based Admin Assistant's log file. It is best to go with the default. </li> <li> You can choose to log all requests made to the OpenLink Request Broker's HTTP-based Admin Assistant. This is not diagnostic-level ODBC tracing nor multi-tier connection logging. The default is no, and this is generally appropriate. </li> <li> You can change the OpenLink Request Broker's HTTP-based Admin Assistant's default username from "<code>admin</code>." This is the username you will use when working with the OpenLink Request Broker's HTTP-based Admin Assistant. (You can set up other usernames later; consider this one similar to "<code>root</code>.") </li> <li> You can change the OpenLink Request Broker's HTTP-based Admin Assistant's default password from "<code>admin</code>." This is the password associated with the username you just set. </li> </ul> The Installation is complete. </li> <li> Optionally, The domain section of the rulebook contains the Database Agent connection parameters for the outgoing connections towards your Oracle database. Default Database Agent names for oracle use the following pattern: <code>[generic_ora{{version}}]</code>. For Example, the Oracle 12 parameters are located in: <code>[generic_ora12]</code>. Locate your Database Agent, and uncomment the "Connect Options" parameter. Add your hostname and port values using the following template: <code>Connect Options = -H {{host}} -P {{port number}}</code>. Configuration is complete. </li> <li> Installation is complete, proceed to making a test connection with your Client Component installation. </li> </ol> <ol> <li> Log in to your Unix or Linux server machine, and Create and/or navigate to the intended OpenLink installation directory, e.g., <code>mkdir /opt/openlink</code> <code>cd /opt/openlink</code> Note: cd into the installation directory. </li> <li> The installation files ship as an installation shell script, a driver <code>.taz</code> archive, and an optional administrator <code>.taz</code> file. Download these documents using binary-preserving methods (e.g., ftp in BIN mode, or scp), and place them in your installation folder. </li> <li> Run the following command to start the installation: <pre><code>sh install.sh</code></pre> You must choose a TCP port at which the OpenLink Request Broker will listen for requests. The default is 5000. You will need to know this port number and the Broker host's IP address or hostname when configuring ODBC Data Source Names (DSNs). You must choose a TCP port at which the OpenLink Request Broker's HTTP-based Admin Assistant will listen for requests. The default is 8000. You will need to know this port number and the Broker host's IP address or hostname to access your Admistrator in a Web browser. The URL will look like this: <code>http://broker-host.example.com:8000/</code> </li> <li> Additional Configuration Parameters: <ul> <li> Log file? enables you to specify the name and location of the OpenLink Request Broker's HTTP-based Admin Assistant's log file. It is best to go with the default. </li> <li> You can choose to log all requests made to the OpenLink Request Broker's HTTP-based Admin Assistant. This is not diagnostic-level ODBC tracing nor multi-tier connection logging. The default is no, and this is generally appropriate. </li> <li> You can change the OpenLink Request Broker's HTTP-based Admin Assistant's default username from "<code>admin</code>." This is the username you will use when working with the OpenLink Request Broker's HTTP-based Admin Assistant. (You can set up other usernames later; consider this one similar to "<code>root</code>.") </li> <li> You can change the OpenLink Request Broker's HTTP-based Admin Assistant's default password from "<code>admin</code>." This is the password associated with the username you just set. </li> </ul> The Installation is complete. </li> <li> Optionally, The domain section of the rulebook contains the Database Agent connection parameters for the outgoing connections towards your Oracle database. Default Database Agent names for oracle use the following pattern: <code>[generic_ora{{version}}]</code>. For Example, the Oracle 12 parameters are located in: <code>[generic_ora12]</code>. Locate your Database Agent, and uncomment the "Connect Options" parameter. Add your hostname and port values using the following template: <code>Connect Options = -H {{host}} -P {{port number}}</code>. Configuration is complete. </li> <li> Installation is complete, proceed to making a test connection with your Client Component installation. If you haven't installed this component, please follow one of the following guides: <ul> <li> <a href="#PreInstallationRequirementsfortheEnterpriseEditionMultiTierGenericClientODBCDriversformacOSClients">macOS</a> </li> <li> <a href="#PreInstallationRequirementsfortheEnterpriseEditionMultiTierGenericClientODBCDriversforWindows">Windows</a> </li> <li> <a href="http://data.openlinksw.com/oplweb/uda/howto/GenericLinuxMulti-TierGenericODBCClientInstallationGuide#this">Unix</a> </li> </ul> </li> <li> Optionally, if you would like to hard-code connection settings, proceed to one of the following Database Agent configuration guides: <ul> <li> Database Agents (Optional) <ul> <li> <a href="#ConfigurationoftheMultiTierOracleDatabaseAgentforGenericLinux">Oracle</a> </li> <li> <a href="#ConfigurationoftheMultiTierProgressDatabaseAgentforGenericLinux">Progress</a> </li> <li> <a href="#ConfigurationoftheMultiTierSQLServerDatabaseAgentforWindows">Microsoft SQL Server</a> </li> <li> <a href="#ConfigurationoftheMultiTierInformixDatabaseAgentforGenericLinux">Informix</a> </li> <li> <a href="#ConfigurationoftheMultiTierIngresDatabaseAgentforGenericLinux">Ingres</a> </li> </ul> </li> </ul> </li> </ol> <ol> <li> Log in to your Unix or Linux server machine, and Create and/or navigate to the intended OpenLink installation directory, e.g., <code>mkdir /opt/openlink</code> <code>cd /opt/openlink</code> Note: cd into the installation directory. </li> <li> The installation files ship as an installation shell script, a driver <code>.taz</code> archive, and an optional administrator <code>.taz</code> file. Download these documents using binary-preserving methods (e.g., ftp in BIN mode, or scp), and place them in your installation folder. </li> <li> Run the following command to start the installation: <pre><code>sh install.sh</code></pre> You must choose a TCP port at which the OpenLink Request Broker will listen for requests. The default is 5000. You will need to know this port number and the Broker host's IP address or hostname when configuring ODBC Data Source Names (DSNs). You must choose a TCP port at which the OpenLink Request Broker's HTTP-based Admin Assistant will listen for requests. The default is 8000. You will need to know this port number and the Broker host's IP address or hostname to access your Admistrator in a Web browser. The URL will look like this: <code>http://broker-host.example.com:8000/</code> </li> <li> Additional Configuration Parameters: <ul> <li> Log file? enables you to specify the name and location of the OpenLink Request Broker's HTTP-based Admin Assistant's log file. It is best to go with the default. </li> <li> You can choose to log all requests made to the OpenLink Request Broker's HTTP-based Admin Assistant. This is not diagnostic-level ODBC tracing nor multi-tier connection logging. The default is no, and this is generally appropriate. </li> <li> You can change the OpenLink Request Broker's HTTP-based Admin Assistant's default username from "<code>admin</code>." This is the username you will use when working with the OpenLink Request Broker's HTTP-based Admin Assistant. (You can set up other usernames later; consider this one similar to "<code>root</code>.") </li> <li> You can change the OpenLink Request Broker's HTTP-based Admin Assistant's default password from "<code>admin</code>." This is the password associated with the username you just set. </li> </ul> The Installation is complete. </li> <li> Optionally, The domain section of the rulebook contains the Database Agent connection parameters for the outgoing connections towards your Oracle database. Default Database Agent names for oracle use the following pattern: <code>[generic_ora{{version}}]</code>. For Example, the Oracle 12 parameters are located in: <code>[generic_ora12]</code>. Locate your Database Agent, and uncomment the "Connect Options" parameter. Add your hostname and port values using the following template: <code>Connect Options = -H {{host}} -P {{port number}}</code>. Configuration is complete. </li> <li> Installation is complete, proceed to making a test connection with your Client Component installation. </li> </ol>
rdf:type: schema:HowTo
schema:step: n7:this n10:this n12:this n13:this n15:this n16:this n18:this n22:this n23:this n24:this