Polarion® ALM™ Installation Guide for Linux

52 Pages·2012·1.06 MB·English

Once the PDF of this guide is exported, this title page will need to be updated in Word.

h ttp://cns.labs.polarion.com/repo/PolarionDPP/PolarionSVN/branches/3.10.3/documentation/sources/Installation

Guides/Polarion_platform/Linux (Polarion_Install_Guide_linux_front_cover.docx)

T hen exported as a PDF, and inserted manually in the PDF output from this file.

(THE Last TWO Pages as well)
​ ​
Polarion® ALM™ Installation Guide for Linux

March 1st, 2017

ver.17

Table of Contents
Table of Contents
About This Guide
Evaluation Installations
Large-scale Installations
1. System Requirements and Recommendations
Server Software
Server Hardware
Client Software
Client Hardware
Additional Recommendations
Libraries Required for Building the Demo Projects
Library Required for Exporting Highchart Charts
Enable Email Notifications
Enable Support for Javadoc
2. Linux Installation and Overview
Installation Types
Automated Installation
Supported Linux Versions for Automated Installation
Supported Platforms and Installation Types
Automated Installation Overview
Manual Installation
3. Automated Installation Procedure
4. System Startup and Shutdown
2
Starting Polarion
Shutting Down Polarion
Starting and Stopping the PostgreSQL Database
Integration with systemd
Integration with Init System
5. After Installation
Configuring PostgreSQL Database
Optimizing the PostgreSQL Database
Securing the Polarion Activation Application
Changing Default System Passwords
Changing the Default System Administrator Password
Changing the Password for SVN User ‘polarion’
Note for LDAP Users
Enter an Error Reporting Email
Configuring OLE Object Support
Prerequisites
Installation and Configuration
Configuring Polarion for OLE
Licensing and Activation
Using Different License Types
Assigning Named and Concurrent Users
License Usage Log File
Subversion Optimization
Multiple Repository Setup
Accessing the Polarion Portal
LDAP Authorization
Configuring Single Sign-on (SSO)
Kerberos SSO
Prerequisites - Configuring the Domain
Configuring Polarion
Configuring Client Browsers
Internet Explorer 11 and Edge, and Chrome on Windows
Chrome on Linux
Firefox
Teamcenter SSO
Prerequisites - TcSS Configuration
© 2017 Polarion AG
3
Polarion Configuration
Other SSO Considerations
Subversion Access
Direct Access to Subversion
Features Requiring Special Configuration in an SSO Setup
Troubleshooting
SSL
File Encoding
Kerberos Hints
Wrong Token Provided by the Browser
Polarion Unable to Log In to KDC
Next Steps after Installation
Removing Polarion
6. Technical Support
APPENDIX
Default Users and Groups
Enabling Email Notifications
Manual Installation on Linux
1. System Requirements and Recommendations
2. Required Third-party Software Components
Apache Server
htpassword utility
Subversion
PostgreSQL
Java SE JDK
Fonts Package
3. Configuration of Third-party Components
Apache HTTPD
Subversion
Java JRE and SDK
Java Virtual Machine Memory Limit
PostgreSQL
4. Installing Polarion
Installation Procedure
Setting Permissions
Notes on the Manual Installation
© 2017 Polarion AG
4
5. Configuring Polarion
6. Next Steps
Supported Microsoft Office® Versions

© 2017 Polarion AG
5
About This Guide
Welcome and thanks for using Polarion.
This guide covers installation information and procedures for creating a production installation for all
​ ​
Polarion products based on the Polarion Application Lifecycle Management Platform. The list of
products covered by this guide currently includes:

● Polarion® ALM™
​
● Polarion® REQUIREMENTS™
​
● Polarion® QA™
​

In general, the information is applicable to all the above products. Any product-specific differences
will be explicitly noted. The information covers both new installations and, where applicable, updating
of existing installations.

This guide applies to installation of the above Polarion products on supported Linux operating
systems.

If you want to install a product on a Windows system, please see the separate Installation Guide for
​
Windows document provided in the download archives for our Windows product versions, and also
​
available on the Polarion Software web site.
Evaluation Installations
If you are installing Polarion for evaluation purposes, we recommend the Polarion® ALM Trial Guide
™ ​
(PDF), available for download on any product download page at
https://polarion.plm.automation.siemens.com/. This guide focuses on getting you up and running
​
with an evaluation installation as quickly as possible, using the 1-click install option of the Windows
installer. (This is recommended for the initial stage of any evaluation.)
Large-scale Installations
If you need a large-scale server environment with multiple clustered servers and failover capabilities,
multiple repositories, etc. you should get the Polarion® ALM Enterprise Setup Guide (PDF), also
™ ​ ​
available on product download pages on the Polarion Software web site.

© 2017 Polarion AG
6
1. System Requirements and Recommendations
Server Software
Requirement Description
Operating SUSE Linux Enterprise Server 11 (SP 3 or higher) or 12, or Red Hat Enterprise Linux
​ ​
System 6.x or 7.x (7.2 or higher)/CentOS 6.x or 7.x (7.2 or higher), or Debian GNU/Linux
​ ​
7.0 or 8.0, or Ubuntu Server 14.04 or 16.04 LTS.
​ ​ ​ ​

URW fonts must be installed in the operating system. For SUSE, use the
ghostscript-fonts-std package from Ghost Script Fonts.
​ ​ ​
Java Runtime Java Platform, Standard Edition Development Kit 8 - Oracle JDK 8.
Environment (http://www.oracle.com/technetwork/java/javase/downloads/index.html)
​ ​
Note that OpenJDK 8 is not the same as Oracle Java 8 and is not officially
supported. JAVA_HOME/bin should exist in the system paths.
​ ​
Version Subversion version 1.6.x, 1.7.x, 1.8.x, or 1.9.x: http://subversion.apache.org/. If
​ ​
control you are compiling Subversion yourself, compile using the --with-apsx or the
​ ​
system --with-httpd option.
​ ​
Web Server Apache HTTPD server with mod_proxy_ajp and Subversion extension
​ ​
(WebDAV+SVN apache modules): http://httpd.apache.org/
​​

In general, the Polarion server should run with whatever Apache version is
present on a Linux system provided it is at least the minimum required version
(2.2), and mod_proxy_ajp and Subversion extension modules are also installed.
​ ​
Database Minimum: PostgreSQL version 8.4
​
Recommended: PostgreSQL version 9.2 or higher1
​ ​
Server Hardware
Requirement Description
RAM Minimum: 4 gigabytes for production installation.
Recommended: 8 gigabytes or more.
Disk Storage ● Minimum: 10 GB (gigabytes)
Space ● Recommended: 40 GB (gigabytes) or more
There is no hard and fast rule for disk storage space. The actual amount you will
require depends on the number and size of projects managed with Polarion. The
more projects, and the larger they are, the more disk storage you will require.
1​ PostgreSQL version 9.2 or higher is required to create the new “rel_module_workitem” database table. The table contains
​ ​ ​
information about Work Items both contained or referenced within a document.
© 2017 Polarion AG
7
Client Software
Requirement Description
Operating System Any operating system that can run the supported web browsers with support
for the Flash plugin (see below).

If the client user will use a Polarion product supporting data interchange with
Microsoft Office®​, the client user must run a Windows operating system
​
compatible with a supported version of the Microsoft Office application(s)
used. For details, please see Appendix: Supported Microsoft Office Versions.
​ ​
Web Browser All you need to use Polarion is a web browser. The most current list of
supported browsers and versions is provided in the Release Notes section of
the README.html file, delivered in all download distributions of all Polarion
​ ​
products.
Adobe Flash The Polarion web portal displays charts and other graphical data about
Polarion-managed projects using Adobe Flash.

To view these properly using a web browser, the client computer must have
Adobe Flash Player installed. You can download it free at
http://www.adobe.com/products/flashplayer/.
​
Client Hardware
Requirement Description
RAM Minimum: 2 GB (4 GB recommended)
Display Resolution Minimum: 1280 x 800 pixels
Server Connection Not less than 1 Mbit/S

© 2017 Polarion AG
8
Additional Recommendations
The items described in this section are not critical for running and evaluating Polarion. However, the
components described are needed to be able to fully utilize the product's capabilities.
Libraries Required for Building the Demo Projects
The distribution contains several demo projects. Each of them needs its particular set of 3rd party
libraries to be correctly built and have the project reports generated. Any missing libraries are
automatically downloaded from the Internet during project processing, so you may need a connection
to the internet when you first try building the demo projects or running reports for them.
Library Required for Exporting Highchart Charts
​ ​
Applicable only for 32-bit Linux: The Phantom JS library is used for preview and PDF export of
Highcharts charts. Only the 64-bit version of the library is bundled with Polarion’s Linux distributions.
​
If you run Polarion on 32-bit Linux, you must obtain and install the 32-bit version of the library. The
procedure is documented in online Help. In the Administrator’s Guide chapter Configuring PDF Export,
​ ​
see the section Configuring Highcharts Export, and in particular the sub-section Installing 32-bit
​ ​ ​
Phantom.js.
​

The urw-fonts package must be installed on CentOS and SuSE. See the same Help topic for
​ ​
information.
Enable Email Notifications
The Polarion server can send email notifications in response to various events in the system such as
build completions, new work items, etc. It can also notify users about external changes.

To enable Polarion to send out email notifications you need to:

1. You can do this before starting Polarion server by setting the host name in the
announcer.smtp.host property in the polarion.properties file located in
​ ​
$POLARION_HOME$/etc/ . There you should also set the announcer.smtp.user and
​ ​ ​
announcer.smtp.password properties to a valid email account on the SMTP host specified in
​
announcer.smtp.host. If your SMTP server doesn’t listen on default port 25, change the port
​
setting in announcer.smtp.port. You may wish to create a special account on your SMTP host
​ ​
for use with Polarion notifications.

2. Provide a valid email address for each user in their user account. (Administration > User
Management > Users.) This can be automated through user self-creation of accounts, or
integration with LDAP. See Help, Administrator’s Guide: Managing Users and Permissions.
​ ​

© 2017 Polarion AG
9
When this configuration is correctly set up, the system will send notification e-mails about various
events according to the notification targets configuration. For information on configuring email
notifications, see Help, Administrator’s Guide: Configuring Notifications.
​

NOTE
If a Work Item is modified outside of the Polarion portal, (e.g.
manually in SVN), email notifications are sent the same as they
would be if the modification has been done in the portal.
Enable Support for Javadoc
The demo projects (and your projects) can be configured to provide Javadoc reports.
Javadoc must also be enabled for the descriptors.xml file. Access it in the Repository perspective:
Repository/.polarion/reports/descriptors.xml . Refer to comments in the file for
​
enabling Javadoc.

© 2017 Polarion AG
10
2. Linux Installation and Overview
This chapter covers installation procedures for Linux. There is also some information about initial
configuration of Polarion on Linux, as well as reference information about the Polarion installation
structure and third-party components.
Installation Types
● Automated installation means that the entire installation process is driven automatically by
​
an installation script. At most you have to answer some questions by typing, but you do not
pre-install anything or do any other manual work in order to satisfy the prerequisites and the
success of the installation process before you start the script. Automated installation is
possible on most, but not all, of the supported Linux platforms.

● Manual installation means you must pre-install required infrastructure software before you
​
attempt to install the Polarion platform. You follow steps in documentation as opposed to
interactive instructions from a script. You may also need to write some shell scripts by hand or
modify the manual_install.sh file before running it.
​ ​

● Semi-automated installation is a third type in which the automated installation process script
​
is not able to install all the prerequisites for some platform automatically, so it requests you to
install something manually before proceeding.

For installation types and the platforms for which they are applicable, see Supported Platforms and
​
Installation Types in the next section.
​
Automated Installation
The automated installer scripts detect the operating system. The OS version is not checked, however,
so you need to ensure that you have the minimal required version of your system as specified in
Server Software Requirements.

If you have different version of the OS from the supported distributions, it is probably still possible to
perform an automatic installation. However, during the process you will need to manually install
required third-party software before you respond no to installation default dependencies.

If your OS is supported, the automated scripts will install the prerequisite third-party software for the
specific supported Linux platform from existing package repositories on your system during the
Polarion installation process, after which they will then install the Polarion platform itself. Please
ensure that you have set up package repositories defaults provided for your system.

© 2017 Polarion AG