IBM Mashup Center fixpack 1.1.0.1, readme file

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

Contents

Installing this fixpack

Prerequisite: If you have IBM Mashup Center, version 1.0 or version 1.0.0.1, you must install the IBM Mashup Center 1.1 upgrade. A link to the installation files and the download instructions for the fixpacks for the IBM Mashup Center 1.1 upgrade are available at: http://www-10.lotus.com/ldd/mashupswiki.nsf/dx/fixpacks.

This fixpack consists of the following files:

Cluster configurations

If you have a cluster configuration, you must run the fixpack installation steps on each node separately.

  1. Stop each server and each node agent in the cluster.
  2. Run the fixpack installation steps on each node.
  3. Start each node agent and each server in the cluster.

If you add more nodes to the cluster, apply the fixpack to the new nodes after synchronization.

Installing on Windows

  1. Verify that the WebSphere® Application Server is shut down:
    1. Open the Services list. Select Start > Control Panel > Administrative Tools > Services.
    2. Open the Service entry for IBM WebSphere Application Server V6.1, or for a cluster node, IBM WebSphere Application Server V6.1node_name.
    3. If the Service status is Started, click Stop and wait for the Status to indicate that the server is Stopped.
  2. Set up directories for the fixpack files:
    1. In the IBM Mashup Center root directory, create a directory named fixes if the fixes directory does not already exist.
    2. Copy the mashupcenter1101.pak file to the IBM Mashup Center\fixes directory.
    3. Copy the updatemashup.bat and updatemashup.xml files to the IBM Mashup Center root directory.

      The directories will have the following structure:

      IBM Mashup Center\updatemashup.bat
IBM Mashup Center\updatemashup.xml
IBM Mashup Center\fixes\mashupcenter1101.pak
  3. Run the fixpack upgrade:
    1. Open a command prompt window. For example, Start > Run > cmd.
    2. Change to the IBM Mashup Center root directory. For example: cd C:\Progs\IBM_MashupCenter
    3. Type updatemashup.bat MashupCenter1101

The update runs automatically.

Installing on Linux

  1. Shut down the WebSphere Application Server by running the stopServer command: 
    IBM Mashup Center/AppServer/bin/stopServer.sh server1
  2. Set up directories for the fixpack files:
    1. In the IBM Mashup Center root directory, create a directory named fixes if the fixes directory does not already exist.
    2. Copy the mashupcenter1101.pak file to the IBM Mashup Center/fixes directory.
    3. Copy the updatemashup.sh and updatemashup.xml files to the IBM Mashup Center root directory.

      The directories and files will have the following structure:

      IBM Mashup Center/updatemashup.sh
IBM Mashup Center/updatemashup.xml
IBM Mashup Center/fixes/mashupcenter1101.pak
  3. Run the fixpack upgrade:
    1. Change to the IBM Mashup Center root directory.
    2. Type updatemashup.sh MashupCenter1101

The update runs automatically.

New features

The IBM InfoSphere™ MashupHub Feed Control Module provides support for feed policy definition, monitoring, and enforcement

The Feed Control Module is an optional component available as a separate download. Licensees of IBM Mashup Center 1.1 are entitled to download the Feed Control Module. You must first apply fixpack 1.1.0.1. The Feed Control Module runs as a separate virtual machine either on the same server where InfoSphere MashupHub is installed or on a separate server. The Feed Control Module provides support for feed policy definition, monitoring, and enforcement for the following policies:

For more information and for download and installation instructions for the Feed Control Module, see the following article on the IBM Mashup Center wiki:

Feed Control Module overview and configuration.

Security features and enhancements for the AJAX proxy

This fixpack includes new security features and enhancements for the AJAX proxy. For details, see New security features and extensions for the AJAX Proxy.

Known issues

InfoSphere MashupHub

The following section contains information about the known issues specific to MashupHub, v1.1.0.1

Table 1. InfoSphere MashupHub known issues
Bug number Problem description
4558

Import/Export issue - importing a public feed belonging to another user ends up having custom privileges in the view details page.

Workaround: Log in as the administrator and change the permission to the desired level.
4577 Editing a Tivoli® Directory Integrator (TDI) feed shows the encrypted password instead of the original password entered during feed creation.
4583 Upgrade to 1.1 fails if non-system/custom plugins have been installed.
4599

Clearing tracked data fails after migrating Oracle

After migrating the catalog database to Oracle, the Clear Tracking Information action does not delete tracked data. Be aware that enabling tracked data can use excessive disk space on these databases. Instead of tracking all cataloged objects, you can turn tracking on for selected feeds that are very important and require tracking so as to reduce tracking entries and save disk space.

This bug has been fixed for IDS and for Microsoft® SQL Server.
4719

Migration to an Oracle database can fail if any of the MashupHub object descriptions are longer than 255 characters and tracking is enabled.

Workaround: Delete the objects with descriptions longer than 255 characters and recreate them with descriptions with fewer than 255 characters before migrating to Oracle.
4724

Migration to another database can fail if MashupHub was previously upgraded from version 1.0 to version 1.1 and any of the MashupHub object descriptions are longer than 255 characters and tracking is enabled.

For example, if you have MashupHub version 1.0.0.1 with tracking turned on and you upgraded to version 1.1, migration to any database can fail if object descriptions are longer than 255 characters.

Workaround: Delete the objects with descriptions longer than 255 characters and recreate them with descriptions with fewer than 255 characters before migration.
4736 Feed Control Module: For a Global filter, using the dollar sign ($) in a Replace string throws an error.
4751 Feed Control Module: In Windows – The Feed Control Module deployment might fail if it is installed in default path with spaces
4764

Feed Control Module: After MashupHub is configured with the Feed Control Module, the Customer List Demo widget from Lotus® Mashups does not load.

Go to settings and enter the URL as in the View Feed link of Veterinary Clients feed and save.
4783

Feed Control Module: In a clustered environment, if MashupHub is configured with the Feed Control Module, it is possible to bypass the rate limiting of pages by using the MashupHub URL instead of the Feed Control Module URL.
4787

Feed Control Module: In a clustered environment, if MashupHub is configured with the Feed Control Module, it is possible that feeds, feed mashups, and widgets can be accessed directly using the original cluster URL instead of using the Feed Control Module URL.

If this problem occurs, you can correct the filtering by copying the MashupHub's web.xml file from the primary node to the Deployment Manager (DM) config directory, and then performing a full synchronization as described in the following steps:

  1. On one of the nodes where fixpack 1.1.0.1 has been applied, locate the web.xml file in the deployment directory. For example:

    On Windows:

    <install-dir>\Hub\installedApps\MashupHub.ear\mashuphub-enterprise.war\WEB-INF

    On Linux:

    <install-dir>/Hub/installedApps/MashupHub.ear/mashuphub-enterprise.war/WEB-INF
  2. Locate the directory where the copy of the web.xml file resides on the Deployment Manager. For example:
    <install-dir>/WebSphere/AppServer/profiles/Dmgr01/config/cells/<DMNodeCell>/applications/MashupHub.ear/deployments/Mashup
Hub/mashuphub-enterprise.war/WEB-INF
  3. Copy the web.xml file from the node's directory to the Deployment Manager's directory.
  4. In the WAS Admin console on the Deployment Manager, select System Administration > Nodes in the console navigation tree to access the Nodes page.
  5. Select the primary and secondary nodes of the cluster.
  6. Click Full Resynchronize for the updated web.xml file to be applied to the nodes.

Lotus Mashups

The following section contains information about the known issues specific to Lotus Mashups, v1.1.0.1

Table 2. Lotus Mashups known issues
Bug number Problem description
3840

Issue: After applying fixpack 1.1.0.1, you might experience the following issues:

  • Not being able to log in to Lotus Mashups unless you specify a port number in the URL.
  • Widgets not working correctly.
  • In a clustered environment, not being able to access mashups through the HTTP server. For example, accessing mashups using http://WebServer/mum/enabler.

Solution: To fix this problem, delete and re-create the Web server in the WAS console. Use the DM WAS console for a clustered environment:

  1. Log in to the WAS console.
  2. Go to Servers > Web servers.
  3. Select the current Web server and click Stop.

    The Status column will indicate that the Web server is stopped.

  4. Select the Web server, and then click Delete.
  5. Click New to create a new Web server.
  6. Select the node, specify the Web server name, and select its Type.
  7. Click Next.
  8. Enter the Web server installation location, plug-in installation location, Username, and Password.
  9. Click Next.
  10. Confirm the creation of the new Web server, and then click Finish.
 4172

 Issue: The following issue occurs after installing the IBM Mashup Center V1.1.0.1 fixpack in a clustered environment.

After uploading a widget WAR file into the catalog and then adding it to Lotus Mashups, you may notice either of the following issues:

  • The widget does not appear in the toolbox, even after refreshing the page.
  • The widget appears in the toolbox, but when you drag it onto a mashup page, a message displays saying that the widget is unavailable.

Next, if you go to Applications > Enterprise Applications in the WAS administrative console, you may notice that the widget is in a Partially Started state.

Solution: To solve this issue, do either of the following actions:

  • In the Enterprise Applications window, stop and then start the application.
  • Restart the server

Bugs fixed

InfoSphere MashupHub

The following section contains information about bugs fixed in MashupHub, v1.1.0.1

Table 3. Bugs fixed in MashupHub, v1.1.0.1
Bug number Problem description
4344 Adding a long comment for a MashupHub object does not work
4541 Sharepoint Web Services does not work in MashupHub
4595 URL with parameters having encoded XML string values fail to load in the Source operator
4599

Clearing tracked data fails after migrating IDS or to Microsoft SQL Server

After migrating the catalog database to IDS or to Microsoft SQL Server, the Clear Tracking Information action does not delete tracked data. Be aware that enabling tracked data can use excessive disk space on these databases. Instead of tracking all cataloged objects, you can turn tracking on for selected feeds that are very important and require tracking so as to reduce tracking entries and save disk space.

This bug is still present for Oracle.
4619

Tracking data requires edit to mmms.config.ini file to enable cache after upgrading

If you have usage tracking enabled or plan to enable it, edit the mmms.config.ini file to enable the caching of the tracked data after you upgrade to MashupHub, V1.1. Caching tracked data improves MashupHub performance.
4622 The cache region used by Tracking is same as that for the Feeds since in a default install the mmm.config.ini setting points to mmms.cache.region=feedRegion.
4648

Microsoft SQL Server does not directly support UTF-8 encoding

Double-byte characters in the feeds details will not be rendered properly.
4658 Mashup Feed Caching, reducing the cache interval for a feed in the Source operator does not have any effect
4692 Feed Creation does not use HTTP proxy settings during initialization

Lotus Mashups

The following section contains information about bugs fixed in Lotus Mashups, v1.1.0.1.

Table 4. Bugs fixed in MashupHub, v1.1.0.1
Bug number Problem description
4425

Auto-wiring fails when dropping a widget onto another widget

After dragging a widget from the Lotus Mashups toolbox and then dropping it onto a widget on a mashup page, the auto-wiring fails to launch. For example, after dragging an HTML Markup widget from the toolbox, and dropping it on the Data Viewer widget, the auto-wiring does not launch and an error occurs.

This issue is now fixed in the V1.1.0.1 fixpack.