| Summary: | Need to document that EDS is not supported with, and cannot be installed into the 5.1 "standalone" server | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Len DiMaggio <ldimaggi> |
| Component: | Documentation | Assignee: | David Le Sage <dlesage> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.1.0.ER9 | CC: | ldimaggi, vhalbert |
| Target Milestone: | --- | ||
| Target Release: | 5.2.0 GA | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-2899 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-11-15 02:31:24 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: | |
Link: Added: This issue related SOA-2900 Release Notes Docs Status: Added: Documented as Known Issue Release Notes Text: Added: To enable deployment to a standalone server, change the eds build.xml by replacing: <property name="jboss_home" value="../jboss-as/"/> with: <condition property="jboss_home" value="../jboss-esb"> Writer: Added: Darrin Release Notes Text: Removed: To enable deployment to a standalone server, change the eds build.xml by replacing: <property name="jboss_home" value="../jboss-as/"/> with: <condition property="jboss_home" value="../jboss-esb"> Added: https://issues.jboss.org/browse/SOA-2899 To enable deployment to a standalone server, change the EDS build.xml by replacing: <property name="jboss_home" value="../jboss-as/"/> with: <condition property="jboss_home" value="../jboss-esb"> We also need to mention that this is not a supported/certified configuration. Note - just to repeat - in the CR1 build - the installer successfully installs EDS into a standalone server's 'default' profile. No additional code changes are needed. The remaining task is to update the documentation. Writer: Removed: Darrin Added: dlesage Release Notes Docs Status: Removed: Documented as Known Issue Added: Documented as Resolved Issue Release Notes Text: Removed: https://issues.jboss.org/browse/SOA-2899 To enable deployment to a standalone server, change the EDS build.xml by replacing: <property name="jboss_home" value="../jboss-as/"/> with: <condition property="jboss_home" value="../jboss-esb"> Added: https://issues.jboss.org/browse/SOA-2899 The all, production, default server profiles are supported with EDS - but with the EMBEDDED server only. Do not try to install EDS into the standalone server as it is not a supported/certified configuration. Updated text of release note after IRC discussion with ldimaggi 14/11/2011 The release note reads:
{color:blue}
https://issues.jboss.org/browse/SOA-2899
To enable deployment to a standalone server, change the EDS build.xml by replacing: <property name="jboss_home" value="../jboss-as/"/> with: <condition property="jboss_home" value="../jboss-esb">
{color}
We should also (re)state that this configuration is not supported.
Looking at the build.xml, it contains
<condition property="jboss_home" value="../jboss-esb/">
<available file="../jboss-esb"/>
</condition>
no changes should be required.
Link: Added: This issue is related to SOA-3236 See SOA-3236 regarding validating installation. |
project_key: SOA The all, production, default server profiles are supported with EDS - but with the EMBEDDED server only. If the user tries to install EDS into the standalone server - this error is returned: ant Buildfile: build.xml prompteds: [input] Enter profile to install EDS to: all, production, or default [default] validate.profile: promptcxf: install: BUILD FAILED /jboss/local/51_ER9/jboss-soa-p-standalone-5/eds/build.xml:36: Profile default does not exist