5 Replies Latest reply on May 14, 2014 3:06 AM by hchiorean

    configuring modeshape subsystem

    basicmodeshaper

      Hi,

       

      sorry if I'm asking newbie question, but currently I'm lost in configuration.

      I need to store files on some file server that is different from where JBoss server resides.

      This is the config from modeshape instaling on the JBoss 7.2.0

       

              <subsystem xmlns="urn:jboss:domain:modeshape:1.0">

                  <repository name="sample" cache-name="sample" cache-container="modeshape" cluster-name="modeshape-sample-cluster" cluster-stack="tcp">

                      <local-file-index-storage path="modeshape/indexes/sample-${jboss.node.name}"/>

                      <cache-binary-storage data-cache-name="sample-binary-fs" metadata-cache-name="sample-binary-fs-meta" cache-container="modeshape-binary-cache-container"/>

                  </repository>

                  <repository name="artifacts" cache-name="artifacts" cache-container="modeshape" cluster-name="modeshape-artifacts-cluster" cluster-stack="tcp">

                      <workspaces allow-workspace-creation="false">

                          <workspace name="default">

                              <initial-content>

                                  initial-content-default.xml

                              </initial-content>

                          </workspace>

                          <workspace name="other"/>

                          <workspace name="extra"/>

                      </workspaces>

                      <local-file-index-storage path="modeshape/indexes/artifacts-${jboss.node.name}"/>

                      <cache-binary-storage data-cache-name="artifacts-binary-fs" metadata-cache-name="artifacts-binary-fs-meta" cache-container="modeshape-binary-cache-container"/>

                      <sequencers>

                               ......

                      </sequencers>

                      <text-extractors>

                          <text-extractor name="tika-extractor" classname="tika" module="org.modeshape.extractor.tika"/>

                      </text-extractors>

                  </repository>

                  <webapp name="modeshape-rest.war"/>

                  <webapp name="modeshape-webdav.war"/>

                  <webapp name="modeshape-explorer.war"/>

                  <webapp name="modeshape-cmis.war"/>

              </subsystem>

       

      Where can I specify the path to repository on different server?

       

      Thanks

        • 1. Re: configuring modeshape subsystem
          hchiorean

          For the index storage you have the attributes: <local-file-index-storage path="" relative-to=""/>. The relative-to attribute has the default value: jboss.server.data.dir but you change that to be any fully qualified folder.

          The Infinispan file stores also have a similar format:  <file-store path="" relative-to=""/>. So you'll also need to configure the Infinispan caches.

          • 2. Re: configuring modeshape subsystem
            basicmodeshaper

            Thanks,

             

            can you please write example of fully qualified folder on different server I have tried a lot of different ways but no success?

             

            Is it ip-adress/d$/folder1/folder2 , or how?

            • 3. Re: configuring modeshape subsystem
              hchiorean

              Sorry, I misread your original question: AFAIK all the configurations work *on the local machine only*. I'm not aware of being able to store files remotely that way.

              • 4. Re: configuring modeshape subsystem
                basicmodeshaper

                really?

                 

                so what is the point to store files only localy?

                 

                Is there any other way to configure modeshape to store files on different server than jboss local?

                • 5. Re: configuring modeshape subsystem
                  hchiorean

                  I'm not 100% sure I understand what you're trying to do.

                  If you're referring to NFS-style shares, you should be able on any Unix-like system to mount such a remote location which then would be referred like a local one would. The relative-to attribute mentioned from above will work with any path/URL as long as it's valid from a java.io.File perspective.

                  1 of 1 people found this helpful