nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Customised web quick start app migration

abbeydom

Hi all,

Is it possible to migrate a customised webquick start application available within alfresco share running on a host (say old-dev) to a new installation of Alfresco running on another host (new-dev)? The new installation does not have webquick start installed.

Thanks for your help.

/Dominic

Find more posts tagged with

Comments

bremmington

Probably. What has been customised and how?

abbeydom

Thanks for your response. For now: Navigation, new folders excluded from navigation, new collections, new and existing pages, templates and webscripts. All modifications made within Alfresco share and by editing the wcmqs source code.

Thanks,
/Dominic

bremmington

Is there any particular reason why the new installation doesn't have WQS installed? It would be simpler if it did…

abbeydom

It was missed out during installation, kind of an oversight, we can probably add it to the install but if do how do we go about migrating the changes over apart of redoing all the customisation steps again?

Dominic

bremmington

I think I need a little more info about the nature of your customisations. Have you altered any of the code or config that is part of either of the two WQS AMP files, or have all of your changes been done eby editing/creating content using Share and by editing the files in wcmqs.war? From your earlier description it sounds like it's the latter, but worth double-checking.

abbeydom

Yes. It is the latter as you stated; that described what I have done. However, I do not know what the wcmqs AMP files are, so not sure if I have touched them or not.

Thanks,
Dominic

bremmington

OK, this shouldn't be too hard then. I recommend that you install WQS on the new instance, create a Share site and import one of the sample WQS sites into it using the WQS dashlet. Then, using Share, go into the Document Library and delete the folder "Alfresco Quick Start". For the sake of these instructions I'll assume that you have named your new Share site "wqs", but naturally you can call it what you want.

On the old instance you should export the "Alfresco Quick Start" folder (or the equivalent, if you've renamed it) to an ACP. I don't know if you're familiar with this process already, but you can read about it on the wiki. Note that this makes use of the Explorer application that comes with Alfresco. It is typically accessed at "alfresco-host:8080/alfresco". Follow the instructions in the "Web Client Export & Import of Folders & Files" section. For the export options choose these:

Package name - "mywqsexport"
Destination - Company Home
Include children - Yes
Include self - Yes
Run in background - No

Once you've clicked OK and it's done its work you should see a file named "mywqsexport.acp" in the Company Home folder. Download this file onto your local disk.

Now point your browser at the Explorer app on your new installation. Navigate to the doc lib of your new Share site (Company Home/Sites/wqs/documentLibrary). Follow the instructions on that wiki page to import your shiny new ACP file (again, I tend to NOT run in the background, but it's up to you).

Take your customised wcmqs.war (or whatever you've called it), and configure it to point at your new Alfresco installation. You can do that either by copying it to the Tomcat used by your new installation, or by editing the "wcmqs.api.alfresco" property in a file located on your classpath here: alfresco/extension/wqsapi-custom.properties (the default for that property is "http://localhost:8080/alfresco").

With any luck at all, you will now have your WQS website deployed on your new instance. You may need to edit the metadata on your website nodes in the repository (the ones named "Quick Start Editorial" and "Quick Start Live" by default) to set the host name appropriately.

abbeydom

Hello Brian,

Thanks a lot for this. I can confirm the procedure works and issue now resolved.

Dominic