Release 10.1A: OpenEdge Application Server:
Administration

> ## WSAMAN update

> Lets you change a Web service’s deployment information (stored in the WSM file) without undeploying and deploying. Updating does not affect the Web service’s `friendlyname`.`props` file. It is useful during development, but not during production.

> #### Syntax

> Operating system | Syntax
> --- | ---
> UNIX Windows |
>     wsaman
>        -name wsainstance-name
>        -wsm wsm-location-on-wsaman-machine
>        { -appname app-friendlyname
>          | -namespace app-targetnamespace }
>        [ -encoding encodingstyle ]
>        -update

> `-name`wsainstance-name``

> The name of the WSA instance the Web service is deployed to.

> `-wsm`wsm-location-on-wsaman-machine``

> The path of the WSM file on the `WSAMAN` machine.

> `-appname `app-friendlyname``

> The friendly name of the Web service.

> `-namespace`app-targetnamespace``

> The target namespace of the Web service.

> `-encoding`encodingstyle``

> An integer indicating the new style/use combination of the WSDL file.

> Use a value from Table B–8, which lists the WSDL style/use combinations supported.

> Table B–8: Setting the SOAP format for update using WSAMAN
> Use this value ... | For this WSDL style/use combination ...
> --- | ---
> 1 | RPC/Encoded
> 2 | RPC/Literal
> 3 | Document/Literal

> #### Notes

> - If the friendly name is different from the AppObject name, you must use the `-appname` option and not the `-namespace` option.

> - Progress Software Corporation recommends that you never use the WSAMAN update function on a production system.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095