skip to main content
Corticon Server: Integration & Deployment Guide : Packaging and deploying Decision Services : Using Studio to compile and deploy Decision Services : Compiling and deploying to a Corticon Server

Try Corticon Now
Compiling and deploying to a Corticon Server
When you choose to deploy to a Corticon Server, you first define a valid server connection, and then select Ruleflows to compile and deploy to that server.
To connect to a Corticon Server from the Server Connection panel:
1. Enter the Server URL of the Corticon Server.
2. Enter the Username and Password for the server. For administrative permissions on Progress Application Server, try the default credentials admin and admin.
3. Click Test Connection.
*On successful connection, the system displays: Server connection test was successful.
*If the username or password is invalid, the system displays: User does not have rights to upload/download content to/from the server.
*On errors such as the server being unavailable, the system displays: Server connection test failed. Server may be off-line, unreachable, not listening on specified port, or incorrect Server URL, username, or password.
*On an unexpected ‘Hard’ failure, the system unwraps the Axis Fault and finds the underlying cause, such as 404 when the user specifies URL incorrectly.
Once the connection test is successful, you are able to proceed.
4. Click Next.
The Decision Services panel lists the Ruleflows in the context you specified.
The columns on this panel show the following about each Ruleflow:
*The wizard copies the Decision Service Name from the Ruleflow file name. You can change any Decision Service Name to publish the Decision Service with a preferred name. When you do that, the wizard might toggle the Status field between New and Update depending on whether that name is already deployed.
*Version is read from the Ruleflow's properties It is not modifiable here.
*Status indicates whether the Decision Service version is New or Update (that is, whether that Decision Service name with that version identity is already deployed on the server).
*Database mode for a Ruleflow that will have a database connection.
*Return entities for a Ruleflow that will have a database connection.
*Ruleflow location within the current workspace.
5. Click the check box for each Ruleflow to be packaged and deployed to the server as Decision Services.
The wizard does not enable the Finish button if any selected Decision Service has the Status 'Update'. You can override this condition by renaming each such Decision Service, or by selecting the Redeploy checkbox to override and redeploy all such Ruleflows under the existing name and version.
6. Click Finish.
The packaging and deployment progress is shown. It can be stopped (although what has been completed is not backed out) by clicking the Stop button adjacent to the progress bar.
When all the packaging and deployment processes are successful, the wizard alerts you with a Deployment Success message. If there are problems, the wizard lists the errors.