Contents: Administering Mashup Center : Mashup Center 2.0
When you want to update your users' personal palettes, for example 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 a page for editing.
Before you begin
Before you begin, take a moment to understand how users' default palettes are loaded and how you can configure changes at a global level. In the root directory where Mashup Center is installed, locate catalog_default.xml and catalog_template.xml in the mm/config directory. The catalog_template.xml file is the catalog file that initially gets loaded when users log into Mashup Center and open a page for editing. Notice how this file contains an include
tag that calls the catalog_default.xml, which is the default catalog that defines the users' default palettes. When you want to make new widgets available on all your users' palettes, you can create a new catalog file and simply add a new include
tag to the catalog_default.xml file so that the new catalog file gets picked up along with catalog_default.xml during the palette loading process. Note that every time you make a change to a catalog file, you must use the import-config-file
command to re-import the file into the WebSphere Application Server WCCM service.
To configure a global palette for users, do the following steps:
- Create a new XML file that uses the same schema as catalog_default.xml. This file is located in the Mashup_Center_root/mm/config directory, where Mashup_Center_root is the name of the directory where Mashup Center is installed.
- Update the new XML file to contain any changes that you want to make to your users' palettes.
- Name the XML file catalog_name.xml, where name is the name that will be used in the catalog attribute of the include tags.
- Save the new XML file and keep note of the directory. You will need to specify the absolute path to this directory in a later step.
- Open catalog_default.xml, and add an include tag for the new catalog XML file.
- If you want to include the entire catalog, insert the include tag at the same level as the categories, for example:
Note: In this example, the catalog file that you are including is named catalog_NewCatalog.xml.
- If you want to add widgets to an existing category, you can nest the include tag inside the category name tag, for example:
<include catalog=“anotherCatalog” category=“stuff”/>
- Save the file.
- Run the config.sh import-config-file command to import both your new catalog file and optionally the catalog_template.xml file into the WebSphere Application Server WCCM service: Note that you will need to re-import these catalog files every time that you make additional changes.
Note: In this example, the catalog file that you are including is named catalog_NewCatalog.xml and is located in the Mashup_Center_root/mm/config/ directory. If you saved your catalog file to a different directory, the command should contain an absolute path to that directory.
Note: These commands are for Unix-based platforms. If you are using a Microsoft Windows platform, the file extension is BAT.
- Optional: If you change catalog_template.xml, then you must reset the default palette in order for users to see the updates. Logged in an WebSphere Application Server administrator, open http://servername:port/mum/osgi/defaultPaletteReset. If you do not complete this step, only new users will see your palette updates.
- Restart the Mashup Center server.
Parent topic: Configuring the palette for users : Mashup Center 2.0