Using the standard Web Dynpro iView template, or your specific iView template, define your Web Dynpro iViews.
1. Switch to the content catalog and select the folder that contains your new Web Dynpro iView. Use the context menu and select New → iView.
2. The Web Dynpro iView Wizard is displayed in the right window. Choose the SAP Web Dynpro iView template or the template you created (see Create a Web Dynpro iView Template).
3. In Step 2 of the Web Dynpro iView Wizard, you have to specify the iView Name and iView ID. The the iView Name is displayed as title of the Web Dynpro iView. The iView ID is the technical name and the iView ID Prefix can be used to define your own namespace. You can also specify the Master Language and the description of the iView.
4. In Step 3 of the Web Dynpro iView Wizard, choose the application variant of the iView. You can choose between a Web Dynpro Java or a Web Dynpro ABAP application.
5. In Step 4 of the Web Dynpro iView Wizard you have to specify the Web Dynpro-specific parameters.
Specify the system alias of the system you want to use for your Web Dynpro application. In SAP NetWeaver every Web Dynpro-based iView runs isolated on a page. The iView uses a specific Web Dynpro application URL to start the Web Dynpro application. The system definition is needed to compute the URL.
A system alias has to exist for every SAP NetWeaver installation to run a Web Dynpro application. If your Web Dynpro application runs on the same installation as the portal itself, you can use the predefined system alias SAP_LocalSystem.
Currently, there is no system type definition available for a SAP NetWeaver installation. Therefore, you must use one of the available SAP backend system types. You have to define only the WAS hostname and WAS Protocol parameters in the system definition. The WAS hostname must be in the form: <host>.<domain>:<port>.
To define and maintain your system entry, navigate to System Administration → System Configuration → System Landscape.
A system alias has to be defined for your system. Only the system alias is visible in the list of available systems. You can define more than one alias if necessary.
Define the namespace containing your Web Dynpro application. The semantic behind this namespace depends on the used Web Dynpro variant:
Using a Web Dynpro Java application, the namespace is the name of the used development component or the name of the Eclipse project defining the Web Dynpro Java application.
If you do not use JDI/DTR, you have to specify the Eclipse project defining your Web Dynpro Java application. Make sure that both a development component name and the Eclipse project name contain the vendor name. Possible values are sap.com/tc~wd~tools (for a development component) or local/MyTestProject for an Eclipse project.
Using a Web Dynpro ABAP application, the namespace is the development class of the Web Dynpro application.
The specified namespace is the same name as displayed in the SAP WebAS console using the LIST_APP command or as used in the Web Dynpro application URL.
c. Application Name
The application name is the name of the Web Dynpro application, for example MyTestApplication
d. Application Parameters
If your Web Dynpro application has startup parameters, you can define specific values for this iView.
Application has two parameters: par1 and par2
The parameters are specified as follows:
6. Now you can define the standard iView parameters with the iView Wizard. If you use the standard Web Dynpro iView template, your Web Dynpro iView has automatic resizing. If you want to define a fixed height or a full-screen iView, you have to adjust this parameter.
The Web Dynpro iView is now ready to use. You can add the iView to pages, worksets, or roles.