You must install Oracle WebLogic 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 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 WebLogic 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 for
passing session information between Application Engine or Workplace XT and the client browser.
- Create a WebLogic Server domain
before installing and deploying Application Engine or Workplace XT. Refer to
your WebLogic Server documentation
for detailed instructions.
Important: You will perform
further configuration on Workplace XT after
you perform the installation.
- Enable trust between the Content Platform Engine WebLogic
domain and the Application Engine or Workplace XT WebLogic domain. If you have already configured a trust on the Content Platform Engine, perform
these steps only on the Application Engine or Workplace XT server.
- Prepare the WebLogic Administration Console for editing.
- In the advanced security settings for your domain, enter
the same password for both the Content Platform Engine domain
and the Application Engine or Workplace XT domain.
- Save and activate your changes.
- Restart the server if needed.
- Repeat this procedure in each domain for which you want
to enable trust.
Important: If you are enabling
this feature in a managed server environment, you must stop the Administration
server and all the Managed Servers in both domains and then restart
them. If this step is not performed, servers that were not rebooted
will not trust the servers that were rebooted. Refer to your WebLogic Server documentation for more
information.