Primavera Unifier Installation and Setup Guide

Transcription

1 Primavera Unifier Installation and Setup Guide For WebSphere Application Server Version /12

2 COPYRIGHT Copyright 1998, 2012, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. The platform-specific hardware and software requirements included in this document were current when this document was published. However, because new platforms and operating system software versions might be certified after this document is published, review the certification matrix on the My Oracle Support Web site for the most up-to-date list of certified hardware platforms and operating system versions. The My Oracle Support Web site is available at the following URL: If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. This software or hardware and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services. Primavera Unifier Installation and Setup Guide for WebSphere

3 Table of Contents Introduction... 1 Primavera Unifier Installation Steps for First Time Install... 1 Upgrading Primavera Unifier Installation Steps... 2 Installation Pack Contents... 2 Cluster Support... 2 Customer Support Contact Information... 2 Where to Get Support... 2 Access to Oracle Support... 2 Chapter 1 Installing the Primavera Unifier Application... 3 Prerequisites... 3 Configuring the Application Server for WebSphere... 3 Installing the Primavera Unifier Application... 5 Chapter 2 Configuring the Database Server... 7 Prerequisites... 7 Configuring the Oracle Database Server... 7 Configuring the SQL Database Server... 7 Chapter 3 Installing AutoVue Server (Optional)... 8 Required Components... 8 Install AutoVue... 8 Enter IIS Web Server Port Number... 8 Latest Service Pack Install... 8 GUI Configuration File Copy... 9 Chapter 4 Configuring the Primavera Unifier Application Configuring the Primavera Unifier Application Troubleshooting tips Chapter 5 Example custom.properties File Configuration Information Miscellaneous (con t) Chapter 6 Installing the WebSphere Plug-in Installing the WebSphere Plug-in Chapter 7 Launching Primavera Unifier Starting Primavera Unifier for the First Time Administrator Account Startup Messages Hosting Company vs. Other Companies Setting up Primavera Unifier Chapter 8 Upgrading Primavera Unifier Primavera Unifier System Upgrade Steps Back up File Repository and Database Uninstall Current Version of Primavera Unifier Install New Version of Primavera Unifier Configure the Primavera Unifier Application Verify Primavera Unifier Installation Perform Data Migration Appendix A: HotFix Installation Primavera Unifier Installation and Setup Guide for WebSphere i

4 HotFix Steps Appendix B: Archiving Configuring Primavera Unifier for Project Archiving Archiving Projects Primavera Unifier Installation and Setup Guide for WebSphere ii

5 Introduction Primavera Unifier is a web-based application. The full functionality of the application can be accessed through a web browser. This guide describes how to: Set up the Primavera Unifier servers and third party services. The requirements include: Oracle 9i, 10g, 11g or Microsoft SQL 2000, 2005, or 2008 Database Server Primavera Unifier Application/Web Server AutoVue Server (Optional) Install and configure Primavera Unifier components This guide is intended for IT professionals who are installing and configuring the server environment for Primavera Unifier and who are supporting Primavera Unifier users. For the full list of system requirements and versions, see the Configuration Information document under Installation and Configuration Documentation in the Primavera Unifier 9.10 Online Documentation Library. Primavera Unifier Installation Steps for First Time Install These steps are provided as a reference for the installation and configuration process for a first time installation. It is recommended that you follow the steps in this order. Note: Configuration of the database server, Reports Server, and Schedule Server must be completed before configuring the Primavera Unifier Application. Step 1 Configure the application server, and then install the Unifier Application Step 2 Configure the Database Server Step 3 Install and configure the servers (database server, Schedule Server, Reports Server). This step must be completed before configuring the Unifier Application. Step 4 Install AutoVue Server (Optional) Step 5 Configure Unifier Application (copy custom.properties file into shared library) Step 6 Launch Unifier Step 7 WebSphere Plug-in Install Primavera Unifier Installation and Setup Guide for WebSphere 1

6 Upgrading Primavera Unifier Installation Steps See Chapter 8 Upgrading Primavera Unifier for details on performing an upgrade. Installation Pack Contents The Primavera Unifier product contains the following folders and files. unifier_ws.war Unifier Installation and Setup Guide Readme.txt Cluster Support See the WebSphere documentation for cluster setup information. Customer Support Contact Information Where to Get Support If you have a question about using Oracle products that you or your network administrator cannot resolve with information in the documentation or help, click support.oracle.com. This page provides the latest information on contacting Oracle Global Customer Support, knowledge articles, and the support renewals process. Access to Oracle Support Oracle customers have access to electronic support through My Oracle Support. For information, visit or visit if you are hearing impaired. Primavera Unifier Installation and Setup Guide for WebSphere 2

7 Chapter 1 Installing the Primavera Unifier Application This chapter describes how to: Configure the applications server before installation Install Primavera Unifier Prerequisites Primavera Unifier is certified with WebSphere 6.1 fix pack 35 and IBM JRE fix pack 35. If using MS SQL Server database, it must use WebSphere 6.1 fix pack 15 or above Red Hat Linux Enterprise 5.0 or above; be sure you have a browser (such as Firefox) on your Linux server WebSphere Plug-in Configuring the Application Server for WebSphere Before you begin It is assumed that you have installed the WebSphere Application Server to the point of applying fix packs for each of the nodes you have installed. To access the WebSphere Integrated Solutions Console (the deployment manager admin console) In a browser, type in Note: For standalone Application Server only: 1. mkdir /opt/ibm/websphere/appserver/optionallibraries/unifier 2. cp /file_repos/was_install/custom.properties /opt/ibm/websphere/appserver/optionallibraries/unifier Note: The path /file_repos/was_install/ is shown in this document as an example of a path, and that any path can be used on the server. Also, server and cluster names are also examples, and site-specific names may be used in your installation. To add a node to a cell 1. If you have created one deployment manager and a node on one VM (for example, vmlinqa2) and a standalone application server on another VM (for example, vm-linqa3). 2. Now, you want to link the two together, i.e., add the standalone application server into the cell (deployment manager). 3. At the Administration console for the deployment manager (for example, vm-linqa2), on the left side choose System Administration > Nodes > Add Node. 4. Click Managed Node. 5. Enter the Host name (for example, vm-linqa3). 6. Click OK. 7. Log out of the console and save the configuration. Primavera Unifier Installation and Setup Guide for WebSphere 3

8 To create a two-node cluster 1. On the left side of the Integrated Solutions Console, click Servers >Cluster. 2. Click New. 3. Name the cluster: unifier_cluster. Note that server and cluster names shown in this document are intended as examples only. Site-specific names may be used in your installation. 4. Click Next. 5. Create a cluster member and give the member a name (for example, Unifier_1). 6. Select the node and click Next. 7. Create additional cluster member and give the member a name (for example, Unifier_2). 8. Select the node and click Add member. 9. Choose default parameters. 10. Click Save. To set up the Application Server memory and system log size 1. For each cluster created, on the left side of the Integrated Solutions Console, click Servers > Application Server and click on the server link just created. 2. On the right column under Server Infrastructure, expand Java and Process Management > Process Definition > Java Virtual Machine Set Initial Heap Size (512) and Maximum Heap Size (1024). 3. Click OK. 4. Click Save. Note that if you have previously modified the memory size on server1 on other nodes, you should reset it to a smaller memory size, such as 128M minimum and 512M as maximum. This will prevent the default server1 from using too much memory. 5. Navigate to Server Infrastructure > Java and Process Management > Process Definition > Logging and Tracing > JVM Logs. 6. By default, the system.out and system.err are 1M. Change both to 20M. 7. Change the Maximum History files to 10 files. 8. Click OK. 9. Click Save. 10. Restart the server to have the size changes take effect. 11. After you shutdown the server, you can delete old logs as necessary. Note: The log files are located in <WAS_Install_DIR>/profiles/AppSrv01/logs. The default Unifier logs are written in that location. The SystemOut.log and the SystemErr.log are located in <WAS_Install_DIR>/profiles/AppSrv01/logs/qa2 and <WAS_Install_DIR>/profiles/AppSrv01/logs/qa3. To add virtual host 1. By default, server1 will be using port When you create the Unifier_1 and Unifier_2 server, the default port will be To determine which port Unifier_1and Unifier_2 use, go to Servers > Unifier_1 > Ports and check WC_defaulthost. Primavera Unifier Installation and Setup Guide for WebSphere 4

9 2. To allow users access port 9081, on the left side of the Integrated Solutions Console, click Environment > Virtual Hosts. 3. Click the default host. Click Host Alias. 4. Click New. Leave host name as * and add port Click OK, the click the Save link. 6. Restart the deployment manager/server to take effect. To uninstall the default application (if any) By default, the WebSphere application server comes with a default application. This application should be uninstalled, because the default application runs as a root application. Unifier requires root context as blank, and this application will create a conflict with Unifier. 1. To uninstall the default application, navigate to Applications > Enterprise Application and select default application. 2. Click Uninstall. 3. Click Save. Installing the Primavera Unifier Application To access the WebSphere Integrated Solutions Console (the deployment manager admin console) In a browser, type in To install the Unifier application 1. On the left side of the Integrated Solutions Console, click Applications > Install New Application. The Preparing for the application installation screen opens on the right. 2. Complete the screen: For Path to the new application, choose Local file system. Click the Browse button and browse to the application file name (unifier_ws.war). In the Contextroot field, enter "/". 3. Click Next. The Select installation options screen opens. (It may take a few moments to extract the file.) 4. Complete the screen: For Application name, enter Unifier. The name must be Unifier, with an uppercase letter U. Do not attempt to use a different Application name. Select Deploy Web services. 5. Click Next. The Map modules to servers window opens. 6. To map the modules, complete the screen: In the Clusters and Servers field at the top of the screen, select the modules you want to deploy unifier_cluster, and web server node if available. Select the second box where it says to install Unifier. Primavera Unifier Installation and Setup Guide for WebSphere 5

10 Next to the check box, verify the location where Unifier will be installed. Make sure you see unifier_cluster appear in the lower box. If you do not see unifier_cluster, the deployment will not be done properly. Make sure you deploy to cluster and web server. Click the Apply button 7. Click Next. The Map context roots for Web modules screen opens. 8. Click Next. The Summary screen opens. Review the summary information to verify the settings you entered. 9. Click Finish. The application will install. It may take a few minutes to complete. 10. When the installation is complete, an Application Unifier installed successfully message appears in the window. 11. Click the Save link. It may take a few moments to finish and populate to other nodes. On the left side of the Integrated Solutions Console, click Applications > Enterprise Applications. Unifier should appear on the list of Enterprise Solutions. The Application Status will appear as a red icon (not started). Primavera Unifier Installation and Setup Guide for WebSphere 6

11 Chapter 2 Configuring the Database Server This chapter describes how to configure the database server. Prerequisites This chapter assumes that one of the following database servers has already been installed, and that you have sufficient Administrator privileges and familiarity with the applications. Oracle 9i, 10g, 11g database server, or Microsoft SQL 2000, 2005, or 2008 database server Configuring the Oracle Database Server The following is an overview of the steps required to configure the Oracle database for use with Unifier. Refer to your Oracle documentation for more information and specific instructions. To configure the Oracle database for use with Unifier 1. Create an instance for the database. 2. Create a user account for the newly created database. 3. Use the default Oracle configuration, and give the new user connect, resource and create view permissions. Note: Be sure the new user account has permission to create a table space, or Unifier will not work. Configuring the SQL Database Server The following is an overview of the steps required to configure the SQL database for use with Unifier. Refer to your SQL documentation for more information and specific instructions. To configure the Microsoft SQL database for use with Unifier 1. Create a new database to be used with Unifier. 2. Create a user account for the newly created database. 3. Use the default SQL configuration. You need to assign the user as db_owner or Unifier will not work. Primavera Unifier Installation and Setup Guide for WebSphere 7

12 Chapter 3 Installing AutoVue Server (Optional) AutoVue is needed if you plan to use Primavera Unifier s markup feature, also referred to as redlining. When attaching documents to a business process form, you can add markups, such as text notes or graphical elements, to the document. These markups display on the document but do not alter it. Note: AutoVue works only in the Windows environment, and is not available for use in the Linux environment. This chapter includes: Install steps for AutoVue version Steps for AutoVue that need to be completed in the Primavera Unifier Configurator Install steps for latest Service Pack Steps to copy/paste GUI configuration files Required Components Microsoft Windows 2003 Enterprise Edition operating system AutoVue version Install AutoVue Choose the desired server and run the installation by selecting the AutoVue installation file. Follow installation instructions. Note: The IIS files will not be installed to the Inetpub directory where they need to be. A folder must be created in the C:\inetpub\wwwroot directory named jvue and the files from \<install directory>\jvue\html must be copied to that folder. Enter IIS Web Server Port Number When prompted, change the port number from 80 to 5099 (or whatever port number you decide to use). Note: This port number will be used in the custom.properties configuration file (Chapter 4 Configuring the Primavera Unifier Application). Latest Service Pack Install After the AutoVue install is complete, run the latest service pack file that has been confirmed to work with Primavera Unifier. At the end of the install, a pop-up window instructs you to copy the jvue.jar and jvue.cab files from the \<install directory>\jvue\bin directory to the C:\inetpub\wwwroot\jVue folder (created earlier). Primavera Unifier Installation and Setup Guide for WebSphere 8

13 After you replace the existing files with these client files, the Service Pack installation is complete. GUI Configuration File Copy To enable AutoVue Markup features to work within Unifier 1. Copy the three configuration files default.gui, defaultnomarkup.gui, and defaultview.gui from Unifier\apps\ROOT\jVue\bin\profile directory. 2. Paste configuration files to AutoVue s bin\profile directory. Primavera Unifier Installation and Setup Guide for WebSphere 9

14 Chapter 4 Configuring the Primavera Unifier Application Configuring Primavera Unifier consists of configuring the custom.properties file, creating a shared library, and copying the file into it. You can also create your own custom.properties file. See Chapter 5 Example custom.properties File for more information. The custom.properties file is used to define parameters such as database connection information, file repository location, and other variables. This file will overwrite the default properties file. This file must be copied to each machine in a cluster. This chapter describes how to: Define the custom.properties file Create folders Access the console Disable auto start Create the shared library for custom.properties and copy the file into it Set the referenced shared library for Unifier Overwrite the default Unifier logs location (optional; do this if you do not want to use the default logs location within WebSphere) Start Unifier and Quick test This chapter also contains troubleshooting tips. Configuring the Primavera Unifier Application To define the custom.properties file 1. Locate the custom.properties file on the Unifier installation file CD or download pack. 2. Open the file in an editor such as Notepad. 3. Using the information in the Configuration Information table as a guideline, define the configuration parameters, and save the file. To create folders 1. Create a unifier folder in the library Go to the WebSphere application server, and go to ${WAS_INSTALL_ROOT}/optionalLibraries create a directory called unifier 2. Copy the custom.properties file into the folder. Do not rename the file. 3. Manually, create a file folder called ${WAS_INSTALL_ROOT}/optionalLibraries/unifier_log4j. 4. Copy the sample log4j.properties file to the shared library folder. Do not rename the file. 5. Open the log4j.properties in the shared folder. 6. Change the default log location as desired. For example, do a global change./logs to /home/<username>/logs. Primavera Unifier Installation and Setup Guide for WebSphere 10

15 7. Verify that the file does not have CRLF line terminators. Type file unifier*/* if you see ASCII English text. If there are CRLF line terminators, use the dos2unix unifier*/* command to remove the CRLF line terminators. To access the Integrated Solutions Console (the deployment manager admin console) In a browser, type in To temporarily disable auto start 1. On the left side of the Integrated Solutions Console, click Applications > Enterprise Applications. 2. Click the Unifier link. 3. Temporarily disable auto start: Click the link Target Specific Application Status. Select the checkbox next to all available servers. Click the Disable Auto Start button. Click the Save link. Note: After configuring and testing the Unifier application, you can turn auto start back on. To create the shared library and copy custom.properties 1. On each cluster node, on the left side of the Integrated Solutions Console, click Environment > Shared Libraries. 2. For Scope, choose unifier_cluster. 3. Click the New button. Complete the screen: For Name, enter unifier_custom Set the Classpath as ${WAS_INSTALL_ROOT}/optionalLibraries/unifier 4. Click OK, then click the Save link. To set the referenced shared library for Unifier 1. On the left side of the Integrated Solutions Console, click Applications servers > Enterprise Application. 2. Click Unifier. 3. Click the Shared library references link. 4. Select the Unifier Web Application checkbox. 5. Click the Reference shared libraries button. 6. In the Available box, select unifier_custom, then click the >> button to move it to the Selected box. 7. Click OK. Primavera Unifier Installation and Setup Guide for WebSphere 11

16 8. Click OK, then click the Save link. To overwrite the default Unifier Logs location (optional) The default Unifier logs will be generated at ${WAS_INSTALL_HOME}/profiles/AppSrv01/logs. To change the default location, follow the steps below for each server in the cluster. 1. Create a Unifier_log4j shared library: On the left side of the Integrated Solutions Console, click Environment > Shared Libraries. Click the New button. Complete the screen: For Name, enter Unifier_log4j Set Classpath as ${WAS_INSTALL_ROOT}/optionalLibraries/unifier_log4j Click Save. Click OK, then click the Save link. 2. Create a log4j classloader for the server: Navigate to Servers > Application servers > websp03 > Java and Process Management. Click the Class loader link. Click New. For Class loader order, select Classes loaded with parent class loader first. Click OK, then click the Save link. This creates an entry (for example, Classloader_ ). Click on the link for the newly generated class loader. Click the Shared library reference link. Click Add. Choose Unifier_log4j. Click OK, then click the Save link. You must restart the server for the changes to take effect. To start Unifier and Quick test 1. On the left side of the Integrated Solutions Console, click Applications > Enterprise Applications. 2. Select the Unifier checkbox. 3. Click the Start button. The red icon will turn to a green arrow when the application is started. If this is the first time you start Unifier or if you have a blank database, be sure to start nodes sequentially the first time you start them, and be sure to let each node start completely before you attempt to start the next node. 4. Open an Internet Explorer browser and enter 5. Verify that Unifier login window opens. If Unifier does not start properly, you may need to open the SystemErr.log or SystemOut.log to find out the problem. 6. Once you have tested that Unifier starts, you can turn auto start back on. Click Applications > Enterprise Applications. Click the Unifier link. Primavera Unifier Installation and Setup Guide for WebSphere 12

17 Click the link Target Specific Application Status. Select the checkbox next to all available servers. Click the Enable Auto Start button. Click the Save link. Troubleshooting tips Starting the application If you attempt to start Unifier and the login window is blank, check that the custom.properties are defined correctly, especially skire.unifier.rooptpath and skire.classes.rootpath. Note that sometimes, WebSphere incorrectly evaluates the environment variable %user.install.root% and the %WAS_CELL% token, so you might have to replace the variable with the actual path (replace %user.install.root% and %WAS_CELL% with the actual path where WebSphere is installed). For example: skire.unifier.rootpath=/opt/ibm/websphere/appserver/profiles/appsrv01/installedapps/w ebsp04cell01/unifier.ear skire.classes.rootpath=/opt/ibm/websphere/appserver/profiles/appsrv01/installedapps/ websp04cell01/unifier.ear/unifier_ws.war /WEB-INF Note for the above skire.unifier.rooptpath and skire.classes.rootpath token replacement issues, you might receive an error such as webant.xml not found in the SystemOut.log or Unifier.log Also, you might have to apply these changes to all servers. If that is the case, change the above two properties based on the actual deployment location. If your database connection fails on login, check these definitions in the custom properties file: skire.datasource.driver, skire.datasource.username, and skire.datasource.password. If you change the custom.properties, be sure to make the same changes for all copies of the properties on the various server nodes. Issue connecting to the application server If SSL is enabled on your servers, the following steps might need to be performed to enable Primavera Unifier to receive business processes from Primavera udesigner. You can get the error com.ibm.jsse2.util.h no trusted certificate found when attempting to connect to the application server if the SSL certificate is not recognized by the server. 1. On the Left column of the Integrated Solutions Console, open Security. 2. Click on SSL certificate and key management. 3. In the Related Items column, select Key stores and certificates. 4. Select CellDefaultTrustStore. 5. Under Additional Properties in the right column, click Signer certificates. 6. When that page opens, click Retrieve from port. A Configuration page opens. 7. Enter the fully qualified Host name in the Host box (websp05.skire.com). Primavera Unifier Installation and Setup Guide for WebSphere 13

18 8. Enter 443 in the Port box. 9. Enter the Host name in the Alias box (websp05.skire.com). 10. Click Retrieve signer information to verify correct settings. 11. Click Apply. 12. Click Save. 13. Restart the cluster. 14. Restart HTTPD Primavera Unifier Installation and Setup Guide for WebSphere 14

19 Chapter 5 Example custom.properties File Depending on your requirement, you should create your own custom.properties file. The following is an example of a typical custom.properties file. ####################################################################### #### ## Required properties ####################################################################### #### #skire.appserver.type=websphere #specify the server type: either it can be staging or production skire.server.type=production # For skire.unifier.rootpath and skire.classes.rootpath properties: be careful, # sometimes, Websphere will not evaluate the environment variable %user.install.root% # token properly, you may have to replace with the real path yourself. i.e. replace # %user.install.root% with real path where websphere application is installed. # Otherwise the application will not start properly. For example, after you replace with your real path: #skire.unifier.rootpath=/opt/ibm/websphere/appserver/profiles/appsrv01/ installedapps/websp04cell01/unifier.ear #skire.classes.rootpath=/opt/ibm/websphere/appserver/profiles/appsrv01/ installedapps/websp04cell01/unifier.ear/unifier_ws.war/web-inf # Use the following two properties (uncomment the below two properties) or replace environment token with real path #skire.unifier.rootpath=%user.install.root%/installedapps/%was_cell%/un ifier.ear #skire.classes.rootpath=%user.install.root%/installedapps/%was_cell%/un ifier.ear/unifier_ws.war/web-inf ##default port is it should be based upon the server port you are using skire.server.local.port=9081 ##For Oracle use: ##skire.database.type=oracle ##skire.datasource.server=jdbc:oracle:thin:@localhost:1521:orcl ##skire.datasource.driver=oracle.jdbc.driver.oracledriver ##For SQL Server ##skire.database.type=mssql ##skire.datasource.server=jdbc:sqlserver://myserver\:1433;databasename= unifer;selectmethod=cursor; ##skire.datasource.driver=com.microsoft.sqlserver.jdbc.sqlserverdriver ## Primavera Unifier Installation and Setup Guide for WebSphere 15

20 skire.database.type=mssql skire.datasource.server=jdbc:sqlserver://myserver\:1433;databasename=un ifer;selectmethod=cursor; skire.datasource.driver=com.microsoft.sqlserver.jdbc.sqlserverdriver skire.datasource.username=myusername skire.datasource.password=mypassword skire.datasource.minconnections=2 skire.datasource.maxconnections=40 # Disable job scheduler. Note in a cluster environment, only one node in the cluster should turns on the scheduler (with # skire.job.disabled=false). The rest of the nodes should be job disabled (i.e. skire.job.disabled=false) skire.job.disabled=true # file repository properties skire.file.rootpath=/file_repos/dev/root skire.file.index.rootpath=/file_repos/dev/index skire.file.webservicedirectory=/file_repos/dev/webservices skire.file.dashboard.rootpath=/file_repos/dev/dashboard skire.file.temppath=/file_repos/dev/tmp #configure outgoing mail server IP skire.mailserver= #configure incoming mail server IP skire.action. .server= skire.action. .account=engmail1@smailtest.com skire.action. .password=!q@w#e$r #configure notification skire.notify.login.url= skire.notify.contact.string=for Skire technical assistance contact <a href="mailto:support@skire.com">support@skire.com</a> or call GO SKIRE ( ). skire. .from.address=unifier_notification@skire.com skire. .from.name=unifier skire. .notify.to=abc@skire.com #specify the help link put the web server name +/help for example if linqa1 is the webserver #skire.server.help.rootpath= skire.server.help.rootpath= ####################################################################### #### ## Optional properties ####################################################################### #### #The max number of concurrent users that can log into the system skire.max.login.user=400 # Enable SSO login # this is the header that contains the valid Unifier User ID Primavera Unifier Installation and Setup Guide for WebSphere 16

21 skire.sso.header=pf-auth-subject # specify SSO logoff url skire.sso.logout=https\://test.skire.com/sso_logoff.asp leave this as sm for SiteMinder skire.sso.provider=sm #Internal in minutes, used by the Unifier Schedule Server for notification tasks. The suggested interval is 15 minutes. A very small interval may degrade performance. skire.server.scheduler.interval=15 # specify the archive directories skire.archive.rootpath=/file_repos/dev/archive/root skire.archive.temppath=/file_repos/dev/archive/tmp # specify the xref server skire.xref.service.port=8123 skire.xref.service.host=localhost #specify the time out (in seconds) skire.login.timeout=1800 # Allow file viewing via VueServlet if VueServlet is used file.viewer.enabled=yes # address for the support group skire. .support.address=support@skire.com # address where Unifier sends licensing notifications, for example, if number of users is exceeded skire.license.notify.to=abc@skire.com # Set VueServlet's ip and port number VueServlet.JVueServer= :5099 Primavera Unifier Installation and Setup Guide for WebSphere 17

22 Configuration Information Type Parameter Description Format and Example Root Root Root paths for Unifier For Unifier: skire.unifier.rootpath=%user.install.root%/installedapps/%was_c ELL%/Unifier.ear skire.classes.rootpath=%user.install.root%/installedapps/%was_ CELL%/Unifier.ear/unifier_ws.war/WEB-INF Server Server Local Port Port used by Unifier to handle http requests. It should be based upon the server port used. This value must match the virtual host port for the server. File Repositories File Directory Index Directory Enter the path where uploaded or attached files are stored. This repository is for storing documents within the Document Manager, such as drawings, plans, Word documents, etc. These files will be available for viewing or attaching to business process forms within Unifier. It also stores imported schedule files. Note: These files must be on a shared drive that is accessible by other server machines that are operating in a clustering environment. This folder is for index files used in Document Manager search function. Note: Uncomment these properties. For the skire.unifier.rootpath and skire.classes.rootpath properties: use care; sometimes WebSphere will not evaluate the environment variable %user.install.root% # token properly, you may have to replace the variable with the real path. Example: Replace # %user.install.root% with the actual full path to where WebSphere application is installed. Otherwise, the application will not start properly. skire.server.local.port=<port> Example: skire.server.local.port=9081 skire.file.rootpath=<full path> Example: skire.file.rootpath=/file_repos/root skire.file.index.rootpath=<full path> Example: skire.file.index.rootpath=/file_repos/index Primavera Unifier Installation and Setup Guide for WebSphere 18

23 Type Parameter Description Format and Example File Repositories Archive Directory For project archiving capability. skire.archive.rootpath=<full path> Example: skire.archive.rootpath=/file_repos/archive/root (cont.) Archive Temp Directory For temporary archived files. skire.archive.temppath=<full path> Web Service Audit Directory Dashboard Data Directory This folder stores files for Web Services calls. This folder stores the.swf and XML files used with custom dashboards. Example: skire.archive.temppath=/file_repos/archive/tmp skire.file.webservicedirectory=<full path> Example: skire.file.webservicedirectory=/file_repos/dev/webservices skire.file.dashboard.rootpath=<full path> Example: skire.file.dashboard.rootpath=/file_repos/dashboard Temp Directory For temporary files. skire.file.temppath=/file_repos/dev/tmp Example: skire.file.temppath=<full path> Database Database Type Specify which database type is in use, Oracle or SQL. For Oracle: skire.database.type=oracle Database/datasource Information Specify database driver (the JDBC driver to connect to the database, data source information (JDBC connection stream), and database name. For SQL: skire.database.type=mssql For Oracle: Example:skire.datasource.server=<server> Example: skire.datasource.driver=<driver> skire.datasource.driver=oracle.jdbc.driver.oracledriver For SQL: Example: skire.datasource.server=<server> Example: skire.datasource.driver=<driver> User Name User Password Enter the database login user account name (created in Oracle) to be used by Unifier. The database login user account needs to have sufficient permissions to create tables in order for Unifier to work correctly. Enter the database login user account password to be used by Unifier. skire.datasource.server=jdbc:sqlserver://myserver\:1433;database Name=unifer;selectMethod=cursor; skire.datasource.driver=com.microsoft.sqlserver.jdbc.sqlserverd river skire.datasource.username=myusername skire.datasource.password=mypassword Primavera Unifier Installation and Setup Guide for WebSphere 19

24 Type Parameter Description Format and Example Max. Connections Min. Connections The setting that defines the maximum connections to the database. The maximum is 400; the recommended maximum is 40 to 100. The setting that defines the minimum connections that must be connected to the database. skire.datasource.maxconnections=n Example: skire.datasource.maxconnections=40 skire.datasource.minconnections=n Example: skire.datasource.minconnections=2 Outgoing mail server Enter the IP address for the SMTP Server. skire.mailserver=<ip address> System Notification E- Mail Address Sender Prefix This is the ID that displays as the Sender s address for all s generated by the Unifier system. Provide the prefix that will be used in the Sender s name whenever is generated from a user from within Unifier. skire. .from.address=<address> Example: skire. .from.address=unifier_notification@company.com skire. .from.name=<sender> Example: skire. .from.name=unifier (cont.) Login URL The URL included for all users logged into the system. skire.notify.login.url= Support Contact Information The message text included in all Support notifications. Note: you can include hyperlink html tag to make the link a clickable mailto hyperlink in the notifications. Example: skire.notify.login.url= skire.notify.contact.string=<message> Example: skire.notify.contact.string=for technical assistance contact <a href="mailto:support@company.com">support@company.com</a > or call Support Address The address for the Support group. skire. .support.address=<address> System Error Notification Address License Notification E- mail Address Incoming mail server Inbound Account The address where the Unifier Application sends a notification if it loses connection to the database while the system is running. The address where Unifier sends licensing notifications, for example, if number of users is exceeded. Enter the server that can receive (for example, if a user takes action via on a business process). This can be the server name or IP address. Create an account on the inbound server; this is where inbound s will be sent. Example: skire. .support.address=<support@company.com> skire. .notify.to=<address> Example: skire. .notify.to=itstaff@company.com skire.license.notify.to=<address> Example: skire.license.notify.to=support@company.com skire.action. .server=<ip address> skire.action. .account=<address> Example: skire.action. .account=inbound@company.com Primavera Unifier Installation and Setup Guide for WebSphere 20

25 Type Parameter Description Format and Example Markup Server Inbound Password Enable Markup Server Markup Server Host Name and Port This is the password that corresponds to the inbound account. This password is used when is retrieved. This setting controls the markup sever, which allows file viewing and markup capabilities using VueServlet. To enable, set to Yes; if you are not using the markup feature, set to No. Enter the host name (or IP address) and port number of the markup server. Report Server Report Server Host Name Enter the name of the computer configured as the Unifier Reports Server. Report Server External Port Report Server Internal Port Virtual Directory ODBC Datasource Name Enter the port number used by Unifier Application Server to communicate to the Reports Server externally. For example, 80 or 443. This may differ, depending upon if the server is operating on a secure channel. Enter the port number used by Unifier Application Server to communicate to the Reports Server internally. For example, 80 or This may differ, depending upon if the server is operating on a secure channel. Enter the name of the virtual directory you created in IIS during setup of the Reports Server. Enter the ODBC Data Source Name you added during Reports Server setup. Miscellaneous Login Session Timeout Login Session Timeout is used to control the amount of time a user can be idle before having to log back into Unifier. The unit is seconds. For security reasons, the recommended timeout setting is between 30 minutes and 4 hours. Late Notice Interval Interval, in minutes, used by the Unifier Schedule Server for notification tasks. The suggested interval is 15 minutes. A very small interval may degrade performance. skire.action. .password=mypassword file.viewer.enabled=yes or file.viewer.enabled=no VueServlet.JVueServer=<hostname or IP addresst>:<port> Example: VueServlet.JVueServer= :5099 skire.server.report.host=computername skire.server.report.port=<port> Example: skire.server.report.port=80 skire.server.report.internal.port=<port> Example: skire.server.report.internal.port=80 skire.server.report.context=<directory> Example: skire.server.report.context=unifier skire.server.report.datasource=<datasource> Example: skire.server.report.datasource=datasourcename skire.login.timeout=<# seconds> Example: skire.login.timeout=1800 skire.server.scheduler.interval=<no.> Example: skire.server.scheduler.interval=15 Primavera Unifier Installation and Setup Guide for WebSphere 21

26 Type Parameter Description Format and Example Miscellaneous (con t) Max. Concurrent Logins Server Type Disable Job Scheduler Help Link The setting for the maximum number of concurrent users that can log into the system. The recommended setting is 400. The setting that defines the mode Unifier server is running. -Set Server Type to Production if this Unifier installation is acting as the Production environment to host the Business processes designed with udesigner. -Set Server Type to Staging if this Unifier installation is acting as the Staging server for testing the Business processes designed with udesigner. Note: If working in a clustered environment, then all servers in a cluster should be set with the same Server Type value. Set to True to disable, or False to not disable. When not disabled, then any background process (e.g., project archiving, update projects, scheduled UDRs and cash flow refresh) will run on this Unifier application server. In a cluster environment, only one of the Unifier application servers can be dedicated to running background jobs by using this option. (That is, disable this on all but one machine in a cluster.) Set to specify the help link containing the web server name. skire.max.login.user=<no.> Example: skire.max.login.user=400 skire.server.type=production or skire.server.type=staging skire.job.disabled=false (for the one node in which the job scheduler is to run) skire.job.disabled=true (all other nodes in the cluster) skire.server.help.rootpath= Example: skire.server.help.rootpath= Primavera Unifier Installation and Setup Guide for WebSphere 22

27 Chapter 6 Installing the WebSphere Plug-in This chapter describes how to: Install the WebSphere Plug-in Installing the WebSphere Plug-in To download the WebSphere Plug-in 1. Navigate to this webpage and login: %3A21%3A R&S_TACT=&S_CMP= 2. The download you want to use is: trial_plugins_7000_linux.ia32.tar.gz Linux servers came with Apache Web Server 2.2. There is no need to install Apache Web Server. After you install Web Server plug in, it will be easier for WebSphere to generate application specified web server configuration script. To install the Web Server Plug-in on the Web Server: 1. Unzip the file to this directory /file_repos/was_install/install_plugin Open a terminal window on the server, cd (change directory) to /file_repos/was_install/install_plugin7000/plugin, and run./install. Web server plug-ins for WebSphere Application Server Version 7.0 window opens 3. Uncheck Installation roadmap and click Next. 4. Accept non-ibm terms, and click Next. 5. At the System Prerequisites Check a dialog is presented informing you (general user) that your operating system prerequisites failed. Ignore this and select Next. 6. Choose Apache Web Server 2.2 as the target web server, and click Next. 7. Select the installation scenario of WebSphere Application Server machine (local) if on the same server as Application Server and click Next. 8. Take the default Product installation location: /opt/ibm/websphere/plugins and click Next. 9. Take the default Location of WebSphere Application Server: /opt/ibm/websphere/appserver and click Next. 10. Select WebSphere Application Server profile to configure: Dmgr01, and click Next. 11. Modify the default web server configuration files from /opt/ibm/httpdserver/conf/httpd.conf to: /etc/httpd/conf/httpd.conf and click Next. If you uninstall this later you will have to manually edit the bottom lines of this file for the httpd daemon to start. 12. Take the default Web server port, and click Next. 13. Specify a unique Web server definition name like websp-unifier, and click Next. 14. Take default for the plug-in configuration file, and click Next. 15. Choose everything else as default. Finish installation. Primavera Unifier Installation and Setup Guide for WebSphere 23

28 16. An Internet Browser window for Web server plug-in installation roadmap will open. Close it. 17. Inside /opt/ibm/websphere/plugins/bin, is a file named configurewebsp-unifier.sh 18. Move the file to {WAS_INSTALL}/bin directory. 19. Inside /opt/ibm/websphere/plugins/config/websp-unifier folder you will find the default configuration files (such as plugin-cfg.xml) for the designated app server. They may be replaced if we install more applications on the Application Server. 20. Restart the Web Server: On a terminal, login in as root: type /sbin/service httpd restart. 21. To test if the web server is working: go to a browser: If the installation was successful, you should see a default Apache page. To configure for the Application Server : 1. In a browser, type in to launch the admin console 2. Go to left hand side expand Guided Activities > Routing requests through a Web Server to application server. Note: After Installing Web server plug-in (the above steps), follow the steps from Run the Web Server Configuration script > Distributed onward. 3. Follow the instructions one by one. Note one of the steps is to copy the configurewebspunifier.sh from web server (websp01) to deployment manager server (websp02) under <WAS_Install_DIR>/bin. Make sure you grant at the read/write access to the Run Account for the file. Also, su to that user account to run this file. It is a good practice to run all scripts on WebSphere App Server using the Run Account to avoid permission problems. 4. Restart deployment manager, all nodes and app servers. 5. Go back to WebSphere Admin console, you will see Servers > Web Servers > websp-unifier show up in the App Server console. 6. Start Unifier application. Note: Every time you install a new application, you need to generate the plug-in configuration files which will be located in <WAS_Install_DIR>/profiles/Dmgr01/config/cells/websp01Cell01/nodes/vmlinwebsp01.skire.com-node/servers/webserver-websp01>. Manually move from Deployment Manager machine to the web server machine. Follow the instructions in the above steps However, if you just update the war file or modify the deployment options, you do not have to move web server config files. 7. To test if Web server is running properly, go to a browser, type in server host name>. It should bring you to the Primavera Unifier login in page. Primavera Unifier Installation and Setup Guide for WebSphere 24

29 Chapter 7 Launching Primavera Unifier This chapter describes how to: Launch Primavera Unifier for the first time If this is the first time you are launching Primavera Unifier, make sure you first read the First Time User Setup Guide available from the login screen. The guide describes configuring Internet Explorer for use with Primavera Unifier. You can find a link to the First Time User Setup Guide on the Primavera Unifier login screen. Starting Primavera Unifier for the First Time In Internet Explorer, navigate to the URL that launches the Primavera Unifier application locally from a machine that has Microsoft Internet Explorer installed. At the Login window, log into Primavera Unifier with the default Administrator username (Administrator) and password (Administrator). Administrator Account The Administrator account is automatically set up the first time the system is installed. We highly recommend that you change the password immediately (see the following section, Setting up Primavera Unifier). The Administrator account is the only account with permissions automatically set for all features. The Administrator cannot be a member of any project, even if created in the Hosting Company. Startup Messages Once the Unifier Login screen displays, you will see a series of startup messages as Unifier sets up the Host Company, creates the Administrator user, and performs other startup processes. Note: These messages appear anytime you start or restart the Unifier Service. Hosting Company vs. Other Companies The Hosting Company users are the only users who can create other companies and manage site level functionalities. To start using Primavera Unifier features, set up a Company record first. Follow the process below to begin Unifier configuration. Refer to the Primavera Unifier Administration Guide for information on the administration of companies, users, and projects. Primavera Unifier Installation and Setup Guide for WebSphere 25