Some of the Oracle BPM applications need additional configuration changes before deploying
them into WebSphere.
-
Copy file
<ORABPM_HOME>/j2ee/websphere/was6stubs/fuegoj2ee-was6-stubs.jar
into each of following directories:
- <ORABPM_HOME>/webapps/archivingviewer/WEB-INF/lib
- <ORABPM_HOME>/webapps/feeds/WEB-INF/lib
- <ORABPM_HOME>/webapps/papiws/WEB-INF/lib
- <ORABPM_HOME>/webapps/portal/WEB-INF/lib
- <ORABPM_HOME>/webapps/portaladmin/WEB-INF/lib
- <ORABPM_HOME>/webapps/webconsole/WEB-INF/lib
- <ORABPM_HOME>/webapps/workspace/WEB-INF/lib
This is to allow client applications to connect with the EJB-based Process Engine running
on WebSphere.
- Create a new directory named jmxextensions under
<ORABPM_HOME>/webapps/webconsole/WEB-INF/.
-
Copy file
WEBSPHERE_HOME/AppServer/runtimes/com.ibm.ws.admin.client_6.1.0.jar
to the jmxextensions directory you just created on the previous
step: <ORABPM_HOME>/webapps/webconsole/WEB-INF/jmxextensions/.
This is to allow the Process Administrator application to connect with the
Process Engines via JMX.