Optional installations
In addition to installing the foundation product, the database, and the application server (PPM Server), you can install Best Practices and Deployment Management Extensions on your system. Best Practices helps optimize your use of Program Management and Portfolio Management. Deployment Management Extensions provides entities unique to Oracle and SAP development environments.
Install Best Practices
This section provides details on installing Best Practices.
Requirements for installing Best Practices
To install Best Practices, you must have the following ready:
-
The OpenText PPM database schema name
-
The OpenText PPM database username and password
-
The OpenText PPM administrator username and password
-
Licenses for both the Portfolio Management and Program Management.
Install Best Practices
Follow the steps below to install Best Practices:
-
Start the PPM Server from the command line.
-
Set your server to RESTRICTED mode.
Note: Although setting your server to RESTRICTED mode is optional, we recommend that you do so. In RESTRICTED mode, the PPM Server enables only users with Administrator access granted to log on. You can use the setServerMode.sh script to set the server to RESTRICTED mode.
-
Run the kDeploy.sh script, as follows:
sh ./kDeploy.sh -best-practices
-
To verify that Best Practices is successfully installed, run the sh ./kDeploy.sh -l script. This returns a list of the deployed bundles in an instance.
Language support for Best Practices
OpenText PPM Best Practices content is available for all supported language packs. We recommend that you deploy language packs soon after you install Best Practices so that the its content matches in all languages.
Note: For detailed information about the language packs and how to install them, see Multilingual user interface.
Best Practices content
The Best Practices content includes the request types and workflows.
Caution: In order for OpenText PPM software to function correctly, Best Practices request types must be installed on your system and correctly associated with the menu items and project types.
Best Practices request types
|
Request Type and Description |
Menu Selections |
Field Groups |
|---|---|---|
|
PFM - Proposal Represents a project proposal within the Portfolio Management module. |
|
PFM Proposal |
|
PFM - Asset Represents the ongoing costs and maintenance of the result of a project in the Portfolio Management system. |
|
PFM Asset |
|
PFM - Project Represents data and process associated with project. This request type is connected to a project type. |
|
PFM Project |
| Program Details |
|
PFM Program |
|
Project Issue Represents issues associated with a project. |
Also associated with a project type to enable creating from within the Project Overview page. |
|
|
Project Risk Represents risks associated with a project. |
Also associated with a project type to enable creating from within the Project Overview page. |
|
|
Project Scope Change Request Represents scope changes associated with a project. |
Also associated with a project type to enable creating from within the Project Overview page. |
|
|
Program Issue Represents issues associated with a program. |
|
|
|
Program Risk Represents risks associated with a program |
|
|
|
DEM - Application Enhancement Used to request new functionality in IT current applications. |
|
|
|
DEM - Database Refresh Database refresh requests can be made for all IT Ops applications in the testing phase. |
|
|
|
DEM - Application Bug Used to report problems in IT applications. |
|
|
|
DEM - Initiative Used to request key projects for future quarters. |
|
|
You can create your own versions of the Best Practices request types by adding the appropriate field group, and then either editing the menu XML files or associating the request type with the project type (for Project Issue, Project Risk, and Project Scope Change).
Best Practices workflows
|
Best Practices Workflow |
Description |
|---|---|
|
PFM - Proposal |
Portfolio Management process for requesting a new project. |
|
PFM - Asset |
Portfolio Management process for an asset life cycle. |
|
PFM - Project |
Portfolio Management process for a project life cycle. |
| Program Process | Portfolio Management process for a program life cycle. |
|
DEM - Enhancement Request Process |
Demand Management process for enhancement requests for new functionality in applications. |
|
DEM - Database Refresh |
Demand Management process for database refresh requests. |
|
DEM - Bug Request Workflow |
Demand Management process for application bug requests. |
|
DEM - Project Initiative Process |
Demand Management process for initiative requests for key projects. |
|
Program Risk Management Process |
Automated process for program risk management. |
|
Risk Management Process |
Automated process for project risk management. |
|
Scope Change Request Process |
Automated scope change request process with three levels of severity. |
|
Issue Management Process |
Automated process for issue management. |
Install Deployment Management extensions
If you plan to install an Deployment Management Extension, you must do so after you install and configure OpenText PPM, and before you use OpenText PPM for processing.
You are not required to stop the PPM Server(s) before you install an Extension. However, we recommend that you install the Extension when no users are logged on to the system. Consider placing the server in RESTRICTED mode before you install.
Note: Although setting your server to RESTRICTED mode is optional, we recommend that you do so. In RESTRICTED mode, the PPM Server enables only users with Administrator access granted to log on. You can use the setServerMode.sh script to set the server to RESTRICTED mode.
For specific information on how to install an Deployment Management Extension, see the documentation for the Extension you purchased.

