test

Technical Note: Managing Sun Java System Portal Server 7.1 Update 1 Blog Portlet

Installing Roller

This technical note contain the following sections:

Roller Installation

Download Roller from the Roller project download page and refer to the Roller Weblogger project page for the detailed steps of installing and configuring Roller. Support files can be found at the Roller java.net support project download page. As part of Roller installation, you must configure a relational database and deploy a web application.

Once Roller is installed and running, enable the APP and AAPP web service endpoints. Refer to the Roller APP Installation / Configuration and AAPP Installation / Configuration wiki pages for details.

The default APP endpoint is:


http://<server>[:<port>]/roller/roller-services/app

The default AAPP endpoint is:


http://<server>[:<port>]/roller/roller-services/aapp

To test them, use the authget.sh, authpost.sh, authput.sh, and authdelete.sh scripts available from the Blogapps Examples java.net project page. These are simple command line utilities to do HTTP GET, POST, PUT, and DELETE operations with HTTP basic authentication. Since the APP and AAPP protocols are XML over HTTP web services that use the standard HTTP operations, you can fully interact with them in this manner.

Example 1 Validate APP Endpoint

To validate that the APP endpoint is enabled, do an HTTP GET on the endpoint URLs as shown below.


$ ./authget.sh roller-user-name roller-user-password http://siroe:8080/roller/roller-services/app
<?xml version="1.0" encoding="UTF-8"?>
<app:service xmlns:app="http://purl.org/atom/app#">
	<app:workspace>
		<atom:title xmlns:atom=http://www.w3.org/2005/atom">Jovial Junkyard</atom:title>
		<app:collection href="http://localhost:8080/roller/roller-services/app/
		 junkyard/entries">
			<atom:title xmlns:atom="http://www.w3.org/2005/atom">Weblog
			 Entries</atom:title>
			<app:categories app:fixed="yes" 
			 app:scheme="http://localhost:8080/roller/junkyard/">
				<atom:category xmlns:atom="http://www.w3.org/2005/atom" 
				 atom:term="/General" atom:label="General" />
				<atom:category xmlns:atom="http://www.w3.org/2005/atom" 
				 atom:term="/Status" atom:label="Status" />
				<atom:category xmlns:atom="http://www.w3.org/2005/atom" 
				 atom:term="/Java" atom:label="Java" />
				<atom:category xmlns:atom="http://www.w3.org/2005/atom" 
				 atom:term="/Music" atom:label="Music" />
				<atom:category xmlns:atom="http://www.w3.org/2005/atom" 
				 atom:term="/Politics" atom:label="Politics" />
			</app:categories>
			<app:accept>entry</app:accept>
		</app:collection>
		<app:collection href="http://localhost:8080/roller/roller-services/app/
		 junkyard/resources">
			<atom:title xmlns:atom="http://www.w3.org/2005/atom">Media Files</atom:title>
			<app:accept />
		</app:collection>
	</app:workspace>
</app:service>
Example 2 Validate AAPP Endpoint

To validate that the AAPP endpoint is enabled, do an HTTP GET on the endpoint URLs as shown below.


./authget.sh roller-admin-user roller-admin-pwd
 http://siroe:8080/roller/roller-services/aapp
<?xml version="1.0" encoding="UTF-8"?>
<service xmlns="http://purl.org/roller/aapp#">
	<workspace title="Workspace: Collections for administration">
		<collection title="Collection: Weblog administration entries" 
 	 href="http://localhost:8080/roller/roller-services/aapp/weblogs">
			<member-type>weblog</member-type>
		</collection>
		<collection title="Collection: User administration entries" 
 	 href="http://localhost:8080/roller/roller-services/aapp/users">
			<member-type>user</member-type>
		</collection>
		<collection title="Collection: Member administration entries" 
 	 href="http://localhost:8080/roller/roller-services/aapp/members">
			<member-type>member</member-type>
		</collection>
	</workspace>
</service>

Roller Deployment

Blog portlet creates Roller weblogs and users in a flat space. Such weblog server resources are not name-spaced by the Portal ID or any other identifier. The desired deployment is therefore one Roller server instance per portal

This image shows one Roller server instance per portal.

You can use a single Roller server instance for multiple portals.

This image shows one Roller server instance for multiple portals.

In this situation, users in Portal A and B will not be allowed to have like-named weblogs. In a community context, users will not be able to have the community Blog service in like-named communities. This is because Blog portlet names the per-community weblog according to the community name.