Test install of the Planets Suite on Windows NT

Today was scheduled for a test install of the  Planets Suite on Windows NT

I initially tried to use the installer at http://planets-suite.sourceforge.net/download/ but ran into problems.   There were error messages during the install and starting up the planets server gave a JBOSS error

WARN  [org.jboss.web.tomcat.service.JBossWeb] Failed to startConnectors

LifecycleException:  service.getName(): “jboss.web”;  Protocol handler start failed: java.io.FileNotFoundException:

So I moved on to attempt building the application using Subversion and ANT following the instructions from Open Planets Foundation  Wiki  for linux installation at

These worked perfectly with some only a few minor changes to accomodate Windows

  • I had Java 6 jdk  and ANT already installed so  I skipped those steps.
  • I followed the ‘Adding paths, JAVA_HOME and ANT_HOME’ section by setting
    – JAVA_HOME to D:\Program Files\Java\jdk1.6.0_21
    – I had ANT in my path already (D:\apache-ant-1.8.1\bin)  for a different application so did not set up ANT_HOME 
  • Downloaded and ran Subversion from http://subversion.apache.org/packages.html  –  taking a Windows version  Win32Svn (32-bit client, server and bindings, MSI and ZIPs; maintained by David Darj)
  • Downloaded Planets Server and Planets Suite Subversion by copying and pasting the OPF instructions.    These installed to a directory D:\~  so renamed that to D:\home after download had finished.

Then over to the planets-server directory : 

  • Copied planets-server.properties.template file to  planets-server.properties
  • Changed the path to the local planets-server to
  • Changed the location of the server configuration directory to
  • Left address/name of the machine as ‘localhost’ as this is a test on my pc
  • Left the port the server will listen on as 8080
  • Left the ssl port the server will listen on as 8443
  • Changed username/ password  for user management database access.  This was a mistake as the Derby DB setup did not work properly and I  had to change back to the original values
  • Copied the email configuration from OPF – as again this was a test implementation

Then over to the Planets-suite directory for similiar changes :

  • Copied build.properties.template to build.properties
  •  Changed the path where the installed IF framework is located to
  • Changed the  location of the IF and service config directory to if_server.conf=D:/home/planets/planets_server/server/default/conf/planets
  • Changed thdirectory that stores the Data Registry configuration to if_server.doms.config.dir=D:/home/planets/planets-server-compiled/server/default/data/planets/dom-config
  • Left the rest as the defaults
    • if_server.host=localhost
    • if_server.port=8080
    • if_server.ssl.port=8443

 Then ran the ANT builds

In Planets-server  …

  • ant deploy:planets-server
  • ant create:dbs
    (The documentation said to expect a number of the sql statements to fail)
  • ant deploy:framework

In Planets-suite …

  • ant deploy:framework
  • ant deploy:services
  • ant deploy:testbed

Then started the  Planets Server by changing to the bin directory where the complied version had been  installed.

cd  D:\home\planets\planets-server \bin

and running  run.bat

To use Planets point your browser at http://localhost:8080/   and login with username user and password user.

So overall an easy process.    Now on to exploring the operational aspects

David Piper



About epiccambridge

Project Manager of the JISC funded EPIC Project
This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s