PE-PE HTTPS for workflow transfer and configuration changes

Communication among Process Engine instances for transferring workflow or changing isolated region configuration is changed default to HTTPS instead of HTTP.

For traditional deployments by using WebSphere or WebLogic, which requires the application server to be configured to allow SSL communications. If this change is not acceptable, you can use a JVM option
```
-Dfilenet.pe.server.interserver.usehttps=false
```
to change the communication to HTTP, for example in a development system. For production systems it remains a best practice to use SSL.
Also, the axis2.xml file, which is used by the FileNet Process Engine services that are deployed from the PewsAxis2.war in the FileNetEngine application ear, was modified to remove the port number and change the name of the transportReceiver to "https". Use of the HTTPS interface that is preferred by most customers and removal of an explicit port yields a more flexible configuration. It is possible for customers to manually edit their installed axis2.xml file after deployment. If that happened, the file might need to be modified again after the software upgrade is applied which lays down a new axis2.xml file. As a part of applying this interim fix:
1. Backup the existing axis2.xml file. (See Server installation instructions)
2. Review the new file to determine it meets the requirements of your environment.
3. After deployment of the upgraded software, apply any modifications that might be needed in the new axis2.xml file.
For more information about troubleshooting and modifying the axis2.xml file, see the troubleshoot topic ProcessEngineWS request failures - javax.servlet.ServletException: https is forbidden.
For containerized deployments, the configuration of the PE-PE communication and axis2.xml file is under the control of the Operator.
The new JVM option must not be applied.

The axis2.xml file cannot be modified.