Hi, 

I will let somebody more knowledgeable to confirm this, but considering that -Djboss.socket.binding.port-offset=1 works just fine then changing the ports directly should also work. 

You might need to adjust the Gateway port (from 8443 to 8444). This can be done in System Administration under the link "Manage Gateways”.

— Jakub.

On 8 Jun 2015 at 21:31:37, helio frota (00hf11@gmail.com) wrote:

Hi all,

We have a server to setup apiman in production, but already exist a wildfly instance.

My question is:

Is 'correct' to change the ports of standalone-apiman.xml ?

I did +1 to all ports

<socket-binding-group name="standard-sockets" default-interface="public"
    port-offset="${jboss.socket.binding.port-offset:0}">
    <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9991}" />
    <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9994}" />
    <socket-binding name="ajp" port="${jboss.ajp.port:8010}" />
    <socket-binding name="http" port="${jboss.http.port:8081}" />
    <socket-binding name="https" port="${jboss.https.port:8444}" />
    <socket-binding name="txn-recovery-environment" port="4713" />
    <socket-binding name="txn-status-manager" port="4714" />
    <outbound-socket-binding name="mail-smtp">
      <remote-destination host="localhost" port="25" />
    </outbound-socket-binding>
  </socket-binding-group>

helio
_______________________________________________
Apiman-user mailing list
Apiman-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/apiman-user