Setting up a Project.net Developer Workstation

  1. Setting up a Project.net Developer Workstation
      1. Step 1 -- Download the needed 3rd party software
      2. Step 2 -- Checkout the Project.net Source Code from the Subversion …
      3. Step 3 -- Configure your workstation for building the source code
      4. Step 4 -- Setup a development database
      5. Step 5 -- Configure the Project.net Application
      6. Step 6 -- Install License Files

A project.net development and build environment can be created on any operating system platform that supports Java, the BEA Weblogic application server, the ant utility, and a Subversion client. Many of the examples in this document are for the Windows operating system, however for Linux/Unix installations, only the file paths and command shell syntax differ.

See the document attachement below on "Configuring a Project.net Development Workstation" for details on these steps.

Step 1 -- Download the needed 3rd party software

To build and run the Project.net application, you will need the following 3rd party software. BEA and Oracle offer free developer downloads of their products.

Step 2 -- Checkout the Project.net Source Code from the Subversion Repository

Refer to this page for directions on downloading a copy of the the Project.net source tree.

Step 3 -- Configure your workstation for building the source code

See the document attachement below on "Configuring a Project.net Development Workstation".

Step 4 -- Setup a development database

  • Install Oracle 10.2 Enterprise Edition
  • Create an Oracle database instance (called v82dev or any name you want). Set and remember the SYSTEM password.
    NOTE: if you have installed the Oracle database on a server (not your development workstation, you will still need a working copy of Oracle's sqlplus program. Only minimal client is necessary.
  • Go to the Project.net database creation scripts located in the Project.net source code directory: core/db/oracle/create-scripts/admin
  • Edit the script file pnetMasterDBBuild.bat (Windows) or pnetMasterDBBuild.sh (Linux). Set the environment variables in this script to be appropriate for your installation. Further instructions are available in the file.
  • Run the Script file pnetMasterDBBuild.bat (Windows) or pnetMasterDBBuild.sh (Linux) from the core/db/oracle/create-scripts/admin directory.
  • Check the logs in the log file location you have specified inside of the pnetMasterDBBuild file. Ensure that there are no errors.
  • If the script fails and you need to re-run it, it's best to run the core/db/oracle/create-scripts/tools/drop_pnet_and_user_schemas.sql script to clean everything up before trying again.

Step 5 -- Configure the Project.net Application

After the project.net application is running, you need to configure a few parameters within the application:

login as the application administrator. NOTE: you can't register and login as a new user until you complete Step 6 below. 

username: appadmin
password: appadmin

Change the file path for document storage on your computer.

Click "Application Space" on the lower left to view and change Project.net application configuration.
Click the "Manage --> Doc Vault" link
Enter a directory path for each of the three "Path to Repository Root" such as:
c:\pnet-doc-vault\one
c:\pnet-doc-vault\two
c:\pnet-doc-vault\three

You may also need to change some of the application settings on the Application Space --> Sys. Settings page to match your server. For instanace, if you are running on linux, you will need to change the postDataTempDir setting since it default to a Windows C:\temp directory.

If you want the URLs in the email notifications to match your machine, you will need to change three configuration tokens. Go to the Application Space --> Configurations --> Project.net configuration --> Tokens --> select Basic Branding --> click Filter

Modify the following tokens used to construct the email notification URLs, probably with the following values: 

prm.global.brand.defaulthost            localhost
prm.global.brand.defaultjsprooturl      /
prm.global.brand.defaultsitescheme      http://

Step 6 -- Install License Files

You need to install a Project.net license properties file and license certificate so you can create user accounts for testing the application. It is important to test using regular users (with various roles such as Space Admin and Team Member). The appadmin user is not good for testing since that user has special security permissions and access checks are bypassed on most pages.

See Installing Licensing Files.pdf from the Downloads page for instructions on installing the License Properties and License files.