Please provide details about the difference between creating a live copies from blueprint and live copies directly(New-> New Live Copy) with scenarios/examples, in AEM
Blueprint: Is the basic structure created as a copy of existing site. Ex: We have a requirement to create a site with the same structure as Geometrixx site, we can create a Blueprint for the new site providing the Source Path attribute as Geometrixx site path.
Live Copy: Is basically creating a new site based on the content and structure of an existing site or blueprint so that when changes are made in base/source site, it is automatically updated here.
i.e. Create a livecopy and enter the source page as “Geometrixx/Global/English”.
So any update to the ‘Geometrixx/Global/English’ page automatically updates the livecopy page.
Rollout: Using blueprint rollout feature we can push modifications to all it’s live copies simultaneously.
Related
Im a newbie to App Scrips and have challenges with having to authorize my app script to run on each newly created document.
I run a merge with Sheet data in to a Doc template (using Autocrat) and have a script (in the template) that cleans up the merged doc - onopen. The problem is that I have to authorize the script in each newly created document.
The script will only be used by my partner and I. We share GDRIVE access.
Do I have to deploy as an Add-on? Web App? Shared Lib? If Shared Lib - how do I envoke it automatically in the newly created doc?
Any feedback/guidance is much appreciated. Thank you all.
I have tired to create a shared lib, but Im not sure how to automatically included the lib in the newly created document.
Is there a good learning tool/"how to" for this?
I am trying to move document libraries, from one site collection to another and retain of the metadata such as Modified By, Date Modified etc.
I have tried using the 'move' function within SharePoint 2013 Content and Structure but unfortunately this doesn't extend to across site collections.
I have tried multiple PowerShell scripts they successfully copy the file from one Site Collection to another but do not retain the metadata.
Any ideas, would be greatly appreciated.
Thanks.
have you tried saving the library as a template? You can mark the template to keep the contents.
Then you can deploy a new library from that template (Site actions / More options / Template name), and after that delete the template.
Additionally you can move it between servers. Go to the Site settings, there to the template gallery and download the template you just created. Now you can move it to another server or application.
Hope it helps.
Take a look at the SharePoint migration tools. Some of them offer free trials for limited amounts of data.
We're considering using Adobe Experience Manager for an upcoming project. But we have a number of pre-made static pages we'd like to import into this project. What would be the best way to 'import' these pages into an AEM project?
Note: these pages are HTML that may contain some CSS and JS.
You can serve static HTML, CSS and JS files from AEM. There are multiple ways of getting your files in AEM including but not limited to:
1) Through CRXDE, goto Create > Create File... name your HTML file and save. On the jcr:content subnode, double click on the jcr:data binary property, upload your HTML file and click save.
2) cURL your files into AEM. See the documentation on the SlingPostServlet. You can write a script in Bash, Python or your language of choice to loop over your files and POST to the AEM instance.
3) Go to CRXDE Package Manager, create a simple package, download it and unzip the file. Examine the contents of the zip including the .content.xml files and the /META-INF/vault/filter.xml file. Add your HTML files and update the package filters, zip up the files, upload the package to AEM through the CRXDE Package Manager and install.
Adding to what "nateyolles" has already mentioned,
Adobe Experience Manager provides several options (direct/Indirect) for either importing or exporting data (within the AEM tool they are labeled importers and are found under the tools area). Lets look at each option so you can decide which one will best service your current needs.
1) Site Importer – Allows you to import either a web page or an entire website into AEM. For site imports, you will need to need to specify the project title, site URL (of page or site to import), thumbnail image for the template, the sitemap (for the pages in CQ using the template) and whether or not you want to overwrite (if page or site exist in AEM)
"Use of Site Importer tool"
Link:- https://docs.adobe.com/docs/en/aem/6-2/develop/dev-tools/site-importer.html
2) Feed Importer – The feed import option within Adobe Experience Manager provides the ability to import content via a feed (whether that be an RSS feed or an Atom feed). This can be extremely beneficial to blog creators, like myself, who might want to bring in the content of their blog (from say WordPress, Drupal or another CMS) into an AEM environment.
3) Offline Importer – This functionality, within Adobe Experience Manager, provides the ability to import content from Microsoft Office Word document files into AEM templates (ending with the file extension of .doc). Please note that you should reach out to Adobe’s consulting team for asssistance on this so that they can set up the inputs in the most optimal way to receive your offline data.
4) Import from older version of CQ – This is a pretty straightforward way to import or upgrade from an older version of CQ. If you are familar with AEM, you can stop existing instance, if you have a stand alone instance of AEM replace the jar file, and restart
If you have an application server instance, you will follow these steps:
Stop existing instance, replace the war file and restart.
5) Bulk Editor – This feature provides a multitude of functionality within AEM. For starters, you can make large changes to content at once. Secondly, you can export content to CSV (Microsoft Excel) files.
Kautuk Sahni
(Adobe AEM Community)
I'm new to Alfresco. What i'm trying to do is to upload a file through REST API in a folder that i have created using Alfresco Web Administration Interface. I have a few problems:
1) I can see a set of folders, but how are them managed by Alfresco? As far as i know, those folders doesn't really exists physically, they are virtual. How does Alfresco manage the folders structure and files?
2) I have seen many examples on the _REST API use to upload a file. Anyway, the destination is set by something like this
workspace://SpacesStore/aae3b33fd-23d4-4091-ae64-44a8e332091341
I can't understand: What exactly is a SpaceStore? And, does the last-part-code refers to a specific folder? How can i get those codes relative to the folder i see in the Alfresco Web Admin Interface?
1) I can see a set of folders, but how are them managed by Alfresco?
As far as i know, those folders doesn't really exists physically, they
are virtual. How does Alfresco manage the folders structure and files?
Alfresco is an implementation of the Java Content Repository (JCR), this means that all the contents are managed using a logic structure similar to a graph of nodes. Storing and manipolating content must be done using the repository API, that's why you don't see anything at a storage level.
Each content in Alfresco is a node connected to at least another node: the parent.
The storage of Alfresco is based on two components:
File system for storing binaries and search indexes
Database for storing the backup of metadata and associations
The way how Alfresco stores contents is not important for you because you typically want to access using the Alfresco API. You can create your own logic structure in the repository using any type of folders tree and content associations.
2) I have seen many examples on the _REST API use to upload a file.
Anyway, the destination is set by something like this
workspace://SpacesStore/aae3b33fd-23d4-4091-ae64-44a8e332091341 I
can't understand: What exactly is a SpaceStore? And, does the
last-part-code refers to a specific folder?
A repository typically consists of a set of JCR workspaces, the SpacesStore is one of the workspaces in Alfresco and it is the logic partition of contents in their latest version.
Alfresco also contains other workspaces:
userStore: contains person nodes
archiveStore: contains removed nodes
version2Store: contains the version history of nodes
How can i get those codes relative to the folder i see in the Alfresco
Web Admin Interface?
That code is the node reference that is the unique identifier for each node in the repository and as you can see it consists of three parts:
workspace: the store protocol
SpacesStore: the store identifier
uuid: the UUID related to the node
The store reference consists of the store protocol appended with the store identifier and it is the identifier of the workspace where the node lives. The UUID specify the content inside the workspace.
These node references are the ID for nodes and you can see all these informations using the Node Browser inside the Alfresco Explorer | Administration Console trying to navigate your repository starting from the Company Home.
Hope this helps.
I am new to CQ5 and am wondering if there is a way to add a workflow to the DAM such a way that it kicks in when the users import file(s).
The workflow needs to do the following:
Call an External API over HTTP (REST) providing the file or the location of the file
The external service will perform some operations on the file and save the file
The service will respond back with the newly saved file or the location of the saved file
Workflow continues on with whatever else CQ5 does when importing files.
I came across the DAM Update Asset workflow where workflows can be dragged and dropped. I believe for my purpose, I will have to create a custom workflow?
I am new to CQ5 but now Java. I would love some guidance on how should I go about creating this custom workflow.
I see 3 solutions here:
1. Modify the DAM Update Asset workflow
You may add a new step to the workflow you've mentioned. I suggest adding new Process step between Metadata extraction and Thumbnail creation, so you'll have all metadata, but still can modify the asset before creating thumbnails (assuming it's an image). Process step invokes a configured OSGi service implementing the WorkflowProcess. More info in the official docs.
2. Create a new workflow
Implement WorkflowProcess as above, rather than adding Process step to the existing workflow, create a new one. The Launcher tab in the workflow console allows you to bind the created workflow to the event raised after uploading new asset.
3. Create an event handler
You don't have to use workflow at all. Create a new OSGi event handler and bind it to the DamEvent.