Hide Forgot
Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes Date of First Response: 2010-02-15 18:12:32 project_key: SOA For SOA 5.0.0 GA, we will not ship two versions of the jBPM console. The "Getting Started Guide" currently contains a section: Securing the jBPM Console This whole section can be removed. The new functionality should be documented in the JBPM Reference Guide, in the section: Deploying a process archive Deploying process archives can be done in 4 ways; with the process designer tool, with an ant task, programatically, or by using the GPD deployer. ... The GPD deployer is available at http://localhost:8080/gpd-deployer/ Processes can be deployed manually by selecting a file to upload, or programmatically by using an HTTP connection to the deployer. The new functionality should also be documented in the Release Notes, in the section on compatibility with SOA-P 4.x. A single, secured version of the jBPM console is shipped with this release of SOA-P. The process deployert that was previously part of the jBPM console is now available at http://localhost:8080/gpd-deployer/ . This new deployer replaces the deployers that were previously available at http://localhost:8080/app/upload or http://localhost:8080/upload .
Affects: Removed: [Release Notes, Documentation (Ref Guide, User Guide, etc.)] Added: [Documentation (Ref Guide, User Guide, etc.), Release Notes]
Being documented as a migration issue in the release notes
The non-secured version of the jBPM console is no longer needed for process deployment because the jBPM console now supports authentication for deployment. The process deployer is available at http://localhost:8080/gpd-deployer/ . This replaces the deployers from previous versions, http://localhost:8080/app/upload and http://localhost:8080/upload .