Install Project.net in a Product Environment on Linux

  1. Install Project.net in a Product Environment on Linux
    1. Step 1: Review checklist of requirements
    2. Step 2: Unpack the Project.net Installation Package
    3. Step 3: Install and configure the Oracle database server
    4. Step 4: Create and configure the Project.net database
    5. Step 5: Install and Configure the BEA WebLogic Server
    6. Step 6: Configure Project.net Server Logging
    7. Step 7: Configure Project.net System Settings
    8. Step 8: Install the Master License Properties for your Server
    9. Step 9: make system auto restart
    10. Step 10: Linking WebLogic to the web server
This document is based on Installing Project.net in a Production Environment For Application Servers on Windows Platforms. Linux PNET installation is 80% similar to the Windows-based one.

Step 1: Review checklist of requirements

Most versions of Linux core 2.6 or higher will support Project.net; it has been tested with: Debian, SuSe, Ubuntu, Fedora . Please review the complete list of hardware and software requirements as described in Summary of Project.net 8.2 Deployment Requirements. Make sure you can meet these requirements before installing Project.net. You will also need to read Preparing to Install Project.net.

Step 2: Unpack the Project.net Installation Package

Use unzip Linux console command to get zip's content; place it in any directory.

Step 3: Install and configure the Oracle database server

  • Oracle 10g installation is not as simple as the other steps and should be installed by a server admininstrator or someone familar with your particular Linux installation. Oracle 10g is certified on SuSe Enterprise and RedHat, to name two. It can be installed on other Linux distributions, but this is not a standard installation.
  • Oracle 10g XE is easier to install. It can be downloaded from the Oracle web site as an rpm archive or a Debian package. Installation and configuration is very simple.
  • After completing the installation, make sure you can run sqlplus from a Linux command line.
  1. Look in the file: /etc/init.d/oracle-xe for the following environment variables: 
ORACLE_HOME=/usr/lib/oracle/xe/app/oracle/product/10.2.0/server
ORACLE_SID=XE
export ORACLE_HOME
export ORACLE_SID
export PATH=$ORACLE_HOME/bin:$PATH
  1. Set these variables in a console window.
  1. Verify that you can start sqlplus, then exit the program. You do not need to make any database changes, the Project.net database creation scripts will handle this.

Step 4: Create and configure the Project.net database

  1. Create an empty database
    • If you are using Oracle 10g - refer to the Oracle documentation for how to create a database and configure it.
    • If you are using Oracle XE you are OK, the database is already created.
  2. Configure the database for Project.net
    • Go to the Project.net directory \weblogic\installer\database\admin and edit pnetMasterDBBuild.sh
    • Start pnetMasterDBBuild.sh from database/admin and database data will be created.

Step 5: Install and Configure the BEA WebLogic Server

Installing the WebLogic server is described in Step 5 of the Windows installation instructions.

Linux related changes:

  1. Starting Installation Wizard
    • If you have GUI terminal access you can run server8*_linux.bin and to open an installation wizard.
    • If you have SSH only access, start server installation:
      • ./server816_linux32.bin -mode=console -log=/pnet/tmp/platform_install.log
      • This will run the same wizard, but in console mode.
  2. How to start Configuration wizard:
    • Go to ...bea/weblogic81/common/bin and run:
      • ./config.sh for GUI or
      • ./config.sh -mode=console for SSH
  3. Create Admin domain
  4. Update Java Encryption Policy as in Windows (bea/jdk....).
  5. Copy Xalan-related files as in Windows.
  6. NodeManager
  • NodeManager should already be installed.
    • Start it in another console (a second ssh connection, for example) so you will be able to work with WebLogic at the same time.
      • cd bea/weblogic81/server/bin/
      • ./startNodeManager.sh
    • Alternatively, you may start NodeManager in the background by running ./startNodeManager.sh &
  • Without NodeManager Alive you will not be able to start the Production server via the WebLogic console.
  1. Now you can finish other parts of Step 5 of the Windows installation instructions.

Step 6: Configure Project.net Server Logging

Follow Configure Project.net Server Logging of the Windows installation instructions.

Step 7: Configure Project.net System Settings

Follow Configure Project.net System Settings of the Windows installation instructions.

Step 8: Install the Master License Properties for your Server

Follow Install the Master License Properties for your Server of the Windows installation instructions.

Step 9: make system auto restart

This step is not 100% ready. Ask server administrator to make init scritps for starting Node manager and managed web logic.

Step 10: Linking WebLogic to the web server