In this step you will set up the design environment for a Portal application. You will build your Portal using WebLogic Workshop, a visual tool for designing Portals.
You will also create a Portal project. Portal projects contain supporting resources for Portal web applications including JSP tag libraries, skins, and personalization tools.
The tasks in this step are:
If you are using a Linux operating system, follow these instructions.
$HOME/bea/weblogic81/workshop/Workshop.sh
sh Workshop.sh
When you create a new Portal Application, Workshop creates the file structure shown to the right.
The data folder contains a Datasync project. A Datasync project contains personalization services that can be used in Portals, including user profiles, events, session properties, campaigns, and others.
The Modules folder contains stand-alone applications (packaged as WAR and JAR files) that can help you develop and administer your portal. The primary application is the WebLogic Administration Portal (adminPortal.war), which is used to administer a Portal both at design time and runtime.
The Libraries folder contains resources commonly used in Portal applications, such as the User Provider Control, which lets you store and retrieve information about the current user of the Portal.
The Security Roles folder lets you define security roles and test users for your Portal. You can test the security design of your Portal by logging in as a test user.
When you create a new Portal project Workshop creates the file structure shown to the right.
The campaigns folder is provided as a convenient place to store your campaign rules. Campaigns let you target users with content (general web content, emails, advertisement, etc.) based on fine-grained rules. For example, a campaign can present a user with web advertisement based on the user's purchasing history, demographics, navigational patterns, or any number of criteria.
The framework folder contains resources for determining the look and feel of your Portal, including skins and themes.
The resources folder stores commonly re-used JSP elements, including CSS files and JSP templates.
The visitorTools folder stores an application that lets users set their own Portal preferences. If you wish, you can include this application in your Portal.
The WEB-INF folder stores JSP tag libraries, configuration files, compiled class files, and other runtime resources.
The Controller.jpf, error.jsp, and index.jsp are the components of the default parent page flow. You may use this page flow as the master error handler and/or the master navigational controller for other page flows in your portal.
In order to run and test your Portal application, it must first be deployed on WebLogic Server. For convenience you will start WebLogic Server now, so that you can test your Portal as you design it.
You can confirm whether WebLogic Server is running by looking at the status bar at the bottom of WebLogic Workshop. If WebLogic Server is running, a green ball is displayed.
If WebLogic Server is not running, a red ball is displayed.
You are now ready to begin designing your Portal.
Click one of the following arrows to navigate through the tutorial: