This documentation is for WSO2 IoT Server 3.0.0. View the documentation for the latest release.
Due to a known issue do not use JDK1.8.0_151 with WSO2 products. Use JDK 1.8.0_144 until JDK 1.8.0_162-ea is released.
Page Comparison - Configuring WSO2 IoT Server with the IP for iOS (v.9 vs v.10) - IoT Server 3.0.0 - WSO2 Documentation

Versions Compared

Key

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

If you are in a production environment, make sure to have the following ports open:

  • 5223 - TCP port used by devices to communicate to APNs servers
  • 2195 - TCP port used to send notifications to APNs
  • 2196 - TCP port  used by the APNs feedback service
  • 443 - TCP port used as a fallback on Wi-Fi, only when devices are unable to communicate to APNs on port 5223
    The APNs servers use load balancing. The devices will not always connect to the same public IP address for notifications. The entire 17.0.0.0/8 address block is assigned to Apple, so it is best to allow this range in the firewall settings. 
  • 10397 - Thrift client and server ports
  • 8280, 8243 - NIO/PT transport ports

Follow the steps given below to configure the ports in WSO2 IoTS to enable the iOS agent to communicate with the IoT server.

  1. Configure the following fields that are in the <IoT_HOME>/core/repository/conf/api-manager.xml file to enable communication with the WSO2 API Manager.

    • Configure the <serverURL> field that is under the <APIKeyValidator> tag by replacing ${carbon.local.ip} with the hostname or public IP of the production environment.
      Example:

      Code Block
      <ServerURL>https://10.10.10.182:${mgt.transport.https.port}${carbon.context}/services/</ServerURL>
    • Configure the <RevokeAPIURL> field by replacing ${carbon.local.ip} with the hostname or public IP of the production environment.
      Example:

      Code Block
      <RevokeAPIURL>https://10.10.10.182:${https.nio.port}/revoke</RevokeAPIURL>
  2. If you started the WSO2 IoT Server's core profile previously, the APIs published will connect to localhost. Therefore, you need to configure the <EnabledUpdateApi> property as true in the <IoT_HOME>/core/repository/conf/etc/webapp-publisher-config.xml file to update the APIs with the Server IP.

    Code Block
    <!-- If it is true, the APIs of this instance will be updated when the webapps are redeployed -->
    <EnabledUpdateApi>true</EnabledUpdateApi>
  3. Configure WSO2 IoT Server with the IP:

    Excerpt Include
    Configuring WSO2 IoT Server with the IP or Hostname
    Configuring WSO2 IoT Server with the IP or Hostname
    nopaneltrue

What's next?

Configuring WSO2 IoT Server to Install iOS Applications.