Regenerating integration libraries and WSDL

You must regenerate the Java API libraries and SOAP WSDL after you make certain changes to the product configuration. Regenerate these files in the following situations.

  • After you install a new PolicyCenter release.
  • After you make changes to the PolicyCenter data model, such as data model extensions, typelists, field validators, and abstract data types.

As you work on both configuration and integration tasks, you may need to regenerate the Java API libraries and SOAP WSDL frequently. However, if you make significant configuration changes and then work on integration at a later stage, wait until you need the APIs updated before regenerating PolicyCenter files.

Regenerating the Java API libraries

For Java development, generate the Java entity libraries with the following command.

gwb genJavaApi

As part of its normal behavior, the script displays some warnings and errors. Note that the Java API libraries are regenerated, but the command does not regenerate the static Java API Reference documentation.

The location for the Java generated libraries is:

PolicyCenter/java-api/lib

WS-I web service regeneration of WSDL for local GUnit tests

For web service development, you can write unit tests that call web services on the same computer. Generate WSDL for testing only using the following command.

gwb genWsiLocal

As part of its normal behavior, the script displays some warnings and errors.

The location for WS-I web service WSDL that you can use for writing test classes is:

PolicyCenter/modules/configuration/gsrc/wsi/local/