REMINDER
Check in on the
COLLABORATE mobile app
Case Study: Migration from CM13 to CM14
Prepared by:
Thomas Everritt
Vice President, PM Systems
Hill International, Inc.
Technology Differences
How to Migrate
Lessons Learned
Session ID#: 15437
■ Founded in 1976
■ Over 4,000 Employees in over 100 offices worldwide
■ Hill is the largest independent U.S. construction management (for fee only) according to Engineering News-Record (June 13, 2013)
■ Hill has managed more than 10,000 projects valued at over $500 billion
■ Hill has resolved more than 50,000 claims valued over $100 billion
Thomas Everritt Vice President, PM Systems
■ Information Technology Management – 13 years
■ Construction Industry – 8 years
■ Primavera Contract Management – 4 years
■ CM14 – 2 years
■ CM Environment
▪ Two CM14
▪ Four CM13.1
▪ Over 1000 users, 20 project groups, and 100 projects
Where to Get Resources
■ Important Information about Primavera Contract Management Releases 13.1 and 14 (1315652.1)
■ What's New in Contract Management 14 - Release Content Document (1363117.1)
■ Video Master Note for Contract Management 14 Installation, Upgrade, and Configuration (1390515.1)
■ Contract Management 14.0, Business Intelligence Publisher Edition, http://docs.oracle.com/cd/E23619_01
■ Contract Management / WebLogic Server Instance Performance Tuning Guide (1504374.1)
Licensing
■ Check with your Oracle Representative
■ My Information about BI Publisher
▪ Read access is included in CM14 license for existing reports
▪ To create or edit reports an edit license is required per named
user. The price is very reasonable
▪ If you connect to any other application outside of CM14, you
must purchase full licensing
Why Migrate from CM13 to CM14?
■ Red Stack
■ Technology
▪ x64 Windows support means more Java memory
— x86 is limited to 1536 MB
▪ Jrockit means more speed and functionality than Sun JDK
▪ Ability to cluster using Weblogic (requires additional licensing)
▪ ActiveX removed
■ Letters work better in BI Publisher than Microsoft Word
■ User Productivity Kit
■ Support
▪ CM13.0 is no longer supported
▪ CM13.1 is only supported through June 2015
Why Stick with CM14?
■ CM14 is close enough without the complexity of Unifier
■ We will need to support
▪ Current projects for the next 4 to 5 years
▪ Archived projects for over 10 years
■ Support
■ CM13.1 Premier Support ends June 2015 and Sustaining Support is not
available.
■ CM14 Premier Support ends August 2016 and Sustaining Support is
Indefinite
Oracle Red Stack
■ Database
■ Application Server: Weblogic
■ Application: PCM, EPPM
■ Reporting: BI Publisher
Technology Differences
■ Database: Oracle and
Microsoft SQL
■ Application Server: Weblogic
and JBoss
■ Repository: WebCenter
Content (Content Server,
UCM, ECM), SharePoint,
Jackrabbit
■ Letters: Microsoft Word
■ Reporting: Infomaker
■ Database: Oracle and
Microsoft SQL
■ Application Server: Weblogic
■ Repository: WebCenter
Content, SharePoint
■ Letters: BI Publisher
■ Reporting: BI Publisher
CM13 CM14
Case Study Technology
■ OS: Windows 2008 x86
■ Database: Microsoft SQL
■ Application Server: JBoss
■ Repository: Jackrabbit
■ Letters: Microsoft Word
■ Reporting: Infomaker
■ OS: Windows 2008 R2
■ Database: Microsoft SQL
■ Application Server: Weblogic
■ Repository: SharePoint
■ Letters: BI Publisher
■ Reporting: BI Publisher
CM13 CM14
Our Situation
■ Dates
▪ CM14 released August 2011
▪ Started migration project in January 2012
▪ Went live in July 2012
■ Knowledge
▪ Good knowledge of CM13, Microsoft SQL, and SharePoint
▪ No experience with Weblogic or BI Publisher
▪ Consultant was available to help with configuration
▪ There was almost no CM14 - BI Publisher expertise in the
market
■ 300 users, 60 projects, and 14 project groups
▪ We had to determine a method to connect BI Publisher to
multiple project groups
General Implementation Methodology
■ Create new development environment
▪ New CM14 and BI Publisher on separate Weblogic servers
▪ New Microsoft SQL instance
▪ Existing SharePoint 2010 development environment
■ Testing
■ New production environment using copies of databases and attachments from the existing system
■ More testing
■ Refreshed databases and attachments
■ Cutover
How Did the Migration Go?
■ Testing revealed
▪ Logon problem
▪ Versioning
— SharePoint or WebCenter Content is needed for versioning
— You will most likely lose versioned documents
▪ BI Publisher is different but it can be mastered
▪ Every report is not the same as it was in CM13
■ Testing did not reveal
▪ Every report is not the same as it was in CM13
▪ Unique interface problems we found as early adopters
▪ Tuning problems
Test Plan Example - User
■ Login and change password
■ Run reports and forms
■ Read, upload, and delete attachments
■ Create, update, generate, and delete document
■ Spellcheck document
■ Version document (if applicable)
■ E-mail document
■ Check workspace and folder views
■ Check layouts and download current layout
■ Test contract modules
■ Test Letters module
■ Change groups (if applicable)
Test Plan Example - Administrator
■ Add reports and forms location
■ Import reports and forms
■ Set attachment storage location if using a file server
■ Add user
■ Set permissions
■ Create project
■ Check dictionaries, custom fields, custom text
CM14 Installation Steps
■ Install Jrockit Java Development Kit (set JAVA_HOME)
■ Install databases with dbsetup.bat
■ Install Weblogic software and configure domain
■ Install CM14
■ Create CM14 JDBC data sources in Weblogic
■ Other Software
▪ Repository
▪ BI Publisher
■ Perform performance tuning
■ Configure CM14 to run as a service
Steps to Migrate CM13 into the New CM14 Environment
■ Remove the CM14 databases created during installation
■ Backup, copy, and restore CM13 databases to the test Microsoft SQL instance used during installation
■ Upgrade databases to CM14 with dbsetup.bat
■ Create CM14 JDBC data sources in Weblogic
■ Update configuration information using admincm.cmd
■ Import forms and reports
■ If using a file share for attachments the following may be required
▪ Copy files to new location
▪ Run script to update file path
Odds and Ends
■ The upgrade of the EXPADMIN database to CM14 changes all alpha characters in passwords to uppercase
■ The Pay Requisitions module no longer prints a complete AIA G702 and G703 report. You can print the data on a sheet of paper purchased from AIA.
■ Send to Excel is now Download Current Layout
■ When you add a file server path, the first backslash is dropped. You must enter \\\madrid\app\project1 to successfully enter \\madrid\app\project1
Repository
■ The Jackrabbit repository is no longer an option
■ Must use SharePoint or WebCenter Content for versioning
■ There is no migration path from Jackrabbit to SharePoint
■ A migration path is available for Jackrabbit to Oracle Content Server. Please contact Oracle Support for assistance with this migration
■ SharePoint lessons learned
▪ The setup of SharePoint as a repository is not that difficult if you
have SharePoint experience
▪ Set SharePoint authentication mode to Single User
▪ The SharePoint default list view threshold (5,000) will quickly
cause versioning to fail and there is no good
▪ Increase the SharePoint/IIS Idle timeout
BI Publisher
■ According to Primavera documentation, there is no migration path from Infomaker to BI Publisher reports
■ It is strongly recommended to run BI Publisher on a dedicated server rather than on the same server with CM14
■ BI Publisher reports written in the Web Application will not produce line breaks on multiple lines of text in a data element. You must use a report in RTF format
How to Setup Reports for Multiple Project Groups
■ Setup new Data Source in the Web Application Administration
■ Copy the US SQL report folder and rename it (data source name)
■ Use Web Application to change every Data Model and Report
▪ Connect Data Model to Data Source
▪ Connect Report to Data Model
or
■ Use text editor like NotePad++ or Developer’s Notepad to search
and replace all occurrences in the new report folder
▪ xdo to connect Report to Data Model
— <dataModel url="/US Sql/Reports/BUL/DM_R_BUL_01.xdm"/> change to new
folder location
▪ xdm to connect Data Model to Data Source
— defaultDataSourceRef="US_SQL" and <sql dataSourceRef="US_SQL">
change to new data source
Database Connection
■ Name
▪ Name shown in CM14 change group
▪ Appended to jdbc/ in JNDIName
▪ JNDIName MUST match Weblogic
data source JNDI name.
■ Database Name (SID)
▪ This name is the DBName and must
match the name in the database.
▪ The JDBC connection will work but BI
Publisher reports will not work
correctly.
Database Driver Transaction Options
■ Single Group Database
▪ EXPADMIN
— Clear Supports Global Transactions
▪ Project Group Database
— Select Supports Global Transactions
— Select One-Phase Commit
■ Multiple Group Databases
▪ EXPADMIN and Project Group Databases
— Select Supports Global Transactions
— Select Emulate Two-Phase Commit
WebLogic Tuning
■ There may be excessive communications overhead with JDBC Unicode String Parameters using Microsoft SQL. To disable, enter the following string in Services Data Sources <Data Source Name> Connection Pool Properties
▪ sendStringParametersAsUnicode=false
■ It is recommended to set the minimum connection count for each JDBC data source to half the number of expected concurrent users.
■ It is also recommended to set the maximum connection count to twice the amount of expected concurrent users.
■ The WebLogic transaction timeout is 30 seconds by default, which may not be enough time for certain Contract Management tasks to run. Set Services JTA Timeout Seconds to a higher number e.g. 300.
Recording Letters
■ Click add document icon
■ Complete fields, select template, and click Save and Create Letter
■ Click the Check Out icon
■ Save the RTF document to your computer for editing.
■ Click the Check In icon
■ Browse to the edited RTF document on your computer and click OK
Final Thoughts
■ I would do it again
▪ The technology is stable
▪ Documentation and support are good
■ Learn the technology in a development environment
■ Develop a thorough testing plan
■ Consider using a consultant if you do not have Weblogic experience
■ Learning BI Publisher is extremely important