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

Prerequisite: You must install IBM Mashup Center, version 2.0 before you install fix pack 2.0.0.1.

This fix pack consists of the following files:

• updatemashup.bat (Windows®)
• updatemashup.sh (Linux®)
• updatemashup.xml
• MashupCenter2001.pak
• fixpack2001_readme.html (this file)

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 V7.0 - node_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 the directories for the fix pack files:
   1. Copy the updatemashup.bat and updatemashup.xml files to the mashupcenterhome directory, where mashupcenterhome is the Mashup Center root directory. For example: C:\Program Files\IBM\Mashup Center\2.0.
   2. Copy the MashupCenter2001.pak file to the mashupcenterhome\fixes directory.

      The directories will have the following structure:

      mashupcenterhome\updatemashup.bat
      mashupcenterhome\updatemashup.xml
      mashupcenterhome\fixes\MashupCenter2001.pak

3. Run the fix pack upgrade:
   1. Open a command prompt window.
   2. Change to the mashupcenterhome directory.
   3. Type updatemashup.bat MashupCenter2001

      The update runs automatically.

4. Start the WebSphere Application Server server. See step 1.

   You can verify that the fix pack is installed successfully by accessing the features of MashupHub and the mashup builder.

Installing on Linux

1. Shut down the WebSphere Application Server by running the stopServer command:

   mashupcenterhome/AppServer/bin/stopServer.sh server1

   Where mashupcenterhome is the Mashup Center root directory. For example, /opt/ibm/MashupCenter/2.0 and server1 is the name of the Mashup Center server.

   If you do not provide a -username and -password, a dialog box appears that prompts you for the username and password.

2. Set up the directories for the fix pack files:
   1. Copy the updatemashup.sh and updatemashup.xml files to the mashupcenterhome directory.
   2. If the updatemashup.sh file does not have execute permission, run this command: chmod 755 updatemashup.sh
   3. Copy the MashupCenter2001.pak file to the mashupcenterhome/fixes directory.

      The directories and files will have the following structure:

      mashupcenterhome/updatemashup.sh
      mashupcenterhome/updatemashup.xml
      mashupcenterhome/fixes/MashupCenter2001.pak

3. Run the fix pack upgrade:
   1. Change to the mashupcenterhome directory.
   2. Type updatemashup.sh MashupCenter2001

      The update runs automatically.

4. Start the WebSphere Application Server by running the startServer command:

   mashupcenterhome/AppServer/bin/startServer.sh server1

   You can verify that the fix pack is installed successfully by accessing the features of MashupHub and the mashup builder.

If you have a cluster configuration, you must install the fix pack on each node separately.

Prerequisite: Before you install the Mashup Center 2.0.0.1 fix pack, be sure that you have installed Mashup Center 2.0 and that you have configured a clustered server environment. For details, see Configuring a clustered server environment.

Do the following steps:

1. In the Deployment Manager administrative console, stop the cluster, and also stop all the node agents.
2. Do the following steps to apply the fix pack on each custom node:
   1. For non-primary nodes, do these steps:
      1. In your Mashup Center installation directory, edit Config/config.properties, uncomment the properties, and set the correct values for SERVER_NAME and CLUSTER_NAME. For SERVER_NAME, add this property to the Config/config.properties, if it does not exist. The value for the SERVER_NAME property is the name of the WebSphere Application Server server (the default value is server1). The value for the CLUSTER_NAME property is the cluster name in the Deployment Manager administrative console.
      2. Change to the MashupHome directory, and run updatemashup.bat MashupCenter2001 for Windows or ./updatemashup.sh MashupCenter2001 for Linux. Be sure the file access privilege of updatemashup.sh is 755 so that it is executable. If it is not executable, run chmod 755 updatemashup.sh.
   2. For primary nodes, do these steps:
      1. In your Mashup Center installation directory, edit Config/config.properties, uncomment the properties, and set the correct values for SERVER_NAME and CLUSTER_NAME. For SERVER_NAME, add this property to the Config/config.properties, if it does not exist. The value for the SERVER_NAME property is the name of the WebSphere Application Server server (the default value is server1). The value for the CLUSTER_NAME property is the cluster name in the Deployment Manager administrative console. Also, set values for these properties:
         • DeploymentManagerHostname=
         • DeploymentManagerConnectorPort=
         • DeploymentManagerAdminuser=
         • DeploymentManagerAdminpass=
      2. Locate mm/config/ConfigService.properties, uncomment and set the correct value for the com.ibm.mashups.cluster property.
      3. Change to the MashupHome directory, and run updatemashup.bat MashupCenter2001 for Windows or ./updatemashup.sh MashupCenter2001 for Linux. Be sure the file access privilege of updatemashup.sh is 755 so that it is executable. If it is not executable, run chmod 755 updatemashup.sh.
      4. Change to the Config directory of your Mashup Center installation root, and run ./config.sh update-was-config for Linux or ./config.bat update-was-config for Windows.
3. Do the following steps to redeploy all applications on the Deployment Manager node:
   1. Stop the Deployment Manager server on the Deployment Manager node.
   2. Locate and extract \fixes\MashupCenter2001.pak\Config\mm.admincommand.jar from fixpack.zip, and copy it under WAS_installation_root/lib. Also, extract the fixes\MashupCenter2001.pak\mashupsWAS7.zip\mm_ear directory to WAS_installation_root/mm. Now, you should have the following layout:
      • WAS_installation_root/lib/mm.admincommand.jar
      • WAS_installation_root/mm/mm_ear/*.ear
   3. Start the Deployment Manager server on the Deployment Manager node.
   4. Go to Dmgr_Profile/bin, and run wsadmin.sh for Linux or wsadmin.bat for Windows. Run the following command in your wsadmin environment. Change the values for the parameters earDirectoryName and clusterName properties according to your environment:

      $AdminTask deployMashupsEAR {-clusterName clustet01 
      -earDirectoryName "WAS_installation_root/mm/mm_ear"}
      $AdminConfig save

4. Start the node agents and the cluster.
5. Do the following steps if the IBM HTTP Server is configured with Mashup Center:
   1. In the WebSphere Application Server Deployment Manager administrative console, delete the existing Web server and create a new one.
   2. If the IBM HTTP Server and the WebSphere Application Server Deployment Manager node are not installed on the same machine, copy the plugin-config file from the WebSphere Application Server Deployment Manager node to the IBM HTTP Server node. If they are installed on the same machine, skip this step.

The following section contains information about known issues in Mashup Center, v2.0.0.1

The following section contains information about bugs that have been fixed in Mashup Center, v2.0.0.1

• Spaces that are not designated as favorites show up in Favorites view

  In the space manager, if you navigate to the Favorite Spaces list, you can click Create space to create a non-favorite space. This new space unexpectedly displays in the Favorites view, but then if you refresh the page, the space is removed from the Favorites view.

• HTML Markup widget does not work properly with Tabbed View widget

  When using the HTML Markup and Tabbed View widgets together, sometimes you may notice that the contents of the HTML Markup widget remain on the page, even after switching to a different tab. This issue is now resolved with this fix pack.

• Content in non-trusted widgets gets lost after saving pages

  After configuring a non-trusted widget and saving the edits, if you refresh the page or navigate back to this page later, the saved settings are lost. This issue is now resolved, and the content does not get lost.

• Anonymous users cannot accept shared pages

  After sharing a page with an anonymous user, when the anonymous user opens the mashup builder and attempts to accept the page and add it to the page navigation, the page does not display in the list of shared pages. This issue is now resolved, and users can now accept shared pages.

• Page settings get lost when importing spaces

  When working with a space, you can add pages to that space. You can set also set a hierarchy for those pages in the page navigation so that some pages are nested below other pages. If you export or publish that space to the catalog and then re-import the space later, you may find that only the top-level page keeps its original settings, for example background and border. Settings for pages that fall beneath that page in the hierarchy are lost.

  Now, with this fix pack, all pages in spaces keep the settings that you configured before exporting or publishing the space.

• Menu is incorrect in Nested Data Viewer widget

  After configuring the Nested Data Viewer widget with a data source and then clicking the Table Content tab, if you right-click inside a column in the table, the menu that displays is the browser's default contextual menu, not a menu that provides options for the table columns. With this fix pack, the menu is now correct.

• Data unexpectedly stops displaying in non-trusted Data Viewer widget after reloading page

  After marking a Data Viewer widget as non-trusted, dragging it to a page, and then wiring it to a Feed Reader widget, the data from the feed displays properly in the Data Viewer widget. However, after reloading the page, the data suddenly stops displaying, even though the wire is still connected.

  This issue is now fixed.

• Language changes unexpectedly after exporting and then re-importing pages

  After exporting a page, and then re-importing the page back into Mashup Center, sometimes the language used in the page suddenly changes. This is because the title locales are not exporting properly. This issue is now fixed.

• Cancel button in Import Page dialog box displays awkwardly

  When importing a page into a space, you may notice that the Cancel button displays in a different style that other Cancel buttons in Mashup Center. With this fix pack, the Cancel button displays normally.

• Pages in spaces are not saved before changing space owner

  When working with a page in a space, after you make a change to the page, for example drag a widget onto the page, if you change the space owner before saving the page, when the new owner access the page, the changes made by the original owner are lost.

  Now, with this fix pack, in the scenario described above, edits are automatically saved before the space owner gets changed.

• Home spaces that have been hidden and then re-hidden do not display in space selector

  When using Mashup Center 2.0, after hiding a space in the space manager, setting the space as a home space, and then reshowing the space in the list, the space may not be listed in the space selector, as expected. This issue has been fixed in this fix pack.

• Hidden spaces are not obvious in the space manager

  When using Mashup Center 2.0, after hiding spaces in the space manager, sometimes the visual indicator that tells you that the space is hidden does not display. This issue has been fixed in this fix pack.

• Page owner is wrong

  After changing a page owner to a different user, when you attempt to change the page owner a second time, the first owner remains the page owner. This issue is now fixed.

• Partial searches do not find users correctly

  In Mashup Center 2.0, when you search for users using a partial name, the results do not display the users that meet that search criteria. In other words, if you type a in the search field and start the search, no results are found, even those users who have names that start with that character.

  This issue is now fixed.

• Anonymous users erroneously have rights to edit shared pages and spaces

  In Mashup Center 2.0, when sharing pages or spaces with anonymous users, you can provide anonymous users with edit rights. However, anonymous users should only have view rights. This issue has now been fixed.

• Error displays after editing the number of columns on page

  When working with a page in which the Customer List and Data Editor widgets are wired together, if you are using a column theme and attempt to edit the number of columns on the page, you may experience a system message error.

  This issue is now fixed.

• Page background disappears after changing style when using the Tab Menu theme

  When using the Tab Menu theme, if you click Customize > Change Style, and then select a color scheme, suddenly the main background of the page disappears and is replaced by a white screen.

  This issue has now been fixed.

• Browser memory leak when opening dialog boxes using Internet Explorer

  When using Internet Explorer, when you open and close various dialog boxes in the mashup builder, you may notice a memory leak in your browser, sometimes as high as 5M for each open-and-close action.

  Currently, the memory leak occurs in the following scenarios:

  • In the palette, open the main actions menu and select Open Catalog in a Dialog Box. Let the catalog load completely, and then close the catalog. After you close the dialog box, you may experience close to 5M of memory leak.
  • Drag a widget onto a mashup page, click the configuration icon at the top of the widget, and select Edit Settings. After you close the configuration dialog box, you may experience close to 1M of memory leak.
  • In the widget builder, when you create a new project using starter files, you can select either Edit file to edit an existing starter file or Create a new file to add a new file to the project. After you close either dialog box, you may experience close to 5M of memory leak.

  You may also notice memory-leak errors when working with pages continuously for long periods of time.

  This issue has been fixed with this fix pack.

• Misleading error in SystemErr.log when adding widgets to mashup builder

  After adding either lightweight widgets or widget WAR packages to the mashup builder from the catalog, you may notice errors in SystemErr.log, even though the widgets were added successfully. For example, you may see this error when adding a widget WAR package:

  [4/9/09 12:01:27:625 CST] 0000001b SystemErr 
  R com.ibm.mm.widgets.deployment.DeployException: 
  BMWWC0023I: The request to install widgets needs to 
  include a WAR file since there there is not a WAR 
  file already installed.
  [4/9/09 12:01:27:625 CST] 0000001b SystemErr 
  R     at com.ibm.mm.was.core.internal.deployer.WASDeployer.shouldDeployWar
  (WASDeployer.java:293)
  [4/9/09 12:01:27:625 CST] 0000001b SystemErr     R 
  at com.ibm.mm.was.core.internal.deployer.WASDeployer.deployWidget
  (WASDeployer.java:132)
  [4/9/09 12:01:27:625 CST] 0000001b SystemErr     R
  at com.ibm.mm.widgets.internal.deployment.DeploymentRequest.doDeployment
  (DeploymentRequest.java:358)
  [4/9/09 12:01:27:625 CST] 0000001b SystemErr     R
  at com.ibm.mm.widgets.internal.deployment.DeploymentDataSinkFactory$1$1.write
  (DeploymentDataSinkFactory.java:108)
  [4/9/09 12:01:27:625 CST] 0000001b SystemErr     R
  at com.ibm.portal.resolver.helper.ByteCharDataSource.write
  (ByteCharDataSource.java:139)

  And here is an example of an error you may see when adding a lightweight widget:

  [10/30/09 14:29:16:960 CST] 0000003b SystemErr     R
  com.ibm.mm.widgets.deployment.DeployException: BMWWC0023I: 
  The request to install widgets needs to include a ZIP file since there 
  there is not a ZIP file already installed.
  [10/30/09 14:29:16:960 CST] 0000003b SystemErr     R
  at com.ibm.mm.framework.lightweight.deploy.Deployer.deployWidget
  (Deployer.java:59)
  [10/30/09 14:29:16:960 CST] 0000003b SystemErr     R
  at com.ibm.mm.widgets.internal.deployment.DeploymentRequest.doDeployment
  (DeploymentRequest.java:358)
  [10/30/09 14:29:16:960 CST] 0000003b SystemErr     R
  at com.ibm.mm.widgets.internal.deployment.DeploymentDataSinkFactory$1$1.write
  (DeploymentDataSinkFactory.java:108)
  [10/30/09 14:29:16:961 CST] 0000003b SystemErr     R
  at com.ibm.wps.resolver.data.ByteCharDataSource.write
  (ByteCharDataSource.java:242)
  [10/30/09 14:29:16:961 CST] 0000003b SystemErr     R
  at com.ibm.wps.resolver.servlet.ContentHandlerDownload.handleDownload
  (ContentHandlerDownload.java:1272)

• User experiences a 404 error message in pages contained within imported spaces

  When you import spaces, the widgets that are contained in the pages within those spaces must be installed and enabled on the server in order to function properly. If the widgets are not available, a 404 error message displays inside the page. To correct this problem, administrators should check the following possible issues:

  • The server is unavailable.
  • The server is available, but the widgets are not installed.
  • The user does not have permission to view the page.

  With this fix pack, a friendlier message now displays to help you solve this issue.

• Save button becomes disabled, and XML files completely disappear from widget builder project

  When using the widget builder, after creating a widget project, and then editing an XML file multiple times, sometimes the Save button becomes disabled, and the XML file completely disappears from the file list in the widget builder.

  This issue is now fixed.

• Pages do not load properly in clustered server environment

  When working in a clustered server environment, you may notice that pages do not load properly because they fail to retrieve the default page theme.

  This issue is now fixed.

• Anonymous URLs can now be used to address a target page, for example :/mum/mashups?nst=pid%3D%26' class='inlinelink' target="_blank">http://<host>:<port>/mum/mashups?nst=pid%3D<pid>%26, where <host> is your host, <port> is the port, and <pid> is the unique page ID.
• The Chart widget cannot consume XML data with a namespace prefix in the tag, for example <a><ns:b>abc</ns:b></a>.
• Events do not get sent multiple times across pages.
• General Config Settings: After updating HTTP and HTTPS ports via the General Config Settings, the information for the <importServiceURL> for spaces is incorrect.
• Add diagnostic tracing to "Add to mashup Builder".
• Tracking status (checked/unchecked) is not cached on each page.
• Resolve dependency/catalog federation issues involving URLs without ports and case-insensitive hostname comparisons.
• [WSDL SOAP Preview] Incorrect SOAP Preview for document literal unwrapped type.
• Widget and Page upload using URL option does not use the HTTP proxy settings.
• XSLT truncates URL from Source operator.
• Failed to connect to Optim Server using the latest Optim Attunity driver with Driver Manager.
• Lightweight widget cannot use custom icon with relative path.
• Header columns with carriage returns: When header column contains a carriage return the header string is not picked up
• General Config Settings: Updating the Mashup Builder URL in Hub via the Settings -> General Config Settings to point to a Lotus Mashups with HTTP server in front gives HTTP 500 error.
• Upload Widget from URL does not default the TITLE to the Widget name.
• Edit Source for a WSDL by file upload resets the operation.
• When creating a feed from a Web service on the Mac Safari 4.0 browser, the XML tree view does not display correctly.

For documentation for Mashup Center, see the following Web sites.

Mashup Center wiki: The Mashup Center wiki contains articles on installing, administering, deploying, and using IBM Mashup Center. You can also create new articles or add comments to the documentation.

Mashup Center information center: The Mashup Center information center contains the original edition of the documentation that was completed when the product released. This edition is accessible by screen readers and is available in multiple languages. You can access the Mashup Center release notes from the Mashup Center information center.