2 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
3 .. http://creativecommons.org/licenses/by/4.0
5 **********************************************
6 Testing, Deploying and Debugging the PDP-X/PAP
7 **********************************************
12 PAP (Policy Administration Point)
13 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
15 Accessing and Starting PAP
16 --------------------------
18 - To access the PAP docker use
22 docker exec -it -u 0 pap su - policy
24 - All Policy related software are installed under the policy account, the policy root directory is under *${POLICY_HOME}* environment variable and it may be changed on a per installation basis. It is typically set up under the */opt/app/policy* directory but can be changed during installation. All Policy software runs with non-root privileges as *policy* is a regular user account.
26 - Once within the PAP Container the running status can be checked using the following policy status command.
30 policy.sh [--debug] status|start|stop
32 - To get the current status of Policy use *policy.sh status*
36 policy@pap:~$ policy.sh status
37 pap: UP: running with pid 2114
38 console: UP: running with pid 2135
39 paplp: UP: running with pid 2155
40 3 cron jobs installed.
42 - To Stop the components use *policy.sh stop*
46 policy@pap:~$ policy.sh stop
51 - To Start use *policy.sh start*
55 policy@pap:~$ policy.sh start
63 - The Healthcheck feature resides in the PDP-D that proxies for PAP, PDP-X, etc. To perform the Healthcheck on policy components you can follow the generic procedure documented as below, these commands must be executed within the PDP-D container.
67 # Assuming the healthcheck service credentials have not been changed
68 # post-installation within the drools container
70 source /opt/app/policy/config/feature-healthcheck.conf.environment
72 curl -k --silent --user "${HEALTHCHECK_USER}:${HEALTHCHECK_PASSWORD}"
73 -X GET https://localhost:6969/healthcheck | python -m json.tool
75 - Additional information can be found in the documentation for Testing, Deploying, and debugging on a PDP-D Healthcheck.
80 - The main application logs for PAP are located at */var/log/onap/policy/pap/* location. The catalina.out can be found at *$POLICY_HOME/servers/pap/logs/* location.
82 * Policy PAP uses EELF logging framework for logging and if needed to be modified can be modified at *$POLICY_HOME/servers/pap/webapps/pap/WEB-INF/classes/logback.xml*. This change needs a restart of the PAP component in order to be in effect.
84 - The logs are divided into separate files and debug logs can be found in *debug.log* and error logs in *error.log* file which are two different files under application logs directory.
86 PDP-X (XACML Policy Decision Point)
87 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
89 Accessing and Starting PDP
90 --------------------------
92 - To access the PDP-X docker :
96 docker exec -it -u 0 pdp su - policy
98 - To start and stop the PDP-X components the same procedure can be followed as documented for PAP.
102 policy.sh [--debug] status|start|stop
105 Swagger UI Testing (Only for HEAT installations)
106 ------------------------------------------------
108 - The PDP-X provides the swagger UI from which PDP-X REST APIs can be tested and used, this also lets us know the PDP Status.
109 - In order to access PDP's swagger UI visit ``https://{PDP_URL}:8081/pdp/swagger-ui.html.``
110 - NOTE: This feature is only available for HEAT installation as it is disabled in OOM installations.
115 - The main application logs for PDP are located at */var/log/onap/policy/pdpx/* location. The catalina.out can be found at *$POLICY_HOME/servers/pdp/logs/* location.
117 * Policy PDP uses EELF logging framework for logging and if needed to be modified can be modified at *$POLICY_HOME/servers/pap/webapps/pdp/WEB-INF/classes/logback.xml*. This change needs a restart of the PDP component in order to be in effect.
119 - The logs are divided into separate files and debug logs can be found in *debug.log* and error logs in *error.log* file which are two different files under application logs directory.
122 BRMSGW (Business Rule Management System Gateway)
123 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
125 Accessing and Starting BRMSGW
126 -----------------------------
128 - To access the BRMSGW docker :
132 docker exec -it -u 0 brmsgw su - policy
134 - To start and stop the BRMSGW components the same procedure can be followed as documented for PAP and PDP-X.
138 policy.sh [--debug] status|start|stop
143 - The main application logs for BRMSGW are located at */var/log/onap/policy/policyapi/* location. The logs are divided into separate files; debug logs can be found in *debug.log* and error logs in *error.log* file which are two different files under application logs directory.
145 * The brmsgw.log can be found at */var/log/onap/policy/brmsgw* location.
150 .. SSNote: Wiki page ref. https://wiki.onap.org/pages/viewpage.action?pageId=16003633