Problematic Server Configurations

Overlapping Environments

In a correctly configured SBM system that has multiple environments, each environment will have its own distinct Application Engine server, and Event Manager server, and an Orchestration Engine server. The Orchestration Engine and Event Manager servers are known to Application Repository as "target servers." The Orchestration Engine installation and database is represented by BPEL Server on the Target Servers tab. The Event Manager server is represented by System Event Manager.

Application Engine and the target servers should be unique to a specific environment so environments do not overlap. However, you can create overlapping environments, because Application Repository lets you reuse the same server in a different environment. This is not the intent of environments, and in most cases it is undesirable and unintended. It means the server is not fully owned by a particular environment and cannot be managed in isolation. You could have created such environments accidentally by using the Clone operation, or could have created them for testing purposes. It is strongly recommended that you clean up such environments before you run renew.

Renew can be used with overlapping environments in a limited capacity, but it is necessary to understand your configuration thoroughly and understand the following limitations of renew:

• Renew clears the Orchestration Engine database. All environments that point to this database will require orchestrations to be redeployed.
• Renew attempts to redeploy all of the orchestrations from the Application Engine defined in the environment. If the Application Engine is shared, renew may deploy more orchestrations than you expect.
• Renew uses the specified environment to bind the endpoints. If the orchestration was not originally deployed through that environment, the endpoint might not be defined or might have the wrong value.

Using renew to redeploy when there are overlapping environments is problematic and is not recommended. You can use renew to clear the Orchestration Engine database but to ensure correct results, you should use Application Repository to manually redeploy each of the process apps from the overlapping environments from which they were originally deployed.

By default, renew tries to detect overlapping environments and will ask for confirmation before redeploying. (If you use the -nowarning option with renew -redeploy, no confirmation warning is presented.) The -listenvs command also detects overlapping environments.