Adding Content to the Portal |
If you have portlets that you no longer use, you can remove the configuration of those portlets. To register portlets, the SAS Information Delivery Portal copies the portlet deployment descriptor file, portlet.xml, from each portlet archive file (PAR) in the SAS-Configuration-Directory/Lev1/Web/Applications/SASPortlets4.3/Deployed directory to the sas.portal4.3.ear file.
To remove a proprietary SAS portlet configuration, follow these steps.
Undeploy the portal from the Web application server where it is running.
Remove your portlet's PAR file from the SAS-configuration-directory/Lev1/Web/Applications/SASPortlets4.3/Deployed directory.
Note: If you cannot remove the PAR file because it is locked, stop the Web application server that is running the portal. During the portlet registration process, the portal loads classes from the PAR files. As a result, the portal has a lock on all PAR files that it deploys. Some Web application servers require the server to be stopped in order to break that lock.
Follow the standard unconfiguration practices for your portlet and the Web application server. This task might include undeploying any Web application or other resource that supports your portlet.
To remove the portlet.xml file from the sas.portal4.3.ear file, use the Rebuild Web Applications option in the SAS Deployment Manager to rebuild the EAR file for the portal. See Rebuilding the SAS Web Applications.
In step 2, if you stopped the Web application server where the portal was deployed, restart the Web application server now.
Use the SAS Deployment Manager to redeploy the sas.portal4.3.ear file. See Redeploying the SAS Web Applications.
Copyright © 2010 by SAS Institute Inc., Cary, NC, USA. All rights reserved.