You can customize the default URL that you use to log into Mashup Center. You can also customize the look and feel of the login screen. See Customizing the Mashup Center login screen for more information.

The following topics provide general administration information for Mashup Center.

This topic describes how to filter IP addresses using proxy elements to define rules for a particular IP address or set of addresses.

You use a context path mapping in the proxyconfig.xml file to map a particular context path to a target URL or specify your own proxy entry point. The proxy resolves context path mappings prior to applying the matching access policy. When working with context path mappings, you work with the ...

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 ...

You can configure security for Mashup Center in various ways. For example, you can configure single signon for users, enable HTTPS between the client and server, configure LDAP to create users and groups and then secure the server, and configure the Ajax proxy. For more information, see the ...

This topic describes the steps required to configure DB2® for Lotus® Mashups.

This topic describes the steps required to configure DB2® when it resides on a different machine than Lotus® Mashups.

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.

Configure the Ajax proxy using an XML file called proxyconfig.xml. You can find proxyconfig.xml in the following location: MashupCenterinstallrootmm.

By default, Mashup Center is designed with an open security model that does not restrict access to servers and websites. This flexible model allows you to configure the proxy based on your own security needs before going into production. This topic provides examples of how you can configure the ...

Each policy element defines an access policy for a given URL pattern. The pattern is specified by means of the url attribute.

The following two examples show sample proxyconfig.xml files that you can use as templates to define your own configurations. You can use these samples as a base to write your own Ajax proxy configuration.

When the palette is in mashup builder mode, you may want to update your users' personal palettes, such as add a new widget, remove an existing widget, or update a category. You can configure a global palette and merge it with your users' personal palettes when they log into Mashup Center and open ...

This topic describes how to configure the MashupHub to avoid the proxy.

This topic describes the steps required to configure DB2® when it resides on the same machine as Lotus® Mashups.

This topic describes how to forward HTTP error codes to the client and enable support for Basic Authentication.

This topic describes how administrators can perform a number of configuration tasks for the default parameters provided with Mashup Center.

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:

You can configure database persistence for various database types, including DB2, Microsoft SQL Server, Informix, and Oracle. See the following topics for details about each type of database.

This topic describes how to create configuration XML files that map a widget's endpoint binding dependencies to URLs. Endpoint bindings are used to resolve URLs dynamically at run time in order to prevent users from getting connection errors when the service is unavailable. Endpoint bindings are ...

This topic describes how administrators can publish widgets to the catalog from the mashup builder.

This topic describes how to change the frequency of session and LTPA token timeouts.

When you configure Microsoft® SQL Server 2005 or 2008 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 to import the default Mashup Center widgets into the catalog when Lotus® Mashups and MashupHub are not installed on the same machine.