Portal fails to start while running the upgrade-profile task as a custom jar file is missing.
Following exception is logged in SystemOut.log during start up:
[4/29/13 10:21:21:686 CDT] 0000002e Authenticatio E com.ibm.wps.auth.impl.AuthenticationFilterChainHandlerImpl initializeChain EJPSD0028E: The filter com.mycompany.portal.filters.MyExplicitLogoutFilter could not be initialized due to error: java.lang.ClassNotFoundException
[4/29/13 10:21:21:705 CDT] 0000002e Servlet E com.ibm.wps.engine.Servlet init EJPFD0016E: Initialization of service failed.
com.ibm.wps.auth.exceptions.impl.FilterChainInitException: EJPSD0028E: The filter com.mycompany.portal.filters.MyExplicitLogoutFilter could not be initialized due to error: java.lang.ClassNotFoundException
If an application that is being migrated needs a custom jar file such as custom login/logout filter and if this has not been copied over to the config directory on the target portal.
Diagnosing the problem
Make sure if there are any custom jar files that are part of an application(s) that needs to be copied over to the target portal environment.
Resolving the problem
Copy any custom-shared library Java archive (JAR) files from both the <app_server_root>/lib and <portal_server_root>/shared/app from WebSphere Portal 6.1.0.x/7.x environment to
<wp_profile>/PortalServer/config directory of WebSphere Portal 8 environment.