Skip to main content

Recommendation for K2 BlackPearl Installation in a single box


I have the following situation Installation of BlackPearl in a single Box.

Computer Name : CN123
Windows Domain: contoso.com
Default URL: cn123.contoso.com
Desired URL: k2bpdev.contoso.com


The idea is to have "Workspace", "Designer" and "Runtime" in the server and also integrate with Sharepoint 2013


My first issue here is the ports... once installed

the application put Workspace on port 80.
http://cn123.contoso.com/workspace

Later trying to install "Designer" and "Runtime" put in port 81.
http://cn123.contoso.com:81/designer
http://cn123.contoso.com:81/runtime

Is my understanding that a good install between K2 and Sharepoint is either http or https but not a combination. Since I like to use SSL put an SSL Certificate to return:


https://cn123.contoso.com/workspace

https://k2bpdev.contoso.com/designer
https://k2bpdev.contoso.com/runtime

As you can see is kind of messy and actually the Workflows start returning some weird errors.


My questions here are:

1) Would you recommend to perform all the installation of the components "Workspace","Designer" and "Runtime" using the Same WebApplication to prevent the generation of another port [ My case 81 ] ???

2) If all the components of K2 are in the same website, perhaps setup a single SSL Certificate will be enough to cover all the components, when is time to integrate with Sharepoint 2013 ?

 

You are correct regarding the mismatching of HTTP and HTTPS.  If SharePoint 2013 is using HTTPS then K2 should use it as well.

 

In regards to using the same web site for all K2 components it would not be the recommended approach.  Putting workspace in its own site and SmartForms (Designer and Runtime) in its own site will allow you more flexibility later down the road.  What you could do is add a host header value to each of the K2 sites for the URL you would like to use and specify HTTPS along with the certificate you would like to use.  Once that is done you can run BlackPearl Setup Manager and then SmartForms Setup Manager again in that order.  Once you get to the site details for each manager you can click on the Bindings section and check the box for Use and Default so that it uses your new host header value.

 

For the actual SSL certificate it is recommended to use a wildcard if you have one as it will cover all sub domains for a given domain (i.e. *.contoso.com would cover both K2 sites).  If that is not an option a SAN certificate would work as well as it can cover several domain names.  If you are looking to use one certiifcate for both SharePoint and K2, however, a wildcard is pretty much going to be your only option as that is required for the app model in SharePoint 2013 if you are using https.

 

Please let me know if this helps.

 


Thanks,

 

Jimmy


Reply