Contributing an instance of a native application to the launcherAdded by IBM on October 4, 2010 | Version 1 (Original)
|You can create a new instance of the Native Application Administration portlet and configure it to represent the native application that appears on the launcher.
You can create a new instance of the Native Application Administration portlet and configure it to represent the native application that appears on the launcher.
To contribute an instance of a native application to the launcher, follow these steps.
- Make sure at least one Workbench Administration portlet is properly installed on WebSphere® Portal.
- Log on to WebSphere Portal using administrator's credentials.
- Click Administration under Product Links.
- Expand Portlet Management and click Portlets.
- Locate the portlet named Workbench Native Application Administration.
Tip: To quickly find the Workbench Native Application Administration portlet, select Title starts with in the Search by field and specify Rich Client in the Search field.
- Click the copy portlet icon to create a copy.
- Name your copy of the portlet as appropriate and click OK.
- Place the new copy on the Workbench Contribution Page.
- Click the Portal down-arrow and select Configure from the drop down menu.
- Configure the native application settings.
Table 1. Native application settings
|Label||Default label for the application. If an appropriate localizable value is not set for the label, this value is used. The label is what is displayed in the launcher as the application title. The ampersand (&) and double-quote (") characters are not allowed to be part of the label string.|
|Launcher path||Defines the location inside the launcher, where the application should appear. The launcher path is a hierarchical delimitation of the parent folders of the launcher item, separated by backslashes. Each element in the path corresponds to the name of a folder to be displayed in the launcher, leading from the root to the final launcher item.|
|Launch automatically at start up||If true, the application is started immediately after the launcher widget is loaded. If multiple applications are set to auto launch, there is no well defined order of execution.|
|Allow Multiple Instances||If true, then any attempt to launch an application more than once will result in multiple instances of the same application be opened. If false, then any attempt to launch more than one instance of the application will bring the existing application instance window to front, if it is still open.|
|Command||The command used to launch the application. A separate command is specified for running under windows and Linux®. The command includes the path to the executable image plus any additional parameters.|
|Working Directory||The working directory of the application, after startup.|
|Environment||The environment variable definitions available to the application.|
|Environment Mode||Controls how additional environment variable definitions will be merged with any existing environment variables:|
If the original environment contains a definition for var1 = A, and the new environment contains a definition for var1 = B, then the final environment contains the definition Var1 = A;BPrepend
If the original environment contains a definition for var1 = A, and the new environment contains a definition for var1 = B, then the final environment contains the definition Var1 = B;AOverride
If the original environment contains a definition for var1 = A, and the new environment contains a definition for var1 = B, then the final environment contains the definition Var1 = B;Replace
The new environment will completely replace the old environment. No merge is done.
|Set localizable values||The link will load a page similar to the following mockup, and allow the administrator to configure the localizable values for tooltip, launcher path, and label. Each row in the localization table defines a supported language, where each column displays a field that supports localized values. The list of supported languages depends on what languages the Portal installation supports. To enable your Portal installation for additional language support, refer to your IBM® WebSphere Portal manual.|
To enter localized values for a supported language, click the edit icon in the row corresponding to that language. In the Editing localized values screen, enter localized values for the selected language.
- Assign appropriate access permissions to the portlet. On the Administration navigation panel, expand Access and click Resource Permissions.
- In the Resource Types table, click Portlets.
- Locate the copy of the portlet created above, and click on the access permissions icon to assign appropriate permissions.
A new instance of the Native Application Administration portlet is crated and is configured to represent the native application that appears on the launcher.
Parent topic: Using the Workbench Administration portlet: XPD621