Show TOC

Background documentationSAPWebDynproLauncher Locate this document in the navigation structure

 

You can use SAPWebDynproLauncher to launch an WebDynpro for Java applications.

Provider specific Information

SAPWebDynproLauncher is provider agnostic. Items may belong to any connector.

Supported Actions

Action name can be anything.

Properties

SAPWebDynproLaucher expects the following properties:

  • WebDynproApplication (mandatory)

    Application name of the Web Dynpro to be launched.

  • WebDynproDeployableObject (mandatory)

    Namespace of the Web Dynpro to be launched

  • System (optional)

    A system alias of the system in the portal system landscape, where to launch the Web Dynpro. Default is the system where the work item originated.

  • DynamicParameter (optional)

    Dynamic parameters (name/value pairs, separated by &) to be passed the Web Dynpro application.

  • DebugMode (optional)

    The values are true and false.

All other properties will be passed as name=URL encoded value to the WebDynpro application.

Example

Following is the definition of an action that launches a Web Dynpro application WebDynproConsole with the dynamic parameters fruit=apple&vegetable=potato:

Syntax Syntax

  1. <Action name="launchWebDynPro" handler="WebDynproLauncher">
  <Properties>
    <Property name="WebDynproApplication" value="WebDynproConsole"/>
    <Property name="WebDynproDeployableObject" value="sap.com/tc~wd~tools"/>
   <Property name="fruit" value="apple"/>
   <Property name="DynamicParameter" value="vegetable=potato"/>
  </Properties>
 </Action>
End of the code.

Caution Caution

This WebDynpro application will be launched on the SAP NetWeaver Application Server configured for your back-end system where the work item originated. For example, if your work item belongs to the system MY_SAP_R3, and the SAP NetWeaver Application Server for MY_SAP_R3 is defined in the portal system landscape as myWASserver:serverPort, then the application is launched as http://myWASserver:serverPort/webdynpro/dispatcher/sap.com/tc~wd~tools/WebDynproConsole?vegetable=potato&fruit=apple If your WebDynpro application is not deployed on that server you have to configure the action as following. Define another system in the portal system landscape, for example, MY_SAP_R3_WD. Then set the SAP NetWeaver Application Server of that system to be the SAP NetWeaver Application Server where your Web Dynpro application is deployed. And add the System property to the Action definition:

End of the caution.

Syntax Syntax

  1. <Action name="launchWebDynPro" handler="SAPWebDynproLauncher">
  <Properties>
    <Property name="WebDynproApplication" value="WebDynproConsole"/>
    <Property name="WebDynproDeployableObject" value="sap.com/tc~wd~tools"/>
   <Property name="fruit" value="apple"/>
   <Property name="DynamicParameter" value="vegetable=potato"/>
    <Property name="System" value="MY_SAP_R3_WD"/>
  </Properties>
 </Action>
End of the code.

To launch the Web Dynpro application on the portal use SAP_LocalSystem:

Syntax Syntax

  1. Action name="launchWebDynPro" handler="SAPWebDynproLauncher">
 <Properties>
  <Property name="WebDynproApplication" value="WebDynproConsole"/>
  <Property name="WebDynproDeployableObject" value="sap.com/tc~wd~tools"/>
  <Property name="fruit" value="apple"/>
  <Property name="DynamicParameter" value="vegetable=potato"/>
  <Property name="System" value="SAP_LocalSystem"/>
 </Properties>
</Action>
End of the code.

The item types for launching the Web Dynpro applications can be configured in two ways.

  • Via Configuration XML

    Syntax Syntax

    1. ItemTypes>
 <ItemType name="uwl.task.webflow.TS91100019" connector="WebFlowConnector"
    defaultView="DefaultView" defaultAction="launchWebDynPro">
  <ItemTypeCriteria connector="WebFlowConnector" externalType="TS91100019"/>
  <Actions>
   <Action name="launchWebDynPro"  handler="SAPWebDynproLauncher">
    <Properties>
     <Property name="WebDynproApplication" value="MyApplication"/>
     <Property name="WebDynproDeployableObject" value="sap.com/tc~wd~tools"/>
     <Property name="DynamicParameter" value="wi_id=${item.externalId}"/>
    </Properties>
   </Action>
  </Actions>
 </ItemType> 
</ItemTypes>
    End of the code.

  • Via backend visualization transaction SWFVISU for visualization type Java WebDynpro. The table below summarizes the mapping between the launcher parameters and the visualization parameters.

    Launcher Parameter

    Visualization Parameter

    WebDynproApplication

    APPLICATION

    WebDynproDeployableObject

    PACKAGE

    DynamicParameter

    DYNPARAM

    System

    SYSTEM_ALIAS

    The default action will be set to launchWebDynpro.

    Note Note

    The UWL system configuration page includes a Web Dynpro system field, which can be used to configure the system alias of Web Dynpro application. For example, the UWL is configured for system alias ALIAS1 that has SAP NetWeaver Application Server NWAS1, and the Web Dynpro applications for work items coming from system ALIAS1 have to be launched against SAP NetWeaver Application Server NWAS2. For this situation a new system alias ALIAS2 should be defined with SAP NetWeaver Application Server NWAS2, and in the UWL configuration page the Web Dynpro system field for system ALIAS1 should be filled with ALIAS2. If System parameter is present for the action in the item type XML configuration or SWFVISU it will take precedence.

    If the default action you want to use (action triggered by clicking on the subject line) is not launchWebDynPro, you have to use XML configuration.

    Above all the references to System mean system alias defined in the portal system landscape.

    End of the note.