CA Strong Authentication Windows Installation Guide › Plan the Deployment › Deployment Models › Single System Deployment › Component Diagrams

Component Diagrams

The component diagrams depict a few deployment options for prerequisite software and CA Strong Authentication components. If you perform a Complete install, then both Java SDKs and Web services are on the system. You can use any of these methods for integrating CA Strong Authentication with your Web application.

• Deploying Java SDKs
• Deploying Web Services

Decision Points

If you plan to perform a single-system deployment, make the following decisions:

• Install a database server on the system which has CA Strong Authentication Server, or use an existing database on a separate system.
• Use Sample Application or write my own Web application.

Important! Sample Application must not be used in production deployments. We recommend that you build your own Web application by using Sample Application as a code-reference.

• Use Java SDKs or Web services to integrate with your own Web application.

The following sections are designed to help you achieve your deployment decision.

Deploying Java SDKs

The following figure illustrates deployment of CA Strong Authentication Server and Java SDKs on a single system.

Note: The use of a Web server to deliver HTML pages for the application server is optional and is transparent to CA Strong Authentication . In production deployments, this approach is used to improve Application Server performance and security. See the documentation of your Application Server for detailed information.

Deploying Web Services

If you plan to deploy Web services, then the following figure illustrates CA Strong Authentication Server and Web Services on a single system.

Note: Because all Web Services are now built into the CA Strong Authentication server module itself, you need to install the CA Strong Authentication server on the target system and generate the requisite client stubs. No further configuration is required.