We are using WSO2esb-4.8.1.
We want to use the WSO2 GUI to view the tenant specific log. But we are getting the following message always when we navigate to Monitor--> Application Logs.
The log must be configured to use the org.wso2.carbon.logging.core.util.MemoryAppender to view entries on the admin console
I found that in the log4j.properties, the following is used
log4j.appender.CARBON_MEMORY=org.wso2.carbon.logging.appender.CarbonMemoryAppender
I changed this to
log4j.appender.CARBON_MEMORY=org.wso2.carbon.logging.core.util.MemoryAppender
The issue remains though.
By default, when you install WSO2 4.8.1, Esb, it installs the Logging Management 4.2.1
With this, the logs are visible in the GUI. It works as expected.
But later, if you install any other feature , that includes a higher version of logging management (eg:- in our case, we installed data services 3.1.1 that includes logging management feature 4.2.2), the GUI stops working.
All I did was unchecking the logging feature in data services 3.1.1 when installing data services. This way, the logging feature did not get upgraded, but the rest of the data services did.
Related
I'm working with WSO2 Identity Server and I'm curious if there is a way to run the product in developer mode without building each component of identity server. I found a way to start the "My Account" component in dev mode by following this tutorial ( https://is.docs.wso2.com/en/5.11.0/develop/setting-up-my-account-in-a-dev-environment/ )
but I want to be able to modify different components such as recovery-portal and authentication-portal by forking and cloning the required github repositories and starting the entire app in developer mode in order to see the code changes in real-time.
AFAIK the developer mode will work only for the MyAccount and Console. You can refer to the doc for more details on that.
The recovery portal, the authentication portal etc. cannot be tried with the developer mode. However, there are two ways that you can try this.
Build the war files manually and add them to the WebApps directory. If the server is running, war file changes will automatically get deployed. If the server is not running, you have to delete the existing directory and restart the server.
You can do the changes to the JSPs that are deployed inside the pack. Once the changes are done, you can save the changes and the changes will automatically get deployed.
I'm currently experimenting/working on WSO2. What i'm trying to do is to have Data Analytics server configured. I started by following the below specified URL
https://docs.wso2.com/display/AM210/Configuring+APIM+Analytics#9d6747f5c0074928b18599abe472987d (Quick Steps)
After performing all the steps, i get the following issue on APIM cmd prompt
YES Its pretty evident from the error that no such table exists BUT that is exactly the issue i'm facing. What could really be the cause here?
Consider the following points:
I've not followed ALL the steps mentioned on
https://docs.wso2.com/display/DAS310/Getting+Started (BUT are they
required?)
In the installation prerequisites for DAS, JDBC-compliant Connector for Java is required which I've not yet installed (BUT its not mandatory at the same time)
Most of the QUICK STEPS for the configuration of DAS in the specified URL i.e. https://docs.wso2.com/display/AM210/Configuring+APIM+Analytics#9d6747f5c0074928b18599abe472987d where already in place and i only had to
Set Up JDK, ANT, Maven
enable the analytics section in the API-M_HOME/repository/conf/api-manager.xml
add log4j.rootLogger=, DAS_AGENT to API-M_HOME/repository/conf/log4j.properties
add snappy-java_1.1.1.7.jar to DAS_HOME\repository\components\lib
Yet the issue persists, Do let me know of what you think. Thank you
Since you are following quick start guide please extract the WSO2 API Manager and the WSO2 API-M Analytics distributions (zip files), to the same directory (preferably an empty directory).
Also, you need to generate some traffic to the published APIs in order to analytics server to create this table for the first time.
I'm looking for some guidance about two specific WSO2 products, API Manager and Identity Server and for the best solution to solve the problem I'm going to explain below.
In my company, we are using ADFS 3.0 for Single Sign On support in our applications. However we are now building applications that will require OpenID Connect Specification (SPA's+Rest API's) and ADFS does not support this out of the box so we've decided to use WSO2 products for that purpose.
I already managed to install WSO2 Identity Server 5.0.0 SP1 and configured ADFS as a federated Identity Provider (the new applications will still have to authenticate users using ADFS). I also installed WSO2 API Manager 1.9.1 and configured it to use WSO2 Identity Server as the Key Manager (Configuration tutorial).
Now the problem:
Using WSO2 Identity Server 5.0.0 SP1 I couldn't get the Logout feature to work due to the issue reported here. It seems that this issue has been solved in version 5.1.0M4 so I tried to install version 5.1.0-alpha and managed to make the logout to work with ADFS (I tested it by enabling SSO for the carbon administration). However, now I'm not able to install the Key Manager feature through the carbon repositories due to incompatibilities.
As a result, with the first combination (wso2is 5.0.0 SP1/wso2am 1.9.1) I had the logout issue with ADFS and with the second combination (wso2is 5.1.0-alpha/wso2am 1.9.1), I'm not able to install the Key Manager feature in Identity Server.
Is there any way to apply a patch to solve the logout issue in the first combination? Is there a way to install the key manager feature on WSO2IS 5.1.0-alpha? Or can someone point me to another solution to solve this issue?
The issue you pointed above, marked as it type as "Patch". Usually that means WSO2 have fixed this issue for a earlier version and provided a patch to its customer. Easiest thing would be, if you are already a customer of WSO2 ask for the patch directly from their support.
If you are not a paid customer of WSO2 you are in bit of a trouble. As per this question, the source of the Service Pack also not available in public.
But luckily in your case, the component which need to have this fix not a core component. So you wouldn't be in trouble if you change the authenticator code bit. But the warning is, it would lose any fixes done for org.wso2.carbon.identity.application.authenticator.samlsso_4.2.1.jar in the service pack.
Anyway, these are the steps you should follow.
Checkout the source. Lazy path would be checkout the whole source from here. That is the most easy way which you will face less troubles when you try to build the source but the downside of that is, it would take bit of time to checkout. If you know how to build specific component from WSO2 source, you can directly checkout component it needed to changed.
Try to build the component without doing any change just to make sure there are not any issues upto this point.
Goto the class DefaultSAML2SSOManager and do the same change done in the PR.
Build the component again.
Create folder named like "patch9000" inside the <IS_HOME>/repository/components/patches/ folder.
Copy build jar (org.wso2.carbon.identity.application.authenticator.samlsso-4.2.1.jar ) in step 4 from the target folder to the <IS_HOME>/repository/components/patches/patch9000 folder.
Restart the server. If you have done everything to the point, in the server startup it would print a log like, org.wso2.carbon.server.extensions.PatchInstaller - Patch changes detected
Now retry the your flow and it would work as expected.
If you too lazy to do all above, you can wait until Identity Server Service Pack 2, which will have your fix.
I am trying to setup nuget custom server, and cannot get it list my packages.
Here is list which I verified:
Server updated to .net 4.5
OS is Windows Web Server 2008 R2
Application pool is set to integrated, dotnet set to 4.0
modules runAllManagedModulesForAllRequests="true" is present
mime map is present in web.config, and visible by IIS
I am able to download file with direct link
i am able to push package to my server
So, when I go to http://servername.com i see nice:
You are running NuGet.Server v2.7.40911.225
Click here to view your packages.
but http://servername.com/nuget returns 404. Probably there is issue with original nuget routing.
It sounds to me like the ODATA routes are just not being picked up. Did you check that nothing is overriding this at the machine.config level? You may also want to check that your package path is configured, and the web app has permission to access it.
One thing that might be easier to do is to install a third-party NuGet server such as ProGet; it's free and installs pretty easily, and also will be a bit more robust in terms of features.
(disclaimer: I work for Inedo)
I have downloaded WSO2 appfacotry and ran it locally for testing purposes. It first gives carbon login and in the running application list I could see the /appmgt jaggery application is running. Then I tried to go to the url through the link provided in Action column in that application list. Initially I was routed to http://{some_ip_address}:9763/appmgt/ and then I was re routed to https://appfactory.example.com:9443/samlsso which gives me error. (because I don't have appfacotry.example.com domain.) How can I run appfactory without this faulty URL?
Here's documentation on installing App Factory: https://docs.wso2.com/display/AF201/Installing+On-Premise
Also, note that there is now a hosted version, which you can use in the cloud with no configuration required: http://wso2.com/cloud/app-cloud/
Other than the 3rd party tools mentioned above, you need App Factory, AS, API manager, Stratos Controller and ELB to have all App Factory features