This chapter discusses techniques for manually configuring and extending a WebCenter Portal: Framework application. This chapter includes the following sections:
This section discusses how to manually configure a WebCenter Portal: Framework application by adding or removing technology scopes.
Framework applications are comprised of a collection of project technologies and features or technology scopes. Each scope has associated libraries that provide specific features to the application. You can manually add or remove technology scopes to manually configure your application. For example, you may wish to remove some components from your Framework application that you know you will never use.
You can add or remove technology scopes (and their associated libraries) in the following ways.
First, you can modify the defaults when you create a new application. Figure 6-1 shows the list of available and selected technology scopes presented in the Create WebCenter Portal – Framework Application wizard. The scopes in the Selected column indicate the default set of technology scopes that comprise a framework application. For more information on this wizard, see Section 5.2, "Creating a Framework Application."
You can also adjust technology scopes in the Project Properties dialog. Select Project Properties from the Application menu. Then, select Technology Scope from the tree. The dialog lets you move project technologies in and out of the project, as shown in Figure 6-2.
Click on a scope in the dialog to display a short description at the bottom of the dialog.
When you create a Framework application using the Create WebCenter Portal – Framework Application wizard, you have one other opportunity to determine the default configuration of the application that is created, and its technology scopes. The final screen of the wizard includes a checkbox labeled Configure the application with standard Portal features, shown in Figure 6-3.
Checked by default, this option tells the wizard to add the Oracle WebCenter Portal: Framework features, like navigations, page hierarchies, delegated administration, and so on, to the application. If you uncheck this box, your application will not include these features. Essentially, you will create an application that is functionally equivalent to a WebCenter PS2 (WebCenter 11g Release 1 220.127.116.11.0) application.
Table 6-1 lists the default technology scopes and libraries that are included with applications created with the WebCenter Portal – Framework Application template. The Oracle WebCenter Portal: Framework technology scope is the only scope that is portal-application specific. This scope provides navigations, page hierarchies, delegated administration, and the rest of the portal features described in Chapter 9, "Understanding Framework Applications."
The Oracle WebCenter Portal: Framework technology scope is added by default to an application created with the Framework application template. The Framework application creation wizard gives you a chance to omit this technology scope if you unselect the Configure the application with standard Portal features checkbox in the Framework application creation wizard (Figure 6-3). In this case, you will create an application that is functionally equivalent to a WebCenter PS2 (WebCenter 11g Release 1 18.104.22.168.0) application.
|Default Technology Scopes||Associated Libraries|
ADF Page Flow
Instant Messaging and Presence (IMP) Service
JSP and Servlets
Oracle WebCenter Portal's Composer
WebCenter Portal – Framework
Portlet Bridge Service
WebCenter Portal's Customizable Components
WebCenter Portal: Services
ADF Faces Runtime 11
ADF Common Runtime
ADF Web Runtime
MDS Runtime Dependencies
Commons Beanutils 1.6.1
Commons Logging 1.0.3
Commons Collections 2.1
ADF Page Flow Runtime
ADF Controller Runtime
When the Configure the application with standard Portal features checkbox is selected in the Framework application creation wizard (Figure 6-3), the Oracle WebCenter Portal: Framework technology scope is added to the application in addition to the rest of the application technology scopes. If you were to unselect this checkbox, the Oracle WebCenter Portal: Framework technology scope would not be added.
This case is not supported. If you want to create a Framework application, you must start with the WebCenter Portal: Framework Application template. For details, see Section 5, "Creating Framework and Portlet Producer Applications."
One possible solution is to create a new Framework application, then turn your existing Framework application into an ADF Library. Then, include the ADF Library in the WebCenter Portal: Framework Application.
The recommended best practice for migration is to create a new (PS3) Framework application using the WebCenter Portal: Framework Application template and then manually migrate the content, configurations, and logic from your old PS2 application to the new framework application. If it is not possible to follow this recommended practice, then follow the procedures described in Appendix H, "Manually Migrating a Framework Application."
Another possible solution is to create a new Framework application, and then turn your existing Framework application into an ADF Library. Then, include the ADF Library in the Framework application.
If your business requirement is to create a non-Framework application, say a Fusion web application, but you want to also include WebCenter capabilities in that application, you can do so by adding the required technology scopes and libraries. For example, you could add features like web services, task flows, and search to the application.
You cannot create a Framework application simply by adding the Oracle WebCenter Portal: Framework technology scope to a non-portal application. This use case is not supported, as explained in Section 6.1.5, "Can I Create a WebCenter Portal: Framework Application by Adding the Oracle WebCenter Portal: Framework Technology Scope Later?."
The technology scopes limit user interface options to those appropriate to the type of application project you are building. The libraries provide the components and elements useful in constructing application content. You can extend an existing application to integrate content from various repositories, create portlets, or consume portlets and WebCenter Portal services. You can extend ADF applications from the current release or from a 10.1.x.x release.
While extending your application, you may decide to create projects that are optimized for specific WebCenter capabilities. This section steps you through the process of manually creating projects like those provided with the WebCenter templates and adding the required technology scopes and libraries to projects.
Open your application.
Click Yes if you are prompted to migrate your application settings.
If you migrated a 10.1.3.x Framework application, then the application continues to have the Model, ViewController, and Portlets projects.
Optionally, create new projects for defining the application data model, consuming content, or creating portlets:
In the Application Navigator, right-click the application and select New Project from the context menu.
In the New Gallery, expand General, select Projects, then Generic Project, and click OK.
In the Create Generic Project wizard, in the Project Name field, enter a name for the project.
In the Directory field, specify the directory path for storing the project or accept the default path.
Click Finish to create the new project.
In the left side of the dialog, select Technology Scope.
In the Project Technologies part of the dialog, add the required technologies and libraries depending on which WebCenter-related capabilities you want to enable in the selected project. See Table 6-1 for a complete list.
Save your work.
Follow this procedure if you have an existing WAR file you want to import into your application environment through JDeveloper. Once the project is imported, you can configure it with WebCenter Portal features manually, as described in Section 6.1, "Manually Configuring a Framework Application With Technology Scopes."
Connection information is stored in the application-level EAR file and is not automatically imported with a project-level WAR file. Therefore, when you import a project-level WAR file, you must reconfigure any connections upon which the application relies.
Right-click your application in the Application Navigator, and choose New Project from the context menu.
In the New Gallery, expand General, select Projects, then Project from War File, and click OK.
Follow the wizard instructions to complete creating the project.
Right-click the newly created project in the Application Navigator, and select Project Properties from the context menu.
Add the required technology scopes and libraries depending on which WebCenter-related capabilities you want to enable in the selected project. For more information, see Section 6.1, "Manually Configuring a Framework Application With Technology Scopes."
Click OK to close the Project Properties dialog.