+

Search Tips   |   Advanced Search

Configure HTTP outbound transport level security with an assembly tool

We can configure the HTTP outbound transport level security with an assembly tool.

We can configure HTTP outbound transport level security with assembly tools provided with WebSphere Application Server.

This task is one of several ways that we can configure the HTTP outbound transport level security for a web service acting as a client to another web service server. We can also configure the HTTP outbound transport level security with the administrative console or using the Java properties. If we do not configure the HTTP outbound transport level security, the web services runtime defers to the Java EE security runtime in the WebSphere product for an effective SSL configuration. If there is no SSL configuration with the Java EE security runtime in the WebSphere product, the JSSE system properties are used.

If we configure the HTTP outbound transport level security with assembly tool or with the administrative console, the Web Services Security binding information is modified. If we have not yet installed the web services application into WAS, we can configure the HTTP SSL configuration with an assembly tool. This task assumes that we have not deployed the web services application into the WebSphere product.

If we configure the HTTP outbound transport level security using the standard Java properties for JSSE, the properties are configured as system properties. The configuration specified in the binding takes precedence over the Java properties. However, the configurations specified by the Java EE security programming model, or are associated with the Dynamic selection, have a higher precedence.

To learn more, see secure communications.


Tasks

  1. Start an assembly tool. Read about starting the assembly tool in the Rational Application Developer documentation.

  2. If we have not done so already, configure the assembly tool so that it works on Java EE modules. We need to make sure that the Java EE and Web categories are enabled. Read about configuring the assembly tool in the Rational Application Developer documentation.
  3. Migrate the web application archive (WAR) files created with the Assembly Toolkit, Application Assembly Tool (AAT) or a different tool to the Rational Application Developer assembly tool. To migrate files, import your WAR files to the assembly tool. Read about migrating code artifacts to an assembly tool in the Rational Application Developer documentation.

  4. Configure the HTTP outbound transport level security. Read about enabling web service endpoints in the Rational Application Developer documentation.

We have configured the HTTP outbound transport level security for a web service acting as a client to another web service with an assembly tool.


Related:

  • Secure web services
  • Overview of standards and programming models for web services message-level security
  • Secure communications using SSL
  • Development and assembly tools
  • Configure Federal Information Processing Standard Java Secure Socket Extension files
  • Authenticating web services clients using HTTP basic authentication
  • Secure web services applications at the transport level
  • HTTP SSL Configuration collection