If you want to sync your Production environment back to Dev and Test and need it to be an exact copy, then the best thing you can do is make a backup of the Production CMS database and restore that on the Dev envrionment.
The only thing you will miss at that point is the what is actually published (the published state is there, but the actual files on your ...
The license is typically bound to a hostname and number of CPU Cores, if your new machine(s) has a different name or different number of CPU Cores then indeed this won't work and you'll need a new license file.
So, either rename the machines, or ask for a new license file. If it is a license violation issue, I am pretty certain it will be logged as such in ...
Moving items across Publications will always require you to write some code, as you noticed you can use copy/paste only inside a Publication and not across Publications.
So you will have to create a new item (as a copy of the original) and update all the links from the original to the new item.
There are no ready made database script to perform these kind ...
I've done it once for a customer, it was a horrible job to do since the sequences didn't migrate well with the data migration assistant from Oracle (but that might have changed as it was a long time ago). We fixed that by setting them all manually, but it took quite a while before everything was running without any errors.
It isn't a supported process for ...
Yes, it's possible, I've done it before, but don't expect to get SDL support afterwards. I've migrated Oracle to MS SQL, but steps are still the same:
Create a database on Oracle. It should be of same version as MS SQL. This will give you correct stored procedures
Migrate data from all tables. There are plenty tools to do the job for you. Most of the tables ...
For CD side it is easier, all DB related info is located in cd_storage_conf and deployer-conf files. After update just restart microservices.
For CM side it is a little trickier since DB related info is encrypted using Tridion Rsa key.
CM DB info is located in %TRIDION_HOME%\config\Tridion.ContentManager.config
Topology Manager DB info is located in %...
Migrations are always a big topic for debate, while in my humble opinion they never have to be. Please let me start of with mentioning my blogpost about content migration and migration tools: http://www.tridiondeveloper.com/how-to-say-goodbye-to-your-migration-tool
In here I explain (based on my own experience), there is no better way to migrate content ...
No, there is no first-party (SDL) migration tool from other Content Management Systems into SDL Tridion.
I've spoken with one vendor that said it can handle importing at an SDL conference. They did not know what BluePrinting was, so be careful with any third-party vendor that promises a tool.
You really should understand Tridion's content model before ...
Migration is the intersection between:
Skills or expertise
You really can't analyze the challenge without a content inventory and model for the source and target systems. Ideally "Inventory x time" is greater than the cost of skills or expertise.
Gotchas in a move:
Dependencies. If Content Porter seems challenging, do not automate.
In 2011 the window.returnValue is no longer used, so as you have already noticed you have to migrate your Custom URL scripts also.
It all starts with adding the PopupInit.js script to your Custom URL, which will register your Custom URL page allowing the script in there to make changes to the Component fields.
Then for the rest you have to work with window....
I'm pretty confident you can return an array and this will populate the multi-value fields, like this:
var values = new Array();
var fields = window.dialogArguments.getFields();
for (var i=0; i<fields.length; i++)
values.push("adding value to field pos: " + i);
window.returnValue = values;
First, I'd try to make sure you are using the latest version of Tridion 2011 (there was a service pack and 2 hotfix rollups issued for this version).
According to this page in the documentation (login required) you can use a method called "setValues" to set the value(s) of Tridion fields:
<!-- Set the (first) value of the field. This assumes a field of ...
No doubt, manual migration is a safer approach with high level of success rate. Apart from this you can also automate migration through some tools.Kapow and Vamosa are two of them. Generally these tools crawl the sites, analyze the content, organize it and finally import this content to the CMS.
These tools have their own connector for SDL Tridion
Unfortunately the answer you're searching for won't be found in Tridion itself. Tridion publishes content that gets formatted for display by a webapplication - which, unless you're using DXA, is not provided by SDL. When following proper guidelines and SEO recommendations, I have normally found that the opposite is true: SEO ranking improves due to better ...
IF you want to use available tools within Tridions (8.5 and 2011), you can use combination of import/export services and Content Porter.
So you can use Content Porter to export data from Tridion 2011, and use import/export service to import data in 8.5
For importing into Web 8.5, please check this documentation.
For Content Porter 2013, please check ...
SDL Web 8 in-process CD APIs are fully compatible with Tridion 2013 SP1.
So, you can just use the DD4T Provider for Tridion 2013 SP1. You only need some so-called assembly binding redirects because the assembly versions are different.
For an example of assembly binding redirects, see: https://github.com/sdl/dxa-web-application-dotnet/blob/master/Site/Web....
SDL Tridion has very comprehensive APIs to interface with the content management system, making the import of content from external sources quite straight forward (research Core Service)
I am not familiar with Interwoven Sitepoint's API, so I cannot comment on the ease of extracting data from your existing CMS.
As posted above, by Bart, also seriously ...
We did migrated many CMS like Word press, Navi CMS and Tridion R5.2 websites to SDL Tridion 2011 and 2013 using Tridion Core Services.
Best practice you can identify your contents Like news, events, press releases this can be automated to migrate.
Those schema content's you can write logic to export all your content as XML.
Using core services and Events ...
Tridion is a web content management system. If you dump everything "one time" into a different repository, you won't be able to use Tridion to content-manage it, will you? That sounds rather self-defeating, but that notwithstanding, Tridion offers many good ways to export its data. For example, the core service API will allow you to read the content and ...
In addition to what others has suggested, please also follow the Installation Manual for SDL Tridion as you may need to apply some additional patch while you shift to Oracle.
Regarding where all you need to change the type of DB and the DB instance, you may choose the SDL Content Manager Config MMC, but once you do changes in any value, do not forget to ...
+1 to Bart's answer though I'd suggest a DB script is akin to setting up a perfect content port without a "go back" option because of checked-in status, dependencies, and localization across the BluePrint.
The logic should be clear but with some subtle gotchas. For items in a given folder:
Check-in (or ignore) checked-out items
Copy item to a "temporary" ...