Un-Deploying 5.7 J2EE Applications

On ALBPM 5.7 environments running on WebLogic or WebSphere you must first stop and un-install all ALBPM-related .EAR and .WAR applications.

This section only applies for the J2EE edition of ALBPM. If you are upgrading an ALBPM Standalone Edition environment then you should skip this section.
  1. Remove file fuegoj2ee-lib-all.jar from your J2EE environment. ALBPM 5.7 required this JAR file to be included in your WebLogic and WebSphere environments. You must now remove all references to it. Starting with ALBPM 6.0, this library file is no longer needed: all libraries are now included within each application archive.
  2. Login to your application server console, stop and un-install all ALBPM-related applications. Make sure you stop and un-install all applications, including:
    • Fuego J2EE Deployer.
    • Engine (You may have one or more Engine applications).
    • WorkSpace.
    • WorkSpace Administrator.
    • Archive Viewer.
    • ALBPM projects (you will have one enterprise application for each ALBPM project deployed).
  3. Stop your application server nodes. Make sure all your WebLogic or WebSphere servers where ALBPM 5.7 was running are completely stopped. This includes the administration server and all additional servers running any ALBPM component.
Parent topic: Migrating Enterprise Environment
Previous topic: Upgrade steps for ALBPM WE Environments
Next topic: Upgrade ALBPM 5.5 DB structures