IBM Mashup Center fixpack 1.0.0.1, readme file

© Copyright International Business Machines Corporation 2007, 2008. 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 on a stand-alone configuration

For information about how to obtain an IBM Mashup Center fixpack, see http://www-10.lotus.com/ldd/mashupswiki.nsf/dx/fixpacks

To install this fixpack:

  1. Verify that the WebSphere Application Server is shutdown.
    1. Open the Services list. For example, select Start > Control Panel > Administrative Tools > Services.
    2. Open the Service entry for IBM WebSphere Application Server V6.1 node-name.
    3. If the Service status is Started, click the Stop button and wait for the status to indicate that the server is Stopped.
  2. In the IBM Mashup Center root directory, create a directory named fixes if the fixes directory does not already exist.
  3. Move the mashupcenter1001.pak fixpack file to the IBM Mashup Center\fixes directory.
  4. Move the updatemashup.bat and updatemashup.xml files to the IBM Mashup Center root directory.
    Note: If you have a cluster configuration, you must run the updatemashup fixpack steps on each node separately
  5. Open a command prompt window. For example Start > Run > cmd
  6. In the command prompt window, change to the IBM Mashup Center root directory. For example: cd C:\Progs\IBM_MashupCenter
  7. In the command prompt window type updatemashup.bat MashupCenter1001, where MashupCenter1001 is the name of the fixpack file. The update runs automatically. See the example output below.
  8. Start the server. You can validate that the fixpack was installed successfully. by accessing the key features in both Lotus Mashups and IBM Mashup Hub.
Note: If you have a cluster configuration, you must:
  1. Stop each server and each node agent in the cluster
  2. Run the installation steps on each of the nodes separately
  3. In the future, if you need to add more nodes to the cluster, apply the fixpack to those nodes after synchronization

Example output:

In the following output, messages ADMU0509I and ADMU0211I are for your information only; they do not indicate a problem. Message ADMU0509I confirms that the WebSphere Application Server is not running, as required for the installation to proceed. Message ADMU0211I points to the file where installation details are logged.

C:\Program Files\IBM Mashup Center>updatemashup MashupCenter1001
Buildfile: updatemashup.xml

update:
     [echo] Root Directory is: C:/Program Files/IBM Mashup Center/mm
     [echo] Fix number is: MashupCenter1001
     [exec] ADMU0116I: Tool information is being logged in file C:\Program Files\IBM Mashup
     [exec]            Center\mm_profile\logs\server1\stopServer.log
     [exec] ADMU0128I: Starting tool with the mm_profile profile
     [exec] ADMU3100I: Reading configuration for server: server1
     [exec] ADMU0509I: The server "server1" cannot be reached. It appears to be stopped.
     [exec] ADMU0211I: Error details may be seen in the file: C:\Program Files\IBM Mashup
     [exec]            Center\mm_profile\logs\server1\stopServer.log
     [exec] Result: -10

     [copy] Copying 62 files to C:\Program Files\IBM Mashup Center\fixes\backup\MashupCenter1001\Config
     [copy] Copying 2636 files to C:\Program Files\IBM Mashup Center\fixes\backup\MashupCenter1001\mm
     [copy] Copying 4455 files to C:\Program Files\IBM Mashup Center\fixes\backup\MashupCenter1001\Hub
     [copy] Copied 736 empty directories to 1 empty directory under C:\Program Files\IBM Mashup Center
              \fixes\backup\MashupCenter1001\Hub
    [unzip] Expanding: C:\Program Files\IBM Mashup Center\fixes\MashupCenter1001.pak into 
              C:\Program Files\IBM Mashup Center\fixes\MashupCenter1 
pre-update:
    [unzip] Expanding: C:\Program Files\IBM Mashup Center\fixes\MashupCenter1001.pak into 
              C:\Program Files\IBM Mashup Center\fixes\MashupCenter1
    [unzip] Expanding: C:\Program Files\IBM Mashup Center\fixes\MashupCenter1001.pak into 
              C:\Program Files\IBM Mashup Center
    [unzip] Expanding: C:\Program Files\IBM Mashup Center\fixes\MashupCenter1001.pak into 
              C:\Program Files\IBM Mashup Center\fixes\MashupCenter1
    [unzip] Expanding: C:\Program Files\IBM Mashup Center\fixes\MashupCenter1001.pak into 
              C:\Program Files\IBM Mashup Center\fixes\MashupCenter1
   [delete] Deleting 1 files from C:\Program Files\IBM Mashup Center\mm_profile\configuration\org.eclipse.core.runtime
   [delete] Deleting 25 files from C:\Program Files\IBM Mashup Center\mm_profile\configuration\org.eclipse.osgi
   [delete] Deleting 3 files from C:\Program Files\IBM Mashup Center\mm_profile\configuration\org.eclipse.update
    [unzip] Expanding: C:\Program Files\IBM Mashup Center\fixes\MashupCenter1001\mashuphub-update.zip into 
              C:\Program Files\IBM Mashup Center\HuMashup Hub.ear

post-update:
     [copy] Copying 3 files to C:\Program Files\IBM Mashup Center\fixes\backup\MashupCenter1001\configuration
    [unjar] Expanding: C:\Program Files\IBM Mashup Center\mm\eclipse\plugins\com.ibm.mm.framework.proxy_1.0.0.jar 
              into C:\Program Files\IBM Mashbackup\MashupCenter1001\proxyconfig
   [delete] Deleting 1693 files from C:\Program Files\IBM Mashup Center\mm\eclipse\plugins
   [delete] Deleted 348 directories from C:\Program Files\IBM Mashup Center\mm\eclipse\plugins
    [unzip] Expanding: C:\Program Files\IBM Mashup Center\fixes\MashupCenter1001\mashupWAS61.zip into 
              C:\Program Files\IBM Mashup Center\mm
     [move] Moving 1684 files to C:\Program Files\IBM Mashup Center\mm
     [copy] Copying 3 files to C:\Program Files\IBM Mashup Center\mm\eclipse\configuration
      [jar] Updating jar: C:\Program Files\IBM Mashup Center\mm\eclipse\plugins\com.ibm.mm.framework.proxy_1.0.0.jar
   [delete] Deleting 1 files from C:\Program Files\IBM Mashup Center\mm_profile\configuration\org.eclipse.core.runtime
   [delete] Deleting 6 files from C:\Program Files\IBM Mashup Center\mm_profile\configuration\org.eclipse.osgi
   [delete] Deleting 3 files from C:\Program Files\IBM Mashup Center\mm_profile\configuration\org.eclipse.update

BUILD SUCCESSFUL
Total time: 1 minute 58 seconds

General - Known issues, resolved problems, and workarounds in this fixpack

The following sections contain information about the known issues, problems that have been resolved, and workarounds that apply to all of Mashup Center.

Migration

When you are migrating the catalog to another database, there is currently no way to prevent a user from creating or running objects in the catalog

Status: Known Issue

There is no mechanism to block a user from creating or running objects in the catalog when migration is in process.
Tip: Schedule the migration of the catalog to a time when no one will be using the product.

Configuration

Cluster configuration now supported for Mashup Center

Status: New capability

IBM Mashup Center now supports a cluster server configuration. For detailed information on setting up a cluster configuation for Mashup Center, see the Cluster server configuration for Mashup Center article on the Mashup Center wiki.

Caching data in a cluster configuration might return data that is out of date

Status: Known Issue

For example, You create a feed mashup with a cache interval of 1 hour. The feed mashup is run at 6:00am. The request to run the feed mashup is processed by node A in the cluster. The data from the feed mashup is cached on node A and the 1 hour cache interval begins. Less than a hour later, at 6:25am, another request to run the feed mashup is processed by node B. The data from the feed mashup is cached on node B and the 1 hour cache interval begins.

  • If a request to run the feed mashup comes in after 6:25am and is processed by node A, the data that is returned to the user is out of date. The data on node B is more current.
  • If a request the run the feed mashup comes in after the cache on node A has been refreshed (at 7:00am) and the request is processed by node B before the cache on node B is refreshed (at 7:25am), the data that is returned to the user is out of date. The data on node A is more current.

Widget WAR deployment fails in a cluster

Status: Resolved

This issue has been fixed. After you apply this fixpack, you will need to update the cluster name by adding the following line to the mm/eclipse/configuration/config.properties file:
com.ibm.mashups.cluster=xx
where xx is the target cluster name.

When you create a feed from a TDI source, the TDI server is started on the node where the feed is created

Status: Known Issue

As additional feeds are created from TDI sources, the TDI server will be started on each node where the request to create the feed originates. However, there is no central mechanism to start or stop all of the TDI servers together. The MashupHub Administrator will need to start or stop the TDI server on each node separately.

When you publish pages from Mashups to Hub in cluster setup you get 500 error and page does not get published

Status: Known Issue

In Mashup Center cluster setup there is a known issue on publishing pages to Hub. You can get around this problem by opening Mashup Hub interface using 'Goto Catalog' option from Mashups action menu. Once the Hub interface is opened in another browser tab and when you go back to Mashups interface to publish pages, that should work without any errors.

InfoSphere MashupHub - Known issues, resolved problems, and workarounds in this fixpack

The following sections contain information about the known issues, problems that have been resolved, and workarounds in InfoSphere MashupHub that are in this fixpack.

Security

If the data from a private feed is cached, other users might be able to access the data

Status: Resolved

When data from a private feed is cached, other users can no longer access the data. An error is returned when an attempt to access a private feed is made by other users.

Running a pubic feed mashup might not return data if the feed mashup contains a private feed source

Status: Resolved

If you create a public feed mashup with a source feed that is private, and you are also the creator of the private feed, the data from the private feed should be returned. Instead, the data from the private feed is not returned. This issue has been resolved. The data from the private feed is now returned.

Administration

The MashupHub version does not get logged in the javamashuphub.log file

Status: Resolved

The MashupHub log file, javamashuphub.log, now contains version information, including the service level, for example: 
InfoSphere MashupHub: v1.0.0.1 10220
The version is also displayed in the version.txt file, for example: 
IBM Mashup Center=1.0.0.1

When an Administrator attempts to add a user with a userid that includes an @ symbol to the restricted user list, the user is not added and no error message is returned.

Status: Resolved

The number of results displayed for tracked data is limited and might return corrupted data

Status: Resolved

Catalog

If a feed or feed mashup is being edited when the catalog server is restarted, the feed or feed mashup will not appear when you list the contents of the catalog or search the catalog

Status: Known Issue

If the owner of a feed or feed mashup is editing a feed or feedmashup when the MashupHub database server is restarted, the feed or feed mashup does not appear when you list the contents of the catalog or search the catalog.

Feeds

Creating a feed from a DB2 XML column (pureXML) source results in all of the element tags being escaped

Status: Resolved

The default behavior of the feed generator for relational databases is now changed so that the XML element tags are not escaped from a DB2 XML column. If you want the old behavior, use the DB2 XMLSerialize or XMLCast function to cast the column to a String data type.

Feed Mashups

Saving a feed mashup that has empty or incomplete parameters will result in an error when you attempt to view or run the saved feed mashup

Status: Resolved

You are no longer able to save a feed mashup that has empty or incomplete parameters.

Using functions in the Filter operator might return a compile error

Status: Resolved

This issue and a workaround were documented in the Version 1.0 Release Notes. This issue has now been resolved.

When a feed mashup is saved, the tab name might appear blank

Status: Resolved

A feed mashup is automatically saved when the browser is refreshed

Status: Resolved

The feed mashup should be saved only when you specify that the feed mashup should be saved.

Lotus Mashups - Resolved problems and workarounds in this fixpack

The following sections contain information about the known issues, problems that have been resolved, and workarounds in Lotus Mashups that are in this fixpack.

Pages

When switching a page or refreshing the current page fragment, you might see an error

Status: Resolved

The following error might appear:
BMWMB0052E: Error happens while invoking serviceManager.getService publishEvent. 
Error details: statusDiv has no properties

This happens because the DOJO resource is not released promptly when the widget is unloaded from the page. This issue has been resolved.

When you e-mail a page URL or publish a page as a URL to a second group of users, the second group of users might not be able to access the URL page directly

Status: Resolved

If the second group of users log onto the page by clicking the URL and authenticate with the server, the second group of users will not be able to access to the URL page directly. Instead the users will access to the first page in their navigation.

As a workaround, you can either publish pages as a URL to MashupHub or replace '#' with '?' when you send the URL in an e-mail. For example, the browser location in the e-mail should change from http://your_ip:port/mum/enabler#pid=100 to http://your_ip:port/mum/enabler?pid=100. This allows users who do not log in to access the page after authentication.

Published pages have the wrong owner

Status: Resolved

URL normalization fixes in the proxy recognize semantically identical URLs even though they differ syntactically (normalizing URLs). This fixpack solves this by allowing you to configure the proxy-config.xml file to forward session and LTPA cookies to MashupHub or to a selected URL.

Users can update page content without having edit access

Status: Resolved

The fragment feed now runs an explicit access verification before updating the page content.

Widgets

You cannot add widgets to a page in the free-form layout

Status: Resolved

This limitation occurs because the height of pages in the free-form layout is fixed. This fixpack allows free-form pages to expand vertically so that you can add as many widgets as you want to.

This limitation occurs because the height of pages in the free-form layout is fixed, and the space is limited. This fixpack allows free-form pages to expand vertically when you drag a widget to the page, which enables you to add as many widgets as you want to.

Skin preview images do not display after updating the layout widget's properties

Status: Resolved

When you add custom theme WAR files, each theme might contain skins. When you set a default skin for the layout widget in properties, the skin preview images do not display. This issue has been resolved.