How to add sling pipes in the project

[VenkateshKA6]

Hi AEM Community,

II'm looking for insights on adding Sling Pipes in the project using pom.xml in AEM Cloud.

Added below dependencies in all/pom.xml,  tenant/pom.xml and root/pom.xml

<dependency>
    <groupId>org.apache.sling</groupId>
    <artifactId>org.apache.sling.pipes</artifactId>
    <version>4.5.0</version>
</dependency>
<dependency>
    <groupId>org.apache.sling</groupId>
    <artifactId>org.apache.sling.query</artifactId>
    <version>4.0.4</version>
</dependency>

Added below com.adobe.dx in tentant.pom and root.pom

<dependency>
    <groupId>com.adobe.dx</groupId>
    <artifactId>content</artifactId>
    <version>0.0.10</version>
</dependency>

Installed script by manually downloading(since not downloading via pom) adobe-dx/apps/scripts/pipe and executing mvn clean install.

Getting forbidden when accessing http://localhost:4502/apps/dx/scripts/exec.json/ .

Please share your strategies and experiences in this area!

[arunpatidar]

Hi @VenkateshKA6 

Since you are accessing Author instance, You need to login 

Sling pipes : check https://sling.apache.org/documentation/bundles/sling-pipes.html 

for sling query check - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-sling-query-comprehens... 

You may need to install Sling pipes and sling query bundle in AEM as well.

[ManviSharma · Accepted solution]

Hi,

The "forbidden" access error when trying to access http://localhost:4502/apps/dx/scripts/exec.json/ typically suggests a permissions issue.
- Also, If the script is not downloading via pom.xml, it might be due to the package not being available in the configured Maven repositories.

[kautuk_sahni]

@VenkateshKA6 Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!

[simonc39079524]

Just in case anyone else is like me and didn't find the "correct answer" useful, particularly if you've upgraded from Sling Pipes 3.x to 4.x

The forbidden access occurs because you need to create a node at :

/system/sling/permissions/pipes/exec

Permissions can then be set on that node to control who can run the pipes.

This isn't mentioned in the Apache documentation, but is referenced in these presentations:
https://www.slideshare.net/slideshow/sling-pipes/244540797#7
https://adapt.to/2020/presentations/adaptto2020-lightningtalk-sling-pipes-4-0-0-update-nicolas-pelti...

You'll also see that the DX Content package for Scripts adds a folder there if you dig into the code or look at what the package installs.