Preparing the application development setup
To establish WS-AT in the participating applications, you need to attach the WS-Transaction application policy set to both the web service provider and web service client applications. Policy sets simplify the configuration of policies as enforced by the quality of service. The WS-Transaction policy set enables WS-AT when it is attached to the applications. For more information, see the Information Center topic, Web services policy sets.
The WS-Transaction policy set is provided by default. The first step before developing the applications is to get a copy of the policy set exported from the application server. We will use this policy set copy to attach it to the applications while developing the applications, and after deployment, to the respective application servers.
In one of the applications servers used in the scenario, perform the following steps to export the WS-Transaction policy set:
- From the administrative console, navigate to Services >
Policy sets > Application policy sets or Services >
Policy sets > System policy sets > Application policy
sets, as shown in Figure 2.
Figure 2. Application policy sets
- From the Application policy sets panel, select and export
WS-Transaction. By default, the WS-Transaction policy
set is not displayed. Use the New… button to add the
WS-Transaction policy set to the default list. See Figure 3.
Figure 3. Adding the WS-Transaction policy set
- Select the WS-Transaction policy set and click the Export… button.
- In the Export policy set archive file page, locate the
policy set archive file and click to download the file as shown in
Figure 4. Export the policy set
- Select File > Import > Web services > WebSphere
Policy Sets (Figure 5) to import the policy set to
WebSphere Integration Developer (hereafter called Integration
Figure 5. Importing policy sets
- Import the archive file to Integration Developer.
- You will need to restart Integration Developer to read the policy set.