Endpoint WCF Service / SmartObject fails when setting 'HTTPGetEnabled' to False.

  • 16 February 2021
  • 0 replies
  • 15 views

Badge +2
 

Endpoint WCF Service / SmartObject fails when setting 'HTTPGetEnabled' to False.

KB001602

PRODUCT
K2 blackpearl 4.6.8 to 4.6.10
BASED ON
K2 blackpearl 4.6.8
TAGS
K2 Services
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.

 

Issue Description

When disabling a web service from exposing metadata by setting the HTTPGetEnabled configuration setting in the web service web.config file to False; and the Host Server is restarted or the service instance refreshed, an exception is thrown when the SmartObject is executed.

 

 

Recreation Steps

  1. Create an Endpoint WCF Service instance and configure it to point to a web service
  2. Create a SmartObject
  3. Edit the Web Service web.config and change the HTTPGetEnabled property to False
  4. Restart the K2 service
  5. Try executing the SmartObject again. An exception is raised.

 

 

Resolution

As of K2 blackpearl 4.6.8, there is a new Service Key setting available when registering or editing the Service Instance called Store Service Metadata and by default is set to False.

Image

  1. When creating a new service instance or updating an existing one, the HTTPGetEnabled configuration setting for the web service must always be set to True, as K2 needs access to the required service metadata.
  2. Set the Store Service Metadata field to True while creatingupdating the service instance.
  3. Set HTTPGetEnabled configuration setting to False.
  4. Now the Host Server can be restarted and the SmartObject can be successfully executed.

Note that if you need to refresh the service instance to discover changes to the service you will need to perform these same steps again.

 


0 replies

Be the first to reply!

Reply