Hide Forgot
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.
Link: Added: This issue depends SOA-1113
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
added to known issues in release notes. Also added more detail in light of this to the deployment instructions in the monitoring guide
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