I installed both WSO2 AM and DAS on same machine and make offset 3 ( 3) for DAS server. But cannot see statistics dashboard in api manager.
Configure Analytics:
Statistics in AM:
DAS only summarizes the statistics in 5 minutes intervals. Eg: 10:00, 10:05, 10:10, ... (fixed intervals in a day). Therefore, until the first 5 minutes are passed (if current time is 10:03, it will happen in 10:05), the summarized tables will not be created in DAS and publisher/store cannot retrieve that information during that time so the default image will be displayed. After that time period, you will be able to see the statistics in the first 5 minutes interval. Next update will happen after another 5 minutes, therefore the API invocations you do after first 5 minutes will be included in the statistics after another 5 minutes an so forth. So you should be able to see the updated summarized statistics of API usages after every 5 minute intervals.
You can verify that the data is published into DAS by login to DAS management console, go to data explorer in the main tab. Then select the table: ORG_WSO2_APIMGT_STATISTICS_REQUEST. You will able to see the information of all API requests you have sent. After 5 minutes interval is passed, you should be able to see API_VERSION_USAGE_SUMMARY table as well, which stores the summarized usage data from which publisher and store retrieves that information. Could you please verify them in the DAS node.
Please follow the steps as below. As this step already done, skipping it.
As you have started API Manager node already pointing to DAS node, it will create some Stream Definitions as below. Navigate to WSO2 DAS Management console open Main -> event -> streams. Delete any stream that has got created. (please see das_stream.png below)
Copy [APIM_HOME]/statistics/API_Manager_Analytics_REST.car file into [DAS_HOME]/repository/deployment/server/carbonapps. Folder carbonapps will not be there by default. You need to create manually. One done you will see below logs in DAS console.
TID: [-1234] [] [2016-08-05 10:28:56,803] INFO {org.wso2.carbon.application.deployer.internal.ApplicationManager} - Deploying Carbon Application : API_Manager_Analytics_REST.car... {org.wso2.carbon.application.deployer.internal.ApplicationManager}
TID: [-1234] [] [2016-08-05 10:28:57,275] INFO {org.wso2.carbon.event.stream.core.EventStreamDeployer} - Stream definition is deployed successfully : org_wso2_apimgt_statistics_destination:1.0.0 {org.wso2.carbon.event.stream.core.EventStreamDeployer}
TID: [-1234] [] [2016-08-05 10:28:57,278] INFO {org.wso2.carbon.event.stream.core.EventStreamDeployer} - Stream definition is deployed successfully : org.wso2.apimgt.statistics.fault:1.0.0 {org.wso2.carbon.event.stream.core.EventStreamDeployer}
TID: [-1234] [] [2016-08-05 10:28:57,280] INFO {org.wso2.carbon.event.stream.core.EventStreamDeployer} - Stream definition is deployed successfully : org.wso2.apimgt.statistics.request:1.0.0 {org.wso2.carbon.event.stream.core.EventStreamDeployer}
TID: [-1234] [] [2016-08-05 10:28:57,281] INFO {org.wso2.carbon.event.stream.core.EventStreamDeployer} - Stream definition is deployed successfully : org.wso2.apimgt.statistics.response:1.0.0 {org.wso2.carbon.event.stream.core.EventStreamDeployer}
TID: [-1234] [] [2016-08-05 10:28:57,282] INFO {org.wso2.carbon.event.stream.core.EventStreamDeployer} - Stream definition is deployed successfully : org.wso2.apimgt.statistics.workflow:1.0.0 {org.wso2.carbon.event.stream.core.EventStreamDeployer}
TID: [-1234] [] [2016-08-05 10:28:57,282] INFO {org.wso2.carbon.event.stream.core.EventStreamDeployer} - Stream definition is deployed successfully : org.wso2.apimgt.statistics.throttle:1.0.0 {org.wso2.carbon.event.stream.core.EventStreamDeployer}
TID: [-1234] [] [2016-08-05 10:28:57,291] INFO {org.wso2.carbon.event.input.adapter.core.internal.InputAdapterRuntime} - Connecting receiver EventReceiver_destination {org.wso2.carbon.event.input.adapter.core.internal.InputAdapterRuntime}
TID: [-1234] [] [2016-08-05 10:28:57,292] INFO {org.wso2.carbon.event.stream.core.internal.EventJunction} - Producer added to the junction. Stream:org_wso2_apimgt_statistics_destination:1.0.0 {org.wso2.carbon.event.stream.core.internal.EventJunction}
TID: [-1234] [] [2016-08-05 10:28:57,292] INFO {org.wso2.carbon.event.receiver.core.EventReceiverDeployer} - Event Receiver configuration successfully deployed and in active state: EventReceiver_destination {org.wso2.carbon.event.receiver.core.EventReceiverDeployer}
TID: [-1234] [] [2016-08-05 10:28:57,293] INFO {org.wso2.carbon.event.input.adapter.core.internal.InputAdapterRuntime} - Connecting receiver EventReceiver_fault {org.wso2.carbon.event.input.adapter.core.internal.InputAdapterRuntime}
TID: [-1234] [] [2016-08-05 10:28:57,293] INFO {org.wso2.carbon.event.stream.core.internal.EventJunction} - Producer added to the junction. Stream:org.wso2.apimgt.statistics.fault:1.0.0 {org.wso2.carbon.event.stream.core.internal.EventJunction}
TID: [-1234] [] [2016-08-05 10:28:57,293] INFO {org.wso2.carbon.event.receiver.core.EventReceiverDeployer} - Event Receiver configuration successfully deployed and in active state: EventReceiver_fault {org.wso2.carbon.event.receiver.core.EventReceiverDeployer}
TID: [-1234] [] [2016-08-05 10:28:57,294] INFO {org.wso2.carbon.event.input.adapter.core.internal.InputAdapterRuntime} - Connecting receiver EventReceiver_request {org.wso2.carbon.event.input.adapter.core.internal.InputAdapterRuntime}
TID: [-1234] [] [2016-08-05 10:28:57,294] INFO {org.wso2.carbon.event.stream.core.internal.EventJunction} - Producer added to the junction. Stream:org.wso2.apimgt.statistics.request:1.0.0 {org.wso2.carbon.event.stream.core.internal.EventJunction}
TID: [-1234] [] [2016-08-05 10:28:57,294] INFO {org.wso2.carbon.event.receiver.core.EventReceiverDeployer} - Event Receiver configuration successfully deployed and in active state: EventReceiver_request {org.wso2.carbon.event.receiver.core.EventReceiverDeployer}
TID: [-1234] [] [2016-08-05 10:28:57,294] INFO {org.wso2.carbon.event.input.adapter.core.internal.InputAdapterRuntime} - Connecting receiver EventReceiver_response {org.wso2.carbon.event.input.adapter.core.internal.InputAdapterRuntime}
TID: [-1234] [] [2016-08-05 10:28:57,295] INFO {org.wso2.carbon.event.stream.core.internal.EventJunction} - Producer added to the junction. Stream:org.wso2.apimgt.statistics.response:1.0.0 {org.wso2.carbon.event.stream.core.internal.EventJunction}
TID: [-1234] [] [2016-08-05 10:28:57,295] INFO {org.wso2.carbon.event.receiver.core.EventReceiverDeployer} - Event Receiver configuration successfully deployed and in active state: EventReceiver_response {org.wso2.carbon.event.receiver.core.EventReceiverDeployer}
TID: [-1234] [] [2016-08-05 10:28:57,295] INFO {org.wso2.carbon.event.input.adapter.core.internal.InputAdapterRuntime} - Connecting receiver EventReceiver_workflow {org.wso2.carbon.event.input.adapter.core.internal.InputAdapterRuntime}
TID: [-1234] [] [2016-08-05 10:28:57,295] INFO {org.wso2.carbon.event.stream.core.internal.EventJunction} - Producer added to the junction. Stream:org.wso2.apimgt.statistics.workflow:1.0.0 {org.wso2.carbon.event.stream.core.internal.EventJunction}
TID: [-1234] [] [2016-08-05 10:28:57,295] INFO {org.wso2.carbon.event.receiver.core.EventReceiverDeployer} - Event Receiver configuration successfully deployed and in active state: EventReceiver_workflow {org.wso2.carbon.event.receiver.core.EventReceiverDeployer}
TID: [-1234] [] [2016-08-05 10:28:57,296] INFO {org.wso2.carbon.event.input.adapter.core.internal.InputAdapterRuntime} - Connecting receiver EventReceiver_throttle {org.wso2.carbon.event.input.adapter.core.internal.InputAdapterRuntime}
TID: [-1234] [] [2016-08-05 10:28:57,296] INFO {org.wso2.carbon.event.stream.core.internal.EventJunction} - Producer added to the junction. Stream:org.wso2.apimgt.statistics.throttle:1.0.0 {org.wso2.carbon.event.stream.core.internal.EventJunction}
TID: [-1234] [] [2016-08-05 10:28:57,296] INFO {org.wso2.carbon.event.receiver.core.EventReceiverDeployer} - Event Receiver configuration successfully deployed and in active state: EventReceiver_throttle {org.wso2.carbon.event.receiver.core.EventReceiverDeployer}
TID: [-1234] [] [2016-08-05 10:28:57,299] INFO {org.wso2.carbon.analytics.spark.core.SparkScriptCAppDeployer} - Deploying spark script: APIM_STAT_SCRIPT.xml for tenant : -1234 {org.wso2.carbon.analytics.spark.core.SparkScriptCAppDeployer}
TID: [-1234] [] [2016-08-05 10:28:57,366] INFO {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task scheduled: [-1234][ANALYTICS_SPARK][APIM_STAT_SCRIPT] {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager}
TID: [-1234] [] [2016-08-05 10:28:57,367] INFO {org.wso2.carbon.analytics.spark.core.SparkScriptCAppDeployer} - Deploying spark script: APIM_STAT_SCRIPT_THROTTLE.xml for tenant : -1234 {org.wso2.carbon.analytics.spark.core.SparkScriptCAppDeployer}
TID: [-1234] [] [2016-08-05 10:28:57,394] INFO {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} - Task scheduled: [-1234][ANALYTICS_SPARK][APIM_STAT_SCRIPT_THROTTLE] {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager}
TID: [-1234] [] [2016-08-05 10:28:57,396] INFO {org.wso2.carbon.application.deployer.internal.ApplicationManager} - Successfully Deployed Carbon Application : APIM_STAT_CAPP_v1.0.3 {super-tenant} {org.wso2.carbon.application.deployer.internal.ApplicationManager}
Go to data explorer window on DAS and make sure you see the tables in drop down.
Restart DAS server to clear up in-memory held information.
Publish some stats (invoke APIs)
Wait for some time and let analytic scripts run. If you need to manually run them navigate to main -> Batch Analytics -> Scripts and execute them.
Access API Manager statistics via API Manager publisher/subscriber pages. (please see store_analytics.png below)
Hope this information helps you.
Related
Im getting the following error while login to the management console of Identity server,
TID: [-1234] [] [2018-05-15 02:39:04,415] ERROR {org.wso2.carbon.user.core.common.AbstractUserStoreManager} - Error occurred while accessing Java Security Manager Privilege Block
TID: [-1234] [] [2018-05-15 02:39:04,415] ERROR {org.wso2.carbon.core.services.authentication.AuthenticationAdmin} - System error while Authenticating/Authorizing User : Error when handling event : PRE_AUTHENTICATION
I have configured the jdbc user store for the user management. What is issue ?
When i have a single adfs configured as a identity server on wso2, authentication from wso2 fails with the below error.
ator returned: INCOMPLETE TID: [-1234] [] [2017-02-24 06:50:04,580]
DEBUG
{org.wso2.carbon.identity.application.authentication.framework.handler.step.impl.DefaultStepHandler}
- SAMLSSOAuthenticator is redirecting TID: [-1234] [] [2017-02-24 06:50:04,580] DEBUG
{org.wso2.carbon.identity.application.authentication.framework.handler.sequence.impl.DefaultStepBasedSequenceHandler}
- Step is not complete yet. Redirechttp://stackoverflow.com/questionsting to outside. TID: [-1234]
[] [2017-02-24 06:50:09,958] DEBUG
{org.wso2.carbon.identity.application.authentication.framework.util.FrameworkUtils}
- Authentication Context is null TID: [-1234] [] [2017-02-24 06:50:09,959] DEBUG
{org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator}
- Session data key is null in the request TID: [-1234] [] [2017-02-24 06:50:09,959] ERROR
{org.wso2.carbon.identity.application.authentication.framework.handler.request.impl.DefaultRequestCoordinator}
- Context does not exist. Probably due to invalidated cache
At the same time if there are more than one federated authentication say 2 adfs servers configured on wso2 as identity server and using the advanced configuration option on wso2-sp , authentication from travelocity is happening fine.
please guide what am i missing here.
This is supported out-of-the-box with Identity Server 5.1.0 M3 onwards. If you are to use this with Identity Server 5.0.0 (with SP 1) you’ll need to some modifications to the source. The details can be found at [1] & [2].
Follow Document[3] for more details for Setting ADFS 3.0 as a Federated Authenticator in WSO2 Identity Server
[1] - https://wso2.org/jira/browse/IDENTITY-3181
[2] - https://wso2.org/jira/browse/IDENTITY-3349
[3] - https://omindu.wordpress.com/2015/06/19/setting-ad-fs-3-0-as-federated-authenticator-in-wso2-identity-server/
Why can't I upload the API Analytics car into the API Manager admin?
There is a warning that says :
Undeploying Faulty Carbon Application On : C:\WSO2AM~1.0\bin\..\repository\deployment\server\carbonapps\API_Manager_Analytics.car {org.wso2.carbon.application.deployer.CappAxis2Deployer}
TID: [-1234] [] [2016-09-23 14:36:10,436] INFO {org.wso2.carbon.application.deployer.internal.ApplicationManager} - Deploying Carbon Application : API_Manager_Analytics.car... {org.wso2.carbon.application.deployer.internal.ApplicationManager}
TID: [-1234] [] [2016-09-23 14:36:10,618] WARN {org.wso2.carbon.application.deployer.internal.ApplicationManager} - No artifacts found to be deployed in this server. Ignoring Carbon Application : API_Manager_Analytics.car {org.wso2.carbon.application.deployer.internal.ApplicationManager}
First of all, Analytics car files should be installed in DAS, not in APIM.
If you want to install any (other) car file in APIM, make sure you set Server Role as Api Manager in each artifact in the car.
I have setup WSO2 Identity server 5.0.0 on Windows 2012 R2 server.
I changed the primary user store to Active Directory following the instructions from WSO2 Documentation.
https://docs.wso2.com/display/IS500/Configuring+an+Active+Directory+User+Store
Since then i am not able to login into the Identity server Management Console.
I tried to login with the AD admin user as well as the WSO2 admin user, none of them work. Below are the errors from the log.
**TID: [0] [IS] [2016-01-05 10:17:22,965] WARN {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} - Failed Administrator login attempt 'wso2\test1[-1234]' at [2016-01-05 10:17:22,965+0000] {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil}
TID: [0] [IS] [2016-01-05 10:17:35,420] WARN {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} - Failed Administrator login attempt 'test1[-1234]' at [2016-01-05 10:17:35,418+0000] {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil}
TID: [0] [IS] [2016-01-05 10:17:46,485] WARN {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} - Failed Administrator login attempt 'admin[-1234]' at [2016-01-05 10:17:46,485+0000] {org.wso2.carbon.core.services.util.CarbonAuthenticationUtil}**
Below is the user-mgt xml file.
http://pastebin.com/zTJ2SJmN
Any help is greatly appreciated ..!!!
Thanks you
Kbasa
I'm using the WSO2 ESB version 4.0.3, with some features installed like: Identity Provider, Identity SAML2.0 Single Sign-on, Identity XACML, also BPEL, Data Services Hosting etc.
Following the instructions from here, I set up SSO Authentication for the ESB Management Console. The sign-in works just fine, but not the sign-out. In the log I can see the following information:
TID: [] [WSO2 ESB] [2012-06-08 18:12:59,592]
INFO {org.wso2.carbon.identity.authenticator.saml2.sso.SAML2SSOAuthenticator} -
'admin' logged out at [2012-06-08 18:12:59,0592]
{org.wso2.carbon.identity.authenticator.saml2.sso.SAML2SSOAuthenticator}
after what I get errors. Furthermore, in the browser shows like I'm still logged in.
Here are the errors I'm getting:
TID: [] [WSO2 ESB] [2012-06-08 18:13:03,581]
WARN {org.wso2.carbon.server.admin.module.handler.AuthenticationHandler} -
Illegal access attempt at [2012-06-08 18:13:03,0581] from IP address :
Service is RegistryAdminService {org.wso2.carbon.server.admin.module.handler.AuthenticationHandler}
TID: [] [WSO2 ESB] [2012-06-08 18:13:03,584]
ERROR {org.apache.axis2.engine.AxisEngine} -
Access Denied. Please login first. {org.apache.axis2.engine.AxisEngine}
...
TID: [] [WSO2 ESB] [2012-06-08 18:13:03,599]
ERROR {org.wso2.carbon.ui.clients.RegistryAdminServiceClient} -
Error occurred while checking registry mode {org.wso2.carbon.ui.clients.RegistryAdminServiceClient}
org.apache.axis2.AxisFault: Access Denied. Please login first.
...
TID: [] [WSO2 ESB] [2012-06-08 18:13:03,879]
ERROR {org.wso2.carbon.server.admin.ui.ServerAdminClient} -
Cannot get server data. Backend service may be unavailable {org.wso2.carbon.server.admin.ui.ServerAdminClient}
org.apache.axis2.AxisFault: Access Denied. Please login first.
Am I missing something in the configuration? If not, can someone please explain what is happening?
Note: The errors are repeating.
These repetitive errors means you are logged out from the back end, and it tries to refresh a page like Carbon home page or statistics page by invoking the corresponding BE services.
Is WSO2 IS running as a separate node or the necessary IdP features are installed in ESB?
Thilina