Configure LCA development

Learn how to configure the tools, credentials, and connectivity required for LCA development.

Configure the tools, cloud credentials, and Reltio-to-cloud connectivity required to build, deploy, and register Life Cycle Actions (LCAs) with the integrated development experience.

You need a connected Reltio tenant or Git repository to ask the AI agent questions or generate LCA code. Maven credentials, environment variables, and Reltio-to-cloud connectivity are required to build, deploy, and register an LCA.

Prerequisites

Before you begin, confirm the following requirements:

You have the integrated development experience installed in Cursor or VS Code.
You have access to a Reltio tenant or a Git repository that contains BusinessConfig.json or L3.reltio.json.
You have Java and Maven installed on your computer.
You have deployment access to the target AWS, Google Cloud, or Azure environment.
You have the command-line tool for your target cloud installed: The AWS CLI for AWS Lambda, the Google Cloud CLI (gcloud) for Google Cloud Functions or the Azure CLI (az) for Azure Functions.
You have access to Reltio Console to configure Reltio-to-cloud connectivity.

To configure LCA development

Connect a business configuration source.
Connect to one source at a time:
- Connect to a Reltio tenant and retrieve its business configuration.
- Connect to a Git repository that contains BusinessConfig.json or L3.reltio.json.
Obtain read-only credentials for the Reltio Maven repository.
Request the credentials from Reltio Support. These credentials provide build-time access to the Reltio libraries used by generated LCA projects.
Configure Maven access to the Reltio repository.
Locate your Maven settings.xml file:
Operating system File location
Windows C:\Users\<your-username>\.m2\settings.xml
macOS or Linux ~/.m2/settings.xml
If the .m2 folder or settings.xml file does not exist, create it. For a new settings.xml file, add the following content and replace the username and password placeholders with your Reltio Maven credentials:
```
<settings>
  <servers>
    <server>
      <id>reltio-libs-public</id>
      <username>YOUR_RELTIO_MAVEN_USERNAME</username>
      <password>YOUR_RELTIO_MAVEN_PASSWORD</password>
    </server>
  </servers>
</settings>
```
If the file already contains a <servers> element, add only the <server> entry inside it. Do not create a second <servers> element.
The generated pom.xml references https://repo-dev.reltio.com/content/repositories/public. The repository requires authentication and is not intended for direct browser access.
Save settings.xml.
Maven uses the reltio-libs-public server ID to match your credentials with the repository in the generated project.

Operating system	File location
Windows	`C:\Users\<your-username>\.m2\settings.xml`
macOS or Linux	`~/.m2/settings.xml`

Configure Reltio-to-cloud connectivity for the target cloud environment.

Complete the connectivity procedure for your target environment:


Cloud environment	Connectivity procedure
AWS Lambda	Set up an AWS connection for LCAs.
Google Cloud Functions	Configure Google Cloud identity and access management.
Azure Functions	Configure Microsoft Entra ID authentication. For an external identity provider, configure OAuth 2.0 client credentials.

This configuration authorizes Reltio to invoke the deployed function. Deployment credentials do not replace Reltio-to-cloud connectivity.

Collect the environment variables required for deployment.

Gather the values for the following environment variables for your target environment. After the AI agent generates the LCA project and its .env.example file, use that file as a template to prepare your local .env file.

Cloud environment	Environment variables
AWS Lambda	`AWS_REGION` and `AWS_PROFILE`. As an alternative to a profile, use `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`. Temporary credentials also require `AWS_SESSION_TOKEN`.
Google Cloud Functions	`GOOGLE_CLOUD_PROJECT` and `GOOGLE_CLOUD_REGION`.
Azure Functions	`AZURE_FUNCTIONAPP_NAME` and `AZURE_RESOURCE_GROUP`.

Important:

Do not enter credential values in prompts to the AI agent or commit them to source control. Add the values to the local .env file before deployment.

Result

Your business configuration source is connected, Maven is configured to access the required Reltio libraries, and Reltio-to-cloud connectivity is configured. You also have the environment variable values needed to prepare the generated project for deployment.

Verification steps

To confirm the LCA development environment is configured, perform the following steps:

In the business configuration tree of the Reltio IDE extension view, confirm that the tree lists the entity and relation types from the connected tenant or Git repository.
In a terminal, run mvn -v and confirm it reports both a Maven version and a Java version.
In a terminal, run aws --version for AWS Lambda, gcloud --version for Google Cloud Functions, or az --version for Azure Functions, and confirm it reports a version.
Open the settings.xml file in your .m2 folder and confirm it contains one reltio-libs-public server entry with your Reltio Maven credentials.
In Reltio Console, confirm the connection for your target cloud environment is configured for the tenant.
Confirm you have a value for each environment variable listed for your target cloud environment.

Unify and manage your data

Configure LCA development

Footer