Description of problem: Vikram Goyal pointed out that " I noticed that the WAR packaged within the ZIP for WAS is in the exploded form. Is that something that is confirmed? Because a user then needs to package it as a WAR before uploading and deploying in Websphere.“ We should package the WAR application in an non exploded form for WAS8 distribution. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Maciej has also pointed out: "One thing I noticed that we do provide applications as exploded wars which is not best option for WebSphere as they need to be packaged anyway. Important to note is that there is crucial manifest entires that must be present in the deployed war to make the deployment successful. So maybe WebSphere assemblies should be delivered as war files directly instead of having them exploded. If not then we should document that when packaging the war file business-central.war/META-INF/MANIFEST.MF must be used instead of generating new one."
Verified with both BRMS and BPMS 6.0.2.ER3