To install WebSphere Portal 8 Beta 3 follow the procedure I described for Beta 2.  The updated download links are here and from there you can link to the installation guide I provided here.

After logging into the portal I landed on the Getting Started page. I decided to take a quick look at the properties and layout of the page using a conventional approach. I navigated to the Administration pages and loaded the Manage Pages portlet. At the top of the page is a new feature. This pane, which I have dubbed the project pane, represents the state of the page as a member of a project. Projects are not new to Web Content Management but they are, so far as I know, new to page management. According to the product Wiki, “When working in a project, any changes you make to a page affect only your view of the page.

Figure 1

After the project is approved and published, the changes are then available to all users.” Welcome to version control for portal pages! The second panel is a conventional display of page properties. There is one variation to the interface as it pertains to the layout template of the page but otherwise there are no other surprises here. (Figure 1)

Returning to the Manage Pages portlet I next selected the Edit Layout portlet. Again a “project pane” and the layout pane appear. By the way, you can collapse the “project pane” to recover more useable space for managing properties or layout. In the layout pane there were not surprises here at all. However, I was a bit disappointed. I realize that this is (1) a beta and (2) the release teams efforts need to be spent on other chores but (3) it would be really nice if the content on the Getting Started Page was web content delivered through the Web Content Viewer portlet and not the “handy dandy” Information Portlet.  What next?

Figure 2

I decided the best way to get a feel for how managed pages might be experienced would be to create a new project and edit a new page. Returning to the Home tab and the Getting Started Page I placed the page into the Edit Mode. Again, the product Wiki states, “There are several ways to enter edit mode: You can click Edit Mode directly in the user interface. A default project is created, with the project name being based on the page name and the date. You can change the project name later. The first thing to note is that the functionality for creating a page related project will be very familiar to users who have created pages with the Page Builder theme interface. (Figure 2).

Working from the Getting Started page I clicked the Edit Mode button.  Right away a vital distinction needs to be made between making changes to a published site and making changes to a project that is not yet published. When stated this way the consequences may seem self evident. However, to a user unfamiliar with the interface they might surmise that the changes they make are not immediately visible.  If they believe this, they are wrong. In this case I elected to create a new project. The properties of the project are self explanatory and for this exercise I elected to select Manual for the Publish option.

I created a new project named Demo Project.  Figure 3  provides a before and after comparison of the interface as I moved through the steps to create a new project. You can select view or edit for a project from the project menu. Choosing the View on the Published site and a particular project allows you to see how one compares to another. Only the published site can be seen by the user community.

Figure 3

Now that we have an unpublished project I added a page, Demo Page.  If you want to follow my experiment, make sure you have an unpublished project and place it in the edit mode as illustrated in the “after” illustration shown in Figure 3 above. Then, select the More button and choose sibling or child page. I chose sibling to simply illustrating the concept. Figure 4 demonstrates this.

Figure 4

Page creation in the context of a project such as the one illustrated in this topic places management of the portal page artifact into a Web Content Management (WCM) library. This means that “Publishing of projects can be scheduled in the same manner as other traditional WCM components. Additionally, this means that managed pages, as a form of managed content, can be syndicated from an authoring environment to a rendering environment. To my mind this is a huge leap forward in portal site development because it is very plausible that revisions to a site would not only incorporate changes to the content that authors might submit but also pages and related artifacts for presenting content.  Syndication does not include propagation of portlets or other web archive (JSP for example) resources.

Before creating the page you can change to another template type. Additional page templates can be defined. Page templates are not a new feature but it

Figure 5

will be interesting to see how these are leveraged in the future as more portal and WCM administrators take advantage of the managed pages feature. See Figure 5 for an example.

Once a page and other artifacts are added to a project you will typically refine their properties. Now that we have a page it will be useful to finalize one more aspect of how managed pages work. Keep in mind that the interface seen by our administrator references the published site as well as the projects that are in progress. In our example we have a Demo Project.  By alternately clicking the View link for either the project or the published site we can quickly visualize the distinction.  Figure 6 illustrates this and in Figure 7 and 8 we show how members of a project are published and, in turn, how the published site is altered.

Figure 6

As mentioned, here are screen shots to illustrate HOW an artifact is published.

Figure 7

NOTE: It may take several minutes for publish to complete.  Be patient!

Figure 8

Top New Portal Features:

1. New Look and Design.

2. Ability to have multiple portals, each based on a company or location. Each portal can have its own logo and color scheme. Great for big clients and Streamline IT clients. Note: there is no longer a logo on the login page due to this new feature as everyone uses the same login page.

3. Ability to accept credit card payments for invoices using Authorized.Net.

4. Ability to customize most colors on the portal.

5. Ability to restrict clients from seeing tickets residing on certain boards.

6. Ability to restrict clients from viewing certain Configuration Types.

Plus a ton of other new features. Take some time and check out the new Customer Portal.

Please Note: As of 1/20/2012 they are still working out a few bugs with the new format, so if you are not currently pushing the portal with your clients I would wait a few weeks to make sure everything is ironed out. But in the mean time take the time to get it configured and ready to roll out.