WebSphere MQ for multiplatforms v7.0 readme

Answer

Readme

Abstract
------------
This document contains the WebSphere MQ readme for product version 7.0.0.0

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

DESCRIPTION
---------------------
This release notes file contains information that was not available in time for
our publications. It also details updates, limitations, and known problems. In
addition to this file, README.TXT, you can find more information on the
WebSphere MQ Web site:
http://www.ibm.com/software/integration/wmq/

The SupportPac Web page is at:
http://www.ibm.com/support/docview.wss?rs=977&uid=swg27007205

For current information on known problems and available fixes, see the Support page of the WebSphere MQ Web site at:
http://www.ibm.com/software/integration/wmq/support/

Web documentation updates
The latest updates to the Web-based WebSphere MQ documentation are now available from the WebSphere MQ Web site at:
http://www.ibm.com/software/integration/wmq/library/

Announcement letter
The announcement letter for WebSphere MQ Version 7.0 (US English) is available
on the Web at
http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&appname=GPA&htmlfid=897/ENUS208-068 
(for distributed platforms), or
http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&appname=GPA&htmlfid=897/ENUS208-067 
(WebSphere MQ for z/OS ).

See the announcement letter for the following types of information:
- Detailed product description, including description of new function
- Product-positioning statement
- Ordering details
- Hardware and software requirements

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

UPDATE HISTORY
14 May 2008 - US English version of this file sent for translation.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

LIMITATIONS AND KNOWN PROBLEMS
------------------------------------------------------------

If you have a previous installation of WebSphere MQ Version 7.0
---------------------------------------------------------------
If you have a previous installation of WebSphere MQ Version 7, for example a Beta
version, you might experience a problem when you launch the WebSphere MQ
Explorer. If you find that Eclipse starts but the WebSphere MQ perspective does
not open properly, perform the following actions, as necessary.

In the Explorer, click the Window menu and select "Restart perspective".

If this does not work, close the Explorer and issue the command
strmqcfg -i
at the command line, the start the Explorer again.

If this does not work, close the Explorer and check there is no Eclipse process running.
This procedure will remove Explorer data such as remote queue manager definitions
and custom schemes and filters, so make a note of any such data you want to keep.
Delete the following folders:
On Windows: C:\Documents and Settings\<userid>\Application Data\IBM\MQ Explorer
C:\Documents and Settings\<userid>\.eclipse
On Linux: /home/<userid>/.mqdata
/home/<userid>/.eclipse
Issue the command
strmqcfg -i
at the command line, the start the Explorer again

Migration from WebSphere MQ Version 6 earlier than CSD 6.0.2.3
--------------------------------------------------------------
The first time the WebSphere MQ Explorer is started after migration, error
message AMQ4473 might be displayed and an FFST logged stating that the
WMQ_Schemes.xml file used to save schemes was found to be in an invalid format,
and that all user-defined schemes must be re-created.
Before CSD 6.0.2.3 schemes were not saved correctly. If you use schemes, you
will have experienced this problem and upgraded to a later CSD level. If you
have not created your own schemes and are using an earlier version of WebSphere MQ
you will see this message on starting WebSphere MQ Explorer. However,
MQ Explorer continues, creating a new default set of schemes, so no action is
required.

Migration from WebSphere MQ Version 6.0.2.3 or earlier on Windows
-----------------------------------------------------------------
When you migrate from WebSphere MQ Version 6.0.2.3 or earlier to Version 7.0,
the "exits" directory is emptied.
This is normally c:\Program Files\IBM\WebSphere MQ\exits or c:\Program
Files\IBM\WebSphere MQ (x86)\exits, but you might have installed to a different
directory.
Either apply service patch 6.0.2.4 or later, or back up your "exits" directory
before migrating.

Migration: save JMSAdmin.config
-------------------------------------------------
Save the file JMSAdmin.config (in the <install_root>/java/bin directory) to another
location before upgrading to WebSphere MQ v.7.0 or it will be overwritten.

Support for WebSphere MQ on Windows Vista Japanese Edition
----------------------------------------------------------
WebSphere MQ does not support the new Japanese standard, JIS X 0213:2004.
Windows Vista Japanese Edition formally supports JIS X 0213:2004 characters.
These JIS X 0213:2004 characters include Unicode CJK Ideographs Extension-B
characters (UTF-16 surrogate pair (four bytes) characters).

OSGi support
--------------------
The OSGi bundles shipped with WebSphere MQ classes for JMS client are not
working.

JMS octal selectors
-----------------------------
A message selector can contain octal literals. Within WebSphere MQ classes for
JMS, octal selectors work only for simple checks for equality.

JMS national language support on Windows
---------------------------------------------------------------
There are problems for some languages writing to a Windows console in code page
850. The workaround is to ensure that the system properties console.encoding and
file.encoding are set to the same value before running Java applications.

Installation verification test program for JCA with WAS CE
----------------------------------------------------------
For the JCA IVT to work on WebSphere Application Server Community Edition
(WAS CE) there must be a connection factory with a name of "qcf" and a
queue with a message-destination-name of "jmstestQ" defined in the
geronimo-rar.xml when you deploy the RAR file.

For the wmq.jmsra.ivt.ear file to deploy on version 2.0.1 or later of WAS CE  
the following xml files within the EAR file have to be updated as below:

geronimo-application.xml
       <xmlns:nam="http://geronimo.apache.org/xml/ns/j2ee/openejb/openejb-jar-2.1.xsd">
             <dep:environment xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2">
 
openejb-jar.xml
       <openejb-jar xmlns="http://www.openejb.org/xml/ns/openejb-jar-2.2.xsd"
                         xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2"
                        xmlns:sec="http://geronimo.apache.org/xml/ns/security-2.0"
                        xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.2"
                        xmlns:pkgen="http://geronimo.apache.org/xml/ns/j2ee/openejb/openejb-pkgen-2.0.xsd">

Clustering of topics
----------------------------
Though clustering of topics is generally supported, do not cluster SYSTEM.BASE.TOPIC or
SYSTEM.DEFAULT.TOPIC. The CLUSTER parameter of these topics must be blank.

Topics in overlapping clusters
-------------------------------------------
If you define two or more topics, with one topic string being a more qualified version of the
other (for example SPORTS and SPORTS/FOOTBALL), with the topics in different but
overlapping clusters, publications can be delivered to unexpected recipient queue managers.
For example:
- Queue manager qmAB is in both clusters ClusterA and ClusterB
- SPORTS is a cluster topic in ClusterA
- SPORTS/FOOTBALL is a cluster topic in ClusterB
Subscribers to SPORTS/FOOTBALL on queue managers which are only in ClusterA also
receive publications from queue manager qmAB.

Similarly, if a cluster topic and a local topic share a name, unexpected publications can be
received.
For example:
- SPORTS is a cluster topic in ClusterA
- Queue manager qmC in ClusterA defines a topic SPORTS with no cluster
Subscribers for SPORTS on queue managers in ClusterA receive publications from qmC.

Selectors on z/OS
----------------------------------
Selectors are not supported for point to point messaging when connecting to a z/OS
queue manager.



+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

TRADEMARKS

The following terms are trademarks of International Business Machines
Corporation in the United States, other countries, or both:
     FFST SupportPac WebSphere z/OS  

Windows is a trademarks of Microsoft Corporation 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.

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




Supplementary information (Readadd)

Abstract
------------
This READADD (readme additions) file contains additions made between
translation of the README file (when it was frozen) and the
manufacturing of this media.

For the latest README additions (including the additions in this file)
access the online version of the readme file at:

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006097

In addition to this file READADD and the README.TXT file, you can find
more information on the WebSphere MQ Web site:

http://www.ibm.com/software/integration/wmq/

The SupportPac(TM) Web page is at:

http://www.ibm.com/software/integration/support/supportpacs/

For current information on known problems and available fixes, see the
Support page of the WebSphere MQ Web site at:

http://www.ibm.com/software/integration/wmq/support/

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

LIMITATIONS AND KNOWN PROBLEMS
------------------------------------------------------------

Installation on Windows on Itanium platform.
---------------------------------------------------------------
WebSphere MQ does not support Windows on the Itanium processor.
(See "WebSphere MQ Quick Beginnings for Windows".)
Do not attempt to install WebSphere MQ on Windows on Itanium.

Using WebSphere MQ with WAS V6.0.2 or 6.1 on HP-UX or Solaris 64-bit platforms
----------------------------------------------------------------------------
If you want to use WebSphere Application Server (WAS) V6.1 with WebSphere MQ
Version 7.0 as a messaging transport (for example, for Message Driven Beans) on
64-bit HP-UX or Solaris, there is a known problem concerning LIBRARY resolution.
To resolve this problem, update to the latest Service level of WAS V6.1 and apply
APAR PK58511 if that APAR is not already integrated into the level.
The same problem applies to WAS V6.0.2 and can similarly be fixed by application
of an APAR.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

TRADEMARKS

The following terms are trademarks of International Business Machines
Corporation in the United States, other countries, or both:
     SupportPac WebSphere

Itanium is a trademark of Intel Corporation in the United States and other countries.

Windows is a trademark of Microsoft Corporation in the United States, other
countries, or both.

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

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