Modifying and extending an existing installation
After you install and configure the runtime environment on your system in IBM® Business Process Manager, you might want to customize your configuration. For example, you might want to customize settings, set up an additional security provider, set up user accounts, and change and encrypt passwords.
- Updating IBM BPM data sources
If you need to modify one or more properties for an IBM BPM data source, or you find that your initial configuration is incorrect for an Oracle data source, you must use the BPMConfig command to make the required updates. You cannot make the updates using the administrative console. - Configuring JDBC drivers
IBM Business Process Manager (BPM) includes Java database connectivity (JDBC) drivers for DB2 databases. The versions of the DB2 JDBC drivers that are included are determined by the levels of the corresponding database products that were supported by the particular release of IBM BPM. You should update the JDBC drivers whenever another level of a database product is released, to avoid unexpected errors from failures that originate from the drivers. If you are using Oracle or SQL Server databases, you must configure your own JDBC drivers. - Switching the edition of Java used in IBM BPM
When you install IBM Business Process Manager (BPM) V8.6.0, Java Technology Edition 8 is installed along with the required version of WebSphere Application Server Network Deployment. However, if you upgraded from an earlier version of IBM BPM, you must install the Java 8 extension package and switch your version of Java to Java 8 by using the managesdk command. - Configuring IBM BPM with a new external ECM server
You might be currently working with the IBM BPM content store to store Enterprise Content Manager (ECM) information in IBM Business Process Manager. But you might want to work instead with a new external ECM system. You can configure IBM BPM to work with a new external ECM system. This configuration continues to use the existing domain and object store without migrating the data from the IBM BPM content store. - Configuring IBM BPM with an existing external ECM server
You might be currently working with an embedded Enterprise Content Manager (ECM) system, which is the default configuration in IBM Business Process Manager. But you might want to work instead with an existing external ECM system. You can configure IBM Business Process Manager to work with an existing external ECM system by using a new object store or by reassigning the IBM BPM content store. - Connections in IBM Business Process Manager
In IBM Business Process Manager, there are several types of connections. Each connection type has its own specific behavior and settings. - Customizing IBM BPM to work with a web server
After you install and configure IBM BPM, you must customize your environment so that it can function properly as a cluster with a web server. - Customizing context roots for the components in a deployment environment
After you create a deployment environment, you can customize the context root for all components in the environment by using the BPMConfig script to add a prefix. You can also customize the Heritage Process Portal context root by adding a prefix that is specific to this component only. - Customizing Business Process Choreographer
Business Process Choreographer is configured by default when you use the BPMConfig command or the deployment environment wizard to create your IBM BPM Server environment. Depending on your requirements, you might need to perform further customization. - Changing IBM Business Process Manager and database passwords
You can change the IBM Business Process Manager and database passwords after completing the installation and configuration. - Configuring Oracle Real Application Cluster (RAC) for use with IBM Business Process Manager
Oracle Real Application Clusters (RAC) is an option of an Oracle database that brings together two or more computers to form a clustered database that behaves as a single system. In a RAC database, Oracle processes that run in separate nodes access the same data from a shared disk storage. - Configuring a proxy server
You can use the configureProxyServer.py script to create the routing server functionality for the Process Center cluster or the Process Server clusters when you have more than one node in your topology. - Configuring the Business Space component and registering REST endpoints on the administrative console
You can install and configure the Business Space component using the administrative console. - Configuring the Business Space Ajax proxy
You might want to modify the Business Space Ajax proxy for special considerations in Heritage Process Portal, such as changing timeout settings or blocking IP addresses for secure production environments. - Creating a new deployment environment based on an existing configuration
You can export the configuration properties from an existing deployment environment, modify the properties with the IBM BPM Configuration editor, and then create another deployment environment on a different IBM Business Process Manager installation that is similar to the exported deployment environment (a clone with modifications). - Exporting configuration properties for comparison
You can export the configuration properties from two different V8.6.0 deployment environments and compare them, using your own comparison tools, to understand the difference between two IBM Business Process Manager systems. You can also compare against V8.5.5 configurations, but you must take into account that the more recent version extracts more properties than the previous version. - Extending and modifying a network deployment environment
You can adjust a network deployment environment to meet your current needs, including adding managed nodes and cluster members or removing managed nodes. To move a managed node to new hardware, first add a new managed node on the new computer and then remove the previous managed node from the old computer before disposing of it. - Adding a network deployment environment
You can add multiple independent deployment environments for your applications in the same cell. However, you can add only one Process Center-based deployment environment in a single cell.