XhandlerLauncher

Provider specific Information

XhandlerLauncher supports WebFlowConnector Provider. Items must belong to the WebFlowConnector.

Supported Actions

Action name can be anything.

Properties

XhandlerLauncher expects one of the following two properties:

• xhandler_url

  URL for launching Launch Handler

• webservice_url

  URL for launching Webservice Handler

  Note The WebServiceLauncher may have the following optional property:

  • System

  This property should point to a portal system alias and when it is maintained, the current absolute URL property shall be used as relative path, appended to the extracted base URL. If this property is not maintained, the webservice_url value shall be treated as absolute URL.

All other properties will be ignored.

The following parameters are passed to the Launch Handler URL:

• wi_id - work item ID

• logsys - system alias, defined in the portal landscape, for the webflow system

• destination - the same as logsys

• task - task ID of the work item in the webflow system

• uname - user ID in the webflow system

• langu - two letter language code of the portal user URL

The following parameters are passed to the Webservice Handler:

• _sapwiid - work item ID

• _saplogsys - webflow system logical name

• _saptask - task ID of the work item in the webflow system

• _sapuname - user ID in the webflow system

• _saplangu - two letter language code of the portal user

Configuration for item types to use Launch Handler or Webservice Handler is done on the back end. Item types for XhandlerLauncher are defined in a webflow system. The table TASK_SF_INFO of URL_SERVER_TYPE_DATA_GET FM contains the information on the item type. If TCODE parameter of TASK_SF_INFO is $EXTSRV , then the item requires launching Launch Handler. A call to SWK_BUILD_LH_URL will get the xhandler_url parameter. If TCODE parameter of TASK_SF_INFO is $WEBSERVICE, then the item requires launching Webservice Handler. A call to SWLWP_COMP_GET_LH_URL will get the webservice_url parameter.