Live Copy is the creation of one site based on the content and structure of another. For many, the initial Live Copy setup can be daunting.
Axis41 AEM Implementation Expert RJ Spiker joins the Adobe Experience Manager Podcast to talk about how to properly set up Live Copy on an Adobe CQ 5.5 site. RJ will then explain how to overcome some of the challenges that he faced while setting up the Live Copy for CMO.com.
You can also check out RJ’s blog post where he goes into more detail about Live Copy and Multi Site Manager (MSM) here.
Music Intro: Code Monkey by Jonathan Coulton
Transcript:Announcer: Welcome to the Adobe Experience Manager podcast, a weekly discussion regarding the Adobe Experience Manager formerly CQ and other marketing and technical issues. This podcast is presented by Axis41, your partner in Adobe Experience Manager implementations. Your hosts for the podcast are Joey Smith and Peter Nash.
Peter Nash: Good afternoon. Welcome to the podcast. I am Peter.
Joey Smith: And I am Joey.
Peter Nash: We are going to talk today about Live Copy within the Adobe Experience Manager system. Here to talk to us about that is RJ Spiker. RJ has been a professional developer for six years and has been with Axis41 for a year now, is that right?
RJ Spiker: That’s right.
Peter Nash: Okay. He has been working with computers since he was in high school, so he is a general whiz when it comes to the technical kinds of stuff. What's probably more relevant though is the fact that he has been working on several different CQ implementations over the last year. So, RJ welcome to the podcast.
RJ Spiker: Thank you.
Peter Nash: Thanks for being with us.
Joey Smith: RJ, I think we should probably start off with just answering the question of what is Live Copy.
RJ Spiker: Live Copy basically is the creation of a site that’s based on content and the structure of another site. So, for example, it allows us to have a large number of sites that we can manage pretty easily.
Joey Smith: So, how would we use that?
RJ Spiker: Let's say for example a site that we have a site that we want to have a mobile site designed around.
Joey Smith: Okay.
RJ Spiker: And on top of that maybe we want to have various languages that we are translating into and that can kind of become cumbersome.
Joey Smith: Okay.
RJ Spiker: As we have several sites that we need to manage. Live Copy will actually allow us to manage those and actually have these sites self-maintain themselves. They will create their own pages, they will update their own pages, they will activate and deactivate all based on what we do with the main site that we are copying.
Joey Smith: That sounds pretty cool. I guess we have to then ask ourselves, is how is that any different from replication? So, CQ has some built in replication features. What makes Live Copy different?
RJ Spiker: Live Copy will handle all the creation and replication for us, whereas we can have a mobile site, we can go and manually create mobile pages and copy over content, but what Live Copy will also do is it will streamline that process. It will basically handle all that for us. We can create what we call rollout configs. Rollout configs will allow us to actually change JCR content within the nodes that were live copy.
Joey Smith: Okay.
RJ Spiker: So, let's say we have a mobile site. We want the mobile site to have the same content as the live site…as our dotcom site. However, we want our mobile site to have a different design. So, maybe we need to point to different templates.
Joey Smith: So, like if you were going to use say a reactive design for your mobile site.
RJ Spiker: Yeah. So, like we can take our rollout config. We can actually using regex basically search for specific properties in our JCR content and we can actually change those dependent on our regex.
So, for example if we need to change our design for a mobile site, we can point our sling resource type to a different sling resource type, maybe inside of a mobile folder.
We could change our templates to point to a different sling resource type. We could change titles around. We could change basically anything that we want, we can actually configure dependent on the changes on the live site, we can change our mobile site.
Joey Smith: And you mentioned earlier that you could also use this for translation. So, does that mean we can actually change the content of the page itself?
RJ Spiker: Yeah, we can Live Copy, so we can create our pages and then maybe we want to go in and we want to have a page that slightly differs from the main site. So, we can actually deactivate specific components on the mobile site or on the language site or whichever and so we can actually deactivate just that specific component and change that component, whereas the rest of the components will still follow the Live Copy; a specific component will remain unchanged.
Peter Nash: So, do you just do that through like cancelling inheritance kind of a thing within the component itself?
RJ Spiker: Exactly. We can do that in the page properties dialog. We can go in and unclick specific things, like the title for example. If we don’t want the title to change, we can actually go in author mode, in editor mode, we can go in and go into the dialog of the specific components or maybe a full parses and say we don’t this parses to take anything from Live Copy. We want this to remain unchanged.
Peter Nash: Okay.
Joey Smith: It sounds pretty cool.
RJ Spiker: It is pretty powerful actually.
Joey Smith: How would you get started? If I were to come in into my CQ for the first time and I am saying you know those guys talked about the Live Copy thing. That sounds pretty neat. How do I get started?
RJ Spiker: So a basic Live Copy is pretty simple. We just go to the site admin section and we just go to New…the New dropdown and there is a new live copy.
Joey Smith: Okay. So, it’s right there.
RJ Spiker: It’s right there. You just follow the dialog that pops up and it will get you started.
Joey Smith: Okay.
RJ Spiker: If you wanted to you can even manage your live copies inside the site admin, but even further you can go to the blueprint control center which is located in the tools section and there we can actually manage all of our live copies as you could have maybe several.
Joey Smith: Sure. Like you mentioned the mobile and all the different languages and maybe even mobile in different languages.
RJ Spiker: Exactly. You could have 1 to 10 to however many you want, however many you need, you can manage them all right there, basically laid out in a nice table where you can actually see which pages have live copy…which pages have specific components that might be deactivated, which pages still need to be live copied or maybe which pages are not live copied because we don’t want them live copied.
Joey Smith: Because we may be set u an exclusion of some sort?
RJ Spiker: Yeah, maybe mobile sites have less pages or less content.
Joey Smith: Okay.
Peter Nash: I remember a specific example cmo.com. We had worked on some pages there for them that were pretty specific to a desktop site, where they had their slide shows. That was not something we wanted to bring over to the mobile version of that site because the nature of the content itself is just not going to fit within a mobile site. So, that's a real example of how we did that.
RJ Spiker: Exactly. For cmo we actually…we inherited…we had our live copies actually being created for the most part, but there were specific pages that we decided that we didn’t want to have live copies. So, we actually would cancel the inheritance for any specific pages, child pages, if that makes sense.
Peter Nash: Right.
Joey Smith: And was that done mostly through the blueprint control center?
RJ Spiker: Yes. That kind of stuff was actually done completely in the blueprint control center.
Joey Smith: Okay. Now, you mentioned earlier that the live copy uses regex. Is that regular regex or is that the kind of weird custom regex that we have seen sling use on different parts of their utilities?
RJ Spiker: I believe it's that custom regex
Joey Smith: Okay. So, maybe sometime we will dive deeper into that specific Regex language and maybe how it differs from what people might be used to.
RJ Spiker: We will have to test that out a little bit.
Joey Smith: Okay. RJ, thank you. That actually really helps and I think it sounds like an incredibly powerful feature that people can use to move forward on their sites.
Peter Nash: So, one of the things RJ had mentioned to me is he was willing to go through and actually do like a little screen cast to show an example of how to actually go through and do simple live copies set up. So, we will probably have that up there eventually for you guys to check out if that is something that you need some help with as well.
Announcer: You have been listening to the Adobe Experience Manager podcast, brought to you by Axis41, your premier partner in AEM implementations. If you have questions, comments or something you would like us to cover, send an email to firstname.lastname@example.org.