javax.servlet.ServletException: Filter [FacesFilter]: could not be initialized
Recently I had a customer report this issue and after logging into the Websphere admin server and checking the parent first class loading and the MyFaces implementation for the castyles ear and the iam_im.ear, the only way I could get this error to disappear
##DISABLED_STATE to: IDMDisabled ##ADMIN_ROLE_CONSTRAINT to: IDMAdminRoles ##PASSWORD_HINT to: IDMForgottenQuestions ##PASSWORD_DATA to: IDMPasswordData ##IDENTITY_POLICY to: IDMIdentityPolicy
##SELF_SUBSCRIBING_FLAG to: IDMSelfSubscribing ##DYNAMIC_GROUP_MEMBERSHIP to: IDMDynamicGroupMembership ##NESTED_GROUP_MEMBERSHIP to: IDMNestedGroupMembership ##ADMIN_GROUP_ADMIN to: IDMAdminGroupAdmin
Anything that has a: <DataClassification name="sensitive"/> paste this below it: <DataClassification name="AttributeLevelEncrypt"/>
If you have not had the chance to visit this document yet, you should. It is a commonly asked question about active directory permissions and how to add exchange after you have already done the initial explore and correlate.
" We are experiencing slow response times on IDM tews services. We are unsure at the moment the source of the delay but the DBA's have indicated wait times at the IO level on IDM tables. My question, based on a DBA report, what is CA's stance on adding indexes to the tables for task persistence?"
The answer I gave was: There is certainly nothing wrong with adding indexes to the taskpersistence tables and in this case it help with not only garbage collection clean up, but also with the processing of everyday user requests. the reason that we do not have these added OOTB is because they are only needed and created on a case by case bases based on the customers environment.
In more recent versions of IM there are some indexes on tables and these indexes are managed by IM, however you, as the customer that owns the database can create more if you need more.
3) Then update the Account Container rules for the new Account Template created and also correct the required groups (I could verify that the Account Template copy also messes the Account Container rules):
We have IHS: (IBM HTTP server) and it is 32 bit, so we have to use the 32 bit siteminder protection agent. We want to have a 64 bit protection agent, so we would like to switch to IIS. IS this possible?
The answer is yes, it is possible.
In order to do this you will need to: Install the WAS plugin on IIS and test that with the Snoop.jsp (WebSphere OOTB sample)
Install the SM agent on IIS and test that with protecting a sample resource
For steps on installing agent on IIS please refer to Siteminder documentation
After the above WebSphere can be used to service requests from IIS The remaining steps are to update the IME to use the new agent.
Consider the reason that you use IHS though, it is easier to manage from the WAS console (stopping and starting the server) and can be run on linux or windows. IIS is only Windows.
Note: You are welcomed to try it on windows, but PLEASE AVOID TO USE IT IN A PRODUCTION ENVIRONMENT.
This simple tool - IMInfo tool, was designed for collecting diagnostic information from Identity Manager Server automatically.
It is easy to use: 1. Copy all its files to a Server with IMS installed and unzip it if they has been compressed to a single file. 2. Run "Cmd.exe" to open windows console. 3. Change current directory to IMInfo's, input "iminfo all" and Enter. (if you type "iminfo" without any parameter and enter, you will get some help info) 4. You will see prompt on console, saying something like "load class..; Collecting OS info..", The last line indicates full path and name of the output file. The output file will be a zip file named iminfo_MMDDYYYY_HHMMSS.zip, where MMDDYYY ... means the time that the output file created. 5. Unzip the output file, here should be a file named "iminfo_report.html". Double click to open it, everything the IMInfo tool collected is in the file.
Currently, this simple tool has been tested under following Environments 1. JDK1.4.2_13 + IM R12CR2 + JBoss 4.0.5 + MSSQL Server 2005 + Windows 2008 2. JDK1.5 + IM R12CR8 + JBoss4.2.3 + MSSQL Server 2005 + Windows 2003 3. JDK1.5 + IM R12.5 + WebLogic9 + MSSQL Server 2005 + Windows 2003
Therefore, it should working well with all IM R12+ release and most application servers (Except for WebSphere).
Since it use JDBC to connect to DB, it should support Oracle DB as well. But we haven't test it yet.
This tool is till in prototype state. Therefore it would be highly appreciate if you can send the output file to the developer's mail box firstname.lastname@example.org. And of course, feedback, issues.. are very desired.
Due to the message [JBAS013412: Timeout after  seconds waiting for service container stability.] it looks like a timeout issue , may be your application deployment/ other management operations taking longer than 300 seconds (300 sec is the default value). So try testing with a larger value to see if you still face the same issue or not?
You can try increasing this value to a higher value using the following system property: