Bug 778638 (SOA-1114)

Summary:	Document management-esb ant task configuration issue
Product:	[JBoss] JBoss Enterprise SOA Platform 4	Reporter:	Mark Little <mark.little>
Component:	Documentation	Assignee:	Dana Mison <dmison>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	4.2 CP02
Target Milestone:	---
Target Release:	4.2 CP03
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-1114
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-01-12 19:31:47 UTC	Type:	Task
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	778637
Bug Blocks:

Description Mark Little 2009-01-09 14:58:43 UTC

Affects: Release Notes
Date of First Response: 2009-01-09 11:34:05
project_key: SOA

Document the workaround (see linked issue) in release notes.

Comment 1 Mark Little 2009-01-09 14:59:24 UTC

Link: Added: This issue depends SOA-1113

Comment 2 Len DiMaggio 2009-01-09 16:34:05 UTC

FYI - this is already in the Getting Started Guide:

2.1.1. Changing the Database used by the platform
.
.
.
After the database reconfiguration the Management Console must be redeployed manually.

1. Edit the file /jboss-as/tools/console/management-esb/build.xml and change the
value for org.jboss.esb.server.config to production or development (if you have a
development profile).

2. Run ant deploy

Comment 3 Dana Mison 2009-01-12 05:27:33 UTC

added to known issues in release notes.  Also added more detail in light of this to the deployment instructions in the monitoring guide

Comment 4 Len DiMaggio 2009-01-12 19:31:47 UTC

Verified in the monitoring guide here:  https://svn.corp.jboss.com/repos/soa/branches/4.2.0/build-tools/docs/esb/governance/


It's now in the Getting Started guide - see the text in the 1st comment to this JIRA (https://jira.jboss.org/jira/browse/SOA-1114?focusedCommentId=12447227#action_12447227) and in the monitoring guide:

The monitoring console is installed by default in the included all and production server
configurations but can easily be installed in other configurations if required.

Procedure 1.1. Manually installing the console

1. You must edit the ${SOA_ROOT}/tools/console/management-esb/build.xml and
specify the server configuration that you wish to deploy to.
<property name="org.jboss.esb.server.config" value="production"/>

2. If you are not using HSQLDB as your database backend for the console you will need to edit the
file ${SOA_ROOT}/tools/console/management-esb/db.properties to define the correct
database settings. Section 1.1.1, "Alternative database usage" contains details of this topic.

3. You then run ant deploy in the ${SOA_ROOT}/tools/console/management-esb
directory.

$ cd tools/console/management-esb
$ ant deploy

Example 1.1. Deploying the monitoring console on Linux/Unix