Setup Guide

Prerequisites

The Policy Admin doesn't require Security to be enabled on the framework in order to be installed, however the functioning of many of its features do. For information on how to start the framework with Security enabled refer to this guide.

Installation

Automated Installation

The Policy Admin module provides three Kit Manager installation scripts located in the bin/pscripts folder.

• "Policy Admin" (found in the file com.prosyst.mbs.policyadmin.txt), which installs only the Policy Admin module. For automated installation execute the console command:

  kitman.i "Policy Admin"

• "Policy Admin Inventory" (found in the file com.prosyst.mbs.policyadmin.inventory.txt), which installs along with the Policy Admin module the Apache Felix Inventory. For automated installation execute the console command:

  kitman.i "Policy Admin Inventory"

• "Policy Admin Web Console" (found in the file com.prosyst.mbs.policyadmin.webconsole.txt), which installs the Policy Admin module along with the Web Console interface. For automated installation execute the console command:

  kitman.i "Policy Admin Web Console"

Manual Installation

Install and start the Policy Admin bundles in the following order:

• com.prosyst.mbs.policyadmin.core.jar
• com.prosyst.mbs.policyadmin.api.jar
• com.prosyst.mbs.policyadmin.commands.jar
• com.prosyst.mbs.policyadmin.identity.condition.jar
• com.prosyst.mbs.policyadmin.identity.useradmin.jar
• com.prosyst.mbs.policyadmin.policy.jar
• com.prosyst.mbs.policyadmin.webconsole.jar
• com.prosyst.mbs.policyadmin.http.websockets.jar

Initial Configuration

Policy Provider

Every bundle, that has the appropriate permissions can be a policy provider. That means that it contains all the required files, in the correct format and placed in the appropriate locations.

Order of Processing

The policy providers are processed in their start order. So if you have two policy providers, the one that starts first, will be also processed first. In the scope of a single policy provider the following operations are performed in sequence: the functions, groups and identities are loaded and created in policy admin associated users with groups (setting group members) creating the policy elements.

Policy Removal

Stopping or uninstalling the Policy Provider will also remove the elements it has provided. That means all identities, groups, functions and policy elements are removed.