In step 2, update the values in the alfresco-global.properties file: ntext=xxx If the reverse proxy maps the target server to a different context path, or if you deployed specifically to a different context path, you need to follow the steps in Deploy with a different context path, with the following changes: To specify the properties relevant to your configuration: alfresco.host=localhostįollow this guidance if you want to run Content Service with a reverse proxy.
If you’re using Solr, modify the following files: solr/workspace-SpacesStore/conf/solrcore.properties Update the Solr configuration to specify the new context path: Repack the contents of ROOT.war and deploy it. Unpack ROOT.war and edit the index.jsp file to set the context path:Ĭhange /alfresco to /new-context-path: if(request.getMethod().equals("PROPFIND") || request.getMethod().equals("OPTIONS")) Repack the contents of the _vti_bin application into a _vti_bin.war file and deploy it. Ī space separated list of url-encoded context paths of SharePoint protocol enabled applications (e.g. The example shows the default values in the WEB-INF/web.xml file: Replace the value with /new-context-path/aos to update the context parameter with the new context path. Locate the WEB-INF/web.xml file in the _vti_bin application. Update the context path setting in the _vti_bin application: Update share-config-custom.xml as described in Configuring the Share default port. Update alfresco-global.properties with the name of the context path: ntext=new-context-path.
For other application servers, set the context path in the Admin Console during deployment. The string new-context-path is used to represent the name of the context path that you’re using:ĭeploy the alfresco.war file to a different context path for example, if you’re using Tomcat, rename the alfresco.war file to new-context-path.war and then deploy it. In other words, the context path can’t be the server root.įollow these steps if you want to deploy to a context path that’s not /alfresco. Note: You can’t install at the server root (i.e. If you change this value, you must reflect the change in your application server configuration. The context path is the path that’s used by applications (for example, Alfresco Share, SOLR, SharePoint, and others) to access the repository. There are a number of updates that you need to make if you want to deploy to a context path that isn’t /alfresco.
0 kommentar(er)
