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 10 lines
# 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.
# Ensure that everyone is out of the system and that no one attempts to log in while changing the P2K password.
# __''Do not''__ shut down any of the managed server while making changes to the P2K password. The follow steps require access to the application. However all managed servers will need to be restarted once completed.
# Change the user password within the application itself, using either the IMUS or IMRU screens.
# Change the password in the DB Login page. Each Personality EAR deployment maintain a separate file with the database connection information, including an encrypted copy of the P2K password. This is generated or altered by navigating to the ''adminConsole'' web 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 change. The web page should have a URL structure similar to http://your.server.name/''Personality''/adminConsole - with ''Personality ''being the name of each managed server the application has been deployed into.
# Change the password in the HLCPooledDataSource within the WebLogic Server. Login into the WLS Administration Console and navigate to Services and Data Sources to find this entry.
# Shutdown and restart each managed server that connects to this database.
# Ensure you are able to log into the application with both Admin and Self-Service.
# Restore the normal links to the index.html file, if you have changed it.
Since the Symmetry Tax Engine (STE) does not connect to the Oracle database, it does not need or store the P2K password. No changes are required for STE and it can remain running while these changes are performed. \\
# 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.
# Ensure that everyone is out of the system.
# All accesses should be shut down while making changes to the P2K password to ensure no one is attempting to log in during this time. It also should not be restarted until the server engine is able to successfully connect to the database after the change is complete.
# US Tax Server
#* If you are using the [Symmetry|SYMMETRY] server, it does not connect to the Oracle database during normal operation and does not store the P2K password anywhere. STE does not need to be running, nor does it need to be upgraded/reinstalled after you change this password
# 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
# Bring up the Admin and all Browser applications and confirm that everything is OK.
# Restore the normal links to the index.html file, if you have changed it.
At line 15 changed 3 lines
! [Notes|Edit:Internal.Instructions for changing P2K Password]
![Notes|Edit:Internal.Instructions for changing P2K Password]
At line 16 added 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