This guide explains how to build WebCenter Portal assets, extensions to WebCenter Portal Server, and shared libraries using JDeveloper. This guide provides in-depth information for all of the following tasks:
How to set up and prepare your development environment
How to build and deploy WebCenter Portal assets
How to build and deploy extensions to WebCenter Portal
How to build and deploy shared libraries that can be used in WebCenter Portal
For the portable document format (PDF) version of this manual, when a URL breaks onto two lines, the full URL data is not sent to the browser when you click it. To get to the correct target of any URL included in the PDF, copy and paste the URL into your browser's address field. In the HTML version of this manual, you can click a link to directly display its target in your browser.
This guide is written for a developer who provides support for WebCenter Portal applications. The developer is primarily responsible for developing assets (such as page templates, resource catalogs, skins, portlets, and task flows), which are published and leveraged by knowledge workers and application specialists. A developer primarily works with JDeveloper and creates WebCenter Portal Asset application and leverages one of three asset-related templates: the WebCenter Portal Asset template, the WebCenter Portlet Producer Application template, or the WebCenter Portal Server Extension template.
The chapters in Working with WebCenter Portal Assets explain how to develop assets such as page templates, resource catalogs, skins, portlets, and task flows. Several other parts of this guide also contain chapters devoted to working with assets such as portlets, pagelets, and shared libraries.
Tasks that are typical of a developer include:
Developing custom assets, like page templates and for portals in WebCenter Portal
Developing Java portlets
Modifying existing WebCenter Portal assets
Developing and deploying task flows, managed beans, and other custom components
Maintaining the source control system
Maintaining a build system
This guide also assumes that the audience has already read the guide Developing Fusion Web Applications with Oracle Application Development Framework and is familiar with the following technologies:
Oracle Application Development Framework (Oracle ADF) (purpose, basic architecture, basic development skills)
Oracle ADF Faces components
Oracle WebLogic Server
For more information, see the following documents in the Oracle Fusion Middleware 12c (184.108.40.206.0) documentation set or on Oracle Technology Network (OTN) at
The following text conventions are used in this document:
Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.
Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.
Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.