Configuring WEM to Use a Shared Datastore

If you use the “shared nothing” deployment model, each instance of the WEM content repository has it’s own set of data that is duplicated across all instances.

The data storage is divided into three sections, Workspace Store, Journal and Data Store. The Data Store is used to hold large binary files.

This post will discuss how to configure the WEM instances to share a single data store among multiple instances. It should be noted that these steps were tested using the ADEP Solutions Quickstart.

Option 1 – Using the default data store location of one of the WEM instances

1) Install the first instance of WEM (for reference purposes, we’ll call it Publish1)

NOTE: Once complete the data store for Publish1 can be found at: drive:/crx-quickstart/repository/repository/datastore

You can utilize this data store as the shared data store. To do so…

2) Install a second WEM instance (for reference purposes, we’ll call it Publish2)

3) Stop the instance

4) Browse to: drive:/crx-quickstart/repository/repository.xml

5) Open repository.xml in an editor

6) Comment out or delete the line…

 

 

7) Add the following in it’s place… set the “path” value specific to your environment

 

8) Restart the second instance (Publish2)

The datastore is now shared between the two instances

Option 2 – Moving the default data store location of one of the WEM instances

1) Install the first instance of WEM (for reference purposes, we’ll call it Publish1)

2) Stop the Publish1 instance

3) Browse to the datastore folder and copy\move it to your desired location

NOTE: Once you confirm that your changes work, you can delete the original datastore folder to free up disk space

4) Browse to: drive:/crx-quickstart/repository/repository.xml

5) Open repository.xml in an editor

6) Edit it as documented in Option 1

7) Install a second WEM instance (for reference purposes, we’ll call it Publish2)

8) Stop the instance

9) Repeat the steps to modify the repository.xml file to point it to the shared datastore

10) Restart the second instance

Option 3 – Modify the quickstart jar file to configure a custom data store location for multiple instances

This method involved modifying the quickstart jar file prior to installing it.

1) Create the folder that will be your datastore in your desired location

2) Open the quickstart jar file using WinZip

3) Navigate to etc\webapps

4) You will see a file named crx-explorer_crx.war in the webapps folder

 

 

 

 

 

 

 

 

 

5)  Double click the crx-explorer_crx.war file to open it (in WinZip)

6)  Navigate to the WEB-INF folder

 

7)  Open repository-template.xml in an editor

8)  Comment out or delete the line…

9) Add the following in it’s place… set the “path” value specific to your environment

NOTE:  If you are using the ADEP Solutions Quickstart with integration to  ADEP Document Services (fka: LiveCycle) via the “–ds” quickstart naming convention, then you must edit the repository-lc-template.xml file with the changes outlined above.

10)  Save the changes to the xml file

11)  Save the jar file and retain the changes

Now you can install the Solutions quickstart and the datastore will be created in the location you specified in the repository-template.xml or repository-lc-template.xml file.

As the shared datastore location is set in the jar file, all subsequent instances that are installed will utilize the shared datastore.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)
This entry was posted in ADEP, Experience Services and tagged , , , . Bookmark the permalink.

One Response to Configuring WEM to Use a Shared Datastore

  1. Davide says:

    Ok, but as far as I remember in this way you’re sharing a datastore but you’re not clustering the publish instances.

    What will happen to the repository and journal when from the author you’ll activate something on each publish?

    Isn’t the clustering a mandatory requirements to use shared data store?