Deploy a widget WAR file package to the portal
You can deploy a widget WAR file package directly to the portal.
To do this...
After deploying the widget, you can make it available in the global toolbox as described in the topic about Configuration options for the mashups toolbox.
- Ensure that the portal sever is running.
- Deploy the widget WAR file package to WAS.
Proceed as follows:
Note that when you install WAR files through the administrative console, specify a context root. This is used as a reference when you define widget in custom catalog. For instance, if you use widgets as context root, widget definition will look like this:
- Open the WAS administrative console for the portal.
- Select Applications -> Install New Application. Depending on version of WAS, the options you click might look slightly different.
- Use the default settings for the individual steps, but make sure to select WebSphere_Portal as the target server mapping.
- After the WAR file is installed, take a note of the application name in the Name column in the list of enterprise applications.
<definition>/widgets/your_Widget/your_Descriptor.xml</definition>
- Run the following task to register the WAR file:
ConfigEngine.sh register-mashup-module -DApplicationName=application_name -DWasPassword=foo -DPortalAdminPwd=foo
To deregister the widget, run the following task:
ConfigEngine.sh deregister-mashup-module -DApplicationName=application_name -DWasPassword=foo -DPortalAdminPwd=foo
Parent
Work with widgets
Configuration options for the mashups toolbox