Steps to Reproduce: #. Start SOA5 #. From Admin Console (admin-console) expand and select localhost -> JBossAS Servers - JBoss SOA-P 5 (default) -> JBoss ESB -> Deployments #. Click 'Add a new resource' button project_key: SOA When deploying a new ESB using admin-console or JBoss Operations Network, the ESB plug-in is asking for deployment options which are only valid for SOA 4. For example, Deployment Location is asking for a path but in SOA 5 ProfileService is used to deploy managed components meaning that a destination directory can not be selected but instead the user should be selecting whether to deploy farmed or not.
Bugzilla References: Added: https://bugzilla.redhat.com/show_bug.cgi?id=767981
Larry O'Leary <loleary> made a comment on [bug 767981|https://bugzilla.redhat.com/show_bug.cgi?id=767981] Logged against downstream JBossESB SOA-P bug tracker as https://issues.jboss.org/browse/SOA-3693 The JBoss ESB plug-in is managed/maintained by the JBossESB project.
Bugzilla References: Removed: https://bugzilla.redhat.com/show_bug.cgi?id=767981 Added: https://bugzilla.redhat.com/show_bug.cgi?id=767981
RH Bugzilla Integration <no-reply> updated the status of jira SOA-3693 to Closed
What is the status of this? This was supposed to be in SOA 5.3 release. Has that happened. We need a tag for the updated ESB plug-in for inclusion in JBoss ON.
Tom Cunningham <tcunning> made a comment on jira JBESB-3734 Added options for farm and exploded. Tested farm option against SOA-P 5.2, seems to work fine. The plugin had already been using profile service, so no changes needed there. tcunning@localhost:jonplugin]$ svn commit Sending jonplugin/as5/src/main/java/org/jbosson/plugins/jbossesb/ESB5Component.java Sending jonplugin/as5/src/main/resources/META-INF/rhq-plugin.xml Transmitting file data .. Committed revision 38087.
Tom Cunningham <tcunning> updated the status of jira JBESB-3734 to Resolved
Tom Cunningham <tcunning> updated the status of jira JBESB-3734 to Closed
Verified for JON and admin console. JON 3.1.0.GA and SOA-P 5.3.0.ER3. The deployment has options: File path, Deploy Exploded (Yes/No) and Deploy Farmed (Yes/No).
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: When a user tried to deploy an ESB archive via either the Admin Console or JON, they were presented with legacy SOA 4.x options that were no longer relevant and some needed options were missing. To fix this issue, new options for farm and exploded archives have been added. As a result, users can now deploy these via the consoles and the right information will be asked of them by the software.