Reset the Siteminder Administrative UI Manually
Article ID: 32458
Updated On:
Products
Issue/Introduction
On occasion it may be necessary to manually ‘Reset’ or reconfigure the Siteminder AdminUI. This can be the case when you’ve overwritten an existing Policy Store to which the Policy Server which the AdminUI is configured to connect to has been overwritten by the import of a policy store from another environment. This may also be necessary when pointing an existing WAMUI at a new environment. This can frequently be presented as a problem connecting to the Policy Server with the AdminUI where previously it had worked without any problems.
Frequently previous attempts to re-run XPSRegClient and even smreg –su to reset the Siteminder password have not resolved connection issues with the AdminUI.
This document goes through the detailed steps on how to rest an existing WAMUI. However it primarily focuses on the steps when the AdminUI is implemented on the default embedded JBoss application server.
Environment
PRODUCT: Siteminder
COMPONENT: Administrative UI
VERSION: Any
OPERATING SYSTEM: Any
Resolution
I. Stop the AdminUI
MS WINDOWS:
Stop the AdminUI using SERVICES
1) Open the Services Manager
Start -> Run -> Services.msc
OR
Server Manager -> Configuration -> Services
OR
Start –> Control Panel -> Administrative Tools -> Services
2) Locate and stop the “SiteMinder Administrative UI” service
Stop the AdminUI from a command prompt:
1) Launch 'cmd.exe' with elevated privileges (Run As Administrator)
2) Run the following command:
sc stop SMADMINUI
LINUX:
1) Change to the AdminUI installation directory
cd /<AdminUI_Dir>/siteminder/adminui/bin
2) Stop the JBoss Application server
jboss-cli.sh -c --command=:shutdown
II. Delete the AdminUI Configuration
1) Logon to the AdminUI host
2) Back-up the following directory
Windows: <AdminUI_Home>\CA\SiteMinder\adminui\server\default\data
Linux: <AdminUI_Home>/CA/SiteMinder/adminui/server/default/data
2) Delete the '/data' directory:
III. Delete the AdminUI objects from the Policy Store
1) Logon to the Policy Server
2) Run XPSExplorer
WINDOWS:
i) Launch 'cmd.exe' with elevated privileges (Run As Administrator)
ii) XPSExplorer
LINUX:
i) Change to the Policy Server installation directory
cd /<PS_InstallDir>/siteminder/
ii) Set the Policy Server Environment Variables
. ./ca_ps_env.ksh
iii) Run XPSExplorer
3) Delete the Trusted Host Object
i) Locate and Open the "TrustedHost" Object class in the XPSExplorer menu
ii) Locate the Trusted Host Object for the AdminUI. (NOTE: This will match the HOSTNAME from the <Install_Dir>\SiteMinder\adminui\standalone\data\siteminder\<OID>.conf
EXAMPLE: <OID> Format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.conf"
4) Delete the AdminUI Administrator
(I) Name : "SMWAMUI:<TrustedHostName>
IV. Prepare the Policy Server for a new AdminUI Registration
1) Logon to the Policy Server
2) Run XPSRegClient
WINDOWS:
i) Launch 'cmd.exe' with elevated privileges (Run As Administrator)
ii) Run the following command:
XPSRegClient siteminder:<password> -adminui-setup
LINUX:
i) Change to the Policy Server installation directory
cd /<PS_InstallDir>/siteminder/
ii) Set the Policy Server Environment Variables
. ./ca_ps_env.ksh
iii) Run the following command:
XPSRegClient siteminder:<password> -adminui-setup
V. Start the AdminUI
MS WINDOWS:
Start the AdminUI using SERVICES
1) Open the Services Manager
Start -> Run -> Services.msc
OR
Server Manager -> Configuration -> Services
OR
Start –> Control Panel -> Administrative Tools -> Services
2) Locate and stop the “SiteMinder Administrative UI” service
Stop the AdminUI from a command prompt:
1) Launch 'cmd.exe' with elevated privileges (Run As Administrator)
2) Run the following command:
sc start SMADMINUI
LINUX:
1) Change to the AdminUI installation directory
cd /<AdminUI_Dir>/siteminder/adminui/bin
2) Start the JBoss Application server
standalone.sh
Additional Information
Feedback
