http://docs.openlinksw.com/mt/srvcompinstall.html Multi-Tier User Guide Mon, 16 Nov 2009 14:28:45 GMT webmaster@openlinksw.com http://docs.openlinksw.com/mt/../images/mt/misc/logo.jpg http://docs.openlinksw.com/mt/srvcompinstall.html Multi-Tier User Guide http://docs.openlinksw.com/mt/oplmgr.html OpenLink License Manager Usage Notes http://docs.openlinksw.com/mt/oplmgr.html Mon, 16 Nov 2009 14:28:45 GMT http://docs.openlinksw.com/mt/winproductlic.html Product Licensing http://docs.openlinksw.com/mt/winproductlic.html Mon, 16 Nov 2009 14:28:45 GMT http://docs.openlinksw.com/mt/getlic.html Upgrading the License http://docs.openlinksw.com/mt/getlic.html Mon, 16 Nov 2009 14:28:45 GMT You may purchase a permanent license key online via the Internet. To purchase a key follow these instructions: In the event that you are unable to use the online ordering system, then please contact sales@openlinksw.com or sales@openlinksw.co.uk to obtain the permanent license key. http://docs.openlinksw.com/mt/wsrvcompinst.html Windows 95/98/NT/XP/2000 Install http://docs.openlinksw.com/mt/wsrvcompinst.html Mon, 16 Nov 2009 14:28:45 GMT If the OpenLink Broker does not respond to client requests, or there was a Broker creation error during the install, then you can verify its operation as follows: http://docs.openlinksw.com/mt/macxsrvinst.html Mac OS X http://docs.openlinksw.com/mt/macxsrvinst.html Mon, 16 Nov 2009 14:28:45 GMT OpenLink Software's server components are fully supported on Mac OS X. Users of Mac OS X 10.2.x ("Jaguar") and later may use the fully migrated GUI components; users of Mac OS X 10.1.5 and earlier must use the Darwin-based components (installation covered in the UNIX and Linux section, below). As shipped from Apple, Mac OS X did not include any ODBC support until Jaguar. The ODBC Driver Manager, Data Source Administrator, etc. - all had to be delivered with the Drivers. When Apple introduced Darwin, an Open-Source project meant to form the kernel of Mac OS X, OpenLink determined to port its open-source iODBC Driver Manager to the new platform. With the introduction of the Preview Release of Mac OS X, the traditional set of dynamic libraries was broadened to include a system of Frameworks to encourage the development of fully ODBC compliant, native Mac OS X drivers and client applications. http://docs.openlinksw.com/mt/unixsrvcompinst.html UNIX & Linux Install http://docs.openlinksw.com/mt/unixsrvcompinst.html Mon, 16 Nov 2009 14:28:45 GMT http://docs.openlinksw.com/mt/servcompinstcont.html Installed Files & Locations http://docs.openlinksw.com/mt/servcompinstcont.html Mon, 16 Nov 2009 14:28:45 GMT The core components required by the Request Broker and Database Agents are situated within the "bin" and "bin/w3config" sub-directories under your OpenLink server components base installation directory. Each of these components is described below and grouped by directory location. On Windows, the default base installation directory is C:\Progam Files\OpenLink\. On Mac OS X, the non-configurable base installation directory is //Library/Application Support/openlink/. http://docs.openlinksw.com/mt/versionnos.html Obtaining Component Details From The Command Line http://docs.openlinksw.com/mt/versionnos.html Mon, 16 Nov 2009 14:28:45 GMT This approach provides you with information about the actual executable file, it includes: Version Number - this is a component identifier that indicates the version number specific of a specific OpenLink Component Release Number - this is an identifier for a collection of OpenLink Components, numerous components with different version numbers make up an OpenLink Data Access Drivers commercial release. http://docs.openlinksw.com/mt/mtfirewalling.html Configuring a Firewall for use with UDA Multi-Tier http://docs.openlinksw.com/mt/mtfirewalling.html Mon, 16 Nov 2009 14:28:45 GMT A multi-tier installation requires the following firewall considerations: On the server on which the Request Broker runs, you must allow your clients to connect to port 5000/tcp (or the value of the "Listen" directive in oplrqb.ini). On the server, you must allow clients to connect to ports 5001/tcp et seq (the values between the "PortLow" and "PortHigh" directives in oplrqb.ini).