Versions Compared

Old Version 8

changes.mady.by.user Former user

Saved on

compared with

New Version 9

changes.mady.by.user Former user

Saved on

Key

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

...

  1. Configure the carbon.xmlfiles of the three profile to port offset.

    Core

    Open the <IOTS_HOME>/conf/carbon.xml file and port offset the IoT Server's core profile by configuring the <Offset> attribute.

    Note

    Make sure that the offset value is not the same as the broker or analytics profile.

    Example:

    Code Block
    <Offset>4</Offset>

    Now the port of the core profile is 9447/9767.

    Analytics

    Open the <IOTS_HOME>/wso2/analytics/conf/carbon.xml file and port offset the IoT Server's core profile by configuring the <Offset> attribute.

    Note

    Make sure that the offset value is not the same as the broker or analytics profile.

    Code Block
    <Offset>5</Offset>

    Now the port of the core profile is 9448/9768.

    Broker

    Open the <IOTS_HOME>/wso2/broker/conf/carbon.xml file and port offset the IoT Server's core profile by configuring the <Offset> attribute.

    Note

    Make sure that the offset value is not the same as the broker or analytics profile.

    Code Block
    <Offset>6</Offset>

    Now the port of the core profile is 9449/9769.

  2. Open the <IOTS_HOME>/bin/iot-server.sh or iot-server.bat file configures the following ports:

    Analytics ports

    By default the analytics profileisoffset by 2. In step 1, you offset the analytics profile by 3 more again. Therefore, all the ports relevant to analytics need to be offset by 3 more.

    Example:

    Code Block
    -Diot.analytics.https.port="9448" \
    Broker ports

    By default, the broker profile is offset by 3. In step 1, you offset the broker profile by 3 more. Therefore, all the ports relevant to broker need to be offset by 3.

    Example:

    Code Block
    -Dmqtt.broker.port="18901889" \
    IoT core ports

    By default the core profile is not offset. In step 1, you offset the broker profile by 4. Therefore, all the ports relevant to core needs to be offset by 4.

    Code Block
    -Diot.manager.https.port="9447" \
-Diot.core.https.port="9447" \
-Diot.keymanager.https.port="9447" \
-Diot.gateway.https.port="8247" \
-Diot.gateway.http.port="8284" \
-Diot.gateway.carbon.https.port="9447" \
-Diot.gateway.carbon.http.port="9767" \
-Diot.apimpublisher.https.port="9447" \
-Diot.apimstore.https.port="9447" \

  3. Open the <IOTS_HOME>/wso2/analytics/bin/wso2server.sh  or wso2server.bat file configures the following ports:

    Broker ports

    By default, the broker profile is offset by 3. In step 1, you offset the broker profile by 3 more. Therefore, all the ports relevant to broker need to be offset by 3.

    Example:

    Code Block
    -Dmqtt.broker.port="18901889" \
    IoT core ports

    By default the core profile is not offset. In step 1, you offset the core profile by 4. Therefore, all the ports relevant to core needs to be offset by 4.

    Code Block
    -Diot.keymanager.https.port="9447" \
-Diot.gateway.https.port="8247" \

  4. Configure the <IOTS_HOME>/conf/identity/sso-idp-config.xml file.

    IoT core

    By default the core profile is not offset. In step 1, you offset the core profile by 4. Therefore, all the ports relevant to core needs to be offset by 4.

    Code Block
    <AssertionConsumerServiceURL>https://localhost:9447/devicemgt/uuf/sso/acs</AssertionConsumerServiceURL>
<DefaultAssertionConsumerServiceURL>https://localhost:9447/devicemgt/uuf/sso/acs</DefaultAssertionConsumerServiceURL>
<Audience>https://localhost:9447/oauth2/token</Audience>
<Recipient>https://localhost:9447/oauth2/token</Recipient>
<AssertionConsumerServiceURL>https://localhost:9447/store/acs</AssertionConsumerServiceURL>
<DefaultAssertionConsumerServiceURL>https://localhost:9447/store/acs</DefaultAssertionConsumerServiceURL>
<AssertionConsumerServiceURL>https://localhost:9447/social/acs</AssertionConsumerServiceURL>
<DefaultAssertionConsumerServiceURL>https://localhost:9447/social/acs</DefaultAssertionConsumerServiceURL>
<AssertionConsumerServiceURL>https://localhost:9447/publisher/acs</AssertionConsumerServiceURL>
<DefaultAssertionConsumerServiceURL>https://localhost:9447/publisher/acs</DefaultAssertionConsumerServiceURL>
<AssertionConsumerServiceURL>https://localhost:9447/api-store/jagg/jaggery_acs.jag</AssertionConsumerServiceURL>
<DefaultAssertionConsumerServiceURL>https://localhost:9447/api-store/jagg/jaggery_acs.jag</DefaultAssertionConsumerServiceURL>
<AssertionConsumerServiceURL>https://localhost:9447/portal/acs</AssertionConsumerServiceURL>
<DefaultAssertionConsumerServiceURL>https://localhost:9447/portal/acs</DefaultAssertionConsumerServiceURL>
<Audience>https://localhost:9447/oauth2/token</Audience>
<Recipient>https://localhost:9447/oauth2/token</Recipient>
<Audience>https://localhost:9447/oauth2/token</Audience>
<Recipient>https://localhost:9447/oauth2/token</Recipient>
    Analytics

    By default the analytics profile is offset by 2. In step 1, you offset the analytics profile by 3 more again. Therefore, all the ports relevant to analytics need to be offset by 3 more.


    Code Block
    <AssertionConsumerServiceURL>https://localhost:9448/portal/acs</AssertionConsumerServiceURL>
<DefaultAssertionConsumerServiceURL>https://localhost:9448/portal/acs</DefaultAssertionConsumerServiceURL>