This page (revision-12) was last changed on 26-Nov-2021 10:22 by Iain Barr

This page was created on 26-Nov-2021 10:22 by rforbes

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
12 26-Nov-2021 10:22 2 KB Iain Barr to previous
11 26-Nov-2021 10:22 2 KB Iain Barr to previous | to last
10 26-Nov-2021 10:22 2 KB Iain Barr to previous | to last
9 26-Nov-2021 10:22 1 KB Iain Barr to previous | to last
8 26-Nov-2021 10:22 1 KB jaiken to previous | to last
7 26-Nov-2021 10:22 1 KB jaiken to previous | to last
6 26-Nov-2021 10:22 2 KB rforbes to previous | to last
5 26-Nov-2021 10:22 2 KB rforbes to previous | to last VERTEX ==> Vertex.VERTEX
4 26-Nov-2021 10:22 2 KB rforbes to previous | to last
3 26-Nov-2021 10:22 2 KB rforbes to previous | to last
2 26-Nov-2021 10:22 985 bytes rforbes to previous | to last Instructions for changing P2K Password ==> Changing P2K Password
1 26-Nov-2021 10:22 985 bytes rforbes to last

Page References

Incoming links Outgoing links
Changing P 2 K Password
Changing P2K Password

Version management

Difference between version and

At line 3 changed one line
# Replace the normal link to get into the Professional and all Self Service applications with a “system temporarily unavailable” web page. This is an optional step. If you have an index.html file, it would be normally located in the \Apache\Apache\htdocs directory.
# Replace the normal link to get into the application with a “system temporarily unavailable” web page. This is an optional step. If you have an index.html file, it would be normally located in the \Apache\Apache\htdocs directory.
At line 8 changed 2 lines
# Change the P2K password through the professional interface and immediately exit the system.
# Each [{$applicationname}] EAR deployment maintain a separate file with the database connection information. This file also contains an encrypted copy of the P2K password. This is configured by navigating to the ''adminConsole'' page. If you have more than one instance connecting to the same database, all their password files will need to altered to ensure they are able to connect the database after the password has been changed
# Change the P2K password through the application and immediately exit the system.
# Each Personality EAR deployment maintain a separate file with the database connection information. This file also contains an encrypted copy of the P2K password. This is configured by navigating to the ''adminConsole'' page. If you have more than one instance connecting to the same database, all their password files will need to altered to ensure they are able to connect the database after the password has been changed
At line 16 removed 2 lines
get into the Professional and all Self Service applications so users can continue.
This page (revision-12) was last changed on 26-Nov-2021 10:22 by Iain BarrTop