Update an application to the TeamForge 17.8 API

To use any of the new API calls introduced in TeamForge 17.8, you must update your existing applications to use the 17.8 API.

What's new in TeamForge 17.8

Click the links in the following table and refer to the Change History section to know the new and changed methods in TeamForge 17.8.
TeamForge service Changed in 17.8? Link to change history
CollabNet service No Javadoc for the CollabNet service
DiscussionApp service No Javadoc for the DiscussionApp service
DocumentApp service No Javadoc for the DocumentApp service
FileStorageApp and SimpleFileStorageApp services No Javadoc for the FileStorageApp and SimpleFileStorageApp services
FrsApp service No Javadoc for the FrsApp service
IntegrationDataApp service No Javadoc for the IntegrationDataApp service
MonitoringApp service No Javadoc for the MonitoringApp service
NewsApp service No Javadoc for the NewsApp service
PageApp service No Javadoc for the PageApp service
PlanningApp service No Javadoc for the PlanningApp service
PluggableApp service No Javadoc for the PluggableApp service
RbacApp service Yes Javadoc for the RbacApp service
ScmApp service No Javadoc for the ScmApp service
TaskApp service No Javadoc for the TaskApp service
TeamApp service No Javadoc for the TeamApp service
TrackerApp service Yes Javadoc for the TrackerApp service
WikiApp service No Javadoc for the WikiApp service
CategorizationApp service No Javadoc for the CategorizationApp service
  1. For calls that use the TeamForge-provided Java SDK classes, update all references to the package containing the classes.
    For this TeamForge version... the package is located at...
    6.x/7.x/8.x/16.x com.collabnet.ce.soap60
  2. For calls that access the WSDL directly, point your application to the new WSDL location.
    For this TeamForge version... the WSDL is located at...
    6.x/7.x/8.x/16.x http://<teamforge‐server>/ce‐soap60/services/<service‐name>?wsdl
  3. Update any calls that have been changed in the 17.8 API.