Upgrading .Net Events system from Tridion 2009 to Tridion 2011 SP1.
Does anyone have a brief overview of the steps involved?
What is the replacement for Events Config XML file to limit events to particular publications?
I have reviewed the subscribe approach implemented by the new Events system but can events be applied per publication. So far the only approach seems to be implementing publication filter logic in code rather than configuration?
Any input greatly appreciated!
This is a really good place to get started. Written by Bart Koopman
http://www.sdltridionworld.com/articles/sdltridion2011/sdltridion2011eventsystem.aspx
It includes a matrix for mapping old events to the new event phases.
To the best of my knowledge, you still need to choose whether or not to execute your code from within your code depending on the publication. You can not subscribe to a particular event for a specific publication.
Related
Is the
OnPageSetPublishedToPost
event supported in Tridion 2011. I am having real difficulty getting this event to fire.
I am deploying legacy events system code to Tridion 2011 SP1 HR1.
Thanks,
Chris
Legacy Events handlers, are not fully compatible with Tridion 2011.
TOM event handlers will no longer be triggered for publishing,
resolving and (for Audience Manager contacts import) Keyword save.
The Legacy Event Adapter can help firing some of these events, but unfortunately I think OnPageSetPublishedToPost is not one of them. You can find a lot of useful info on the companion article though
May not be the answer you are looking for, but for this specific event handler you can consider a rewrite to the new event system model. You can mix both old style and new event handlers on the same system.
Try events like the following. This should work. What did you try so far?
EventSystem.Subscribe<PublishTransaction, SaveEventArgs>(YourMethod, EventPhases.TransactionCommitted);
and
EventSystem.Subscribe<Page, PublishEventArgs>(YourMethod, EventPhases.TransactionCommitted);
We are upgrading to Tridion 2011 SP1 and as a part of Tridion search implementation we are using FS4SP (Fast Search for sharepoint 2010).
In proposed implemenatation search environement consists of following servers:
FAS4SP
FISE
Can someone guide us regarding how to push content to FAST from tridion and how to retrieve the same?
(Here due to some reasons we are not considering crawling of website by FAST)
What all APIs can be used for this implementation?
If you don't want to use the crawling approach, you will need to create a custom deployer, please take a look at this other article:
How can we integrate Microsoft FAST with SDL Tridion 2011 SP1?
Alternatively, if you don't have a development team who is familiar with Java, you might considering creating a .NET application which updates your FAST index based on either a File System or Database trigger when your pages or components are published, updated or deleted from your broker repository.
You will probably want to create XML for FAST and have the Custom Deployer (or Event System) send the content to FAST.
First create the FAST XML that works and write a sample app so you can insert it into the FAST index from either a .NET or Java application. This does not yet involve Tridion.
Then write your Custom Deployer or Event System and pass the XML to FAST.
IF you are using a Custom Deployer approach I would suggest to contact Tridion Professional Services if you have not done it yourself or are not a Java programmer. The new Tridion 2011 Storage API provides new opportunities for the Custom Deployer. In the meantime I would suggest to append the FAST XML to the normal Page Content at the end, surrounded by some markers, and have your custom deployer pull it out of the Page output, send to FAST, then remove from the output before continuing.
This is a fairly difficult challenge for those who do not have serious Content Delivery / Deployer / Java skills. However, if you want to go for it yourself I would suggest taking at least 2 weeks of time to research existing solutions and experiment with the API.
Using the Event System might be a little easier - but your success or failure message will not appear in the Publish Queue and if the search index fails to update you can only log the failure and not pass the info back to users.
Right now we are using Tridion 5.3. For number of publications we have event system implemented like sending some mail notification if component is localized, or sending a mail notification when particular activity is completed in workflow process etc.
Our current event system is implementation in Visual Basic 6.0, now when we have to rewrite our code we have to use .NET for the same.
My question is where I can get some sample code for beginners or documentation how event system can be implemented in Tridion 2011 SP1.
These are the top three links when I google for Tridion 2011 event systems:
http://www.sdltridionworld.com/articles/sdltridion2011/sdltridion2011eventsystem.aspx
http://www.julianwraith.com/2011/02/event-systems-in-sdl-tridion-2011/
http://www.curlette.com/?p=90
Each of them is a decent introduction to writing event handlers for Tridion 2011, which in itself is a lot clear/less involved than writing an event system for previous Tridion versions.
If you are having a concrete problem with your Tridion 2011 event handler, I suggest posting the code and describing the problem.
In addition to Frank's excellent suggestions, there is also a sample event handler and full documentation available in the online docs (Username/Password required).
SDL Tridion's TOM.NET API replaced the deprecated TOM (Tridion Object Model) starting in, I believe, version R5.3.
Aside from asking Stack Overflow (Exchange) questions, which documentation should we refer to when working with and learning the TOM.NET API?
So far, I've found (logins required):
SDL Live Content
TridionWorld Download (select latest version, currently 2011 SP1 to download the "SDL Tridion 2011 SP1 TOM.NET API" chm)
I see these (plus questions on the forum), but can't tell which is better. What do you use most when working with TOM.NET?
Good Question and Probably most of the Tridion new developers might be wondering the same when to to use which. I would say both the documents has a different purpose and go side-by-side. API Documentation does provide information on methods and usage, SDL Live Content docs provide information is more of understanding what to use for your scenario. We do get these kind of questions when we are on boarding any new developer "Which document provides me the most information".
I refer to these simple examples to explain the differences on when to use which documentation.
what variables are available in package (vs) What API method to use when reading variables from package ?
Referring Live Docs for the first and API doc for second
How do I loop through the embedded fields (vs) what method I use to loop through embedded value fields ?
Referring Live Docs for the first and API doc for second.
I see this question with different variation keep popping up almost every month.
I know I used simple use cases, but sometimes keeping it simple is better.
Hope this information helps.
Also according to this page in the documentation the TOM.NET API should be only used in Templating and Event Handlers. For third party applications you should use the Core Service API.
I use the API documentation, and when I really want to know more use Reflector. But that's not really advisable(?).
we use Windows Workflow Foundation internally on a large data manipulation and loading operation. Some of the workflows are complicated and take, with their sub-workflows - significant time, up to a total runtime for the main workflow of arounr 3-4 hours at the moment. THis is expected.... but it would be nice to be able to see where a workflow is.
We have an ASP.NET front end for the operational users. We would lvoe for them to be able to open a page showing a specific running workflow instance in a visualization with basically presenting a way to see the status of the activities (i.e. which activity executed, which is currently executing). No editing is required here . the idea is purely one of not having a black box 3 hour run. We are writing log entries internally which can be seen, but as always, a picture says more than a thousand words, and a visual presentation would definitly be better for them.
Anyone knows of any suite of components for asp.net (preferably mvc) that can visualize a server side running workflow? Editing is NOT required.
This is perhaps not exactly what you are looking for...
I am not aware of any ready-made components but perhaps you can built one for your self using WF designer. See this sample that hosts workflow designer on server side, capture the image and shows it on the page. It uses custom tracking services to depict which activity has run. Unfortunately, its a dated article and I am not sure if similar approach can work in .NET 4 (AFAIK, workflow designer has changed in .NET 4).
In case designer can not be hosted then you may try painting workflow activities/nodes by custom code. You have to use tracking to see the workflow state.