ibm-webservicesclient-bnd.xmi
ibm-webservicesclient-bnd.xmi contains WAS-specific information on the Web services runtime and contains the following assembly properties:
- componentNameLink
Attribute of componentScopedRefs element. Specifies link to corresponding <component-scoped-refs> element in webservicesclient.xml. Used only when the Web service client is an EJB.
- serviceRefLink
Attribute of the serviceRefs element that specifies the link to the <service-ref-name> in the webservicesclient.xml file.
You can edit this property in the Assembly Toolkit...
- deployedWSDLFile
Attribute of the serviceRefs element is optional and permits an alternate WSDL file to be used other than that specified in the <wsdl-file> element of webservicesclient.xml file. If this attribute is specified, the alternate WSDL file must be packaged in the same module and must be compatible with the development WSDL file. The deployedWSDLFile property is used to supply a new WSDL file containing a different endpoint URL than the original WSDL file.
- defaultMappings element
Identifies which port should be used for a given portType when none is explicitly selected by the client. This element has the following attributes: portTypeNamespace, portTypeLocalName, portNamespace, portLocalName. These attributes identify which wsdl:port should be used for a wsdl:portType.
- syncTimeout
Attribute of the portQnameBindings element that specifies how long, in seconds, to wait for a response from a synchronous call.
- basicAuth
Element of the portQnameBindings element that can be used to authenticate a service client to the service endpoint, independent of the underlying transport that includes, HTTP, HTTPS, and JMS. Set the user ID and password attributes as needed.
- sslConfig
Element of the portQnameBindings element that specifies the SSL configuration of an HTTPS outbound request. The name attribute is the name of a SSL configuration entry or alias defined in the SSL Configuration Repertoire.
Note that This attribute is only used when the client is running in the WAS.
Example bindings file
The following example 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, 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
<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.c../WAS51/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="node/DefaultSSLSettings"/> </portQnameBindings> </serviceRefs> </com.ibm.etools.webservice.wscbnd:ClientBinding>
See Also
Configuring the ibm-webservicesclient-bnd.xmi deployment descriptor
Assembling Web services applications based on Web Services for J2EE