Troubleshooting Deployments

Deployment terminates with an error message if there is an orchestration in the process app and the destination environment does not have at least one ALF event manager and one JBPM engine. For details on solving this problem, refer to Target Servers.

If the process app that you are deploying contains a report with the same name as an existing report in the target environment, and the two reports are in the same project, are stored in the same table, and have the same access level (public or private), deployment generates a warning about duplicate reports.

If the process app uses an unsupported older schema version, attempting to deploy the process app will generate an error. In this case, you must first open the process app in SBM Composer and then republish the process app before deploying it.

If you experience a "Transport error: 404 Error–Not found" error when you deploy a large process app to Internet Information Services (IIS) 7.5, it is likely that you have a "request filtering" limit set in IIS that causes IIS to reject the request as being too large. The value is set to 500 MB by default. To increase the value, change the Maximum request content length setting on the IIS tab in SBM Configurator.