WebSphere Test Environment

VisualAge(R) for Java(TM)

Version 3.5

WebSphere(TM) Test Environment

RELEASE NOTES

1.0 Limitations and known problems
      1.1 WebSphere Test Environment Control Center repaints strangely on Windows 2000
      1.2 The WebSphere Test Environment Control Center not in foreground when launched a second time
      1.3 Cannot save JSP files in a directory with name that contains a "."
      1.4 Cannot use DBCS characters in a DataSource name
      1.5 The com.ibm.db2.jdbc.app.stdext.javax.sql.DataSource interface not in runtime
      1.6 Changing the attributes of a DataSource results in old attributes being used
2.0 Hints and Tips
      2.1 Changing the default HTML page
      2.2 Persistent Name Server (PNS) configuration
3.0 Prerequisites

1.0 Limitations and known problems

1.1 WebSphere Test Environment Control Center repaints strangely on Windows 2000

If you are using VisualAge for Java on Windows 2000, you may notice that some of the GUIs repaint strangely. To work around this problem, minimize the GUI, and then maximize it again. The GUI will then be restored properly.

1.2 The WebSphere Test Environment Control Center not in foreground when launched a second time

The WebSphere Test Environment Control Center does not come to the foreground when it is launched a second time. Select the Control Center icon from the taskbar to bring it into the foreground.

1.3 Cannot save JSP files in a directory with name that contains a "."

If you save a JSP file in a directory that has a name with a "." in it (for example, JSP1.0), then the browser will show a compilation error. This is a limitation of the WebSphere Test Environment.

1.4 Cannot use DBCS characters in a DataSource name

You cannot use DBCS characters in a DataSource name. If you try to add a DataSource object with a DBCS character in the name, the following error occurs:

javax.naming.NamingException: root exception is org.omg.CORBA.DATA_CONVERSION minor code:6 completed: no

1.5 The com.ibm.db2.jdbc.app.stdext.javax.sql.DataSource interface not in runtime

The com.ibm.db2.jdbc.app.stdext.javax.sql.DataSource interface is no longer part of the WebSphere run time. When migrating existing code that refers to DataSources, you must change all references of com.ibm.db2.jdbc.app.stdext.javax.sql.DataSource to javax.sql.DataSource.

1.6 Changing the attributes of a DataSource results in old attributes being used

If you want to change the attributes of a DataSource (for example, if you wish to change the database driver), and do not shut down the WebSphere Test Environment Control Center between deleting the DataSource and recreating it, the old attributes may be used instead of the new attributes when you recreate the DataSource. To avoid this problem, follow these steps:

In the WTE Control Center, on the DataSource Configuration page, delete the DataSource.
Shut down the Persistent Name Server and the WTE Control Center.
Restart the WTE Control Center and the Persistent Name Server.
Create the DataSource with the new parameters.

2.0 Hints and Tips

2.1 Changing the default HTML page

You can change the default HTML page from index.html to another page. Add the following lines to the default_app.webapp file:

<init-parameter> <name>default.page</name> <value>index2.html</value> </init-parameter>
where index2.html is the name of the file you want to be the new default HTML page.

You must also add these lines to the section near the end of the default_app.webapp file (the lines to insert are flagged by comment tags):

<servlet> <name>file</name> <description>File serving servlet</description> <code>com.ibm.servlet.engine.webapp.SimpleFileServlet</code> <servlet-path>/</servlet-path> <init-parameter> <name></name> <value></value> </init-parameter>  <autostart>true</autostart> </servlet>

where index2.html is the name of the file you want to be the new default HTML page.

2.2 Persistent Name Server (PNS) configuration

We strongly recommend that the default PNS configuration is used; the default configuration uses InstantDB.

If you choose to use Oracle or Sybase, you may encounter configuration issues, in which case you should revert to InstantDB.

The PNS cannot use DB2/400 as a backing store.

3.0 Prerequisites

Pentium (R) II processor or higher recommended. We recommend a minimum processor speed of 400 MHz. 128 MB RAM minimum is required if you wish to work in the VisualAge for Java WebSphere Test Environment. We strongly recommend 256 MB to avoid disk thrashing. If you want to run the Websphere Application Server with DB2(R) and VisualAge for Java concurrently, then a minimum of 512 MB is recommended.