Chuyển đến nội dung chính

[DATABASE] USE DATASOURCEPOOL WITHIN OSGI BUNDLE TO CONNECT MYSQL

Goal:

Create a CQ/AEM project to connect mysql by


Create project:



mvn archetype:generate \
   -DarchetypeRepository=http://repo.adobe.com/nexus/content/groups/public/ \
   -DarchetypeGroupId=com.day.jcr.vault \
   -DarchetypeArtifactId=multimodule-content-package-archetype \
   -DarchetypeVersion=1.0.2 \
   -DgroupId=mysqldemo \
   -DartifactId=mysqldemo \
   -Dversion=1.0-SNAPSHOT \
   -Dpackage=com.mysqldemo \
   -DappsFolderName=mysqldemo \
   -DartifactName="Mysql Demo" \
   -DcqVersion="5.6.1" \
   -DpackageGroup="Mysql Demo"


Update bundle pom:



<dependency>
           <groupId>com.day.commons</groupId>
           <artifactId>day.commons.datasource.poolservice</artifactId>
           <version>1.0.10</version>
           <scope>provided</scope>
</dependency>


Update content pom:


<dependencies>
...
<dependency>
           <groupId>mysql</groupId> <artifactId>mysql-connector-java</artifactId> <version>5.1.22</version> <scope>provided</scope>
</dependency>
...
</dependencies>

...

<embeddeds>
...
<embedded> <groupId>mysql</groupId> <artifactId>mysql-connector-java</artifactId> <target>${install.target}</target> </embedded>
...
</embeddeds>



Configure the DataSourcePool connection properties:
Add a configuration for the JDBC Connections Pool service that uses the JDBC driver to create data source objects. The OSGi bundle created in this development article uses this service to connect to the MySQL database. For information, see Connecting to SQL Databases.  
To configure a DataSourcePool, peform these tasks:
1. Login to Adobe CQ’s Apache Felix Web Console at http://server:port/system/console/bundles (default admin user = admin with password= admin).
2. Click the Configuration tab..
3. Click the + icon that appearts in the JDBC Configuration Pool row (in AEM 6, the row is titled Day Commons JDBC Connections Pool).
4. Enter the following values:
  • JBDC Driver class - the driver class to use to connect to the database. To connect to MySQL, enter com.mysql.jdbc.Driver.
  • JDBC connection URI - the URI to the database. In this example, enter jdbc:mysql://localhost:3306/databasename.
  • Username - the user name to use to connect to MySQL.
  • Password - the corresponding password.
  • Datasource name - the datasource name. This is the value that you reference in the Java logic located in the OSGi bundle. In this example, enter Customer.
5. Click Save.


Code to get connection:



           @Reference
private DataSourcePool source;

// Returns a connection using the configured DataSourcePool
private Connection getConnection() {
DataSource dataSource = null;
Connection con = null;
try {
// Inject the DataSourcePool right here!
dataSource = (DataSource) source.getDataSource("Customer");
con = dataSource.getConnection();
return con;

} catch (Exception e) {
e.printStackTrace();
}
return null;
}

Nhận xét

Bài đăng phổ biến từ blog này

[PERFORMANCE] Adobe WEM/CQ performance tuning

Adobe WEM/CQ performance tuning Contents Caching-related configurations CRX Bundle cache CRX Search index handler (Lucene) cache Tar PM index cache Scalability Maintenance Optimizing Tar Files (for Tar Persistence Manager) Data Store Garbage Collection Main documentation you should consult first: http://dev.day.com/docs/en/cq/current/deploying/performance.html http://dev.day.com/content/kb/home/cq5/CQ5Troubleshooting/performancetuningtips.html Caching-related configurations CRX Bundle cache CRX caches bundles, consisting of a node with all its properties. This is used by all bundle-based Persistence Managers. The default size of BundleCache is 8 MB. If this is too small it can cause an excessive number of read-accesses to the underlying persistence layer. Set the bundleCacheSize to something larger than the default. See more here: http://dev.day.com/docs/en/cq/current/deploying/performance.html#CRX%20Bundle%20Cache CRX Search index handler (Lucene...

[Query Builder] Advanced Search

Using the Advanced Search When using a list, select from the 'Build list using' options 'Advanced Search.' This will open a new tab in the list window with one text box labeled: 'Querybuilder Predicate Notation.' This is asking for a few lines of code to define search parameters. Example Code - With Explanations of Results Searching for Pages type=cq:Page property=jcr:content/jcr:title property.value=Places 'type' defines what sort of object you'll be searching for (it's usually a page). 'property' defines what property of the object you'll be filtering by; in this case, its by the title. 'property.value' defines your search term. So this search would be searching all PAGES with the TITLE of PLACES. So it would find every page titled Places. *IMPORTANT* Searches by title ARE case-sensitive, so 'Places' is not the same as 'places'. type=cq:Page path=/cq/sandbox property=jcr:cont...

[CQ6-SYSTEM] MAINTAINING THE REPOSITORY - Reduce repository size (cleanup repository)

Compacting Tar Files As data is never overwritten in a tar file, the disk usage increases even when only updating existing data. To make up for the growing size of the repository, AEM employs a garbage collection mechanism called Tar Compaction. The mechanism will reclaim disk space by removing obsolete data from the repository. Revision Clean Up By default, tar file compaction is automatically run each night between 2 am and 5 am. The automatic compaction can be triggered manually in the Operations Dashboard via a maintenance job called Revision Clean Up. To start Revision Clean Up you need to: Go to the AEM Welcome Screen. In the main AEM window, go to Tools - Operations - Dashboard - Maintenance or directly browse to http://localhost:4502/libs/granite/operations/content/maintenance.html Click on Daily Maintenance Window. Hover over the Revision Clean Up window and press the Start button. The icon will turn orange to indicate that the Revision Clean Up ...