Deployment Archives - Sourced Code

50 Visual Studio | VS Code Hot Key / Shortcuts for Mac 2023

briankasingli — Mon, 31 Jul 2023 06:55:50 +0000

Welcome to our guide on 50 Visual Studio Code shortcuts for Mac users. Whether you’re a seasoned developer or just starting, mastering these keyboard shortcuts will significantly enhance your coding productivity. Let’s dive in and discover the most efficient key combinations for a seamless coding experience!

For Window users, visit this article, 50 Visual Studio Code Hot Key / Shortcuts for Mac 2023.

Shortcuts List:

(Command + P): Quickly open files by typing their names in the Quick Open dialog.
(Command + N): Create a new file in the current workspace.
(Command + Shift + P): Open the Command Palette to access various commands and settings.
(Command + B): Toggle the visibility of the Side Bar.
(Command + Shift + E): Focus and show the File Explorer in the Side Bar.
(Command + Shift + F): Search across files in the entire workspace.
(Command + J): Toggle the Panel (Output, Terminal, or Debug Console).
(Command + /): Toggle line comments for the selected code.
(Option + Shift + Up/Down Arrow): Move lines of code up or down.
(Option + Click): Add multiple cursors at different positions to edit multiple lines at once.
(Command + Shift + L): Select all occurrences of the current selection.
(Command + D): Add the next occurrence of the current word to the selection.
(Command + G): Jump to a specific line number in the active file.
(Option + Left/Right Arrow): Move the cursor to the beginning/end of the current word.
(Option + Up/Down Arrow): Move the cursor up or down by paragraph.
(Command + Shift + K): Delete the current line.
(Command + Shift + T): Reopen the last closed tab.
(Command + Tab / Command + Shift + Tab): Cycle through open tabs.
(Command + F2): Set multiple cursors to the same word in the file.
(Command + Shift + [ / Command + Shift + ]): Indent or unindent lines of code.
(Option + Shift + O): Sort lines in ascending order.
(Option + Command + Down Arrow): Copy lines down.
(Option + Shift + Down Arrow): Move lines down.
(Option + Shift + Up Arrow): Move lines up.
(Option + Shift + F): Format the selected code.
(Option + Command + U): Transform to uppercase.
(Option + Command + L): Transform to lowercase.
(Command + Enter): Insert a new line below the current line.
(Command + Shift + Enter): Insert a new line above the current line.
(Command + Shift + \): Jump to matching bracket.
(Command + Shift + G): Open the Source Control view.
(Command + Shift + E): Show Explorer/Files view.
(Command + Shift + X): Open the Extensions view.
(Option + Shift + F): Format document in the editor.
(Command + F): Find and replace text.
(Command + Shift + H): Replace in files (Find and replace across multiple files).
(Command + Shift + M): Show Problems panel.
(Command + Shift + U): Show output panel.
(Command + K + W): Close all editor tabs.
(Command + Shift + [ / Command + Shift + ]): Fold or unfold region.
(Option + F12): Show all references of a symbol in the workspace.
(Command + Shift + F10): Run a specific test.
(Command + Shift + D): Open the Debugger panel.
(Command + Shift + O): Go to Symbol in File.
(Command + Shift + U): Go to a symbol’s implementation.
(Command + K + R): Show keyboard shortcuts reference.
(Command + Shift + F): Show keyboard shortcuts reference.

Conclusion:

Boost your coding productivity with these 50 essential Visual Studio Code shortcuts, tailored for Mac users. Incorporate these time-saving key combinations into your coding workflow, and watch as you breeze through tasks with remarkable speed and efficiency. Happy coding!

The post 50 Visual Studio | VS Code Hot Key / Shortcuts for Mac 2023 appeared first on Sourced Code.

Deploying Core Module of the AEM Project

briankasingli — Thu, 22 Dec 2022 04:33:04 +0000

For rapid AEM backend developer, we would like to build the AEM core module bundle to our running local AEM instance. In this article, we will configure the core bundle with an automated script. Simple build the project with mvn clean install -PautoInstallBundle. This is actually a standard that is shipped from the aem-project-archetype-39, but not configured to the AEM core module.

At the creation of this article, I have used https://github.com/adobe/aem-project-archetype/tree/aem-project-archetype-39.

1. Add a new profile in your core/pom.xml

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

>
>
>autoInstallBundle>
>
>false>
>
>
>
>
>
>org.apache.sling>
>sling-maven-plugin>
>2.4.0>
>
>
>install-bundle>
>
>install>
>
>
>${aem.host}:${aem.port}/system/console>
>
>
>
>
>
>
>
>
>

2. Change directory to the core bundle folder, and then run the command below:

1
2
3

cd ~/git/2023/sourcedcode/core

mvn clean install -PautoInstallBundle

3. What’s the difference between Maven plugins vs dependencies?

Plugins are used during the code build phase, when code is being built by Maven; plugins are where much of the real action is performed, plugins are used to: create jar files, create war files, compile code, unit test code, create project documentation, and on and on. Almost any action that you can think of performing on a project is implemented as a Maven plugin.

Dependencies are declared and used by Maven. During the build, Maven will download the dependencies to your local repository and then use this to compile your JAR. We use the

The post Deploying Core Module of the AEM Project appeared first on Sourced Code.

Send Out Emails with AEM Servlet

briankasingli — Fri, 21 Jan 2022 03:31:31 +0000

In this article, we will be setting up the local AEM author developer’s environment to send out an email utilizing the Day CQ Mail Service. This article includes code snippets to a Sling Servlet that will be used to send out the email.

We will be using a Google Gmail account as the SMTP Mail Server in this article. To learn how to set up your Google Gmail account as the SMTP server, click here.

1. Configure the Day CQ Mail Service

a. Visit http://localhost:4502/system/console/configMgr/com.day.cq.mailer.DefaultMailService

b. Include the configurations below:
Google SMTP Configurations
SMTP server hostname: smtp.gmail.com
SMTP server port: 465, 25 or 587 (test in that order)
SMTP user: @@YOUR_EMAIL_ADDRESS@@
SMTP from emai: @@YOUR_EMAIL_ADDRESS@@
SMTP password: @@YOUR_PASSWORD@@
SMTP TLS/SSL: true

To automate this configuration, you can run a Curl command like the example below. But please be aware, you must use your own Google Gmail account.

To update the Curl command below, use this tool here, Tool: Generate Curl Command to Update OSGI Configurations

curl -u admin:admin 'http://localhost:4502/system/console/configMgr/com.day.cq.mailer.DefaultMailService' --data-raw 'apply=true&action=ajaxConfigManager&%24location=&smtp.host=smtp.gmail.com&smtp.port=587&smtp.user=contact@sourcedcode.com&smtp.password=p4ssw0rd&from.address=contact@sourcedcode.com&smtp.ssl=true&propertylist=smtp.host%2Csmtp.port%2Csmtp.user%2Csmtp.password%2Cfrom.address%2Csmtp.ssl'

2. Create the SendEmailServletExample AEM Servlet

Create a Java class named, SendEmailServletExample.java, copy and paste the code below, replace line:44 with your own email, and then use your Java Maven skills to build the servlet in AEM.

Once when the SendEmailServletExample.java is built into AEM, visit http://localhost:4502/bin/sendemail,

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72

package com.sourcedcode.core.servlet;

import com.day.cq.mailer.MessageGateway;
import com.day.cq.mailer.MessageGatewayService;
import org.apache.commons.mail.Email;
import org.apache.commons.mail.EmailException;
import org.apache.commons.mail.HtmlEmail;
import org.apache.sling.api.SlingHttpServletRequest;
import org.apache.sling.api.SlingHttpServletResponse;
import org.apache.sling.api.servlets.SlingAllMethodsServlet;
import org.json.JSONException;
import org.json.JSONObject;
import org.osgi.service.component.annotations.Component;
import org.osgi.service.component.annotations.Reference;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

import javax.servlet.Servlet;
import java.io.IOException;

import static org.apache.sling.api.servlets.ServletResolverConstants.SLING_SERVLET_PATHS;

@Component(
service = { Servlet.class },
property = {
SLING_SERVLET_PATHS + "=/bin/sendemail"
}
)
public class SendEmailServletExample extends SlingAllMethodsServlet {

private static Logger log = LoggerFactory.getLogger(SendEmailServletExample.class);

@Reference
private MessageGatewayService messageGatewayService;

@Override
protected void doGet(SlingHttpServletRequest request, SlingHttpServletResponse response) throws IOException {
JSONObject jsonResponse = new JSONObject();
boolean sent = false;
try {
String[] recipients = { "contact@sourcedcode.com" };
sendEmail("This is an test email",
"This is the email body", recipients);
response.setStatus(200);
sent = true;
} catch (EmailException e) {
response.setStatus(500);
}
try {
jsonResponse.put("result", sent ? "done" : "something went wrong");
} catch (JSONException e) {
e.printStackTrace();
}
response.getWriter().write(jsonResponse.toString());
}

private void sendEmail(String subjectLine, String msgBody, String[] recipients) throws EmailException {
Email email = new HtmlEmail();
for (String recipient : recipients) {
email.addTo(recipient, recipient);
}
email.setSubject(subjectLine);
email.setMsg(msgBody);
MessageGateway<Email> messageGateway = messageGatewayService.getGateway(HtmlEmail.class);
if (messageGateway != null) {
log.debug("sending out email");
messageGateway.send((Email) email);
} else {
log.error("The message gateway could not be retrieved.");
}
}
}

The post Send Out Emails with AEM Servlet appeared first on Sourced Code.

Get Cookie Example of AEM Servlet and Sling Model

briankasingli — Wed, 19 Jan 2022 04:58:31 +0000

In this short article, we will show two code examples; for example, one will be showcasing how cookies values can be accessed for an AEM Servlet, and for example two, Sling Model.

1. AEM Servlet Get Cookie Example

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65

package com.sourcedcode.core.servlet;

import com.cat.wcm.core.util.JSONObject;
import org.apache.commons.lang.StringUtils;
import org.apache.sling.api.SlingHttpServletRequest;
import org.apache.sling.api.SlingHttpServletResponse;
import org.apache.sling.api.servlets.SlingAllMethodsServlet;
import org.osgi.service.component.annotations.Component;

import javax.servlet.Servlet;
import javax.servlet.http.Cookie;
import javax.servlet.http.HttpServletRequest;
import java.io.IOException;

import static org.apache.sling.api.servlets.ServletResolverConstants.SLING_SERVLET_PATHS;

@Component(
service = { Servlet.class },
property = {
SLING_SERVLET_PATHS + "=/bin/getCookieExample"
}
)
public class GetCookieServletExample extends SlingAllMethodsServlet {

@Override
protected void doGet(SlingHttpServletRequest request, SlingHttpServletResponse response) throws IOException {
Cookie myCookie = getCookie(request, "myCookie");
String myCookieValue = "";
if (myCookie != null && !myCookie.getValue().isBlank()) {
myCookieValue = myCookie.getValue();
}

// server response
response.setStatus(200);
response.setContentType("application/json");

JSONObject jsonResponse = new JSONObject();
jsonResponse.put("myCookie", myCookieValue);
response.getWriter().write(jsonResponse.toString());
}

// extracted helper method
private Cookie getCookie(HttpServletRequest request, String cookieName) {
if (StringUtils.isBlank(cookieName)) {
return null;
} else {
Cookie[] cookies = request.getCookies();
if (cookies == null) {
return null;
} else {
if (cookies.length > 0) {
Cookie[] var3 = cookies;
int var4 = cookies.length;
for(int var5 = 0; var5 < var4; ++var5) {
Cookie cookie = var3[var5];
if (StringUtils.equals(cookieName, cookie.getName())) {
return cookie;
}
}
}
return null;
}
}
}
}

2. Sling Model Get Cookie Example

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54

package com.sourcedcode.models.pages.page;

import org.apache.commons.lang.StringUtils;
import org.apache.sling.api.SlingHttpServletRequest;
import org.apache.sling.api.resource.Resource;
import org.apache.sling.models.annotations.DefaultInjectionStrategy;
import org.apache.sling.models.annotations.Model;
import org.apache.sling.models.annotations.injectorspecific.SlingObject;

import javax.annotation.PostConstruct;
import javax.servlet.http.Cookie;
import javax.servlet.http.HttpServletRequest;

@Model(
adaptables = {SlingHttpServletRequest.class, Resource.class},
defaultInjectionStrategy = DefaultInjectionStrategy.OPTIONAL)
public class ExampleModel {

@SlingObject
protected SlingHttpServletRequest request;

@PostConstruct
private void init() {
Cookie myCookie = getCookie(request, "myCookie");
String myCookieValue = "";
if (myCookie != null && !myCookie.getValue().isBlank()) {
myCookieValue = myCookie.getValue();
}
}

// extracted helper method
private Cookie getCookie(HttpServletRequest request, String cookieName) {
if (StringUtils.isBlank(cookieName)) {
return null;
} else {
Cookie[] cookies = request.getCookies();
if (cookies == null) {
return null;
} else {
if (cookies.length > 0) {
Cookie[] var3 = cookies;
int var4 = cookies.length;
for(int var5 = 0; var5 < var4; ++var5) {
Cookie cookie = var3[var5];
if (StringUtils.equals(cookieName, cookie.getName())) {
return cookie;
}
}
}
return null;
}
}
}
}

The post Get Cookie Example of AEM Servlet and Sling Model appeared first on Sourced Code.

5 Popular Ways to Replicate a Page in AEM

briankasingli — Sun, 21 Jun 2020 16:17:11 +0000

In AEM 6+ there are many ways to accomplish the goal to “replicate” a page. This article will display 5 Popular Ways to Replicate a Page in AEM. At the end of this article, you should be able to “replicate” a page using different methods within AEM.

Quick Links:

Touch UI – Site Console – Quick Publish
Touch UI – Site Console – Manage Publication
Touch UI – Editable Page – Sidebar Drop Options
Touch UI – AEM Workflow
CRX/DE – Replication Tab

Typically a scaled AEM structure, security is the highest priority. Typically Content Author’s privileges are restricted, so AEM page publishing is restricted; therefore AEM Workflows are utilised. Click here to skip the the Touch UI – AEM Workflow topic.

1. Touch UI – Site Console – Quick Publish

If you have the right privilege to replicate a page, and all it’s referenced resources, you can simply publish a page with the “Quick Publish” button from the Site Console’s navigation.

How to publish a page using the “Quick Publish” AEM feature:

Step 1: Navigate to the Touch UI – Sites Console http://localhost:4502/sites.html/content.
Step 2: Select on the “Targeted Page” by clicking on the thumbnail tile.
Step 3: Click on “Quick Publish” to replicate the Page.
Done.

2. Touch UI – Site Console – Manage Publication

If you have the right privilege to replicate a page, and all it’s referenced resources, you can simply replicate a page with the “Quick Publish” button from the Site Console’s navigation.

But if you wish to manage the “referenced resources”, you can use the “Manage Publication” replication AEM feature.

How to publish a page using the Manage Publication AEM feature:

Step 1: Navigate to the Touch UI – Sites Console http://localhost:4502/sites.html/content.
Step 2: Select on the “Targeted Page” by clicking on the thumbnail tile.
Step 3: Click on the “Manage Publication” (if your screen is too small, click on the drop down … icon to expose this link).
Step 4: Select on the “Publish” option.
Step 5: Click on “Next”.
Step 6: Review References: By default, all resources in AEM that are referenced by the targeted page will be replicated. References items should be reviewed before replicating the page.
Step 7: Review References – Select on the “Targeted Page” by clicking on the thumbnail tile.
Step 8: Review References – Click on “Published References” to reveal a dialogue of all the referenced resources.
Step 9: Review References – Manage “Targeted References”; radio button clicked mean to “include resource as a part of the page replication. Click on “Done” to save settings.
Step 10: Click on “Publish” to replicate the Page.
Done.

Steps 2 & 3

Steps 4 & 5

Steps 6…10

If you have the right privilege to replicate a page, after a change within the AEM Page Editor, a replication from the sidebar drop options can be utilised to replicate the page.

How to publish a page using from the “Editable Page” AEM feature:

Step 1: Navigate to the Touch UI – Sites Console http://localhost:4502/editor.html/content/we-retail/us/en/about-us.html.
Step 2: Click on “Publish Page” to replicate the Page.

4. Touch UI – Activate a Page with an AEM Workflow

Typically a scaled AEM structure, security is the highest priority. Typically Content Author’s privileges are restricted, so AEM page publishing are restricted; therefore AEM Workflows are utilised.

One of the most popular page publishing type AEM Workflows utilised in AEM is Content Approval AEM Workflows. Content Approval AEM Workflows are implemented based on the business requirements and context of the AEM customer, but as an example of this blog article, we will take the “Request to Publish”, out of the box AEM Workflow model as an example.

The “Request to Publish” is an example of an out of the box AEM Workflow model that can be used by Content Authors with less privileges. When the “Request to Publish” AEM Workflow has been started, a AEM Workflow task is sent to a supporting user-group, for them to approve the request. Once the request have been approved, the page will be replicated; typically a system user is replicating the page with the correct privileges.

How to publish a page using from the “Activate a Page” AEM Workflow:

Step 1: Navigate to the Touch UI – Sites Console http://localhost:4502/sites.html/content.
Step 2: Select on the “Targeted Page” by clicking on the thumbnail tile.
Step 3: Click on “Create” to reveal a drop down menu & Click on “Workflow”.
Step 4: Select on the targeted “Workflow Model”.
Step 5: Input a “Workflow Title”.
Step 6: Click on “Next”.
Step 7: Click on “Create”.
Done. When the page is approved the page will be published.

Steps 2 & 3

Steps 4…6

Step 7

5. CRX/DE – Replication Tab

In some cases where an administrator needs to quickly publish a page, they are utilise the “Replication Tab” within the CRX/DE web console. This feature is only used by users who knows that they are doing.

How to publish a page using “CRX/DE Replication Tab”:

Step 1: Navigate to the CRX/DE Console http://localhost:4502/crx/de/index.jsp
.
Step 2: Select on the “Targeted Page”.
Step 3: Select on the “Replication” tab.
Step 4: Click on “Replicate” to replicate the Page.
Done.

The post 5 Popular Ways to Replicate a Page in AEM appeared first on Sourced Code.

How many times is an AEM Component used in the JCR?

briankasingli — Thu, 11 Jun 2020 23:09:16 +0000

Can we detect and remove unused components from our codebase? Is this AEM component being used at all? How many times is my component used within my running AEM instance?

These are the common questions we have when we are trying to figure out the number of use and the node-paths of the targeted searched component within the Java content repository, known as “JCR”. In this article, you will discover one of the quickest techniques used to retrieve the total number of uses and node-paths of a component within the JCR by using the Query Builder API, query debugger tool.

If you don’t have certain user priveledges within your AEM instance, there’s another way to find out the usage of your component(s), Components Console; however, the Components Console is restricted in a sense where the component search results-list only display pages of a given component and does not provide a total number of how many pages are returned from the search.

Quick Links

Component Search by the Query Builder API, Query Builder Debugger Tool
Component Search by the Components Console
Extra: How many pages are using an AEM template?
Extra: How to search for all nodes in AEM, JCR, with an existing property?

1. Component Search by the Query Builder API, Query Builder Debugger Tool

The AEM Query Builder is an API which can be used to search for nodes in JCR. Well defined “Predicates” are typically created from using the Query Builder Debugging Tool, as this tool serves instant search results within the UI.

Step 1: With your running AEM instance, visit http://localhost:4502/libs/cq/search/content/querydebug.html.

Step 2: Paste in the search query below & hit search; view screenshot.
Replace with your component’s path: weretail/components/content/heroimage
Note!: sometimes the descendant path must be more nested, so /content/we-retail/gb/en

1
2
3

path=/content/we-retail
1_property=sling:resourceType
1_property.value=weretail/components/content/heroimage

This query searches for all types of nodes with the sling:resourceType equals to the value, weretail/components/content/heroimage, and where the path is descendant from /content/we-retail; to learn more about the Query builder API and queries, click here (Adobe Documentation)

Step 3: Review the results.

Extra:

Find out How many pages are using an AEM template?

The query below will find all cq:Page nodes in the JCR, which cq:template equals to /conf/we-retail/settings/wcm/templates/hero-page; under the content path /content/we-retail. The search results will show you the absolute node page path of whom has the matched property and value set.

1
2
3
4

type=cq:Page
path=/content/we-retail
1_property=jcr:content/cq:template
1_property.value=/conf/we-retail/settings/wcm/templates/hero-page

Ensuring that the “path” property is set is important, because you would not want to excessively triverse through the entire JCR; which will exhaust the AEM environment performance.

Extra:

How to search for all nodes in AEM, JCR, with an existing property?

The query below will search all nodes in the JCR, which “myCustomProperty” exists; under the content path /content/we-retail. The search results will show you the absolute node page path of whom has the matched property and value set.

1
2
3

path=/content/we-retail
property=myCustomProperty
property.operation=exists

Ensuring that the “path” property is set is important, because you would not want to excessively triverse through the entire JCR; which will exhaust the AEM environment performance.

2. Component Search by the Components Console

This out of the box Components Console, CC, is available from AEM 6.2+ right under Tools -> General -> Components. The CC displays search results in a form of pages where the component is being used; rather than each node from the example above. This console is accessible to authors so that even they can check for which pages use the searched component.

Step 1: Within your running AEM instance, visit http://localhost:4502/libs/wcm/core/content/sites/components.html.

Step 2: Search for a component. Insert your search criteria with either by “keyword”, “component path”, or “component group”. On every change of the search criteria, you should see results in a list format on the right hand side of the search left side bar.
Step 3: Click on the targeted component, and you will be redirected to the details page.
Step 4: From the details page, click on “live usage”, and a results-list of pages will be displayed, where the targeted component can be found.
Step 5: From the results-list, clicking on a link will open the page’s editor.

Components Console – Steps 2 & 3

Components Console – Steps 4 & 5

The post How many times is an AEM Component used in the JCR? appeared first on Sourced Code.

How to Check all Active Run Modes in a Running AEM Instance.

briankasingli — Fri, 01 Nov 2019 21:38:02 +0000

The fastest way to retrieve all active run modes that are enabled within a running AEM instance would be from the OSGI console, Apache Sling Settings.

Follow the two simple steps below:

Log in to AEM as an admin or a user who has access to the OSGI console using this URL: http://localhost:4502/crx/de/index.jsp
Navigate to the Apache Sling Settings OSGI console page http://localhost:4502/system/console/status-slingsettings

Expected screen from visiting http://localhost:4502/system/console/status-slingsettings

The active AEM run modes here are: “local-local”, “s7connect”, “crx3”, “author”, “samplecontent”, “local”, “crx3tar:

Propertie Breakdown

Sling ID: A unique identifier of the running Sling instance. This value is created when Sling is first started and may be used to identify the instance, for example if multiple Sling instances are running on top of a Jackrabbit Repository Cluster.
Sling Home: The absolute filesystem path to the directory where Sling stores all its content.
Sling Home URL: The Sling Home path as an java.net.URL instance.
Run Modes: The active Run Modes of the running Sling instance.

The post How to Check all Active Run Modes in a Running AEM Instance. appeared first on Sourced Code.

How to install multiple packages in CRX/DE on a clean instance?

briankasingli — Mon, 09 Apr 2018 23:28:07 +0000

You are ready to ship your project packages and package-dependencies over to your customers. You have 7+ packages that need to be individually installed; installing 7 packages is manually is not the best approach, and it will take too long (imagine when there are 5 AEM instances that need to be configured). What is the fastest way to install multiple packages into CRX/DE? The answer is automation.

Pre-requisites:

Standalone AEM instance, quickstart jar
Java SE installed on your machine
CQ5.5 and above

To install multiple packages in CRX/DE during a clean application startup automatically

Open terminal or command line, and change directory to your standalone AEM instance, quickstart jar file.
In terminal or command line:
1
java -jar cq-author-4502.jar -unpack

This line of code unpacks the installation files for the jar file, and will not run AEM. You should see a /crx-quickstart folder being generated.
Create the folder “install” under “/crx-quickstart/install”.
Include all the packages in the “install” folder; this will upload and install all the packages within the folder on a application startup;packages will install in alphabetical order.
Start AEM.
Visit CRX/DE Lite, package manager to ensure all packages are installed(http://localhost:4502/crx/packmgr/index.jsp).
Done.

Final Notes

When working with AEM 6.3 forms package addon, I suggest to not include the forms packages in the automation. This will break your AEM instance. I tried it multiple times.

The post How to install multiple packages in CRX/DE on a clean instance? appeared first on Sourced Code.

How to revert deployed packages in CRX/DE package manager?

briankasingli — Wed, 04 Apr 2018 16:46:50 +0000

In this tutorial, you will learn how to revert a deployed package in CRX/DE package manager.

The package is uploaded into CRX/DE and not yet replicated.

Visit CRX/DE Lite (http://localhost:4502/crx/packmgr/index.jsp)
Locate the project package.
Click on “more” (the drop-down on the right).
Click on “uninstall” (this will ensure your AEM instance is back to what it was before the installation. Imagine all the “filter paths” have taken a backup snapshot. When uninstalling your package, this will bring your backup snapshot of back to life, and delete any thing in the folder that is not in the snapshot.)
Delete the current version (unwanted version) of the project package.
Done.

The package is uploaded into CRX/DE and has already been replicated.

Visit CRX/DE Lite (http://localhost:4502/crx/packmgr/index.jsp)
Locate the project package.
Click on “more” (the drop-down on the right).
Click on “uninstall” (this will ensure your AEM instance is back to what it was before the installation. Imagine all the “filter paths” have taken a backup snapshot. When uninstalling your package, this will bring your backup snapshot of back to life, and delete any thing in the folder that is not in the snapshot.)
Delete the current version (unwanted version) of the project package.
Repeat steps 1-5 for all your AEM instances (Author and Publish AEM servers)

Final Notes

I insist not to replicate the /content folder that holds your site pages. This will replicate(copy) all your web pages to your publish instance. Even if your site manager indicates whether your page is not active, your page will be copied over to the publish instance and will available to your consumers.

The post How to revert deployed packages in CRX/DE package manager? appeared first on Sourced Code.

How to deploy new releases manually on Staging and Production AEM environments?

briankasingli — Tue, 03 Apr 2018 19:30:11 +0000

There are many ways for deploying new releases to AEM staging and Production environments. In this tutorial, I will share with you my process for deploying new releases manually. I personally found this the safer way to deploy new releases because you can easily roll back versions, and you let AEM’s out of the box replicate agents transport new changes to your production publish environments.

This tutorial illustrates how you would manually deploy a new content package to AEM staging and AEM production environments, manually.

Scenarios

Scenario 1: You are ready to make a release on Staging on AEM-onPrem
Scenario 2: You are ready to make a new release on Productionon AEM-onPrem

Scenario 1: You are ready to make a new release on Staging

Change the project version in maven(remove SNAPSHOT, because SNAPSHOT packages are only for development).

1
2
3
4

// documentation: http://www.mojohaus.org/versions-maven-plugin/examples/set.html
// updates project version to 1.2.0 (remove "SNAPSHOT", and don't commit version)
mvn versions:set -DnewVersion=1.2.0
mvn versions:commit

Build your project to your local machine.
1
2
3
<code lang="java">
// builds your maven project into target without installing packages on AEM
mvn clean install -Padobe-public

// output ui.apps in /ui.apps/target/{projectName}.ui.apps-x.x.x.zip
// output ui.content in /ui.content/target/{projectName}.ui.content-x.x.x.zip
Upload the build (/ui.apps/target/{projectName}.ui.apps-x.x.x.zip) into “Staging Author”, package manager.
Upload the build (/ui.content/target/{projectName}.ui.content-x.x.x.zip) into “Staging Author”, package manager.
Replicate {projectName}.ui.apps-x.x.x.zip to Staging Publish. Replicating this package will ensure that all your publish instances will be up to date; all files are overwritten.
Do not replicate ui.content because unpublished pages will all be replicated to your publish instance. You can activate pages in the author instance at your desire.
Done.

Scenario 2: You are ready to make a new release on Production

Your updates on the staging environment have been approved, and now we want to deploy a new release on to production; the version of your packages should be the same version as your approved staging packages.

Change the project version in maven(remove SNAPSHOT because SNAPSHOT packages are only for development).

1
2
3
4

Build your project to your local machine.
1
2
3
<code lang="java">
// builds your maven project into target without installing packages on AEM
mvn clean install -Padobe-public

// output ui.apps in /ui.apps/target/{projectName}.ui.apps-x.x.x.zip
// output ui.content in /ui.content/target/{projectName}.ui.content-x.x.x.zip
Upload the build (/ui.apps/target/{projectName}.ui.apps-x.x.x.zip) into “Production Author”, package manager.
Upload the build (/ui.content/target/{projectName}.ui.content-x.x.x.zip) into “Production Author”, package manager.
Replicate {projectName}.ui.apps-x.x.x.zip to Production Publish. Replicating this package will ensure that all your publish instances will be up to date; all files are overwritten.
Do not replicate ui.content because unpublished pages will all be replicated to your publish instance. You can activate pages in the author instance at your desire.
Check-in your code to master (and request for a pull request) with the “SNAPSHOT” label removed in your .pom file.
Tag your master with v1.2.0 (or whichever version you are working on)

Final Notes

There are many ways of deploying new releases to your AEM Staging or Production environments, but this is my take on this for a manual release strategy. Please leave a comment if you have any questions or suggestions on how I can improve me “package manager oriented way of deploying my releases”.

The post How to deploy new releases manually on Staging and Production AEM environments? appeared first on Sourced Code.

Deployment Archives - Sourced Code

50 Visual Studio | VS Code Hot Key / Shortcuts for Mac 2023

Shortcuts List:

Conclusion:

Deploying Core Module of the AEM Project

1. Add a new profile in your core/pom.xml

2. Change directory to the core bundle folder, and then run the command below:

3. What’s the difference between Maven plugins vs dependencies?

Send Out Emails with AEM Servlet

1. Configure the Day CQ Mail Service

2. Create the SendEmailServletExample AEM Servlet

Get Cookie Example of AEM Servlet and Sling Model

1. AEM Servlet Get Cookie Example

2. Sling Model Get Cookie Example

5 Popular Ways to Replicate a Page in AEM

1. Touch UI – Site Console – Quick Publish

How to publish a page using the “Quick Publish” AEM feature:

2. Touch UI – Site Console – Manage Publication

How to publish a page using the Manage Publication AEM feature:

3. Touch UI – Editable Page – Sidebar Drop Options

How to publish a page using from the “Editable Page” AEM feature:

4. Touch UI – Activate a Page with an AEM Workflow

How to publish a page using from the “Activate a Page” AEM Workflow:

5. CRX/DE – Replication Tab

How to publish a page using “CRX/DE Replication Tab”:

How many times is an AEM Component used in the JCR?

1. Component Search by the Query Builder API, Query Builder Debugger Tool

Find out How many pages are using an AEM template?

How to search for all nodes in AEM, JCR, with an existing property?

2. Component Search by the Components Console

How to Check all Active Run Modes in a Running AEM Instance.

Follow the two simple steps below:

Propertie Breakdown

How to install multiple packages in CRX/DE on a clean instance?

To install multiple packages in CRX/DE during a clean application startup automatically

Final Notes

How to revert deployed packages in CRX/DE package manager?

The package is uploaded into CRX/DE and not yet replicated.

The package is uploaded into CRX/DE and has already been replicated.

Final Notes

How to deploy new releases manually on Staging and Production AEM environments?

Scenarios

Scenario 1: You are ready to make a new release on Staging

Scenario 2: You are ready to make a new release on Production

Final Notes