Set a Web service client deployed WSDL file name with the wsadmin tool


 

+

Search Tips   |   Advanced Search

 

An instance exists for each deployed Web service which contains deployment information such as the client bindings.

To complete this task, we need to know...

Bindings can define...

The following steps describe how to edit the bindings of deployed Web services..

To configure client bindings with wsadmin...

Use WebServicesClientBindDeployedWsdl to change the endpoint...

  1. Launch a scripting command.

  2. Run...

    $AdminApp edit <app_name> { -WebServicesClientBindDeployedWsdl {{<module_name> <EJB_name> <web_service> <deployed_WSDL_filename>}...}

    The example shows multiple nodules and URL endpoints because we can edit multiple URL fragments. where:

    • app_name is the application name, for example WebServicesSample.ear

    • module_name is the EJB or Web module name, for example AddressBookW2JE.jar

    • EJB_name is the name of the EJB if the module is not a Web module, for example Exchange

    • web_service is the name of the Web service, for example service/StockQuoteService

    • deployed_WSDL_filename identifies the WSDL file, relative to this module, for example,

      META-INF/wsdl/AlternativeStockQuoteFetcher.wsdl

  3. Save the configuration changes with the $AdminConfig save command:

 

Results

Your Web service client bindings are configured.

 

Example

Application, module and WSDL file name as written in...

$AdminApp edit MultiEjbJar {-WebServicesClientBindDeployedWSDL {{ejbclientonly.jar Exchange service/StockQuoteService META-INF/wsdl/AlternateStockQuoteFetcher.wsdl}...}}

 

What to do next

Now we can finish any other configurations, start or restart the application, and verify the expected behavior of the Web service.

 

Related tasks

Web services client bindings
Set Web services client bindings

 

Related

installInteractive, edit, editInteractive, update, and updateInteractive