RAINMAKER GATEWAY(tm) 1.0 This Readme file contains information that is not included in printed or electronic documentation for Rainmaker Gateway, version 1.0. This file contains the following topics: * Extracting Installation Files and Documents * System Requirements and Installation Instructions * Advisory Notes * Other Documentation * About OnLink(tm) Technologies * Contact Information * Copyright -------------------------------------------------------------------- EXTRACTING INSTALLATION FILES AND DOCUMENTS -------------------------------------------------------------------- If you downloaded the compressed installation distribution from your OnLink representative, you must extract the Rainmaker Gateway files to a temporary directory before beginning installation. These files and the temporary directory can be deleted after installation. To extract the installation files: - For Windows NT(tm): In Windows Explorer, double-click RainmakerGateway10Setup.exe, choose the temporary directory to which the files will be extracted, and click Finish to extract the files to the specified location. - For UNIX(tm): Create a temporary directory, copy rainmakergateway10.tar.Z into the temporary directory, and run the following command (the last character is a dash): uncompress < rainmakergateway10.tar.Z | tar xvf - -------------------------------------------------------------------- SYSTEM REQUIREMENTS AND INSTALLATION INSTRUCTIONS -------------------------------------------------------------------- For Rainmaker Gateway system requirements and installation instructions, refer to your Rainmaker Gateway 1.0 Reference Manual (rg10refman.pdf). This Portable Document Format (PDF) file is located in the directory named "docs" in your Rainmaker Gateway 1.0 distribution (either the root directory of the CDROM or the directory into which the Gateway files were extracted). NOTE: You must have Adobe(r) Acrobat(r) Reader installed on your system in order to read this file. If you do not have this free Adobe application, visit the Adobe web site (www.adobe.com) and download the setup program for your operating system. For your convenience, the Adobe PDF readers for Windows NT and UNIX are included with the Gateway distribution. These applications are provided as a service to our customers, and their inclusion does not imply a warranty, support, or endorsement of the applications. -------------------------------------------------------------------- ADVISORY NOTES -------------------------------------------------------------------- This section contains the advisories known at the time of this release. ----- Internal Error After Exporting from Rainmaker Composer(tm) Reference ID: 537 Following an export from Rainmaker Composer, you must run the DIS Administrator to update the Interface tables. If you do not run the DIS Administrator after each Composer export, the message "Internal Error" may appear the next time you export from the DIS. NOTE: This is not an internal error and the message should read as "Missing Composer Table." The error message will be corrected in a future release of Rainmaker Gateway. To avoid this message, run the DIS Administrator after each time you export from Composer. ----- MATCH ROWSET Policy Failure Reference ID: 610 During an UPDATE job, the Rainmaker Gateway DIS may detect a MATCH ROWSET policy failure when the following two conditions occur: * The parameter MATCH ROWSET is set to YES in the job definition. NOTE: If the MATCH ROWSET parameter is not explicitly defined in the job definition, it is set to YES by default. * A Rainmaker Composer table associated with an interface table contains duplicate key values. Duplicate key values are detected when all the values for the key columns in a Composer table are the same in one or more rows. The following is an example of a MATCH ROWSET policy failure error message: Updating: Gateway.p1589.MAIN.DATA [Mon 13 Mar 2000 10:48:48.448] MATCH ROWSET Policy Failure: RowSet-Gateway.p1589.MAIN.DATA in Rows-5,7,8,9,10,11,29,30,31 If the DIS triggers a MATCH ROWSET error, check that the key values for each of the rows that caused the error are unique by comparing them to all other rows. Be sure to check all rows, and not just the rows explicitly listed in the error set. Wherever possible, change the key values to eliminate the duplication. If you find duplicate values and are unable to modify the Composer project, set the parameter MATCH ROWSET=NO in the job definition to have Gateway skip this check. ----- Slow Exports from Rainmaker Composer Reference ID: 643 If you use the Rainmaker Composer "Export Model Set to Repository" command, you may notice that the export operation executes significantly faster the first time you export a model set than all subsequent times. This is a consequence of the way Composer executes its export operation. Each time you export a model set from Composer to the Rainmaker Gateway Repository, Composer inspects the Repository to determine if an identically named model set already exists. If the model set already exists, Composer deletes it before exporting the Composer model set to the Repository. Gateway provides a utility program to delete a model set from the Repository before you export the identically named model set from Composer. Because the utility program deletes the model set significantly faster than the Composer export operation does, you can speed up export operations by using the utility program to delete the existing Repository model set before you select the "Export Model Set to Repository" command. The utility script is named "rmproj.oitcl" and is located in the composer/tcl subdirectory of your Gateway application directory. The script is called as an argument when launching the Tcl shell, as shown in the example below (where is your Gateway installation directory). IMPORTANT: You must close the Composer project file before running the utility script. If Composer is left open, there may be locks on the project files that would prevent the utility from running successfully. \bin\onlitclsh31 \composer\tcl\rmproj.oitcl -C [conn_string] -l [filename] -L [directory] -v [level] modelset1 modelset2 ... NOTE: On a UNIX system, use slashes (/) instead of backslashes (\). Command line arguments for the rmproj.oitcl script are: -C [conn_string] Sets the connection string for the database connection. Format of the connection string is "OCI:/@", with a default value of "OCI:onlink/onlink@DataBroker". -l [filename] Sets the name of the log file. The extension ".log" will be appended to the filename specified. Default value is "rmproj". -L [directory] Sets the directory to which the log file is saved. Default value is "c:\temp" (Windows NT) or "/tmp" (UNIX). -v [level] Sets the log level. Accepted values are (in increasing order of detail reported): Error, Warning, Status, Info, Verbose, Debug, and Test. Default value is "Status". For example, on an NT system, to delete model sets MS_1 and MS_2 from the Repository using user name "sgladman", password "eccentric", and service name "OLGateway", use the following command (typed on one line, with spaces between the arguments): c:\onlink\gateway1_0\bin\onlitclsh31 c:\onlink\gateway1_0\composer\tcl\rmproj.oitcl -C OCI:sgladman/eccentric@OLGateway MS_1 MS_2 ----- DIS UPDATE Fails with Large Projects Reference ID: (none) The Rainmaker Gateway DIS UPDATE operation may fail if the database rollback segment size is not large enough to accommodate the project. When the DIS executes an UPDATE job, it starts a database transaction so it can roll back (revert) any changes made if the job fails or is cancelled before finishing. Because this transaction is kept open for a long period of time, and potentially large amounts of data are modified, the database may run out of space in the rollback segments tablespace. If this happens, the UPDATE operation will fail. Check the log file for error messages to confirm that this is the case. If this happens, contact your database administrator to increase the size of the database rollback segments tablespace. A good rule of thumb is to set the rollback segment size to at least the size of the Rainmaker Composer project. This is a known limitation of Rainmaker Gateway and it will be addressed in a future release. -------------------------------------------------------------------- OTHER DOCUMENTATION -------------------------------------------------------------------- In addition to the information in this Readme file, you should also refer to the Rainmaker Gateway 1.0 Reference Manual. This Portable Document Format (PDF) file (rg10refman.pdf) is located in the directory named "docs" in your Rainmaker Gateway 1.0 distribution (either the root directory of the CDROM or the directory into which the Gateway files were extracted), or after installation in your Gateway application directory named "docs". -------------------------------------------------------------------- ABOUT ONLINK TECHNOLOGIES -------------------------------------------------------------------- OnLink is the leading provider of the next generation of business-to-business e-commerce applications designed to enable the customer's buying decision. The OnLink mission is to improve the online buying experience by taking a new perspective: the buyer's. Our Web applications take the buyer's point of view by delivering instant response, high interactivity, and complete information. Built on our innovative Customer Decision Architecture, the OnLink Commerce Suite humanizes the online decision making process by guiding and advising the customer. Needs are understood and captured, tradeoffs and "what-ifs" are easily explored, and the ideal solution is recommended. The OnLink Commerce Suite brings a new perspective to online buying with an integrated complement of software applications that address e-commerce from the customer's point of view. Why OnLink? Because customers decide. They decide where, when, and how they want to buy products or services. And they buy from the company that best satisfies their needs. -------------------------------------------------------------------- CONTACT INFORMATION -------------------------------------------------------------------- You can contact OnLink by mail, telephone, facsimile, or e-mail. OnLink Corporate Headquarters 700 Bay Road, Suite 200 Redwood City, CA 94063 Phone: (650) 298-3800 Fax: (650) 298-3809 E-mail: info@onlink.com for brochures and other collateral sales@onlink.com for product sales and demonstrations support@onlink.com for technical support You can also visit our web site for contact and product information: www.onlink.com -------------------------------------------------------------------- COPYRIGHT -------------------------------------------------------------------- (c) 2000 On-Link Technologies, Inc. All rights reserved. Information in this document is subject to change without notice and does not represent a commitment on the part of OnLink Technologies, Inc. The software described in this document is furnished under a license agreement or nondisclosure agreement. This software may be used or copied only in accordance with the terms of those agreements. No part of these materials may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form or by any means (electronic, mechanical, or otherwise) without the written permission of OnLink Technologies, Inc. Rainmaker Composer, Rainmaker Gateway, and Rainmaker Sales are trademarks of OnLink Technologies, Inc. in the USA and other countries. All other trademarks, registered trademarks, trade names, or company names referred to herein are used for identification only and are the property of their respective owners. OnLink Technologies, Inc. makes no claim to these marks or names. olti000310sg