Upgrade Guide › Upgrade Procedures › Policy Server and CSP Console Upgrade › Verify the Upgrade

Verify the Upgrade

Follow these steps:

1. Verify dxserver status by executing these commands:

   su - dsa
   dxserver status
   

   Verify that one "tenantname-tenant-router started" message exists for each tenant in the environment.

2. Verify that the CSP console is working properly by confirming that the tenant and container tasks exist. Execute the following command:

   ps -ef | grep ui
   

   You should see a message similar to the following:

   00:00:00 /bin/sh /opt/CA/siteminder/adminui/jboss-as/bin/run.sh 
   

3. Verify that the Policy server is working properly. Execute the following command:

   ps -ef | grep site
   

   You should see output similar to the following:

   smuser   17067     1  0 06:10 ?        00:00:00 /bin/sh /opt/CA/siteminder/adminui/bin/run.sh
   smuser   17095 17067  1 06:10 ?        00:06:15 /opt/java32/bin/java -Dprogram.name=run.sh -server
   -Djboss.platform.mbeanserver -Djava.security.policy=workpoint_client.policy -Xms256m -Xmx1024m
   -XX:MaxPermSize=256m -XX:ReservedCodeCacheSize=50m -Djava.net.preferIPv4Stack=true
   -Djava.endorsed.dirs=/opt/CA/siteminder/adminui/lib/endorsed -classpath
   /opt/CA/siteminder/adminui/bin/run.jar:/opt/java32/lib/tools.jar org.jboss.Main -b 0.0.0.0 -c default
   root     17533     1  0 06:13 ?        00:00:00 /opt/CA/siteminder/bin/smexec
   root     17534 17533  0 06:13 ?        00:00:26 /opt/java32/jre/bin/java -Xrs
   -Dnete.ps.root=/opt/CA/siteminder -classpath
   /opt/CA/siteminder/lib/smconapi.jar:/opt/CA/siteminder/monitor/smmon.jar
   com.netegrity.smmonagent.SmMonAgentRun
   root     32507 32487  0 15:50 pts/0    00:00:00 grep site
   

4. Verify that Tomcat is working properly. Execute the following command:

   ps -ef | grep tom
   

   You should see output similar to the following:

   root      1661     1  0 05:29 ?        00:00:00 automount --pid-file /var/run/autofs.pid
   root     22801     1  0 06:03 ?        00:02:20 /opt/java64/jre/bin/java
   -Djava.util.logging.config.file=/opt/CA/AdvancedAuth/Tomcat/conf/logging.properties -Xms256m -Xmx1024m
   -XX:MaxPermSize=256M -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
   -Djava.endorsed.dirs=/opt/CA/AdvancedAuth/Tomcat/endorsed -classpath
   /opt/CA/AdvancedAuth/Tomcat/bin/bootstrap.jar:/opt/CA/AdvancedAuth/Tomcat/bin/tomcat-juli.jar
   -Dcatalina.base=/opt/CA/AdvancedAuth/Tomcat -Dcatalina.home=/opt/CA/AdvancedAuth/Tomcat
   -Djava.io.tmpdir=/opt/CA/AdvancedAuth/Tomcat/temp org.apache.catalina.startup.Bootstrap start
   root     32528 32487  0 15:53 pts/0    00:00:00 grep tom
   

5. Verify that Riskfort is working properly. Execute the following command:

   ps -ef | grep rf
   

   You should see output similar to the following:

   nobody    1960     1  0 05:29 ? 00:00:00 /usr/sbin/dnsmasq --strict-order --bind-interfaces
   --pid-file=/var/run/libvirt/network/default.pid --conf-file= --except-interface lo --listen-address
   192.168.122.1 --dhcp-range 192.168.122.2,192.168.122.254
   --dhcp-leasefile=/var/lib/libvirt/dnsmasq/default.leases --dhcp-lease-max=253--dhcp-no-override
   root     21679     1  0 06:13 ?        00:00:00 /opt/CA/AdvancedAuth/sbin/arrfwatchdog
   /opt/CA/AdvancedAuth/sbin/arrfserver
   root     21680 21679  0 06:13 ?        00:00:00 /opt/CA/AdvancedAuth/sbin/arrfserver
   root     32537 32487  0 15:53 pts/0    00:00:00 grep rf
   

6. Verify that Webfort is working properly. Execute the following command:

   ps -ef | grep wf
   

   You should see output similar to the following:

   root     21718     1  0 06:13 ?        00:00:00 /opt/CA/AdvancedAuth/sbin/arwfwatchdog
   /opt/CA/AdvancedAuth/sbin/arwfserver.real
   root     21721 21718  0 06:13 ?        00:00:01 /opt/CA/AdvancedAuth/sbin/arwfserver.real
   root     32546 32487  0 15:54 pts/0    00:00:00 grep wf