| |
|
| |
Each policy element defines an access policy for a given URL pattern. The pattern is specified by means of the url attribute. |
| |
|
| |
The following topics provide information for administering Lotus® Mashups. |
| |
|
| |
This topic describes how to configure Informix for Lotus® Mashups on a Linux platform. |
| |
|
| |
Mashup Center includes a public content store for users to share content such as JavaScript™ and other types of files. In order to prevent users from storing harmful files, you can either turn off the content store completely, or you can put an authorization proxy in front of the content store ... |
| |
|
| |
Increase the WebSphere Application Server session timeout value to avoid losing unsaved data. |
| |
|
| |
This topic describes how to secure the Mashup Center server by enabling HTTPS between the client and server. |
| |
|
| |
When working in an environment in which the catalog is not installed, you can add new gadgets to the OpenSocial category in the palette by adding URL references to the OpenSocial category in the catalogdefault.xml file on the server. This topic describes the required steps for add the ... |
| |
|
| |
This topic describes how to restore your users' palette to the original one shipped with Mashup Center. This task is useful when you want to delete a custom global palette and replace it with the original one that is defined by the catalog XML files that are shipped with the product. |
| |
|
| |
The following topics provide general administration information for Mashup Center. |
| |
|
| |
This topic describes how to import the default Mashup Center widgets into the catalog when Lotus® Mashups and MashupHub are not installed on the same machine. |
| |
|
| |
This topic describes how to configure a custom widget deployed to mashup builder so that it can never be sandboxed. |
| |
|
| |
Exported pages that include widgets require manual configuration to add to the target mashup builder. |
| |
|
| |
This topic describes how to forward HTTP error codes to the client and enable support for Basic Authentication. |
| |
|
| |
This topic describes how to configure access control for the default folders that are stored in the file store provided with Mashup Center. |
| |
|
| |
An administrator can create feed filtering policies, configure IP address access, disable feed replay attacks, and limit feed access rates. |
| |
|
| |
This topic provides a list of the custom properties that administrators can customize for Mashup Center. All of these properties are available in the ConfigService.properties file located in the MashupCenterinstallrootmmconfig directory. You can also customize many of these properties in the ... |
| |
|
| |
This set of topics provide information about configuring the HTTP proxy for AJAX (Asynchronous JavaScript™ and XML) applications. It includes configuration details, examples, and troubleshooting tips. |
| |
|
| |
To create feeds from a SharePoint Services repository, you must configure support on the SharePoint Services server. |
| |
|
| |
You can disable the "Add to WebSphere® Portal" action so that it does not appear in the MashupHub user interface. |
| |
|
| |
The palette that is shipped with Mashup Center is defined by a set of XML files. As an administrator, you can use these files as a reference when you want to define your own palette for users. |
| |
|
| |
This topic describes how to troubleshoot issues when working with OpenSocial gadgets. |
| |
|
| |
This topic describes how to configure and optimize cache settings for REST services. These settings are located in the mmconfigCacheService.properties file in your Mashup Center installation root. |
| |
|
| |
When you configure Microsoft® SQL Server 2005 for Mashup Center, you must configure it for both MashupHub and Lotus® Mashups. This topic covers only the configuration steps for Lotus Mashups in a Windows® environment. |
| |
|
| |
This topic describes how user preferences are set and stored for OpenSocial gadgets. |
| |
|
| |
As an administrator, you can configure the palette in the mashup builder. For example, you can create a global palette for all users, update the palette template for new users, and reset the default palette. For more information, see the following topics: |