skip to main content
Corticon Server: Integration & Deployment Guide : Introduction to Corticon Server deployment : Choose the deployment architecture : Installation option 1: Web services

Try Corticon Now
Installation option 1: Web services
Web Services is the most common deployment choice. By using the standards of Web Services (including XML, SOAP, HTTP, WSDL, and XSD), this choice offers the greatest degree of flexibility and reusability.
Corticon Server may be installed as a Web Service using a Java Servlet running in a J2EE web or application server's Servlet container. You can use a Web Services server with IBM WebSphere, Oracle/BEA WebLogic, Apache Tomcat or other containers that support multi-threading Web Services (see Installing Corticon Server).
The Web Services option is the easiest to configure and integrate into diverse consuming applications. Refer to Corticon Server: Deploying Web Services with Java and Corticon Server: Deploying Web Services with .NET.
When deploying Corticon Decision Services into a Web Services server, the Deployment Console (or Deployment Console API) is used to generate WSDL files for each Decision Service (see Deploying Corticon Ruleflows). These WSDL files can then be used to integrate the Decision Services into Consuming applications as standard Web Services (see Integrating Decision Services). Corticon users can also build their own infrastructure that publishes the WSDL files to UDDI directories for dynamic discovery and binding.