Creating a cross-launch URL

As an administrator, you can create cross-launch URLs to enable IT operators to access other BMC or third party applications more easily. You can create dynamic URLs by specifying slot names in the URL. When accessed, the slot names are replaced with the slot values present in the event.

You can specify conditions that determine when the URL will be accessible to IT operators, based on the slot values present in the event. Specifying these conditions can make the cross-launch URL more relevant to the context of the event from where they are expected to be accessed.

Note that specifying slots in the URL is optional. 

The following information can help you understand the process of creating cross-launch URLs:

To create cross-launch URLs 

1. Log on to the TrueSight console as a super admin.

2. In the navigation pane, go to Administration > Cross-Launch URLs. 

3. Click Create Cross-Launch URL. 
   Alternatively, select Create Cross-Launch URL from the action menu  at the top of the page. 

4. Provide the following details and click Save.

   Field	Description
   Name	Provide a name to identify the cross-launch URL. Best practice: Ensure that you provide a meaningful name for the URL so that IT operators understand the application that they can expect to access or launch from the events. For example, to allow IT operators to access the cross-launch URL for the BMC Remedy with Smart IT application to view incident tickets, consider providing one of the following names: Launch BMC Remedy with Smart IT View incident details in BMC Remedy with Smart IT Note: The cross-launch URL name is unique to a tenant and the object from where the cross-launch URL is accesible (for example, events).
   Enable Cross-Launch	By default, this setting is turned on. If you do not want to allow IT operators to view and access this URL, turn off this setting. You might want to turn off this setting in the following scenarios: If you want to stop IT operators from accessing this URL during the application's maintenance window. If you want to capture URL details of various applications in advance so that IT operators can be provided access to them some time in the future.
   Launch From	By default, the URL is only accessible from events (on the Monitoring > Events page). This field is not editable.
   Tenants	Select the tenants that must have permissions to view and access the URL.
   URL Prefix (By Component)	(Optional) Select one of the registered components that you want to use as prefix in the URL. When you select the component, the URL field is automatically populated with the path to the component server. Thus, providing this input can help you easily create a URL to one of the registered component applications. Providing this input is optional. Note: While viewing the cross-launch URL, this field is not displayed. Furthermore, while editing the cross-launch URL, this field remains blank even if a value was selected.
   URL	Add the URL that must be accessible from events. You can create a dynamic URL by specifying slot names in square brackets in the URL. For example, http://hostName/[slotName]. When accessed, the slot names are replaced with the slot values present in the event. If you selected a URL prefix by component earlier, the path to the component server is automatically added in this field. You can modify the path to create a meaningful URL relevant to the event from where it is expected to be accessed. Note: You can specify HTTP or HTTPS URLs only. Unless you specify an HTTP or HTTPS URL, you cannot save the cross-launch URL. Example scenarios: Scenario: To add a URL for viewing details of the incident Inc04 in BMC Remedy with Smart IT, you can add the following URL with the slot, itsm_incident_id (referring to incident ID): URL syntax: http://smartITHostName:9000/ux/smart-it/#/search/[itsm_incident_id] Expected URL to be accessed by IT operator: http://smartITHostName:9000/ux/smart-it/#/search/Inc04 Scenario: To add a URL for viewing details of a CI in BMC Remedy with Smart IT, you can add the following URL with the mc_smc_id slot (referring to component ID) and the mc_smc_type slot (referring to component type). URL syntax: http://smartITHostName:9000/ux/smart-it/#/asset/[mc_smc_id]/[mc_smc_type] Expected URL to be accessed by IT operator: http://smartITHostName:9000/ux/smart-it/#/asset/df23g87sh1/BMC_DATABASE
   Method Type	Method type to be used for accessing the cross-launch URL via the HTTP or HTTPS protocol. Based on the method type with which the URL must be sent to the server to be accessed, select one of the following options: (Default) GET POST
   Show URL If	The following conditions can help you control the accessibility of the URL. These conditions can also help you make the URL more relevant to the event from where it is likely to be accessed. All slot values are present: Select this option if you want to make the URL accessible only when all the slot values are present in the event. At least one slot value is present: Select this option if you want to make the URL accessible when at least one slot value is present in the event. No slot values are present: (Default) Select this option if you do not want to specify any conditions related to slots for making the URL accessible. In other words, selecting this option will make the cross-launch URL accessible irrespective of the slot information included in the event. Note: If you do not specify any slot names in the URL, then irrespective of the preceding options selected, that URL will continue to be accessible from the selected event.

Where to go from here

Understand the process of editing and deleting cross-launch URLs. For more information, see Configuring context-aware cross-launch URLs.