I would like to know where does elmah bootstrapper store logs and how can i make a function to delete them. Nothing on the documentation says how to store them or where they are stored....
Thanks.
ELMAH Bootstrapper doesn't store logs anywhere. It's a tool to help configure ELMAH in a project. ELMAH, on the other hand, can store errors in a number of different destinations. There are loggers for in-memory, XML, SQL Server and much more. I've listed some of them in this ELMAH Tutorial.
The ELMAH documentation also have a list of the officially supported databases here: https://elmah.github.io/a/error-log-implementations/. For the full picture of ELMAH error loggers, you can check out this search on NuGet.org: https://www.nuget.org/packages?q=elmah. To mention a few, there are third-party loggers available for RavenDB, PostgreSQL and MongoDB.
Related
We are just configuring our first Microsoft CRM Portal using the Portals Add-In.
We are doing this in our sandbox, obviously. Question: How do we deploy this to our production system? As far as I see, most of the data is not saved in a solution but in entity records. Is there a practical way to deploy the stuff?
You’ll want to use the Portal Records Mover in the XRMToolbox. It will allow you to export/import the relevant records for the Portal.
https://community.dynamics.com/crm/b/dynamicscrmtools/archive/2017/06/13/new-xrmtoolbox-plugin-portal-records-mover
Alternatively, you can use the Configuration Migration tool (available in the SDK NuGet package) to move the records. I prefer the Portal Records Mover because it provides more granular control and supports updates without overwriting.
As suggested by #Nicknow use Configuration Migration and Portal Records Mover.
I would do the first transfer with the Configuration Migration and continue with Portal Records Mover where you can filter records that were updated on a given time frame.
You can also build your own SSIS package to filter the modified records and move them on the productive system.
Im trying to create a project with SonarQube web api, I can't find any good tutorial to create them.
I need to analyze a code and then get the information that SonarQube provides, I need to automatize all of this in a web application.
Is this possible to do with SonarQube web api?
The latest SonarQube versions have an api-documentation link. For SonarCloud you can find the documentation here. The documentation to create a new project is here. If you look at the details of api/projects/create you can see the parameters needed, the changelog and a response example. This API is available since version 4.0.
Please help me out to access the project specific information stored in my Sonar default server derby. As have very leass understading on it.
What I want to retrieve is very simple: it is just the information displayed on every sonar home page (http://localhost:9000/), that is to say the project name, the rules compliance indicator, the code coverage indicator and the build time...
Your guidance will be appreciable..
Thanks in advance..
You should not try to retrieve information directly from the database, for the DB is not an API and may change at any time without notice.
If you want to retrieve information stored by Sonar, please use Sonar Web Service API instead.
In order to know which revision number the application is built from, we use to give the ears we deploy to Glassfish names like myapp_2012-01-20_rev22123.ear. Then we can simply login to Glassfish and see what version is deployed in the web interface (as the appname is the name of the ear file). A downside of this approach is that we need to do a manual undeploy/redeploy to update the name...
But I would like to script the undeploy/deploy process, and having each version of an ear get a different name is not very suitable to scripting this redeployment process. Glassfish 2 does not support the "list applications" goal that Glassfish 3 has, which I could have used to retrieve the application name to undeploy.
So is there any good strategy that will easily allow us to see what version is deployed of an application, and that does not suffer from the above fault?
It would be preferable if this meant we did not have to change the existing applications (like add a jsp page or something to show the current scm revision), but a change in a Maven build script would be acceptable.
I faced a similar issue, I finally came around it by using maven-buildnumber-plugin and writing a simple servlet to get build information. You can find the details in the blog post I made.
Why not use the built-in GlassFish Server versioning to assign a version number at deploy time? This will also enable you to rollback to prior versions. For example:
asadmin deploy --name MyApplication:2012-01-20_rev22123 MyApplication.ear
There is more information on application versioning here:
http://docs.oracle.com/cd/E18930_01/html/821-2417/gihzx.html#gkhhv
Hope this helps.
Is it possible to create a new user in sonar without using the web interface?
I need to write a script that inserts the same users for some tools, including sonar.
There are three ways you can do this:
Write directly to the database (there is a simple table called users).
Use the LDAP plugin, if you specify sonar.authenticator.createUsers: true in sonar.properties, it will create the users in the sonar database automatically the first time they authenticate.
Write a java application that depends on the sonar plugin API, you can then use constructor injection to get a Sonar hibernate session and persist the user you want. See Here.
Since SonarQube version 3.6, there is support for user management in webservice API:
https://sonarqube.com/web_api/api/users
http://docs.sonarqube.org/display/DEV/Web+API
The web service API does not seem to support user management. Anything's possible, but it doesn't look like this is offered directly via Sonar.
You could probably use some web automation library (webbrowser, webunit, watir, twill) to do it through the running server; it might even be possible to just use something like 'curl' by looking carefully at the page source for the users/create form.
Or, if you want to go straight to the database, you could try to pull out the user creation functionality from the code and mess with the sonar.users table directly.
There is the LDAP Plugin, which would take care of authentication, but it still requires you to create the users in Sonar, so that wouldn't solve your problem.