Petals ESB Container

Being able to separate administration and production networks by modifying configuration files

Details

  • Type: New Feature New Feature
  • Status: New New
  • Resolution: Unresolved
  • Affects Version/s: 3.1.1
  • Fix Version/s: None
  • Component/s: Topology/network
  • Security Level: Public
  • Description:

    Hello,

    I would like to start petals JMX service on a network interface which is not the network interface used by the BC SOAP, or other components.

    AFAIK we can't configure this right now, is it possible to implement this feature?

  • Environment:
    all

Activity

Ascending order - Click to sort in descending order
Sébastien André made changes - Thu, 28 Apr 2011 - 14:39:46 +0200
Field Original Value New Value
Link This issue blocks SPVEOLIAE-95 [ SPVEOLIAE-95 ]
Hide
Permalink
Christophe Hamerling added a comment - Thu, 28 Apr 2011 - 15:16:23 +0200

You do already do it. Just change the IP address in the SOAP component configuration file : Put one local IP address which is not used and defined in the local topology.xml file.

Show
Christophe Hamerling added a comment - Thu, 28 Apr 2011 - 15:16:23 +0200 You do already do it. Just change the IP address in the SOAP component configuration file : Put one local IP address which is not used and defined in the local topology.xml file.
Hide
Permalink
Christophe DENEUX added a comment - Thu, 28 Apr 2011 - 15:34:28 +0200

Moreover, we want to separate network traffic of the JMX server and the one of the TCP transporter.

Show
Christophe DENEUX added a comment - Thu, 28 Apr 2011 - 15:34:28 +0200 Moreover, we want to separate network traffic of the JMX server and the one of the TCP transporter.



People

Dates

  • Created:
    Thu, 28 Apr 2011 - 14:37:39 +0200
    Updated:
    Thu, 28 Apr 2011 - 15:34:28 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.