| Original IBM content |
English |
| Brazilian
Portuguese |
|
German |
|
Japanese |
|
Korean |
|
Spanish |
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 installation with a separate database and directory server used as the data repository.
- Scenario 3: Non-clustered installation with a Web server, database and directory server. Includes single sign-on.
- Scenario 4: Clustered installation with Web server, Web proxy, database, and directory server.
- Scenario 5: Clustered installation with Web server, Web proxy, database, directory server, and separate widget server. Also includes the AJAX proxy.
Note: To learn about the test infrastructure used by the IBM System Verification Test (SVT) team, see
IBM Mashup Center V1.1 test infrastructure.
Deployment scenario 1: Default installation of Lotus Mashups and InfoSphere MashupHub on a single server. Data repositories include file system and embedded Derby database
In this scenario, you install and deploy IBM Mashup Center in a non-clustered environment. You install both Lotus Mashups and InfoSphere MashupHub on a single server using the default installation wizard settings. For Lotus Mashups, you use the local file system to manage your mashup applications. For InfoSphere MashupHub, you use the WAS embedded Derby database as your data respository. Since IBM Mashup Center is a browser-based application, you install a Web server on a separate server to handle HTTP requests.
This scenario is the simplest of the five scenarios described in this topic.
Here are the details for the components that make up your environment:
Component | Description |
Lotus Mashups | Installed on same server as InfoSphere MashupHub. Supported operating systems include Windows 2003 Server and Red Hat Enterprise Linux V5. |
InfoSphere MashupHub | Installed on same server as Lotus Mashups. Supported operating systems include Windows 2003 Server and Red Hat Enterprise Linux V5. |
Web server | IBM HTTP Server V6.1.0.13 running either Windows 2003 Server or Red Hat Enterprise Linux V5 (32bit) on separate server. |
Data respository | File system for Lotus Mashups, and the default embedded Derby database for InfoSphere MashupHub. |
Here is a graphical overview of your environment:
To install, configure, and deploy the components for scenario 1, do the following steps:
Install both Lotus Mashups and InfoSphere MashupHub on a single server. For installation instructions, see the IBM Mashup Center Quick Start Guide.
Do the following steps to install IBM HTTP Server V6.1.0.13 on a different server. For more information about installing IBM HTTP Server (IHS), see the Installing IBM HTTP Server topic in the WAS Information Center.
Install IBM HTTP Server 6.1 from the WAS Network Deployment 6.1 download CD.
During the installation process, do the following steps:
Set the installation location, for example C:\IBM\HTTPServer.
Select Run HTTP server as the Windows server and IBM HTTP Administration as the Windows Service. Log on using the specified user account, and type the system administrator's user name and password.
Specify the HTTP adminstrator's user ID and password. Click Next.
Select to install the IHS plug-in for WAS, and specify the Web server definition and the host name for WAS. Click Next to finish.
Go to the IBM Support site and download IHS 61013 fixpack (6.1.0-WS-IHS-WinX32-FP0000013.pak and plug-in fixpack 6.1.0-WS-PLG-WinX32-FP0000013.pak).
Install the IHS 61013 fixpack 6.1.0-WS-IHS-WinX32-FP0000013.pak on IBM HTTPServer using the Update Installer.
Install the IHS plug-in 61013 fixpack 6.1.0-WS-PLG-WinX32-FP0000013.pak on IBM HTTPServerPlugin using the Update Installer.
Deployment scenario 2: Clustered installation with a separate database and directory server used as the data repository
In this scenario, you install and deploy IBM Mashup Center in a horizontally clustered WAS environment. The basic configuration is the same as Deployment scenario 1, except for the cluster. You install Lotus Mashups and InfoSphere MashupHub as two separate nodes and federate them into the cluster.
Next, you install and configure a separate database as your data repository. In this scenario, the database can be DB2, Oracle, or SQL Server. You enhance the performance of the database and improve manageability by installing a directory server on top of the database. The directory server can be either Microsoft Active Directory, Tivoli Directory Server, or another supported LDAP server.
After you get all the components installed and configured, you are ready to start unlocking information sources such as SAP, databases, and desktop and departmental information in spread sheets by creating consumable feeds. Using the feed-generation capabilities of IBM Mashup Center, you can easily connect to your back-end data sources, transform the data into a "mashable" feed format, publish the new data to your catalog, and then use it in your mashup applications.
This scenario is more common than the first scenario.
For more information about installing and configuring a cluster, see Configuring a clustered server environment for IBM Mashup Center.
Here are the details for the components that make up your environment:
Component | Description |
Lotus Mashups | Installed on same server as InfoSphere MashupHub. Supported operating systems include Windows 2003 Server and Red Hat Enterprise Linux V5. |
InfoSphere MashupHub | Installed on same server as Lotus Mashups. Supported operating systems include Windows 2003 Server and Red Hat Enterprise Linux V5. |
Web server | IBM HTTP Server V6.1.0.13 running Windows 2003 Server on Red Hat Enterprise Linux V5 (32bit) separate server. |
Database | One of the following options:
- DB2 Enterprise Edition V9.5 running Windows 2003 Server
- DB2 Enterprise Edition V9.5 (64bit) running Red Hat Enterprise Linux V5 (64bit)
- DB2 Express Edition V9.5 running Red Hat Enterprise Linux V5 (32bit)
- Oracle 10.2.0.1 running either Windows 2003 Server or Red Hat Enterprise Linux V5 (32bit)
- Microsoft SQL Server 2005 (requires the IBM Mashup Center V1.1.0.1 fixpack, available here)
- IBM Informix (InfoSphere MashupHub only)
|
Directory server | One of the following options:
- Microsoft Windows Server 2003 Active Directory running Windows 2003 Server
- IBM Tivoli® Directory Server 6.1 running Windows 2003 Server
- Other supported LDAP server
|
Here is a graphical overview of your environment:
To install, configure, and deploy the components for scenario 2, do the following steps:
Install both Lotus Mashups and InfoSphere MashupHub on a single server. For installation instructions, see the IBM Mashup Center Quick Start Guide.
Configure DB2, Oracle, or SQL Server for Lotus Mashups. For information about creating the database, the Lotus Mashups resources, and the data source, see either Confguring DB2 for IBM Lotus Mashups, Configuring Oracle for IBM Lotus Mashups, or Configuring SQL Server for IBM Lotus Mashups.
Configure the database for InfoSphere MashupHub. See the IBM InfoSphere MashupHub User and Administrator Guide for details.
Configure the LDAP directory server on the WAS Deployment Manager.
Do the following steps to install IBM HTTP Server V6.1.0.13 on a different server. For more information about installing IBM HTTP Server, see the Installing IBM HTTP Server topic in the WAS Information Center.
Install IBM HTTP Server 6.1 from the WAS Network Deployment 6.1 download CD.
During the installation process, do the following steps:
Set the installation location, for example C:\IBM\HTTPServer.
Select Run HTTP server as the Windows server and IBM HTTP Administration as the Windows Service. Log on using the specified user account, and type the system administrator's user name and password.
Specify the HTTP adminstrator's user ID and password. Click Next.
Select to install the IHS plug-in for WAS, and specify the Web server definition and the host name for WAS. Click Next to finish.
Go to the IBM Support site and download IHS 61013 fixpack (6.1.0-WS-IHS-WinX32-FP0000013.pak and plug-in fixpack 6.1.0-WS-PLG-WinX32-FP0000013.pak)
Install the IHS 61013 fixpack 6.1.0-WS-IHS-WinX32-FP0000013.pak on IBM HTTPServer using the Update Installer.
Install the IHS plug-in 61013 fixpack 6.1.0-WS-PLG-WinX32-FP0000013.pak on IBM HTTPServerPlugin using the Update Installer.
Set up the WAS horizontal cluster with Lotus Mashups and InfoSphere MashupHub as two separate nodes. For details, see Configuring a clustered server environment for IBM Mashup Center.
Deployment scenario 3: Non-clustered installation with a Web server, database and directory server. Includes single sign-on
In this scenario, you install and deploy Lotus Mashups and Mashup Hub on two separate servers. During the installation process, you have the option to install them separately for each server.
Similar to the first scenario, you install a Web server to handle HTTP requests.
Next, you install and configure a separate database as your data repository. In this scenario, the database can be DB2, Oracle, or SQL Server. You enhance the performance of the database and improve manageability by installing a directory server on top of the database. The directory server can be either Microsoft Active Directory, Tivoli Directory Server, or another supported LDAP server.
Next, because Lotus Mashups and InfoSphere MashupHub are installed separately, you configure single sign-on for end users. This means that users will only have to authenticate with the server the first time they log on. You set up single sign-on directly from the WAS administrative console.
After you get all the components installed and configured, you are ready to start unlocking information sources such as SAP, databases, and desktop and departmental information in spread sheets by creating consumable feeds. Using the feed-generation capabilities of IBM Mashup Center, you can easily connect to your back-end data sources, transform the data into a "mashable" feed format, publish the new data to your catalog, and then use it in your mashup applications.
Here are the details for the components that make up your environment:
Component | Description |
Lotus Mashups | Installed on a single node with WebSphere Application Server. Supported operating systems include Windows 2003 Server and Red Hat Enterprise Linux V5. |
InfoSphere MashupHub | Installed on a single node with WebSphere Application Server. Supported operating systems include Windows 2003 Server and Red Hat Enterprise Linux V5. |
Web server | IBM HTTP Server V6.1.0.13 running Windows 2003 Server or Red Hat Enterprise Linux V5 (32bit) on separate server. |
Database | One of the following options:
- DB2 Enterprise Edition V9.5 running Windows 2003 Server
- DB2 Enterprise Edition V9.5 (64bit) running Red Hat Enterprise Linux V5 (64bit)
- DB2 Express Edition V9.5 running Red Hat Enterprise Linux V5 (32bit)
- Oracle 10.2.0.1 running either Windows 2003 Server or Red Hat Enterprise Linux V5 (32bit)
- Microsoft SQL Server 2005 (requires the IBM Mashup Center V1.1.0.1 fixpack, available here)
- IBM Informix (InfoSphere MashupHub only)
|
Directory server | One of the following options:
- Microsoft Windows Server 2003 Active Directory running Windows 2003 Server
- IBM Tivoli® Directory Server 6.1 running Windows 2003 Server
- Other supported LDAP server
|
Here is a graphical overview of your environment:
To install, configure, and deploy the components for scenario 3, do the following steps:
Install Lotus Mashups and InfoSphere MashupHub on two different servers. For installation instructions, see the IBM Mashup Center Quick Start Guide.
Configure DB2, Oracle, or SQL Server for Lotus Mashups. For information about creating the database, the Lotus Mashups resources, and the data source, see either Confguring DB2 for IBM Lotus Mashups, Configuring Oracle for IBM Lotus Mashups, or Configuring SQL Server for IBM Lotus Mashups.
Configure the database for InfoSphere MashupHub. See the IBM InfoSphere MashupHub User and Administrator Guide for details.
Configure the LDAP directory server on the WAS Deployment Manager.
Do the following steps to install IBM HTTP Server V6.1.0.13. For more information about installing IBM HTTP Server, see the Installing IBM HTTP Server topic in the WAS Information Center.
Install IBM HTTP Server 6.1 from the WAS Network Deployment 6.1 download CD.
During the installation process, do the following steps:
Set the installation location, for example C:\IBM\HTTPServer.
Select Run HTTP server as the Windows server and IBM HTTP Administration as the Windows Service. Log on using the specified user account, and type the system administrator's user name and password.
Specify the HTTP adminstrator's user ID and password. Click Next.
Select to install the IHS plug-in for WAS, and specify the Web server definition and the host name for WAS. Click Next to finish.
Go to the IBM Support site and download IHS 61013 fixpack (6.1.0-WS-IHS-WinX32-FP0000013.pak and plug-in fixpack 6.1.0-WS-PLG-WinX32-FP0000013.pak)
Install the IHS 61013 fixpack 6.1.0-WS-IHS-WinX32-FP0000013.pak on IBM HTTPServer using the Update Installer.
Install the IHS plug-in 61013 fixpack 6.1.0-WS-PLG-WinX32-FP0000013.pak on IBM HTTPServerPlugin using the Update Installer.
Configure single sign-on on the Lotus Mashups and InfoSphere MashupHub servers using the WAS administrative console. For more infomation, see Configuring single sign-on for users. Also see this topic in the WAS Information Center.
Deployment scenario 4: Clustered installation with Web server, Web proxy, database, and directory server
In this scenario, you install and deploy IBM Mashup Center in a horizontally clustered WAS environment. A horizontal cluster has cluster members on multiple nodes. In this case, Lotus Mashups is installed on multiple nodes federated to a cluster to the same cell as the InfoSphere MashupHub cluster that is installed on multiple nodes. Since the Lotus Mashups and InfoSphere MashupHub clusters are in the same cell, you do not need to perform any steps to enable single sign-on.
Similar to the previous scenarios, you install a Web server to handle HTTP requests. In addition, you install a second Web server for high availability, and you configure an HTTP proxy on the separate server to channel HTTP requests from the client to the Web server.
Next, you install and configure a separate database as your data repository. In this scenario, the database can be DB2, Oracle, or SQL Server. You enhance the performance of the database and improve manageability by installing a directory server on top of the database. The directory server can be Microsoft Active Directory, Tivoli Directory Server, or another supported LDAP server.
After you get all the components installed and configured, you are ready to start unlocking information sources such as SAP, databases, and desktop and departmental information in spread sheets by creating consumable feeds. Using the feed-generation capabilities of IBM Mashup Center, you can easily connect to your back-end data sources, transform the data into a "mashable" feed format, publish the new data to your catalog, and then use it in your mashup applications.
Here are the details for the components that make up your environment:
Component | Description |
Lotus Mashups | Installed as a separate node in a horizontally clustered WAS environment. Supported operating systems include Windows 2003 Server and Red Hat Enterprise Linux V5. |
InfoSphere MashupHub | Installed as a separate node in a horizontally clustered WAS environment. Supported operating systems include Windows 2003 Server and Red Hat Enterprise Linux V5. |
Web server | IBM HTTP Server V6.1.0.13 running Windows 2003 Server or Red Hat Enterprise Linux V5 (32bit) on separate server. |
Web server proxy | IBM Edge Caching Proxy Version 6.1 running Windows 2003 Server. |
Database | One of the following options:
- DB2 Enterprise Edition V9.5 running Windows 2003 Server
- DB2 Enterprise Edition V9.5(64bit) running Red Hat Enterprise Linux V5 (64bit)
- DB2 Express Edition V9.5 running Red Hat Enterprise Linux V5 (32bit)
- Oracle 10.2.0.1 running either Windows 2003 Server or Red Hat Enterprise Linux V5 (32bit)
- Microsoft SQL Server 2005 (requires the IBM Mashup Center V1.1.0.1 fixpack, available here)
- IBM Informix (InfoSphere MashupHub only)
|
Directory server | One of the following options:
- Microsoft Windows Server 2003 Active Directory running Windows 2003 Server
- IBM Tivoli® Directory Server 6.1 running Windows 2003 Server
- Other supported LDAP server
|
Here is a graphical overview of your environment:
To install, configure, and deploy the components for scenario 4, do the following steps:
Install IBM Mashup Center. For installation instructions, see the IBM Mashup Center Quick Start Guide.
Configure DB2, Oracle, or SQL Server for Lotus Mashups. For information about creating the database, the Lotus Mashups resources, and the data source, see either Confguring DB2 for IBM Lotus Mashups, Configuring Oracle for IBM Lotus Mashups, or Configuring SQL Server for IBM Lotus Mashups.
Configure the database for InfoSphere MashupHub. See the IBM InfoSphere MashupHub User and Administrator Guide for details.
Configure the LDAP directory server on the WAS Deployment Manager.
Do the following steps to install IBM HTTP Server V6.1.0.13. For more information about installing IBM HTTP Server, see the Installing IBM HTTP Server topic in the WAS Information Center.
Install IBM HTTP Server 6.1 from the WAS Network Deployment 6.1 download CD.
During the installation process, do the following steps:
Set the installation location, for example C:\IBM\HTTPServer.
Select Run HTTP server as the Windows server and IBM HTTP Administration as the Windows Service. Log on using the specified user account, and type the system administrator's user name and password.
Specify the HTTP adminstrator's user ID and password. Click Next.
Select to install the IHS plug-in for WAS, and specify the Web server definition and the host name for WAS. Click Next to finish.
Go to the IBM Support site and download IHS 61013 fixpack (6.1.0-WS-IHS-WinX32-FP0000013.pak and plug-in fixpack 6.1.0-WS-PLG-WinX32-FP0000013.pak)
Install the IHS 61013 fixpack 6.1.0-WS-IHS-WinX32-FP0000013.pak on IBM HTTPServer using the Update Installer.
Install the IHS plug-in 61013 fixpack 6.1.0-WS-PLG-WinX32-FP0000013.pak on IBM HTTPServerPlugin using the Update Installer.
Configure IBM Edge Caching Proxy Version 6.1.
Configure a horizontal clustered WAS server environment Lotus Mashups server, the InfoSphere MashupHub server, and the Web server. For details, see Configuring a clustered server environment for IBM Mashup Center.
Deployment scenario 5: Clustered installation with Web server, Web proxy, database, directory server, and separate widget server. Also includes the AJAX proxy.
In this scenario, you install and deploy IBM Mashup Center in a horizontally clustered WAS environment. A horizontal cluster has cluster members on multiple nodes. In this case, Lotus Mashups is installed on multiple nodes federated to a cluster to the same cell as the InfoSphere MashupHub cluster that is installed on multiple nodes. Since the Lotus Mashups and InfoSphere MashupHub clusters are in the same cell, you do not need to perform any steps to enable single sign-on.
In this scenario, you create a separate widget server cluster. You will mostly use this server to deploy your custom widget applications. This helps maintain the performance of the Lotus Mashups server in case any widgets become. This also helps distribute custom application processing. You could also deploy some of the inbox widgets to this new cluster.
Similar to Deployment scenario 4, you install a Web server to handle HTTP requests, and you configure an HTTP proxy on a separate server to channel HTTP requests from the client to the Web server.
Next, you install and configure a separate database as your data repository. The database can be DB2, Oracle, or SQL Server. You enhance the performance of the database and improve manageability by installing a directory server on top of the database. The directory server can be Microsoft Active Directory, Tivoli Directory Server, or another supported LDAP server.
Now, you configure the AJAX proxy. The AJAX proxy provides security by restricting access to trusted origins in a more flexible way than a browser-based solution. Standard installation comes pre-configured for basic needs. For advanced configuration and more information about the AJAX proxy, see Configuring the HTTP proxy for AJAX applications. You can configure the AJAX proxy for any of the scenarios described above.
After you get all the components installed and configured, you are ready to start unlocking information sources such as SAP, databases, and desktop and departmental information in spread sheets by creating consumable feeds. Using the feed-generation capabilities of IBM Mashup Center, you can easily connect to your back-end data sources, transform the data into a "mashable" feed format, publish the new data to your catalog, and then use it in your mashup applications.
Here are the details for the components that make up your environment:
Component | Description |
Lotus Mashups | Installed in a horizontally clustered WAS environment. Supported operating systems include Windows 2003 Server and Red Hat Enterprise Linux V5. |
InfoSphere MashupHub | Installed in a horizontally clustered WAS environment. Supported operating systems include Windows 2003 Server and Red Hat Enterprise Linux V5. |
Widget server | Installed in a horizontally clustered WAS environment or any widget application supported environment. Supported operating systems are limited to the widget hosting environment that you choose. From widget implementation perspective, you are no limited, because widgets can use an back-end support to support its functionality. |
Web server | IBM HTTP Server V6.1.0.13 running Windows 2003 Server or Red Hat Enterprise Linux V5 (32bit) on separate server. |
Web server proxy | IBM Edge Caching Proxy Version 6.1 running Windows 2003 Server. |
Database | One of the following options:
- DB2 Enterprise Edition V9.5 running Windows 2003 Server
- DB2 Enterprise Edition V9.5(64bit) running Red Hat Enterprise Linux V5 (64bit)
- DB2 Express Edition V9.5 running Red Hat Enterprise Linux V5 (32bit)
- Oracle 10.2.0.1 running either Windows 2003 Server or Red Hat Enterprise Linux V5 (32bit)
- Microsoft SQL Server 2005 (requires the IBM Mashup Center V1.1.0.1 fixpack, available here)
- IBM Informix (InfoSphere MashupHub only)
|
Directory server | One of the following options:
- Microsoft Windows Server 2003 Active Directory
- IBM Tivoli® Directory Server 6.1 running Windows 2003 Server
- Other supported LDAP server
|
Here is a graphical overview of your environment:
To install, configure, and deploy the components for scenario 5, do the following steps:
Install IBM Mashup Center. For installation instructions, see the IBM Mashup Center Quick Start Guide.
Install and configure a separate server for your widgets.
Configure DB2, Oracle, or SQL Server for Lotus Mashups. For information about creating the database, the Lotus Mashups resources, and the data source, see either Confguring DB2 for IBM Lotus Mashups, Configuring Oracle for IBM Lotus Mashups, or Configuring SQL Server for IBM Lotus Mashups.
Configure the database for InfoSphere MashupHub. See the IBM InfoSphere MashupHub User and Administrator Guide for details.
Configure the LDAP directory server on the WAS Deployment Manager.
Do the following steps to install IBM HTTP Server V6.1.0.13. For more information about installing IBM HTTP Server, see the Installing IBM HTTP Server topic in the WAS Information Center.
Install IBM HTTP Server 6.1 from the WAS Network Deployment 6.1 download CD.
During the installation process, do the following steps:
Set the installation location, for example C:\IBM\HTTPServer.
Select Run HTTP server as the Windows server and IBM HTTP Administration as the Windows Service. Log on using the specified user account, and type the system administrator's user name and password.
Specify the HTTP administrator's user ID and password. Click Next.
Select to install the IHS plug-in for WAS, and specify the Web server definition and the host name for WAS. Click Next to finish.
Go to the IBM Support site and download IHS 61013 fixpack (6.1.0-WS-IHS-WinX32-FP0000013.pak and plug-in fixpack 6.1.0-WS-PLG-WinX32-FP0000013.pak)
Install the IHS 61013 fixpack 6.1.0-WS-IHS-WinX32-FP0000013.pak on IBM HTTPServer using the Update Installer.
Install the IHS plug-in 61013 fixpack 6.1.0-WS-PLG-WinX32-FP0000013.pak on IBM HTTPServerPlugin using the Update Installer.
Configure IBM Edge Caching Proxy Version 6.1.
Configure a horizontal clustered WAS server environment, the Lotus Mashups server, the InfoSphere MashupHub server, the widget server, and the Web server. For details, see Configuring a clustered server environment for IBM Mashup Center.