Installing Project.net in a Production Environment For Application Servers on Windows Platforms

  1. Installing Project.net in a Production Environment For Application Servers …
  2. Step 1: Review checklist of requirements
  3. Step 2: Unpack the Project.net Installation Package
  4. Step 3: Install and configure the Oracle database server
    1. Prerequisites
    2. Instructions
  5. Step 4: Create and configure the Project.net database
    1. Prerequisites
    2. Instructions
  6. Step 5: Install and Configure the BEA WebLogic Server
    1. 5.1: Install the BEA WebLogic Server
      1. Prerequisites
      2. Instructions
    2. 5.2: Create pnet Domain with admin Server
      1. Prerequisites
      2. Instructions
    3. 5.3: Update the Java Security for Strong Encryption
      1. Prerequisites
      2. Instructions
    4. 5.4: Endorse the Xalan XSLT Jar Files
      1. Instructions
    5. 5.5 Install Node Manager as a service
      1. Prerequisites
      2. Instructions
    6. 5.6 Configure PRM-1 Server in the pnet Domain
      1. Prerequisites
      2. Instructions
    7. 5.7 Deploy Project.net to PRM-1 Server
      1. Prerequisites
      2. Instructions
  7. Step 6: Configure Project.net Server Logging
    1. Prerequisites
    2. Instructions
  8. Step 7: Configure Project.net System Settings
    1. 7.1 Specify document vault storage
      1. Instructions
    2. 7.2 Customize system settings
      1. Prerequisites
      2. Instructions
    3. 7.3 Create a configuration for your installation
      1. 7.3.1 Modify the default configuration
        1. Instructions
      2. 7.3.2 Create a custom configuration
        1. Instructions
      3. 7.3.3 Site-specific token values
        1. Instructions
  9. Step 8: Install the Master License Properties for your Server
    1. Prerequisites
    2. Instructions
  10. Step 9: Configure Project.net Server to Automatically Restart
    1. 9.1 Install admin service
      1. Prerequisites
      2. Instructions
    2. 9.2 Install PRM-1 server as a Managed Service
      1. Prerequisites
      2. Instructions
  11. Step 10: Linking WebLogic to the web server
    1. 10.1 Microsoft Internet Information Server (IIS)
      1. Prerequisites
      2. Instructions
    2. 10.2 Apache Web Server
      1. Prerequisites
      2. Instructions
  12. Step 11: Finished
  13. Troubleshooting the Installation

This document guides a user through the process of installing Project.net, version 8.2.1, on a Windows application (WebLogic) server. In addition to the application server, a Project.net installation will also require: web server, database server, mail (SMTP) server, document vault (file server) and LDAP server (optional).

Step 1: Review checklist of requirements

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

The installation package includes the Project.net software in a CD or zip archive file. The first step to installing Project.net is to unpack the software onto an accessible file location.

  1. If it does not exist, create a temporary directory to unpack the installation package, suggested, C:\pnet. These instructions will refer to this location throughout the steps.
  2. Unzip the zip file from your download or installation CD into the C:\pnet directory. This file is located in the Software\ subdirectory. Once unpacked, you will have c:\pnet\v8.2.1.

Step 3: Install and configure the Oracle database server

Project.net requires an Oracle database server. Follow the instructions in this section to install and configure an Oracle database server, if one is not prepared.

Prerequisites

  • A copy of Oracle as specified in the Project.net 8.2 Deployment Requirements.
  • If you are installing on a system with a non-static IP address, served from a DHCP-server, you will need to install a Microsoft Loopback Adapter. Follow How to install the Microsoft Loopback adapter in Windows XP. When complete, open the new adapter’s properties and set its IP address to a non-routing address, like 192.168.x.x (where x is any number between 0 and 255). Also, set its Subnet mask to 255.255.255.0. Make note of this address, you will need it further in the installation.

Instructions

  1. Start the Oracle 10g Database Installation program.
  2. Choose Enterprise Edition as the Installation Type.
  3. Uncheck Create Starter Database.
  4. Click [Next].
  5. Confirm that the Product-Specific Prerequisite Checks have passed and correct any errors.
  6. Click [Next].
  7. Review the installation summary and click [Install].
  8. When complete, exit the installer.

Step 4: Create and configure the Project.net database

This section will guide you through the steps of creating the tables, stored procedures and such for the Project.net database.

Prerequisites

  • An Oracle database server, installed as above.
  • A working copy of sqlplus. Normally, this is installed with the Oracle database, but if not, the Oracle instant client is sufficient.
  • The system password for the Project.net database instance.
  • You will need to know the database server’s hostname.

Instructions

  1. Run the Oracle Database Configuration Assistant located in the Windows Start/Oracle/Configuration and Migration Tools menu to create a database instance for the Project.net application.
    1. Select Create a Database the click Next.
    2. Choose the General Purpose database template.
    3. Note the Global Database Name and SID that you use.
    4. Choose your preferred management method. If unsure, chose the default.
    5. Note the password(s) you use for the various accounts.
    6. Select the appropriate storage mechanism for your installation. Again, if unsure, chose the default.
    7. Specify the storage location.
    8. And Recovery Configuration.
    9. Do not install the Sample Schemas.
    10. Select the remaining options, as appropriate to your installation, and create the database.
  1. Add a listener using Oracle Net Configuration Assistant.
    1. Start / Programs / Oracle-OraHome10g / Configuration and Migration tool / Net configuration assistant
    2. First screen - select Listener Configuration
    3. Second screen - select Add
    4. Third screen - enter listener name
    5. Fourth screen - keep default values (TCP)
    6. Fifth screen - keep default values (1521)
    7. Sixth screen - Select No (don’t configure another listener) and click Next.
    8. Click Next on the Listener configuration complete screen.
    9. Click Finish on the Welcome screen.
  1. Update the following files in %ORACLE_HOME%\NETWORK\ADMIN\ (most likely, C:\oracle\product\10.2.0\db_1\NETWORK\ADMIN)
    1. Ensure listener.ora has: 
      LISTENER =
  (DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = <hostname>)(PORT = 1521))
    )
  )
    2. To Tnsnames.ora add after the current entries: 
      <database SID> =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = <hostname>)(PORT = 1521))
    )
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SID = <database SID>)
    )
  )
    3. To sqlnet.ora add at the end: 
      NAMES.DIRECTORY_PATH= (TNSNAMES)
  1. CHECKPOINT: Ensure the Oracle Database listener services are running.
    1. Run the command lsnrctl status in a command window and check the values for: 
        - ALIAS
  - Listener Parameter File
  - Listening Endpoints Summary
    2. Open the Windows Services Monitor (Start / All Programs / Administrative Tools / Services) and look for: 
        - OracleDBConsole<SID>
  - OracleOraDb10g_home1TNSListener<Listener name>
  - OracleService<SID>
    3. Close the Windows Services Monitor
    4. Return to the command window and check TNS connect identifier with tnsping <database SID>.
    5. Also, check that sqlplus system/<database admin password>@<database name> connects.
    6. Close the command window.
  1. Change directory into the C:\pnet\v.8.2.1\weblogic\installer\database\admin directory.
  1. Using the editor of your choice, edit the pnetMasterDBBuild.bat file. Set the environment variables in this script to be appropriate for your installation. Further instructions are available in the file.
  • Note: the PNET_BUILD_DB_SCRIPTS_PATH should be set to c:\pnet\v8.2.1\weblogic\installer\database
  • The directory specified for PNET_BUILD_DB_LOG_PATH must exist; create it if it does not. Suggested is c:\pnet\logs.
  1. To start the database installation, run the batch command pnetMasterDBBuild.bat from the installer\database\admin directory. The script will take some time to run; you can monitor its progress by checking the log file you specified inside of pnetMasterDBBuild.
  • When complete, check the log for errors. You will notice some errors in the logs about public synonym already existing, but there should be only about 55 lines in the log file with the word “ERROR”.
  • 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: Install and Configure the BEA WebLogic Server

This section outlines the BEA WebLogic configuration settings needed for a production deployment of the Project.net application.

5.1: Install the BEA WebLogic Server

Prerequisites

  • Project.net 8.2.1 requires BEA WebLogic 8.1 SP3-SP6. For best performance and reliability, use BEA WebLogic 8.1 SP6.
  • The WebLogic console interface may differ slightly than described in this document

Instructions

  1. Install WebLogic 8.1.6 (SP6); accepting the defaults and selecting Express Install will result in an installation at C:\bea. Uncheck Start Quick Start on the completion screen.

5.2: Create pnet Domain with admin Server

Prerequisites

  • BEA WebLogic 8.1 SP3-SP6 installed as above.
  • The WebLogic console interface may differ slightly than described in this document.
  • A user name and password for the WebLogic administrator.
  • For more information on configuring and administering BEA WebLogic 8.1, see the following BEA Documentation:Configuring and Managing WebLogic Server

Instructions

  1. Open the Bea WebLogic Configuration Wizard from Start / All Programs / BEA WebLogic Platform 8.1 / Configuration Wizard
  2. Create a new WebLogic configuration.
  3. Basic WebLogic Server Domain.
  4. Choose Custom configuration.
  5. Name: admin
  6. Select the default values until, Administrative Username and Password. Choose a secure name and password; make sure to note them.
  7. Choose Production Mode for production server & the Sun SDK.
  8. Domain name: pnet.
  9. When finished, the Configuration Wizard will close.

5.3: Update the Java Security for Strong Encryption

Prerequisites

Instructions

  1. Locate the downloaded zip archive of the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 1.4.2.
  2. Unzip the individual policy files into the jre/lib/security directory of the BEA JRockit Java runtime (JVM) location from Step 8 above. Most likely, the location is c:\bea\jrockit81sp6_142_10\jre\lib\security.
  • Place the files directly into the security directory, overwriting any existing files that conflict.

5.4: Endorse the Xalan XSLT Jar Files

Project.net uses Xalan XSLT Jar files that are a different version than those included in the standard Java JRE/JDK. These files are included in the installer\jdk\endorsed directory in the Project.net product installation CD or unzipped directory. Move them to the jre\lib\endorsed subdirectory of the BEA JRockit Java runtime (JVM) location; look for a directory starting with jrockit in the C:\bea directory.

Instructions

  1. mkdir c:\bea\jrockit81sp6_142_10\jre\lib\endorsed
  2. copy c:\pnet\v8.2.1\weblogic\installer\jdk\endorsed\*.jar c:\bea\jrockit81sp6_142_10\jre\lib\endorsed

5.5 Install Node Manager as a service

Prerequisites

Instructions

  1. Edit C:\bea\weblogic81\server\bin\installNodeMgrSvc.cmd script and uncomment the following values: 
    set NODEMGR_HOST=localhost
set NODEMGR_PORT=5555
  2. Open a command window and run the !installNodeMgrSvc.cmd script.
  3. Open the Windows Services Console (Start / All Programs / Administrative Tools / Services).
  4. Right-click on BEA WebLogic 8.1.6 NodeManager and select Properties.
  5. Click the Recovery tab.
  6. Set "Select the computer's response if this service fails” for the First, Second and Subsequent failures to "Restart the Service"
  7. Click [OK] and close the Services Console.
  8. Edit c:\bea\weblogic81\common\nodemanager\nodemanager.hosts and add the IP address of the host system to allow only local servers to connect.

5.6 Configure PRM-1 Server in the pnet Domain

Prerequisites

  • BEA WebLogic application server installed as above.
  • The WebLogic console interface may differ slightly than described in this document; it varies slightly from SP3-SP5.
  • IMPORTANT: The BEA Jrockit JVM that ships with 8.1 SP5 does not work with the Project.net application. You can still install 8.1 SP5, but you will need to use the Sun JVM or the version of JRockit that shipped with WebLogic 8.1 SP4. If possible, use 8.1 SP6.
  • The WebLogic administrator user name and password.
  • A copy of Configuring BEA WebLogic for Project.net 8.2.1 attached at the end of this page.
  • The information used for the Project.net database instance above.
  • The location of the document vault file store. This can be a location on a local or network file share.
  • You will need to know the information for your SMTP mail server.
  • For more information on configuring and administering BEA Weblogic 8.1, see the following BEA Documentation:Configuring and Managing WebLogic Server.

Instructions

  1. Temporarily start the pnet domain admin server from Start / All Programs / BEA WebLogic Platform 8.1 / User Projects / pnet / Start Server
  2. A command window will open:
    1. Enter the WebLogic administrator's user name defined when you installed WebLogic (default weblogic).
    2. Enter the WebLogic administrator's password (default weblogic).
  3. Open a web browser, enter the URL: http://localhost:7001/console
  4. Log in using the username / password used above.
  5. Select Servers from pnet tree in the left pane.
  6. Choose Configure a new Server…
  7. Configure a new server using the settings in Configuring BEA WebLogic for Project.net 8.2.1 attached to this page.
  8. Test PRM-1
  • start PRM-1 from Servers-->PRM-1-->Control-->Start/Stop then click on the "View server log link" on that page.

5.7 Deploy Project.net to PRM-1 Server

Prerequisites

  • BEA WebLogic 8.1 SP3-SP6 installed as above.

Instructions

  1. If not logged into the WebLogic Console, follow Steps 1 – 4 in Section 5.6 above.
  2. Select Deployments / Applications from pnet tree in the left pane.
  3. Choose Deploy a new Application…
  4. Specify the location of the Project.net EAR (pnet.ear) file you unpacked with the archive in Step 2, usually c:\pnet\v8.2.1\weblogic. You may either:
    1. Enter the path in the set new Location text box (c:\pnet\v8.2.1\weblogic) and press [Enter], or
    2. Click on the links in the Location: path.
  • Note, if the archive is not located on the system you can use the upload your file(s) link hidden in the instructions to browse your local file system and upload the archive.
  1. Choose pnet.ear from the list, and then click Target Application.
  2. Check PRM-1 and click [Continue].
  3. Select Copy this application onto every target for me.
  4. Choose an appropriate name, such as "pnet-8.2.1-enterprise"
  5. Click [Deploy]
  6. The Deployment Status page will show Deployment Status Unavailable - this is OK because deployment is deferred
  7. Restart PRM-1 from WebLogic.
    1. Pnet -> Servers -> PRM-1 -> Start/Stop -> Force Shutdown of this server…
    2. Click Yes
    3. Pnet -> Servers -> PRM-1 -> Start/Stop -> Start this server…
    4. Click Yes
    5. Wait until the Status for PRM-1 shows TASK COMPLETED.
    6. Review each of the logs available at Pnet -> Servers -> PRM-1 -> Remote Start Output
  8. Check the deployment status of "pnet-8.2.1-enterprise"
  9. Log into http://localhost:20000 as appadmin.

Step 6: Configure Project.net Server Logging

Prerequisites

Instructions

  1. If it does not exist, create the directory C:\pnet\config
  2. Copy C:\pnet\v8.2.1\weblogic\installer\logconfig\log4j-config.xml to C:\pnet\config\log4j-config.xml
  3. Edit C:\pnet\config\log4j-config.xml file and modify the value for the name of the log file by deleting @default.logging.location@/, as shown: 
    <param name="file" value="pnet-application.log"/>

Step 7: 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.

7.1 Specify document vault storage

Instructions

  1. If not already logged into the Project.net server, log into http://localhost:20000 as appadmin user (default password: appadmin).
  2. From the Personal Workspace, click "Application Space" on the lower left to enter the Application Administration interface.
  3. Select Manage / Doc Vault.
  4. 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
  5. Click [Update].

7.2 Customize system settings

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.

Instructions

  1. Select Manage / Sys Settings
  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
  • Variable: postDataTempDir
    • 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 WebLogic user has access to write in the specified directory.
    • Example value: C:\temp
  • Variable: mpdImportTempDirectory
    • New Value: File path to directory for tempoary file storage
    • Description: : This value is used as a temporary storage when importing a Microsoft Project file - the file is placed here before it is converted into Project.net format. Make sure that the WebLogic user has access to write in the specified directory.
    • Example value: C:\temp

7.3 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.

7.3.1 Modify the default configuration

You must change one token in the default configuration.

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. Submit your changes. They will not take effect until the server has been restarted from the WebLogic Console or the Windows Services Console.

7.3.2 Create a custom configuration

Follow these steps to create a installation-specific configuration

Instructions

  1. From within the Application Administration interface, chose Manage / Configurations.
  2. Click the Create icon 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.
    • Abbreviation – This will be used as part of the token identifier.
    • Choose the Default Language. You can leave this as the default 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.

7.3.3 Site-specific token values

Follow these steps to create a installation-specific configuration

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 on the left.
  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.defaultjsprooturl: /
prm.global.brand.defaulttimezone
prm.global.brand.defaultsitescheme: http://
prm.global.login.channel.login.title
prm.global.brand.logo.login.href
prm.global.default.site.href
prm.global.footer.copyright.href
prm.global.login.requestinformation.text
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. They will not take effect until the server has been restarted from the WebLogic Console or the Windows Services Console.

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

Step 8: 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.

Prerequisites

  • The document Installing Licensing Files.pdf from the Downloads page 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 Downloads page.

Instructions

  1. If not already logged into the Project.net server, log into http://localhost:20000 as appadmin user (default password: appadmin).
  2. From the Personal Workspace, click Application Space on the lower left to enter the Application Administration interface.
  3. Select Licensing in the left navigation bar.
  4. Click on the light blue Licensing Tasks 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.

Step 9: Configure Project.net Server to Automatically Restart

The production configuration strategy is to have the BEA WebLogic Node Manager and the prm-admin server run as Windows services, while the PRM-1 server is run as a managed server started and restarted by the Node Manager. This will allow Project.net to automatically start when the host system boots up and automatically restart if it ever fails.

9.1 Install admin service

This service automatically starts the WebLogic admin server on OS reboots. The admin server hosts the WebLogic console at http://localhost:7001/console.

Prerequisites

Instructions

  1. Copy C:\bea\user_projects\domains\pnet\installService.cmd script to C:\bea\user_projects\domains\pnet\install-admin-Service.cmd
  2. Edit C:\bea\weblogic81\server\bin\install-admin-Service.cmd script and look for the command to “Install the service”: 
    Modify the line for installing the service ("%WL_HOME%\server\bin\beasvc") to include -delay:120000
  3. Execute the admin install script in a command window substituting the WebLogic administrator username and password: 
    c:\bea\user_projects\domains\pnet\install-admin-Service.cmd Weblogic-Administrator-Username
 Weblogic-Administrator-Password
  4. You can confirm the installation of the admin server by opening the Windows Services console and looking for beasvc pnet_admin. If the console is already open, choose Action / Refresh.

9.2 Install PRM-1 server as a Managed Service

If PRM-1 is installed as a Managed Service, Node Manager will start, kill and restart the PRM-1 server as needed.

Prerequisites

Instructions

  1. Copy C:\bea\user_projects\domains\pnet\installService.cmd script to C:\bea\user_projects\domains\pnet\install-PRM-1-Service.cmd
  2. Edit C:\bea\user_projects\domains\pnet\install-PRM-1-Service.cmd script and verify the following values. Change any that are not correct. 
    Set PRODUCTION_MODE=true
set JAVA_VENDOR=BEA
set JAVA_HOME=E:\bea\jrockit81sp6_142_10 
set SERVER_NAME=PRM-1
set DOMAIN_NAME=pnet
  3. Add the following: 
    @rem PRM-1 is a managed server, set the URL for the admin server.
set ADMIN_URL=http://localhost:7001
  4. Change JAVA_OPTIONS to the same values used in the WebLogic console for console/pnet/Servers/PRM-1/Remote Start/Arguments. These values are also listed in the Configuration:: Remote Start section of Configuring BEA !WebLogic for Project.net 8.2.1 document. They will be similar to: 
    set JAVA_OPTIONS= -Xms1024m -Xmx1024m –Xns60m -Xnohup -Xgc:gencon
-Xmanagement -Xnoopt -Xdebug -Xnoagent -Djava.compiler=NONE 
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005
-Dlog4j.configuration=file:///C:/pnet/config/log4j-config.xml
  5. Look for the command to “Install the service”: 
    Add to the Install the service line, "%WL_HOME%\server\bin\beasvc":
-depend:"beasvc pnet_admin”
  6. Save the script file.
  7. Execute the PRM-1 install script in a command window substituting the WebLogic administrator username and password:

c:\bea\user_p:qrojects\domains\pnet\install-PRM-1-Service.cmd Weblogic-Administrator-Username Weblogic-Administrator-Password

  1. You can confirm the installation of the PMR-1 server by opening the Windows Services console and looking for beasvc pnet_PRM-1. If the console is already open, choose Action / Refresh.
  2. Shut down servers in WebLogic.
  3. Reboot system.
  4. Check services (all three should be running).
  5. Log in to Project.net.

Step 10: Linking WebLogic to the web server

The final step is to link the WebLogic server to a web server. The web server will handle the requests coming from the user and marshal the appropriate one to the WebLogic server for processing by the Project.net PRM-1 server. WebLogic Server may be operating in a different process, possibly on a different host. To the end user — the browser —the HTTP requests delegated to WebLogic Server still appear to be coming from the web server.

10.1 Microsoft Internet Information Server (IIS)

WebLogic provides a Microsoft Internet Information Server Plug-In to seamlessly link the two servers.

Prerequisites

Instructions

  1. Login to the WebLogic Admin server.
  • http://localhost:7001
  • Use the username and password you created when you set up the server (default weblogic)
  1. Specify IIS plug-in
  • Select Servers from pnet tree in the left pane.
  • Select PRM-1 from server tree.
  • Open the Configuration / General tab.
  • From the bottom of the page, click Advanced Options show.
  • Make sure the box labeled WebLogic Plug-In Enabled is checked, then [Apply] at the bottom of the page.
  1. Restart PRM-1 server from the Windows Services console.
  • Open the Windows Services Monitor (Start / All Programs / Administrative Tools / Services)
  • Look for beasvc pnet_PRM-1.
  • Click Restart.
  1. On the system where IIS is deployed, create a directory named C:\pnet\deploy\www-scripts\
  2. Copy the iisproxy.dll and iisforward.dll files from the WL_HOME/server/bin directory of your WebLogic Server installation (where WL_HOME represents the top-level directory for the WebLogic Platform) to C:\pnet\deploy\www-scripts\.
  3. In the C:\pnet\deploy\www-scripts\ directory, create a file named iisproxy.ini with the following contents: 
    # This file contains initialization name/value pairs
# for the IIS/WebLogic plug-in.
WebLogicHost=localhost
WebLogicPort=20000
ConnectTimeoutSecs=60
ConnectRetrySecs=2
WlForwardPath=/
PathTrim=/
Debug=OFF
DebugConfigInfo=OFF
KeepAliveEnabled=true
  • If IIS is running on a different system than the WebLogic server, use the hostname and port of the WebLogic server.
  1. Start the Internet Information Service Manager by selecting it from the Start menu.
  2. In the left panel of the Service Manager, select your IIS Web site (the default is "Default Web Site").
  3. Open the properties for the selected Web site by right-clicking the Web site selection in the left panel and selecting Properties.
  4. In the Properties panel, select the Home Directory tab, and click the Configuration button in the Applications Settings section.
  5. On the Mappings tab, click the Add button.
  6. In the Add dialog box, browse to the iisproxy.dll file (c:\pnet\deploy\www-scripts\iisproxy.dll).
  7. Set the Extension to wlforward
  8. If you are configuring for IIS 6.0 or later, be sure to deselect the "Check that file exists" check box.
  9. When you finish, click the OK button to save the configuration.
  10. Make sure Cache ISAPI applications box is checked.
  11. On the ISAPI Filters tab, click the Add button.
  12. Set the Filter Name to iisforward
  13. Executable C:\pnet\deploy\www-scripts\iisforward.dll
  14. [Apply]
  15. Click the OK button to close the Properties panel.
  16. If you are configuring IIS 6.0 select Web Service Extensions set All Unknown ISAPI Extensions to Allowed
  17. Stop the web site, if it is started.
  18. Click the "Play" arrow in the toolbar to start the web site.

10.2 Apache Web Server

Prerequisites

  • Apache Web Server, version 2.0, installed and configured.
    • Project.net 8.2.1 works best with Apache 2.0, while you can use Apache 2.2.X you will not be able to configure it with any non-default parameters, including log file parameters, debug parameters, etc.

Instructions

  1. If running, stop the Apache server.
  2. Confirm the version of the Apache web server with the following command: apache.exe -v
  3. Verify that the Apache server was built with the mod_so module. Run the command apache.exe/httpd2 -l and look for mod_so.c in the results list. If you cannot find this module, you should reinstall or rebuild Apache.
  4. Locate the SO module required for WebLogic and Apache integration. Look in the WebLogic installation folder, WL_HOME\server\bin, for a module named mod_wl_20.so. Copy mod_wl_20.so into the modules folder for your Apache installation.
  5. To load this module automatically when the Apache server starts up, edit the Apache httpd.conf configuration file to add the following: 
    LoadModule weblogic_module     modules/mod_wl_20.so

    <IfModule mod_weblogic.c>
   WebLogicHost localhost
   WebLogicPort 20000
</IfModule>

    <Location />
  SetHandler weblogic-handler
  PathTrim /

  ConnectTimeoutSecs=60
  ConnectRetrySecs=2
  Debug=OFF
  DebugConfigInfo=OFF
  KeepAliveEnabled=true
</Location>
  6. Verify the configuration settings by executing the command apache.exe/httpd2 -t. The command should display a 'Syntax OK' message.
  7. The integration is complete, re-start the Apache server.

Step 11: Finished

  1. Installation is now complete, the Project.net application should now be accessible using the URL: http://your-server/
  2. The BEA WebLogic Server Console is available using the following URL: http://localhost:7001/console.
  • Use the user name and password you selected above.
  • The default login is: weblogic
  • The default password is: weblogic
  • Replace localhost with the name of your application server machine if accessing remotely. You may have to open port 7001 on your application server machine

Troubleshooting the Installation

Attachments