You must install WebSphere® Application
Server on
the machine where you are going to install and deploy Application Engine or Workplace XT.
About this task
Application Engine or Workplace XT can be collocated with Content Platform Engine as long as the server
is appropriately sized. However, each instance of the Application Engine or Workplace XT and each instance of
the Content Platform Engine must run
in its own JVM. For assistance in sizing your system, access the IBM®
FileNet® P8 Platform support site.
Procedure
To configure WebSphere Application
Server:
- Verify that the application server is set to use JSESSIONID
as the default cookie name. To avoid forcing end users
to log in individually to applets such as Process Designer, Search
Designer, and Process Simulator,
configure the application server to use JSESSIONID as cookie name,
and not use application-unique cookie names. Using JSESSIONID is typically
the default setting for the supported application servers. Both Application Engine and Workplace XT use cookie names to pass
session information between Application Engine or Workplace XT and the client browser.
- Determine the Initial and Maximum Heap Size. Refer
to your application server vendor's recommendation for Initial and
Maximum heap size values. You will use this information when you configure WebSphere Application
Server after you install Application Engine or Workplace XT.
- When WebSphere is
running as a service and a UNC path is specified in web.xml for
configuration, upload, and download directories, the account that
is specified to run the WebSphere service
must have permissions to the share of the UNC path.