Configure the JAX-RPC web services client bindings in the ibm-webservicesclient-bnd.xmi deployment descriptor
We can configure the ibm-webservicesclient-bnd.xmi deployment descriptor file with assembly tools.
We can configure deployment descriptors with assembly tools provided with the application server.
Configure the assembly tool before we can use it. Read about configuring the assembly tool in the Rational Application Developer documentation.
Now that we have assembled the client module, complete this step to configure the ibm-webservicesclient-bnd.xmi deployment descriptor. Deployment descriptors are required so that so that WebSphere Application Server can process the incoming web services requests.
Configure the ibm-webservicesclient-bnd.xmi deployment descriptor file with the following steps provided:
Tasks
- Start an assembly tool. Read about starting the assembly tool in the Rational Application Developer documentation.
- Switch to the Java EE Perspective.
- Click Window > Open Perspective > Other > Java EE.
- Open the Project Explorer.
- Click Window > Show View > Other > Project Explorer.
- Locate the deployment descriptor file for the module. Hint: Deployment Descriptor: <module>
- Double-click the deployment descriptor file to open the Deployment Descriptor editor.
- Select the WS Binding tab in the editor window to open the Web Services Client Bindings editor.
- Verify the serviceRefLink element settings.
- Open the Web Services Client Bindings editor.
- Click the Services References tab.
- Click Add.
- Select the service references defined in the client deployment descriptor file from the list.
- Verify the deployedWSDLFile element settings.
- Open the Web Services Client Bindings editor.
- Select the service reference.
- Expand the Service Reference Details section.
- Click Browse located to the side of the Deployed WSDL file field.
- Select the new Web Services Description Language (WSDL) file.
- Click OK.
We can also change the deployedWSDLFile element of a deployed web service using the administrative console. Click Enterprise Applications > application > Web module or EJB module > module > Web services client bindings.
- Verify the defaultMappings element settings.
- Open the Web services client bindings editor.
- Click Default mappings.
- Click Add.
- Edit the entries in the newly added row to establish a mapping between a portType and a port in the WSDL file. Only one entry is supported for each portType.
- Click OK.
We can also change the defaultMappings element of a deployed web service using the administrative console. Click Enterprise Applications > application > Web module or EJB module > module > Web services client bindings.
- Access the web services client Port bindings editor through the Port qualified name binding details section.
- Verify the syncTimeout element settings.
- Create a Port qualified name bindings for the port.
- Open the Web services client bindings editor.
- Confirm that a service reference is selected in either the Component-scoped references or the Service references section.
- Expand the Port qualified name binding section.
- Click Add. The Add port qualified name binding dialog opens.
- Type the namespace of the WSDL file port we want to configure, in the Port namespace link field.
- Type the local_name of the WSDL file port we want to configure in the Port local name link field. The name displayed in the Port qualified name binding list is the local name of the WSDL file port.
- Click OK.
- Configure the syncTimeout property by locating the Synchronization timeout field and enter the desired value. The default is 300 seconds.
- Verify the basicAuth element settings.
- Locate the HTTP basic authentication field in the Port qualified name binding details section.
- Type the desired value in the User ID and Password fields.
- Click OK.
- Verify the sslConfig element settings.
- Locate the SSL configuration field in the Port qualified name binding details section.
- Type the desired value in the Name field.
- Click OK.
- After editing the properties, type ctrl-s on your keyboard to save the changes.
We have configured the ibm-webservicesclient-bnd.xmi deployment descriptor. If we have configured all of the client deployment descriptors, test the web services client. If we have not configured all of the client deployment descriptors, complete the configurations and then test the web services client.
Subtopics
- ibm-webservicesclient-bnd.xmi assembly properties for JAX applications
The ibm-webservicesclient-bnd.xmi deployment descriptor file contains information for the web services run time that is WebSphere product-specific. This deployment descriptor file is used with Java API for XML-based web services.
Related:
Development and assembly tools