IBM WebSphere Development Studio Client, Version 7.0.0.2 Readme

© Copyright International Business Machines Corporation 2000, 2007. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

1.0 About this release
   1.1 New in this release
2.0 Installation information
   2.1 Hardware requirements
   2.2 Software requirements
   2.3 Other requirements
   2.4 Installation instructions
      2.4.1 Installing WebSphere Development Studio Client, Version 7.0.0.2 as an update
      2.4.2 Downloading the fix pack for local installations   
   2.5 Uninstalling the fix pack
3.0 Fixes contained in this release
   3.1 XML tools
   3.2 Crystal reports
   3.3 JavaServer Faces and ODC tools
   3.4 Web services
   3.5 J2EE tools
   3.6 Portal and portlet tools
   3.7 Data tools
   3.8 EJB tools
   3.9 User assistance
   3.10 Web tools
   3.11 Modeling framework
   3.12 Java domain modeling
   3.13 WSDL/XSD domain modeling
   3.14 UML model platform
   3.15 EJB deployment tools
   3.16 Server tools
   3.17 WebFacing tool
4.0 Known limitations, problems, and workarounds
   4.1 Data tooling documentation contains a reference to unsupported functionality
   4.2 Internal server error "SAXException: Premature end of file" occurs when invoking an Axis Web service on WebSphere Application Server
   4.3 J2C "Same Input and Output" Sample link does not work on the Linux operating system
   4.4 Converting static Web project with Web site navigation enabled to a dynamic Web project fails with an exception
   4.5 Publishing an EJB with multiple source directories fails with an error
   4.6 The rollback feature is not supported in Installation Manager, Version 1.0.0.3   
   4.7 Internet Explorer cannot handle AJAX requests on pages with character sets of "Windows-31J"
   4.8 IMS TM Resource Adapter information
   4.9 Relational SDO wizard may treat Oracle Numerics as Short data types instead of Integers
   4.10 In data tools, you may get the "session manager not available" error message
   4.11 Problems profiling on a server
   4.12 Running a Junit test on the Integrated Agent Controller fails if the test is first run on a stand-alone Agent Controller    
5.0 IBM WebSphere Software Support
6.0 Notices and trademarks

1.0 About this release

This fix pack contains new features, enhancements, and fixes to the version 7.0 and version 7.0.0.2 releases of IBM^® WebSphere^® Development Studio Client for iSeries.

For an updated version of this readme file, see the file available online at: http://download.boulder.ibm.com/ibmdl/pub/software/awdtools/wdsc/v7/7002/documents/readme/readme.html

In addition, see the release notes for version 7.0 of this product to learn about its new features and any limitations or problems known at the time of its release. The release notes for version 7.0 are available at: http://download.boulder.ibm.com/ibmdl/pub/software/awdtools/wdsc/v7/70/documents/readme/readme.html

1.1 New in this release

This release of WebSphere Development Studio Client for iSeries contains the following new features and enhancements:

• Platform, operating system, and browser support enhancements:
  • Eclipse 3.2.2 (for compatibility with previous releases and known issues, see the Eclipse 3.2.2 Project Release Notes).
  • Mozilla Firefox 2.0.
  • IBM Runtime Environment for Windows^®, Java^™ 2 Technology Edition, Version 5.0 service release 4.
  • IBM Runtime Environment for Linux^®, Java 2 Technology Edition, Version 5.0 service release 4.
  • Microsoft^® Internet Explorer 7.0.
  • WebSphere Portal Server, Version 6.0.1 is compatible as a target runtime. (The user interface will continue to display WebSphere Portal v6.0 as the type of runtime.)
  
  
• Transformation authoring:
  • Pathmap URI support: The resource selection windows in the Transformation Mapping editor and the Auxiliary Model page of the Transformation Configuration editor now enable you to specify a URI that is a pathmap; for example "pathmap://UML_LIBRARIES/UMLPrimitiveTypes.library.uml".
  • Registered UML profile browsing: You can browse and select registered UML profiles from the resource selection windows in the Transformation Mapping editor.
  • Automatic import of referenced models: Referenced models are now automatically imported when submaps that reference elements or features in them are created by using the "New" submap feature.
  • Automatic resolution of simple cross-model references: Previously, if a deferred reference could not be resolved because there was no corresponding object created for it, then the transformation failed and an error message was displayed. Now, the product checks for the following conditions and, if both conditions are met, then the original object (for example, an integer) is used to resolve the reference:
    • The reference is to an object in a different model from the main source that is being transformed.
    • If the type of the original reference is compatible with the new reference in the transformed model.
  • Disabling creation of mapping models in non mapping projects: The New Transformation Mapping wizard displays an error message and disables the Finish button if you attempt to create a mapping model in a non mapping project, which is a project without the proper project nature.
•  J2EE Connector (J2C) tools, updates, and enhancements for IMS^™ TM resource adapters:
  • Alternate Client ID: The alternate client ID enhancement allows Java client applications to retrieve messages from any asynchronous output queue (OTMA Tpipe) by specifying an alternate client ID on shareable persistent socket connections. Prior to this enhancement, a client could retrieve asynchronous messages from a Tpipe in two ways. The first approach was to use dedicated persistent socket connections. However, the use of dedicated persistent sockets could cause duplicate client ID problems in a Sysplex distributor environment. The second approach was to use shareable persistent socket connections. This approach was too limiting because the original interaction that led to the generation of asynchronous output and the retrieval of that asynchronous output would have to occur on the same socket (usually within the same application). With this enhancement, both of these limitations are eliminated.
  • SSL Null Encryption: The SSL null encryption enhancement allows you to specify "ENULL" encryption for a connection factory. This enables you to use the authentication capability provided for an SSL socket connection without incurring the overhead of encrypting each message that flows over that connection. Prior to this enhancement, you could only specify that the connections created by a connection factory use either "STRONG" or "WEAK" encryption, which meant that strong or weak data encryption would be used on the connections. You will find this new feature useful when you want to prevent access to a server by internal users with malicious intent, but you are not concerned about encrypting the data that flows to and from that server because the data flow takes place behind your firewall.

    For more information on these new features, see the IMS TM Resource Adapter User's Guide and Reference, available from the IBM Information Management Software for z/OS^® Solutions Information Center.

• WSDL domain modeling enhancements:
  • Creation of XML Schema Definition (XSD) elements within a Web Service Definition Language (WSDL) file, including XSD simple and complex types
  • Editing of XSD elements, such as changing XSD types and adding XSD elements to existing XSD complex types

2.0 Installation information

This section describes the installation requirements and specific installation instructions for this fix pack.

For information about installing WebSphere Development Studio Client for iSeries, Version 7.0, including installation prerequisites, see the Installation Guide online at http://download.boulder.ibm.com/ibmdl/pub/software/awdtools/wdsc/v7/70/documents/install_instruction/install.html.

2.1 Hardware requirements

There are no additional processor or memory requirements for installing this fix pack; however, there might be additional disk space requirements depending on whether you are installing the fix pack at the same time that you install WebSphere Development Studio Client for iSeries, Version 7.0 or if you are installing the fix pack as an update:

• If you are installing the fix pack at the same time that you install WebSphere Development Studio Client, Version 7.0, then the disk space requirements are essentially the same as for version 7.0.
• If you are installing the fix pack as an update, however, you might need up to an additional 2 GB of disk space. Your actual disk space requirements depend on the features that you selected when you installed version 7.0 or 7.0.0.1 of the product.

If you choose to download the update as a compressed file for local installation, you require approximately 2 GB to store and extract the compressed file.

2.2 Software requirements

This section describes the additional software requirements for installing WebSphere Development Studio Client for iSeries, Version 7.0.0.2; to see the requirements for installing WebSphere Development Studio Client 7.0, see the Installation Guide.

Before you can install this fix pack, you must install IBM Installation Manager, Version 1.0.0.3. In Installation Manager, if you have not disabled the default setting to search the linked repositories during installation and update, IBM Installation Manager, Version 1.0.0.3 is automatically installed on your computer when you attempt to update or install packages using an earlier version of Installation Manager.

For additional information about Installation Manager, Version 1.0.0.3, refer to http://download.boulder.ibm.com/ibmdl/pub/software/rationalsdp/v7/im/1003/docs/readme/readme.html.

If you are extending an Eclipse IDE, then before you install this fix pack you must install version 3.2.2 or higher of the Eclipse IDE and one of the following Java runtime environments:

• For Windows: IBM 32-bit Runtime Environment for Windows, Java 2 Technology Edition, Version 5.0 service release 4; Sun Java 2 Platform Standard Edition Runtime Environment Version 5.0 Update 11 for Microsoft Windows
• For Linux: IBM 32-bit Runtime Environment for Linux on Intel® architecture, Java 2 Technology Edition, Version 5.0 service release 4; Sun Java 2 Platform Standard Edition Runtime Environment Version 5.0 Update 11 for Linux x86 (not supported for SUSE Linux Enterprise Server [SLES] Version 9)

To update an existing Eclipse IDE to version 3.2.2 or later, if you have internet access, complete the following steps:

1. Start WebSphere Development Studio Client.
2. Click Help > Software Updates > Manage Configuration.
3. In the Manage Configuration dialog box, expand the folder that contains the current Eclipse IDE and click the entry starting with Eclipse Project SDK 3.2.1.r321.
4. In the right-hand pane, click Scan for updates.
5. In the Update Site Mirrors window, select an update site mirror and click OK.
6. In the Updates wizard, on the Search results page, select an Eclipse update site and click Next.
7. Follow the on-screen instructions in the Updates wizard to install the update.

   Note: When you are prompted to verify the update of the features that have not been digitally signed, click Install All.
    

8. After the update completes, in the Install/Update window, click Yes to restart the product.

Now your Eclipse IDE meets the prerequisite version for installing this fix pack.

2.3 Other requirements

Internet access is usually required because, by default, the update is located and installed by Installation Manager directly from the IBM update repository for WebSphere Development Studio Client, Version 7.0.

Important: When WebSphere Development Studio Client is installed, the location of its update repository is automatically embedded in Installation Manager. For Installation Manager to search the default update repository, the preference Search the linked repositories during installation and updates on the Repositories preference page must be selected. This preference is selected by default.

To install the fix pack from a different repository location (for example, if the fix pack is available on a shared drive or HTTP or HTTPS server), you must add the repository location in Installation Manager. To add a repository location:

1. Start Installation Manager
2. On the Start page of Installation Manager, click File > Preferences, and then click Repositories. The Repositories page opens.
3. On the Repositories page, click Add Repository.
4. In the Add repository window, enter the URL of the repository location or browse to it and enter a file path, and then click OK.
5. Click OK to close the Preference page.

2.4 Installation instructions

The following are the two common ways to install this update:

• If IBM WebSphere Development Studio Client for iSeries, Version 7.0 or 7.0.0.1 is already installed on your system, then you can install this update by using the Update Packages wizard in IBM Installation Manager. For general instructions on installing an update, refer to the section "Updating WebSphere Development Studio Client" in the Installation Guide. For detailed instructions, see section 2.4.1 Installing WebSphere Development Studio Client, Version 7.0.0.2 as an update.
• If you are installing IBM WebSphere Development Studio Client for iSeries, Version 7.0 for the first time or if you are installing an additional instance of it, then you can install this update at the same time that you install IBM WebSphere Development Studio Client for iSeries, Version 7.0 by clicking Check for updates on the Install page of the Installing Packages wizard in IBM Installation Manager. For general instructions on installing an update, refer to the section "Installing IBM WebSphere Development Studio Client using the IBM Installation Manager graphical interface" in the Installation Guide.

By default, the update is installed directly from the IBM update repository; however, it is also available for download. For details, see the specific installation instructions noted below for WebSphere Development Studio Client for iSeries, Version 7.0.0.2.

2.4.1 Installing WebSphere Development Studio Client for iSeries, Version 7.0.0.2 as an update

Install the fix pack with the same user account that installed the product.

Restrictions:

• WebSphere Development Studio Client for iSeries, Version 7.0 or 7.0.0.1 must be installed.
• The product cannot be open when you install this fix pack. Also, ensure that all browsers and other applications opened by WebSphere Development Studio Client are closed.

To find and install WebSphere Development Studio Client for iSeries, Version 7.0.0.2 as an update:

1. Start IBM Installation Manager.
2. On the Start page of Installation Manager, click the Update Packages button.
3. If a new version of Installation Manager is found, you are prompted to confirm that you want to install it before you can continue. Click OK to proceed. Installation Manager automatically installs the new version, stops, restarts, and resumes.
4. In the Update packages wizard, select the Installed Location for WebSphere Development Studio Client and click Next. Installation Manager searches for updates in the WebSphere Development Studio Client repository on the Web, as well as any repository locations that you entered. A progress indicator shows the search is taking place.
5. By default, recommended updates are displayed and selected on the Update Packages page. Ensure that you select Version 7.0.0.2 for WebSphere Development Studio Client, then click Next.
6. On the Licenses page, read the license agreements for the update. On the left side of the License page; click each item to display the license agreement text.
   1. If you agree to the terms for all of the license agreements, click I accept the terms of the license agreements
   2. Click Next to continue.
   3. On the Summary page, review the information displayed, and then click Update. A progress indicator shows the percentage of the installation completed.
7. When the update process completes, a message that confirms the success of the process is displayed near the top of the page. Click View log file to open the log file for the current session in a new window. You must close the Installation Log window to continue.

You can download a compressed file containing the WebSphere Development Studio Client for iSeries, Version 7.0.0.2 fix pack; the files that you extract from the compressed file form a repository for the fix pack. You can install the fix pack from the repository on your own computer, or you can copy the repository to a shared drive or an HTTP or HTTPS server.

To download and install the fix pack, complete the following steps:

1. Download the fix pack.
2. Extract the compressed file in an appropriate directory. For example, extract the file to C:\temp.
3. Add the fix pack repository location in IBM Installation Manager:
   1. Start IBM Installation Manager.
   2. On the Start page of Installation Manager, click File > Preferences, and then click Repositories. The Repositories page opens.
   3. On the Repositories page, click Add Repository.
   4. On the Add repository window, browse to and enter the file path to the wdsc\updates directory. For example, enter C:\temp\wdsc\updates and then click OK.
   5. Click OK to close the Preference page.
4. Install the fix pack as described previously in this document.

   Note: During the process of updating from a local repository, Installation Manager might prompt you for the location of the repository for WebSphere Development Studio Client for iSeries, Version 7.0. If you installed the product from CDs or other media, they must be available when you use the update feature.

2.5 Uninstalling the fix pack

To revert to an earlier version of WebSphere Development Studio Client you must uninstall the entire package and reinstall the appropriate version. A single uninstallation procedure removes the version 7.0 package and the upgraded version 7.0.0.2 package. After uninstalling, you can reinstall the version 7.0 package.

Before you uninstall WebSphere Development Studio Client for iSeries, Version 7.0.0.2, perform the following steps:

1. Log in with a user account that has the same privileges as the account that was used to install the packages to be uninstalled.
2. Close WebSphere Development Studio Client for iSeries, Version 7.0.0.2 and any other applications that you installed with IBM Installation Manager.
3. If any applications opened by WebSphere Development Studio Client are still open, such as a browser or IBM WebSphere Application Server, then close them.

To uninstall WebSphere Development Studio Client for iSeries, Version 7.0.0.2:

1. Start IBM Installation Manager.
2. On the Start page, click Uninstall Packages.
3. Follow the instructions in the wizard.

For additional instructions on uninstalling WebSphere Development Studio Client, see the Installation Guide or see the Installation Manager online help.

3.0 Fixes contained in this release

The following APARs are fixed in this release:

For all WebSphere Development Studio Client APARs refer to: http://www-1.ibm.com/support/search.wss?rs=3239&lang=en&loc=en_US&r=10&cs=utf-8&rankfile=0&cc=&spc=&stc=&apar=include&q1=5722WDS03+OR+5722WDS04+OR+5722WDS05+OR+5722WDS06+OR+5722WDS07+OR+5722WDS08+OR+5722WDS09&q2=7.0.0.2&Go.x=0&Go.y=0&sort=desc&tc=SSZND2&dc=DB550+D100&dtm

3.1 XML tools

• (PK08271) Bean generator fails for plug-in projects.
• (PK39390) The WSDL validator does not tolerate JAX-WS 2.0 embedded bindings.
• (PK41387) DOM to model reconciliation issue with xmlns.

3.2 Crystal reports

• (PK33424) Runtime issue with Oracle 10g driver in Crystal Reports XI.
• (PK34073) The wrong code is generated for parameter fields property for Report Page Viewer of Crystal Report.

3.3 JavaServer Faces and ODC tools

• (PK30284) A null point exception is thrown if a faces managed bean contains an ArrayList in client data.
• (PK34549) The value of input rich text is not empty string when editor is empty.
• (PK36302) After canceling the edit dialog box, selecting components loses state information.
• (PK36566) HashMap in com.ibm.faces.util.JavaScriptUtil cannot be synchronized.
• (PK37661) The size property of the file upload component does not have an effect.
• (PK38502) Using ODC tree, dataGrid and graph component bound to client data fails if configured in multiple portlets.
• (PK38763) hx:inputHelperSetFocus fails to render if the target attributes value refers to an HTML tag's ID.
• (PK39128) A JSF tree component collapses every time it is reloaded.
• (PK39783) Ajax code works in Firefox, but not in Internet Explorer.
• (PK39803) There are no snippets to bind the tree component for example with an input box.
• (PK40319) hxclient library fails to initialize if page contains an iframe that references an "external site" and the library needs taborder.
• (PK41085) Running jsf:ajax pages on internet explorer with https causes the "page contains non secure items..." error.
• (PK41985) When requestLink's action attribute is set to a String and client-side state saving is used, the state of the UIREquest component can not be restored.

3.4 Web services

• (JR25649) The preference to use generate WebSphere Application Server version 5.1.0 Web service emitter code using the version 5.1.1 runtime was removed in version 7.0 of the product. However, it is still needed for customers that want to develop Web service applications for WebSphere Application Server version 5.1 on z/OS as it is currently using at the version 5.1.0 release. Therefore, the Web service emitters need to generate code for WebSphere Application Server version 5.1.0 and not version 5.1.1.
• (JR25242) Excessive amount of JNDI lookups occur when using the generator Web service Proxy class resulting in performance degradation.
• (JR25396) WSDL files cannot import XSD files using a relative "../" directory structure as it causes deployment and runtime problems as the imported XSD files will not be found by the WebSphere Application Server runtime.
• (PK34575) Web Services wizard had an internal error: IWAB02234E.
• (PK35951) WSDL files are misplaced in Web Services wizard.
• (PK35624) If a WSDL file contains an xsd:include statement then it will not be parsed and processed correctly and result in a NullPointerException being displayed in the console window used to launch the Web service command-line scripts.
  

3.5 J2EE tools

• (PK32061/PK38615) Project migration from v6.0 fails.
• (PK37579) Reordering dependent JARs in J2EE module dependencies does not function properly.
• (PK37884) A reference to an EJB not in the workspace cannot be created.
• (PK38785) System hangs during JSR-109 indexing task.

3.6 Portal and portlet tools

• (PK39190) An NPE error occurs when enabling portlet to send data.

3.7 Data tools

• (PK39470) SQL model migration rejected the DATE type and replaced the DATE type with CHAR(20).

3.8 EJB tools

• (PK40172) The EJB Mediator does not allow more than one query for the same schema type.

3.9 User assistance

• (PK35538) Data is missing in the Help page of "Creating a new EJB composer".
• (PK38098) XSD-to-Java bean generation documentation is not accurate.

3.10 Web tools

• (PK12748) JSF components are shown as question marks (?) in the Turkish locale.

3.11 Modeling framework

• (PK19773) Rectilinear generalization between associations does not redraw correctly when classes are moved.
• (PK20573) Copying/Pasting elements from a composite structure diagram to a Microsoft Word document does not work as expected.
• (PK25885) Copying and pasting a diagram into Microsoft Word 2003 truncates the image.
• (PK26442) The ability to scroll across diagrams is inconsistent.
• (PK28072) An IView facade could not be found for the given notational view.
• (PK28764) Renaming a folder containing a model from the Navigator view might break references.
• (PK35774) Closing a very large model takes a long time.
• (PK36064) Port text box resizes to a random size.
• (PK36311) Printing font is distorted, in low-resolution, and does not shrink well.
• (PK38705) The system may hang on opening search results.
• (PK39287) Printing a diagram Fit to Page prints an illegible diagram.

3.12 Java domain modeling

• (PK11411) Generating Javadoc HTML documentation with diagram images will generate documentation for empty packages.
• (PK16389) Renaming a method in source file does not propagate changes to the corresponding sequence diagram message.

3.13 WSDL/XSD domain modeling

• (PK38452) Reference to existing elements should not persist URI Authority portion.

3.14 UML model platform

• (PK06655) Interaction occurrence is not functional in stand-alone sequence diagrams.
• (PK14091) Unexpected results occur when deleting an association class from a diagram and dropping it again in the same diagram.
• (PK25019) Moving lifelines between existing ones requires movements of excessive precision.

3.15 EJB deployment tools

• (JR25257) An EJBQL finder method using a local EJB interface as input parameter results in an 'Unknown EJB or ASN name' validation error.
• (JR25368) If an EJB project has been configured to use a source folder that is a linked to a directory in a non-source folder than EJB Deploy may fail to locate this directory properly. The result is some EJB deploy code will go to the non-source folder parent directory followed by deploy failing with a NullPointerException.
• (JR25549) Type mismatch: cannot convert from char to String error in the deployed code after deploying an EJB project containing a CMP entity with a char primary key CMP attribute.
• (PK36222) Preparation for Deployment fails on an EJB project checked into ClearCase^® in a workspace that is not connected to ClearCase.

3.16 Server tools

• (PK39466) The v5.1 WebSphere Test Environment does not stop when starting in v7.0 of the product with Global Security enabled.

3.17 WebFacing tool

WebFacing 7.0.0.2 requires Host Access Transformation Services (HATS) 7.0.0.1 or later for linked HATS/WebFacing projects. If you have HATS installed, you will also need to update to HATS 7.0.0.1 when it is available.

• The Display Program Messages screen now truncates messages the same way as on a 5250 display.
• The Web Settings view icons for the selected record or field are now consistent with the DDS outline view.
• Display files with FRCDTA or DFRWRT(*NO) are now rendered properly in linked HATS/WebFacing projects.
• A warning message will now pop up when launching the Properties page for an unmigrated project.

4.0 Known limitations, problems, and workarounds

This section describes known limitations and problems specific to this release, and any workarounds that are available.

Updates, limitations, and known problems about WebSphere Development Studio Client for iSeries, Version 7.0, are documented in the form of technotes on the IBM Support Web site http://www.ibm.com/software/awdtools/wdt400/support.

As limitations and problems are discovered and resolved, the IBM Software Support team updates the knowledge base. By searching the knowledge base, you can quickly find workarounds or solutions to problems that you experience. The Technotes link in the Self Help section of the WebSphere Development Studio Client for iSeries Web site launches a customized query of the live Support knowledge base. To narrow your search, specify V7 as the search term. To create your own query, go to the Advanced search page on the IBM Software Support Web site.

4.1 Data tooling documentation contains a reference to unsupported functionality

The "Developing data access applications" section of the information center incorrectly contains a reference to functionality supporting the deployment of JAR files for Java stored procedures, in the topic called "Routine and JAR file deployment." 
JAR file deployment is not supported, and the reference should be ignored. The rest of the information in this topic is accurate.

4.2 Internal server error "SAXException: Premature end of file" occurs when invoking an Axis Web service on WebSphere Application Server

When invoking an Axis Web service created using the Web Services Wizard on a WebSphere Application Server server, you might get a "(500) Internal Server Error" with the following message in the server console:

org.apache.axis.InternalException: org.apache.axis.ConfigurationException: org.xml.sax.SAXException: Fatal Error: URI=null Line=-1: Premature end of file.

This error occurs because the server-config.wsdd file in the Web project's WebContent/WEB-INF directory is empty.

Workaround: Choose a non-default location as the Web project's Java output directory before creating an Axis Web service on a WebSphere Application Server. 
To change the Java output directory:

1. In the Project Explorer view, right-click the Web project and select Properties.
2. In the left-hand pane of the Properties window, click Java Build Path.
3. Click the Source tab.
4. On the Source folders on build path page, Select Allow output folders for source folders check box, and then change the Default output folder entry to something other than WebProject/WebContent/WEB-INF/classes, where WebProject is the name of the Web Project.   For example, change the output folder to WebProject/output/classes.
   

4.3 J2C "Same Input and Output" Sample link does not work on the Linux operating system

An error occurs when you run the application on the Linux operating system only. When you open Help > Samples Gallery > Technology Samples > J2C Java Bean Technology Samples > Same Input and Output sample, and you click on the Import the sample (for WAS 6.0) link, you will get an error. The import wizard does not open, and a Null Pointer Exception message appears in the console:
Exception in GalleryWizardAction: java.lang.NullPointerException
wizard = com.ibm.etools.project.interchange.generic.CustomProjectInterchangeImportWizard
java.lang.NullPointerException
        at com.ibm.etools.project.interchange.generic.CustomProjectInterchangeIm portWizard$1.getAllProjectMap(Unknown Source)
        at com.ibm.etools.project.interchange.generic.CustomProjectInterchangeIm portWizard$1.doAddPages(Unknown Source)
        at com.ibm.etools.emf.workbench.ui.wizard.datamodel.WTPWizard.addPages(Unknown Source)
        at org.eclipse.jface.wizard.WizardDialog.createContents(Unknown Source)
        at org.eclipse.jface.window.Window.create(Unknown Source)
        at org.eclipse.jface.dialogs.Dialog.create(Unknown Source)
        at com.ibm.samplegallery.GalleryWizardAction$RunnableWizardDelegate.run( Unknown Source)
        at org.eclipse.swt.widgets.RunnableLock.run(Unknown Source)
        at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Unknown Source)
        at org.eclipse.swt.widgets.Display.runAsyncMessages(Unknown Source)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
        at org.eclipse.ui.internal.Workbench.runEventLoop(Unknown Source)
        at org.eclipse.ui.internal.Workbench.runUI(Unknown Source)
        at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown Sourc e)
        at org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source)
        at org.eclipse.ui.internal.ide.IDEApplication.run(Unknown Source)
        at org.eclipse.core.internal.runtime.PlatformActivator$1.run(Unknown Sou rce)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runAppli cation(Unknown Source)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Un known Source)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.eclipse.core.launcher.Main.invokeFramework(Unknown Source)
        at org.eclipse.core.launcher.Main.basicRun(Unknown Source)
        at org.eclipse.core.launcher.Main.run(Unknown Source)
        at org.eclipse.core.launcher.Main.main(Unknown Source)

Workaround:  Select the Import the sample (for WebSphere Application Server 6.1) link, and it will work on either WebSphere Application Server 6.0 or 6.1.

4.4 Converting static Web project with Web site navigation enabled to a dynamic Web project fails with an exception

When you attempt to convert a static Web project that has the Web site navigation enabled to a dynamic Web project (by selecting the project in the Project Explorer view, and then clicking Project > Convert to a Dynamic Web Project), the conversion fails with the exception "Cannot remove nature org.eclipse.wst.common.modulecore.ModuleCoreNature because it is a prerequisite of nature com.ibm.etools.siteedit.WebSiteNature".

Cause: The internal process of converting a static Web project (with Web site navigation) to a dynamic Web project requires removal of a project nature (ModuleCoreNature) that has a dependant nature (WebSiteNature).

Workaround: To convert the project successfully, remove the Website Navigation facet by completing the following steps:

1. Right click the Static Web Project; then click Properties and select Project Facets.
2. Click Add/Remove Project Facets.
3. In the Add/remove Project Facet dialog box, clear Website Navigation facet and click Finish.
4. Click OK.

Note: These steps are only required when you try to convert a Static Web project with Website Navigation facet enabled.

4.5 Publishing an EJB with multiple source directories fails with an error

If you attempt to publish an EJB project containing more than one source folder (for example, an annotation project that has an alternative source folder), publishing fails with errors.
You might see errors similar to the following example in the Console view:
 [1/11/07 15:28:36:906 PST] 00000027 SystemErr     R
*** ERROR ***: Thu Jan 11 15:28:36 PST 2007    org.eclipse.jst.j2ee.commonarchivecore.internal.exception.OpenFailureException: IWAE0023E Unable to open module file "AuctionV60EJB.jar" in EAR file "C:\v7001workspaces\7001Week2\AuctionV60EAR"
    Stack trace of nested exception:
    org.eclipse.jst.j2ee.commonarchivecore.internal.exception.OpenFailureException: IWAE0006E Archive is not a valid EJB JAR File because the deployment descriptor can not be found (case sensitive): META-INF/ejb-jar.xml

Workaround:  Edit the looseconfig.xmi file (a generated file) using the following steps:

1. On your computer, navigate to your workspace directory open in an editor the file /.metadata/.plugins/com.ibm.etools.wrd.websphere/looseconfigurations/EAR project name/looseconfig.xmi, where EAR project name is the name of your EAR project.
2. Change the two path attributes binariesPath and resourcesPath so to reference "ejbModule" instead of  "gen/src" for the EJB jar file.
3. Save your changes.

You should now be able to successfully publish the EJB.

4.6 The rollback feature is not supported in Installation Manager, Version 1.0.0.3

The rollback feature in the Uninstall Packages wizard and the rollback command for silent installation is not supported in Installation Manager, Version 1.0.0.3. As such, you cannot revert to a previously installed version of a package.

For example, if you installed WebSphere Development Studio Client, Version 7.0, and then updated to version 7.0.0.2, it is not possible for you to revert to version 7.0 by using the wizard or the command.

Workaround: To revert to an earlier version of a package, you must uninstall the entire package. A single uninstallation procedure removes the version 7.0 package and the upgraded version 7.0.0.2 package. After uninstalling, you need to reinstall the version 7.0 package.

4.7 Internet Explorer cannot handle AJAX requests on pages with character sets of "Windows-31J"

AJAX requests in Internet Explorer fail if "Windows-31J" is specified as the page's character set. If this character set is required for the page, use the alternative spelling "csWindows31J". 

4.8 IMS TM Resource Adapter information

The IMS TM Resource Adapter information included in the Help topics does not discuss the new features in IMS TM Resource Adapter Version 9.1.0.1.5 and Version 9.1.0.2.4. For details about the alternate client ID and SSL null encryption enhancements, see the IMS TM Resource Adapter User's Guide and Reference in the IBM Information Management Software for z/OS Solutions Information Center at http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/topic/com.ibm.etools.ims.tmra.doc/topics/tmresoverview.htm. 

4.9 Relational SDO wizard may treat Oracle Numerics as Short data types instead of Integers

When using the Relational SDO wizards, any Oracle database columns that were created as an Integer type (with no scale or precision) will be incorrectly treated as a java.lang.Short type by the Relational tooling.  This can cause problems at runtime with columns containing data values larger than a Short can contain.  To work around this issue, you can change the JDBC type for such columns.  In the Add or Configure Relational Record/Record List wizard, go to the page that shows the columns and corresponding types for the selected table.  You can right-click on any column and select Change JDBC Type from the context menu.  Select a type of Integer and click OK and then finish the wizard.  That column type will now be treated as an Integer at runtime. 

4.10 In data tools, you may get the "session manager not available" error message

In the Data perspective, you may get the "session manager not available" error message when you select the debug option for a stored procedure. The error message indicates that the session manager on the DB2^® server for z/OS Version 9 or DB2 for Linux, UNIX^®, and Windows Version 9 is not starting or is unreachable. In that case, you will need to run the session manager shipped with the product.

To start the session manager shipped with the product:

1. Open a command window and change to the <product install>\bin directory. By default, the product is installed in the C:\Program Files\IBM\SDP70 directory on Windows.
2. From the command prompt, run db2dbgm.bat from and note the IP address and the port number for the session manager.
3. Start the product and modify preferences for the debugger to use the local session manager:
   a. Click Window > Preferences, expand the Run/Debug node, and click DB2 Stored Procedure Debugger.
   b. In the Debugger pane, select Use already running session manager.
   c. In Host field, specify the IP address of the machine. You can also obtain the IP address from the command or terminal window where the session manager is running.
   d. In the Port field, specify the port for the local session manager. By default, the port number is 4554. You can also obtain the port number from the command prompt or terminal window where the session manager is running.

4.11 Problems profiling on a server

When starting a WebSphere Application Server V6.x server in profiling mode, and confirming that the server status displays profiling mode, the user interfaces for setting profiling options and for attaching Java processes do not display.

Workaround:

1. Start the server in profiling mode.
2. Click  Profile >  Attach-Java process and  create a new attach launch configuration. 

The server agent appears in the agent list of the Agents tab. You can now access the user interfaces for setting options for your profiling session.

4.12 Running a Junit test on the Integrated Agent Controller fails if the test is first run on a stand-alone Agent Controller

If you run a test suite as a Junit test by using Rational Agent Controller (stand-alone Agent Controller) and then run it again by using the Integrated Agent Controller, a message displays stating that the Agent Controller is not found or is not started.

Workaround: Delete the directory /tmp/IBMRAC and run the Junit test by using the Integrated Agent Controller.

4.13 Samples Gallery and Tutorials Gallery do not support the high resolution setting on Windows Vista operating system

The Samples Gallery and Tutorials Gallery do not support the new high resolution display setting "Larger scale(120DPI)- make text more readable" on Windows Vista operating system. The gallery content does not display if this option is set.

This setting enables through the following steps:

1. Open the Control Panel.
2. Click Ease of Access Center > Make Computer easier to see > Change the size of text and icon.
3. Select  Larger scale(120DPI)- make text more readable.
4. Click Save settings.

Workaround

If you changed to the new high resolution display option, change to a lower resolution setting (for example, the default 90 DPI setting).

5.0 IBM WebSphere Software Support

IBM WebSphere Software Support provides you with technical assistance.

For contact information and guidelines or reference materials that you will need when you require support, read the IBM Software Support Handbook.

For FAQs, lists of known problems and fixes, and other support information, visit the IBM WebSphere Software Support Web site.

For WebSphere software product news, events, and other information, visit the IBM WebSphere Software Web site.

Before you contact IBM WebSphere Software Support, gather the background information that you will need to describe your problem. When describing a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:

• What software versions were you running when the problem occurred?
• Do you have logs, traces, or messages that are related to the problem?
• Can you reproduce the problem? If so, what steps do you take to reproduce it?
• Is there a workaround for the problem? If so, be prepared to describe the workaround.

Posting questions on a newsgroup

To post your questions on the newsgroups, use the following resources.

News server:

• news://news.software.ibm.com/ibm.software.websphere.studio400

Suggested newsgroup:

• ibm.software.websphere.studio400

Other suggested forum:

• http://lists.midrange.com/cgi-bin/listinfo/wdsci-l

6.0 Notices and trademarks

© Copyright IBM Corporation 2000, 2007. All Rights Reserved.

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this documentation in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this documentation. The furnishing of this documentation does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this documentation and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

Trademarks and service marks

• CICS
• ClearCase
• DB2
• IBM
• IMS
• i5/Os
• iSeries
• Rational
• System i
• WebSphere
• z/OS

Intel is a registered trademark of Intel Corporation or its subsidiaries in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, or service names may be trademarks or service marks of others.