9 1:Configuration and License Properties

From Pnet-Community

Jump to: navigation, search

Contents

[edit] Project.net Configuration and License Properties

Once Project.net is installed, there are a few items to finish before it can be used: update the administrator account, set some system settings and install a license.

[edit] Update the appadmin user account

There is one application administrator account pre-defined for a Project.net installation, appadmin. For security reasons you should change some of the default settings for the appadmin account, such as password and email address, as described below. Project.net Application Administrator Accounts contains guidelines for using this account and tells how to create other administrator accounts.

[edit] Prerequisites

  • You will need the following information for the built-in administrator's account
Item Description Default
email address Email address for the appadmin account. Used to recover the appadmin's password
username Username for logging in using the Admin account appadmin (It is not recommended that you change this)
Password A secure password for the appadmin account appadmin
Jog question/answer A question you will be asked if you forget your password and its answer

[edit] Instructions

  1. Log into the Project.net server, http://localhost:8080, as appadmin user (default password: appadmin).
  2. From the Personal Workspace select Setup from the left-hand menu.
  3. Click Personal Profile.
  4. In the Name sub-tab enter the Primary Email Address:
  5. In the Login sub-tab
    a. Enter appadmin as the current user account and password.
    b. Check-mark Change Password and enter a new secure password.
    c. Check-mark Change Jog Question or Answer and enter a question and answer you will easily remember. If you need to recover the appadmin's password this question will be used to validate you.
  6. Click Submit

[edit] Configure Project.net System Settings

Now that the server is up and running, you will need to configure some settings within Project.net. These are set through the Application Administration interface.

[edit] Specify document vault storage

[edit] Instructions

  1. If not already logged into the Project.net server, log into http://localhost:8080, if application is deployed as the ROOT, or default, application otherwise log into http://localhost:8080/<Your desired application name>/, as appadmin user.
  2. From the Personal Workspace, click "Admin" at the top of the page next to the log out link to enter the Application Administration interface.
  3. Select Manage / Doc Vault from the menu ribbon.
  4. Enter a directory path for each of the three "Path to Repository Root" such as:
C:\Project-Net\docvault\vault-1
C:\Project-Net\docvault\vault-2
C:\Project-Net\docvault\vault-3
Or in Linux:
/var/Project-Net/docvault/vault-1
/var/Project-Net/docvault/vault-2
/var/Project-Net/docvault/vault-3
(Be sure to set the CATALINA_HOME variable or you will get an Invalid Directory message when setting the directory path for Doc Vault)
Click [Update].

[edit] Customize system settings

[edit] Prerequisites

  • You should be logged into the Application Administration as above
  • Note, if document upload or Microsoft Project import is failing, check the settings in this section.

[edit] Instructions

  1. Select Manage / Sys. Settings from the menu ribbon.
  2. Change the following variables:
    • Variable: siteHost
      • New Value: The external name of the Project.net website.
      • Description: This variable defines the hostname and port number that Project.net uses when it constructs URLs containing the hostname and port of the web site. Typically used in email notifications, this variable should be set to the fully qualified name of your Project.net server.
      • Example values: myserver.com, myserver.com:7001
    • Variable: supportEmail
      • New Value: Email address of support team.
      • Description: 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.
      • Example value: support@project.net
    • Variables: postDataTempDir and xmlImportTempDirectory
      • New Value: File path to directory for tempoary file storage
      • Description: : This value is used as a temporary storage when uploading files. Make sure that the Tomcat user has access to write in the specified directory.
      • Example value: C:\tmp or /opt/pnet/tmp
  3. [Submit] to accept your changes. They will not take effect until the server has been restarted from the Tomcat Management Console or the Windows Services Console.

[edit] Create a configuration for your installation

Project.net contains many of its settings in configuration tokens; these tokens are stored in named configuration sets. For example, if you want your company's name and logo to appear on the Project.net login page, you would change the values of two specific tokens.

While you can alter the Project.net default configuration set, it is recommended that you create a configuration just for your installation. Project.net will first use the values from your configuration. Any values not set in your configuration will receive their values from the system default configuration. Using a separate configuration isolates your custom settings, making them more obvious. More importantly, alternate configurations are preserved whenever the Project.net software is upgraded, while the default configuration loses any changes.

Note, Project.net can have more than one active configuration. Which configuration is selected for a user is determined by the URL or IP address he or she used to access the Project.net server. For example, users accessing the server through projects.mycompany.com may see the results of the default configuration, while those using custom-projects.mycompany.com could see a site customized by an alternate configuration.

For more information see Customizing and Branding Project.net

[edit] Modify the default configuration

You must change one token in the default configuration.

[edit] Instructions

  1. From within the Application Administration interface, chose Manage / Configurations.
  2. Click on Project.net Configuration from the list of configurations.
  3. Choose Tokens from the menu on the left.
  4. Enter defaulthost in the Token Name: search field and click the Filter button.
  5. Change the Project.net Default value of prm.global.brand.defaulthost to the external name of the Project.net website. Usually, this is the same as the siteHost variable above.
  6. Also set the value for the prm.global.default.email.fromaddress token, as well.
  7. Submit your changes. They will not take effect until the server has been restarted from the Tomcat Management Console or the Windows Services Console.

[edit] Create a custom configuration

Follow these steps to create a installation-specific configuration

[edit] Instructions

  1. From within the Application Administration interface, chose Manage / Configurations.
  2. Click the [New] Toolbox action to create a new configuration.
  3. Enter
    • Name - Suggestion: use Standard Production Configuration or use the value used for the siteHost token.
    • Description - Suggestion: include the siteHost value as part of the description.
    • Choose the Default Language, you _must_ select a value.
    • Select multiple Supported Languages by holding down the Control key while clicking the desired names. You can leave this as the default value.
    • Supported Host Names (CSV) – The values in this field determine when this configuration set will be used. List the web site names you want associated with configuration, separated by commas. If you enter projects.mycompany.com, login.projects.mycompany.com either address will cause the values in this configuration set to be used, in conjunction with the values from the default configuration.
  4. Submit your changes to create the configuration set.

[edit] Site-specific token values

Follow these steps to create a installation-specific configuration

[edit] Instructions

  1. From within the Application Administration interface, chose Manage / Configurations.
  2. Click on the name of the custom configuration from the list of configurations.
  3. Choose Tokens from the menu ribbon.
  4. Select Basic Branding from the Category list.
  5. Click Filter
  6. Set the appropriate values for the tokens below.
  7. If a token does not appear in the list you can enter its name in the Token Name: search field and click the Filter button to locate it.
    prm.global.brand.defaulthost: Same as the default configuration token
    prm.global.brand.defaulttimezone
    prm.project.login.login_header_text-1 (Login prompt)
    prm.global.default.email.fromaddress
    prm.global.help.feedback.emailaddress
    prm.global.help.info.emailaddress
    prm.global.help.legal.emailaddress
    prm.global.help.sales.emailaddress
    prm.global.help.support.emailaddress
    prm.base.errors.reportErrors.email
  8. Submit your changes.
  • If you get an error message (Null Pointer Exception) when you submit your changes you forgot to select a default language for the configuration. Go back to the configuration's properties and edit them to set the Default Language.

For information on customizing Project.net with your company's text and images see Customizing and Branding Project.net.

[edit] Install the Master License Properties for your Server

All Project.net servers require Project.net Master Properties. Without these properties it is not possible to register as a user or log in except as the application administrator.

[edit] Prerequisites

  • The document Installing Licensing Files.pdf from the Project.net Downloads contains complete details. A brief summary of the license installation steps is listed below.
  • The Master License Properties and License Key files for Open Source installations are available from the Project.net Downloads.

[edit] Instructions

  1. If not already logged into the Project.net server, log into http://localhost:9090 as apachemanager user.
  2. From the Personal Workspace, click "Admin" at the top of the page next to the log-out link to enter the Application Administration interface.
  3. Select Manage / Licensing from the menu ribbon.
  4. Click on the Licensing Tasks sub-tab near the top of the screen.
  5. Click on Update License Properties.
  6. Follow the steps on the screen, pasting in the license properties from the license file you received from Project.net.
  7. Again, click on the light blue Licensing Tasks tab near the top of the screen.
  8. Click on Install a new license.
  9. Follow the steps on the screen, pasting in the license key from the license file you received from Project.net.

[edit] Installation and Configuration Complete

That's it, Project.net is ready to go. Your next step is to create a regular user account for yourself by registering from the login page using the license key you installed above. With this user you can create businesses and projects, invite other users to those projects, and begin to explore the functionality of Project.net. Tutorials, training guides and documentation are available from the Using Project.net page.

[edit] More Help

Personal tools