topic Re: How can I tell if Sharepoint protocol was installed? in Alfresco Archive

How can I tell if Sharepoint protocol was installed?

gsvitak — Tue, 03 Mar 2009 20:43:36 GMT

Hello,I downloaded and installed the full stable linux installer for 3.0 that supposedly included the SharePoint protocol support. In the preview edition, I know there was a ROOT.war that I thought I had to place in the webapps directory. I noticed this is missing on my install. However I do see tha

Re: How can I tell if Sharepoint protocol was installed?

mikeh — Tue, 03 Mar 2009 20:58:18 GMT

Check you can connect to port 7070 on the server.

Please see the PDF linked from this wiki article for details:
http://wiki.alfresco.com/wiki/Alfresco_Labs_3#Microsoft_Office_SharePoint_Protocol_Support

Thanks,
Mike

Re: How can I tell if Sharepoint protocol was installed?

gsvitak — Thu, 05 Mar 2009 04:54:13 GMT

Hello

thanks for the response. I cannot connect to port 7070 and I am internal to my firewall. Any suggestions on how to debug? I do not have CIFS working yet.. do I need this first?

G

Re: How can I tell if Sharepoint protocol was installed?

mikeh — Thu, 05 Mar 2009 08:27:48 GMT

No, you don't need CIFS configured.

Check whether the server is listening on port 7070 using netstat or equivalent and that a machine-local firewall isn't blocking connections.

If it all seems ok, please post the startup log.

Thanks,
Mike

Re: How can I tell if Sharepoint protocol was installed?

gsvitak — Thu, 05 Mar 2009 14:14:07 GMT

Hello,

Thanks for the continued help.

When I did a netstat -a |grep ":7070".. this returned nothing. So it does not appear to be listening on port 7070.

Cannot remember if I said we are using Fedora Core 10…

19:25:28,642 INFO [org.alfresco.config.xml.XMLConfigService$PropertyConfigurer] Loading properties file from class path resource [alfresco/file-servers.properties]
19:25:42,826 INFO [org.alfresco.repo.domain.schema.SchemaBootstrap] Schema managed by database dialect org.hibernate.dialect.MySQLInnoDBDialect.
19:25:43,524 INFO [org.alfresco.repo.domain.schema.SchemaBootstrap] No changes were made to the schema.
19:25:46,386 INFO [org.alfresco.repo.admin.ConfigurationChecker] The Alfresco root data directory ('dir.root') is: /opt/alfresco/alf_data
19:25:46,424 INFO [org.alfresco.repo.admin.patch.PatchExecuter] Checking for patches to apply …
19:25:46,650 INFO [org.alfresco.repo.admin.patch.PatchExecuter] No patches were required.
19:25:46,654 INFO [org.alfresco.repo.module.ModuleServiceImpl] Found 0 module(s).
19:25:52,590 ERROR [org.alfresco.smb.protocol] Failed to get local domain/workgroup name, using default of WORKGROUP
19:25:52,591 ERROR [org.alfresco.smb.protocol] (This may be due to firewall settings or incorrect <broadcast> setting)
19:25:53,168 INFO [org.alfresco.service.descriptor.DescriptorService] Alfresco JVM - v1.6.0_12-b04; maximum heap size 506.313MB
19:25:53,169 INFO [org.alfresco.service.descriptor.DescriptorService] Alfresco started (Labs): Current version 3.0.0 (Stable 1526) schema 1002 - Installed version 3.0.0 (Stable 1526) schema 1002
19:26:13,990 INFO [org.alfresco.web.site.FrameworkHelper] Successfully Initialized Web Framework
19:26:18,040 INFO [org.alfresco.web.scripts.DeclarativeRegistry] Registered 67 Web Scripts (+0 failed), 71 URLs
19:26:18,042 INFO [org.alfresco.web.scripts.AbstractRuntimeContainer] Initialised Presentation Web Script Container (in 1212.9506ms)
19:27:18,604 INFO [org.alfresco.web.scripts.DeclarativeRegistry] Registered 101 Web Scripts (+0 failed), 105 URLs
19:27:18,604 INFO [org.alfresco.web.scripts.AbstractRuntimeContainer] Initialised WebFramework Web Script Container (in 60544.836ms)
19:27:18,690 INFO [org.alfresco.web.site.FrameworkHelper] Successfully Initialized Web Framework
19:35:32,080 INFO [org.alfresco.repo.activities.post.lookup.PostLookup] Update: 1 activity posts
19:36:03,430 INFO [org.alfresco.repo.activities.feed.FeedTaskProcessor] >>> Generated 4 activity feed entries for 1 activity posts
19:57:47,041 INFO [org.alfresco.repo.activities.post.lookup.PostLookup] Update: 2 activity posts
19:58:02,259 INFO [org.alfresco.repo.activities.feed.FeedTaskProcessor] >>> Generated 8 activity feed entries for 2 activity posts
21:23:47,029 INFO [org.alfresco.repo.activities.post.lookup.PostLookup] Update: 1 activity posts
21:24:02,225 INFO [org.alfresco.repo.activities.feed.FeedTaskProcessor] >>> Generated 4 activity feed entries for 1 activity posts

Re: How can I tell if Sharepoint protocol was installed?

mikeh — Thu, 05 Mar 2009 15:15:21 GMT

19:25:46,654 INFO [org.alfresco.repo.module.ModuleServiceImpl] Found 0 module(s).

Doesn't look like the Sharepoint module is installed. Try shutting the server down, then running the "apply_amps" script.

Thanks,
Mike

Re: How can I tell if Sharepoint protocol was installed?

gsvitak — Thu, 05 Mar 2009 17:05:58 GMT

thank you that worked.

Last question… the normal sharepoint protocolo runs over the default web server port.. any plans to support this configuration so the user does not have to remember "7070"?

thanks,
G

Re: How can I tell if Sharepoint protocol was installed?

sravenscroft — Mon, 10 Aug 2009 12:29:50 GMT

I agree - it would really be great if the sharepoint protocol could run on port 80 instead of 7070.

In theory I suppose you could just change the 7070 to 80 and all should be ok:

vti.server.port=80
vti.alfresco.deployment.context=/alfresco
‍‍‍

Except that I have changed my tomcat setup to run on port 80 (instead of 8080).

I wonder if it will be possible to have both run on the same port (80) ???

Re: How can I tell if Sharepoint protocol was installed?

mikeh — Mon, 10 Aug 2009 12:52:38 GMT

I wonder if it will be possible to have both run on the same port (80) ???

No because the SharePoint protocol is quite mad - it expects all sort of FrontPage extension folders to reside off the root (hence the first implementation used a ROOT.war, but this was unpopular).

You might be able to arrange a different hostname and proxy the connection through to the default port instead - you'd probably be better off using an Apache web server instead of trying to get Tomcat to do this however (that's the usual way to enable port 80 by the way).

Thanks,
Mike