Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Table of Contents
EPM Live 2013 - Installation Guide ............................................................................................................. 4
Installation Guide Disclaimer ........................................................................................................................................ 5
Introduction to EPM Live 2013 - Installation Guide............................................................................................. 6
Pre-Installation.................................................................................................................................................... 7
Pre-Installation Setup ...................................................................................................................................................... 8
Required Information Prior to Installation............................................................................................................. 12
Client Desktop Setup (Optional)................................................................................................................................ 15
Page 4
Page 5
Page 6
Pre-Installation
Page 7
Pre-Installation Setup
SQL Server 2012
SQL Server 2012 must be installed and configured for use by SharePoint. During the SharePoint
installation, do NOT install using SQL Server Express. If SQL Server Express is used for SharePoint, the
EPM Live installation will not be able to take place and SharePoint will need to be re-installed.
SP1 is required for SQL Server 2012.
SQL Server 2012 Reporting Services is required for use with EPM Live.
Service Packs
EPM Live recommends that Service Pack 1 be installed.
Page 8
March and April CUs are the minimum requirement. Note: This patch level is required for Cloud
configuration installs.
Current EPM Live Cloud version:
15.0.4505.1002
April 2013 CU
SharePoint Foundation 2013
Note: If the client domain contains commas, there is an issue that has been fully resolved with the
November 2014 CU.
Page 9
Load Balancer
If using Project Publisher, must set the "persistence" setting in your Load Balancer to "Source IP."
Internet Connectivity
Confirm Internet connectivity from the SharePoint Farm server running Central Admin. Internet access
without a proxy will be needed to properly authenticate the EPM Live key. If Internet access is not
available, please provide the farm GUID.
Internet is required for installation of applications. There are no other alternatives at this time. If a
proxy server that does not require authentication is used, please refer to the following article to create a
Page 10
configuration file for the WorkEngine timer service so that the service can access the internet to
download application content.
Article: https://epmlivesupport.desk.com/customer/portal/articles/841857
Page 11
SharePoint URL
This is the URL of the site that will be created using EPM Live. EPM Live does not recommend hosting
this site at the root of a web application.
For example, http://epm.epmlive.com/sites/epmlive
API URL
There will be a separate IIS site created for EPMLive API. This site only needs to be accessible to the end
users if a third party integration is being used. The IIS site will be created during installation.
For example: http://epmapi.epmlive.com
Page 12
SSL Certificates
If SSL is needed for the above URLs, please ensure to have the certificate imported into IIS and added to
the IIS site accordingly in the binding settings within IIS manager. This must be done on all WFE servers
as well as the APP server that is running the WorkEngine Timer service. The entire SSL certificate chain
must also be added into SharePoint central admin under the Manage Trusts page. This means that if
you have a root certificate, intermediate certificate, etc. that they must all be uploaded into the Manage
Trusts page separately as per the example below.
Note: This also includes environments that are using SSL offload.
Page 13
Farm GUID
This step is only necessary if you do not have Internet Access available on the application box that runs
SharePoint Central Administration. This must be provided for each SharePoint farm that will have EPM
Live installed.
Note: The farm GUID can be found by either of the following:
Using Powershell. Powershell: $farm = Get-SPFarm $farm.Id
Once EPM Live is installed, the Feature Keys page (located in Central Admin) lists the Farm GUID.
Hardware ID
There is an optional feature called Designer Forms. If planning to use Designer Forms in any EPM Live
Lists, you will need to activate the feature with an activation key. EPM Live will provide a unique
activation key based your server Hardware ID.
To get your Hardware ID, run the following executable file on EACH Web Front End Server:
http://app.ecwid.com/download/1244062/aaf44c4bc212a5bc352ce6ba79e827cc/HIDGenerator.exe
Contact your EPM Live Installation Specialist and provide them with your Hardware ID(s). They will then
provide you with the necessary Activation Keys. Please note, it will take approximately 2 business days
for the activation key(s).
After the Designer Forms feature has been activated, the Site Feature must be activated. Then, Designer
Forms can be created from scratch in any EPM Live List. Also, some pre-created Designer Forms may be
available in the App Marketplace.
License Keys
Locate the email with license keys for the environment.
Page 14
Active-X Controls
Most Active X controls have been removed; however, one admin page and one end user feature will
require the installation of Active X components. If your organization will be using the Portfolio Cost
Views feature, each admin and end user who will configure or use that feature needs to download the
v5.5 Active X control.
Silverlight 4.0
Required for some of the EPM Live charts. Alternatively, there is an html chart web part that may be
created instead of any of the Silverlight chart web parts.
Any administrator who will be configuring the use of EPM Live Designer Forms (SP Forms Designer)
must have Silverlight installed.
Page 15
If you are using Project 2007, you will be required to use a custom macro to publish to
SharePoint.
Trusted Sites
EPM Live recommends that the new Web Application URL be entered in the Trusted Sites for all end
users to avoid any issues. \
Page 16
Page 17
Page 18
The Custom Setup page will allow you to change the installation path if needed. If you would prefer to
change the path or drive that EPM Live installs to, click the Change button. Otherwise, click the Next
button.
Note: You will need to do this for EACH feature that is being installed.
Page 19
1. Enter in the Username and Password of the Application Pool account. This account will be
used to install the EPM Live Timer and Queue service. These are Windows Services, so the
account will need to be a local administrator on the Application Server. Note: The username
must be in the format of domain\username.
2. Click Install. The wizard will process the installation for a few moments.
3. The wizard will finish installing the services. If there are any errors, troubleshoot them as
needed. If there are multiple servers in the farm, the installer may error stating that the solutions
did not deploy in a timely manner. Disregard these messages. Click Finish when it is done.
Page 20
Each WFE configure the Loopback. Refer to the following article, in which method one is the
recommended method: http://support.microsoft.com/kb/896861.
Each WFE The host file needs to point the URL back to its own loopback IP address. This
prevents a double-hop issue.
Page 21
Page 22
Verify Solutions
Installing EPM Live creates a number of new solution files in SharePoint. Make sure these solutions
installed properly, and were deployed to the correct Web Application. In Central Administration, click
the Manage Farm Solutions link under the Farm Management heading of System Settings. Make
sure that all solutions listed in the previous step have a status of Deployed. If they are not globally
deployed, ensure that they have been deployed to the web application that EPM Live is being installed
on only with the exception of the "workenginecore.wsp" solution file. This solution is deployed to the
central administration web application as well.
Note: If they are not globally deployed, ensure that they have deployed to the EPM Live Web
Application.
1.
2.
3.
4.
Page 23
5. Click the Create Database button to create the EPM Live Database.
Page 24
Page 25
Web.config Modifications
Make the Following Changes to your Web.config
There are some minor changes that need be made in the web.config.
NOTE: Prior to changing the web.config file, save a back-up copy of the original. Do this on the Central
Admin server and any additional Web Front End servers.
1. Find the web config for the EPM Live Web Application.
2. Edit the web config file in notepad and search for the providers section. Change this value to
true.
3. Above the line you just found, add the following line:
<add name="MultiAppCustomSiteMapProvider"
type="EPMLiveCore.MultiAppCustomSiteMapProvider, EPM Live Core, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=9f4da00116c38ec5" />
<add name="EPMLiveQuickLaunchProvider"
type="EPMLiveCore.Controls.Navigation.EPMLiveQuickLaunchProvider, EPM Live Core, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=9f4da00116c38ec5" />
5. Search for the modules section. You will need to apply the following line item to the end of the
section, if its not already there. Be sure to check first.
<add name="Session" type="System.Web.SessionState.SessionStateModule" />
6. Search the web config file for ReportViewerMessages. Comment out this line by adding <!--
before and --> after it, like this:
<!--add key="ReportViewerMessages"
value="Microsoft.SharePoint.Portal.Analytics.UI.ReportViewerMessages, Microsoft.SharePoint.Portal,
Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" /-->
Page 26
7. In the </appSettings> section, add the following key: (Note: This is only for windows authentication.)
<add key="Prefix" value="i:0#.w|" />
<add key="Domain" value="YourDomainHere" />
Replace YourDomainHere with your user domain. (Ex: If your login is corp\username then put corp
where it says YourDomainHere.)
8. Save the web config file and close it.
9. Reset IIS.
Add executionTimeout=3600 to the web.config file. Search for httpruntime from the top of the
web.config file.
Page 27
Page 28
Verify Services
EPM Live installs two Windows Services, PortfolioEngine Queue and WorkEngine Timer
Service. These services will only be installed on the application server where all EPM Live
components were installed.
Page 29
Page 30
Page 31
EPM Live will need to be activated in order to use the new functionality. In Central Administration,
General Application Settings, click the Feature Keys link under the WorkEngine Administration
heading. You should have received a Primary Feature Key from EPM Live to activate your installation. If
you servers do not have internet access, or are behind a proxy, you will need to use a manual key.
Simply send the Farm Guid found on this page along with your key to your EPM Live representative,
and they will assist you.
Enter your key into the Add Key section of the Feature Key page and click the Activate button. You
should see the key listed in the top part of this page, along with each feature you have access to and
how many users are active for each feature.
Page 32
Click the Application Settings link under the EPM Live Administration heading of the General
Application Settings page. This page displays the connection string used for EPM Live for each Web
Application, as well as the SSRS information. Be sure to enter the URL for Reporting Services for your
EPM Live web application, along with the Use Integrated Mode box.
In the Username and Password fields, you must enter the service account that is running the web
application on which EPM Live is installed. Enter the username in the form of domain\username. This is
the account that will be used to authenticate to SSRS, so it must have the permissions to read and
execute in SSRS.
Page 33
Page 34
Page 35
From the Server Start Menu, select SharePoint 2013 Central Administration.
Page 36
Under the WorkEngine Administration section, EPM Live has the following links for management of
EPM Live.
Feature Keys
Reporting Configuration
Queue
Application Settings
Active Servers
Solution File Versions
Create Site Collection
Page 37
This page shows the EPM Live keys that have been activated in your SharePoint environment. The keys
enable (allow) for the various EPM Live features, settings, and tools to be available on your server(s).
Page 38
This page is also where additional keys are added, such as when additional users are purchased, or new
functionality is to be enabled. If needed, the Farm Guid is shown on the page, under the field for
activating new keys.
When a user is disabled in EPM Live, it is recommended to come to the Feature Keys page to remove
that user from whichever features that user was active. This will free up the license access to that/those
features for an additional user.
Note: For customers whose servers do not have internet access, a "special key" will be created for your
organization. To create the special key, you will need to provide your Farm Guid to your EPM Live
Account Manager.
This page shows each site collection's mapping to its EPM Live Reporting Database. New mappings can
also be set up here. The mapping details include:
Site Collection
Database Server
Reporting Database Name
Page 39
3.3 Queue
This page allows for management of the EPM Live Queue (Timer) settings.
1. Enter the number of seconds for the Queue Interval. This specifies how often the queue
attempts to retrieve items awaiting the queue.
2. Enter the Thread Count. This specifies the number of concurrent threads the queuing system
will run.
3. Enter the Security Thread Count. This specifies the number of concurrent security threads the
queuing system will run.
Version Note: The Security Thread Count feature is available as of version 5.6.9.
Page 40
This page shows the current Queue Status for the selected Web Application.
This page shows which EPM Live solution files have been deployed on the server.
Page 41
This page displays the connection string used for EPM Live for each Web Application. The Connection
String needs to be entered for the EPM Live web application, as well as Central Administration. If your
Central Administration web application doesnt have a connection string, you can copy it from the EPM
Live web application. The Status dialog will turn green when you click Save Settings if your connection
string is entered properly.
Page 42
This page shows the SSRS information. Be sure to enter the URL for Reporting Services for your EPM
Live web application, along with the Use Integrated Mode box.
This page shows the active Web Front End (WFE servers) in the SharePoint Farm. If you have a "server"
key rather than "user" key, you would be able to specify the server(s) on which to activate the key.
Page 43
This page shows each of the EPM Live Solution Files and their corresponding version numbers.
Page 44
This page is the recommended approach for new EPM Live Site Collections. Using this method ensures
that the EPM Live templates, settings, etc. are set up correctly in the new Site Collection.
Page 45
This page shows the email templates that go out to users. Example emails include when a new user is
added to a site, when a new comment has been entered, when a user is assigned to a work item, and
when a project manager's project has pending updates in the Online Project Planner. You may edit the
body of these emails as needed.
Page 46
1. Navigate to Server
Navigate to your server that hosts Upland Analytics.
Page 47
3. Open web.config
Page 48
Find the old value for IzendaLicenseKey and replace with the new value that was provided.
Save file.
Close file.
5. Reset IIS
Page 49
Page 50
Page 51
1. For the Reporting Database section, select the New radio button.
2. Enter the SQL Server name and a database name. EPM Live recommends using the site name
and appending _Reporting to make it easy to find.
3. When finished, click the OK button.
When your new site collection is created, you will be directed to the new site collection. There are now
additional steps to be completed in the site collection. Refer to the next lessons to complete the
installation process.
Page 52
Navigate to the EPM Live Setup page by adding _layouts/ppm/setupppm.aspx to the end of the URL
of your site.
Leave the Base Path as it is pre-populated. Enter in your Product Key for EPM Live and the Company
name exactly as it was received by EPM Live. The database name you enter into the Database
Information section will be created in SQL by EPM Live. Enter your Database Server name. Typically the
Database Name will be your base path followed by _EPM Live. The User Name and Password will also
be created in SQL as a SQL Server Authenticated Account. This account is used for back end
communication with the EPM Live database. Click Setup Site.
Page 53
Complete Setup
Reload the Setup Status page until you receive the Complete status.
Note: If the status stays as "Queued" after several minutes of refreshing the page, make sure the
WorkEngine Timer service is started. If the service is started, then try restarting it and the job should
run.
Registry Modifications
There are some additional minor changes that need to be made to the registry after the PPM site setup
is complete.
Page 54
Follow the link to get to the site you just created. A window will pop up guiding you through the Setup
Wizard. Click Next.
Page 55
Enter the Username and Password of the account that will be used in the data sources for the SSRS
reports.
Be sure to select the "Use as Windows Credentials" box if using the web application account in the
format of domain\username. Alternatively, a SQL account can be used instead, so that the EPM Live End
Users (typically a site collection administrator) can create their own adhoc SSRS reports. This way, the
service account and credentials would not have to be given to the end users, nor do the end users need
direct access to the reporting database. Instead, the SQL account credentials would be given. A SQL
account is better for security reasons and administration overhead. If using a SQL account, do NOT
select this checkbox, and ensure that the account specified has at least datareader permissions to the
reporting database as well as execute permissions for all the stored procedures that have the "dbo."
prefix.
Click Next.
Page 56
Set a time for the Notifications, Timer, and Reporting Refresh Services to run. Typically these are set to
run late at night, or during off hours. Click Next. The Timer calculates recalculates fields that are the
Total Roll Up field type. The Timer runs on any lists on the Timer Settings page.
Page 57
If you select Yes, you will be directed to the Getting Started Page. If you select No, you can return to
the additional configuration steps (Get Started page) later. Click Finish.
Page 58
Page 59
Page 60
Page 61
Page 62