Configuration options for the mashups toolbox

To make additional widgets available to your users, you add them to the catalog.

For example, this can be the case when you deployed new widgets. To make these available to your users, you change configuration options for the mashups tool box in the portal.

Default toolbox content

The default toolbox entries are defined within an xml file that is stored as the value of the parameter mashups.catalog_template.xml in the portal WP Mashup Binary ConfigService Resource Environment Provider (REP) in the administrative console. The content of this property is a simple catalog represented in XML. By default it contains a single catalog level include to another catalog.xml that is stored in the same REP under the property mashups.catalog_default.xml.

As the only entry in the default toolbox is an include, none of the widgets within mashups.catalog_default.xml can be removed from a user's toolbox.

Catalog name resolution

A catalog that is part of an include statement must be represented in the Binary ConfigService.

The name of the property determines the catalog name referenced in <include> statements.

The property naming conventions follow the template mashups.catalog_some_category.xml where some_category is the actual name of the catalog. For example, an include statement such as this: <include catalog="newcatalog" /> requires a Resource Environment Provide (REP) property named mashups.catalog_newcatalog.xml to resolve correctly.

To modify the default catalog properties in the WAS REP, locate the XML source in the subdirectory PortalServer_root/base/wp.mmi.deploy/config/bianaries/catalogs. Modify them as desired, for example to add a new catalog include, and use the import-config-file to modify the WAS property. Then use the task import-config-fileto add the newly included catalog as a binary catalog.

Update and modifying the toolbox

To enhance the toolbox, update the catalog properties in the REP.

To do this...

1. Locate the XML source in the directory PortalServer_root/base/wp.mmi.deploy/config/catalogs.

2. Modify the file as required.

3. Run...
   following configuration

   :

   ConfigEngine.bat/.sh import-config-file -DMMImportFile="fully_qualified_filename" -DMMImportFilePropertyName="propertyname_in_WAS"

Example:

ConfigEngine.sh import-config-file -DMMImportFile="c:/catalogs/mycatalog.xml" -DMMImportFilePropertyName="mashups.catalog_custom.xml"

This example creates a REP property with the name mashups.catalog_custom.xml in the WP Mashup Binary ConfigService. Include statements need to reflect the catalog name of custom for this catalog as follows: <catalog include="custom" /> . You can also use this task to create new catalogs in the REP based on files that you have customized yourself. Again, be aware of the naming conventions for REP properties.

Parent topic:

Configure options for mashups in portal (optional)

---