This topic provides instructions for installing IBM® Mashup Center 3.0 on AIX®.

This topic describes how to add the correct interceptor class to the WebSphere Application Server Deployment Manager so that users can successfully access the WebDAV file store in the Mashup Center cluster.

This topic provides instructions for installing IBM® Mashup Center 3.0 on Linux™.

This topic describes how to add the correct interceptor class to the WebSphere Application Server Deployment Manager so that users can successfully access the WebDAV file store in the Mashup Center cluster.

In this step, you will update WebSphere Application Server Network Deployment preferences to enable application security and synchronize the cluster nodes.

In this step, you will enable SSL between the IBM® HTTP Server and WebSphere Application Server servers.

In this step, you will federate the Mashup Center servers as managed nodes in the cluster.

This topic provides the instructions for installing the Mashup Center 3.0.0.1 fix pack and migrating data on Red Hat and SUSE Linux® and AIX platforms in a single server environment.

For information about configuring a clustered server environment for Mashup Center, see the following topics:

In this step, you will install IBM® HTTP Server 7.0 and its associated fix packs on the WebSphere Application Server Deployment Manager server.

This topic describes how to complete the tasks for installing the Mashup Center 3.0.0.1 fix pack when upgrading from Mashup Center version 2.0.0.2 in a clustered server environment.

The following topics describe how to set up a Mashup Center clustered environment using WebSphere Application Server Deployment Manager server and two Lotus® Mashups server nodes that connect to a standalone MashupHub server.

Mashup Center v3.0.0.1 corrects a data mashup builder behavior that affects how nonexistent text nodes are treated by copy operations in the Transform operator. As a result of this correction, data mashups affected by the behavior in v2.x might behave differently after they are migrated to ...

In this step, you will create a centralized cache for all MashupHub objects shared between nodes in a cluster. The hubclustercache.py script creates a centralized cache for all MashupHub objects shared between nodes in a cluster.

This topic describes how to migrate data from Mashup Center 2.0.0.2 to 3.0.0.1 in a single server environment.

This topic describes how to migrate data Mashup Center from version 2.0.0.2 to 3.0.0.1 in a clustered server environment.

See the following topics to learn how to install Mashup Center 3.0:

In this step, you will create and configure a new database and connect it to MashupHub on the primary node.

In this step, you will update WebSphere Application Server Network Deployment preferences to enable application security and synchronize the cluster nodes.

When you upgrade to IBM® Mashup Center, v3.0.0.1, some of your data mashups might be affected by changes that have been made to the Transform operator.

In this step, you will create a centralized cache for all MashupHub objects shared between nodes in a cluster. The hubclustercache.py script creates a centralized cache for all MashupHub objects shared between nodes in a cluster.

This topic describes known issues with upgrading that you should be aware of before completing the prerequisites in the next topic.

In this step, you will install WebSphere Application Server Network Deployment 7.0 and its associated fix packs on the Deployment Manager server. You will also configure LDAP on the WebSphere Application Server Deployment Manager server.

In this step, you will use the WebSphere Application Server Deployment Manager set up the cluster, federate the IBM® HTTP Server as a unmanaged node server, and create the web server for the cluster environment.

In this step, you will connect MashupHub on the secondary node to the database that you created earlier for the MashupHub server on the primary node. After completing this step, both servers will connect to a common database.