Adobe Experience Manager (AEM) is a server-side application that runs on the Java platform. It is available in two forms:
· A standalone executable jar file referred to as a quickstart file.
· A war file that can be deployed in a third-party application server.
· A standalone executable jar file referred to as a quickstart file.
· A war file that can be deployed in a third-party application server.
What is Must?
For installing Adobe Experience Manager, you at least need below
· Installed Java Platform, Standard Edition JDK (Minimum 1.8)
· Experience Manager Quickstart file (Either JAR or WAR) and valid license files
· A system with at least 2 GB RAM and 5 GB space in the installation directory.
· If you are working on a content-heavy website, which uses more assets, then you will need more base memory·
For installing Adobe Experience Manager, you at least need below
· Installed Java Platform, Standard Edition JDK (Minimum 1.8)
· Experience Manager Quickstart file (Either JAR or WAR) and valid license files
· A system with at least 2 GB RAM and 5 GB space in the installation directory.
· If you are working on a content-heavy website, which uses more assets, then you will need more base memory·
Installing an Author Instance of Adobe Experience Manager:
Typical AEM installation involves at least two AEM instances. An instance is a copy of AEM running on a server.
Author: An AEM instance used to administer the website and content management (create, upload, edit, delete, etc…). Content is moved to publish instance (replicated), once the content is ready to go live.
Publish: An AEM instance that serves the published content to the public.
Author and publish instances are differentiated by configuration only and are the same in terms of installed software.
Typical AEM installation involves at least two AEM instances. An instance is a copy of AEM running on a server.
Author: An AEM instance used to administer the website and content management (create, upload, edit, delete, etc…). Content is moved to publish instance (replicated), once the content is ready to go live.
Publish: An AEM instance that serves the published content to the public.
Author and publish instances are differentiated by configuration only and are the same in terms of installed software.
Generally, AEM needs to be set up in both Author and Publish mode i.e. setup author instance and publish instance. Both author and publish instance setup contains almost the same steps. This procedure describes how to set up a default Author instance on port 4502 of the desired host.
To install an author instance:
1. In your file system, under installation directory (ex. C:/AEM62), create a directory and name it Author.
2. Copy the cq5-.jar file into the author directory along with license files(C:/AEM62/Author).
3. Rename cq5-.jar to cq5-author-p4502.jar.
· cq: You can use any name here, cq refers to the communique.
· author: It specifies the WCM mode in which instance will be started
· 4502: It specifies the port AEM starts on. If you do not specify anything here it will start by default on 4502.
1. In your file system, under installation directory (ex. C:/AEM62), create a directory and name it Author.
2. Copy the cq5-.jar file into the author directory along with license files(C:/AEM62/Author).
3. Rename cq5-.jar to cq5-author-p4502.jar.
· cq: You can use any name here, cq refers to the communique.
· author: It specifies the WCM mode in which instance will be started
· 4502: It specifies the port AEM starts on. If you do not specify anything here it will start by default on 4502.
Note: If that port is not available or already in use, quickstart automatically checks and starts on the mentioned ports serially: 4502, 8080, 8081, 8082, 8083, 8084, 8085, 8888, 9362,.
Now the AEM file is ready for installation, we just need to start the AEM file for installation. There are altogether 3 methods to start AEM
1. Double-click the cq5-author-p4502.jar file
2. Using Command Prompt
3. Using custom script (start.bat and stop.bat)
· Double-click the cq5-author-p4502.jar file
Now the AEM file is ready for installation, we just need to start the AEM file for installation. There are altogether 3 methods to start AEM
1. Double-click the cq5-author-p4502.jar file
2. Using Command Prompt
3. Using custom script (start.bat and stop.bat)
· Double-click the cq5-author-p4502.jar file
It is recommended for systems having a GUI file-system explorer.
· Using Command Prompt
for a 32bit VM type:
java -Xmx1024M -jar cq5-author-p4502.jar
Or, for a 64bit VM, type:
java -XX:MaxPermSize=256m -Xmx1024M -jar cq5-author-p4502.jar
· Using custom script (start.bat and stop.bat)
· Using Command Prompt
for a 32bit VM type:
java -Xmx1024M -jar cq5-author-p4502.jar
Or, for a 64bit VM, type:
java -XX:MaxPermSize=256m -Xmx1024M -jar cq5-author-p4502.jar
· Using custom script (start.bat and stop.bat)
Use a custom script located in the bin (crx-quickstart\bin) folder, such as start.bat to start AEM. The Start and Stop scripts are for UNIX, Linux, and Macintosh. The start.bat and stop.bat scripts are for Windows.
Note: If you are installing AEM for the first time, you must unpack the jar to access custom scripts in the repository. To unpack the jar using java -jar cq5-author-p4502.jar –unpack command
Once installation completes, you will be automatically redirected to new web browser window opening http://localhost:4502/
The Default credentials for newly installed AEM instance are
User Name: admin
Password: admin
Enter credentials and start exploring your fresh AEM author instance.
Once installation completes, you will be automatically redirected to new web browser window opening http://localhost:4502/
The Default credentials for newly installed AEM instance are
User Name: admin
Password: admin
Enter credentials and start exploring your fresh AEM author instance.
No comments:
Post a Comment
If you have any doubts or questions, please let us know.