Connecting to the WebDav folder to customize Heritage Process Portal (deprecated)

You can use web-based Distributed Authoring and Versioning (WebDAV) to make and deploy customized login pages and banners to Heritage Process Portal. WebDAV provides a network protocol for creating interoperable, collaborative applications.

Before you begin

Various third-party clients are available that support the WebDAV protocol. Ensure that you have a recommended WebDAV client installed; other clients might not work in your environment. For more information about the recommended clients and the versions that are supported, see the detailed system requirements for your IBM® Business Process Manager configuration. In the linked to page, select your IBM product, version, and operating system. In the generated page, select Prerequisites and then search for WebDAV Client to see the list of supported clients.

Tip: If customizing Heritage Process Portal with WebDAV does not work, you might need to adjust the following security configuration settings:
  • In the administrative console, open the Global security page by clicking Security > Global security.
  • Expand Web and SIP security and click General settings.
  • Make sure that Default to basic authentication is selected. Then click OK and save the configuration.
  • Restart the server to apply changes.

About this task

Because WebDAV works over HTTP, you get all the benefits of HTTP that FTP cannot provide, such as strong authentication, encryption, proxy support, and caching.

By default, IBM BPM blocks HTTP requests with methods other than GET, PUT, POST, DELETE, HEAD, and OPTIONS. A WebDAV connection also uses the methods PROPFIND, PROPPATCH, MKCOL, COPY, MOVE, LOCK, and UNLOCK. These methods need to be white listed as described for the ProcessServer.AllowedHttpMethods property in the topic Security-hardening properties. It is recommended that you enable these particular HTTP methods only temporarily while modifying the theme.

Procedure

Regardless of the WebDav client that you use, ensure that you configure the client to use the HTTP/SSL protocol. In addition, include the following information in the configuration settings.