PeopleTools Version :
From PIA you could press ctrl+J and check the tools version.
From file server, you can check the version at the top left when you open the psadmin utility.We can also see the details from App d or data mover on signin page .Also you can check in peopletools.properties file. This should be updated when you install a patch to show the correct patching detail.
Application version :
From PIA press ctrl+J and check the application version.
From database query the table PSRELEASE and check the latest updated row.
Tuxedo version :
From cmd , change directory to the bin folder of where you installed the tuxedo. then run this command :
tmadmin -v
WebLogic Version :
From cmd change directory to WL_HOME/server/lib and run this command :
java -cp weblogic.jar weblogic.version
Database Version :
When you connect to database, it shows which version are you connected to.
Also you can query v$instance .
Verity Version :
Navigate from file server to Navigate to verity\winx86\_nti40\bin
and run the command : Rcvdk.exe
From PIA you could press ctrl+J and check the tools version.
From file server, you can check the version at the top left when you open the psadmin utility.We can also see the details from App d or data mover on signin page .Also you can check in peopletools.properties file. This should be updated when you install a patch to show the correct patching detail.
Application version :
From PIA press ctrl+J and check the application version.
From database query the table PSRELEASE and check the latest updated row.
Tuxedo version :
From cmd , change directory to the bin folder of where you installed the tuxedo. then run this command :
tmadmin -v
WebLogic Version :
From cmd change directory to WL_HOME/server/lib and run this command :
java -cp weblogic.jar weblogic.version
Database Version :
When you connect to database, it shows which version are you connected to.
Also you can query v$instance .
Verity Version :
Navigate from file server to Navigate to verity\winx86\_nti40\bin
and run the command : Rcvdk.exe
No comments:
Post a Comment