• Topic
  • Discussion
  • UdaWikiWeb.InstallServerWIN32(Last) -- Owiki? , 2016-08-19 15:00:27 Edit owiki 2016-08-19 10:00:27

    Installation and Configuration of Enterprise Edition (Multi-Tier) Request Broker and Database Agent(s) for All Data Sources, for Windows

    Review Preinstallation Documentation: Pre-Installation Requirements

    Installation

    Our Enterprise Edition (Multi-Tier) server components installers for Windows are distributed as .msi files. You need to download one Enterprise Edition Request Broker installer (ntbrzzzz.msi for all 32-bit processor architectures, wabrzzzz.msi for x86_64, or wibrzzzz.msi for IA_64) and at least one Agent installer (same architecture) for the specific target data source(s). Follow the procedure below for each installer.

    1. Double-click the MSI file to start the installation:





    2. This is the Welcome dialog for the OpenLink Enterprise Edition Request Broker:





    3. Read the Software License Agreement before continuing your installation:





    4. The Request Broker installers will specifically prompt for the location of a local license file. (Agent installers do not, as their licensing is handled through the Broker.) Click the Browse button to locate a license file on your Windows machine. Check the "I don't want to install a license file" box, if you do not have one.





    5. Choose to perform a Typical, Complete (recommended), or Custom installation of the driver:





    6. If you chose the Custom option, specify where the components should be installed:





    7. You can choose which options to install, if you chose the custom installation option:





    8. A final confirmation screen is displayed for your review prior to performing the installation:





    9. The installation is complete:





    10. Repeat the above installation process with your agent installer. The agent install process is similar to the Request Broker installation but lacks a prompt for a license.

    Configuration

    Our server components require minimal configuration. In most instances, the primary configuration file (oplrqb.ini) is automatically configured for basic connectivity during installation. Use the following steps to check and enhance your individual agent settings.

    1. Launch the Enterprise Edition Administrative Assistant in a Web browser. The URL convention is:


      http://hostname_or_ip_address_of_machine_with_mt_server components:mt_admin_port/

      e.g.,


      http://myhost.example.com:8000/






    2. Click the Server Components Administration link.





    3. Click the Database Agent Administration link.





    4. Click the Database Settings by Wizard link.





    5. Login with your Administrative username and password. Both default to admin.





    6. Select the configuration section that you want to review. The naming convention for default database agent configuration sections is generic_ followed by an abbreviation for the OpenLink agent, e.g., generic_inf9.





    7. The Agent Details dialog allows you to rename the default agent configuration section and provide an optional comment. This is an advanced feature that should not be pursued for basic connectivity.





    8. Click Edit to continue.
    9. The first Connection Parameters dialog allows you to hardcode a single username and password for all client connections that are mapped to this agent configuration section. This will over-ride all authentication credentials provided by all clients, so can pose a significant security risk if highly privileged, or a significant limitation on functionality if privileges are too limited; thus, this option is usually not used for simple configurations.




      • User Name — A valid database user ID.
      • Password — A valid database password.
    10. Click Next to continue.
    11. The second Connection Parameters dialog allows you to hardcode a single Database, Read/Write access mode, and Connection Options for all client connections that are mapped to this agent configuration section. This will over-ride all such settings provided by all clients, so is often used to ease client-side configuration in both simple and complex environments. It can also be used to enhance database security in any environment.





      • Database Name — Takes a database name, Oracle SID, or similar, depending on target DBMS.
      • Read Only specifier — Specifies whether the connection is Read-only (does not permit execution of stored procedures nor anything that writes ) or Read/Write.
      • Connect Options — This field takes arguments that enable users to connect to databases running on different machines than the OpenLink Request Broker and Agent. MySQL, PostgreSQL, Microsoft SQL Server, and Sybase targets are always available in this way. Other DBMS may require additional native components or configuration for such "three-tier" connections to work. Review Complete Settings and Usage for Connect Options
    12. Click Next to continue.
    13. The next Connection Parameters dialog allows you to hardcode Server Options, a Domain, and a Host Name for all client connections that are mapped to this agent configuration section. This will over-ride all such options provided by all clients; thus, this option is usually not used for simple configurations.





      • Server Options — Server Options are typically Progress-specific options which are passed to the database native client at Agent start-up. Ensure that the options used when starting the actual database match the options passed in the Server Options field or ServerOptions Rulebook parameter.
      • DomainOnly used for n-tier connections, going through Proxy Agents. If you don't know what that is, you don't need to set this. The value must match a [Domain Alias], which is defined in the next Request Broker's Session Rulebook. This Alias typically represents the name and version of an OpenLink Agent. That agent version may differ from the DBMS version to which it connects. Note that advanced users may create custom domain names that follow their own localized conventions.
      • Host NameOnly used for n-tier connections, going through Proxy Agents. If you don't know what that is, you don't need to set this. Host name or IP address of the machine that contains the next Request Broker.
    14. Click Next to continue.
    15. The Secure SSL Connection dialog allows you to designate an SSL certificate. It also allows you to force all connections to use SSL (secure sockets layer) communications.





      • SSL Key File — The location of an SSL certificate, local to this Request Broker instance. If left blank, the Broker will self-sign when SSL-based connections are requested.
      • SSL Required — If set, all clients must use SSL-based connections.
    16. Click Next to continue.
    17. The first Application & Database Specific Parameters dialog allows you to enable "opsyslogin". Opsyslogin authenticates against the operating system, instead of the database.





      • Require Operating System Identity — If checked, the Request Broker will test to see that the username and password which are supplied to it are valid for log-in to the Broker host. If the authentication parameters are valid, it will start the database agent under the identity of the specified user. If unchecked, the username and password will be passed to the back-end database for authentication.
    18. Click Next to continue.
    19. The second Application & Database Specific Parameters dialog allows you to disable autocommit and enable Jet Engine catalogs.





      • No auto commit on startup — Default driver behavior is AutoCommit (box unchecked); i.e., each SQL statement is immediately and automatically committed. In rare cases, this causes problems with DBMS or client application transaction management; in such case, check the box, and all SQL will have to be committed by the client application and/or user.
      • Jet engine catalogs — Check this box if you intend to use this connection with Microsoft Access, Microsoft Excel, Microsoft SQL Server, or any Jet-based client application. This option causes certain datatypes to be handled better by the Microsoft Jet Engine, as documented elsewhere.
    20. Click Next to continue.
    21. The third Application & Database Specific Parameters dialog allows you to limit your rowset size and pass an initial SQL script.





      • Limit result set to n records — Allows you to define a limit on the maximum number of rows to be returned from a query. The default value of 0 means no limit.
      • Initial SQL script — Lets you specify a file containing SQL statements that will be run automatically against the database upon connection.
    22. Click Next to continue.
    23. The Startup parameters screen enables you to identify the OpenLink database agent to use for your ODBC connections. It also allows you to hardcode specific environment variables for the connection. Proper environment variables are essential for ODBC connectivity.





      • Executable name — Allows you to choose which OpenLink agent should serve all connections associated with this agent configuration section.
      • Environment VariablesOpenLink's agents are written using the database native CLI. Consequently, they use the same environment variables that database native clients use to connect to the relevant DBMS. Use this box to set them. Complete List of Variables by Database
    24. Click Next to continue.





    25. The Process Mapping dialog enables you to set your agent reuse rules. Reuse rules dictate whether or not an agent will be used for subsequent connections. Reuse of agents reduces overhead associated with agent spawning.








    26. Click Next to continue.
    27. The Save Settings dialog allows you to save your new agent settings. Check the Reinitialize checkbox to reinitialize the OpenLink Request Broker with these settings. Your new settings will not be active unless the Request Broker is reinitialized, or restarted in some cases. Note: Restarting the Broker cannot be done through this interface.





    28. Click Save to complete the agent configuration process.

    Proceed to Commercial Licensing Documentation

    Should you decide to purchase a commercial license at the end of your evaluation period, be sure to consult our documentation which explains the placement and uptake of commercial license files and the use of our OpenLink License Manager technology: License Technology & Application


    Referenced by...