Network Deployment (Distributed operating systems), v8.0 > Secure applications and their environment
Secure Client applications
This page provides a starting point for finding information about application clients and client applications. Application clients provide a framework on which application code runs, so that your client applications can access information on the application server.
For example, an insurance company can use application clients to help offload work on the server and to perform specific tasks. Suppose an insurance agent wants to access and compile daily reports. The reports are based on insurance rates that are located on the server. The agent can use application clients to access the application server where the insurance rates are located.
- Configure secure access to resources for applet clients
By default, the applet client is configured to have security enabled. If we have administrative security turned on at the server from which you are accessing resources, then you can use secure sockets layer (SSL) when needed.
- Example: Running the thin or pluggable application client with security enabled
Your Java thin application client no longer needs additional code to set security providers if we have enabled security for your WAS instance. This code found in iSeries Java thin or pluggable application clients should be removed to prevent migration and compatibility problems. The java.security file from your WebSphere instance in the properties directory is now used to configure the security providers.
- Configure secure access for stand-alone clients
The Thin Client for JMS with WAS and the Resource Adapter for JMS with WAS use the standard Java Secure Socket Extension (JSSE) that all supported JREs provide for making SSL connections.
End-to-end paths for Client applications
Administer Client applications
Client applications
Develop Client applications
Tune Client applications
Troubleshoot Client applications