I need to deploy the message broker. However is not clear if I must have the ESB profile running too.
I'm following this guide https://dzone.com/articles/wso2-enterprise-integrator-with-a-message-broker-p and it seems that ESB profile is needed. Is it correct? What's the point in running ESB profile alongside the MB profile? thanks
If you only need message broker you only need to start MB profile. documentation
To start the MB profile: Open a terminal, navigate to the /bin directory where all the startup scripts are stored and run the startup script:
On Windows: broker.bat
On Linux: sh broker.sh
The document you referred explains how to integrate message broker and ESB. You don't have to start ESB profile unless it's applicable for your use-case.
Related
I am working with Micro Integrator which is available inside latest Integration studio as run time. When I check the axis2.xml file to configure the MailTransportSender to send email notifications, I didn't see those properties.
I tried to copy those from ESB profile and tried to use in Micro Integrator. As soon as I start the server the properties are disappearing from axis2.xml file of Micro Integrator.
How do I resolve this?
It should work in Micro Integrator. But the way you add them is different. Micro Integrator comes with new deployment toml file, where you have to edit all the configurations, which will overwrite the config files on startup ( also axis2 ). Please refer the documentation https://ei.docs.wso2.com/en/latest/micro-integrator/setup/transport_configurations/configuring-transports/#configuring-the-mailto-transport for more details.
Thanks !
Nirothipan
I already was able to create API Manager and Enterprise Integrator as service, following this tutorials: https://docs.wso2.com/display/EI611/Installing+as+a+Windows+Service
https://docs.wso2.com/display/AM210/Installing+as+a+Windows+Service
But i can't found a tutorial to show me the way to configure Message Broker to be installed as windows service. Could anyone help me?
Thank you.
I discovered the solution from that. Unfortunately the WSO2 don't have the support to create a message broker as a service yet. Been like that, you can't do that yet, unless you find anothers way out of the original platform to do so.
Its possible to do that through the YAJSW by installing the version of 11.03.
I tried and resolved the same by keeping the ESB and Message Broker as a different services in the windows service.
Just change the name and convention as per the services and maintain the uniqueness which you want to execute as a service.
Also, do the steps as provide by the YAJSW steps to install as a service for both either EI or ESB and Message Broker.
Follow the below link for the steps,
https://docs.wso2.com/display/ESB500/Installing+as+a+Windows+Service#InstallingasaWindowsService-SettinguptheYAJSWwrapperconfigurationfile
Thanks,
Praveen Tallakokula
Application creation workflow - Approval task is not showing in API Manager admin-dashboard after creating a new Application. [Tried with different users]
When I am checking in Business Process Server Management Console --> Human Tasks, It shows the list of Claimable talks. When I select from the list of Claimable tasks, it show the following error.
Task request information cannot be loaded. Please check
ApproveApplication-input.jsp file available inside Human Task package
web directory.
Could you please suggest, how could I fix this issue?
You have to do the below step as instructed under Configuring the API Manager heading.
Open the <APIM_HOME>/repository/deployment/server/jaggeryapps/admin-dashboard/site/conf/site.json file and configure workFlowServerURL under workflows to point to the BPS server (e.g. "workFlowServerURL": "https://localhost:9445/services/")
I'm new to WSO2 products and I was trying to set up the API statistics by configuring APIM with BAM as said in this documentation for publishing the stats https://docs.wso2.com/display/AM170/Publishing+API+Runtime+Statistics#PublishingAPIRuntimeStatistics-point3.
However every time I try to configure the statistics, start BAM, and re-start APIM I always get an error on the APIM console "Error occured while getting API's".
What does this mean?
Does it mean I have to configure first APIM and BAM before I can make an API and check it's statistics?
I don't get it why following the manual results into something like an error. Is there something wrong with my configuration?
here are few ways to debug whats going wrong. How API-M and BAM integration works is that
API -> publish stats to BAM
BAM stores the stats in Cassandra
BAM uses Hive scripts to analyse the data and write the results to a RDBMS mentioned in master-datasources.xml
I would recommend you to check the number 2. by checking if stats are published to BAM. You can do this by login into the management console of BAM and going to the Analytic section and adding the following script
select * from APIRequestData;
Execute this script and see if any data is returned. If no data is returned then data is not correctly published from API-M to BAM. If data is available here then there is an issue in reading the data from RDBMS to API-M.
I recommend you check the master-datasources.xml file which you edited during configuration. There may be an issue there, if the API Manager cannot connect to its' own database. The datasources given in step 2 of the guide you used are in addition to the existing datasources. If this isn't it, then please provide a stack dump or more detailed error messages. Cheers.
WSO2 experts
I downloaded the WSO2 AppFactory, but couldn't login into the web console with admin/admin. Has the default password changed?
Regards,
Terry
Please try with the following credentials
Username:admin#admin.com
password:admin
If you just tried with a downloaded 'binary' set-up of WSO2 App Factory; this will only allow you to log in to the Carbon admin console of the App Factory (If you just clicked on and visited the URL, that was printed on the server console). This Carbon admin console does not have any App Factory specific functionality which you might expect [WSO2 Carbon is the underlying platform which is used by all of the WSO2 products].
Since App Factory runs having few other servers alongside (such as WSO2 AS, WSO2 ELB, Jenkins, Redmine etc) this set up that you are running will not provide the same User interfaces or functionality which you have observed within the setup provided with https://appfactorypreview.wso2.com/samlsso .
I just thought to leave this answer, because; you would get disappointed after spending your time expecting the same Application (User Interfaces) available with the online setup (which I have mentioned with the hyperlink) by running the binary setup(wso2appfactory-1.0.0.zip) that you have downloaded from the WSO2 Web site.