Hi Bernard, Latest EI-Analytics profile is based on WSO2 Stream Processor for which the configurations are different from the previous versions.
EI-Analytics 6.4.0 by default uses a file-based user store(via Local IdP Client). As you have mentioned, by default admin/admin is the user credentials used. with admin/admin credentials EI instance should have been able to publish to Analytics profile w/o any issue. Could you give follwing information to reproduce this issue? 1. Is the TCP protocol used for publishing or SSL protocol? (i.e <property name="receiverURL">*tcp*://localhost:7612</property> ) 2. Is the password encrypted? (i.e <property encrypted="*false*" name="password">admin</property>) In the meantime, please refer to "User Management via IdP client Interface <https://docs.wso2.com/display/SP430/User+Management+via+the+IdP+Client+Interface>" for more information on setting up the user store. Best Regards, *Niveathika Rajendran,* *Senior Software Engineer.* *Mobile : +94 077 903 7536* On Tue, Nov 6, 2018 at 3:59 PM Bernard Paris <[email protected]> wrote: > Hi Ramindu, > > thanks for this. > > Effectively I saw that everything has been changed in new analytics > distribution, and I can't cope with it ;-( > By default I don't see any users stuffs, like the use user-mgt.xml file. > So I suppose the "admin" user is just store in the DB, nothing else. > > I didn't change the default password for it, but remote ESB instances are > unable to send data to analytics because of > ERROR > {org.wso2.carbon.databridge.core.internal.authentication.CarbonAuthenticationHandler} > - Authentication failed for username 'admin'. Error : > 'Invalid_Credentials'. Error Description : 'The login credential used for > login are invalid, username : 'admin'.' > ERROR > {org.wso2.carbon.databridge.core.internal.authentication.Authenticator} - > wrong userName or password > > Local instance (I mean IE640 running on same localhost) can. > > I just edited this files to put admin/admin as user/passwd > <EI_HOME>/repository/deployment/server/eventpublishers/MessageFlowConfigurationPublisher.xml > & MessageFlowStatisticsPublisher.xml > > > > Thanks for your help, > Bernard > > > Le 1 nov. 2018 à 14:34, Ramindu De Silva <[email protected]> a écrit : > > Hi Bernard, > > EI analytics 6.3.0 uses WSO2 DAS <https://docs.wso2.com/display/DAS320> > runtime. EI analytics 6.4.0 uses WSO2 SP > <https://docs.wso2.com/display/SP430> runtime. WSO2 SP is a total rewrite > of the WSO2 DAS, which has a feature enhancements as well. > > On Tue, Oct 23, 2018 at 1:50 PM Bernard Paris <[email protected]> > wrote: > >> Hi devs, >> >> we were using these only 4 DBs to make analytics aggregating datas from >> our ESB until version 6.3.0 ; >> >> ANALYTICS_CARBON_DB >> ANALYTICS_METRICS_DB >> ANALYTICS_EVENT_STORE_DB >> ANALYTICS_PROCESSED_DATA_STORE_DB >> >> We have our from the scratch data aggregation mechanism > <https://wso2.github.io/siddhi/documentation/siddhi-4.0/#aggregate-function> > instead of using apache spark which was in DAS. And that the the > explanation for not having configurations for ANALYTICS_EVENT_STORE_DB and > ANALYTICS_PROCESSED_DATA_STORE_DB's . > We still have the ANALYTICS_CARBON_DB and ANALYTICS_METRICS_DB. > Please look into Monitoring Stream Processor > <https://docs.wso2.com/display/SP430/Monitoring+Stream+Processor> in-order > to configure the metrics for WSO2 SP. > >> >> >> These were postgres databases. >> Now I see there are more then 10 databases preconfigured in the default >> analytics 6.4.0 config (conf/dashboard/deployment.yaml >> and conf/worker/deployment.yaml). >> Well, … this is suggesting me lot of questions. >> >> First of all, is it still recommended (like it is for ESB&DSS databases) >> to do *not* use local H2 databases in production environment ? >> This question comes because the 6.4.0 analytics seems to me to be used as >> it is, out of the box, lot of DBs and no documentation for a any >> configuration as it was for previous versions. >> > Yes. We still recommend NOT to use the embedded H2 databases. > >> >> If we need to create external DBs for all the stuffs, what exactly are >> each DB for ? >> > Please refer Configuring Datasources > <https://docs.wso2.com/display/SP430/Configuring+Datasources> > >> >> Is there any migration tool and/or documentation about migrating from >> analytics 6.3.0 to 6.4.0 ? ( >> https://docs.wso2.com/display/EI640/Upgrading+from+WSO2+EI+6.3.0 does't >> talk about that) >> > > >> Any matching between former 4 DBs and the 6.4.0 new ones ? >> > ANALYTICS_CARBON_DB - In-order to use/ migrate this database the previous > analytics, please answer the following questions > > Seems, you are not using a usr-mgt database, Do you have add additional > users? If not its not necessary to migrate the carbon db. You just can move > on with a new db > > ANALYTICS_METRICS_DB - Metrics values stored in the DB depends on the node > that we run. But IMO since this is a new version of the product, there is > no use of migrating the older metrics data into the new one. > ANALYTICS_EVENT_STORE_DB and ANALYTICS_PROCESSED_DATA_STORE_DB - This is > replaced by aggregation tables. And aggregation > <https://wso2.github.io/siddhi/documentation/siddhi-4.0/#aggregate-function> > will be done via Siddhi <https://wso2.github.io/siddhi/> > >> >> Is there a way to keep (transfer into 6.4.0) datas we collected with >> previous analytics version ? >> > We are currently looking at several methods in-order to migrate the > ANALYTICS_EVENT_STORE_DB and ANALYTICS_PROCESSED_DATA_STORE_DB data and we > will update you on that regard. > >> >> Thanks, >> Bernard >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > Best Regards, > Ramindu. > -- > *Ramindu De Silva* > Senior Software Engineer > WSO2 Inc.: http://wso2.com > lean.enterprise.middleware > > email: [email protected] <[email protected]> > mob: +94 719678895 > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
