ALfresco endpoints modification safe?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-12-2009 07:43 AM
Hi!
I have read that people who tried to modify all endpoints fro Alfresco ended up with some problems.
My situaltion is like that - I have two hosts on Tomcat server localhost:8080 (not localhost:8080/alfresco !) that serves Alfresco and share:8080 with Share application.
I did it because I was unable to map this into Apache HTTPD server in this way:
mydomain.com -> localhost:8080/alfresco (the mod_JK connctor does not work this way or I don't know how to configure it)
But this works (if alfresco is the ROOT application):
mydomain.com -> localhost:8080
That is very nice and clean solution, but ALfresco has many (too many) endpoints:
Including the really problematic ones like: http://localhost:8080${url.serviceContext}${uri}
My question is - should I modify all endpoints and hope for this setup not to fall apart, or should I search for other solution when I will still have localhost:8080/alfresco available (but in this case I don't know how to make it availavle under mydomain.com instead of mydomain.com/alfresco
Thanks,
Maciej
I have read that people who tried to modify all endpoints fro Alfresco ended up with some problems.
My situaltion is like that - I have two hosts on Tomcat server localhost:8080 (not localhost:8080/alfresco !) that serves Alfresco and share:8080 with Share application.
I did it because I was unable to map this into Apache HTTPD server in this way:
mydomain.com -> localhost:8080/alfresco (the mod_JK connctor does not work this way or I don't know how to configure it)
But this works (if alfresco is the ROOT application):
mydomain.com -> localhost:8080
That is very nice and clean solution, but ALfresco has many (too many) endpoints:
WEB-INF/classes/alfresco/webscripts/org/alfresco/indexall.get.mediawiki.ftl: [http://localhost:8080${url.serviceContext}${uri} ${desc.method} ${url.serviceContext}${uri}]WEB-INF/classes/alfresco/subsystems/imap/default/imap-server.properties:#imap.server.web.application.context.url=http://localhost:8080/alfrescoWEB-INF/classes/alfresco/webscript-framework-config-test.xml: <endpoint-url>http://localhost:8080/alfresco/s</endpoint-url>WEB-INF/classes/alfresco/templates/webscripts/org/alfresco/repository/repository.get.html.ftl: <tr><td>Service URI: <input name="url" size="50" value="http://localhost:8080/alfresco/service/api/cmis"></td></tr>WEB-INF/classes/alfresco/webscript-framework-config.xml: <endpoint-url>http://localhost:8080/alfresco/s</endpoint-url>WEB-INF/classes/alfresco/webscript-framework-config.xml: <endpoint-url>http://localhost:8080/alfresco/s</endpoint-url>WEB-INF/classes/alfresco/webscript-framework-config.xml: <endpoint-url>http://localhost:8080/alfresco/s</endpoint-url>WEB-INF/classes/alfresco/webscript-framework-config.xml: <endpoint-url>http://localhost:8080/alfresco/s</endpoint-url>WEB-INF/classes/alfresco/webscript-framework-config.xml: <endpoint-url>http://localhost:8080/alfresco/php</endpoint-url> wsdl/authoring-service.wsdl: <wsdlsoap:address location="http://localhost:8080/alfresco/api/AuthoringService'/>wsdl/access-control-service.wsdl: <wsdlsoap:address location="http://localhost:8080/alfresco/api/AccessControlService'/>wsdl/dictionary-service.wsdl: <wsdlsoap:address location="http://localhost:8080/alfresco/api/DictionaryService'/>wsdl/action-service.wsdl: <wsdlsoap:address location="http://localhost:8080/alfresco/api/ActionService'/>wsdl/repository-service.wsdl: <wsdlsoap:address location="http://localhost:8080/alfresco/api/RepositoryService'/>wsdl/authentication-service.wsdl: <wsdlsoap:address location="http://localhost:8080/alfresco/api/AuthenticationService'/>wsdl/administration-service.wsdl: <wsdlsoap:address location="http://localhost:8080/alfresco/api/AdministrationService'/>wsdl/content-service.wsdl: <wsdlsoap:address location="http://localhost:8080/alfresco/api/ContentService'/>wsdl/classification-service.wsdl: <wsdlsoap:address location="http://localhost:8080/alfresco/api/ClassificationService'/>
Including the really problematic ones like: http://localhost:8080${url.serviceContext}${uri}
My question is - should I modify all endpoints and hope for this setup not to fall apart, or should I search for other solution when I will still have localhost:8080/alfresco available (but in this case I don't know how to make it availavle under mydomain.com instead of mydomain.com/alfresco
Thanks,
Maciej
Labels:
- Labels:
-
Archive
2 REPLIES 2

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-12-2009 08:17 AM
I'm not quite sure this is what you are looking for, but I presented an Apache configuration in this thread, that might be of use:
http://forums.alfresco.com/en/viewtopic.php?f=9&t=22176
Combining mod_jk and mod_rewrite, it allows users to access Alfresco and Share on two different domains, without needing to add the /alfresco and /share respectively (it will appended by Apache).
It works this way:
1. The user enters http://www.myalfrescodomain.com in the browser
2. Apache checks if there's a /alfresco in the URL and since there's not, that's appended
3. Apache receives the new URL (myalfrescodomain.com/alfresco), this time it passes the check
4. Apache forwards the request to Tomcat with mod_jk.
I don't know if that solves your problem?
http://forums.alfresco.com/en/viewtopic.php?f=9&t=22176
Combining mod_jk and mod_rewrite, it allows users to access Alfresco and Share on two different domains, without needing to add the /alfresco and /share respectively (it will appended by Apache).
It works this way:
1. The user enters http://www.myalfrescodomain.com in the browser
2. Apache checks if there's a /alfresco in the URL and since there's not, that's appended
3. Apache receives the new URL (myalfrescodomain.com/alfresco), this time it passes the check
4. Apache forwards the request to Tomcat with mod_jk.
I don't know if that solves your problem?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-12-2009 09:59 AM
hello gronfelt, nice to see you again 
Yes, that is something that I was planning to do, but your previous post made it simpler
It is not as beautiful as I would like it to be (like it is with my Share site) but is works well and I will leave it that way.
The good thing is that I don't have to mess with alfresco endpoints.

Yes, that is something that I was planning to do, but your previous post made it simpler

It is not as beautiful as I would like it to be (like it is with my Share site) but is works well and I will leave it that way.
The good thing is that I don't have to mess with alfresco endpoints.
