http://docs.openlinksw.com/mt/AgentCompAdm.html Multi-Tier User Guide Wed, 09 Apr 2008 14:37:12 GMT webmaster@openlinksw.com http://docs.openlinksw.com/mt/../images/mt/misc/logo.jpg http://docs.openlinksw.com/mt/AgentCompAdm.html Multi-Tier User Guide http://docs.openlinksw.com/mt/agentconfig.html Administration Assistant http://docs.openlinksw.com/mt/agentconfig.html Wed, 09 Apr 2008 14:37:12 GMT Every database engine has a one or more key values that need to be set in order for database clients to be able to communicate with database servers. These values take the form of host operating system environment variables, database connection string formats/parameters, or a combination of both. Configuring your OpenLink database agent is all about creating session initialization templates in the Sessions Rules Book which map key database client values with OpenLink Agent Template Attributes. OpenLink provides a user friendly utility for configuring your database agents, namely the OpenLink Admin Assistant. Another option is to edit the rule book manually, but the availability of the utility makes this a less recommended option, certainly one for experienced OpenLink users only. http://docs.openlinksw.com/mt/dbspecset.html Agent-Specific Settings http://docs.openlinksw.com/mt/dbspecset.html Wed, 09 Apr 2008 14:37:12 GMT OpenLink database agents are database clients built using the SQL Call Level or Embedded SQL interfaces of the respective supported backend database engines. Thus, the process of configuring or administering a database agent is similar in essence to what you would have to do if you were administering a native database client. Database engines use environment variables to creating a database specific operating space within which database clients and servers interact, these environment typically address the following important database session related issues: The sections that follow address specific environment settings that affect the configuration of your OpenLink database agents, the values provided can supplanted values used in the Admin Assistant configuration examples provided in the prior section. http://docs.openlinksw.com/mt/unicode.html Database Configuration for Unicode http://docs.openlinksw.com/mt/unicode.html Wed, 09 Apr 2008 14:37:12 GMT Below are instructions on the configuration of the Unicode enabled drivers and databases for testing. Typically the first task to be performed is the creation of a Unicode enabled Database, which for most databases means configuring them to store data using the UTF8 encoding. http://docs.openlinksw.com/mt/getagntinfo.html Obtaining Agent Information http://docs.openlinksw.com/mt/getagntinfo.html Wed, 09 Apr 2008 14:37:12 GMT OpenLink Database agents have a specific naming convention, reflecting the identification of a particular database engine, and in some case specific versions of a given database engine. The OpenLink executable binary file naming convention consists of three distinctive logical parts: <db_engine>[<db_ver>]_<[sv|mv]>[.exe] http://docs.openlinksw.com/mt/relinkdb.html Linking OpenLink DB Agents http://docs.openlinksw.com/mt/relinkdb.html Wed, 09 Apr 2008 14:37:12 GMT http://docs.openlinksw.com/mt/conprog.html Progress Troubleshooting & Advanced Configuration http://docs.openlinksw.com/mt/conprog.html Wed, 09 Apr 2008 14:37:12 GMT It assumed at this point that you have successfully installed OpenLink's client and server components on one or more computers within your I.T. infrastructure. Understanding the fundamental concepts that drive the OpenLink Data Access Drivers for Progress is central to you exploiting the deliberate simplicity of our product architecture. A failure to grasp these concepts will certainly make the last sentence an absolute contradiction in terms. http://docs.openlinksw.com/mt/appserverarchitect.html Application Server Architecture http://docs.openlinksw.com/mt/appserverarchitect.html Wed, 09 Apr 2008 14:37:12 GMT