After editing a widget, for example by editing the widget definition file or by editing a widget WAR file using the WebSphere Application Server administrative console, the Mashup Center server will not recognize those changes automatically. This topic describes how to run the correct configuration task to make those changes effective on the server.
In a High Availability environment, updating the widget definition on one host is sufficient. Before you run the following commands, confirm that the MashupCenter_install_root/Config/config.properties
file is set up correctly and that the MashupCenter_install_root/mm_profile/properties/portdef.props
file points to the correct server ports.
To update the widget on the server, run either of the following commands:
- For Unix-based systems, run config.sh update-widget-reference -DwidgetURL=URL_of_definition_file
- For Microsoft Windows systems, run config.bat update-widget-reference -DwidgetURL=URL_of_definition_file
In the commands above, the URL_of_definition_file
variable refers to the URL of the widget definition file. The URL can either be a relative URL or an absolute URL to a widget. An absolute URL is allowed only when the widget is located on a different server. If an updated web module contains multiple widget definitions, then run the configuration task for each widget definition file that you have modified.
Also, be sure to specify the administrator's password for the MashupPass
parameter in the MashupCenter_install_root/Config/config.properties
file, for example MashupPass=passw0rd
Parent topic: Administering widgets and gadgets