Hi all,

I have implemented the policy core as described in the previous mail. There
is a single osgi service which exposes all the function of the policy core.

org.wso2.carbon.policy.mgt.core.PolicyManagerService

This service is exposing the PAP, PIP, PEP functionalities. To integrate
with the admin UI, use the getPAP() method which will give
the org.wso2.carbon.policy.mgt.common.PolicyAdministratorPoint
implementation.

To integrate with device type based jax-rs web apps, please use getPEP(),
which will return org.wso2.carbon.policy.mgt.common.PolicyEvaluationPoint
implementation. This has two methods, one returns the effective policy and
other returns the feature set with configurations.

Thanks
Geeth


*G. K. S. Munasinghe*
*Senior Software Engineer,*
*WSO2, Inc. http://wso2.com <http://wso2.com/> *
*lean.enterprise.middleware.*

email: [email protected]
phone:(+94) 777911226

On Mon, Mar 16, 2015 at 12:27 PM, Geeth Munasinghe <[email protected]> wrote:

> Hi all,
>
> CDM is capable of applying configurations (profiles) to managed devices.
> These configurations (or profiles) will defend on device types, device
> supported OS versions, device owners privileges, time and location of the
> devices.
>
> Configurations are such as disable/enable camera, change wifi settings,
> device locking, adding security.  A set of configuration is identified in
> CDM as a Profile. Profile can be  attached to  policies. Policy has the
> conditions and rules how this profile should be applied to a given device.
>
> Following is the proposed policy architecture which is being implemented
> with CDMF.
>
>
> ​
> There are several components and web applications in the architecture
> diagram.
>
>
>    1. Policy Core   - This will have the core functionalities related to
>    policy which includes policy persisting (PAP), policy retrieval from the
>    database (PIP) and a policy management service. This service will be an
>    osgi service which expose the full policy management functionality.
>    2. PDPs (Policy Decision Point) can be pluggable to the current
>    architecture. We will write a simple PDP (Priority based) in the first
>    release and complex PDP (with policy merging) in the next release.
>    3. PEP Web applications - These will be device type related web
>    applications which will communicate with devices.
>    4. PAP Web application - This will be a restful web app which will
>    expose the policy admin functionalities. (This is for external users) But
>    we are using jaggery web app as front end application which will call the
>    backend osgi service directly.
>
>
> Thanks
>
> Geeth
>
>
>
>
> *G. K. S. Munasinghe*
> *Software Engineer,*
> *WSO2, Inc. http://wso2.com <http://wso2.com/> *
> *lean.enterprise.middleware.*
>
> email: [email protected]
> phone:(+94) 777911226
>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to