So I finally got around to having enough time to set up a Java-based DXA connecting to a Content Service in the Amazon cloud.
It was a fun adventure, to say the least, and most of it is due to my rustiness in Java. I have tried with both Eclipse and IntelliJ Idea, and definitely IntelliJ made it a lot simpler by detecting project dependencies and installing them for me – which actually made it harder to get Eclipse to work, as I hadn’t noticed what it had done.
Anyway – below are the steps I followed to get a local instance of DXA running within Eclipse. As with the .NET install, you need to make sure you have a proper firewall configuration allowing communication between your machine and the CIS, as well as having the right mappings set in Topology Manager (I used the default of “localhost:8080″ for this). I will not cover those steps in this post.
What is it?
If you want to track content versions created between Workflow Activities in a Workflow Process, you can enable auditing of a Workflow Process. When you enable Workflow auditing, “snapshots” are taken of an item as it progresses through a Workflow Process.
I know time’s precious so let me give you the summary – read on for the rationalisation!
An RTF field is exactly that – a Rich Text Field – it was never intended to facilitate how the combination of text and images are presented across multiple views in different devices; that is what we use CSS, HTML, JS and-the-like for.
Control’s important and should be in the hands of the people with the tool for the job. Tridion is an excellent content management system and affords editors with a multitude of tools to manage content across hundreds (if not thousands) of publications.
Late last year I decided to work on an easier setup for Web 8.5 and, happy with my results, I decided to continue playing around with it.
This post is mostly a reminder to myself of what I needed to do to:
- Load DXA on my local machine/visual studio
- Connect to the content services running on my AWS server
- Debug/run DXA from my local machine
Earlier in December, I had the opportunity to travel to Boston for the two-day SDL Web 8 System Administration Course in Wakefield, MA. It’s an excellent course, especially for those transitioning from Tridion 2013 to Web 8 and for people like myself who are traditionally weak in the area of sysadmin. I would highly recommend it.
A while back I wrote a post on using Context Variables as a templating cache. When I came across some requirements to cache data between templates on a recent project I revisited this concept, but found some limitations with Context Variables which I had not realized before. As such I ended up implementing a different approach to caching
Recently I was involved in the setup of a new content-delivery environment, migrating from a WebSphere 7.* application server to WebSphere 8.5.5. Right away when we started up the application, we started seeing some content-delivery errors with our session preview web-service which we did not experience on WebSphere 7. I’m going to review the problem, and talk about how it was resolved. Continue reading
Oddly enough, yes it can – in a very specific scenario – of course, this can be avoided
with clear processes (or even better automation) with the right hotfix (TT88491: Translation Manager revert retrieved translation for target item in “Reserved state”) but it’s good to know as tracking this down was a real bugger!
Often times when folks are stepping into the world of the Razor Mediator they do not fully understand what new capabilities are provided OOTB. Back in the days where DWT reigned supreme, more often than not, we had to write TBBs for simple logic such as grouping component presentations for rendering, etc. Continue reading
I finally found some time to start working on my own plugin built in this incredible new framework developed by Content Bloom called Alchemy. You can see my plugin on the Alchemy Webstore here. It’s called Not Used and it’s really just a basic cleanup tool that allows a Tridion user to search for and remove various items that are not in use. Perhaps more interesting than the plugin itself is the process of learning to work within the Alchemy framework, which requires a combination of knowledge in Tridion’s Anguilla framework, C# core service API and standard .NET web technologies. Some of these have documentation that is seemingly hidden or otherwise very difficult to track down and/or decipher. Here I discuss some of the trickier bits of my experiences developing an Alchemy plugin, in hopes that these details will help others encountering the same challenges. Continue reading