DataPower

DataPower

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Back to discussions
Expand all | Collapse all

How datapower handles updated files during config updates

  • 1.  How datapower handles updated files during config updates

    Posted Wed December 02, 2020 03:58 PM

    Hello everyone,

    Right now, we have some automated scripts that deploy MPGs/WSPs etc through a SOMA call (import-config). There have been a few instances, that when the proxy, primarily a WSP, was deployed, we have had to do a WSDL Refresh through the following page:

    BoxAddress:9090/status/WSWSDLStatusSimpleIndex

    Or with a SOMA call:

    <dp:do-action> <RefreshWSDL> <WSGateway>###WSP_NAME###</WSGateway> <WSDL>###WSDL_PATH###</WSDL> </RefreshWSDL> </dp:do-action>

    We are wanting to automate this refresh.

    So my questions are something like:

    When the configuration of a proxy is updated through a SOMA call, do all the files get auto-refreshed, including the WSDLs configured to a WSP?

    If we upload just a file through a SOMA call, does the proxy automatically detect this and pull the new version?



    #DataPower
    #Support
    #SupportMigration


  • 2.  RE: How datapower handles updated files during config updates

    Posted Fri December 04, 2020 07:43 AM

    Hi,

    WSP is a bit tricky. We automated the deploy using a chain of SOMA requests. For example set-file+refreshWSDL. When you import a WSP through do-import, it should refresh the WSDLs and XSDs related. Of course, it depends what do you have inside the package that you are importing because what you see as an WSP is actually the WSP configuration and a bunch of policies and rewrite rules. If you just export and import a WSP without dependencies then I'll bet that the interface definitions won't get updated.

    --HP



    #DataPower
    #Support
    #SupportMigration


Related Content