Novell
exteNd Professional and Enterprise Suite 5

5.2.1 RELEASE NOTES

March 2005

Welcome to Novell^® exteNd^TM 5 (Version 5.2.1). These release notes include the following sections:

Important note about 5.2.1 documentation	Where to find information about Version 5.2.1 of Novell exteNd
Installing exteNd	How to prepare for installing Novell exteNd
System requirements	Software and hardware needed to run Novell exteNd
Supported databases for exteNd Application Server	Database types and versions supported by the Novell exteNd Application Server
What's new in 5.2	New features in Version 5.2 of Novell exteNd
What's new in 5.2.1	New features in Version 5.2.1 of Novell exteNd
Documentation updates	Updates to the documentation for Novell exteNd
Known issues	Known problems with this version of Novell exteNd
Problems fixed in Version 5.2.1	Problems that have been fixed in 5.2.1, including problem numbers

Release note updates   To check for updates to these release notes, click here.

exteNd Web site   For the latest exteNd downloads, discussion forums, news, and information, click here.

Important note about 5.2.1 documentation

Documentation specific to the 5.2.1 maintenance release of exteNd is provided in the product release note files:

• exteNd Suite Release Notes (which you are reading now)
• exteNd Director Release Notes
• exteNd Composer Release Notes
• exteNd Application Server Release Notes

These files include:

• Directions for upgrading to 5.2.1
• Descriptions of new features
• Added information about some existing features

The other exteNd help and PDF files are still primarily at the 5.2 level; they have not been updated to reflect 5.2.1 product changes (except where noted).

Installing exteNd

For a complete guide to installing exteNd 5 (including exteNd Director^TM, exteNd Composer^TM, and exteNd Application Server), see Installing Novell exteNd in the exteNd 5 Suite help. Additional notes and updates related to installation are listed below:

• Upgrading an existing exteNd installation
• Upgrading your exteNd applications
• Backing up MySQL databases before upgrading or uninstalling
• Backing up exteNd compile libraries before upgrading
• Changing MySQL encoding when upgrading
• Installing the exteNd development tools
• NetWare notes
• Linux notes
• Solaris notes
• Japanese documentation

Also, make sure you read Supported databases for exteNd Application Server and follow the configuration instructions for your DBMS before installing exteNd.

Upgrading an existing exteNd installation

To upgrade your machine to the current version of exteNd (5.2.1) if you have a prior version installed:

1. Back up any MySQL databases that you want to keep (see Backing up MySQL databases before upgrading or uninstalling).

2. Back up your current exteNd compile libraries if you want to continue using them (see Backing up exteNd compile libraries before upgrading).

3. Uninstall your prior exteNd version from the machine.

4. Save any of the remaining data files (from the Novell exteNd directory) that you want to continue using.

5. Install the new exteNd version on the machine.

   For details on these steps, see Installing Novell exteNd in the exteNd 5 Suite help.

   After the install, see Changing MySQL encoding when upgrading if you need to continue using any MySQL databases with Latin1 encoding.

Upgrading your exteNd applications

When moving to the new exteNd version, you must also think about upgrading your existing exteNd applications as needed. Use the following links to find the application upgrade topics that apply to you:

• exteNd Director upgrade notes
• exteNd Composer upgrade notes
• exteNd Application Server upgrade notes
• Moving to the JBoss Application Server

Backing up MySQL databases before upgrading or uninstalling

Before you upgrade or uninstall exteNd on Linux or Windows, you should back up any MySQL databases that you want to keep. The exteNd uninstall process removes all of the exteNd Suite components, including the MySQL database server. Any MySQL databases that you have may be affected when you uninstall or when you install a new exteNd version. By backing up first, you can safeguard that data for future use. (On NetWare, the exteNd install/uninstall does not affect MySQL.)

MySQL provides tools (such as mysqldump) that you can use to back up your databases. For more information on the backup process (and how to restore your data), see the MySQL documentation.

Here's a simple example of creating a backup of the MySQL database named expressportal:

   mysqldump expressportal --port=63306 --user=root --password=password --result-file=backup1.sql

And here's a simple example of restoring the expressportal database:

   mysql --user=root --password=password expressportal < backup1.sql

Setting FOREIGN_KEY_CHECKS when restoring

If you use mysqldump, then you may need to set the FOREIGN_KEY_CHECKS flag when restoring your database. If you see a message like the following, you probably need to set FOREIGN_KEY_CHECKS:

   ERROR 1005 at line 42: Can't create table '.\expressportal\cmdoccategories.frm' (errno: 150)

For more information, see the MySQL documentation.

Backing up exteNd compile libraries before upgrading

In some cases, you may want to keep using your older version of the compile libraries that exteNd provides. If so, before you uninstall your prior exteNd version, make a copy of the Novell exteNd tools\compilelib directory and its contents. After installing your new version of exteNd, you can rename the newly-installed tools\compilelib directory and replace it with your copy of tools\compilelib from the prior exteNd version. (PPRs 48955 and 48962)

Changing MySQL encoding when upgrading

By default, the MySQL 4.1.9 server installed with exteNd 5.2.1 is configured to support Unicode characters using UTF8 encoding. If you were running a previous version of MySQL using Latin1 encoding, you may want to change the MySQL 4.1.9 server to use Latin1 encoding rather than the installed configuration for Unicode.

Changing the MySQL 4.1.9 server to use Latin1 encoding is particularly important if you are restoring MySQL databases from previous versions of exteNd. Using a restored Latin1 database on a MySQL server configured for Unicode will result in the following error:

   ** SQLException : Illegal mix of collations (latin1_general_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '='

If you see this error, change the MySQL 4.1.9 server to use Latin1 instead of Unicode by following these steps:

1. Make sure you have backup copies of your existing MySQL databases.

   For more information, see Backing up MySQL databases before upgrading or uninstalling.

2. Connect to the MySQL server as the administrator and drop all databases except the database mysql.

   The mysql database is required for MySQL server configuration. The MySQL server will not start if this database is missing.

3. Shut down the MySQL server.

4. Edit the my.cnf or my.ini file.

   On Windows, the my.ini file is found in C:\WINDOWS.

5. Change the default character set by commenting out the line for UTF8 and adding a line for Latin1:

      #default-character-set=utf8
      default-character-set=latin1

6. Restart the MySQL server.

7. Restore the existing MySQL databases that you backed up.

   For more information, see Backing up MySQL databases before upgrading or uninstalling.

8. If you restored your SilverMaster database, you should run SilverMasterInit in Refresh mode to bring it up to the state of your new exteNd version:

      SilverMasterInit -U mysql_username -P mysql_password -r -A admin_username -W admin_password

   If you did not restore your SilverMaster database, you need to create a new SilverMaster database (in mysql) and then initialize it:

      mysql> create database silvermaster;
   
      SilverMasterInit -U mysql_username -P mysql_password -f -A admin_username -W admin_password

9. Start your application server.

10. Recreate any connection pools needed.

Installing the exteNd development tools

The exteNd development tools (designers) are supported for a single user per install. When installing the exteNd development tools on any platform, log in as the same user who will be using these tools. Otherwise, you may encounter file permission problems (such as Access is denied for ide.props.txt) when trying to run the tools. (PPR 45454)

On Linux, it's recommended that you log in as a user other than root when installing and using the exteNd development tools. Just make sure that user has adequate permissions for your target install directory (which defaults to /opt/novell/exteNd5).

NetWare notes

On Novell NetWare^®, you install the Novell exteNd Application Server as part of the NetWare install. You can choose to install the application server during the initial NetWare install, or you can do it later after NetWare is set up.

For updated notes on installing NetWare and the application server, see the NetWare Readme.

Starting the exteNd install on NetWare

If you plan to install the exteNd Suite on NetWare, note the following details about starting the installer:

• When installing from the product CD, you can start the installer by running the provided install.NCF file as is.

• When installing from another location, you may need to edit install.NCF before running it. Make sure the java command line in install.NCF specifies the correct path for the xtndInst.jar file. For example:

     java -cp sys:\xtndInst.jar install

  Alternatively, you can execute this java command line directly (instead of using the install.NCF file).

Completing the exteNd install on NetWare

When the GUI screens of the exteNd Suite installer complete and indicate that the install is finished, be aware that the exteNd Composer server components may take several additional minutes to deploy to the application server. Please wait during this time to allow that deployment to complete.

To monitor the exteNd Composer deployment, go to the NetWare logger screen. You'll know that you're done when you see the deployment completed message on the console. (PPR 43934)

Linux notes

When you start the exteNd Suite installer on Linux (xtndInst_lnx.bin), note that it may take several minutes for the installer to extract the files it needs. Please wait during this time. Although it may seem that nothing is happening, the installer will eventually display. (PPR 46892)

Solaris notes

Before you run the JRE on Solaris, you must install the required patches. The patch files are shipped on the Novell exteNd product CD in the required subdirectory. You may copy the patches from the CD or you may download these patches and any newer required patches from the Sun Web site.

See sunsolve.sun.com/pub-cgi/show.pl?target=patches/J2SE for Solaris patch requirements.

Restart exteNd Application Server after installation

After you install exteNd on Solaris, you must restart the exteNd Application Server before deploying to it. Otherwise, you'll get deployment errors. (PPR 49031)

Japanese documentation

A Japanese edition of the Novell exteNd 5 documentation is available at www.novell.com/ja-jp/documentation/extend.html. You can do either of the following:

• Browse the Japanese exteNd 5 documentation online.

• Download the installer for the Japanese exteNd 5 documentation.

  You can then run this installer to add the Japanese documentation to your local exteNd installation. The installer stores it in the Novell exteNd Docs_JA directory (alongside the English documentation in the Docs directory).

  Installing the Japanese documentation does not affect exteNd context help; it always displays the English documentation from the Docs directory.

NOTE: The manuals currently included in the Japanese documentation apply to the exteNd 5.0 products; due to production schedules, Japanese translations of the 5.2 manuals are not yet available. However, all exteNd release notes in the Japanese documentation are at a 5.2 level.

Release notes in Japanese

You can click the following links to read the latest exteNd product release notes in Japanese on the Novell exteNd documentation Web site:

• exteNd Suite Release Notes
• exteNd Director Release Notes
• exteNd Composer Release Notes
• exteNd Application Server Release Notes

System requirements

This section describes the software and hardware needed to run exteNd 5.2.1:

• Development environment
• Server environment
• Deprecated system platforms
• J2EE compatibility

Development environment

Topic	What's required
Operating system	One of the following: SUSE Linux Professional 9 Novell Linux Desktop 9 Windows 2000 Professional with Service Pack 1 or higher Windows XP Professional
Minimum RAM (memory)	512 MB for exteNd (1 GB or more recommended) in addition to memory required for the OS and any other applications
Disk space	Depends on what you choose to install, for example: 1.1 GB for the full exteNd Suite 365 MB for exteNd Director only 210 MB for exteNd Composer only NOTE: Install may take up to 2.0 GB in temporary storage.
Display mode	True Color (32-bit), 800 x 600 or higher (1024 X 768 minimum recommended)
Java 2 JRE (Java Runtime Environment)	One of the following, included with exteNd 5: Linux: JRE 1.4.2_03 Windows: JRE 1.4.2_03-b02

Server environment

Topic	What's required
Operating system	One of the following: SUSE LINUX Enterprise Server 9 (SP1) Novell Open Enterprise Server Red Hat Enterprise Linux AS 3.0 Novell NetWare 6.5 SP3 and SP5 Windows 2003 Server Windows 2000 Server with Service Pack 1 or higher (see the note below) Solaris (Sparc) 8, 9
Application server	One of the following: JBoss Application Server Version 4.0.1 or Version 4.0.3 with SP1 (4.0.3 with SP1 is the preferred platform) Novell exteNd Application Server Version 5.2.1, included with exteNd 5 (on NetWare, it is provided by the NetWare install) BEA WebLogic Server Version 8.1 Service Pack 4 (Enterprise Suite only) IBM WebSphere Server Advanced Edition Version 5.0 or 5.1 (Enterprise Suite only) Jakarta Tomcat Version 4.1
Database support	One of the following: Oracle 9i or 10g IBM DB2 8.1 or 8.2 Microsoft SQL Server 2000 MySQL 4.1.9, included with exteNd 5 on Windows and Linux Sybase Adaptive Server Enterprise (ASE) 12.5 For more information, see Supported databases for exteNd Application Server (below).
LDAP directory	(Optional) exteNd Director supports the following: Novell eDirectoryTM 8.6.2, 8.7.3 Novell exteNd LDAP Utility, included with exteNd 5 (for development only; not supported in production)
Web browser	One of the following: For the DAC (Director Administration Console) and Portal tiers: Internet Explorer 6 SP1 (recommended) Firefox 1.0 Mozilla 1.6.x or 1.7 For the CMS (Content Management Subsystem) Administration Console: Internet Explorer 6 SP1
Minimum RAM (memory)	1 GB for exteNd (2 GB or more recommended) in addition to memory required for the OS and any other applications
Disk space	250 MB for the core server product; 58 MB for the JRE NOTE: Install may take up to 2.0 GB in temporary storage.
Display mode	High-color, 16-bit or higher when running the Server Management Console (SMC) with resolution 1024x768 or better On NetWare, the default resolution for the GUI environment is 800x600. To view the entire SMC, you must change this setting to at least 1024x768.
Java 2 JRE (Java Runtime Environment)	One of the following, included with exteNd 5: Linux: JRE 1.4.2_03 NetWare: Novell JVM 1.4.2 for NetWare (provided by the NetWare install) Windows: JRE 1.4.2_03-b02 Solaris: JRE 1.4.2_03
CORBA ORB JMS server JTS server	Novell exteNd Messaging Platform 5.2, included with exteNd 5 For details on running the JMS server in the Novell exteNd Application Server environment, see the chapter on running the server in the exteNd Application Server Administrator's Guide.

Support for Windows 2000

The Novell exteNd Application Server does not currently support these features of Windows 2000:

• Active Directory (except as a straight LDAP provider)
• Kerberos
• The Windows 2000 load balancing and clustering features

Web Server Integration Modules

The Web Server Integration (WSI) modules of the Novell exteNd Application Server are available for download at developer.novell.com/ndk/wsi.htm. These are the supported Web servers and platforms:

Web server	Platform
Apache HTTP Server 2.0 or higher	Linux, NetWare, Solaris, Windows NT/2000
Microsoft IIS 4.x	Windows 2000/2003
Sun iPlanet 4.x, 6.x	Solaris, Windows 2000/2003

Server Management Console

The Server Management Console (SMC) of the Novell exteNd Application Server is a standalone J2EE application. It is supported on all of the same platforms as the application server. It is normally installed with the server (if installed alone, it requires about 75 MB of space including the JRE, SilverCMD tools, and supporting files).

Deprecated system platforms

This section lists system platforms for which support is now deprecated.

• Operating systems:
  • SUSE LINUX Enterprise Server 8

    Note: The Autonomy search engine provided with exteNd Director 5.2.1 is not compatible with this OS.

  • Red Hat Enterprise Linux AS 2.1

    Note: The Autonomy search engine provided with exteNd Director 5.2.1 is not compatible with this OS.

• Databases:
  • Oracle 8i

J2EE compatibility

This version of exteNd enables you to develop applications for Java 2 Platform, Enterprise Edition (J2EE) Version 1.3.

Supported databases for exteNd Application Server

This section presents the database types and versions supported by the Novell exteNd Application Server. It's organized according to the various database uses possible in an application:

• SilverMaster and deployment support
• Connection pool support
• XA support
• EJB 2.0 container support

General policy on database support   The tables in this section list the most recent versions of databases and drivers Novell has tested. Newer database/driver versions not listed will usually work fine for the Application Server—especially minor point releases. Older versions Novell has previously supported should still work for the Application Server as well.

If Novell knows of a specific database or driver version that is problematic, these notes will mention it. As long as you're using a database type and driver generally supported on a recent version of the Novell exteNd Application Server and are using a driver version that the vendor says is compatible with your database version, issues specific to newer databases or drivers can be submitted to Technical Support and Novell will investigate. Some issues are driver problems that Novell cannot address and that will simply require using an earlier or later version of the driver.

Database configuration help   The Novell exteNd Application Server Database Configuration Guide provides information about configuring various types of databases to work with the application server. Make sure you follow these configuration instructions before installing exteNd. Use this table to find the chapter for your database type:

To use this database type	See
DB2	Configuring DB2 Databases
Microsoft SQL Server	Configuring Microsoft SQL Server Databases
MySQL	Configuring MySQL Databases
Oracle	Configuring Oracle Databases
Sybase Adaptive Server Enterprise	Configuring Sybase Adaptive Server Enterprise Databases

SilverMaster and deployment support

The following table lists databases/drivers that have been successfully tested for use as the application server's SilverMaster or as deployment databases.

Database	Driver type	Novell exteNd Application Server platforms
IBM DB2 8.1	IBM DB2 JDBC/Type 2 Version 2.0	Windows, Linux, Solaris
Microsoft SQL Server 2000	Microsoft ODBC driver for SQL Server version 2000.80.194.00 with Novell exteNd JDBC-ODBC bridge (see the Note on deprecation)	Windows
Microsoft SQL Server 2000	Microsoft JDBC driver for SQL Server version 2.2.0022	Windows, NetWare
MySQL 4.1.9	Connector/J 3.1.6	Windows, Linux, NetWare 6.5 SP4
Oracle 9i (9.0.1.1.1)	Oracle OCI Driver	Windows, Linux, Solaris
Oracle 9i (9.2.0.1)	Oracle Thin JDBC 9.2.0.1 Driver	Windows, Linux, NetWare, Solaris
Oracle 9i (9.2.0.1)	Oracle OCI Driver	Windows, Linux, Solaris
Sybase Adaptive Server Enterprise 12.5	jConnect 5.5	Windows, Linux, NetWare, Solaris

Note on deprecation   The Novell exteNd JDBC-ODBC bridge and the Novell exteNd Oracle drivers are deprecated. Novell recommends that you use the vendors' JDBC drivers to connect to your databases.

Connection pool support

The application server supports JDBC access to databases via connection pools. JDBC connection pools can be established for databases that provide either a JDBC 1.0 or JDBC 2.0 driver.

For more information on connection pool support, see the chapter on data source configuration in the exteNd Application Server Administrator's Guide.

XA support

The following table lists databases/drivers that have been successfully tested with the application server's XA (global transaction) support in connection pools.

Database	Driver type	Novell exteNd Application Server platforms
Oracle 9i (9.2.0.1)	Oracle Thin JDBC 10.1.0.3 Driver	Windows, Solaris, Linux, NetWare

EJB 2.0 container support

The following table lists databases/drivers that have been successfully tested with the application server's EJB 2.0 container.

Database	Driver type	Novell exteNd Application Server platforms
IBM DB2 8.1	IBM DB2 JDBC/Type 2 version 2.0	Windows, Linux, Solaris
Microsoft SQL Server 2000	Microsoft JDBC driver for SQL Server version 2.2 patch 1	Windows, NetWare
MySQL 4.1.9	Connector/J 3.1.6	Windows, Linux, NetWare 6.5 SP4
Oracle 9i (9.0.1.1.1)	Oracle OCI Driver	Windows, Solaris
Oracle 9i (9.2.0.1)	Oracle Thin JDBC 9.2.0.1 Driver	Windows, Linux, NetWare, Solaris
Oracle 9i (9.2.0.1)	Oracle OCI Driver	Windows, Solaris
Sybase Adaptive Server Enterprise 12.5	jConnect 5.5	Windows, Linux, NetWare, Solaris

What's new in 5.2

For a summary of the new features in exteNd 5.2, see:

• What's New for exteNd Director
• What's New for exteNd Composer
• What's New for exteNd Application Server

Also, note these new general features of the exteNd Suite in 5.2:

Feature	Description
Linux support for development	When installing exteNd on Linux, you can now choose the exteNd design tools (including exteNd Director and exteNd Composer) as well as the exteNd server components. You'll see that the suite installation program offers all of the exteNd product configuration options on Linux: Express, Server Express, Server, Tools, and Custom. (For details, see Installing Novell exteNd.) This expanded platform support gives you the choice of working in either Linux or Windows when developing exteNd applications.
International character sets	In this version, support for international character sets has been improved throughout exteNd, especially for multibyte character sets.
Performance	Numerous aspects of exteNd performance have been enhanced in this version.

What's new in 5.2.1

For information on the new features in exteNd 5.2.1, see:

• exteNd Director Release Notes
• exteNd Composer Release Notes
• exteNd Application Server Release Notes

Also, note these new general features of the exteNd Suite in 5.2.1:

• JBoss support
• Improved support for EPM
• EPM on JBoss
• MySQL changes

JBoss support

This version of exteNd includes support for the JBoss Application Server Version 4.0.1 and Version 4.0.3 with SP1. Version 4.0.3 with SP1 is the preferred platform. The exteNd Director and exteNd Composer development environments provide deployment support for JBoss. In addition, the installation program for exteNd gives you the ability to deploy the Composer Enterprise Server to the JBoss Application Server.

For instructions on migrating to JBoss, see the JBoss Migration Guide.

Improved support for EPM

This version of exteNd makes it easier for you to configure the Novell Enhanced Provisioning Module (EPM) for Nsure^TM Identity Manager (a provisioning toolkit that you add on to exteNd). With exteNd 5.2, you needed to install patches for exteNd Director and exteNd Composer in order to use EPM (as described in the EPM Administrator's Guide in the chapter "Setting Up Your Environment"). exteNd 5.2.1 is made to support EPM, so you don't need those patches.

For the latest notes on using EPM and this version of exteNd, go to these links on the Novell documentation Web site:

• EPM release note updates
• exteNd Suite release note updates

EPM on JBoss

With this version of exteNd, you can now deploy EPM portal applications to the JBoss Application Server. When setting up EPM on JBoss, follow the instructions in the EPM Administrator's Guide and use the JBossLDAP realm instead of native LDAP. The panels you fill out are exactly the same. For more information about the JBossLDAP realm, see the chapter on deployment in the JBoss Migration Guide.

To deploy an EPM project on JBoss   To deploy an EPM project on JBoss you'll need to change the log4j entry in the extendlogging.properties file. After you extract the files from the SetupEPM.jar file, you'll find the extendlogging.properties file in the \config subdirectory. Change the log4j.rootLogger=ERROR, CON to log4j.logger.com.novell=ERROR, CON (PPR 49120)

MySQL changes

This version of exteNd includes several changes related to MySQL:

• New MySQL version
• Using MySQL tools
• MySQL directory changed on Linux
• MySQL driver JAR renamed

New MySQL version

On Linux and Windows, exteNd now includes Version 4.1.9 of MySQL, along with Version 3.1.6 of the Connector/J driver. (On NetWare, you still use the MySQL version provided by the NetWare installer.)

MySQL is installed as a Unicode database server with support for multibyte character sets, including UTF8.

Using MySQL tools

MySQL tools are provided in the Novell exteNd MySQL\bin directory. Here are a few of the most useful ones (these are all non-graphical, command-line tools):

MySQL tool	Description
mysql	Client for executing SQL statements interactively or in batch mode
mysqladmin	Client for performing administrative operations (checking server configuration and status, creating and dropping databases, etc.)
mysqldump	Client for dumping a database for backup (dumps contain SQL statements to create and/or populate tables)
mysqlimport	Client for importing data files into tables

When running any of these tools, you must specify the location of the MySQL configuration file (my.cnf). You do that by including the --defaults-file option. For example:

   --defaults-file=/opt/novell/exteNd5/MySQL/my.cnf

MySQL-Front is no longer included with the MySQL install.

Note that MySQL AB offers a visual administration console (MySQL Administrator) that you might want to obtain to administer your MySQL environment. For more information, go to www.mysql.com/products/administrator.

MySQL directory changed on Linux

The MySQL directory that exteNd provides has been renamed on Linux (from mysql to MySQL) to be consistent with other platforms (PPR 48428). For example, in the previous version it was:

   /opt/novell/exteNd5/mysql

In this version it is:

   /opt/novell/exteNd5/MySQL

MySQL driver JAR renamed

The JAR file that exteNd provides for the MySQL JDBC driver has been renamed to mysql-connector-java-bin.jar (PPR 48428). For example, on Windows it is:

   C:\Program Files\Novell\exteNd5\MySQL\jdbc\mysql-connector-java-bin.jar

On Linux it is:

   /opt/novell/exteNd5/MySQL/jdbc/mysql-connector-java-bin.jar

Documentation updates

The following updates apply to the documentation and help for the exteNd Suite:

Novell exteNd 5 Guided Tour has been updated

The exteNd Suite Guided Tour has been updated to work with exteNd 5.2.1. Use the following links to get the updated Guided Tour:

HTML: http://www.novell.com/documentation/extend52/Docs/help/exteNd/books/learnTOC.html

PDF: http://www.novell.com/documentation/extend52/pdfdoc/exteNdSuite_pdfs/NE52-NovellexteNd5GuidedTour.pdf

Running the LDAP utility

The LDAP utility's readme.txt file (in the Novell exteNd tools\LDAPUtility directory) describes how to run the utility on Windows by executing the following command line:

   javaw -jar ldaputility.jar [-option1 -option2 -etc]

Note that on other platforms, you should execute the following command line instead (PPR 46623):

   java -jar ldaputility.jar [-option1 -option2 -etc]

Running the application server as a UNIX/Linux daemon

When you set up the Novell exteNd Application Server (or cluster) to run as a daemon in UNIX or Linux, note that the startup scripts you need are provided in the following directory (assuming that you install exteNd to the default path /opt/novell/exteNd5):

   /opt/novell/exteNd5/AppServer/etc/

Keep this in mind when reading the exteNd installation documentation, which is vague on the script location. (PPR 48626)

Known issues

The following is a summary of current known issues with the exteNd Suite. Note that you may encounter other issues; check the release note updates for more information.

• Installation issues
• MySQL issues
• Platform issues

See the individual product release notes for related known issues:

• exteNd Director Release Notes
• exteNd Composer Release Notes
• exteNd Application Server Release Notes

Installation issues

• Temp directory size   The InstallAnywhere wizard uses a temp directory for storage at the time of install. Depending on what you choose to install, the temp directory will grow to three times the size of the actual files. For the entire suite, this could approach the 2 GB range.

• Total size requirements   The size of the actual files on disk may be from 0 to 100 MB larger than what is estimated by InstallAnywhere during the install. The entire suite should not exceed 1.1 GB.

• Xerces versions installed with exteNd   In Version 5.2 of exteNd, Xerces is installed as follows:
  • If you install only the exteNd Application Server, you get Xerces 2.4.0 (required for strict J2EE compliance)

  • If you install exteNd Director or exteNd Composer, you get Xerces 2.6.0 (required to support features of these products)

    In this case, note that the signature of one of the Xerces implementation methods has changed in an incompatible way; it now throws an additional exception. As a result, it is not in strict J2EE compliance, but this is unlikely to affect you.

  (PPR 44293)

• exteNd Messaging Platform required when installing Composer Designer alone   If you want to install just Composer Designer on a machine, you can select it via the Custom option of the exteNd installation program. But make sure you also select exteNd Messaging Platform (MP), which is required by Composer Designer. If MP is not installed, you'll get an error (concerning com.phaos.SSL.SSLSocket) when you try to start Composer Designer. (PPR 46750)

• Installing exteNd Composer Enterprise in an exteNd Application Server cluster   When you install exteNd Composer Enterprise in a clustered exteNd Application Server environment, the following exception will appear in the clustered application server console:

     exteNd Composer Enterprise Failed to Start due to the following exception: java.lang.NoClassDefFoundError

  Restarting the application server will clear this exception, then exteNd Composer Enterprise will start normally. (PPR 46752)

• Building and deploying Express Portal for installs over ssh or telnet   On Linux, if you install over a non-XWindows terminal (such as ssh or telnet) using console mode (xtndInst_lnx.bin -i console), Express Portal will not be built or deployed. The workaround is to follow these steps:
  1. After installing from console mode, enter export DISPLAY=:0:0
  2. To build the Express Portal EAR, execute exteNd_dir/install/buildEARandSharedLibs.sh
  3. To deploy the Express Portal EAR, execute exteNd_dir/install/OTB_EARDeploy.sh
  4. When finished, enter unset DISPLAY

  (PPR 46763)

• False errors after install to non-default location on Linux   On Linux, if you install the exteNd Suite to a location other than the default directory, the installer may generate some false error messages concerning the default directory (/opt/novell/exteNd5). In this case, the installer's Done panel indicates that the install completed but with errors, and the messages are listed in the install log file. You can ignore these messages. (PPR 48762)

• Japanese installer displays some English text   When you use the Japanese version of the exteNd installation program, the MySQL portion of the install displays information in English, not in Japanese. (PPR 49008)

• expressportal and samples50 databases not installed during Custom install   When you choose a Custom install of exteNd, the expressportal and samples50 databases should be installed by default, but are not (PPR 48987). To create these databases yourself, follow these steps:
  1. You must install MySQL before creating the samples50 database.

  2. To create the MySQL database samples50, manually execute the script:

        ...\exteNd5\install\samples50.sql

     To use this database, you must create a connection pool for it.

  3. To create the expressportal database:
     • Create a clean database. You can use any supported DBMS.
     • Create a connection pool for this database.

     When the ExpressPortal application is deployed, the database will be populated with the necessary tables.

MySQL issues

• Protecting MySQL against the UDF Worm   On Windows, MySQL servers with poor firewall and password security are vulnerable to the UDF Worm, which uses the MySQL root account to install a UDF (User Defined Function) and then tries to infect other machines. To protect your environment against this worm, make sure that you:
  • Use strong (hard-to-guess) passwords on MySQL root and other accounts
  • Set up your MySQL servers behind a firewall

  For more information, see the following MySQL Tech Resources article: Security Alert 01/27/2005.

  (PPR 48784)

• Starting exteNd installer stops MySQL service   If you start the exteNd installer on a machine where the MySQL service is running, the installer will automatically stop that service. So remember to consider your MySQL availability needs before beginning an exteNd install. (PPR 46772)

• Avoiding conflicts with existing MySQL installations   (Windows only) Avoid using the MySQL that ships with exteNd 5 if you do not want to conflict with an existing MySQL installation. If you have a different database from the exteNd list of supported database vendors, you can choose to use that database while running through the Custom option of the exteNd 5 install.

• SQL NOT statements are not evaluated as expected in some cases   exteNd does not have any code that is affected by this, but developers may run into it when writing their own SQL code. For example, say you have a table1 with the following columns and rows: key_column value_column 0 value0 1 value1 2 value2. The following SQL statement returns an empty result set: SELECT key_column FROM table1 WHERE NOT value_column = 'value0'. If you put parentheses around the evaluation condition, it returns keys 1 and 2 as expected: SELECT key_column FROM table1 WHERE NOT (value_column = 'value0').

Platform issues

• Tomcat 5.0 needs javax.transaction to support exteNd   Jakarta Tomcat Version 5.0 no longer provides an implementation of the javax.transaction.* package. This package is required (in the Tomcat lib directory) if you intend to deploy exteNd applications to Tomcat 5.0. (PPR 48900)

Problems fixed in Version 5.2.1

Number	Description
43541	Docs & Help - Install/Common - error in server install chapter
46772	Install - Common - Starting install stops MySQL Service
46632	Install - Common - Description of Composer Server for existing exteNd App Server needs updating
46642	Install - Common - Incorrect jars are installed in Composer Tomcat, WebSphere, WebLogic
46757	Install - Common - MySql root password dialog is different on Linux than Windows
46731	Install - Common - Composer Designer fails to start after installing as Custom - Composer only
41131	Install - Common - MySQL charset/sort should probably be UTF8 General
47498	Install - Common - NW installer has reference to "Extend Suite" but should be "exteNd Suite"
47414	Install - Common - SilverMasterInit failed during Express install
46863	Install - Common - DirCPCreate.out file is desired, but it contains potentially confidential info
47569	Install - Common - DB password field is not encrypted (does not appear as ****)
47526	Install - Common - Missing some information text in error dialog during installation
47499	Install - Common - Component named "Extend Suite" in NW installer has a vague description
47242	Install - Common - Custom Install on Windows does not prompt for Driver location
38595	Install - Common - Uninstaller needs to check and warn that Appserver is running
47117	Install - Common - EVAL Install Keys do not properly turn on Workflow for Director
39180	Install - Common - Composer process DB not available message on app server console
44448	Install - Common - install ShutdownCacheCoordinator in extend5/Director program folder for windows
47440	Install - Common - install failed, can't start VM, VM is wrong or mangled
47190	Install - Common - Installer doesn't clean up references to old mysql jars in AGCLASSPATH
45670	Install - Common - Failure with sminit in install using MySQL 4.1.1 (for ScottK or James)
46591	Install - Common - Japanese install: Error on choosing restrict access to the Novell AppServer
42276	Install - Common - server installs should not install dir exes
44173	Install - Common - Need some kind of upgrade direction in install
45454	Install - Common - Get "Access is denied" when running Designer as different user
42405	Install - Common - MySQL: using mysqld-max-nt to create a service fails
43557	Install - Common - casing in install
46621	Install - Common - Installer should not install xd_dev script

---

Copyright © 2004-2005 Novell, Inc. All rights reserved. Copyright © 1997, 1998, 1999, 2000, 2001, 2002, 2003 SilverStream Software, LLC. All rights reserved.