Filevault Checkin/Checkout

[AEM_Forum]

Hi all,

I did not understand Filevault Checkin/Checkout purpose.

Checkin/Checkout is used for a source control system as I understand, to prevent multiple concurrent edits to a file.

Filevault is not such a source control system.

How does Checkin/Checkout apply to it?

Appreciate all your responses.

Thanks,

RK.

[arunpatidar]

In Adobe Experience Manager (AEM), FileVault is a versioned data store used for storing content. Check-in and check-out are part of the versioning mechanism in AEM.

It is for JCR content which stored in the node.

[AEM_Forum]

Thanks Arun.

When a specific JCR content is checked out by some user, what is the implication?

No other user could update that specific content?

Just like a classical Checkin/Checkout functionality?

Check-in and check-out are part of the versioning mechanism in AEM behind the doors.

But Checkin/Checkout functionalities are not directly exposed/available to users, correct?

Share a couple of use cases for Filevault Checkin/Checkout please.

Thanks,

RK.

[arunpatidar · Accepted solution]

Hi @AEM_Forum 
Please check 

https://experienceleague.adobe.com/docs/experience-manager-65/content/implementing/developing/devtoo... 

https://experienceleague.adobe.com/docs/experience-manager-65/content/implementing/developing/devtoo...

https://jackrabbit.apache.org/filevault/overview.html 

FileVault is a versioning file system that is often used in the context of Adobe Experience Manager (AEM) for content versioning and management. The concepts of "checkin" and "checkout" are used to manage changes in the content repository. Below is an explanation with examples using the provided links for reference.

1. Checkin:

   • Definition: The process of committing changes made to a file or subtree back into the repository. It essentially finalizes the changes and makes them available to other users.
   • Example using vlttool: When working with the vlttool in AEM, you can perform a checkin using the following command:
     bash

     vlt --credentials admin:admin checkout http://localhost:4502/crx/server -o myLocalWorkingCopy

2. Checkout:

   • Definition: The process of obtaining a working copy of a file or subtree from the repository, allowing a user to make changes locally. The file or subtree is locked for editing until it is checked back in.
   • Example using vlttool: To perform a checkout using vlttool in AEM, you might use a command like:
     bash

     vlt --credentials admin:admin checkin myLocalWorkingCopy http://localhost:4502/crx/server
     This command checks in the changes made in the local working copy back to the repository.

3. Checking Out a Subtree (Jackrabbit FileVault):

   • Reference Link: Jackrabbit FileVault Overview
   • Explanation: FileVault, being the underlying technology in AEM for content versioning, follows similar principles. When checking out a subtree, it means obtaining a local working copy of a specific directory and its contents for modification.
   • Example: In Jackrabbit FileVault, the process might involve using specific APIs or commands to check out a subtree. The exact implementation details would depend on the programming language and tools being used.

In summary, "checkin" and "checkout" are fundamental concepts in version control systems like FileVault. They enable users to manage changes, collaborate effectively, and maintain a history of revisions in a content repository. The examples provided illustrate how these operations can be performed using the vlttool in the context of AEM. The Jackrabbit FileVault documentation provides a more in-depth understanding of the underlying technology.

[AEM_Forum]

Thanks Arun.

When a specific JCR content is checked out by some user no other user could update that specific content?

Thanks,

RK.

[arunpatidar]

Hi @AEM_Forum 
Others can update the content as well but you might see the conflict, similar to git.