You can choose to deploy your additional application instance
as an EAR file. You must perform the additional configuration for
each custom Workplace instance
you plan to deploy.
Procedure
- Modify the application.xml file located
in the copied deploy directories, as follows:
- Open each instance of the application.xml file,
for example, install_path/FileNet/AE/deploy1/META-INF/application.xml.
- Change the <display-name> and the <context-root>
elements to your custom name, for example, Workplace1.
<display-name>Workplace1</display-name>
<description>FileNet Application Engine</description>
<module>
<web>
<web-uri>app_engine.war</web-uri>
<context-root>Workplace1</context-root>
</web>
</module>
- In the create_app_engine_war file,
set the install home and deploy directory to match your custom names.
For example, you would make the following changes:
install_home="/opt/FileNet/AE/Workplace1"
"${install_home}/../_AEjvm/bin/jar" -cf "${install_home}/../
deploy1/app_engine.war"*
- In the create_app_engine_ear file,
set the install home, deploy directory, and EAR file to match your
custom names.
For example, you would make the following
changes:
install_home="/opt/FileNet/AE/Workplace1"
cd "${install_home}/../deploy1"
"${install_home}/../_AEjvm/bin/jar" -cvf "${install_home}/../
deploy1/app_engine1.ear" META-INF *.war
- Delete the existing app_engine.war and app_engine.ear files.
- Create your custom WAR and EAR files by running the create_app_engine_war and
then the create_app_engine_ear files.
- Deploy the EAR file for each custom Workplace instance according to
the procedures for your application server type.
- Install any service packs, fix packs, or interim fixes
required. To determine whether such additional software updates are
needed, access the IBM®
FileNet® P8 Platform support
site.