This article describes how to upgrade and migrate
data to IBM Mashup Center 1.1 from either IBM Mashup Center 1.0. or 1.0.0.1.
What's
New
General
upgrade instructions
Cluster
configurations
Installing
the fixpack for 1.0.0.1
Installing
the fixpack for 1.1
Migrating
data
Troubleshooting
What's new?
Here are some of the key new features and enhancements that you will experience
after you upgrade to IBM Mashup Center V1.1:
Note: For a complete list of new features and functionality, see the
IBM Mashup Center V1.1 release notes on the IBM Mashup Center wiki site
at
http://www-10.lotus.com/ldd/mashupswiki.nsf/dx/release-notes.
New and enhanced out-of-the-box widgets
The following new widgets have been added to the toolbox:
- OpenStreetMap -- visualizes one or more locations on a
map based upon longitude and latitude coordinates, postal code, city, airport
code, place name, or street address. This widget supports a wide range
of configuration options, including the ability to display data from one
or more feeds, specify custom icons used, and tailor the information that
appears in the pop-up bubble.
- URL Customizer -- allows you to create dynamic URLs with
customized parameters. The URL can come from an event that is passed from
another widget on the mashup page, or it can come from a parameterized
feed in the catalog or on the Web.
- User Input -- provides a way for you to create a simple
form with various input controls quickly and easily. Input controls include
drop-down lists, radio buttons, text inputs, text areas, check boxes, and
date pickers.
- Action Timer -- allows you to set up a timer that controls
the frequency that an event gets passed to another widget in milliseconds.
Each time an event gets passed, the counter increases by one. You can wire
the Action Timer widget to another widget on the page to trigger repeatable
actions such as page refreshes or other updates.
- Slide Show -- automatically cycles through a series of
images. You can easily add and remove new images. You can customize the
slide show to repeat automatically, configure a delay, and add bubble descriptions.
- Chart -- replaces the existing V1.0 pie, bar, and line
chart widgets, combining them into one powerful new widget that supports
both comma-separated value (CSV) and XML data.
- Data Editor -- uses common operations such as sort, filter,
and limit to transform content received from one widget into outgoing content
to be sent to a second widget. Using the Data Editor widget, you can send
only the content you need in a format that can be consumed by other data-displaying
widgets. This widget has been significantly streamlined in V1.1, resulting
in fewer clicks to transform payload types.
For
more information about widgets, including example usage scenarios, see
the
Widget
help in the in the IBM Mashup Center wiki.
Ability to embed widgets and mashups in your
Web pages
IBM Mashup Center now provides the ability to embed mashup
pages and widgets into any external HTML Web page. With a few mouse clicks,
end users can generate HTML markup for a widget or page, and then copy
and paste the markup into a browser-based page, such as a WebSphere Portal
page, web content page, blog, wiki, or even a portlet. The end result is
seamless syndication of mashups and pages with minimal effort. For more
information about the new embedding feature, see Adding
widgets and mashup pages to your Web pages.
Page layout has moved to a theme model
Now, when you want to change the look and feel of your
mashup pages, you can switch between two default themes. One theme adds
columns to your pages, and the other does not. Each theme contains several
skins. Themes provide the navigation, appearance, and layout of the mashup
page, including colors, fonts, and images that surround the widgets on
the page. Skins define the look and feel of the widgets that you drag onto
the page. Skins essentially wrap the widgets and define the menu icons
and colors of the widget. When working in edit mode, you can switch between
the two default page themes and change the widget skins. For more information,
see Working
with themes and skins.
New widget data model
For widgets to communicate properly (send and receive data),
they need to be able to understand the type of data received from other
widgets on the page. To ease this communication process, IBM Mashup Center
now defines a common data model for widgets. It defines many simple, out-of-the-box
data types such as string, URL, date, email, and person, as well as some
complex types such as table, Atom, and JSON. Of course, widget developers
can also create and register their own customized data types. With a well
defined set of data types, widget developers can more easily build mashable
widgets that can communicate by speaking a common language. For more information
about data types see Working
with payload types.
More friendly widget event names
The IBM widget specification has been enhanced to include
a display name for events. As a result, the event names that appear in
the wiring interface are now more user-friendly, making it easier for business
users to connect widgets together.
New administrator interface to perform tasks
Now, WAS administrative console users can access a new
interface to perform the following tasks:
- Reset the default palette: Resets all users' toolboxes.
This option is useful because it allows you to move new widgets to your
users' toolboxes without having to add them manually from the catalog.
Note that this task removes any customization that users have applied to
their toolboxes.
- Migrate data: Migrates your Lotus Mashups data
to V1.1. This task migrates page fragments, removes page layout data and
adds them to separate tables as metadatam changes widget titles and icon
references, changes event names, creates a combined bar, line, and pie
Chart widget, and more.
- Migrate MashupHub: Migrates V1.0 mashup pages that
are published to MashupHub data to V1.1.
- Publish widgets: Creates widget URL links in the
catalog, making it easier for users to re-add deleted widgets and also
add the new V1.1 widgets to their toolboxes without administrator intervention.
To
access the interface, go to http://
server:port/mum/administration,
where
server is the Lotus Mashups server and
port is the
port number.
General upgrade instructions
To upgrade to IBM Mashup Center version 1.1. do the following steps:
- Determine the version of Mashup Center that is installed on your
machine. You can confirm the version by looking in the following log file:
C:\Program
Files\IBM Mashup Center\version.txt.
- Download and apply the appropriate fixpack packages:
| Your current version
| Fixpack to apply
|
| IBM Mashup Center 1.0.0.1
| Fixpack for version 1.1
|
| IBM Mashup Center 1.0
| Fixpack for version 1.0.0.1 and Fixpack for
version 1.1
Note: If you have IBM Mashup Center version 1.0, IBM Support Fix Central
will list both of the fixpacks so that you can download them at one time.
There is no need for you to download the fixpacks separately. |
- You can obtain the fixpack packages from the IBM Support Fix
Central Web site at http://www.ibm.com/support/fixcentral.
- From the Product family list, select either Information
Management or Lotus.
- From the Product list, select IBM Mashup Center.
- From the Installed Version list, specify the version of
IBM Mashup Center that you currently have installed.
- From the Platform list, specify the operating system that
you have IBM Mashup Center installed on.
- You will be asked to log in to Fix Central. If you do not already
have a user ID and password for Fix Central, you can register directly
from
the site to obtain a user ID and password.
- Download the fixpacks.
- Follow the steps below for installing the fixpacks.
Cluster configurations
If you have a cluster configuration, do the following steps:
- Stop each server and each node agent in the cluster.
- Run the installation steps on each of the node separately.
- In the future, if you need to add more nodes to the cluster,
apply the fixpack to those nodes after synchronization.
Installing the fixpack for 1.0.0.1
Important: You should install fixpack 1.0.0.1 before you install fixpack
1.1. If you already have installed fixpack 1.0.0.1, you can ignore this
step.
To obtain the readme file for fixpack 1.0.0.1,
go to the IBM Mashup Center wiki site at http://www-10.lotus.com/ldd/mashupswiki.nsf/dx/fixpacks.
To install the fixpack, do the following steps:
- Do the following steps to verify that WebSphere Application Server
(WAS) is shut down.
- Open the Services list by selecting Start > Control Panel
> Administrative Tools > Services.
- Open the Service entry for IBM WebSphere Application Server
V6.1 node-name.
- If the Service status is Started, click the Stop
button and wait for the status to indicate that the server is Stopped.
Note: If WAS is already stopped and you click the Stop button, the
process attempts to stop the server and will display a message similar
to the following error if the server is already stopped:
[exec] ADMU0509I: The server "server1" cannot be reached.
It appears to be stopped.
[exec] ADMU0211I: Error details may be seen in the file:
[exec] C:\Progs\IBM_MashupCenter\mm_profile\logs\server1\ stopServer.log
- In the IBM Mashup Center root directory, create a directory named
fixes if it does not already
exist.
- Move the mashupcenter1001.pak
fixpack file to the IBM Mashup Center\fixes
directory.
- 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.
- Open a command prompt window by selecting Start > Run >
cmd.
- In the command prompt window, change to the IBM Mashup Center
root directory, for example cd C:\Progs\IBM_MashupCenter.
- 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.
- Start the server. You can validate that the fixpack was installed
successfully by accessing the key features in both Lotus Mashups and MashupHub.
Example output:
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
Installing the fixpack for 1.1
You must install fixpack 1.0.0.1 before you install fixpack 1.1.
Read the IBM Mashup Center V1.1 release notes on the IBM Mashup
Center wiki
site at http://www-10.lotus.com/ldd/mashupswiki.nsf/dx/release-notes.
To install the fixpack, do the following steps:
- Do the following steps to verify that WebSphere Application Server
(WAS) is shut down.
- Open the Services list by selecting Start > Control Panel
> Administrative Tools > Services.
- Open the Service entry for IBM WebSphere Application Server
V6.1 node-name.
- If the Service status is Started, click the Stop
button and wait for the status to indicate that the server is Stopped.
Note: If WAS is already stopped and you click the Stop button, the
process attempts to stop the server and will display a message similar
to the following error if the server is already stopped:
[exec] ADMU0509I: The server "server1" cannot be reached.
It appears to be stopped.
[exec] ADMU0211I: Error details may be seen in the file:
[exec] C:\Progs\IBM_MashupCenter\mm_profile\logs\server1\ stopServer.log
- In the IBM Mashup Center root directory, create a directory named
fixes if it does not already
exist.
- Move the mashupcenter11.pak
fixpack file to the IBM Mashup Center\fixes
directory.
- Move the updatemashup.bat
and updatemashup.xml files
to the IBM Mashup Center root directory.
- Open a command prompt window by selecting Start > Run >
cmd.
- In the command prompt window, change to the IBM Mashup Center
root directory, for example cd C:\Progs\IBM_MashupCenter.
- In the command prompt window, type updatemashup.bat
MashupCenter11, where MashupCenter11
is the name of the fixpack file. The update runs automatically. See the
example output below.
- If you migrated the catalog to either IBM DB2 Database for Linux,
UNIX, and Windows, or IBM Informix Dynamic Server, you must update the
database schema. Refer to the IBM Mashup Center version 1.1 release notes
on the IBM Mashup Center wiki site at http://www-10.lotus.com/ldd/mashupswiki.nsf/dx/release-notes.
- If you migrated a Lotus Mashups server that is connected to a
DB2 Database, update the database schema by applying the SQL commands in
the IBM Mashup Center\Config\dbscripts\DB2\SchemaExtensionForV11.sql
file.
- Start the server.
Migrating data
To migrate data, do the following steps:
- To upgrade Lotus Mashups pages, go to the administration interface
at http://servername:port/mum/administration
and run the steps Migrate Data and Migrate Hub. You can also
run the Publish Widgets task to add the V1.1 widgets to the catalog.
Note: You should back up your file system either by copying the file
tree to a backup or using system backup tools. Additionally, you should
back up your database by using the DB2 or Informix data backup tools before
you migrate the database.
- Restart the server. This will clean the cache and refresh the
catalog list.
- You can validate that the fixpack was installed successfully
by accessing the key features in both Lotus Mashups and InfoSphere Mashup
Hub.
When you install fixpack version 1.1, you might receive the following
error message:
[wsadmin] OSError: [Errno 0] No such directory:
C:/Program Files/IBM Mashup
Center/fixes/MashupCenter11/ears/mm/mm_ear
This error occurs when step 4 is skipped. To recover from this error, move
the updatemashup scripts
from version 1.1 into the IBM Mashup Center root directory. Then repeat
steps 5 through 7 again.
Example output:
Buildfile: updatemashup.xml
update:
[echo] Root Directory is: C:/ProgramFiles/TestInstalls/
MCenter081021/mm
[echo] Fix number is: MashupCenter11
[exec] ADMU0116I: Tool information is being logged in file
[exec] C:\ProgramFiles\TestInstalls\MCenter081021\
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:
[exec] C:\ProgramFiles\TestInstalls\MCenter081021\
mm_profile\logs\server1\stopServer.log
[copy] Copying 62 files to C:\ProgramFiles\TestInstalls\
MCenter081021\fixes\backup\MashupCenter11\Config
[copy] Copying 2201 files to C:\ProgramFiles\TestInstalls\
MCenter081021\fixes\backup\MashupCenter11\mm
[copy] Copying 6528 files to C:\ProgramFiles\TestInstalls\
MCenter081021\fixes\backup\MashupCenter11\Hub
[copy] Copied 895 empty directories to 4 empty directories under
C:\ProgramFiles\TestInstalls\MCenter081021\fixes\
backup\MashupCenter11\Hub
[unzip] Expanding: C:\ProgramFiles\TestInstalls\MCenter081021\
fixes\MashupCenter11.pak into
C:\ProgramFiles\TestInstalls\MCenter081021\fixes\
MashupCenter11\plugin
pre-update:
[copy] Copying 3 files to C:\ProgramFiles\TestInstalls\
MCenter081021\fixes\backup\MashupCenter11\configuration
[unzip] Expanding: C:\ProgramFiles\TestInstalls\
MCenter081021\fixes\MashupCenter11.pak into
C:\ProgramFiles\TestInstalls\MCenter081021\fixes\
MashupCenter11\plugin
pre-update:
[unzip] Expanding: C:\ProgramFiles\TestInstalls\MCenter081021\
fixes\MashupCenter11.pak into
C:\ProgramFiles\TestInstalls\MCenter081021
...
[exec] [wsadmin] Config Dynamic Cache for services/cache/
mmmsRegion was successful
[exec] BUILD SUCCESSFUL
[exec] Total time: 6 minutes 25 seconds
[exec] C:\ProgramFiles\TestInstalls\MCenter081021>cd /d
C:\ProgramFiles\TestInstalls\MCenter081021\Config\
[exec] C:\ProgramFiles\TestInstalls\MCenter081021\Config>set
WAS_ANT_CLASSPATH=lib\dbt.jar;lib\dbupdate.jar;
lib\engine.jar;lib\parser.jar;lib\wkplc.misc.jar;lib\
wkplc.tools.jar;lib\wp.config.jar;lib\mm.config.jar
[exec] C:\ProgramFiles\TestInstalls\MCenter081021\Config>
call ..\AppServer\bin\ws_ant.bat -f config.xml
-listener org.apache.tools.ant.XmlLogger
-Dplatform.script.ext=bat action-config-hub-upgrade
[exec] Buildfile: config.xml
[exec] [echo] Root Directory is use: C:/ProgramFiles/
TestInstalls/MCenter081021/mm
[exec] action-config-hub-upgrade:
[exec] [java] 17:10:53,775 (main) ERROR [DBHelper]
SQL Exception: Database 'C:/ProgramFiles
/TestInstalls/MCenter081021/Hub/installedApps/
Mashup Hub.ear
/mashuphub-enterprise.war\\hubdb'
shutdown.,
SQLState = 08006, ErrorCode = 45000
[exec] BUILD SUCCESSFUL
[exec] Total time: 8 seconds
BUILD SUCCESSFUL
Total time: 15 minutes 5 seconds
Troubleshooting
This section describes some known issues and workarounds that you may experience
as you upgrade IBM Mashup Center.
Note the following issues:
- After migrating to V1.1, users must clear their browser cache
to avoid getting errors. Users must also clear their browser cache if both
versions of IBM Mashup Center are installed on the same machine.
- If there are V1.0 widget
WAR files in the catalog, they should function as is when added to your
toolbox. But if you are adding any out-of-the-box widgets, you should be
careful not to overwrite them with old versions.
- In order to run properly, the
following V1.1 widgets require a native Lotus Mashups environment. If you
attempt to embed them in a remote location, they may produce errors at
runtime:
- Data Editor
- Event Explorer
- Web Site Displayer
- HTML Markup
- Portal
- Regular Expression
- JavaScript Adapter