Configuring HTTP outbound transport level security with an assembly tool
You can configure the HTTP outbound transport level security with an assembly tool.
Before you begin
You can configure HTTP outbound transport level security with assembly tools provided with WebSphere® Application Server.
This task is one of several ways that you can configure the HTTP outbound transport level security for a web service acting as a client to another web service server. You can also configure the HTTP outbound transport level security with the administrative console or by using the Java™ properties. If you do not configure the HTTP outbound transport level security, the web services runtime defers to the Java Platform, Enterprise Edition (Java EE) security runtime in the WebSphere product for an effective Secure Sockets Layer (SSL) configuration. If there is no SSL configuration with the Java EE security runtime in the WebSphere product, the Java Secure Socket Extension (JSSE) system properties are used.
About this task
If you configure the HTTP outbound transport level security with assembly tool or with the administrative console, the Web Services Security binding information is modified. If you have not yet installed the web services application into WebSphere Application Server, you can configure the HTTP SSL configuration with an assembly tool. This task assumes that you have not deployed the web services application into the WebSphere product.
If you configure the HTTP outbound transport level security using the standard Java properties for JSSE, the properties are configured as system properties. The configuration that is specified in the binding takes precedence over the Java properties. However, the configurations that are specified by the Java EE security programming model, or are associated with the Dynamic selection, have a higher precedence.
To learn more, see the secure communications using Secure Sockets Layer information.
Procedure
- Start
an assembly tool. Read about starting the assembly tool in the Rational® Application Developer documentation.
- If you have not done so already, configure the assembly
tool so that it works on Java EE modules. You 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.
- Migrate the web application archive (WAR) files
that are 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.
- Configure the HTTP outbound transport level security.
Read about enabling web service endpoints in the Rational Application Developer documentation.