Thursday, December 13, 2007
Exo ECM Architectiure request process
Exo_platform Architecture
Form request->to portlet (UIPortlet’s subclass) or UICommand class -> sets Renderer using (VelocityRenderer), sets class using setClazz
-> gets RequestInfo using RequestInfo class -> using a Business service object (For ex:OrganizationService)-> gets Handler(Handler Implementor which is like a DAO) -> using hibernate service ->gets data from database and puts in java objects -> Performs
Business process
Exo-ECM postgres SQL configuration
1) JDBC Driver – copy the driver to application service lib directory.
URL: jdbc:postgresql:postgres
Driver Class: org.postgresql.Driver
Username: postgres
Password: postgres
2) Configure the driver .
http://docs.exoplatform.org/exo-documents/exo-jcr.site/dbcontainer.html
Single-database configuration:
Configure the “database-configuration.pgsql.xml” and “database-configuration.xml” available in “%EXO-TOMCAT-HOME%/conf” directory to postgres: (If ‘database-configuration.pgsql.xml’ not available then take a content copy of ‘database-configuration.hsql.xml’ file and create new one)
The changes includes update the url of data base, driver class, username, password and dialect.
Here are the details for Poetgres:
URL: jdbc:postgresql:postgres
Driver Class: org.postgresql.Driver
Username: postgres
Password: inkriti
Dialect: org.hibernate.dialect.PostgreSQLDialect
3) Intigration
Work n progress:
We are getting issues while creating the tables into postgres data base as hibernate configuration for postgres sql is different from hsql(Ex: In scenarios of identity generation is different for different data bases)