Bug 779081 (SOA-1481)

Summary: Additional configuration required for running quickstarts when server not listening on localhost
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Julian Coleman <jcoleman>
Component: JBossESBAssignee: Julian Coleman <jcoleman>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4.3 CP02   
Target Milestone: ---   
Target Release: FUTURE   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1481
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
N/A
Last Closed: 2011-02-25 15:20:13 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:

Description Julian Coleman 2009-09-04 14:29:48 UTC
Affects: Interactive Demo/Tutorial
Date of First Response: 2009-10-27 15:55:40
Workaround: Workaround Exists
Workaround Description: Manually add serverName argument, as shown above.
project_key: SOA

The file .../samples.quickstarts/conf/readme.txt notes that the jndi.properties
files must be updated if the server is not listening on localhost or on 0.0.0.0.
However, the address must also be changed in the jBPM process deployer
section of the build.xml:

-       <deployToServer username="${jbpm.console.username}" password="${jbpm.console.password}" serverDeployer="${org.jboss.esb.jbpm.console.upload.url}">
+       <deployToServer username="${jbpm.console.username}" password="${jbpm.console.password}" serverName="my.server.name" serverDeployer="${org.jboss.esb.jbpm.console.upload.url}">

The serverName setting should be added to the file
.../conf/quickstarts.properties-example as a minimal fix.  A better fix would be
to define the hostname in a single place and inherit that in the other files
(jbossesb-properties.xml, jndi.properties, juddi.properties, etc.).

Comment 1 Burr Sutter 2009-10-27 19:55:40 UTC
Is this just a documentation issue?