Tridion 2011 SP1 HR1 - which extension to use?

Question

We have a requirement that on a public page we need:

• Find a presentation of a component with a component based on a specific diagram.
• Extract the specific field values ​​from this component and save them in the user database table available to our .NET application (on the content delivery side).

I think this is a good candidate for a Deployer extension or a storage extension, but I'm a bit unclear, and why never wrote?

I excluded the event system, since this code will be posted on CM, which seems to be the wrong “side” for me. I focus on expanding what happens on the CD side after the page is published.

Read some articles about the world of Tridion ( this , this , this and this ), and I think a repository extension would be a better choice?

Mihai's article seems to be very close to what we need, where it uses a new element type mapping:

<ItemTypes defaultStorageId="brokerdb" cached="true"> <Item typeMapping="PublishAction" cached="false" storageId="searchdb" /></ItemTypes> 

But how does Tridion “know” to use this new type of element when publishing content (its not one of the defined TYPE_NAME , which is a point view)?

I have to clarify that I am .NET / C # dev is not a Java developer, so this is probably really obvious to the Java people - sorry if that is the case!

Greetings

Answer 1

Tridion does not by default recognize how to expand a new object. My advice is to create a Deployer module (your links should provide you with enough information about how you can do this), which is performed during the post-processing phase (deployment process), which processes all components from the deployment / transport package, extracts the necessary information and uses a custom extension to store the necessary information.

Be careful: you need to configure your new type in the configuration, but you also need to use it yourself from this Deployer module.

Hope this helps.