Building a cURL-Ready AEM CommandĬURL commands can be built for most operations in AEM such as triggering workflows, checking OSGi configurations, triggering JMX commands, creating replication agents, and much more. ĬURL’s source repository can be found on GitHub as well. However it is avaialble for most every operating system. Downloading cURLĬURL is a standard part of macOS and some Linux distros. All ACLs and access rights are respected when using cURL to execute an AEM command. In addition you can create your own cURL commands for most tasks in AEM.Īny AEM command executed through cURL has to be authorized just as any user to AEM. Content manipulation tasks such as activating pages, and starting workflows as well as operational tasks such as package management and managing users can be automated using cURL. The name cURL originally meant “see URL.”īecause of the RESTful nature of the Sling framework upon which AEM is built, most tasks can be reduced to a URL call, which can be executed with cURL. It supports a wide range of internet protocols including HTTP, HTTPS, FTP, FTPS, SCP, SFTP, TFTP, LDAP, DAP, DICT, TELNET, FILE, IMAP, POP3, SMTP, and RTSP.ĬURL is a well-established and widely-used tool for getting or sending data using the URL syntax and was originally released in 1997. What is cURLĬURL is an open-source command-line tool used to perform URL manipulations. cURL can be used to execute such URL calls and can be a useful tool for AEM administrators. In AEM for example, managing users, installing packages, and managing OSGi bundles are tasks that must be commonly done.īecause of the RESTful nature of the Sling framework upon which AEM is built, most tasks can be done with a URL call. Administrators often need to automate or simplify common tasks within any system.
0 kommentar(er)
