Set up a separate dummy service

The dummy service is a dummy implementation of the CollabNet Connect / link (also known as Integrated Application Framework or IAF) web service the TeamForge connector uses for authentication and authorization.

IAF provides functionality that requires all applications using it to implement a SOAP WebService interface; it also requires that the TeamForge server be able to connect to every integrated application. Since the connector doesn't actually make use of this extra functionality, we ship a dummy service that simply returns static, no-op responses for all web service calls.

Important: For TeamForge 7.0:

If you are using TeamForge connector (CCF) 2.0 - 2.2 to integrate with TeamForge 7.0, there is a built-in dummy service that runs within TeamForge. The CCF Admin needs to update ccf.iafServiceEndpoint in the ccfhomeruntimeconfig.properties file:
```
ccf.iafServiceEndpoint=http://localhost:8080/ce-soap/services/IAFDummyService
```
You do not need to separately install the dummy service.
When you use TeamForge connector 2.2.1 (or later) to integrate with TeamForge 7.0 (or later), you can use the in-built dummy service that runs within TeamForge 7.0. CCF will automatically detect the Integrated Application Framework (IAF) service endpoint for TeamForge 7.0 and use it. You do not need to separately install the dummy service on the TeamForge server. You do not need to add or edit the ccf.iafServiceEndpoint property in ccfhomeruntimeconfig.properties either.

For TeamForge versions 5.4 through 6.2: Normally, this dummy service runs on the same application server as the connector. When the TeamForge server isn't able to connect to the server hosting the connector, it is necessary to deploy a separate dummy service at a location that the TeamForge server can reach. To avoid unnecessary inter-host communication, we recommend you install the dummy service on the same host that runs TeamForge.