While developers build portal functionality in the development phase, administrators and developers perform tasks at the staging phase.
In the staging phase, you get your portal application ready for public consumption. You assemble, configure, and test the application, then deploy it to the production environment when it is ready for public consumption.
Using the WebLogic Portal Administration Console and resources created by the development team, you perform tasks such as:
- Creating desktops
- Creating desktop and community templates
- Creating content and content types
- Creating administrative users
- Creating delegated administration roles and applying them to resources
- Creating visitor entitlement roles and applying them to portal resources
- Modifying interaction management rules
- Connecting WebLogic Portal to external security and content providers
- Configuring services such as behavior tracking and campaign e-mail
- Modifying cache settings to ensure optimum performance.
- Testing the application and deploying it to the production environment
The primary tools used in this phase are the WebLogic Portal Administration Console,
the WebLogic Portal Production Operations Tools (to move database and LDAP data between
staging, development, and production), WebLogic Server application deployment tools, and
any external content or security providers you are using.
The staging phase overlaps with the development phase. Because development code and resources are often dependent on database and security data, such as content, users, and security roles, development occurs in parallel with staging where database and security data are populated. The staging environment provides a single location for all developers to share the same resources. The overlap between phases also allows iterative application testing.
The following guides detail staging considerations within the portal life cycle: