Isolating deployment environments

Edit online

Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15

To isolate multiple deployment environments within a single cell, complete the following steps.

Before you begin

You should have some familiarity with the concepts described in the topic Considerations for multiple deployment environments in the same cell.

Note: Although deployment environments can be isolated, you should understand that they cannot be completely isolated due to the presence of cell-scoped artifacts that are shared by all of the deployment environments in the cell.

Restriction: Business Automation Workflow does not support the use of different service integration (SI) bus topologies between deployment environments in the same cell. All deployments environments must either use their isolated deployment environment-specific SI bus or share the legacy component-specific SI buses.

Procedure

Create the deployment environments.
Select one of the following methods to create unique HTTP endpoints:
- Use a dedicated virtual host for each deployment environment. See Step 3.
- Use dedicated context root prefixes for each deployment environment. See Step 4.
- Use dedicated web servers for each deployment environment. See Customizing Business Automation Workflow to work with a web server.
If you have multiple deployment environments in a single cell, and if you want to use the same web server, create a dedicated virtual host for each deployment environment. For each deployment environment (dep_env_name) in the cell, complete the following actions. For more information, see Virtual hosts in the WebSphere® Application Server information center.
1. Decide on the virtual host name, virtual_host_name.
2. Create a dedicated virtual host. Using the administrative console, navigate to Environment > Virtual hosts and click New.
3. Specify a name for the new virtual host. For example, vh_de1.
4. If you are using an external HTTP server, you must add the HTTP server's virtual host alias. Navigate to Environment > Virtual hosts > Name of the virtual host created in previous step > Host Aliases and click New. For example, navigate to vh_de1 and click New. Then enter the host name of your HTTP server and associate it with the HTTP or HTTPS port.
5. If you want to access the web container of the cluster members, add the host name of the cluster member as a host alias. Navigate to Environment > Virtual hosts > Name of the virtual host created in previous step > Host Aliases and click New. Enter the host name of the cluster member and associate it with the WC_defaulthost_secure port.
  Here is an example of the host aliases that must be added for a single cluster deployment environment that contains two members:
  
  Deployment environment name: de1
  
  Cluster name: de1.AppTarget
  
  Cluster member 1: de1.AppTarget.Member1
  
  Cluster member 2: de1.AppTarget.Member2
  
  Virtual host name: vh_de1
  Virtual host aliases in vh_de1:
  - To access IBM® Business Automation Workflow over HTTPS, add the cluster member host names and WC_defaulthost_secure ports to the host alias:
    
    Cluster member host name for de1.AppTarget.Member1 on the WC_defaulthost_secure port . For example 9443.
    
    Cluster member host name for de1.AppTarget.Member2 on the WC_defaulthost_secure port. For example 9443.
  - To access IBM Business Automation Workflow over HTTP, add the WC_defaulthost ports.
    
    Cluster member host name for de1.AppTarget.Member1 on the WC_defaulthost port. For example 9080.
    
    Cluster member host name for de1.AppTarget.Member2 on the WC_defaulthost port. For example 9080.
  - If you use an external HTTP server, add the HTTP server's virtual host alias. This is mandatory if you are using an external HTTP server.
    
    Virtual host that corresponds to your HTTP server. For example ihs.virtual.host.for.de1.ibm.com on port 80
    
    Virtual host that corresponds to your HTTP server. For example ihs.virtual.host.for.de1.ibm.com on port 443.
6. Map the virtual host name, virtual_host_name, to the deployment environment, dep_env_name, by running the BPMConfig command:
```
install_root/bin/BPMConfig.sh -update -profile profile_name -de dep_env_name -virtualHost virtual_host_name
```
```
install_root\bin\BPMConfig.bat -update -profile profile_name -de dep_env_name -virtualHost virtual_host_name
```
  Tip: If there is only one deployment environment in the WebSphere cell, you can omit the -de option. For more information about the BPMConfig command, see BPMConfig command-line utility. For information on the Business Automation Workflow virtual host, see Configuring endpoints to match your topology.
7. If you are using an external HTTP server, regenerate and propagate the HTTP server plug-in.
  1. In the administrative console, navigate to Servers > Server Types > Web Servers.
  2. Select the name of your HTTP server, then click Generate Plug-in.
  3. Select the name of your HTTP server, then click Propagate Plug-in.
    Tip: The administration service must be running on your HTTP server.
Configure dedicated context root prefixes for each deployment environment by running the BPMConfig command. For more information about the BPMConfig command, see BPMConfig command-line utility.
Configure an endpoint for the remote artifact loader (REMOTE_AL scenario) in each deployment environment. See Configuring endpoints to match your topology.
Optional: If you plan to use applications containing advanced content, such as BPEL process, or that have been imported into IBM Integration Designer and you are adding more than one deployment environment to the cell, provide a way to distinguish between the advanced content in these business-level applications across the deployment environments. You do this by setting the AdvancedDeploymentDEScoped property on the second and subsequent deployment environments:

Important: This topology can impact application maintenance, deployment, and administration. For information, see Considerations for multiple deployment environments in the same cell.
1. At a command prompt, navigate to the bin folder of the BPM installation.
2. Launch the wsadmin command line and set it to use Jython:
```
wsadmin -username adminuser -password mypassword -lang jython
```
3. Set the AdvancedDeploymentDEScoped property:
```
AdminTask.setBPMProperty( [ "-de", "DE_NAME", "-name", "ProcessCenter.AdvancedDeploymentDEScoped", "-value", "true"] )
```
  DE_NAME is the name of the deployment environment for which you are setting the property. By setting the property to true, business level-applications in the deployment environment have the deployment environment name added as an appendix to their name when they are installed into the deployment environment.
4. Save the change:
```
AdminConfig.save()
```
5. Restart the deployment environment and the deployment manager.
6. If Integration Designer is running, restart it.