Web Dynpro ABAP Applications with CAF Guided Procedures 

The use of Web Dynpro ABAP applications in the CAF Guided Procedures framework is restricted.

 Web Dynpro ABAP applications can only be integrated as self-contained steps in a Guided Procedure. Each individual application is closed using a button defined by the GP framework, without any data exchange between the Web Dynpro ABAP application and the GP framework. A data exchange between the steps of the Guided Procedure, that is, between individual WDA applications, can only be implemented in the database in the ABAP back end.

Prerequisites

Authorizations

The CAF Guided Procedures is a fixed component of a NetWeaver Portal. Both the design environment to create Guided Procedures and the tool to start a process can be found in the portal on the Guided Procedures tab page. Guided Procedures require a separate set of Portal Roles as a self-contained concept. Authorizations of the individual roles extend from the actual execution of processes, the creation and management of these processes, through to the administration of the necessary back end systems. You should ensure that you have sufficient authorization for the tasks you want to do.

End Points

To integrate a WDA application into a Guided Procedure and to the application, the J2EE Engine of your NetWeaver portal must be connected to an ABAP back end system. Guided Procedures use end points to open this connection. An end point is a defined point in the GP framework through which a Guided Procedure can use an external service. There must be at least one end point configured for each ABAP back end system you want to access. Each end point has a unique alias that can be chosen when a Guided Procedure is created. If no end point has been configured in your system for the ABAP back end you require, you must first create one.

 

 To Configure End Points you need administration authorization within the GP framework. You must therefore be assigned an appropriate role.

 

In the administration work set of the GP framework you have two options to configure an end point.

 

●      SLD-defined connection

●      User-defined connection

 

SLD-Defined Connection

In a productive NetWeaver environment you will normally find an SLD connection set up for the ABAP back end you are using. If one is, you have to define the following names in the configuration of the end point:

 

○       Name of the end point alias:

You can choose this name, if applicable, following the naming conventions for your project.

○       Name of the SLD connection

Here you enter the name of the JCo destination defined in the Web Dynpro Content Administrator. To view existing JCo destinations and to create new ones, you need to have administrator authorization for the portal. Without portal administration authorization it is not possible to view existing destinations. Contact your portal administrator.

 The Web Dynpro content administrator is not the same as the Content Administration tab page of the portal.

If there is no appropriate JCo destination available, you can create one. To do this, the required back end system must have been specified in the SLD as the technical system. If this is not the case, also contact the administrator of the SLD.

 

User-Defined Connection

The user-defined connection is intended solely for test purposes. You can directly access an ABAP back end system, though you must enter a user and password.

 

Guided Procedures with Web Dynpro ABAP

Provided that all administrative prerequisites are fulfilled, you can create the elements required for one guided procedure and merge them together into a procedure. You can find a detailed description in the documentation Developing Composite Applications with CAF GP.