Chapter 1. Getting Started Guide

Transcription

1 Chapter 1. Getting Started Guide This Getting Started guide proides an introduction to WebSphere Portal content publishing. The topics within the guide include: A product oeriew Where to get help and the components of the WebSphere Portal content publishing Help System Interface fundamentals A step-by-step tutorial Copyright IBM Corp

2 2 WebSphere Portal content publishing Help System

3 Chapter 2. Getting help WebSphere Portal content publishing is a browser-based product and works with Microsoft Internet Explorer 5.5 and higher or Netscape Naigator 6.2. The WebSphere Portal content publishing Help System may be iewed using a Jaa applet or in HTML. Use the Jaa and HTML buttons to switch iews. There are seeral ways to get help when using WebSphere Portal content publishing: Components of the Help System Support on the IBM Web site on page 4 Components of the Help System The WebSphere Portal content publishing Help System is diided into the following sections: Contents: Organized by subject, the Contents section enables you to browse for information. Subjects within the Contents section include: Getting Started Guide: The Getting Started Guide proides an introduction to WebSphere Portal content publishing, including a product oeriew, interface fundamentals, and a tutorial. User s Guide: Targeted for the end user (or business user), this guide contains conceptual, task-oriented, and reference information on how to use WebSphere Portal content publishing. Administrator s Guide: Targeted for the administrator, this guide contains conceptual, task-oriented, and reference information on how to configure and administer WebSphere Portal content publishing. Deeloper s Guide: Targeted for the deeloper (or programmer), this guide contains conceptual, task-oriented, and reference information most often needed by programmers deeloping tools that interface with WebSphere Portal content publishing. Migration Guide: This guide contains information about migrating WebSphere Personalization projects. It also contains information about the new LikeMinds programming model. Desktop Integration Guide: This guide contains information on how to use WebSphere Portal content publishing from a Microsoft Windows client system. Desktop Integration allows you to create and edit content while you are disconnected from the WebSphere Portal content publishing authoring serer. Appendices: The Appendices include: - AGlossary containing terms found in the documentation and on the WebSphere Portal content publishing user interface. - Accessibility information such as keyboard shortcuts, specifying fonts and colors, and general information about setting up your Web browser. - Notices and Trademarks. Index: The index points to subjects within the Help System. Copyright IBM Corp

4 Search: Use search to find information in the Help System. The search feature requires your browser to support Jaa applets and hae Jaa support turned on. The WebSphere Portal content publishing Help System may be iewed using a Support on the IBM Web site Jaa applet or in HTML. Use the Jaa and HTML buttons to switch iews. You can find support information on the IBM Web site. This is the official Web site for WebSphere Portal content publishing. The Web site contains technical information, documentation, and other support information. news://news.software.ibm.com/ibm.software.websphere.portal-serer.contentpublisher. This is the official WebSphere Portal content publishing news group.. 4 WebSphere Portal content publishing Help System

5 Chapter 3. Product oeriew WebSphere Portal content publishing proides a browser-based interface that enables nontechnical users to create, contribute, and manage content on Portals and Web sites. With WebSphere Portal content publishing you can: Quickly and easily create, contribute, and manage your Web site content Use templates to create, generate, and updated Web site content Add syndicated content to your Web site Manage the workflow of your team Personalize your Web site using simple editors to create rules and campaigns Generate reports about the effectieness of the rules and campaigns on your Web site Copyright IBM Corp

6 6 WebSphere Portal content publishing Help System

7 Chapter 4. Interface fundamentals Login page Tabs This section discusses the basic parts and functions of the WebSphere Portal content publishing interface. Login page Tabs Frames on page 8 To start WebSphere Portal content publishing: Go to in your Web browser, where <yourfullyqualifiedhostname> includes the host name and domain name of the serer where you installed the WebSphere Portal content publishing authoring serer. Click Start Web Content Publisher. A new window is displayed. Type your User ID and Password. Click Login. After logging in, the WebSphere Portal content publishing interface is displayed. The interface includes six tabs. Depending upon your access control settings, you will see different functions under each tab. The tabs hae the following functions in common: You can determine the Job, Project, and Edition that you are working on by looking at the top right of the interface. You can determine the name of the User you are logged in as by looking at the bottom right of the interface. You can logout of WebSphere Portal content publishing by clicking Log out at the bottom right of the interface. You can find information About WebSphere Portal content publishing, start the Help System by clicking Help, orrefresh the your browser window, from the bottom left of the interface. A description of each tab follows: Tasks tab From the Tasks tab, you can iew a list of the tasks you hae accepted and tasks that are aailable for you to work on. Note: The Tasks tab is not displayed if the option No Workflow was selected during WebSphere Portal content publishing installation. Content tab The Content tab displays content you can work on. The left frame displays a list of content types. Depending on the project you are working in, the content types Copyright IBM Corp

8 aailable to you might include Structured Content, Syndicated Content, and Files. When you click an item in the left frame, the corresponding content is displayed in the right frame. Personalization tab From the Personalization tab, you can create a personalized experience for Web site isitors or recipients. In the left frame, you can organize rules or campaigns. In the right frame, you can create new rules or campaigns or work on existing ones. Preiew tab From the Preiew tab, you can test rules and campaigns using a preiew profile. The preiew profile enables you to see how the rules respond to Web site isitors with attributes you define. Reports tab From the Reports tab, you can generate reports about the effectieness of the campaigns and rules on your Web site. Administration tab The Administration tab contains controls for managing: User roles and access File-type access Projects and editions Resource registration Background eent handling and status Channels for syndicated content Publishing serers Access to these controls is determined by the user role you hae been granted by the Administrator. At a minimum, you can select the project you wish to modify. Users with higher authority can create and manage projects, serers, and publish content to serers. Administrators can assign priileges to users and user roles. Frames Depending on what tab you are working on, you will see different frames. In general: The left frame proides naigation features. The right frame enables you to select items to work on. The bottom frame proides you with detailed information about items you select in the right frame. Selections in the left frame determine what you see in the right frame. Selections in the top right frame determine what you see in the bottom right frame. Controls for the different frames are user and selection sensitie. That is, the controls you see in the different frames depend on your role and user access as well as what you select in each frame. 8 WebSphere Portal content publishing Help System

9 You can re-size the frames by placing your cursor on the frame (a light purple line). When you see the horizontal or ertical line with arrows (for example ), click your mouse and drag the frame. Chapter 4. Interface fundamentals 9

10 10 WebSphere Portal content publishing Help System

11 Chapter 5. Getting Started tutorial How to use this tutorial Prerequisites: To use this Getting Started tutorial you must hae the following installed: WebSphere Portal content publishing authoring serer and the authoring serer sample. Note: This tutorial is based on the Lite Workflow Local Operating system installation option. Refer to the WebSphere Portal content publishing Installation Guide for instructions on installing the authoring serer. WebSphere Portal content publishing run-time serer installed on a separate machine from the authoring serer. Refer to the WebSphere Portal content publishing Installation Guide for instructions on installing the run-time serer. WCPDemo_Runtime.ear installed on your run-time serer. For instructions on installing WCPDemo_Runtime.ear, after installing the authoring serer, refer to steps 1 4 of readme.html located in <WAS_HOME>\wcp\author\samples\utils (WAS_HOME is where your WebSphere Application Serer is installed). Note: This tutorial requires you to install the authoring serer and run-time serer on two separate machines. This is a recommended best practice. About the tutorial: This tutorial is based upon the authoring serer sample that is optionally installed with WebSphere Portal content publishing. The authoring serer sample contains all of the data (such as JSPs (Jaa Serer Pages), HTML files, populated database tables, user resources, content resources, and so on) you need to manage a fictitious financial institution s Intranet and Internet. Although the authoring serer sample is comprehensie in function and resources, this Getting Started tutorial addresses the basic function of WebSphere Portal content publishing and is not intended to coer all of the components of the authoring serer sample. This tutorial walks you through the basic features of WebSphere Portal content publishing. Using resources from the authoring serer sample, you will learn how to use WebSphere Portal content publishing to create and manage content, personalize content, and generate reports. Each section of the tutorial may include the following headings: Scenario: Sets the scene for the section you are reading. Behind the scenes: Supplies you with background information so you can understand what is happening when you perform a specific function. Task: The actual task you perform to complete a section within the tutorial. Copyright IBM Corp

12 Tutorial scenario For this tutorial, your company has decided to add news to their Web site. Using a predefined workflow, your team will: Set up a project and import files Use a predefined workflow to create, approe, and complete tasks Use templates to generate content Personalize content using rules Publish content to your Web site Generate reports about the effectieness of your Web site s rules The players For this tutorial you will be playing the role of all of the members on a fictitious team. The people on the team are: Administrator, the WebSphere Portal content publishing system administrator. To login as the administrator you will need the user ID and password that was used when the WebSphere Portal content publishing authoring serer was installed. This user has complete authority of WebSphere Portal content publishing and can set access control, create users, create projects, and so on. Tara, the Webmaster and Content Publisher. She has the authority to initiate jobs and publish content to the production Web site. Tara is also responsible for generating reports about the effectieness of the Web site. Rob, the Project Lead and Domain Expert. He has the authority to reiew, accept, and reject requests pertaining to the Web site. For example, if a manager requested that all news articles on the Web site should hae an associated picture, Rob would determine if the request is alid. Dae, a Content Contributor. He has the authority to make content changes in a non-production enironment. Dae is responsible for adding content. Greg, a Content Contributor. He has the authority to make content changes in a non-production enironment. Although Greg s role is Content Contributor, he has the additional responsibility of personalizing content by creating rules. The workflow process A workflow is a set of interdependent tasks that occur in a specific sequence and is used to produce, process, and publish content. This tutorial uses WebSphere Portal content publishing s Simple Change Process workflow. The Simple Change Process workflow is a workflow that is installed with WebSphere Portal content publishing. For more information on workflow, refer to the WebSphere Portal content publishing Help System s section on workflow. Using the Simple Change Process workflow, your team will perform seeral tasks that are necessary to deelop and publish content to a production serer. The workflow tasks and players are identified below: Requesting a change (Tara) Reiewing the request (Rob) Making the changes (Dae) Making the changes (Greg) Reiewing and approing the changes (Rob) 12 WebSphere Portal content publishing Help System

13 The diagram below shows a graphical iew of the Simple Change Process workflow. Behind the scenes: The Simple Change Process can be configured to automatically publish content upon approal of the Reiew Change task. Modifying the Simple Change Process is beyond the scope of this tutorial. For information on customizing workflow processes, refer to Customizing the workflow in the WebSphere Portal content publishing Help System. Lets get started Now that you are familiar with the basic scenario, players, and workflow of the tutorial you can get started with the actual tutorial. Starting WebSphere Portal content publishing To start WebSphere Portal content publishing: In your Web browser, go to where <yourfullyqualifiedhostname> includes the host name and domain name of the serer where you installed the WebSphere Portal content publishing authoring serer. Click Start. WebSphere Portal content publishing is displayed in a new window. Before logging in, go to Configuring user roles and access on page 14. Chapter 5. Getting Started tutorial 13

14 Configuring user roles and access Setting up the project Scenario: Tara (the Webmaster and Content Publisher) and Rob (the Project Lead and Domain Expert) hae been tasked with creating a Web site that contains news articles for their company s Web site. Before they can start creating and personalizing content, the WebSphere Portal content publishing administrator needs to set access for the user Rob so that Rob can import a project. Task: To set Rob s access leel: 1. On the WebSphere Portal content publishing login page, type the WebSphere Portal content publishing administrator User ID and Password. This is the user ID and password that was used when the WebSphere Portal content publishing authoring serer was installed. 2. Click Login. 3. Click the Administration tab. 4. In the left frame, click Users. 5. In the right frame, click rob. (Note, do not click the check box next to rob, just click the name rob.) 6. In the lower frame, click Edit Authorities. The Access control for rob window is displayed. 7. In the Access control for rob window, in the Allow column, check Oerride and click Sae. 8. In the lower right corner, click Log out. Behind the scenes: You hae just gien the user rob Oerride authorities. Oerride authorities means rob has the same permissions as the administrator. By giing rob Oerride authorities, rob will be able to perform seeral functions necessary to complete this tutorial. The appropriate authorities for the other users in this tutorial hae already been set. For the next section of this tutorial you will need to log in as a different user. Scenario: In this section of the tutorial, you will play the role of Rob and set up a project for your team. Task: To set up the project, complete the following steps: 1. Adding a project 2. Importing a project on page Setting up the preiew user resource on page Setting up templates on page 17 Adding a project 1. Log into WebSphere Portal content publishing as rob. The User ID and Password are both rob. 2. Click the Tasks tab. 3. In the left frame, click My Tasks. 4. In the right frame, erify Quick Edit Task is denoted by the Work On icon. If you do not see the next to Quick Edit Task: 14 WebSphere Portal content publishing Help System

15 Click Quick Edit Task. In the lower frame, click Work On. The Work On Task window is displayed. In the Work On Task window, click Work On. The Work On Task window closes and the Work On icon Edit Task job. indicates you are working on the Quick Behind the scenes: Quick Edit Task enables users to perform functions outside of the workflow. In this tutorial, Rob needs to add and set up a new project for his team. Adding a project is not part of the Simple Change Process workflow, so Rob needs to temporarily exit the workflow in order to set up the project. Quick Edit can be turned on or off in the project s settings. 5. Click the Administration tab. 6. In the left frame, click Projects/Editions. 7. In the right frame, click Add Project. The Add Project window is displayed. 8. In the Add Project window, complete the following fields: In the Name field, type TutorialCompanyNews In the Description field, type Sample News Web Site for the Getting Started Tutorial In the Context Root field, type wps/wcpdemoauthor In the War Root Path field, type <WAS_HOME>\installedApps\WCPDemo_Author.ear\wcpdemo.war Where <WAS_HOME> is the drie and directory where WebSphere Application Serer is installed. For example: C:\WebSphere\AppSerer\installedApps\WCPDemo_Author.ear\wcpdemo.war In the Import/Export Root Path field, type <WAS_HOME>\wcp\author\samples\foo\wcpdemo, where foo is the database system you are using. For example: C:\WebSphere\AppSerer\wcp\author\samples\db2\wcpdemo or C:\WebSphere\AppSerer\wcp\author\samples\oracle\wcpdemo or C:\WebSphere\AppSerer\wcp\author\samples\cm\wcpdemo In the Preiew Start Page field, type wps/wcpdemoauthor/yourco.jsp Verify the Default Process is set to Simple Change Process. Accept the default alues for the other fields. Behind the scenes: Notice the other options you can set. Version Proider. If you are using a ersion control system, you would select the system you are using from this drop-down list. As preiously discussed, the Quick Edit feature enables you to work outside of a workflow. You can turn Quick Edit on and off from within the project settings. Lock allows you to lock a resource, such as a file. If lock is turned on then multiple users cannot work on a resource at the same time. Click Add. Behind the scenes: When you add a project, the project alues are stored in the WebSphere Portal content publishing database in the PROJECTS table. Chapter 5. Getting Started tutorial 15

16 You hae just added a project for your team. The next step is to import the sample project. Importing a project Behind the scenes: This tutorial supplies you with a sample project that includes all of the.html,.jsp.,.hrf, and other resource files that make up a Web site. The sample was created in WebSphere Studio Application Deeloper, exported as an.ear file, and installed as an Enterprise Application in WebSphere Application Serer as part of the authoring serer sample installation. The tutorial does not coer how to create a project in WebSphere Studio Application Deeloper or how to install an.ear in WebSphere Application Serer. Scenario: Now that Rob has added the project, he needs to import the files from the sample project. Task: To import the sample project: 1. If you logged out, log in as rob. 2. Click the Administration tab. 3. Click TutorialCompanyNews base. 4. Click Work On. 5. Click Import. The Import Project window is displayed. 6. In the Import Project window: Click Import. The import may take seeral minutes. To erify the import is complete: Scroll to the bottom of the window. When all of the files are imported, you will see a confirmation message indicating how many files were imported. For example, CTAC0168I: Total imported: 308. Click OK and Log out. 7. After you import content, open the WebSphere Application Serer Administratie Console and stop and start the WCPDemoAuthor Enterprise Application. Note: This is a required step. To erify content was imported: 1. Log in as rob. 2. Verify you are working on the base job of the TutorialCompanyNews project. To erify this, look at the top right of the WebSphere Portal content publishing interface. If you are not working in the correct project, click the Administration tab Projects/Editions TutorialCompanyNews base Work On. 3. Click the Content tab. 4. In the left frame, click Structured Content GeneralNews. In the right frame, a list of news articles is displayed. Behind the scenes: When you import a project, the project files are stored in seeral of the WebSphere Portal content publishing database tables. The project s class files are stored in the database tables and in the <WAS_HOME>\installedApps\WCPDemo_Author.ear\wcpdemo.war\WEB- INF\classes\resources directory. The class files and hrf files were created in WebSphere Studio Application Deeloper. They enable you to work with structured content. When you import a project, any resource collections (files with a.hrf extension) imported are automatically registered to the WebSphere Portal content publishing structured content system. 16 WebSphere Portal content publishing Help System

17 You hae just imported the files that your team will use to create a sample Web site. The next step is to set up the preiew user resource for your team. Setting up the preiew user resource Scenario: After you import a project, you must set up the user resource that is used for preiewing your Web site. You do this by editing the project s settings. Behind the scenes: A user resource contains information about the real or fictitious users of your Web site. The preiew user resource enables you to preiew and test the output of your Web site rules you can see how your Web site displays to different users. Later on in the tutorial, you will see how preiew works. The directory path for the preiew user resources in this sample is: <WAS_HOME>\wcp\author\samples\foo\wcpdemo\webApplication\wcp\preiew\resources.User where foo is the database system you are using. Task: To set up the preiew user resource: If you logged out, log in as rob. Click the Administration tab. Click Projects/Editions. Click TutorialCompanyNews. In the lower frame, click Edit. In the Preiew User Resource field, select User. Note: You may need to re-size the frame or scroll down. Click Sae. Now that the Preiew User Resource is set, you will set up the templates. Setting up templates Behind the scenes: Templates proide a way for your team to contribute content in a structured format. Templates are used with structured content or syndicated content. They cannot be used with filed-based content. There are three types of templates in WebSphere Portal content publishing: authoring, detail, and summary. Before continuing with the tutorial, here is a brief oeriew of the WebSphere Portal content publishing templates: Authoring templates are used by your team to add, edit, show, and preiew structured or syndicated content. Detail templates are used to generate the content your team has contributed. Summary templates are used to generate a list of content that your team has contributed. You can create your own JSP or XSL files to use as templates. You can also use the wizard to create authoring JSP templates based on your resource definitions. Scenario: Continuing with the tutorial, you will log in as Rob and set up the templates for the project. Note, in this exercise you will use template JSP files that were installed with the authoring serer sample. Chapter 5. Getting Started tutorial 17

18 Setting up the Authoring template Task: To set up the Authoring template: 1. If you logged out, log in as rob. 2. Click the Content tab. 3. In the left frame, click Structured Content GeneralNews. 4. Click Templates. The Templates window is displayed. 5. In the Authoring tab of the Templates window: a. Click the Browse button under Template for add form. The Search in File window is displayed. b. In the Search in File window: In the Filename field search for the template file by typing AddNews.jsp. Click Search. Note: You can also use wildcards in the search fields, for example, try searching for *News* or *News.jsp. Search is case sensitie. In the Search Results window click templates/author/generalnews/addnews.jsp. Click OK. The file name (and file path) is displayed in the Template for add form field. c. Repeat the aboe steps for the remaining fields (Template for edit form, Template for show form, Template for preiew form) by selecting the files EditNews.jsp, ShowNews.jsp, and PreiewNews.jsp. 6. Optionally preiew the templates by clicking the Preiew button for each of the templates. 7. Click Sae. Setting up the Detail template Task: To set up the Detail template: 1. If you logged out, log in as rob. 2. Click the Content tab. 3. In the left frame, click Structured Content GeneralNews. 4. Click Templates. The Templates window is displayed. 5. In the Templates window, click the Detail tab. 6. Click the Browse button under Template file. The Search in File window is displayed. 7. In the Filename field type News_Details.jsp. 8. Click Search. 9. In the Search Results window click templates/generation/generalnews/news_details.jsp. 10. Click OK. The file name (and file path) is displayed in the Template file field. 11. In the New generation folder field, type news and click the add button. Behind the scenes: When you generate content, a folder named news is created and displayed under Files of the Content tab. 12. Check Regenerate content files affected by this template. 18 WebSphere Portal content publishing Help System

19 Behind the scenes: When you check this option, content deried from the detail template is automatically regenerated as a background eent. For example, the sample includes seeral news articles. When you check Regenerate content files affected by this template and click Sae, the files dependent upon the template are regenerated. You can iew these files on the Content tab, by clicking Files (you may need to click the Files refresh icon ) and expanding generated resources.generalnews news. The right frame lists the regenerated content in the form of.html files (the numeric.html files not the summary.html file). To iew background eents, click the Administration tab Background Eents. 13. Click Sae. Setting up the Summary template Task: To set up the Summary template: 1. If you logged out, log in as rob. 2. Click the Content tab. 3. Click Structured Content GeneralNews. 4. Click Templates. The Templates window is displayed. 5. In the Templates window, click the Summary tab. 6. Click the Browse button under Template file. The Search in File window is displayed. 7. In the Filename field type News_Summary.jsp. 8. Click Search. 9. In the Search Results window click templates/generation/generalnews/news_summary.jsp. 10. Click OK. The file name (and file path) is displayed in the Template file field. 11. In the New generation folder field, type news and click the add button. Behind the scenes: When you generate content, a folder named news is created and displayed under Files of the Content tab. 12. Check Regenerate content files affected by this template. Behind the scenes: When you check this option, a summary list is automatically regenerated as a background eent. For example, the sample includes seeral news articles. When you check Regenerate content files affected by this template and click Sae, existing summary files are regenerated from the summary template. You can iew the regenerated summary.html on the Content tab, by clicking Files (you may need to click the Files refresh icon ) and expanding generated resources.generalnews news. To iew background eents, click the Administration tab Background Eents. 13. Click Sae. 14. Click Log out. You hae completed setting up your team project named TutorialCompanyNews. Your team can now begin to create content for your sample Web site. Chapter 5. Getting Started tutorial 19

20 Creating and personalizing content Scenario: Now that the project has been set up, your team can begin to use WebSphere Portal content publishing to create content. Using the Simple Workflow Process described aboe (see The workflow process on page 12) your team will perform a number of tasks, including: Requesting a change Reiewing the request Making the changes on page 21 Reiewing the changes on page 30 Requesting a change Scenario: For this exercise, you will play the role of Tara. In collaboration with her management team, Tara has identified the need for news to be displayed on the company Web site. Using WebSphere Portal content publishing Tara initiates a new job and requests that a change be made to the Web site. Task: To initiate a new job and request a change: 1. Log into WebSphere Portal content publishing as tara. The User ID and Password are both tara. 2. In the left frame, click My Tasks. 3. In the right frame, click New Job. The Initiate New Job window is displayed. 4. In the Initiate New Job window: In the Name of the job field, type Tutorial Company News. In the Job description field, type the following description. (You can copy and paste from this document.) Rob, hae your team create a Web site that contains personalized news. In the Project field, select TutorialCompanyNews. In the Process for new job field, select Simple Change Process. Accept the default alues for the other fields. 5. Click Start. Behind the scenes: The job moes to the next stage in the workflow. Only users who hae access to this part of the workflow can see the job in their Aailable Tasks folder. Tara is not a Project Lead (a role that approes and accepts new jobs) so you will not see the job displayed in her Aailable Tasks folder. 6. Click Log out. Reiewing the request Scenario: In the Simple Change Process workflow, after a request is created any user in the appropriate role can work on it. Rob has been assigned the roles of Project Lead and Domain Expert. As Project Lead, it is his responsibility to reiew and accept requests before they can be worked on. For this task you will play the role of Rob and will accept the job that Tara created. Task: To reiew and accept the request: 1. Log into WebSphere Portal content publishing as rob. The User ID and Password are both rob. 2. In the left frame, click Aailable Tasks. A list of jobs that Rob that can work on is displayed in the right frame. 20 WebSphere Portal content publishing Help System

21 Behind the scenes: When you look at the image below, you can see that Job Rob can work on is entitled Tutorial Company News and the Task he can work on is Reiew Request. The text Reiew Request is directly associated with the Simple Change Process workflow. 3. Click the name of the job: Tutorial Company News. In the bottom frame, you can click the Task Details or Commentary tabs to see additional information about the task. 4. Click Accept. The Accept Task window is displayed. 5. In the Commentary field type: Dae, create the content and then assign the task to Greg so he can create the rules. 6. Click Accept. Behind the scenes: The job moes to the next stage in the workflow. Only users who hae access to this part of the workflow can see the job in their Aailable Tasks folder. Rob is not a Content Contributor (a role that allows you to contribute content and edit content) so you will not see the job displayed in Rob s Aailable Tasks folder. Dae and Greg hae been assigned the role of Content Contributor, so they will both see the job in their Aailable Tasks folders. 7. Click Log out. Now that Rob has accepted the task, Dae (a Content Contributor) can add content. Making the changes Behind the scenes: This section is entitled Making the changes because it is the next step in the Simple Change Process workflow. Scenario: After Rob accepts the Tutorial Company News job, Dae (a Content Contributor) uses templates to add and generate content. Task: To make changes Dae needs to complete the following tasks: Chapter 5. Getting Started tutorial 21

22 Working on the task Adding structured content Generating structured content on page 23 Assigning the task on page 24 Completing the task on page 29 Working on the task Scenario: Dae has receied notification that he needs to create content for his company Web site. The first step in the process of creating content is to work on the task. Task: To work on a task: 1. Log into WebSphere Portal content publishing as dae. The User ID and Password are both dae. 2. Click Aailable Tasks. The list of jobs Dae can work on is displayed on the right. Behind the scenes: Notice the Job Dae can working on is entitled Tutorial Company News and the Task he can work on is Make Change. The text Make Change is directly associated with the Simple Change Process workflow. 3. Click Tutorial Company News. 4. Click Commentary. Dae sees Rob s comment and knows that after he creates the content he will assign the task to Greg. 5. Click Work On. The Work On Task window is displayed. 6. Click Work On. The task moes into Dae s My Tasks folder. Adding structured content Scenario: Now that Dae can work on the Tutorial Company News job, he can use the templates that Rob set up to add structured content. Task: To add structured content: 1. If you logged out, log in as dae. 2. Click the Content tab. 3. Click Structured Content GeneralNews. 4. In the right frame, click the add button. The GeneralNews template is displayed. 5. In the GeneralNews template: Leae the Path field blank. In the Newsid field, type 24. Note: The Newsid must be a unique integer. If you use this tutorial more than once you will need to type in another number (and not 24). In the Headline field, type Fashion Show Yields Designer Discounts. In the NewsType field, select Entertainment News and click the add button. In the Article Details field, type: If you re interested in getting big discounts on the newest fashions, check out the NYC Fashion show on Orchid Street. Many of the top designers will be selling their garb at huge discounts. 22 WebSphere Portal content publishing Help System

23 Click Add. The GeneralNews template closes and the article information is displayed in the list of articles. The article you just added is denoted by the icon. Click the preiew icon to preiew the article. Generating structured content Scenario: Dae has just added structured content. He needs to generate the content so that the new file is displayed in the summary.html file. Behind the scenes: Recall, when Rob set up the templates he checked Regenerate content files affected by this template. The effect of checking this box means that when content is added or modified the content is automatically generated (and in this tutorial example,.html files are automatically created). Howeer, in order for the content to be displayed in the summary.html file, Dae must generate the content he just created. WebSphere Portal content publishing also supports generating structured files to other formats such as XML, WML, and PDF. All you need to do is supply the template. Task: To generate the summary.html file: 1. If you logged out, log back in as dae. 2. Click the Content tab. 3. In the left frame, click Structured Content GeneralNews. 4. Click Generate. The Generate Items window is displayed. 5. Click Generate. 6. Click OK to close the Generate Items window. To erify content was generated, in the left frame: 1. Click Files. 2. Expand Files generated resources.generalnews. 3. Click news. In the right frame, a list of files is displayed. These are the files you just generated. Behind the scenes: The numeric files (such as 24.html) were automatically generated from the Detail template. The summary.html file was generated from the Summary template. 4. Click next 24.html to preiew the article you just created. Click next to summary.html to preiew a list of news articles that were generated. Behind the scenes: The new content Dae just created (24.html) is displayed in Dae s workspace but not in the workspaces of the other team members. The content will become isible to the other team members when the task is completed. Dae is finished with his responsibility of generating content, howeer Greg (the other Content Contributor on the team) needs to personalize the content by creating rules and campaigns. Dae assigns the task to Greg. Chapter 5. Getting Started tutorial 23

24 Assigning the task Scenario: Dae is finished with his responsibility of generating content, howeer he is working with Greg (the other Content Contributor on the team). Dae needs to assign the task to Greg, so that Greg can personalize the content by creating rules. Task: To assign a task: If you logged out, log in as dae. In the Tasks tab, click My Tasks Tutorial Company News. In the lower frame, click Assign. The Assign Task window is displayed. In the Assign Task window, select greg from the User drop-down list. Click Assign. The task moes from Dae s My Tasks folder into Greg s Aailable Tasks folder. Working on the task Scenario: Dae assigned the Make Change task to Greg. Greg logs into WebSphere Portal content publishing and works on the task. Task: To work on a task: 1. Log into WebSphere Portal content publishing as Greg. The User ID and Password are both greg. 2. In the Tasks tab, click Aailable Tasks. 3. Click Tutorial Company News. 4. Click Work On Work On. Greg is now ready to personalize content. Personalizing content Behind the scenes: This sample includes rules that hae already been created. You can look at these rules for reference or use these rules in this next section. Although some rules hae already been created, this section of the tutorial shows you how to create your own rules. To iew the rules that were installed with the sample, in the Personalization tab click Rules and expand the Rules folder. Click FrontPage. The rules are displayed in the right frame. Scenario: Greg has the task of creating rules to personalize the content on the company Web site. He will create seeral types of rules to accomplish his task: Creating a Select Content rule Creating a Profiler rule on page 27 Creating a Binding rule on page 28 Creating a Select Content rule: Behind the scenes: A Select Content rule retriees data or content resources from your data store or a current resource. This type of rule is typically used to display content on a Web page. Scenario: Greg is ready to create rules to personalize the content on his Web site. Before he creates his first rule, he creates a new folder to store the tutorial rules. Task: Create a new folder to store the tutorial rules and then create a Select Content rule: 1. If you logged out, log in as greg. 24 WebSphere Portal content publishing Help System

25 2. Click the Personalization tab. 3. Click Rules Rules. 4. Create a new Rules folder by clicking the Add Folder button aboe Rules. The Add a Rules Folder window is displayed. 5. In the Folder Name field type TutorialRules and click Sae. The Add a Rules Folder window closes and TutorialRules is highlighted. 6. In the right frame, click the add button. The Rule Properties tab is displayed in the lower frame. 7. On the Rule Properties tab: In the Rule Name field, type TutorialGetDiscountNews. In the Description field, type This rule gets news articles that contain the word discount. In the Rule Type field, select Select Content. 8. Click Resource.Attribute. The Specify a Resource Attribute window is displayed. Chapter 5. Getting Started tutorial 25

26 9. In the Specify a Resource Attribute window, click the GeneralNews Resource Collection and the News Attribute. Click Sae. 10. Click is equal to. The Specify Ealuation window is displayed. 11. In the Specify Ealuation window, click includes Sae. 12. Click alue. The Specify a Value window is displayed. 13. In the Specify a Value window, erify Value is selected and type discount. Click Sae. Note: Make sure you type a lower case d. Rules are case sensitie. 14. On the bottom of the Rule Properties tab, click Sae. Your saed rule should look like: Select content whose GeneralNews.News includes discount order as is Create and sae another rule using the following alues: Rule Name TutorialGetMuscicNews Description This rule gets news articles about music. Rule Type Select Content Resource.Attribute GeneralNews and Headline is equal to includes alue Music Note: Make sure you type an upper case M. Your saed rule should look like: Select content whose GeneralNews.Headline includes Music order as is 26 WebSphere Portal content publishing Help System

27 Optionally, after saing TutorialGetMuscicNews you can edit the rule to add additional conditions. To do this, in the Personalization tab: 1. Click TutorialGetMuscicNews Edit. 2. Click add Condition. 3. Select GeneralNews and Headline. Click Sae. 4. Click and. Select or. Click Sae. 5. Click is equal to. Select includes. Click Sae. 6. Click alue. Type Rock and Roll. Click Sae. 7. On the bottom of the Rule Properties tab, click Sae. Your saed rule should look like: Select content whose GeneralNews.Headline includes Music or whose GeneralNews.Headline includes Rock and Roll order as is Creating a Profiler rule: Behind the scenes: A Profiler rule is used to categorize a Web site isitor or the characteristics or circumstances of his or her isit, such as the time of day in which it occurs. Scenario: You will create a Profiler rule that identifies the income groups of your Web site isitors. Task: To create a Profiler rule: 1. If you logged out, log in as greg. 2. Click the Personalization tab. 3. Click Rules Rules TutorialRules. 4. In the right frame, click the add button. 5. On the Rule Properties tab: In the Rule Name field, type TutorialGenderProfile. In the Description field, type This rule groups users by gender. In the Rule Type field, select Profiler from the drop-down list. Click Profile. The Specify Profile Name window is displayed. In the Specify Profile Name window, type Female. Click Sae. Click Resource.Attribute. The Specify a Resource Attribute window is displayed. In the Specify a Resource Attribute window, click the current User Resource Collection and the Gender Attribute. Click Sae. Click alue. The Specify a Value window is displayed. In the Specify a Value window, select Female (F). Click Sae. Click add Profile. The Specify Profile Name window is displayed. In the Specify Profile Name window, type Male. Click Sae. Click Resource.Attribute. The Specify a Resource Attribute window is displayed. In the Specify a Resource Attribute window, click the current User Resource Collection and the Gender Attribute. Click Sae. Click alue. The Specify a Value window is displayed. Chapter 5. Getting Started tutorial 27

28 In the Specify a Value window, select Male (M) from the drop-down list. Click Sae. 6. On the bottom of the Rule Properties tab, click Sae. Your saed rule should look like: TutorialGenderProfile is Female when current User.Gender is equal to Female Male when current User.Gender is equal to Male Creating a Binding rule: Behind the scenes: A Binding rule combine profilers and actions (select content rules) into sophisticated conditional clauses in which certain actions are performed when certain profilers ealuate as true. Task: To create a Binding rule: 1. If you logged out, log in as greg. 2. Click the Personalization tab. 3. Click Rules Rules TutorialRules. 4. In the right frame, click the add button. 5. On the Rule Properties tab: In the Rule Name field, type TutorialNewsGenderBinding. In the Description field, type This rule retriees news articles based on gender. In the Rule Type field, select Binding from the drop-down list. Click Profiler. The Select a Profiler window is displayed. In the Select a Profiler window, click TutorialGenderProfile. Click Sae. Click Profile. The Select Profile window is displayed. In the Select Profile window, check Female. Click Sae. Click do Action. The Select an Action, Binding, or Profiler window is displayed. In the Select an Action, Binding, or Profiler window, scroll down and click TutorialGetDiscountNews. Click Sae. Under Otherwise, click do Action. The Select an Action, Binding, or Profiler window is displayed. In the Select an Action, Binding, or Profiler window, scroll down and click TutorialGetMusicNews. Click Sae. 6. On the bottom of the Rule Properties tab, click Sae. Your saed rule should look like: When TutorialGenderProfile is Female do TutorialGetDiscountNews Otherwise do TutorialGetMusicNews order as is Preiewing content Behind the scenes: Preiew enables you to iew your Web site as a customer would. In Preiew, you can iew personalized content for a specific user on a specific data. The Preiew function also allows you to edit content spots you can 28 WebSphere Portal content publishing Help System

29 change what rules are associated with a specific spot mapping. The Preiew page, YourCo.jsp, was installed with the authoring serer sample. Scenario: Greg is ready to preiew the Web site. Task: To preiew the Web site: 1. If you logged out, log in as greg. 2. Click the Preiew tab. 3. In the right frame, click Preiew. The Specify Preiew Criteria window is displayed. 4. In the Specify Preiew Criteria window, select Platinum Employee from the Profile drop-down list. Click Submit. The YourCo Financial Web page is displayed. 5. On the YourCo Financial Web page, click the content spot next to YourCo General News Information. The Fill Content Spot window is displayed. 6. In the Fill Content Spot window: a. Click Edit. b. On the Spot Mapping Details tab, next to Rule, select TutorialNewsGenderBinding from the drop-down list. Click Sae Close. 7. Refresh the YourCo Financial Web page using your browser s refresh button (you may see window asking you to click Retry, go ahead an click the Retry button). The news article Fashion Show Yields Designer Discounts is displayed. 8. Close the YourCo Financial Web page. 9. In the right frame, click Preiew. The Specify Preiew Criteria window is displayed. 10. In the Specify Preiew Criteria window, select Titanium Customer from the Profile drop-down list. Click Submit. The YourCo Financial Web page is displayed. The news article Country Music Star to Wed is displayed. Note, if you optionally added Rock and Roll to the TutorialGetMusicNews rule, then two news articles are displayed. Completing the task Scenario: After Dae generates content and Greg creates rules, the task needs to be completed. Task: To complete the task: 1. If you logged out, log back in as greg. 2. In the Tasks tab, click My Tasks. 3. In the right frame, click the job Tutorial Company News. 4. Click Complete. The Complete Task window is displayed. 5. In the Commentary field of the Complete Task window, type: Content has been added and generated. Rules hae been created. 6. Click Complete. 7. Click Log out. Chapter 5. Getting Started tutorial 29

30 Behind the scenes: The job moes to the next stage in the workflow. Only users who hae access to this part of the workflow can see the job in their Aailable Tasks folder. Greg is not a Project Lead (a role that reiews changes) so you will not see the job displayed in his Aailable Tasks folder. Now that Greg has completed the task, Rob (the Project Lead) can reiew the Content Contributors work. Reiewing the changes Scenario: After Dae and Greg make changes to the Tutorial Company News job, Rob reiews the changes. Task: To reiew the changes: 1. Log into WebSphere Portal content publishing as rob. The User ID and Password are both rob. 2. In the Tasks tab, click Aailable Tasks. 3. Click the name of the job: Tutorial Company News. 4. Click Work On. The Work On Task window is displayed. 5. Click Work On. The task moes into Rob s My Tasks folder. Scenario: At this point, assume Rob has reiewed the generated content and rules. Rob does not hae any additional changes to the Content Contributors work. He accepts the task. Note, accepting the task means that he has approed Dae and Greg s work. Accepting the task Task: To accept the task: Publishing the changes 1. If you logged out, log back in as rob. 2. In the Tasks tab, click My Tasks. 3. Click the job Tutorial Company News. 4. Click Accept. The Accept window is displayed. 5. Click Accept. Behind the Scenes: After Rob accepts the changes the Content Contributors work is promoted. This means all members of the team will see this work in their workspace for the TutorialCompanyNews project. Note, after Rob accepts the changes all of the steps in the Simple Change Process workflow are complete. 6. Click Log out. Behind the scenes: To publish the TutorialCompanyNews project to a production Web site, you must hae the WebSphere Portal content publishing run-time serer installed on a different machine than the authoring serer. Furthermore, WCPDemo_Runtime.ear needs to be installed on your run-time serer. Refer to the WebSphere Portal content publishing Installation Guide for information on installing the run-time serer. For instructions on installing WCPDemo_Runtime.ear, refer steps 1 4 of the readme.html file located in <WAS_HOME>\wcp\author\samples\utils. Scenario: The content changes hae been reiewed and accepted by Rob. The next step is to publish the TutorialCompanyNews project to a production Web site. In this 30 WebSphere Portal content publishing Help System

31 exercise, you will play the role of Tara (the Content Publisher). You will set up the publish serer and publish your project to your production Web site. Setting up a publish serer Task: To set up a publish serer: 1. Log in to WebSphere Portal content publishing with the User ID tara and the password tara. 2. Click the Administration tab. 3. Click Projects/Editions TutorialCompanyNews base Work On. 4. In the left frame, click Publish Serers. 5. In the right frame, click. The Add Publish Serer window is displayed. 6. In the Add Publish Serer window: a. In the Serer Name field, type the name you want to use to reference the serer. b. In the Serlet URL field, type &password=<password>, where: <yourruntimeserer> is the WebSphere Portal content publishing run-time serer. <user> and <password> represent a alid user on the run-time serer. For example: &password=db2admin Behind the scenes: The username and id needs to be passed in the string for the publish serlet to work using the authoring serer sample. The alues are needed to register your resources on a secure run-time serer. c. Click Realm. For the Realm User ID and Password use the same strings as aboe. For example, db2admin db2admin. d. Click Add. Chapter 5. Getting Started tutorial 31

32 Publishing the project Task: To publish the project: 1. If you logged out, log back in as tara. 2. Click the Personalization tab. 3. Click Rules. 4. Click Publish. The Publish Content window is displayed. Note: Clicking from the Content or Personalization tabs produces the same results. When you click Publish, the content that is published includes files (e.g..html, JSP), resources, rules, and so on. 5. In the Publish Content window: a. In the Select publish serer list, click the name of the serer you are publishing to and use the right arrow button to moe it to the list on the right. b. Click Publish. c. Wait until you see the message Publish is Complete and click OK. 6. Click Log out. To erify the project was published, go the following Web address in a browser: where <yourruntimeserer> is the name of the run-time serer to which you just published. Login with the username and password tara. 32 WebSphere Portal content publishing Help System

33 The content in your Web browser should look similar to the image below: Behind the scenes: The file YourCo.jsp was a file shipped with the authoring serer sample, so it contains content and rules that were not created during this tutorial. On the right side of the YourCo Financial Web page you can see two General News articles: Rock and Roll Hall of Fame opens New Wing and Country Music Star to Wed. These two articles are displayed due to the TutorialNewsGenderBinding rule that you assigned to the content spot. Recall the binding rule you created: Chapter 5. Getting Started tutorial 33