Re: [Dev] [EMM] Configurations to Enabling Dashboard Server Communication

2016-08-30 Thread Shavindri Dissanayake
Thank you, Dilan!

Thanks & Regards
Shavindri Dissanayake
Technical Writer

WSO2 Inc.
lean.enterprise.middleware

On Tue, Aug 30, 2016 at 1:03 PM, Dilan Udara Ariyaratne 
wrote:

> Hi Shavindri,
>
> We are maintaining the sources for common widgets for both EMM and IoT
> products in one carbon-app and
> the sources for emm-specific widgets in another.
>
> In order to deploy all these widget related sources coming from two
> carbon-apps into the corresponding location of portal jaggery app,
> we have to maintain the two server roles as mentioned and server-role
> "CDMFPlatform" will only be necessary for this particular requirement.
>
> That's why we have to add this role to carbon.xml and since we are not
> maintaining a custom carbon.xml, adding "CDMFPlatform" role by default into
> the file, will not be possible.
>
> Next issue in question, is the %https.ip% template that we use in
> designer.json file of the portal app for configuring various services.
>
> Of course in a default pack, even without replacing these templates,
> dashboard will work as all these services comes by default in a regular
> pack.
> But in a real deployment scenario, this might not work if these services
> are decided to run on separate servers. In that case, we will have to set
> the correct
> IP and port for such services explicitly here by replacing the default
> %https.ip%. But that would not always necessarily be https://
> : and could be some
> other IP and port.
>
> Regarding the issue, "EMM analytics dashboard is not appearing after the
> configurations" > yes, this has to be looked into ASAP with swagger and
> scope related improvements.
>
> Cheers,
> Dilan.
>
>
> *Dilan U. Ariyaratne*
> Senior Software Engineer
> WSO2 Inc. 
> Mobile: +94766405580 <%2B94766405580>
> lean . enterprise . middleware
>
>
> On Tue, Aug 30, 2016 at 11:46 AM, Shavindri Dissanayake <
> shavin...@wso2.com> wrote:
>
>> Hi Team,
>>
>> Need your expertise to verify a few areas, as to why we have to configure
>> the following for the $subject.
>>
>>- As documented [1]
>>
>> ,
>>we need to add the CDMF platform role under server roles in the
>>/repository/conf/carbon.xml file.
>>-
>>Can we have the CDMF platform role added into the carbon.xml file by
>>default, without having the user to add it in?
>>If this is  possible, we can reduce the number of steps.
>>
>>- Next, we need to configure the designer.json file that is in the
>>/repository/deployment/server/jaggeryapps/portal/configs
>>directory.
>>In [1]
>>
>> 
>>we mention to replace %https.ip% with https://:.
>>--
>>Is this necessary? By default, in all WSO2 products shouldn't the
>>servers details be taken for %https.ip%?
>>
>> P.S: Currently, the EMM analytics dashboard is not appearing after the
>> configurations are done due to the API refactoring.
>>
>> [1] https://docs.wso2.com/display/EMM220/General+Server+Conf
>> igurations#GeneralServerConfigurations-EnablingDashboardServ
>> erCommunication
>> [2] https://wso2.org/jira/browse/EMM-1523
>>
>> Thanks & Regards
>> Shavindri Dissanayake
>> Technical Writer
>>
>> WSO2 Inc.
>> lean.enterprise.middleware
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [EMM] Configurations to Enabling Dashboard Server Communication

2016-08-30 Thread Dilan Udara Ariyaratne
Hi Shavindri,

We are maintaining the sources for common widgets for both EMM and IoT
products in one carbon-app and
the sources for emm-specific widgets in another.

In order to deploy all these widget related sources coming from two
carbon-apps into the corresponding location of portal jaggery app,
we have to maintain the two server roles as mentioned and server-role
"CDMFPlatform" will only be necessary for this particular requirement.

That's why we have to add this role to carbon.xml and since we are not
maintaining a custom carbon.xml, adding "CDMFPlatform" role by default into
the file, will not be possible.

Next issue in question, is the %https.ip% template that we use in
designer.json file of the portal app for configuring various services.

Of course in a default pack, even without replacing these templates,
dashboard will work as all these services comes by default in a regular
pack.
But in a real deployment scenario, this might not work if these services
are decided to run on separate servers. In that case, we will have to set
the correct
IP and port for such services explicitly here by replacing the default
%https.ip%. But that would not always necessarily be https://
: and could be some
other IP and port.

Regarding the issue, "EMM analytics dashboard is not appearing after the
configurations" > yes, this has to be looked into ASAP with swagger and
scope related improvements.

Cheers,
Dilan.


*Dilan U. Ariyaratne*
Senior Software Engineer
WSO2 Inc. 
Mobile: +94766405580 <%2B94766405580>
lean . enterprise . middleware


On Tue, Aug 30, 2016 at 11:46 AM, Shavindri Dissanayake 
wrote:

> Hi Team,
>
> Need your expertise to verify a few areas, as to why we have to configure
> the following for the $subject.
>
>- As documented [1]
>
> ,
>we need to add the CDMF platform role under server roles in the
>/repository/conf/carbon.xml file.
>-
>Can we have the CDMF platform role added into the carbon.xml file by
>default, without having the user to add it in?
>If this is  possible, we can reduce the number of steps.
>
>- Next, we need to configure the designer.json file that is in the
>/repository/deployment/server/jaggeryapps/portal/configs
>directory.
>In [1]
>
> 
>we mention to replace %https.ip% with https://:.
>--
>Is this necessary? By default, in all WSO2 products shouldn't the
>servers details be taken for %https.ip%?
>
> P.S: Currently, the EMM analytics dashboard is not appearing after the
> configurations are done due to the API refactoring.
>
> [1] https://docs.wso2.com/display/EMM220/General+Server+Conf
> igurations#GeneralServerConfigurations-EnablingDashboardServ
> erCommunication
> [2] https://wso2.org/jira/browse/EMM-1523
>
> Thanks & Regards
> Shavindri Dissanayake
> Technical Writer
>
> WSO2 Inc.
> lean.enterprise.middleware
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] [EMM] Configurations to Enabling Dashboard Server Communication

2016-08-30 Thread Shavindri Dissanayake
Hi Team,

Need your expertise to verify a few areas, as to why we have to configure
the following for the $subject.

   - As documented [1]
   
,
   we need to add the CDMF platform role under server roles in the
   /repository/conf/carbon.xml file.
   -
   Can we have the CDMF platform role added into the carbon.xml file by
   default, without having the user to add it in?
   If this is  possible, we can reduce the number of steps.

   - Next, we need to configure the designer.json file that is in the
   /repository/deployment/server/jaggeryapps/portal/configs
   directory.
   In [1]
   

   we mention to replace %https.ip% with https://:.
   --
   Is this necessary? By default, in all WSO2 products shouldn't the
   servers details be taken for %https.ip%?

P.S: Currently, the EMM analytics dashboard is not appearing after the
configurations are done due to the API refactoring.

[1] https://docs.wso2.com/display/EMM220/General+Server+Configurations#
GeneralServerConfigurations-EnablingDashboardServerCommunication
[2] https://wso2.org/jira/browse/EMM-1523

Thanks & Regards
Shavindri Dissanayake
Technical Writer

WSO2 Inc.
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev