IBM BPM, V8.0.1, All platforms > Installing, deploying, and undeploying applications in the runtime environment
Installing process application snapshots
When install a process application snapshot to a process server, the library items for that snapshot (including toolkit dependencies) are moved from the repository to the selected process server. The process server can be connected or offline. Depending on your needs and whether the process server is connected or offline, you can use the Process Center Console or wsadmin commands to install the snapshot.
Important: Make sure the version of the Process Center server and the version of the connected or offline process server match exactly before install to the process server. Version matching is applicable to the first three digits only (for example, 7.5.0 or 7.5.1).
If you plan to install a process application snapshot that contains IBM BPM Advanced content or an IBM Business Monitor model, the user or group to which you belong must be assigned to the Configurator, Operator and Deployer administrative security role.
If you are not currently assigned to all of these roles, click Users and Groups in the WebSphere administrative console to modify the user or group roles. See "Administrative security roles" in the related links.
Connected process servers
You can install snapshots of process applications to connected process servers in your environment using either the Process Center Console or the BPMInstall command. Ordinarily, you have connections to one or more servers in your environment, as shown in the following figure.
Offline process servers
You can also install process application snapshots to an offline server that is running but is not connected to Process Center (for example, if the process server is behind a firewall). In this situation, use the wsadmin commands to create an installation package for a particular snapshot on the Process Center Server, transfer the package to the offline process server, and then run the package.
- Steps in the snapshot installation process
Understanding the individual steps in the installation process can help you identify and resolve any errors that occur during snapshot installation.- Restricting installation access to runtime servers
In order to install a snapshot on an online process server (a runtime server), you must have the appropriate access to the process application. Access requirements vary depending on whether the runtime server is in a development, non-production, or production environment.If you need to restrict installation access further, edit the 100Custom.xml file.
- Installing snapshots on a connected process server
You can install a process application snapshot with or without toolkit dependencies to any test or production process server that supports the artifacts in the application. When install a process application snapshot, a corresponding business level application (BLA) is created and started.
- Installing snapshots on offline process servers
If you want to install a snapshot to a process server that is not currently connected to the Process Center server (an offline server), create an installation package, extract it, and transfer it to the offline server. Then, use administrative commands on the server to install the package.
- Migrating instances
When you are installing snapshots on a process server, consider how to handle the business process definition instances that are running on the server.- Advanced installation topics
By default, a standard installation service is created for each process application when you first create and save the process application. You can customize this service to support more advanced requirements (for example, calling commands before or during the installation process).- Completing post-installation tasks
Depending on your environment and the installed process application, there are several tasks that might need to be completed immediately after installation.- Troubleshooting snapshot installations
Exceptions, timeouts, and other failures in the installation process can result in the snapshot not being installed on the server, or in an incomplete snapshot installation.
Installing, deploying, and undeploying applications in the runtime environment
Related concepts:
Administrative security roles