Setting up a Web Dynpro Application for a Logon Ticket 

You want to configure a Web Dynpro application that receives data from a SAP system with an adaptive RFC model so that it logs onto the SAP system with the user’s logon ticket.

JCo Destinations

If you use an adaptive RFC model in a Web Dynpro application, two JCo destinations are automatically created in the Web Dynpro Content Administrator. You must maintain these JCo destinations with this tool.

●      Over the first connection the Web Dynpro application receives the metadata, which is not user-specific, but the same for all users. You have to make it available to all users. Technical name of the destination: WD_MODELDATA_DEST.

●      With the second connection, the Web Dynpro application receives the application data, which is normally user-specific. Technical name: WD_RFC_METADATA_DEST.

When you create JCo destinations, you can also give them different names. When the data for further adaptive RFC models is loaded from other SAP systems, you may not use the default names; you must define unique names for the JCo destinations.

The JCo destinations are displayed in the Content Administrator when you select the corresponding development component or local Web Dynpro application in the Browse and Search Area.

Prerequisites

●      You have administrator rights for the Java Engine or for the SAP NetWeaver Portal you are using.

●      You set up the SAP system so that the logon tickets that are sent by the Web Dynpro application are accepted. These logon tickets can be issued by either the Java Engine on which the Web Dynpro application was deployed or another system, such as an NW Portal.

●      The Web Dynpro Content Administrator is running.

Procedure

...

       1.      Select the required development component or local Web Dynpro application in the corresponding level in the Browse and Search Area. The first level local contains all the locally deployed Web Dynpro applications. The second level contains all the development components and is specified with the vendor name, e.g. sap.com.

       2.      In JCO Connections select the JCo destination you want to maintain and choose Edit in the detailed view.

       3.      You have to specify the maximum pool size and the client. Depending on the pool size a specific number of connections that can be opened at runtime is permitted.

       4.      You can define the SAProuter string as well as the message server.

       5.      If you select Ticket as the authentication method, the logon of the user is sent for authentication to the SAP system. When defining the JCo destination for metadata, only authentication method User/Password is supported.

The user is predefined for authentication method User/Password and cannot be changed. This user is a technical user who does not need dialog authorization. The name and password assigned to this user must be known in the back end. The authorizations for this user must be set in the back end so that this user can access all DDIC function modules.

       6.      Follow the same steps for the second JCo destination.