How to set an absolute path in an OSGi .config file for a directory on a shared network drive
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
- We are attempting to use a Document Library directory "External_Library" on a shared network drive, but cannot determine how to use an absolute path instead of a relative path; during startup, a relative path is being used and the full directory structure is getting created within Liferay Home.
- Our Liferay bundle is hosted in a Windows environment (with the network drive on a server using Ubuntu), and we'd like to use the Advanced File System Store.
Resolution
- When setting an absolute path for a directory, per the Universal Naming Convention, it is necessary to use a double slash at the beginning of the path to specify a path on a separate host/server.
- As such, the process to use an OSGi .config file for the Advanced File System Store configuration (with the appropriate syntax for an absolute path on a shared drive) would be to create a file titled
com.liferay.portal.store.file.system.configuration.AdvancedFileSystemStoreConfiguration.config,
placed within [Liferay_Home]\osgi\configs, with the following content included:
rootDir="//server-name/directory/path/External_Library"
Did this article resolve your issue ?