This documentation is for WSO2 App Manager 1.0.0. View documentation for the latest release.
Page Comparison - Changing the Default Ports with Offset (v.12 vs v.13) - App Manager 1.0.0 - WSO2 Documentation

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The port offset specified earlier in the <AppM_HOME>/repository/conf/carbon.xml file does not affect the ports of the Thrift client and server because Thrift is run as a separate server within WSO2 servers. Therefore, you must change the Thrift ports separately using <ThfirtClientPort> <ThriftClientPort> and <ThriftServerPort> elements in the <AppM_HOME>/repository/conf/app-manager.xml file. For example, the following configuration sets an offset of 2 to the default Thrift port, which is 10397:

...

When you run multiple instances of the App Manager in distributed mode, the Gateway and Key Manager (used for validation and authentication) can run on two different JVMs. When the API Gateway receives API invocation calls, it contacts the API Key Manager service for verification (given that caching is not enabled at the Gateway level). Communication between API Gateway and Key Manager happens in either of the following ways:  

...

The App Manager has a service which listens for workflow callbacks. Find this service configuration at <AppM_HOME>/repository/deployment/server/synapse-configs/default/proxy-services/WorkflowCallbackService.xml. Open this file and change the port value of the <address uri uri> accordingly. 

For example,

...