Does SharePoint Portal Server or Windows SharePoint Services need to be installed on the same server as the K2.net Server in order for K2.net processes to be able to be initiated by SharePoint events or to initiate SharePoint events?
The SP1A intallation guide mentions that in order to install the K2.net 2003 SharePoint Server Web Service, SPS and/or WSS needs to be configured on the current installation server.
+4
Hi Steve,
SharePoint (SPS/WSS) can be installed on the same server the K2 Server, but you will have to make sure that you configure the Managed Paths to ensure that the SPS/WSS ISAPI filter does NOT grab the K2 URLs (Workspace, Web Services etc.) and try to route those requests to the database.
In our environment, we have separate servers for SPS, K2 and Meridio and a common SQL server shared by all the apps. In order to use the SPS K2 components, they need to be installed onto your SPS server - The installer detects the presence of the SPS/WSS files and makes an additional option visible in the "Custom Setup" page.
These options include the Task List Web Part and a Web Service. My post at http://forum.k2workflow.com/viewtopic.php?t=261 has an extract from our build scripts outlining how we installed K2 and the K2/SPS components.
Once these have been installed, you should be able to build K2 processes that can interact with SPS.
One thing to watch out for - SPS initiates K2 processes as the Anonymous user, so you will have to grant this user the Plan/Start privilege using the Service Manager.
Hope this helps.
Regards,
Dave.
SharePoint (SPS/WSS) can be installed on the same server the K2 Server, but you will have to make sure that you configure the Managed Paths to ensure that the SPS/WSS ISAPI filter does NOT grab the K2 URLs (Workspace, Web Services etc.) and try to route those requests to the database.
In our environment, we have separate servers for SPS, K2 and Meridio and a common SQL server shared by all the apps. In order to use the SPS K2 components, they need to be installed onto your SPS server - The installer detects the presence of the SPS/WSS files and makes an additional option visible in the "Custom Setup" page.
These options include the Task List Web Part and a Web Service. My post at http://forum.k2workflow.com/viewtopic.php?t=261 has an extract from our build scripts outlining how we installed K2 and the K2/SPS components.
Once these have been installed, you should be able to build K2 processes that can interact with SPS.
One thing to watch out for - SPS initiates K2 processes as the Anonymous user, so you will have to grant this user the Plan/Start privilege using the Service Manager.
Hope this helps.
Regards,
Dave.
+3
Thanks for the info...what I gather is that it would be preferable to keep the K2.net server and the SharePoint Portal Server separate from each other to reduce conflicts. Is that right?
+6
Yes. Although using the "Exclude" option is often mentioned to run K2 and SPS on the same web site, it is not recommended and (from K2 Support's experience), never seems to work 100% over the long run.
Unless there is a compelling reason to run them both on the same site...don't.
Unless there is a compelling reason to run them both on the same site...don't.
+9
Hi,
You can run K2.net Server and SPS on the same server, however I would recommend that you install K2.net Workspace on a different site as SPS. The security log down that SPS does is only relevant to the site it is installed on and will not have any impact on the other Sites configured on the IIS server.
You can run K2.net Server and SPS on the same server, however I would recommend that you install K2.net Workspace on a different site as SPS. The security log down that SPS does is only relevant to the site it is installed on and will not have any impact on the other Sites configured on the IIS server.
Reply
View our Community Site Map
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.