9 1:Troubleshooting Installation
 Verifying and Troubleshooting Project.net
 Verifying an Installation
Perform these simple steps to verify that your Project.net installation is set up and configured correctly. Specific directions for completing each step are included in the original installation instructions, referenced at each step below.
Generally, someone other that the person who did the installation should check for errors. In addition to this list, you will need the user names, passwords and settings used by the original installer.
- Check DB installation/connection
- Log into Oracle Home Page, check existence of db
- Use tnsping to check existence of db listener. Follow sub-step 3 of Create and configure the Project.net database]
- Use sqlplus to check connection to db, again, following sub-step 3 listed above.
- Verify the JDBC settings in the Tomcat configuration file as outlined in Deploy Project.net to Tomcat Server].
- Check installation of JRE and Tomcat
- Check location of JVM
- Verify JVM was upgraded with JCE
- Check installation directory of Tomcat
- Check TOMCAT_HOME/bin/Catalina.sh for the correct JAVA_OPTS settings.
- Check that Tomcat is configured to auto-start (depends upon OS how this is done)
- Check deployment & Configuration of Pnet
- Verify TOMCAT_HOME\webapps\ contains the Project.net application war file, either root.war or pnet.war.
- Can you get to the login page at http://<hostname> (root.war installations) or http://<hostname>/pnet (pnew.war installations)?
- Login as appadmin
- Check all settings from Step 9 in Configure Project.net System Settings].
- Check installation of license properties and key
- Register as a test user using license key.
- Verify receipt of email from system while registering
- Review Apache integration settings, plus make sure you can reach the login page via the hostname, as mentioned above.
- If the Activity Log does not show any entries double-check that Apache ActiveMQ is configured and running properly.
- If you get Server Error when you try to make a blog (Blog-It) post double-check that Apache ActiveMQ is configured and running properly.
 Using Project.net Log Files for Troubleshooting
To help debug installation and application issues Project.net provides a logging mechanism utilizing the log4j logger. In addition, the application servers have log files of their own. For installations using Apache Tomcat, the Tomcat log files are saved in CATALINA_HOME/logs.
To control Project.net's level of logging you need to create the file CATALINA_HOME\webapps\ <Project.net deployment directory (ROOT by default)> \WEB-INF\classes\log4j.properties. When log4j.properties is missing logging is turned off. This file also specifies the location of the log file.
For example, the following log4j.properties file sets the logging level to debug (the highest level) and places the resulting log file in C:\Tomcat5\logs\pnet-log.log (Note: Do not use Debug level continuously because it can affect Tomcat performance and the log files grow rapidly).
log4j.rootLogger=DEBUG, logfile, stdout
log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.layout=org.apache.log4j.PatternLayout log4j.appender.stdout.layout.ConversionPattern=%d %p [%c] - <%m>%n
log4j.appender.logfile=org.apache.log4j.RollingFileAppender log4j.appender.logfile.File=C:\\Tomcat5\\logs\\pnet-log.log log4j.appender.logfile.MaxFileSize=8192KB
# Keep three backup files. log4j.appender.logfile.MaxBackupIndex=100
# Pattern to output: date priority [category] - message log4j.appender.logfile.layout=org.apache.log4j.PatternLayout log4j.appender.logfile.layout.ConversionPattern=%d %p [%c] - %m%n