Why and when to perform this task
Steps for this task
For example, you might have a Java client communicating with an Enterprise JavaBean (EJB) application server, which in turn communicates to a downstream EJB application server. The Java client utilizes the sas.client.props file to configure outbound security (pure clients only need to configure outbound security). The upstream EJB application server configures inbound security to handle the right type of authentication from the Java client. The upstream EJB application server utilizes the outbound security configuration when going to the downstream EJB application server.
This type of authentication might be different than what you expect from the Java client into the upstream EJB application server. Security might be tighter between the pure client and the first EJB server, depending on your infrastructure. The downstream EJB server utilizes the inbound security configuration to accept requests from the upstream EJB server. These two servers require similar configuration options as well. If the downstream EJB application server communicates to other downstream servers, then the outbound security might require a special configuration.