Skip to main content

Toolkit - Model Factory

This post if part of a series about the File System Toolkit - a custom content delivery API for SDL Tridion.

This post presents the Model Factory, an layer that offers CRUD operations on models backed by a cache and a file system provider.

The Model Factory is a singleton that allows the creation, retrieval, update and deletion of a model. It works using a CacheFactory and a File System Provider that acts as a data abstraction layer.

The Model Factory works on two types of models only: ComponentMeta and PageMeta. They are both generics passed to the factory methods or inferred from the returned type.

Method getOrCreate(TcmUri)

This method tries first to read a model from the cache. If it doesn't exist in cache, it tries to read it from the file system provider. If there is no such model on disk, then it will proceed to create a stub model that only has its TcmUri property set. The idea is that the user will populate the other model properties and will execute a updateModel.

public <T extends ItemMeta> T getOrCreateModel(TcmUri tcmUri) {
    T model;
    String key = cacheFactory.getKey(tcmUri);
    CacheElement<T> cacheElement = cacheFactory.get(key);

    if (cacheElement == null) {
        model = modelProvider.read(tcmUri);
    } else {
        model = cacheElement.getPayload();
    }

    if (model == null) {
        model = modelProvider.create(tcmUri);
        cacheFactory.put(key, model);
    }

    return model;
}

Method getModel(TcmUri)

This method is the most used method of the factory. It provides the read operation of a model from either the internal cache or from the file system provider. Usually the 'write' operations of this factory are called only by the Deployer extensions, during the publish/unpublish activities. The 'read' operation is used mainly in the Toolkit CD API.

public <T extends ItemMeta> T getModel(TcmUri tcmUri) {
    T model;
    String key = cacheFactory.getKey(tcmUri);
    CacheElement<T> cacheElement = cacheFactory.get(key);

    if (cacheElement == null) {
        model = modelProvider.read(tcmUri);
        if (model != null && model.getLastPublished() == null) {
            model = null;
        }
        cacheFactory.put(key, model);
    } else {
        model = cacheElement.getPayload();
    }

    return model;
}

Method updateModel(T model)

This method is a write operation that persists the model sent as parameter to the file system. It also places the updated model in the cache.

public <T extends ItemMeta> void updateModel(T model) {
    TcmUri tcmUri = model.getTcmUri();
    String key = cacheFactory.getKey(tcmUri);
    model = modelProvider.update(model);
    cacheFactory.put(key, model);
}

Method removeModel(TcmUri)

This method is a write operation that deletes a model from the file system and removes it from the cache.

public boolean removeModel(TcmUri tcmUri) {
    String key = cacheFactory.getKey(tcmUri);
    cacheFactory.remove(key);

    return modelProvider.delete(tcmUri);
}



Comments

Popular posts from this blog

Scaling Policies

This post is part of a bigger topic Autoscaling Publishers in AWS . In a previous post we talked about the Auto Scaling Groups , but we didn't go into details on the Scaling Policies. This is the purpose of this blog post. As defined earlier, the Scaling Policies define the rules according to which the group size is increased or decreased. These rules are based on instance metrics (e.g. CPU), CloudWatch custom metrics, or even CloudWatch alarms and their states and values. We defined a Scaling Policy with Steps, called 'increase_group_size', which is triggered first by the CloudWatch Alarm 'Publish_Alarm' defined earlier. Also depending on the size of the monitored CloudWatch custom metric 'Waiting for Publish', the Scaling Policy with Steps can add a difference number of instances to the group. The scaling policy sets the number of instances in group to 1 if there are between 1000 and 2000 items Waiting for Publish in the queue. It also sets the

Toolkit - Dynamic Content Queries

This post if part of a series about the  File System Toolkit  - a custom content delivery API for SDL Tridion. This post presents the Dynamic Content Query capability. The requirements for the Toolkit API are that it should be able to provide CustomMeta queries, pagination, and sorting -- all on the file system, without the use third party tools (database, search engines, indexers, etc). Therefore I had to implement a simple database engine and indexer -- which is described in more detail in post Writing My Own Database Engine . The querying logic does not make use of cache. This means the query logic is executed every time. When models are requested, the models are however retrieved using the ModelFactory and those are cached. Query Class This is the main class for dynamic content queries. It is the entry point into the execution logic of a query. The class takes as parameter a Criterion (presented below) which triggers the execution of query in all sub-criteria of a Criterio

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as