During the approach of Angular 2 I have found a nice official documentation about the language and how to develop the very first project. On the opposite, no official documentation seems to be developed yet, to describe how to setup the various and possibile Angular 2 development environments, in particular using Eclipse. Ok, Eclipse seems to be not elected as the “best” IDE to develop on Angular 2, but a lot of developers are using it. To cover this need I would like to share in this post, the step-by-step setup of the first Angular 2 project, using the famous IDE.
It’s time to change something!
Let’s start from the theme of this blog.
New theme, new graphic and new challenges…
During the support activities on the A.A.A.R. solution, one of the most common request is about the success (or failure) of the extraction task from Alfresco. As a standard Business Intelligence solution, the extraction task is developed as a batch (called ETL process), in average executed during the night time.
How can you be sure that the extraction from Alfresco succeed or failed?
And how can you be sure that all the audit trail, the documents, the folders and workflow instances are correctly available into the analytic environment?
For those purpose, the brand new A.A.A.R. v4.4 release has been developed, together with some minor improvements you can fin detailed here in the change log.
“Eating our own dogfood and putting our trust in your Alfresco Community instance” has been the vision proposed at the BeeCon’16 by two known guys from the Order Of The Bee: marsband (aka Martin Cosgrave) and Digital Catalyst (aka Daren Firminger). The vision became real at the BeeCon’16 in two ways, at least:
- With a presentation talking about Honeycomb edition (and beyond).
- With an Alfresco Community instance, called buzzdoc, to support the speakers and organisers in the run up to the event.
Talking about the buzzdoc (the BeeCon’16 Alfresco instance for speakers and organisers) Digital Catalyst shares some interesting descriptions and numbers, using AAAR. To view the KPIs and to know further details, you can refer directly to the full article from Daren, at the link below.
Deleting of a large set of nodes from Alfresco is not an easy task using Alfresco Share or the repository’s API. After the probe to discover if your SolR index server is working or not, in this new project Francesco Fornasari and Cristian Tiralosi have developed another interesting stand alone application written in Java, to cover an interesting feature not easily available.
Do you want to know how to manually install A.A.A.R.?
Are you using the A.A.A.R. analytics over Alfresco and want to understand its scalability?
Do you want start to understand how to Dockerize A.A.A.R.?
Thank you Vincenzo!
After a stress test on a 2 milion documents repository, more than 6 milions of instances of custom types and aspects and 180.000 instances of workflows (everything on the same Alfresco instance). Together with two others different sources (a real Enterprise Record Management System and a ERP repository) the A.A.A.R. v4.3 has been released. This version has been tested on the brand new Pentaho 6.1 release, that comes with some relevant improvements on performance over JSON treatment and various other nice changes.
This release is dedicated to the incoming BeeCon event (to thank all of BeeGirls/BeeGuys for the support) and the Pentaho girls and guys for the sponsorship of the event.
As you probably know, the next 28-th and 29-th of April in Brussels, will happen the very first BeeCon. The place for the Alfresco community of professionals and enthusiasts to meet, share, learn, build, and enrich relationships.
Unfortunately this friendly event is less happy than expected, for the respect we all have for the victims of the recent tragedy. Said that, I would like to submit to your attention the brand new official agenda of the event with a lot of interesting contributions… all of them based on technical and practical topics.
I would like to personally invite all of you to talk, meet, share, learn about Content Intelligence on Alfresco and I’ll be pleased (as usual) to hear about interesting feedback about A.A.A.R., Alfresco, Pentaho and what you have done or what you would like to have from the analytics (a not only from the analytics).
Are you sure that the Solr Index Server of your production environment is updating your content?
As a consequence, are you sure that your Alfresco search indexes are correctly (and regularly) updated?
From a theoretical point of view, the answer is ‘yes’, but in a real life scenario, something could goes wrong and a message in our email box could arrive from your users, saying:
Hei fellow, the Alfresco installation that you are maintaining cannot find the documents I have uploaded a lot of time ago: this is not acceptable!
In this post is described a project that has, as its main goal, to avoid this awful issue. The project is called Solr probe (solr-probe) ad it is available on GitHub, for Solr versions greater than 1.4 (the one used from a lot of Alfresco versions).