Updating Enterprise

Follow this procedure to apply Maintenance Packs or Hotfixes to ALBPM Enterprise.

You perform the Enterprise update procedure from Admin Center.

Before updating Enterprise, check which version and edition you currently have. On the upper right corner of the main window, click About.

To update Enterprise:

Using a Web browser, download the update file from the BEA Downloads page, and save it to a local drive. Once downloaded, verify that the file has a .upd extension.
You cannot update Enterprise while BPM Web Applications are running. If the BPM Web Applications are running, click Stop BPM Web Applications ().
Note: If any process execution engines are running, you must also stop them in order to perform the upgrade. First stop the engines from Process Administrator, and then stop the Web Applications from Admin Center.
Note: If the updater service is running, you must also stop this service. In the Windows Services console, this is called the ALBPM 6.0 DatawareHouse Service. In UNIX you must execute the following:
```
$ALBPM_HOME/bin$ ./albpmwarehouse.sh stop
```
Where ALBPM_HOME is the folder where Enterprise is located.
In the Admin Center main window, click Configuration (). The Configuration dialog box will appear.
Click the rightmost tab, Service Pack Updates. You may need to click on the right arrow button so this tab comes into view.
Click Local Update. If this button is disabled, you need to stop the BPM Web Applications. The Open dialog box is displayed.
Specify the update (.upd) file you downloaded in step 1, and click Open. The update process will execute, and Admin Center will automatically restart for the update to take effect.
If you have chosen to deploy ALBPM to an application server, the Engine, WorkSpace and other deployed ALBPM J2EE applications will need to be re-generated and re-deployed to the application server container.
This is needed since these ALBPM applications use libraries that may have been patched on the installed Hotfix or Maintenance Pack.

You can automate the generation of the ALBPM Application archives using ALBPM Ant Tasks scripts.

Follow this procedure to generate the ALBPM application archives manually:
1. Login to ALBPM Process Administrator. By default, it runs on http://host:8686/webconsole.
2. Click on Engines and then click on the name of your J2EE ALBPM Engine. You should see the configuration properties for your Engine.
3. Click on the Basic Configuration tab and then on J2EE Application Server Files.
  This page allows you to (re)create the .ear files of those ALBPM applications associated with this Engine.
  
  Note: When you access this page, the Process Administrator gets the status of each of the applications by contacting ALBPM Deployer. You will get a warning message at the bottom of the page if there was any problem contacting ALBPM Deployer. If this is the case, make sure the BPM Application Deployer URL (within the Application Server tab) is correct and that ALBPM Deployer is up and running on your J2EE server.
4. Click on the "new" icon () next to each of the applications you want to install.
5. Click on the "install" icon () next to each of the applications you want to install.
  Attention: This may take several minutes. Do not click any link on the page and do back in your browser until the page is automatically reloaded. When you click on the icon, ALBPM Process Administrator transfers the file over to the J2EE server (by means of ALBPM Deployer) and the server goes through the application installation process.

Once the update is complete, you may have to perform additional steps, particularly if you have deployed to an application server. These steps will be described in the Release Notes.