Web Application Toolkit

This topic provides information related to the backward compatibility of custom applications built using the 3.5.x Web Application Toolkit. If you have already modified your 3.5.x applications to run in a 4.0.x environment, there are no additional modifications needed to run your applications in a 4.5 environment.

Upgrading Custom Applications to Web Application Toolkit Version 4.x

When using JAAS container-managed authentication, Workplace does not have access to full user credentials and therefore, does not generate user tokens since it has nothing to encrypt as the basis for the token. As a result, in situations where Workplace might expose an action that invokes some piece of UI hosted by, for example, IBM FileNet Records Manager (RM), and container-managed authentication is in use, the user will be presented with a second sign-in page when launching the RM-based action. To avoid the second sign-in page, the site must install and configure an SSO solution that offers JAAS support, such as CA/Netegrity SiteMinder.

NOTE As of IBM FileNet P8 4.0, an Application Integration client cannot participate in a JAAS-integrated SSO deployment. The client does not support integration to leverage SSO-authenticated user credentials in this type of deployment.

Upgrading Custom Applications to Access Workflows on a 4.x IBM FileNet P8 System

The following procedure shows you how to upgrade 3.5.x Toolkit-based applications to access workflows stored and processed on a 4.x Content Engine and Process Engine. The procedure does not require modification of custom code, and it applies to Workplace as well as custom Toolkit-based applications.

NOTE The 3.5.x Process applets, for example, Administrator and Designer, are not supported in the 4.x IBM FileNet P8 environment.

The procedure assumes that:

To update the 3.5.x Toolkit-based application

  1. Stop the 3.5.x application (custom or Workplace).
  2. From the 4.x Application Engine, copy the following JAR files in <app>/WEB-INF/lib to the corresponding directory in your 3.5.x Application Engine.
  3. In <app>/WEB-INF/WcmApiConfig.properties of the 3.5.x application, change the remote server settings to point to the 4.x Content Engine.
  4. Start the Toolkit-based application, and sign in as a user who is a member of the Application Engine Administrators group.
  5. Click Admin, then click Site Preferences.
  6. In the General preference view, scroll to the Tasks category.
  7. In the "Process Router - Host:port/name" option, change the "vmrouter" setting to the Process Engine Connection Point name.
  8. Apply your change.
  9. Restart the Application Engine.
  10. To verify that the upgrade works, go to the Tasks primary view. You should get a list of workflows from the IBM FileNet P8 4.x system.

Obsolete APIs

The APIs listed below, which were deprecated prior to release 4.0, are obsolete.

FormProcessor Class

WcmAuthoringDataProvider Class

WcmController Class

WcmCredentialsServlet Class

WcmDateUtil Class

WcmEProcessDataProvider Class

WcmException Class

WcmGetContentServlet Class

WcmIcons Class

WcmModule Class

WcmSearchDataProvider Class

WcmServerCredentials Class

WcmSignInPolicy Class

WcmSignInPolicyInterface Class

WcmSSLInfo Class

WcmString Class

WcmStringEditor Class

WcmStringResourceLoader Class

WcmStringResources Class

WcmXSLUtil Class