Preparing to Install Project.net

In addition to the required hardware and software to run Project.net, you will need some information prior to installing Project.net. This list outlines those requirements based on the servers you need to install.

To install the Oracle database server you need:

1. Remote access to the console of the database server (Remote Desktop Connection, VNC, SecureClient, etc)
2. System username and password authorized to install software
3. Access to the Oracle install package (local hard drive or Internet download)

To create and configure the Project.net database you will need:

1. The hostname of the Oracle database server.
2. Remote access to the database server or the system that will host the Project.net application server.
3. A working copy of sqlplus installed on this system. Normally, sqlplus is installed with the Oracle database, but if not, the Oracle instant client is sufficient.
4. The system password for the Project.net database instance.
5. A Project.net database has two users, you will need to specify passwords for these users.

To set up your Project.net application server you will need:

1. Remote access to the console of the application server (Remote Desktop Connection, VNC, SecureClient, etc)
2. Username and password authorized to install software
3. Access to the WebLogic or Tomcat install package (local hard drive or Internet download)
4. A specified username and password for the WebLogic administrator's account
5. A mechanism for copying files to the application server (ftp, !WinSCP, Internet)
6. SqlPlus access to the database server from the application server
7. Project.net database SID
8. User name and passwords for the two Project.net database users, as defined above.
9. The fully qualified name of your Project.net server (e.g. login.project.net)
10. The location of the document vault file store. This can be a location on a local or network file share.
11. The location of a temporary storage area for Project.net to use while uploading files, such as C:\temp. This can be a location on a local or network file share.
12. You will need to know the information for your SMTP mail server.
13. The fully qualified name of your Project.net server.
14. The label on the login page; the default is “Member Log In”.
15. The time zone chosen as the default when users register.
16. The Project.net Master License Properties file for your installation (this may be provided by Project.net).
17. Internet access to the Project.net web server, to test the installation
18. Email addresses for the following purposes

Name	Purpose	Default value
Support Team	Specifies the email address listed in the Help pages for support queries. It is also used if a user submits an automated error report within the application	support@project.net
From address	Used as return address in notifications and messages sent from Project.net	Project.net Notification <noreply@project.net>
Feedback address	Feedback initiated from Project.net is sent to this address.	feedback@project.net
Information request	Address listed on the Contact Us page in help information.	pnet-info@project.net

1. URLs for the following purposes

Token	Used when someone clicks on...	Default value
login.href	...the Project.net Home label on the login page	http://www.project.net
logo.login.href	...the Project.net logo on the login page	http://www.project.net
default.site.href	...any link that does not have a URL specified	http://www.project.net

To utilize an LDAP or AD server for authentication you will need:

To required information for configuring Project.net to use an LDAP or AD server for authentication refer to the Configure Project.net for an LDAP Server page.

To link the application server to a web server you will need:

1. Remote access to the console of the web server host system (Remote Desktop Connection, VNC, SecureClient, etc)
2. System username and password authorized to install or configure IIS.
3. The Username and password of an account with administrative rights on the application server.
4. If desired, the application can be protected using SSL. These certificates usually need to be ordered in advance and configured on the web server prior to the install of the Project.net application.