Using the Policy Manager Services Feature

Learn how to install the Policy Manager Services feature.

Using Admin Console Managing Containers

Supported Platforms: 7.x, 8.0

Table of Contents

  1. Introduction
  2. Step 1: Installation Prerequisites
  3. Step 2: Install Policy Manager Services Feature
  4. Step 3: Configure PKI Keys
  5. Step 4: Configure Database Options
  6. Step 5: Perform Provisioning (PM80)
  7. Step 6: Configure Policy Manager Administrator Credentials
  8. Step 7: Complete Configuration

Introduction

This feature includes services provided by the central Policy Manager governance application. These services include, but are not limited to, UDDIv2 and UDDIv3, WS-MetadataExchange, Container Configuration, an XACML Policy Decision Point, a WS-Trust Security Token Service, Alert reporting, and RESTful interfaces to the governance model. In addition, this feature includes engines for performing Quality of Service calculations and health and status monitoring.

Note: Managed Services, Scheduled Jobs, Security Services features are installed as part of this feature installation.

Back to top

Step 1: Installation Prerequisites

  • Installation of one of the supported platform versions.
  • A Policy Manager container must be defined using the Configure Container Instance Wizard.
  • If you are using MySQL 5.6 with Policy Manager 8.0 and/or Policy Manager 8.0 and Community Manager 8.0 a series of MySQL property settings must be configured. See MySQL Database Property Settings.

Back to top

Step 2: Install Policy Manager Services Feature

  1. Launch the Administration Console (http://<hostname:<port>/admin/).
  2. On the Installed Features screen, select Feature from the Filter menu.
  3. Select the Policy Manager Services feature and click Install Feature.
  4. After the installation is complete, click Configure and continue to Step 3.

Back to top

Step 3: Configure PKI Keys

  1. The Manage PKI Keys Wizard wizard allows you to configure the private key and certificate for the container when communicating with a governance console.
  2. Select a "Key Management Option" and click Next to continue. For this walkthrough we will use the default key option Generate PKI Keys & X.509 Certificate.
  3. Refer to Managing Keys for more information about each option and configuration instructions.
  4. After completing the key management task, click Next to continue.

Back to top

Step 4: Configure Database Options

  1. The Configure Database Options Wizard > Select Database Option screen provides options for selecting the database to be used with the current container configuration.
  2. Refer to Configure Database Options / Add Database for more information about available options, properties for your specific database type, and configuration instructions.
  3. For MSSQL users. Complete the following steps after you configure MSSQL and receive the summary screen confirmation.
  4. You must set the quartz trigger property to True. This is a required to prevent database dead-locks.
  5. Select the Configuration tab and the com.soa.scheduler.quartz Configuration Category. Change the org.quartz.jobStore.acquireTriggersWithinLock property to B. Resume the Policy Manager configuration after completing this task.

For MSSQL Users

Complete the following steps after you configure MSSQL and receive the summary screen confirmation. You must set the quartz trigger property to True. This is a required to prevent database dead-locks.

  1. Select the Configuration tab and the com.soa.scheduler.quartz Configuration Category. Change the org.quartz.jobStore.acquireTriggersWithinLock property to True and Apply Changes. Resume the Policy Manager configuration after completing this task.

For MySQL 5.6 and Users (Policy Manager 8.0 and Community Manager 8.0 only)

If you are using MySQL 5.6 with Policy Manager 8.0 and/or Policy Manager 8.0 and Community Manager 8.0 a series of MySQL property settings must be configured. See MySQL Database Property Settings.

Back to top

Step 5: Perform Provisioning (Policy Manager 8.0 only)

Provisioning initializes resources associated with the current feature set being installed. For example, if you install both the Policy Manager Services and Policy Manager Console features and enable provisioning, the system will add system services, default policies, default workflows, a default container to the Policy Manager Management Console, and will create a Policy Manager Admin User account. In this scenario, if you did not enable provisioning, you would not be able to log into the Policy Manager Management Console unless another Policy Manager container was provisioned.

Note: This feature is introduced in Policy Manager 8.0. If you are using an earlier Policy Manager version, skip this step.

There may be scenarios where provisioning is not required. For example, if the current deployment is using a read-only database you could disable provisioning.

  1. Select the “Perform Provisioning” checkbox to enable provisioning. Uncheck it to skip provisioning for the current feature set. After making your selection click “Finish.”

Note: This is a one time configuration task performed in the Administration Console, and does not appear in the Configure > Configuration Categories section after you have completed the feature configuration.

Back to top

Step 6: Configure Policy Manager Administrator Credentials

The Policy Manager Administrator Credentials screen is used to create an "Administrator" user account definition for logging into the Policy Manager Management Console. The user account definition is composed of a "Username" and "Password." After restarting the Administration Console, you can log into the Policy Manager Management Console using the administrator credentials. The User Account definition can be updated via the Security tab.

Note: This is a one time configuration task performed in the Administration Console, and does not appear in the Configure > Configuration Categories section after you have completed the feature configuration.

  1. In the "Credentials" section, enter "Username," "New Password," and "Confirm New Password" for the Policy Manager "Administrator" user account. After completing your entries, click Finish. The system restart message displays. Click OK to restart the system, click Cancel to restart the system later.
  2. When the "Complete Configuration" screen displays, continue to the next step.

Back to top

Step 7: Complete Configuration

  1. The Complete Configuration task performs configuration operations associated with one or more "Feature" installations. Operations typically include starting components, setting property values, and initializing credentials.
  2. The system restart was initiated when Finish was clicked on the Credentials Summary screen. After the system restarts and initializes the installed features for use, click Close to log out of the Administration Console.
  3. To exit the wizard and perform a system restart at a later time, click Close. Configuration changes are saved and the Complete Configuration task is available via the "Installed Features" tab in the "Pending Installation Tasks" section.

Back to top