My fellow Product Owners for SDL Tridion Sites have an interesting challenge to somehow understand and clarify the top community product ideas to size them for prioritization against everything else that will be in the Tridion Sites 9.1 release (scheduled for after Sites 9, if the version wasn’t clear).
My colleague Rick has been leading this effort and I’m doing my part to point out all the (many) channels we have in the community and ways to solicit feedback. Ironically, it’s hard to get feedback that we can use to actually understand and size a few of these ideas, especially after I’ve noticed everyone seems to have an idea.
One of our customers has a pattern where they have a list of component links in a container component. Some of these container components are hundreds of links long.
Although the contained components are ported from DEV to UAT to PROD, adding the components to the containers is done manually. This usually works well, but what happens when some links are missing? How do you sort through hundreds of component links to find if you need to add one?
In this post I show how to use Excel and Notepad++ to work with the contents of the container component.
You have a bunch of SDL Tridion Content Delivery microservices set up in various locations. In Windows, these can be installed as Windows Services, which allow you to configure automatic start rather easily, via the Services interface. But how can you do the equivalent in Linux?
When you install one of the Tridion micro-services as a Windows service, you can specify a number of startup parameters. These may include settings such as the database host, database login, the port to use, etc.
These settings will be remembered and used every time the Windows service starts.
But what if you want to see which settings were used, later on?
For that, you will have to look in the Windows registry. The following location is an example using the Discovery service:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Apache Software Foundation\Procrun 2.0\SDLWebDiscoveryService\Parameters
You’ll notice a number of sub-keys:
Stop. The most interesting information is in the
Java key contains the classpath to use (yes, set at the time of installation), the JVM options, and most of the parameters specified for the service (in the
Registry key containing most of the startup options
Start key contains the working directory and the parameters directly related to the hosting of the service (e.g. port to use and whether or not it should register its capabilities with the Discovery service automatically).
Registry key containing the hosting options
If you just need to tweak one of the values, you can edit these registry keys and restart the service. If you require a large amount of changes, I recommend simply uninstalling the service and re-installing it with the new parameters.
Continuing on with the creation of Alchemy Plugin videos, I’ve just added a new one to show how to upload a bunch of multimedia items into SDL Tridion. The video is posted after the jump.
In http://www.tridiondeveloper.com/intro-to-the-event-system I described the overall event system, listing many of the options available, but not describing them in detail. One of these options requires further examination: Asynchronous Events.
Asynchronous Events happen outside of the regular process of the code that is running. They may run now, or they may run later. You can think of Asynchronous Events as “Fire And Forget” rockets. Sometimes that’s exactly what you need, and sometimes that’s exactly the wrong thing. Let’s look at some scenarios for both.
When mass publishing content from Tridion, the publish job is handled as a single transaction. Using the Alchemy Page Publisher plugin it’s possible to perform this task but create single items for publishing.
After the jump I’ve created a short video to demonstrate this functionality.
We’ve been quietly releasing some new plugins over at the Alchemy Webstore. As part of those releases I’ve made some quick demonstration videos as it’s far nicer to watch a video showing how to use a plugin than reading the description
To crack things off, after the jump we have the first in the series dedicated to generating Tridion documentation automatically.
As announced by SDL earlier this week – it’s here!
Just in case you’re week’s still too busy to read the full-monty here’s a few snippet to highlight the main ‘changes introduced’ in this new framework:
One of our clients uses Tridion 2013 SP1, and has strict audit requirements for their publishing. We need to know what is on the site at any particular point in time. The auditors might ask, for example, what the user saw if they viewed the site two weeks ago last Tuesday at 3am.
We have to track what gets published, and make sure that we have no significant performance degradation while we’re doing that. Publishing for our releases already take several hours, and we can’t extend that by any significant amount of time.
These tests let us look at different options for this timing. Once the tests have been run, we will then have a better idea of which one to implement.