******************************************************** (c) Copyright 1999 International Business Machines Corp. All rights reserved. ******************************************************** ReadMe.txt ******************************************************** Welcome to IBM WebSphere (TM) Studio 3.0 Entry Edition This Entry Edition allows you to publish 250 files before you must close Studio and restart it. This ReadMe file contains information about installing and using the IBM WebSphere Studio 3.0. This information corrects and supplements the information in the product help and documentation. It includes the following topics: >> LICENSE INFORMATION >> PRODUCT CONTENTS >> STUDIO HARDWARE/SOFTWARE REQUIREMENTS >> STUDIO INSTALLATION INSTRUCTIONS >> STUDIO UNINSTALL INSTRUCTIONS >> STARTING WEBSPHERE STUDIO >> KNOWN RESTRICTIONS AND CONSIDERATIONS >> JAVA DEVELOPMENT KIT >> FOR MORE INFORMATION >> TRADEMARKS >> THIRD PARTY LICENSE TERMS AND CONDITIONS >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >> LICENSE INFORMATION >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Please read the license information before using this product. You can find the license information in the directory where you install the product. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >> PRODUCT CONTENTS >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> WebSphere Studio 3.0 has all these important features: - Graphical display of the links between files in a project - Automatic update of links whenever files change or move - Registration of your favorite tools for editing - A built-in Page Designer to visually create and edit HTML and JSP files - Wizards that jump-start the creation of dynamic pages using databases and JavaBeans - Staging and publishing to different (and to multiple) servers - Integration with popular source control management software - Companion tools that round out your web development toolkit: - Applet Designer, a visual authoring tool for building Java applets - WebArt Designer, for creating masthead images, buttons, and other graphics for your pages - AnimatedGif Designer, for assembling GIF animations >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >> STUDIO HARDWARE/SOFTWARE REQUIREMENTS >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -- A minimum 180 MB of disk space is required for WebSphere Studio 3.0 -- Microsoft Windows NT version 4.0 with Service Pack 3, Microsoft Windows 95, or Microsoft Windows 98 -- Microsoft Internet Explorer, version 4.0 or higher >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >> STUDIO INSTALLATION INSTRUCTIONS >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> To install IBM WebSphere Studio 3.0: 1) Download the Studio installation file from the web site and unzip the file into a local directory. 2) Run the "setup.exe" program. 3) Follow the instructions in the InstallShield windows. >>If you have installed a prior version of WebSphere Studio, it is recommended that you uninstall it before installing Studio. Be sure to copy any existing Studio files that you want to preserve to another location to avoid having them overwritten. >>If you are going to publish the files generated by the Studio Database wizard to WebSphere Application Server 2.02 or to versions running on OS/390 and AS/400, you will have to copy Studio JAR files to the Application Server directories. These are required by the Studio 3.0 database access servlets which use Dates, Times, or Timestamps as query parameters. It will not impact existing servlets. If you do not copy these files and attempt to use database access servlets that have these query parameters, you get com.ibm.db.DataException. >>>For WebSphere Application Server 2.02: Copy webtlsrn.jar and databeans.jar from WebSphere\Studio\lib\AppServerV2\ to WebSphere\AppServer\lib\. >>>For AS/400: Copy webtlsrn.jar and databeans.jar from WebSphere\Studio\lib\AppServerV2\ to WebSphere\AppServer\lib\. >>>For OS/390: Copy webtlsrn.jar, databeans.jar, and xml4j.jar from WebSphere\Studio\lib\AppServerV2\ to WebSphere\AppServer\lib\. >>Prior to publishing and running your servlets, it is very important that you review the "Tell me about... Server configuration" in the online Studio Guide. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >> STARTING IBM WEBSPHERE STUDIO 3.0 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -- To start IBM WebSphere Studio: Look for IBM WebSphere on the Start Programs menu, and select Studio 3.0. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >> STUDIO UNINSTALL INSTRUCTIONS >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -- To uninstall IBM WebSphere Studio: Use the Add/Remove Programs control panel. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> KNOWN RESTRICTIONS AND CONSIDERATIONS FOR THIS RELEASE >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >> FOR MIGRATION >> Because there have been changes to the project format, you will not be able to use any projects you created with Studio 3.0 Beta releases. If you want to migrate Beta projects, you can: - Publish the project to a Web server and import it into Studio - Or, recreate the project in Studio by copying or inserting the existing folders and files from your file system into a new project. In either case, you should delete any .wao and .nbl files created with any Studio Beta. >>>>>>>>>>>>>>>>>>>> >> FOR DBCS VERSIONS >> Using Studio in languages with double-bye character sets (DBCS) When publishing to servers that use EBCDIC, in order to convert DBCS characters from PC code to EBCDIC code: - First, publish the files using FTP in binary mode. - Then, use the tools on the host system (S/390 and AS/400) to convert the files to DBCS EBCDIC. You can change your FTP publishing options on the Advanced tab of the Publishing options dialog. From the main menu, click Tools => Publishing options. >> When you search DB2 graphic data in a DBCS version of DB2, you need to use the DBCS wild card. However, in order to keep compatibility for the other database products, the SQL statements created by the Studio SQL wizard use the SBCS wild card. Therefore, to access DB2 graphic data in a DBCS version of DB2, you must modify these SQL statements manually. >>>>>>>>>>>>>>>>>>>>>>>>>> >> FOR THE DATABASE WIZARD >> If you check the "Allow Update" box on the Web Pages page of the Database wizard, you must ensure that one row, and only one row, is returned from the query. Additionally, you should select a primary key field to display on the query's output page. This primary key will become input to the subsequent update operation, ensuring that the update finds a single row to be updated. If you do not want this field to be visible to your users, you can modify the generated JSP and make this a hidden field. >>>>>>>>>>>>>>>> >> FOR COMPILING >> If your CLASSPATH environment variable has quotes in it, compiling Java files from within Studio will not work. >>>>>>>>>>>>>>>>>>>>>>>>>>>> >> FOR LOTUS VERSION CONTROL >> If you install Lotus Notes after you install Studio and you want to use Web Content Library for version control, you need to update your registry so it knows where to find sccdll.dll. 1. In Studio's DominoWCL directory, edit LCMRegistry.reg to ensure that it has the correct path for the sccdll.dll file. (sccdll.dll is in Studio's \bin directory) 2. At a Windows command prompt, enter: regedit LCMRegistry.reg. 3. Copy wcl50.ntf from Studio's DominoWCL directory to the Lotus Notes notes\data directory. 4. Copy icon.bin from Studio's DominoWCL directory to Studio's \bin directory. >> If you are using Lotus version control with Notes 4.0 or 5.0: After you have added a project or folder to version control, you need to start Notes and perform some initial configuration. This process includes using the Workflow tab to define the approvers names. Note that you must "save" before exiting Workflow, even if you have no approvers defined. After saving, you can continue checking files in and out of Notes version control. >> If you are using Lotus version control with Notes 5.0: When you are presented with the "Project Path for New Database" dialog that allows you to enter a name for the notes database, verify that you are using the wcl50.ntf. template. If the template name that is displayed in the "Template" drop-down list is NOT wcl50.ntf, click the drop-down arrow to select this correct template from the list. >> Files that are added to Lotus version control are not permitted to contain any DBCS characters. >>>>>>>>>>>>>>>>>>>>>>> >>FOR ORACLE DATABASES >> There is a known problem with the Oracle 8.0.4 ODBC driver when running the database server on Windows NT (see Oracle ODBC README File). Do not use the Oracle ODBC Driver for database servlets that will run in this environment. Instead, use the Oracle Thin driver. >> When developing servlets to access Oracle databases using the WebSphere Studio SQL Wizard, unless you're able to use the Oracle ODBC driver via the Jdbc-Odbc bridge, you must use Oracle's JDBC-Thin/100% Java for JDK1.1.x driver. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >> FOR MICROSOFT ACCESS DATABASES >> There are known problems which can cause the WebSphere Application Server to crash when running Database wizard servlets that query Microsoft Access databases. When using Microsoft Access, you should upgrade the JDK on your WebSphere Application server machine to JDK 1.1.7B. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >> JAVA DEVELOPMENT KIT >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> A Java Development Kit version 1.1.7 is included with WebSphere Studio in order to compile servlets to run on the WebSphere Application Server. This JDK will be removed when you uninstall the WebSphere Studio. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >> FOR MORE INFORMATION >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Find the most up-to-date information about the Studio, Frequently Asked Questions (FAQs), and White Papers at: http://www.ibm.com/software/websphere/studio Be sure to visit our newsgroup at: news://news.software.ibm.com/ibm.software.websphere.studio >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >> TRADEMARKS AND NOTICES >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> IBM, WebSphere is a trademark of IBM Corporation. Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others. ***************************************************** Portions copyright (c) Blue Sky Software Corporation. All rights reserved. Portions copyright (c) Microsoft Corporation. All rights reserved. ***************************************************** >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >> THIRD PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided below. This software is based in part on the work of the Independent JPEG Group. In addition, this software contains software code developed by Guy Eric Schalnat, Group42, Inc., Andreas Dilger, Glenn Randers-Pehrson, Jean-loup Gailly and Mark Adler.