I wanted to integrate AEM (6.3) with Magento (2.1.10) to show products on AEM page, I have searched a lot but not getting any proper documentation.
Although I followed below link :
https://helpx.adobe.com/experience-manager/6-3/sites/deploying/using/magento.html
Through this link I got connector, and I installed that connector for AEM, But I am not able to install the connector on Magento as I am new to Magento. I'd like to add connector in Magento or integrate AEM with Magento.
To install the AEM extension in Magento you have to place the content of the extension under /app/code/{name of provider}/{name of extension} (in this case, the name of the provider is InfieldDigital and the name of the extension is Sample) in your Magento instance folder.
After that, you'll be able to find your extension listed in the in the Module Manager tab under the Web Setup Wizard.
Finally, you'll have to enable said extension in Magento. After following the steps, you should be ready to go.
I was able to fix this with changing jcr:primaryType="nt:unstructured" to jcr:primaryType="sling:Orderedfolder"
Fixes:
Replace jcr:primaryType="nt:unstructured" with jcr:primaryType="sling:Orderedfolder" under jcr:root(line 3) for both the below files:
.content.xml file under /magento2-aem-connector-master 2/aem-connector/ui.apps/src/main/content/jcr_root/apps/commerce/gui/content/catalogs/importblueprintswizard/importers/magento/
.content.xml file under /magento2-aem-connector-master 2/aem-connector/ui.apps/src/main/content/jcr_root/apps/commerce/gui/content/products/importproductswizard/importers/magento/
Rebuild and install the package 'mvn clean install -PautoInstallPackage'
Check the repository.. nodes should have installed correctly:
Download and install this Package in package manager: updated package for AEM Magento Integration.
After that follow below steps to import catalog:
Goto AEM navigation screen, click on "commerce" > click on "Catalogs".
Create folder magento, goto magento folder.
click on create, then "Import Blueprints".
Select Magento from Importer.
Enter server URL(not admin URL), admin username, password, write and name for catalog and write "we-retail" in theme.
Click on import.
Catalog will be imported.
To import products follow below steps:
Goto AEM navigation screen, click on "commerce" > click on "Products".
Create folder magento, goto magento folder.
click on create, then "Import Products".
Select Magento from Importer.
Enter server URL(not admin URL), admin username, and password.
Click on import.
Catalog will be imported.
You can download the AEM connector from: https://helpx.adobe.com/it/experience-manager/6-4/sites/deploying/using/magento.html
Inside the magento2-aem-connector-master.zip, there are two folders
aem-connector
magento2
In AEM side, follow the steps:
extract aem-connector and go to the location:
magento2-aem-connector-master\aem-connector\ui.apps\src\main\content\jcr_root\apps\commerce\gui\content\catalogs\importblueprintswizard\importers\magento
here, one content file available open and change the line "3":
from: jcrSmiley TonguerimaryType="nt:unstructured"
to: jcrSmiley TonguerimaryType="slingSmiley Surprisedrderedfolder" and
extract magento2, and go to the location:
magento2-aem-connector-master\aem-connector\ui.apps\src\main\content\jcr_root\apps\commerce\gui\content\products\importproductswizard\importers\magento
open it and change:
from: jcrSmiley TonguerimaryType="nt:unstructured"
to: jcrSmiley TonguerimaryType="slingSmiley Surprisedrderedfolder"
Save both product and catalog file.
Upload to the aem connector to eclipse and build the package using maven:
mvn clean install -P installPackage
check the package available in AEM package manager
http://localhost:4502/crx/packmgr/index.jsp
also:
http://localhost:4502/system/console/bundles magento bundle in active state.
under http://localhost:4502/system/console/configMgr
configure the Magento identity provider, synchandler, external login module:
magento2-aem-connector-master\aem-connector\readme --follow file
Related
Unable to read repository at https://testng.org/testng-eclipse-update-site/content.xml
Am getting this message while trying to install testng getting the updated link from testng.org downloads....
Please use the below step to install it on eclipse:
Install via Eclipse Marketplace
Go to the TestNG page on the Eclipse Market Place and drag the icon called "Install" onto your workspace.
OR
Install from update site
Select Help / Install New Software...
Enter the update site URL in
"Work with:" field: Update site for release:
https://testng.org/testng-eclipse-update-site.
Make sure the check
box next to URL is checked and click Next.
Eclipse will then guide
you through the process.
Ref: https://testng.org/doc/download.html
Main update site URL: https://testng.org/testng-eclipse-update-site
Also you can use the below link directly, if you want to install a specific version:
Versioned update site URL:
https://testng.org/testng-eclipse-update-site/7.4.0
https://testng.org/testng-eclipse-update-site/7.3.0
https://testng.org/testng-eclipse-update-site/7.2.0
https://testng.org/testng-eclipse-update-site/7.1.0
https://testng.org/testng-eclipse-update-site/7.0.0
https://testng.org/testng-eclipse-update-site/6.14.3
We have a cdt eclipse product. We work on windows XP and Bundle JRE for this environment with the product option in launching page of product file does not work...
We want to upgrade our jre via update. We have the JRE in our previous bundle and dont want to copy paste new version manually but we want to do it via update repository... How can we do this ? Is it possible to change the JRE via update ?
You will need to create a p2 update site (possible with eclipse tycho) and these are the steps you need (kind of tedious)
Open a new workspace
Create a new feature project -> new -> plugin development > feature
Give your feature an ID and name
import your new jre bundle into the workspace and increment the version to what it should be.
go to your feature.xml in the feature project, click "included plugins" and add the jre bundle plugin.
Next in the site.xml (or category.xml based on what version of eclipse you have) of the update site you created select site map editor view, create a new category called "JRE Runtimes" or something like that. under that category add the feature you created using the wizard.
Then to build the p2 site In the sitemap view of the site.xml editor click "build all"
After that completes you can refresh the update site plugin and you will see a folder for plugins/features/ and other resource files for the update site. Then you can do a couple of things, the best is to zip that entire update site and upload to an FTP site or HTTP Site in its extracted state and if you give your users the URL they can go into the app, go to help -> install new software. Add a new update site using the URL you provide. Once they do that they can view the features to install and clicking on the feature you created will install the updated jre bundle version.
There are some more gotcha's though, if you have plugins in the app that specify a specific version of the jre bundle it will not use the new one. Best way is to not specify a version and it will use the newest one. Also going forward you should do this same process for your entire app so users can get updates using the p2 provisioning framework. If you want to automate the building of the update site look into eclipse tycho which can also upload the p2 site for you every release.
Hope that helps - Duncan Krebs
How can we remove default HomePage Theme with Custom Theme in DNN 8? I haven't got any blog providing me clear idea about it.
You can change the styling of a page by changing the "Skin" or "Theme" in the Page Settings on the page.
Update:
To create a skin I highly recommend you follow my tutorials:
http://www.christoc.com/Tutorials/All-Tutorials/aid/8
In order to use the DNN Theme Project template (new with the 4.0 release of Christoc’s development templates, January 2015), you will need to follow the steps laid out in this tutorial exactly. If you choose to not follow each of the steps, you may run into trouble and will have to figure out things on your own. As always, support for our tutorials is provided in the form of paid DNN Support and Consulting. You can also visit www.dnnchat.com and possibly get some free support there, but no guarantees are made that support will be provided there.
Prerequisites
The latest release of the Project templates requires Visual Studio 2013+, it will not work on VS2010 or VS2012.
As with the Module Development templates, the Theme development template requires you to have your DNN Development environment configured in a specific way. You should have your development environment running at the URL http://dnndev.me/ good news for you, it is very easy to do, all you need to do is follow this tutorial.
Once you have your environment setup, you need to install the Project templates. This is another easy step, simply follow this tutorial.
Now that you have the Templates installed, you can get to doing the real work, working with the Theme project template itself.
How to use the DNN Theme Project Template
Run Visual Studio 2013 as an Administrator (right click on the shortcut to do so)
File –> New Project
Choose the Visual C# option from the Languages section of the new project dialog
Select the DotNetNuke Folder
Choose the DotNetNuke C# Compiled Theme template for your project template
For the new project creation screen using the following settings
Name: ThemeName (something unique here, example MyFirstTheme)
Location: c:\websites\dnndev.me\portals_default\skins\ (this assumes you setup your development environment as instructed) DO NOT PUT THE SKIN IN /PORTALS/#/SKINS/
Solution: Create new solution
Create directory for solution : Unchecked (this will cause path problems if checked, the templates assume the SLN is in the same folder as the project file)
Add to source control: Unchecked
Click OK
Once your Theme has been created, you will want to perform the following steps.
After project creation steps
Delete the Documentation folder (it isn’t needed)
Switch from DEBUG to RELEASE mode
Build the project. This will create an INSTALL and SOURCE zip file in the /install folder within the project’s folder on the file system (/portals/_default/skins/themename/install/)
Login to your DNNDEV.me site with a HOST/Super User account
Navigate to the Host/Extensions page
Upload the newly created INSTALL zip file (created in step 3) using the Install Extension Wizard on the Host/Extensions page.
Navigate to a Page and apply the skin to your page.
A few items of Note:
The Theme template and package MUST be in the /portals/_default/skins/ folder, not in one of the individual portal’s (/portals/0/skins/) folders.
The Containers are inside of the Containers folder, inside of the project. This is not where DNN expects them to be, they need to be in /portals/_default/containers/ThemeName/. The Project templates will put them into that location in your development environment when you BUILD the project in RELEASE mode. During Installation in another environment, when installing the INSTALL package for the theme will do the same thing.
I creat an eclipse plugin that I finished.
I would like to "share" my plugin with some people without just send them the whole code and they have to "create" the plugin by copy paste the code.
How can I make an installation file/ other way to make this plugin installable for others.
Thanks
One option is to create a Feature project. (An Eclipse Feature is essentially a feature.xml file and build.properties file that specify a collection of one or more Eclipse plugins that will be included when the Feature is installed into an Eclipse application).
Feature projects allow you to choose which plugins to include in them when you create them using the New Feature Project Wizard.
Once your project is created, you will have the feature.xml file opened for you in its editor. There you will be able to fill in more meta data if desired, and you will be given links for Exporting and Publishing the feature for others to consume.
Follow the steps under "Exporting" in the Overview tab of the feature.xml editor and choose to deploy using the Export Wizard. I suggest that you choose to deploy to an Archive file.
Then you can send that resulting Archive file (zip file) to your people. Then have those people open their Eclipse instance and go to "Help -> Install New Software". Then choose "Add" to add an update site. Then choose "Archive" which will allow them to navigate to the zip file that you have sent them.
Once they select that, they will be on their way to installing your Feature which contains your plugin into their Eclispe installation.
You can send them the plugin jar file, and they can put it in their
dropins folder.
Eclipse will not let you install using an archive unless the you have an update site.
In our source code, we have some dialog.xml files to represent the structure of our dialog components. We deploy the project via maven to our local CQ server for development and testing. There are times we need to modify the dialog component via CRXDE Lite (in the CQ server) because it's much faster to edit the dialog that way.
The problem is: How do I export (from CRXDE Lite) the edited dialog component back to it's corresponding dialog.xml file?
CRXDE Lite itself doesn't provide export-to-XML feature, but you can get your dialog.xml in a few different ways. Let's assume you want to get dialog for the /libs/foundation/components/text component:
1. Sling GET servlet - quick & dirty
Enter the dialog path to your browser and add .xml extension:
http://localhost:4502/libs/foundation/components/text/dialog.xml
2. VLT - recommended way
Use VLT Tool which is a standard way to synchronize between JCR and local filesystem:
vlt export http://localhost:4502/crx /libs/foundation/components/text my-export
# cat my-export/jcr_root/libs/foundation/components/text/dialog.xml
3. Package manager
Open /crx/packmgr/index.jsp and click Build on the package that contains the first version of dialog. It'll rebuild the package using current content. Download the package, unzip it and find appropriate dialog.xml file inside.
Another way of doing this (related to the third option described in Tomek Rękawek's answer) is to create a package using CRXDE Lite's Package Manager. Here is an easy step-by-step guide on how to do it:
Open CQ5, and go to CRXDE Lite.
Click on the "Package" icon on the top bar
Click on the "Create Package" link.
A pop-up will open, enter a name and version for the package that you want to create and assign it to a group:
Now the package that you created will be displayed in the list of packages, click on its title to get some additional options:
Click on edit and a new pop-up window will show up. Then click on the "Filters" tab, you should not have any as you just created the package:
Click on "Add filter" button, and enter the path of the component that you wan to export in the "Root path" field (for example, I created a textimage2 component for the Geometrixx app based on this tutorial):
Click on "Done", the filter should show now:
Click on the "Save" button.
The filter should display now in the description of the package. Click on the "Build" option:
A confirmation message will be displayed, click on "Build" again:
Now all the options for the package will be active. Click on the "Download" one to get the ZIP with all the files.
Extract the contents of the ZIP file, the dialog.xml file will be there for you to modify.
I know the process may seem a bit long, but it is really easy to complete, and it has the great advantage of being reusable: once you create a package, you only need to rebuild it to get the latest version of the component's code in ZIP.
It is really easy to import/share too once modified: just zip again all the files (keeping the folder structure) and use the "Upload Package" feature from CRX Package Manager.
WebDAV is one more way to export and import jcr-repository content;
To get access to the repository, at first, you have to take any webdav client (Total Commander with WebDAV plugin is the best or BitKinex).
Ensure 'Apache Sling Simple WebDAV Access to repositories (org.apache.sling.jcr.webdav)' bundle is in 'active' state (on the tab 'h t t p://host:port/system/console/bundles');
Just connect to your instance by webdav client by url:
host:port\crx\repository\crx.default
provide instance's login and password;
As a result - you can download or upload files from or into repository to/from your file system. It works more stable than vlt synchronization starting from cq 5.5 (we had problems with cq 5.4); An we had many probles with vlt even on cq 5.6 (like '[ERROR] checkout: java.lang.NullPointerException: null' during check out process)