Remove a WebSphere Application Server Profile on AIX

WebSphere Application ServerThere may be times when you need to remove a WebSphere deployment manager, node, or application server profile. I have successfully used the following steps in versions 7 and 8 of WebSphere.

  • Stop the deployment managers, nodes, or application servers that are associated with the profile that you want to remove
  • List all profiles on a server:
    [was_install_dir]/bin/manageprofiles.sh –listProfiles
  • Remove a WebSphere Application Server profile:
    [was_install_dir]/bin/manageprofiles.sh –delete –profileName profile
  • Ensure that references to the deleted profile are removed from the profile registry:
    [was_install_dir]/bin/manageprofiles.sh –validateAndUpdateRegistry
  • Delete the profile directory tree (if it was not deleted by the previous action):
    [was_install_dir]/profiles/rm -r profile
Email this to someoneTweet about this on TwitterShare on LinkedInPin on PinterestShare on Google+Share on FacebookPrint this page

Fix for a [SanitizingRequestFilter] error in the SAS Information Delivery Portal

saslogo.gifI recently deployed the SAS Enterprise Business Intelligence Server on a brand-new AIX LPAR.  During my validation of the platform, I created a new stored process portlet and added it to my home page.  My test portlet then displayed the following error:

Error 500: javax.servlet.ServletException: Filter [SanitizingRequestFilter]: could not be initialized.

Here’s how it looked in the portlet:

9-24-2014 6.43.16 AM

I searched for the error at support.sas.com and found a Problem Note about an error very similar to mine.  This error can arise when SAS BI portlets (the stored process portlet is one of these) are deployed to a WebSphere application server.  During the configuration phase of my deployment, I specified that SAS should automatically deploy the web applications to WebSphere.  Configuration did complete successfully, creating two WebSphere profiles and an application server (SASServer1), and deploying all of the web applications.  An important file for the SAS BI portlets (sas.portlet.container.runtime.extensions.jar) did not get copied to WebSphere, however, and required manual intervention.

The fix is easy enough:

  1. Stop the SASServer1 application server
  2. Using the SAS installer account, copy the sas.portlet.container.runtime.extensions.jar file from the [SASCONFIG-DIR]/Lev1/Web/Staging/Exploded/sas.biportlets4.X.ear/lib directory to the [WEBSPHERE-HOME]/lib directory of the IBM WebSphere Application Server
  3. Start SASServer1

I logged back in to the Information Delivery Portal and my stored process portlet was happy and ready for a stored process:
A happy stored process portlet
Here are a couple of notes from the Problem Note:

  • These manual steps are required because of a limitation in the WebSphere application server
  • In UNIX operating environments, the JAR file must be copied using the same account that is used to install the WebSphere application server

SAS also provided a more time consuming fix which fixes the issue in the Problem Note if someone preferred to use the WebSphere Integrated Solutions Console.

I have run into this issue in versions,, and of WebSphere.  I am running SAS EBI 9.3 Maintenance Release 2 with BI portlets 4.3.  I would also like to note that the steps I listed above were also included in the Instructions.html document located at [SASCONFIG-DIR]/Lev1/Documents directory in my environment.  It is created after a successful installation and configuration of the EBI environment.

Email this to someoneTweet about this on TwitterShare on LinkedInPin on PinterestShare on Google+Share on FacebookPrint this page

Locating the Log Files for the SAS 9.3 Middle Tier

SASI have been doing some maintenance recently on one of our SAS EBI installations and needed to review the logs generated by the middle tier.  At some point any BI administrator will have to do this, so here are the default locations, directly from SAS:

The log files for the SAS 9.3 middle tier are located in the following directories:

Application Servers

Red Hat JBoss

  • /JBoss-home-directory/server/SAS-JBoss-server/log/server.log
  • /JBoss-home-directory/server/SAS-JBoss-server/log/boot.log

Oracle WebLogic

  • If WebLogic is started as a service, a UNIX daemon, or a batch process, the location is
  • If WebLogic is started using the Node Manager, the location is

IBM WebSphere

  • /WebSphere-home-directory/AppServer/logs/server/SystemOut.log
  • /WebSphere-home-directory/AppServer/logs/server/SystemErr.log

WebDAV Server

  • SAS Content Server:

SAS Web Applications

  • SAS Admin:
  • SAS BI Dashboard:
  • SAS BI Portlets:
  • SAS BI Web Services:
  • SAS Information Delivery Portal:
  • SAS Logon Manager:
  • SAS Package Viewer:
  • SAS Preferences:
  • SAS Remote Services:
  • SAS Shared Apps:
  • SAS Stored Processes Web Application:
  • SAS Web Report Studio:
    Note: Beginning with the second maintenance release for SAS 9.3 (TS1M2), the log is named SASWebReportStudio.log
  • SAS Web Infrastructure Platform Client Access:
  • SAS Web Infrastructure Platform Services:
  • SAS Web Infrastructure Platform SOAP Services:
  • SAS Workflow Services:

In my case, I was looking for my Websphere application server logs.  And as I should have suspected, my System Admin did not have the application servers or the log directories installed in the typical locations, so I had to do a little hunting.

Email this to someoneTweet about this on TwitterShare on LinkedInPin on PinterestShare on Google+Share on FacebookPrint this page

© 2017 Technoleros

Theme by Anders NorénUp ↑