19 Managing Portlets in Production

During the life cycle of a WebLogic Portal application it moves back and forth between development, staging, and production environments. This chapter contains information about managing portlets that are on a production system.

This chapter contains the following sections:

• Section 19.1, "Pushing Changes from the Library into Production"

• Section 19.2, "Transferring Changes from Production Back to Development"

19.1 Pushing Changes from the Library into Production

Proliferation is the process by which changes made to the Library instance of a portal asset are pushed into user-customized instances of that asset. For example, if a portal administrator deletes a portlet from a desktop, that change must be reflected into user-customized instances of that desktop.

The WebLogic Portal Administration Console includes a configuration setting for Proliferation under Configuration Settings > Service Administration > Portal Resources. The proliferation settings include synch, asynch, and off.

For more information on proliferation, refer to the Oracle Fusion Middleware Production Operations Guide for Oracle WebLogic Portal.

19.2 Transferring Changes from Production Back to Development

WebLogic Portal utilities such as the propagation tools and the Export/Import Utility allow you to reliably move and merge changes between environments. The Export/Import Utility allows a full round-trip development life cycle, where you can easily move portals from a production environment back to your Oracle Enterprise Pack for Eclipse development environment.

For instructions on using the propagation tools and Export/Import Utility, refer to the Oracle Fusion Middleware Production Operations Guide for Oracle WebLogic Portal.