| |
|
| |
Contents: Administering Mashup Center : Mashup Center 2.0 This topic describes how administrators can publish widgets to the catalog from the mashup builder. Before you begin
As a prerequisite, set the com.ibm.mashups.hub.url parameter in ... |
| |
|
| |
This article describes how to deploy a widget WAR package to the Mashup Center server when the MashupHub catalog is not installed or available. Do the following steps: Install the widget WAR file in WebSphere Application Server. Be sure you provide the appropriate access to the widget ... |
| |
|
| |
This topic describes three common deployment scenarios for IBM Mashup Center. This content is provided by the Mashup Center System Verification Test (SVT) test team, which was responsible for installing, configuring, deploying, and testing Mashup Center 2.0. Setting up a Lotus Mashups cluster ... |
| |
|
| |
This topic describes the following five common deployment scenarios for IBM Mashup Center. Scenario 1: Default installation of Lotus Mashups and InfoSphere MashupHub on a single server. Data repositories include file system and embedded Derby database.
Scenario 2: Clustered ... |
| |
|
| |
The goal of this document is to outline the steps that the IBM System Verification Test (SVT) team used to install, configure, and verify Mashup Center in both a clustered and non-clustered environmen |
| |
|
| |
This topic describes how to create a widget as a WAR file, deploy it to MashupHub, and install it in Lotus Mashups. You can create widgets using IBM Lotus Widget Factory and IBM WebSphere sMash and thendeploy them to Lotus Mashups. For information about how to create and deploy widgets using ... |
| |
|
| |
This topic describes how to create a widget as a WAR file, deploy it to MashupHub, and install it in Lotus Mashups. You can create widgets using IBM Lotus Widget Factory and IBM WebSphere sMash and |