Installation and Setup - AEM as a Cloud Service – Straker Translations

Installation

Section 1: Add S3 Bucket artefact information for Straker

1. Create a file in your repository called settings.xml (or modify the current one) in your AEM as a Cloud Service git repository. The path for this file should be .cloudmanager/maven /settings.xml

2. Add a straker-aem-repo with the AWS API keys given by Straker. The resulting file should look something like this:

<?xml version="1.0" encoding="UTF-8"?>

<settings

 xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"

 xmlns="http://maven.apache.org/SETTINGS/1.0.0"

 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

 <servers>

 <server>

 <id>straker-aem-connector-snapshots</id>

 <username>AAAAAAAA</username> <!-- Straker given AWS API key -->

 <password>BBBBBBB</password> <!-- Straker given AWS API secret -->

 <configuration>

 <endpoint>https://s3.eu-de.cloud-object-storage.appdomain.cloud</endpoint>

 <region>eu-de</region>

 <pathStyleEnabled>true</pathStyleEnabled>

 <publicRepository>false</publicRepository>

 </configuration>

 </server>

 <server>

 <id>straker-aem-connector-release</id>

 <username>AAAAAAAA</username> <!-- Straker given AWS API key -->

 <password>BBBBBBB</password> <!-- Straker given AWS API secret -->

 <configuration>

 <endpoint>https://s3.eu-de.cloud-object-storage.appdomain.cloud</endpoint>

 <region>eu-de</region>

 <pathStyleEnabled>true</pathStyleEnabled>

 <publicRepository>false</publicRepository>

 </configuration>

 </server>

 </servers>

</settings>

3. In the reactor POM (the pom.xml at the root of the directory), add the following lines just before the closing tag (or add extension into existing <extensions> tag):

        <extensions>

            <extension>

                <groupId>com.github.ehsaniara</groupId>

                <artifactId>maven-repository-aws-s3</artifactId>

                <version>1.2.11</version>

            </extension>

        </extensions>

4. In the same POM, add the following repository inside any profile that is activated by default (it can be added in the adobe-public profile):

<repository>

<id>straker-aem-connector-release</id>

<name>Straker S3 Repository - Release</name>

<url>s3://straker-aem-connector/release</url>

<releases>

<enabled>true</enabled>

<updatePolicy>never</updatePolicy>

</releases>

<snapshots>

<enabled>false</enabled>

</snapshots>

</repository>

<repository>

<id>straker-aem-connector-snapshots</id>

<name>Straker S3 Repository - Snapshots</name>

<url>s3://straker-aem-connector/snapshots</url>

<releases>

<enabled>true</enabled>

<updatePolicy>never</updatePolicy>

</releases>

<snapshots>

<enabled>true</enabled>

</snapshots>

</repository>

5. In the all POM (all/pom.xml), add the following segment inside the dependencies (substituting the correct {straker-version-number}):

<dependency>

<groupId>com.adobe.granite.translation.connector</groupId>

<artifactId>straker-connector.ui.apps</artifactId>

<type>zip</type>

     <version>1.0.1-SNAPSHOT</version>

</dependency>

6. Inside the same pom.xml (all/pom.xml), add the following snippet inside the <embedded>fort the filevault-maven-package-plugin artefact:

<embedded>

<groupId>com.adobe.granite.translation.connector</groupId>

<artifactId>straker-connector.ui.apps</artifactId>

<type>zip</type>

<target>/apps/straker-connector/application/install</target>

</embedded>

7. Commit all the changes to the branch and push the changes

8. The build for AEM as a Cloud Service can now be done.