The chapter describes what system administrators must do, after installation, to get Portal Framework applications up and running. Portal Framework applications are portal applications built using the WebCenter Portal Framework application template in Oracle JDeveloper.
The chapter includes the following topics:
Section 4.1, "Installing Oracle WebCenter Portal and the WebCenter Portal Framework Libraries"
Section 4.2, "Deploying Portal Framework Applications for the First Time (Roadmap)"
Permissions:
To perform the tasks in this chapter, you must be granted the following roles:
WebLogic Server: Admin
role granted through the Oracle WebLogic Server Administration Console.
Users with this role are also known as Fusion Middleware administrators.
Portal Framework application: Administrator
role granted through the Administration Console.
Users with this role are also known as Portal Framework administrators.
See also, Section 1.8, "Understanding Administrative Operations, Roles, and Tools."
Oracle WebCenter Portal's out-of-the-box portal application "WebCenter Portal" requires some special administration tasks that your own Portal Framework applications do not. To see a comprehensive list of these tasks, refer to Chapter 2, "Getting WebCenter Portal Up and Running."
Oracle WebCenter Portal installation is described in Oracle Fusion Middleware Installation Guide for Oracle WebCenter Portal.
Oracle JDeveloper installation, required for building Portal Framework applications, is described in Oracle Fusion Middleware Installation Guide for Oracle JDeveloper.
Portal Framework applications can be deployed to any WebLogic Server instance that is provisioned with WebCenter Portal's Framework shared library files. For details, see, Section 42.1.4, "Creating a Managed Server."
The roadmap in Table 4-1 outlines the tasks that a system administrator must perform to deploy a Portal Framework application, and get it up and running.
Note:
Oracle WebCenter Portal's out-of-the-box portal application "WebCenter Portal" requires additional administration tasks that other Portal Framework applications do not. To see a comprehensive list of these tasks, refer to Chapter 2, "Getting WebCenter Portal Up and Running."
Table 4-1 Roadmap - Getting Portal Framework Applications Up and Running for the First Time
Step | Documentation | Role |
---|---|---|
Step 1 - Verify your Oracle WebCenter Portal installation |
Verify your Oracle WebCenter Portal installation and settings. See: |
Fusion Middleware Admin |
Step 2 - Launch Fusion Middleware Control |
Launch the Fusion Middleware Control Console, a Web-based management tool for WebCenter Portal applications. See: Learn about the command-line administration tool WLST. See Section 1.13.3, "Oracle WebLogic Scripting Tool (WLST)." |
Fusion Middleware Admin |
Step 3 - Deploy the Portal Framework application |
Create a suitable container in which to deploy the Portal framework application archive: See also, Section 42, "Deploying Portal Framework Applications." |
Fusion Middleware Admin |
Step 4 - Reconfigure back-end servers |
Reconfigure back-end server connections, if required, through Fusion Middleware Control. |
Fusion Middleware Admin |
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
Step 5 - Connect to an identity store |
Ensure that your identity store is installed, configured, and contains all the required user data. See: See also Oracle Fusion Middleware Application Security Guide. |
Fusion Middleware Admin |
Step 6 - Restart the managed server |
Restart the managed server on which the application is deployed. See: |
Fusion Middleware Admin |
Step 7 - Verify Portal Framework application configuration |
Login to the application to verify the configuration: identity store, tools/services, applications, and so on. |
Portal Framework Application Admin |
Step 8 - Perform administrative tasks through the application's Administration Console |
Perform administrative duties:
See: Administering Portal Framework Applications Using the Administration Console |
Portal Framework Application Admin |