
This IT process describes the steps for preparing a portal to serve as an external-facing portal.
Prerequisites
Process Workflow
Set up the portal to accept anonymous users, and define the users and groups to which anonymous and self-registered users are mapped.
Select the content to be accessible to anonymous and self-registered users, and assign these users to the content.
To improve performance, the portal caches navigation hierarchies and nodes, so that the portal can retrieve the hierarchy from the cache instead of creating it for each request.
By default, caching is turned off. After the portal is set up and tested, turn on and configure caching by setting the appropriate J2EE parameters.
Create your own navigation iViews, or modify the default light navigation iViews to fit your company's needs. You can use the Navigation tag library to build JSP-based navigation iViews.
Replace the navigation iViews in the light framework page with your customized navigation iViews.
The Theme Editor includes styles that are used in the default light navigation iViews.
Using desktop display rules, assign the light framework page to anonymous and self-registered users, as well as other users who need it.
You can assign the framework pages based on the URL alias, role, or group, or the user's network bandwidth.
Results
You have set up an external-facing portal, and anonymous users can view content in the portal. Anonymous users can also register to view additional content.
The next steps in implementing an external-facing portal can be performed. For more information, see Creating External-Facing Portal Content .