SharePoint Products TechCenter >
SharePoint Products and Technologies Forums
>
SharePoint - Enterprise Content Management
>
Content Deployment over the internet
Content Deployment over the internet
- Hello all, my question is can we use content deployment feature (jobs,paths) of MOSS for deploying content from a MOSS authoring farm that is located within company intranet to deploy contents to a remote MOSS server (production farm) that is accesible via internet? The remote production server is accessible via the internet and I don't have physical access to it. however I am able to do remote desktop into the server. What are the limitations/restrictions/pre-requisites in this scenario? Please help.
Answers
- Hi,
Content deployment uses a single destination port: The Central Administration port. This mean that you will have to expose Central Admin to Internet.
From the security point of view, it's not a good practice to do that.
But if you really want to do it, the only port you have to open in the firewall is the central administration port.
Hope that help,
Mario
My blog (en français) : http://spcontext.wordpress.com/- Marked As Answer byLu Zou-MSFTMSFT, ModeratorWednesday, October 28, 2009 9:27 AM
- As well as the concern Mario has alluded to, you will likely hit a problem with timeout and contention if you are not on a dedicated point to point connection. You have no guarantee of service levels when publishing over the internet and you would need to think about ensuring SSL was enabled between the services to stop your publishing traffic being intercepted.RegardsJohn Timney
- Marked As Answer byLu Zou-MSFTMSFT, ModeratorWednesday, October 28, 2009 9:27 AM
- Hi,
Here is a link to customize content deployement for a disconnect scenario :
http://msdn.microsoft.com/en-us/library/aa981161.aspx
I think this is what you're looking for.
Regards,
Mario
My blog (en français) : http://spcontext.wordpress.com/- Marked As Answer byLu Zou-MSFTMSFT, ModeratorWednesday, October 28, 2009 9:27 AM
All Replies
- Hi,
Content deployment uses a single destination port: The Central Administration port. This mean that you will have to expose Central Admin to Internet.
From the security point of view, it's not a good practice to do that.
But if you really want to do it, the only port you have to open in the firewall is the central administration port.
Hope that help,
Mario
My blog (en français) : http://spcontext.wordpress.com/- Marked As Answer byLu Zou-MSFTMSFT, ModeratorWednesday, October 28, 2009 9:27 AM
- As well as the concern Mario has alluded to, you will likely hit a problem with timeout and contention if you are not on a dedicated point to point connection. You have no guarantee of service levels when publishing over the internet and you would need to think about ensuring SSL was enabled between the services to stop your publishing traffic being intercepted.RegardsJohn Timney
- Marked As Answer byLu Zou-MSFTMSFT, ModeratorWednesday, October 28, 2009 9:27 AM
- Thanks John and mario for highlighting the limitations and problems. Also I want to know are there any alternatives that we can utilize in this scenario instead of MOSS OOB content deployment. As I mentioned that we have a intranet authoring farm and the production server is a remote server that is accessible via HTTP and FTP. Any custom code/ any API that we can use in this scenario?
- Hi,
Here is a link to customize content deployement for a disconnect scenario :
http://msdn.microsoft.com/en-us/library/aa981161.aspx
I think this is what you're looking for.
Regards,
Mario
My blog (en français) : http://spcontext.wordpress.com/- Marked As Answer byLu Zou-MSFTMSFT, ModeratorWednesday, October 28, 2009 9:27 AM
