Configure web services applications

We can use the wsadmin scripting tool to complete the several tasks for a web services application.

Develop a web services application. To learn more, see the implementing web services applications information.

The WebSphere Application Server wsadmin tool provides the ability to run scripts. We can use wsadmin.sh to manage a WAS installation, as well as configuration, application deployment, and server run-time operations. The WAS only supports the Jacl and Jython scripting languages.

To use wsadmin.sh to configure a web services application, publish a WSDL file, or to configure policy sets:

1. Launch a scripting command. To learn more, see the starting the wsadmin scripting client information.

2. Follow the steps in one of the following topics, depending on what task to complete:

   • Publish WSDL files.

   • Configure web services client deployed WSDL file names.

   • Configure web services client preferred port mappings .

   • Configure web services client port information .

   • Configure the scope of a web services port .

Results

You have configured web services applications with wsadmin.sh.

Subtopics

• Enable WSDM
  Use wsadmin.sh with the AdminConfig object to enable Web Services Distributed Management (WSDM) in the environment. WSDM is an OASIS approved standard that supports managing resources through a standardized web service interface.

• Querying web services
  We can use the Jython or Jacl scripting language to query for web services properties with wsadmin.sh. Use the commands in the WebServicesAdmin group to list all web services, service references and attributes, find attributes of a specific web service, determine the web service endpoint, and determine the operation name of a Web service.

• Configure a web service client deployed WSDL file name
  When a web service application is deployed into WebSphere Application Server, an instance is created for each application or module. The instance contains deployment information for the web module or EJB module, including the client bindings.

• Configure web service client-preferred port mappings
  A client port type can be configured with ports that have different qualities of service. We can use the WebServicesClientBindPreferredPort command-line option to specify which port to use.

• Configure web service client port information
  A web service can have multiple ports. We can view and configure the port attributes for each defined web service port.

• Configure the scope of a web service port
  When a web service application is deployed into WebSphere Application Server, an instance is created for each application or module. The instance contains deployment information for the web module or EJB module, including implementation scope, client bindings and deployment descriptor information. There are three levels of scope that can be set: application, session and request.

• Publish WSDL files
  The WSDL files in each web services-enabled module are published to the file system location specified. We can provide these WSDL files in the development and configuration process of web services clients so that they can invoke the web services.

• Configure application and system policy sets for web services
  Use wsadmin.sh, which supports the Jython and Jacl scripting languages, to configure application or system policy sets for web services. We can manage the policies for the Quality of Service (QoS) by creating policy sets and managing associated policies.

• Configure secure sessions between clients and services
  Use wsadmin.sh, which supports the Jython and Jacl scripting language, to edit trust service configurations. Use the STSManagement command group for the AdminTask object to specify details related to secure sessions between clients and target services.

Related tasks

Task overview: Implement web services applications

Start the wsadmin scripting client

Configure additional HTTP transport properties using wsadmin-line tool