|
|
Within content management, the development phase covers both creation of content as well as delivering that content to your portal users. Using the Portal Administration Console, content contributors add content to the content repository using workflows and versioning. Using Workshop for WebLogic, developers use to incorporate content within the portal by using personalization tools such as content selectors and placeholders. Developers can also display content with JSP tags, controls and the content API.
Part II includes the following chapter:
Content and portal developers can use these features to deliver content to your portal by performing some of the following tasks:
The decisions you made during the architecture phase shape what you do in the development phase. For example, content contributors create content according to the repository hierarchy and content types you have already put in place.
When you finish the development phase you can proceed to the staging phase. Consider setting up a common development environment for the development phase and the staging phase. You might move iteratively between these two phases, developing and then testing what you created.
If you moved on to the production phase and then go back to make changes that affect the development phase, you must redeploy your portal application in order to view your changes. The BEA Propagation Utility performs the redeployment; see the BEA WebLogic Portal Production Operations User Guide for more information.
For a detailed description of the development phase of the portal life cycle, see the BEA WebLogic Portal Overview. The portal life cycle is shown in the following graphic:
|