Web services assembly properties

ibm-webservices-bnd.xmi properties

The ibm-webservices-bnd.xmi file is a deployment descriptor for a Web Services-enabled Web module. It contains information for the Web services runtime that is either WebSphere product-specific or was not included in the Web services specification.

You can manually edit these assembly properties or use WebSphere Development Studio Client for iSeries (Version 5.1 or later).

To use the Development Studio client, open the webservices.xml file for your Web service module in the Web Services Editor. The assembly properties are located on the Bindings and Binding Configurations tabs.

Note: Although you open the webservices.xml file for editing, the Web Services Editor stores the values in the ibm-webservices-bnd.xmi file in your module.

The following user-definable assembly properties are supported:

ibm-webservicesclient-bnd.xmi properties

The ibm-webservicesclient-bnd.xmi file contains information for the Web services run time that is WebSphere product-specific. The ibm-webservicesclient-bnd.xmi file is used for Web services clients or Web services that act as clients to another Web service.

You can manually edit these assembly properties or use WebSphere Development Studio Client for iSeries (Version 5.1 or later).

To use the Development Studio client, open the webservicesclient.xml file for your Web service module in the Web Services Client Editor. The assembly properties are located on the Bindings and Port Bindings tabs.

Note: Although you open the webservicesclient.xml file for editing, the Web Services Editor stores the values in the ibm-webservicesclient-bnd.xmi file in your module.

The following user-definable assembly properties are supported:

The values of deployedWSDLFile and the defaultMappings of a deployed Web service can also be changed using the administrative console. Using application management, navigate to the Web module and select Web Services Client Bindings.

Example bindings files

The following examples demonstrate the spelling and position of the various attributes. You cannot cut and paste these examples because they do not contain the required ID attributes. If you add elements to a binding file template generated by the WSDL2Java command, you must confirm that each element has an ID attribute whose value is a unique string. Review the template xmi files generated by the WSDL2Java command for examples of ID strings.

Example ibm-webservices-bnd.xmi file

<com.ibm.etools.webservice.wsbnd:WSBinding xmi:version="2.0"
    xmlns:xmi="http://www.omg.org/XMI" xmlns:com.ibm.etools.webservice.wsbnd=
    "http://www.ibm.com/websphere/appserver/schemas/5.0.2/wsbnd.xmi">
  <wsdescBindings wsDescNameLink="AddressBookService">
    <pcBindings pcNameLink="AddressBook" scope="Application"/>
  </wsdescBindings>
</com.ibm.etools.webservice.wsbnd:WSBinding>

Example ibm-webservicesclient-bnd.xmi file

<com.ibm.etools.webservice.wscbnd:ClientBinding xmi:version="2.0"
    xmlns:xmi="http://www.omg.org/XMI" xmlns:com.ibm.etools.webservice.wscbnd=
    "http://www.ibm.com/websphere/appserver/schemas/5.0.2/wscbnd.xmi">
  <componentScopedRefs componentNameLink="myComponent ref"/>
  <serviceRefs serviceRefLink="myService ref" deployedWSDLFile="META-INF/wsdl/alternate.wsdl">
    <defaultMappings portTypeLocalName="AddressBook"
        portTypeNamespace="http://www.com.ibm" portLocalName="AddressBookPort"
        portNamespace="http://www.com.ibm"/>
      <portQnameBindings portQnameNamespaceLink="http://www.com.ibm"
          portQnameLocalNameLink="AddressBookPort" syncTimeout="99">
        <basicAuth userid="myId" password="myPassword"/>
        <sslConfig name="mynode/DefaultSSLSettings"/>
      </portQnameBindings>
    </serviceRefs>
  </com.ibm.etools.webservice.wscbnd:ClientBinding>