Search WebSpherePower's 6,973 WebSphere, Java, and Eclipse article archive 
Home
EasyPrint
News details Click here for the RSS feed's XML code. This is not a browser URL.
Articles-only Click here for the RSS feed's XML code. This is not a browser URL.
Twitter Feed Click here for the Twitter feed.
Setting up a Wiki in WebSphere Studio Application Developer (continued)

FIGURE J


Select your workspace before the Studio is launched. Roll over picture for a larger image.

Some of the folders inside of the .war are duplicates of those provided by Studio when it creates a new Web project, so you will need to click on Yes To All when it asks if you would like to overwrite those duplicate items, as shown in Figure K.

FIGURE K


Select Yes To All when asked if you would like to overwrite existing items. Roll over picture for a larger image.

At this point, you should see all of the downloaded items that were imported into your Web project. Other than some configuration properties that we need to set, this project is actually ready to run, but there is one small change that I like to make at this point. Studio will create a default context root (the relative address used to launch your application) based on the name of your Web project. I usually have something else in mind, and now is a good time to change it.

Right click on the Web project again to bring up the context menu, and this time select properties, as shown in Figure L.

FIGURE L


Select Properties from the context menu. Roll over picture for a larger image.

Under the list of properties, select Web, then overwrite the default context root with a name of your own choosing. I just used the term wiki for mine. Click OK to save this change, as I did in Figure M.

FIGURE M


Set your context root and click OK. Roll over picture for a larger image.

Configure Your Wiki
The last thing that you will need to do is to set all of the configuration properties to match your implementation. Many of the default values are actually OK as they are set, but there are a few that you will want to change now, and probably some others that you will eventually want to play with at some time in the future.

Open up the WEB-INF folder in your WebContents folder and find the wiki properties file called jspwiki.properties. Double click on the file (or right click and select Open) to bring this file up in the text editor. You can see this in Figure N.

FIGURE N


Bring up the jspwiki.properties file in your text editor. Roll over picture for a larger image.

The first property you will want to set is jspwiki.applicationName, particularly because this name will appear on the screen. Set this property to the appropriate name for your wiki.

The next property I like to change from the default is jspwiki.pageProvider. There are a number of options here, and you can leave it just the way it comes, but by changing this value to VersioningFileProvider, you get a running change log of alterations made to your wiki pages. This is a nice thing to have, so I always change this value, as I did in Figure O.

FIGURE O


Set the version control with this property. Roll over picture for a larger image.

The next property to change, and the most important, is jspwiki.fileSystemProvider.pageDir. This is the directory where the wiki will store all of the pages for your wiki. For testing purposes, set this property to the directory where you unzipped all of the sample pages that came bundled with the software. A little further down in the file you will also find the property jspwiki.basicAttachmentProvider.storageDir. Set this property to the same value.


« Previous  ·  1  ·  2  ·  3  ·  4  ·  Next »
Other articles you might like
Home > WebSphere Studio (9 articles)
   Upgrading WebSphere Studio to Version 5.1.2
   Managing multiple workspaces with WebSphere Studio
   Using the Fast View feature to be quicker on the draw
Get Weekly Email Updates
Subscribe to our regular weekly email newsletter. It's packed with tips, reviews, deep analysis, and the latest news.
 
Recent WebSpherePower Articles
A perfect 10: celebrating 10 years online
You can help bring security and safety back to White House email
Introducing the WebSpherePower RSS feeds
From New Jersey to Palm Bay, Florida
A WebSphere pot o' gold
How Elvis entered the building and CES went out the window
WebSphere Application Server 6: what's it all mean?
WebSpherePower News
Legal question: Can HP keep Hurd from going to Oracle?
Caringo announces integration with Symantec EV 9.0
Cisco & Citrix marry on virty PCs
Take Heed, Tech Giants: Edison's Failed Plot To Hijack Hollywood
IBM code unchains virtual workloads
Oracle names H-P ex-CEO Mark Hurd as co-president
Cloud Messaging Provider, Linxter, Releases SDK for Java and Android
>> Read all the news
More from the ZATZ journals
Computing Unplugged: Introducing the Jones family and their full-family backup challenges
David Gewirtz Online: CNN commentary and analysis
DominoPower: Lotus must open source Notes and Domino
OutlookPower: Hands on debugging a broken Outlook forwarding rule
-- Advertisement --

SECURE YOUR SITE WITH AN IRONCLAD SSL CERTIFICATE
An IronClad SSL Certificate helps you build an impenetrable fortress around your customer's credit card information. IronClad SSL Certificates are:

  • Fully validated
  • Up to 256-bit encryption
  • One, two, or three year validity (our Turbo SSL Certificates are valid up to 10 years)
  • 99% browser recognition
  • Stringent authentication
  • Around-the-clock customer support

Build trust. Protect your customers. Grow your online business.

Tap here now and be IronClad with SSL tonight.

ZATZ Home  ·  News  ·  Back Issues  ·  Credits/Trademarks ·  Link To Us
Copyright © 2010, ZATZ Publishing. All rights reserved worldwide.
Editor's Login