. . . . . . "Installation of the Multi-Tier \"Enterprise\" Edition Server Components, on Unix-like OS" . . "
    \n
  1. \n Log in to your Unix or Linux server machine, and Create and/or navigate to the intended OpenLink installation directory, e.g.,
    \n mkdir /opt/openlink
    \n cd /opt/openlink
    \n
    \n Note: cd into the installation directory.\n
  2. \n
  3. \n The installation files ship as an installation shell script, a driver .taz archive, and an optional administrator .taz file. Download these documents using binary-preserving methods (e.g., ftp in BIN mode, or scp), and place them in your installation folder.\n
  4. \n
  5. \n Run the following command to start the installation:
    \n
    sh install.sh
    \n
    \n 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:
    \n http://broker-host.example.com:8000/\n
  6. \n
  7. \n Additional Configuration Parameters:\n
      \n
    • \n 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.\n
    • \n
    • \n 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.\n
    • \n
    • \n You can change the OpenLink Request Broker's HTTP-based Admin Assistant's default username from \"admin.\" 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 \"root.\")\n
    • \n
    • \n You can change the OpenLink Request Broker's HTTP-based Admin Assistant's default password from \"admin.\" This is the password associated with the username you just set.\n
    • \n
    \n The Installation is complete.\n
  8. \n
  9. \n Optionally, The domain section of the rulebook contains the Database Agent connection parameters for the outgoing connections towards your Oracle database.
    \n Default Database Agent names for oracle use the following pattern:
    \n [generic_ora{{version}}]. For Example, the Oracle 12 parameters are located in:
    \n [generic_ora12].
    \n Locate your Database Agent, and uncomment the \"Connect Options\" parameter.
    \n Add your hostname and port values using the following template:
    \n Connect Options = -H {{host}} -P {{port number}}.
    \n Configuration is complete.\n
  10. \n
  11. \n Installation is complete, proceed to making a test connection with your Client Component installation. \n
  12. \n
" . . "OpenLink Multi-Tier Server Components Installation " . . . . . . . . . . . . . . "OpenLink Multi-Tier Server Components Installation " . "
    \r\n
  1. \r\n Log in to your Unix or Linux server machine, and Create and/or navigate to the intended OpenLink installation directory, e.g.,
    \r\n mkdir /opt/openlink
    \r\n cd /opt/openlink
    \r\n
    \r\n Note: cd into the installation directory.\r\n
  2. \r\n
  3. \r\n The installation files ship as an installation shell script, a driver .taz archive, and an optional administrator .taz file. Download these documents using binary-preserving methods (e.g., ftp in BIN mode, or scp), and place them in your installation folder.\r\n
  4. \r\n
  5. \r\n Run the following command to start the installation:
    \r\n
    sh install.sh
    \r\n
    \r\n 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:
    \r\n http://broker-host.example.com:8000/\r\n
  6. \r\n
  7. \r\n Additional Configuration Parameters:\r\n
      \r\n
    • \r\n 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.\r\n
    • \r\n
    • \r\n 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.\r\n
    • \r\n
    • \r\n You can change the OpenLink Request Broker's HTTP-based Admin Assistant's default username from \"admin.\" 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 \"root.\")\r\n
    • \r\n
    • \r\n You can change the OpenLink Request Broker's HTTP-based Admin Assistant's default password from \"admin.\" This is the password associated with the username you just set.\r\n
    • \r\n
    \r\n The Installation is complete.\r\n
  8. \r\n
  9. \r\n Optionally, The domain section of the rulebook contains the Database Agent connection parameters for the outgoing connections towards your Oracle database.
    \r\n Default Database Agent names for oracle use the following pattern:
    \r\n [generic_ora{{version}}]. For Example, the Oracle 12 parameters are located in:
    \r\n [generic_ora12].
    \r\n Locate your Database Agent, and uncomment the \"Connect Options\" parameter.
    \r\n Add your hostname and port values using the following template:
    \r\n Connect Options = -H {{host}} -P {{port number}}.
    \r\n Configuration is complete.\r\n
  10. \r\n
  11. \r\n 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:\r\n \r\n
  12. \r\n
  13. \r\n Optionally, if you would like to hard-code connection settings, proceed to one of the following Database Agent configuration guides:\r\n \r\n
  14. \r\n
" . "Installation Guide" . . "
    \r\n
  1. \r\n Log in to your Unix or Linux server machine, and Create and/or navigate to the intended OpenLink installation directory, e.g.,
    \r\n mkdir /opt/openlink
    \r\n cd /opt/openlink
    \r\n
    \r\n Note: cd into the installation directory.\r\n
  2. \r\n
  3. \r\n The installation files ship as an installation shell script, a driver .taz archive, and an optional administrator .taz file. Download these documents using binary-preserving methods (e.g., ftp in BIN mode, or scp), and place them in your installation folder.\r\n
  4. \r\n
  5. \r\n Run the following command to start the installation:
    \r\n
    sh install.sh
    \r\n
    \r\n 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:
    \r\n http://broker-host.example.com:8000/\r\n
  6. \r\n
  7. \r\n Additional Configuration Parameters:\r\n
      \r\n
    • \r\n 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.\r\n
    • \r\n
    • \r\n 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.\r\n
    • \r\n
    • \r\n You can change the OpenLink Request Broker's HTTP-based Admin Assistant's default username from \"admin.\" 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 \"root.\")\r\n
    • \r\n
    • \r\n You can change the OpenLink Request Broker's HTTP-based Admin Assistant's default password from \"admin.\" This is the password associated with the username you just set.\r\n
    • \r\n
    \r\n The Installation is complete.\r\n
  8. \r\n
  9. \r\n Optionally, The domain section of the rulebook contains the Database Agent connection parameters for the outgoing connections towards your Oracle database.
    \r\n Default Database Agent names for oracle use the following pattern:
    \r\n [generic_ora{{version}}]. For Example, the Oracle 12 parameters are located in:
    \r\n [generic_ora12].
    \r\n Locate your Database Agent, and uncomment the \"Connect Options\" parameter.
    \r\n Add your hostname and port values using the following template:
    \r\n Connect Options = -H {{host}} -P {{port number}}.
    \r\n Configuration is complete.\r\n
  10. \r\n
  11. \r\n Installation is complete, proceed to making a test connection with your Client Component installation. \r\n
  12. \r\n
" . . . . . "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" . "Installation of the Multi-Tier \"Enterprise\" Edition Server Components, on Linux or Unix-like OS" . .