Bug 903848
| Summary: | Update the BRMS deployable instructions for EAP6 | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | lcarlon <lcarlon> |
| Component: | Documentation | Assignee: | lcarlon <lcarlon> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jiri Svitak <jsvitak> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | BRMS 5.3.1 | CC: | brms-docs, mbaluch, tkobayas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-08-21 02:00:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
lcarlon
2013-01-24 22:30:53 UTC
The content has been modified, I'll post a link as soon as it is available on the internal doc-stage for review. http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Enterprise_BRMS_Platform/5/html/BRMS_Getting_Started_Guide/Installing_the_Deployable_Package1.html I'll be moving the content of the procedure that relates specifically to EAP6, to a separate procedure in the guide. But for now, the changes provide the required guidance. Verified. Miguel (mreyesab) reported: ======= I just verified BRMS 5.3.1 with EAP 6.0.1 and this problem has been fixed and it deployment is working as it should. It is no longer necessary to use the flag auto-deploy-exploded="true" nor the .dodeploy files need to be recreated with every server restart. Just like bmaxwell said on 1/24/2013: "In EAP 6.0.1 a bug is fixed, if you have auto-deploy-exploded=false (default) then an exploded app is deployed by creating a <deployment-name>.dodeploy this triggers JBoss to deploy. Upon restart the .deployed will not be deleted and JBoss will deploy the war since it was deployed successfully before the restart." ======= So this is an issue only with EAP 6.0.0. Isn't it better to mention it in the Note? http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Enterprise_BRMS_Platform/5/html/BRMS_Getting_Started_Guide/Installing_on_JBoss_Enterprise_Application_Platform_61.html Hi Toshiya. Do we make a distinction in support between 6.0.0 and 6.0.1? I'll add a note stating that this is an issue with 6.0.0, but if we expect customers to be on the latest 6.0.x version, then we could just remove the note altogether. Yeah, removing the note is fine, Thanks! |