| |
|
Rinaldo Bonazzo's Blog, outdoor passionate - sometimes likes to blog about Disruptive Technology #EnterprisePortal #BigData #Analytics #Cloud #Iot #node.js ...
Showing posts with label entando. Show all posts
Showing posts with label entando. Show all posts
Thursday, October 2, 2014
Cagliari Code Week 2014 - Creating a portal from Scratch
Cagliari Code Week 2014, al via una settimana dedicata alla programmazione
“In principio doveva essere un evento di uno o due giorni”, così ci racconta Raffaella Sanna dell’Associazione no-profit Sardegna 2050 una delle promotrici dell’evento Cagliari Code Week 2014. “Poi, grazie all’entusiasmo ed alla partecipazione di tanti si è trasformato in una settimana ricca e piena di iniziative”.
Leggi tutto il post
Leggi tutto il post
Thursday, April 24, 2014
Japsersoft BI Suite Tutorials: Drill down functionality example on HTML-5 charts ...
Hi Guys,
I have read and test the latest post from Sadakar. I must say that it allowed me to better understand some tip on how to manage drill down with HTML5 and Jasper Studio. This will allow me to review the Entando / Jaspersoft connector and provide more dynamic effects in the presentation in dashboards and graphs.
Read it
I have read and test the latest post from Sadakar. I must say that it allowed me to better understand some tip on how to manage drill down with HTML5 and Jasper Studio. This will allow me to review the Entando / Jaspersoft connector and provide more dynamic effects in the presentation in dashboards and graphs.
Read it
Thursday, November 21, 2013
Sunday, September 8, 2013
Boostrap in practice
Entando R&D director William Ghelfi has completed his book on #Bootstrap! Grab the first chapter for free!
Bootstrap in practice
Bootstrap in practice
Friday, September 6, 2013
Wednesday, June 12, 2013
Create an Entando Page Template Bundle
From Entando blog
Here the link where you can find all the file mentioned in the section:
Rinaldo
In the latest Entando versions a new object is coming "Bundles".Read it
BUNDLE! what is this?
Bundles are "off-the-shelf" solutions website which developers can seamlessly add to their portal ie
- Page Templates
- Type of Contents (ie News, Announcements, ...)
- Widgets
Here the link where you can find all the file mentioned in the section:
We need now to update the following filesRegards
Rinaldo
Thursday, May 23, 2013
Entando Dublin Bootcamp 15th May 2013
For all those who was present at the bootcamp in Dublin 15th May 2013 and ... ;) yes also for those that did not could partecipate, here found the link where you can find the slides of my talk.
For those who want more info on the platform I'm available for confcall contact me r (dot) bonazzo (at) entando (dot) com
(y)
GitHub workflows inside of a company | NCZOnline
very useful post for all those who use github (ie Entando on GitHub) or think to use it
GitHub workflows inside of a company | NCZOnline:
'via Blog this'
GitHub workflows inside of a company | NCZOnline:
'via Blog this'
Friday, May 10, 2013
Your portal with Entando
You are curious to see how you can create a portal with Entando, nothing more simple.
I urge you to read this Trumbitta guide "Entando: an unexpected journey. Or, my portal from scratch."
Good Entando to all
Rinaldo
Labels:
entando,
GitHub,
jetty,
Maven,
Open Source
Monday, April 22, 2013
Entando Wiki
Today I want to talk about the Entando Wiki.
Why?
Well as you know Entando version 3.2 was launched on the web and therefore as each new version it is necessary to review all the technical documentation.
The development team is in the process to complete this process and is has already releasing the most important document to permit you to start developing using this new version.
So click here to access the Entando Wiki page on GitHub.
At the moment available documents are (I changed the order of the list of documents to try to follow a logical order that seems most consistent for me )
Why?
Well as you know Entando version 3.2 was launched on the web and therefore as each new version it is necessary to review all the technical documentation.
The development team is in the process to complete this process and is has already releasing the most important document to permit you to start developing using this new version.
So click here to access the Entando Wiki page on GitHub.
At the moment available documents are (I changed the order of the list of documents to try to follow a logical order that seems most consistent for me )
General documentation
- Setup a Java development environment for the Entando Platform
This document explains how to setup a development environment for Java developers. Those who are approaching "Entando" for the first time will find all the software needed in the first place to run, and then a few configuration hints to develop on the Entando platform. - The Entando Model
This is an overall view of the model of the platform. Users, Groups, Contents etc. are introduced from an high level perspective, without going too deep in the subject. - Entando: an unexpected journey. Or, my portal from scratch.
This guide shows how to create a new portal from scratch in minutes. - Pattern for application services creation and integration
This developers-oriented document shows the way and the conventions adopted to create Application Services in the Entando core. - Plugin Pattern
This guide explains how to create applications services in form of Entando plugins. - Entando Rest API Engine
This guide shows how to implement a REST based service - Build an Entando portal
The material contained in this page resumes some of the concepts already seen in the Entando Model, to deepen subjects such as Pages, Contents and Widgets; the aim is to provide quick information to build a portal. - Entando in production: how to prepare a server, how to deploy your Entando based application
This step-by-step guide shows to system or network administrators how to setup a basic server where to deploy your project. - Migration from Entando 3.0 to 3.2
This step by step guide shows the procedure to port the core of your Entando 3.0 installation to version 3.2
Wednesday, April 17, 2013
Becoming an Entando developer
Did you know that you can write applications that work with content stored in Entando? With our Public API, you can query, update, and delete contents, resources stored in your Entando portals.
Becoming an Entando developer costs nothing and you can create as many API keys as you need. Documentation, sample code, and other resources can be found on the Entando Developer Portal at Entando GitHub
Monday, February 25, 2013
Entando - Open Data Italian Election 2013 Results
Need realtime results from Cagliari Municipality?
For Senate of the Republic Results use one of the following REST API'S call
http://www.comune.cagliari.it/portale/api/rs/it/cagliari/risultatiElezioni.xml?idElezione=82&sezione=true (if you need polling station details, false otherwise)
http://www.comune.cagliari.it/portale/api/rs/it/cagliari/risultatiElezioni.json?idElezione=82&sezione=true (if you need polling station details, false otherwise)
For Chamber of Deputies Results use one of the following REST API's call
http://www.comune.cagliari.it/portale/api/rs/it/cagliari/risultatiElezioni.xml?idElezione=83&sezione=true (if you need polling station details, false otherwise)
http://www.comune.cagliari.it/portale/api/rs/it/cagliari/risultatiElezioni.json?idElezione=83&sezione=true (if you need polling station details, false otherwise)
For Senate of the Republic Results use one of the following REST API'S call
http://www.comune.cagliari.it/portale/api/rs/it/cagliari/risultatiElezioni.xml?idElezione=82&sezione=true (if you need polling station details, false otherwise)
http://www.comune.cagliari.it/portale/api/rs/it/cagliari/risultatiElezioni.json?idElezione=82&sezione=true (if you need polling station details, false otherwise)
For Chamber of Deputies Results use one of the following REST API's call
http://www.comune.cagliari.it/portale/api/rs/it/cagliari/risultatiElezioni.xml?idElezione=83&sezione=true (if you need polling station details, false otherwise)
http://www.comune.cagliari.it/portale/api/rs/it/cagliari/risultatiElezioni.json?idElezione=83&sezione=true (if you need polling station details, false otherwise)
Monday, February 11, 2013
Introduction to Entando Architectural Model
Hi guys,
today I present to you the last post published on the blog Entando:
Entando architectural model is composed by three layers:
- Data Access Layer: It is composed by all the elements which superintend the Persistence Layer. The main component are the DAO classes (Data Access Object) which are the only linking element between the framework and the data sources (Database, Filesystem, LDAP service directory etc.)
- Business Layer: This is the core of the system. Here the concept of Entando service as manager of every macro functionality, takes place. This layer is built upon the Spring Framework, whose listener, during the system start-up, initializes all the services and injects them in the web application context as beans. The Business Layer utilizes the Data Access layer to get the data needed, gives to the higher layer (the Presentation layer) the elements to display and supports it in the execution of actions.
- the Portal View, referred to as Front-end
- Presentation Layer: the aim of this layer is to build the graphic interfaces which represent the mean through which the users interact with the system. This layer gives a pure View layer (that is, a JSP without any business logic) and a "slim" controller (which checks the consistency of the data submitted and serves the data produced); both of them provide support to the layer below, the Business Layer. In the Entando framework this layer is divided in two parts:
- the Administration View referred to as Back-end
read more.
Sunday, January 27, 2013
Entando: Pattern for Application Services creation and integration
I suggest you read the new document that will help you to develop new Entando Applications Services
Read the doc
Read the doc
Thursday, January 24, 2013
Thursday, January 3, 2013
Entando Technical Series - Part 2
As promised I'm back to talk about Entando, today I'll present the second article in the Entando technical series.
I'll talk about the Entando Core Services.
I'll talk about the Entando Core Services.
Before starting I suggest you to take a look at the package com.agiletec.aps.system.services in the Core Engine Entando, you can download it from https://github.com/entando/entando-core-engine
The Entando Core Services layer contains the business logic for the portal platform, the plugin included out of the box, the external data Services, The External Application Services, the UI Control and the REST API public interface.
The following lists present the basic services that are provided by default by Entando
- authorization this is the service that manages and verifies the permissions to access the portal displaying all the necessary methods
- baseconfig this is the service that manage the configuration. The configuration consists of items , identified by a name, and parameters (Parameters can be Simple strings or Complex XML texts)
- cache this is the service that manage the System cache it’s based on the EhCache library.
- category this is the service that manage the Category tree
- controller this is the service that controls the execution of a request from the client. The execution is carried out in sequence by invoking any other services specified in configuration
- group this is the service that manage the user’s group
- i18n this is the service that provides strings/labels based on the used language(local). The strings/labels are specified by an identification key and the reference language.
- keygenerator as Entando doesn't use the Db sequences generator, for be independent from different players (mySql, Oracle, Postgresql,...) we had create our own sequence service
- lang this is the service that manage the different language used in the portal.
- page this is the service that manage the pages. Pages are held in a tree-like structure, to allow a hierarchical access.
- pagemodel this the service that manage the pagemodel. An Entando portal can have multiple templates, these “templates” are called Page Models (more info http://blog.entando.com/eblog/pages/en/homepage/view_post/?contentId=BLG25)
- role this is the service that manage the different users role present in the portal (for ie administrator, editor, guest, …)
- showlettype this the service that manage the different showlet(*) type used in the portal
- url this is the service that manage URL and creates a full URL to a portal page based on essential information
- user this is the service that manage the users registered in the portal
That's it for now. I expect you all to my next post
(*) Showlets are a key element in the creation of portals with Entando. In short Showlets are dynamic blocks of the portal, all those elements that are expected to want to move, adapt or change in the handling of the pages.(I will talk more in detail about showlet in a later post )
Saturday, December 22, 2012
Entando for government
Government agencies need to adopt innovative models and tools to improve quality service to citizens at a reduced cost. This is an overview about how Entando's platform effciently solves issues ...
Open Data with Entando
Need to know how to manage Open Data with Entando?
Have a look at this slideshare presentation.
I wish you a Merry Christmas and an Happy New Year
Rinaldo
Have a look at this slideshare presentation.
I wish you a Merry Christmas and an Happy New Year
Rinaldo
Friday, December 14, 2012
SOA and Enterprise Inter-Operability with a Portal
Last Post from Sam’s World
Enterprise based portals employ a desirable set of functional characteristics that provide value any number of ways. While ROI and other business calculators are engaged to offer a compelling business argument to the introduction of a company based knowledge repository, my focus will instead lie with efficiencies derived from penetrating the middleware platform of an enterprise. Several benefits provided through the use of web-based portal services & SOA are what I will explore in this post. There is a dominant, myopic perspective in which enterprise portals are viewed as an information architecture and not for what they are – an application. The architecture establishes the foundation for a common view of the data, applications, and a common management interface for content. However, the real benefit of an enterprise portal comes from the convergence, not from the web based display mechanism. This fusion differentiates enterprise portals from a collection of web sites by offering
- universal access to information,
- role-based personalization,
- cross-application workflow,
- common content management, and
- centralized user management.
Read the full Post SOA and Enterprise Inter-Operability with a Portal.
Subscribe to:
Posts (Atom)