Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-37245

Add ability to setup separate documents library reporsitory for each portal instance

    Details

      Description

      Use case:
      We have 2 departments and we have setup separate Liferay instances, one for each department. We would like to setup first department to store documents and media in Amazon S3 storage and 2nd instance to store documents and media locally in File system.

      As of now this does not seem to be supported as when we set more Liferay portal instances and set property file per instance (such as portal-site1.properties, portal-site2.properties and portal-ext.properties), instance property files are loaded but some properties (such as for document library) defined in those instance property files are not taken into account.

      Steps to reproduce:
      1) Set up clean Liferay Portal with default file repository
      2) Add another portal instance via Control Panel / Portal Instances.
      3) Create empty instance properties file and set loading these files via http://www.liferay.com/documentation/liferay-portal/6.1/user-guide/-/ai/properties-override .
      4) Add to one instance properties file (e.g. portal-site1.properties) valid configuration to Amazon S3:
      dl.store.s3.access.key=
      dl.store.s3.secret.key=
      dl.store.s3.bucket.name=
      dl.store.impl=com.liferay.portlet.documentlibrary.store.S3Store
      5) Restart Liferay Portal
      6) Upload document to first instance and check (via Amazon S3 management console) that files are loaded to Amazon S3 storage.

      It seems that Document Library connection to S3 set in instance configuration file (e.g. portal-site1.properties) are not taken into account and Liferay uses default file repository.

      In other situation, instance property file is loaded and partly handled - reported in related issue: https://issues.liferay.com/browse/LPS-37226 .

      It is also not clear from documentation how properties defined in portal instance property files are being handled. When they are taken into account and when not.

      In application log we can see loading property files in following order:
      Loading file: .../webapps/ROOT/WEB-INF/classes/portal-site1.properties for

      {companyId=10900, webId=site1}
      Loading file: .../webapps/ROOT/WEB-INF/classes/portal-ext.properties for {companyId=10900, webId=site1}

      ...
      Loading file: .../webapps/ROOT/WEB-INF/classes/portal-site2.properties for

      {companyId=10613, webId=site2}
      Loading file: .../webapps/ROOT/WEB-INF/classes/portal-ext.properties for {companyId=10613, webId=site2}

        Attachments

          Activity

            People

            • Assignee:
              support-lep@liferay.com SE Support
              Reporter:
              jan.profiq Jan Hájovský (Inactive)
            • Votes:
              3 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: