> Installation and Upgrade Guide > Upgrading AquaLogic BPM Workspace Extensions

Installation and Upgrade Guide

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Upgrading AquaLogic BPM Workspace Extensions

This chapter describes the procedures for upgrading ALBPM Workspace Extensions. The following table summarizes the upgrade procedure. No other upgrade paths are supported.

Table 0-1 Upgrade Paths
Upgrade Paths
Upgrade references
ALBPM Workspace Extension 5.7 MP2 to ALBPM Workspace Extensions 5.7 MP3
First, ensure that you have upgraded to ALBPM Workspace Extension MP2 using the procedures outlined in Upgrading to ALBPM Workspace Extensions 5.7 MP2.
Then, upgrade to ALBPM Workspace Extensions MP3 by following the procedures outlined in Upgrading to ALBPM Workspace Extensions 5.7 MP3.
ALBPM Workspace Extensions 5.7 to ALBPM Workspace Extensions 5.7 MP2
Follow the procedures in Upgrading to ALBPM Workspace Extensions 5.7 MP2.
ALIP 1.5 to ALBPM Workspace Extensions 5.7 MP2
First, upgrade to ALBPM Workspace Extensions 5.7 by following the procedures in Upgrading from ALIP 1.5 to ALBPM Workspace Extensions 5.7.
Then, upgrade to ALBPM Workspace Extensions 5.7 MP2 by following the procedures in Upgrading to ALBPM Workspace Extensions 5.7 MP2

Note: It is only possible to upgrade from ALIP 1.5 to ALBPM Enterprise Standalone and ALBPM Workspace Extensions 5.7 MP2.

 

Upgrading to ALBPM Workspace Extensions 5.7 MP3

This section describes how to upgrade from ALBPM Workspace Extensions 5.7 MP2 to 5.7 MP3. Before upgrading to 5.7 MP3, you should ensure that you have upgraded to 5.7 MP2. See Upgrading to ALBPM Workspace Extensions 5.7 MP2 for more information.

ALBPM WE 5.7 MP3 on ALBPM Enterprise Standalone

To upgrade ALBPM Workspace Extensions 5.7 MP3:

Note: In the following procedures INSTALL_DIR is the path to the ALBPM 5.7 Enterprise Standalone installation. For example, d:/bea/albpm5.7/enterprise.
  1. Download ALBPM WE 5.7 MP3 from the following location:
    2. http://commerce.bea.com/showproduct.jsp?family=ALBPMWSEXT&major=5.7&minor=3
  2. Expand ALBPMWorkspaceExtensions_5-7_MP3_<platform>.zip.

    3. This file contains the following .zip files which are used to upgrade your ALBPM installation:

    • MaintenancePack.zip
    • ImageServerMaintenancePack.zip
      • Note: You do not need to run the installer to perform the upgrade to 5.7 MP3.
  3. Stop the process execution engine using the ALBPM Process Administrator
  4. Stop the BPM Application Server using the ALBPM Admin Center.
  5. Upgrade ALBPM 5.7 SP1 to ALBPM 5.7 MP2. For details, see the Installation and Upgrade Guide for AquaLogic BPM 5.7.
  6. Create a backup of the following directories:
    7. <INSTALL_DIR>/webapps
    <INSTALL_DIR>/j2ee
    <ALUI_INSTALL_DIR>/ptimages/imageserver/plumtree/process/public/css/
  7. Expand MaintenancePack.zip into the INSTALL_DIR directory.

    8. The following files are updated in your ALBPM installation: 

    <INSTALL_DIR>/webapps/portal/ptjsp/audittrail.jsf
    <INSTALL_DIR>/webapps/portal/ptjsp/detail-js.jsff
    <INSTALL_DIR>/webapps/portal/ptjsp/detail-tasks.jsff
    <INSTALL_DIR>/webapps/portal/ptjsp/reassign.jsf
    <INSTALL_DIR>/webapps/portal/ptjsp/workitems.jsff
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_de.properties
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_en.properties
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_es.properties
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_fr.properties
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_it.properties
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_ja.properties
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_ko.properties
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_nl.properties
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_pt.properties
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_zh.properties
    <INSTALL_DIR>/webapps/portal/ptjsp/executiondispatcher/closeWindow.jsp
    <INSTALL_DIR>/webapps/portal/ptjsp/attachments/attachment-edit.jsf
    <INSTALL_DIR>/webapps/portal/WEB-INF/server-config.wsdd
    <INSTALL_DIR>/webapps/portal/WEB-INF/lib/ptprocessserver.jar
    <INSTALL_DIR>/j2ee/common/templates/portal/base/WEB-INF/web.xml
    Note: If you have made changes to your installation that required updating any of the above files, you may have to manually merge these files to retain your configuration changes.
  8. Copy the ptprocessserver.jar file you just installed from:
    9. <INSTALL_DIR>/webapps/portal/WEB-INF/lib/ptprocessserver.jar

    to:

    <INSTALL_DIR>/webapps/webconsole/WEB-INF/lib/ptprocessserver.jar

  9. Expand ImageServerMaintenancePack.zip into your ALUI home directory.

    10. The following file is updated: 

    <ALUI_INSTALL_DIR>/ptimages/imageserver/plumtree/process/public/css/
    work-portal.css
  10. Delete the contents of the Tomcat work directory located at:
    11. <INSTALL_DIR>/enterprise/tomcat/work/

    This removes any files cached by the Tomcat web server.

  11. Restart the BPM Application Server using the Admin Center.

ALBPM WE 5.7 MP3 on ALBPM Enterprise WebLogic or WebSphere

To upgrade ALBPM Workspace Extensions 5.7 MP3:

Note: In the following procedures INSTALL_DIR is the path to the ALBPM 5.7 Enterprise installation for you application server. If you are using BEA WebLogic Server, for example, the default installation directory is c:/bea/albpm5.7/j2eewl. For WebSphere Application Server, the default installation directory is: c:/bea/albpm5.7/j2eewl.
  1. Download ALBPM WE 5.7 MP3 from the following location:
    2. http://commerce.bea.com/showproduct.jsp?family=ALBPMWSEXT&major=5.7&minor=3
  2. Expand ALBPMWorkspaceExtensions_5-7_MP3_<platform>.zip.

    3. This file contains the following .zip files which are used to upgrade your ALBPM installation:

    • MaintenancePack.zip
    • ImageServerMaintenancePack.zip
      • Note: You do not need to run the installer to upgrade to 5.7 MP3.
  3. Stop the process execution engine using the ALBPM Process Administrator
  4. Stop the BPM Application Server using the ALBPM Admin Center.
  5. Upgrade ALBPM 5.7 SP1 to ALBPM 5.7 MP2. For details, see the Installation and Upgrade Guide for AquaLogic BPM 5.7.
  6. Stop your application server.
  7. Remove generated JSP files:
    1. Remove all directories in <INSTALL_DIR>/tomcat/work/Catalina/localhost.
    2. Follow your application server's documentation for finding the directory for generated JSP files and delete that directory.
    3. Remove all files in <INSTALL_DIR>/<j2ee_version>/cache.
  8. Create a backup of the following directories:
    9. <INSTALL_DIR>/webapps
    <INSTALL_DIR>/j2ee
    <ALUI_INSTALL_DIR>/process/public/css
  9. Expand MaintenancePack.zip into the %PT_HOME/albpm5.7/<j2ee_version> directory.

    10. The following files are updated in your ALBPM installation: 

    <INSTALL_DIR>/webapps/portal/ptjsp/audittrail.jsf
    <INSTALL_DIR>/webapps/portal/ptjsp/detail-js.jsff
    <INSTALL_DIR>/webapps/portal/ptjsp/detail-tasks.jsff
    <INSTALL_DIR>/webapps/portal/ptjsp/reassign.jsf
    <INSTALL_DIR>/webapps/portal/ptjsp/workitems.jsff
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_de.properties
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_en.properties
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_es.properties
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_fr.properties
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_it.properties
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_ja.properties
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_ko.properties
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_nl.properties
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_pt.properties
    <INSTALL_DIR>/webapps/portal/WEB-INF/classes/messages_zh.properties
    <INSTALL_DIR>/webapps/portal/ptjsp/executiondispatcher/closeWindow.jsp
    <INSTALL_DIR>/webapps/portal/ptjsp/attachments/attachment-edit.jsf
    <INSTALL_DIR>/webapps/portal/WEB-INF/server-config.wsdd
    <INSTALL_DIR>/webapps/portal/WEB-INF/lib/ptprocessserver.jar
    <INSTALL_DIR>/j2ee/common/templates/portal/base/WEB-INF/web.xml
    Note: If you have made changes to you installation that required updating any of the above files, you may have to manually merge these files to retain your configuration changes.
  10. Copy the ptprocessserver.jar file you just installed from:
    11. <INSTALL_DIR>/webapps/portal/WEB-INF/lib/ptprocessserver.jar

    to:

    <INSTALL_DIR>/webapps/webconsole/WEB-INF/lib/ptprocessserver.jar

  11. Expand ImageServerMaintenancePack.zip into your ALUI home directory.

    12. The following file is updated: 

    <ALUI_INSTALL_DIR>/ptimages/imageserver/plumtree/process/public/css/
    work-portal.css
  12. Configure shared libraries. For details, see Configuring WebLogic and WebSphere with ALBPM Workspace Extensions Shared Libraries.
  13. Regenerate the WorkSpace EAR:
    1. In the ALI Portal, go to Administration and open the Process Administrator.
    2. On the Engines page, click the engine name.
    3. On the Engines | Edit Engines page, click J2EE Application Server Files (EARs, WARs).
    4. Next to BEA AquaLogic BPM WorkSpace WAR, click the Create WAR and EAR icon.
    5. To the right of the generated WorkSpace EAR file, click the Re-Install WorkSpace EAR in the Application Engine icon.
  14. In the ALBPM Admin Center, start the BPM Application Server.
  15. In the ALBPM Process Administrator, start the Process Execution Engine.
  16. Restart the BPM Application Server using the Admin Center.

 

Upgrading to ALBPM Workspace Extensions 5.7 MP2

This section describes how to upgrade from ALBPM Workspace Extensions 5.7 to 5.7 MP2. To upgrade from ALIP 1.5, first follow the instructions to upgrade to ALBPM Workspace Extensions 5.7, then follow these instructions to install MP2.

ALBPM WE on ALBPM Enterprise Standalone

To upgrade to ALBPM Workspace Extensions 5.7 MP2:

  1. In the ALBPM Process Administrator, stop the process execution engine.
  2. In the ALBPM Admin Center, stop the BPM Application Server.
  3. Upgrade ALBPM 5.7 SP1 to ALBPM 5.7 MP2. For details, see the Installation and Upgrade Guide for AquaLogic BPM 5.7.
  4. Remove generated JSP files by removing all directories in:
    1. <INSTALL_DIR>/tomcat/work/Catalina/localhost
    2. <INSTALL_DIR>/cache
  5. In the <INSTALL_DIR>/webapps/portal/WEB-INF directory, rename processreport-faces-config.xml to processreport-faces-config.xml.albpm57.
  6. Copy processreport-faces-config.xml from the webapps/portal/WEB-INF directory of the maintenance pack to <INSTALL_DIR>/webapps/portal/WEB-INF.
  7. Delete html_basic.tld from <INSTALL_DIR>/webapps/portal/WEB-INF/lib.
  8. Rename the following files in <INSTALL_DIR>/webapps/portal/WEB-INF:
    1. processreport-faces-config.xml to process-faces-config.xml.albpm57
    2. server-config.wsdd to server-config.wsdd.albpm57
    3. web.xml to web.xml.albpm57
  9. Copy processreport-faces-config.xml, web.xml, and server-config.wsdd from the webapps/portal/WEB-INF directory of the maintenance pack to <INSTALL_DIR>/webapps/portal/WEB-INF
  10. Rename the following file in <INSTALL_DIR>/webapps/portal/WEB-INF/lib:
    1. ptprocessserver.jar to ptprocessserver.jar.albpm57
  11. Copy commons-httpclient-3.0.1.jar and ptprocessserver.jar in the webapps/portal/WEB-INF/lib directory of the maintenance pack to <INSTALL_DIR>/webapps/portal/WEB-INF/lib.
  12. Make changes to axis.jar in <INSTALL_DIR>/webapps/portal/WEB-INF/lib:
    1. Make a copy of axis.jar.albpm57 and rename it to axis.jar
    2. Open axis.jar in WinZip.
    3. Extract client-config.wsdd to the root directory. Keep the directory structure, namely org/apache/axis/client. If you use the WinZip default option of "Use folder names", this should create the directory structure. Make sure that there is not already an existing "org" folder in the root directory. Make sure that the extracted file is writable.
    4. Open client-config.wsdd in a text editor and replace this element:

      5. <transport name="http" pivot="java:org.apache.axis.transport.http.HTTPSender"/>

      with

      <transport name="http" pivot="java:org.apache.axis.transport.http.CommonsHTTPSender"/>

      Save and close the file.

    5. Drag the "org" folder on top of the open WinZip window and click "Add".
    6. Close WinZip.
  13. In the <INSTALL_DIR>/webapps/portal/ptjsp directory, rename the following files:
    1. detail.jsff to detail-jsff.albpm57
    2. detail-attachments.jsff to detail-attachments.jsff.albpm57
    3. detail-knowledgebase.jsff to detail-knowledgebase.jsff.albpm57
    4. detail-notes.jsff to detail-notes.jsff.albpm57
    5. detail-standalone.jsff to detail-standalone.jsff.albpm57
    6. detail-tabs.jsff to detail-tabs.jsff.albpm57
    7. navigation-portlet.jsf to navigation-portlet.jsf.albpm57
    8. workitems.jsff to workitems.jsff.albpm57
    9. worklist-portlet.jsf to worklist-portlet.jsf.albpm57
  14. Copy the following files from the webapps/portal/ptjsp directory of the maintenance pack to <INSTALL_DIR>/webapps/portal/ptjsp:
    1. detail.jsff
    2. detail-attachments.jsff
    3. detail-knowledgebase.jsff
    4. detail-notes.jsff
    5. detail-standalone.jsff
    6. detail-tabs.jsff
    7. navigation-portlet.jsf
    8. workitems.jsff
    9. worklist-portlet.jsf
  15. In the <INSTALL_DIR>/webapps/portal/ptjsp/executiondispatcher directory, rename closeWindow.jsp to closeWindow.jsp.albpm57.
  16. Copy closeWindow.jsp from the webapps/portal /ptjsp/executiondispatcher directory of the maintenance pack to <INSTALL_DIR>/webapps/portal/ptjsp/executiondispatcher
  17. In the <INSTALL_DIR>/webapps/portal/ptjsp/processreport directory, rename processreport.jsf to processreport.jsf.albpm57.
  18. Copy processreport-jsf, processreport.jsff, and processreport-refresh.jsf from the webapps/portal/ptjsp/processreport directory of the maintenance pack to <INSTALL_DIR>/webapps/portal/ptjsp/processreport.
  19. In the <INSTALL_DIR>/webapps/webconsole/ptjsp/console directory, rename chooseproject.jsp to chooseproject.jsp.albpm57.
  20. Copy chooseproject.jsp from the webapps/webconsole /ptjsp/console directory of the maintenance pack to <INSTALL_DIR>/webapps/webconsole/ptjsp/console
  21. In the <INSTALL_DIR>/webapps/webconsole/ptjsp/attachments directory, rename attachment-edit.jsf to attachment-edit.jsf.albpm57.
  22. Copy attachment-edit.jsf from the webapps/webconsole /ptjsp/attachments directory of the maintenance pack to <INSTALL_DIR>/webapps/webconsole/ptjsp/attachments
  23. In the ALBPM Admin Center, start the BPM Application Server.
  24. In the ALBPM Process Administrator, start the process execution engine.

ALBPM WE on ALBPM Enterprise WebLogic or WebSphere

To upgrade to ALBPM Workspace Extensions 5.7 MP2:

  1. In the ALBPM Process Administrator, stop the process execution engine.
  2. In the ALBPM Admin Center, stop the BPM Application Server.
  3. Stop the WebLogic or WebSphere application server.
  4. Upgrade ALBPM 5.7 SP1 to ALBPM 5.7 MP2. For details, see the Installation and Upgrade Guide for AquaLogic BPM 5.7.
  5. Remove generated JSP files:
    1. Remove all directories in <INSTALL_DIR>/tomcat/work/Catalina/localhost
    2. Follow your application server's documentation for finding the directory for generated JSP files and delete that directory.
    3. Remote all files in <INSTALL_DIR>/cache
  6. Delete html_basic.tld from <INSTALL_DIR>/webapps/portal/WEB-INF/lib.
  7. Rename the following files in <INSTALL_DIR>/webapps/portal/WEB-INF:
    1. processreport-faces-config.xml to process-faces-config.xml.albpm57
    2. server-config.wsdd to server-config.wsdd.albpm57
    3. web.xml to web.xml.albpm57
  8. Copy processreport-faces-config.xml, web.xml, and server-config.wsdd from the webapps/portal/WEB-INF directory of the maintenance pack to <INSTALL_DIR>/webapps/portal/WEB-INF
  9. Rename web.xml in <INSTALL_DIR>/j2ee/common/templates/portal/base/WEB-INF to web.xml.albpm57.
  10. Copy web.xml from the j2ee/common/templates/portal/base/WEB-INF directory of the maintenance pack to <INSTALL_DIR//j2ee/common/templates/portal/base/WEB-INF
  11. Rename the following files in the <INSTALL_DIR>/webapps/portal/WEB-INF/lib:
    1. axis.jar to axis.jar.albpm57
    2. ptprocessserver.jar to ptprocessserver.jar.albpm57
  12. Copy commons-httpclient-3.0.1.jar and ptprocessserver.jar in the webapps/portal/WEB-INF/lib directory of the maintenance pack to <INSTALL_DIR>/webapps/portal/WEB-INF/lib.
  13. Make changes to axis.jar in <INSTALL_DIR>/webapps/portal/WEB-INF/lib:
    1. Make a copy of axis.jar and rename it to axis.jar.abpm57.
    2. Open axis.jar in WinZip.
    3. Extract client-config.wsdd to the root directory. Keep the directory structure, namely org/apache/axis/client. If you use the WinZip default option of "Use folder names", this should create the directory structure. Make sure that there is not already an existing "org" folder in the root directory. Make sure that the extracted file is writable.
    4. Open client-config.wsdd in a text editor and replace this element:

      5. <transport name="http" pivot="java:org.apache.axis.transport.http.HTTPSender"/>

      with

      <transport name="http" pivot="java:org.apache.axis.transport.http.CommonsHTTPSender"/>

      Save and close the file.

    5. Drag the "org" folder on top of the open WinZip window and click "Add".
    6. Close WinZip.
  14. Make changes to fuegoj2ee-lib-all.jar in <INSTALL_DIR>/j2ee/common/lib:
    1. Make a copy of fuegoj2ee-lib-all.jar and rename it to fuegoj2ee-lib-all.jar.albpm57.
    2. Open fuegoj2ee-lib-all.jar in WinZip.
    3. Extract org/apache/axis/client/client-config.wsdd to the root directory. Keep the directory structure, namely org/apache/axis/client. If you use the WinZip default option of "Use folder names", this should create the directory structure. Make sure that there is not already an existing "org" folder in the root directory. Make sure that the extracted file is writable.
    4. Open client-config.wsdd in a text editor and replace this element:

      5. <transport name="http" pivot="java:org.apache.axis.transport.http.HTTPSender"/>

      with

      <transport name="http" pivot="java:org.apache.axis.transport.http.CommonsHTTPSender"/>

      Save and close the file.

    5. Drag the "org" folder on top of the open WinZip window and click "Add".
    6. Close WinZip.
  15. In the <INSTALL_DIR>/webapps/portal/ptjsp directory, rename the following files:
    1. detail.jsff to detail-jsff.albpm57
    2. detail-attachments.jsff to detail-attachments.jsff.albpm57
    3. detail-knowledgebase.jsff to detail-knowledgebase.jsff.albpm57
    4. detail-notes.jsff to detail-notes.jsff.albpm57
    5. detail-standalone.jsff to detail-standalone.jsff.albpm57
    6. detail-tabs.jsff to detail-tabs.jsff.albpm57
    7. navigation-portlet.jsf to navigation-portlet.jsf.albpm57
    8. workitems.jsff to workitems.jsff.albpm57
    9. worklist-portlet.jsf to worklist-portlet.jsf.albpm57
  16. Copy the following files from the webapps/portal/ptjsp directory of the maintenance pack to <INSTALL_DIR>/webapps/portal/ptjsp:
    1. detail.jsff
    2. detail-attachments.jsff
    3. detail-knowledgebase.jsff
    4. detail-notes.jsff
    5. detail-standalone.jsff
    6. detail-tabs.jsff
    7. navigation-portlet.jsf
    8. workitems.jsff
    9. worklist-portlet.jsf
  17. In the <INSTALL_DIR>/webapps/portal/ptjsp/executiondispatcher directory, rename closeWindow.jsp to closeWindow.jsp.albpm57.
  18. Copy closeWindow.jsp from the webapps/portal /ptjsp/executiondispatcher directory of the maintenance pack to <INSTALL_DIR>/webapps/portal/ptjsp/executiondispatcher
  19. In the <INSTALL_DIR>/webapps/portal/ptjsp/processreport directory, rename processreport.jsf to processreport.jsf.albpm57.
  20. Copy processreport-jsf, processreport.jsff, and processreport-refresh.jsf from the webapps/portal/ptjsp/processreport directory of the maintenance pack to <INSTALL_DIR>/webapps/portal/ptjsp/processreport.
  21. In the <INSTALL_DIR>/webapps/webconsole/ptjsp/attachments directory, rename attachment-edit.jsf to attachment-edit.jsf.albpm57.
  22. Copy attachment-edit.jsf from the webapps/webconsole /ptjsp/attachments directory of the maintenance pack to <INSTALL_DIR>/webapps/webconsole/ptjsp/attachments.
  23. In the <INSTALL_DIR>/webapps/webconsole/ptjsp/console directory, rename chooseproject.jsp to chooseproject.jsp.albpm57.
  24. Copy chooseproject.jsp from the webapps/webconsole /ptjsp/console directory of the maintenance pack to <INSTALL_DIR>/webapps/webconsole/ptjsp/console
  25. Configure shared libraries. For details, see Configuring WebLogic and WebSphere with ALBPM Workspace Extensions Shared Libraries.
  26. Regenerate the WorkSpace EAR:
    1. In the ALI Portal, go to Administration and open the Process Administrator.
    2. On the Engines page, click the engine name.
    3. On the Engines | Edit Engines page, click J2EE Application Server Files (EARs, WARs).
    4. Next to BEA AquaLogic BPM WorkSpace WAR, click the Create WAR and EAR icon.
    5. To the right of the generated WorkSpace EAR file, click the Re-Install WorkSpace EAR in the Application Engine icon.
  27. In the ALBPM Admin Center, start the BPM Application Server.
  28. In the ALBPM Process Administrator, start the process execution engine.

 

Upgrading to ALBPM Workspace Extensions from 5.7 MP1

 

Upgrading from ALIP 1.5 to ALBPM Workspace Extensions 5.7

To upgrade to ALBPM Workspace Extensions 5.7 from ALIP 1.5:

  1. Install AquaLogic BPM 5.7 SP1 and ALBPM Workspace Extensions 5.7. For details, see Installation or Installing AquaLogic BPM Workspace Extensions.
  2. For an Oracle database, run the following scripts in order:
    1. Against the directory database:
      2. <INSTALL_DIR>/alui/ptprocess/1.7/sql/<DB>/upgrade_directorydb_5.5.8_to_5.5.11.sql
    2. Upgrade the AquaLogic BPM database by following the instructions in the Upgrade chapter of the Installation Guide for AquaLogic BPM
    3. Against the directory database:
      4. <INSTALL_DIR>/alui/ptprocess/1.7/sql/<DB>/upgrade_directorydb_5.5_to_5.7.sql
      Note: This script requires manual editing. Change the value of YOUR_JDBC_USER* to the name of the directory schema name appended by an *. For example, if the oracle schema name is fdi_production, replace YOUR_JDBC_USER* with fdi_production*.
    4. Against the process database:
      5. <INSTALL_DIR>/alui/ptprocess/1.7/sql/<DB>/upgrade_processdb_1.5_to1.7.sql
  3. For a SQL Server database, run the following scripts in order:
    1. Against the directory database:
      2. <INSTALL_DIR>/alui/ptprocess/1.7/sql/mssql/upgrade_directorydb_5.5.8_to_5.5.11.sql
    2. Against the directory database:
      3. <INSTALL_DIR>/alui/ptprocess/1.7/sql/mssql/upgrade_directorydb_5.5_to_5.7.sql
      Note: This script requires manual editing. Change the value of YOUR_JDBC_USER* to the name of the directory schema name appended by an *. For example, if the oracle schema name is fdi_production, replace YOUR_JDBC_USER* with fdi_production*.
    3. Against the process database:
      4. <INSTALL_DIR>/alui/ptprocess/1.7/sql/mssql/upgrade_processdb_1.5_to1.7.sql
  4. Configure a directory service to use the existing directory service database.
    1. From the AquaLogic BPM Administration Console, click Configuration.
    2. To add a directory service, click Add...
    3. Select Use Existing Directory. Click OK.
    4. Enter a name for the directory service in the Directory ID field.
    5. For Provider choose either Oracle (ALI) or SQLServer (ALI).
      6. Caution: Do not use any of the other JDBC providers.
    6. Complete the directory service settings based on your existing database and ALI portal installation. For a description of directory service settings, see Configuring an ALBPM Workspace Extensions Directory Service.
    7. Verify the directory service. From the Configuration page, click Check.

  Back to Top       Previous  Next