skip to main content
Corticon Server: Integration & Deployment Guide : Packaging and deploying Decision Services : Creating custom context URLs on a web server
 

Try Corticon Now

Creating custom context URLs on a web server

Corticon web service deployment is preset to a singular web service identity, axis. To access that web service, you might enter http://localhost:8850/axis. You can choose to run multiple instances of Corticon Server on the same host:port , such as http://localhost:8850/another. This enables you to use one application server, yet create unique Decision Service URL end points that provide isolation to different sets of Decision Services.
To add another Java WAR file to a Java web server:
This example clones the default WAR file, axis.war that was deployed on the embedded Progress Application Server, and then configures and runs the new web archive successfully.
1. Stop the Java web server.
2. In [CORTICON_WORK_DIR]\pas\server\webapps, copy axis.war, and then paste it there to make a copy.
3. Edit the name axis - Copy.war to your preferred .war name. Use alphanumeric characters and underscores, and no spaces. For example Java_UAT.war for your user acceptance testing instance. The new WAR file will be expanded into its directory structure when you start the application server.
4. To configure settings specific to this new Corticon Server node, expand the WAR file with an archive utility, such as WinZip.
5. Navigate in the new context's file location to \Server\pas\server\webapps\Java_UAT\WEB-INF\lib\CcConfig.jar.
6. Extract and edit the CcServer.properties file as follows:
*Change the line com.corticon.ccserver.sandboxDir=%CORTICON_WORK_DIR%/%CORTICON_SETTING%/CcServerSandbox to com.corticon.ccserver.sandboxDir=%CORTICON_WORK_DIR%/%CORTICON_SETTING%/Java_UAT/CcServerSandbox
*Change the line com.corticon.ccserver.autoloaddir=%CORTICON_WORK_DIR%/cdd to com.corticon.ccserver.autoloaddir=%CORTICON_WORK_DIR%/Java_UAT/cdd
*Change the line com.corticon.server.embed.managementWebLogDirectory=%CORTICON_WORK_DIR%/logs to com.corticon.server.embed.managementWebLogDirectory=%CORTICON_WORK_DIR%/Java_UAT/logs
*Save the edited file.
7. Extract and edit the cccommon.properties file, and then change the line logpath=%CORTICON_WORK_DIR%/logs to logpath=%CORTICON_WORK_DIR%/Java_UAT/logs
8. Save both files and replace them in the CcConfig.jar.
9. Repackage the entire set of files back into its WAR file.
10. Restart the Java web server.
The two Java server deployments run. Using the Web Console, you can manage the two distinct server context URLs, for example, myServer:8850/axis and myServer:8850/Java_UAT.
To add another Corticon .NET web service to an IIS server:
This example clones the default .NET web service, axis that was installed from a Corticon Server for .NET installation to an IIS server configured for Corticon web services, and then runs the new application successfully.
1. In the IIS Manager, on the Actions panel, click Stop.
2. In the Server .NET's [CORTICON_HOME]\IIS folder, copy install.bat, and then paste it there to make a copy.
3. Edit the name install - Copy.bat to your preferred .war name. Use alphanumeric characters and underscores, and no spaces. For example install_anotherNET.bat.
4. Edit that file to replace all instances of axis with anotherNET, and then save the edited file.
5. Run the script.
6. Navigate in the new context to C:\inetpub\wwwroot\anotherNET\conf.
7. Edit the CcServer.properties file as follows:
*Change the line com.corticon.ccserver.sandboxDir=%CORTICON_WORK_DIR%/%CORTICON_SETTING%/CcServerSandbox to com.corticon.ccserver.sandboxDir=%CORTICON_WORK_DIR%/%CORTICON_SETTING%/AnotherNET/CcServerSandbox
*Change the line com.corticon.ccserver.autoloaddir=%CORTICON_WORK_DIR%/cdd to com.corticon.ccserver.autoloaddir=%CORTICON_WORK_DIR%/AnotherNET/cdd
*Change the line com.corticon.server.embed.managementWebLogDirectory=%CORTICON_WORK_DIR%/logs to com.corticon.server.embed.managementWebLogDirectory=%CORTICON_WORK_DIR%/AnotherNET/logs
*Save the edited file.
8. Extract and edit the cccommon.properties file, and then change the line logpath=%CORTICON_WORK_DIR%/logs to logpath=%CORTICON_WORK_DIR%/AnotherNET/logs
9. Save the edited file.
10. In the IIS Manager, perform the same tasks that were performed when axis was installed into IIS. In brief:
a. Set Access Permissions for the application's directories,
b. Convert the new folder into an application.
c. Set the application to use the appropriate application pool.
See Setting up and updating IIS for .NET Server in the Installation Guide for more information and links to the various IIS setup articles in the Knowledgebase.
11. In the IIS Manager, on the Actions panel, click Start.
The two .NET server deployments run. Using the Web Console, you can manage the two distinct server context URLs, for example, myServer:80/axis and myServer:80/anotherNET.