Custom launch steps

To set up a custom launch, you must specify the templates and services to which the custom launch applies, know the parameters that you want the service to pass to your target application, the parameters that can be accepted by the target application, and also the format in which these parameters must be provided. The steps for creating a custom launch are outlined in this topic.

Procedure

  1. Select the templates and services to which the custom launch applies. You can choose to apply a custom launch to existing templates and services in your installation, or you can choose to apply the custom launch to all templates and services. For more information, see the Displaying a new launch action in the standard view definitions section of this document.
  2. Create a customized view definition that allows you to map personalized actions. For more information, see the Creating and Editing View Definitions section of this document.
  3. Edit the customized view definition to add the custom launch URL and specifications. These launch actions are added to the right-click menus displayed in the Service Editor or Service Viewer portlet. For more information, see the Creating launch actions and Enabling service attributes. section of this document.
    Note: The changes to the view definition do not affect the right-click menu that is displayed in the Service Navigation portlet.
  4. If the custom launch URL uses attributes from the service model to pass instance information to the target application, enable the usage of those attributes in the view definition.
    Note: You must manually edit XML files, stored in the database, to allow custom launch actions to be added to the right-click menus displayed in the Service Tree. For more information, see the Extending custom launch actions beyond view definitions section of this document. For information about export and import commands, see the TBSM Administrator's Guide.
    Note: The instructions in this procedure assume that you are already logged into the Dashboard Application Service Hub console with a user ID that has a roles of tbsmAdminUser and tbsmViewDefinitionAdmin assigned to it. The tbsmAdminUser role is required so that you can access the Service Administration and Service Configuration pages. The tbsmViewDefinitionAdmin role is required so that you can edit view definitions.