Note that the servlet version will determine the choice of target servers that appear in the drop-down list.
Check the Create portlet subclass check box to create a subclass of com.ibm.faces.webapp.WPFacesGenericPortlet (or com.ibm.faces.webapp.FacesGenericPortlet if the portlet uses the JSR 168 API), using the common class and package name prefixes previously defined in the wizard, and insert method stubs that call the super implementation. You can customize the portlet class as you choose.
View mode is initially selected by default, but can be deselected. For each mode that is selected (including View) you can specify an Initial page other than the default, which is built using the project name. The Initial page field takes a path specification, relative to the Web Content folder (for example, if you type /folder/subfolder/TestView.jsp, TestView.jsp would be created in the /WebContent/folder/subfolder directory. Folders that do not currently exist will be created. The leading "/" is optional.
From the Model drop-down list, you can select either Portlet, for a standard Faces portlet JSP file, or Portlet with client-side data caching to add the Faces Client Framework feature to the project, along with the appropriate taglib directive in the JSP file.
The specified initial JSP files are created and the corresponding <config-param> (for an IBM portlet) or <init-param> (for a JSR 168 portlet) values are automatically generated in portlet.xml when you complete the wizard. To add additional modes after you create the portlet, the configuration parameters must be specified using the Portlet Deployment Descriptor editor.