Serving HTTP OPTIONS requests to the server context root by WebDAV clients

Some WebDAV clients send an HTTP OPTIONS request to the server context root ( / ) to check whether the server supports WebDAV. To support these clients, the portal provides a web application called wp.webdav.options.war that you can enable. This application responds to such requests with a confirmation that the portal supports WebDAV.

About this task

To enable this WAR file, adapt the application.xml files of the deployed Enterprise Application (EAR), wps.earnamed WebDAV for WebSphere Portal, so that wp.webdav.options.war is mapped to the context root ( / ). Proceed as follows:

Procedure

Export the EAR, wps.earWebDAV for WebSphere Portal, through the WebSphere® Integrated Solutions Console.
Open a command prompt. Under z/OS®, open a UNIX System Services (USS) command prompt.
Run the following command to expand the EAR:
- ./EARExpander.sh|bat -ear directory/WebDAV_for_HCL Portal and HCL Web Content Manager.ear -operationDir directory webdav_expanded -operation expand
Locate the file application.xml in the expanded EAR file directory.

Edit the file application.xml of the exported EAR, and uncomment or add the following section:

<module>
                                                  <web>
                                                  <web-uri>wp.webdav.options.war</web-uri>
                                                  <context-root>/</context-root>
                                                  </web>
                                                  </module>

Run the following command to collapse the EAR:

./EARExpander.sh|bat   -ear directory/wps.ear 
                                                            -operationDir directory/wps_expanded 
                                                            -operation collapse

Update the enterprise application with these changes by using the WebSphere Integrated Solutions Console.
Save your changes.
Restart the portal for your changes to take effect.

What to do next

Note: Depending on how your web server is set up, this change might cause all requests to be routed to the web server plug-in. In this case refer to your web server documentation for information about how to route only OPTIONS requests to the plug-in.