skip to main content
Corticon Server: Deploying Web Services with .NET : Setting up Corticon Server for .NETon IIS : Testing the installed Corticon Server for .NET : Testing a remote server on IIS
 

Try Corticon Now
Testing a remote server on IIS
To test that Corticon Server deployed as a SOAP service is running correctly, all you need is a SOAP client or the sample batch file provided and described below.
Testing the installation here assumes you have already set up IIS, and installed Corticon Server for .NET as a Web Service. Be sure that you have created an application from the axis directory, and that it is bound to application pools appropriately.
Because a SOAP service is listening for SOAP calls, we need a way to invoke an API method via a SOAP message then send that message to Corticon Server using a SOAP client. In the sample code supplied in the default installation, Corticon provides an easy way to send API calls through a SOAP message.
Sample code is provided that demonstrates a remote deployment of Corticon Server for .NET on IIS. This code is packaged as the executable Corticon-Api-Remote-Test.exe in the Server\bin directory of your Corticon Server for .NET installation directory.
When executed, it opens a Windows console and displays the API menu, as shown below:
Figure 389. Top Portion of the .NET Server remote API console
The menu displayed in the Windows console is too large to fit on a single printed page, so it has been divided into two screenshots here. In the upper portion of the Windows console, shown in the figure above, the classpath definition process is visible. Once all classes are loaded, the Corticon Server for .NET starts up in the IIS, which is needed by our simple SOAP client class.
Figure 390. Lower Portion of the .NET Server remote API console
In the lower portion of the Windows console, shown in the figure above, we see the available API methods of the Common Functions (the 100 series) listed by number. You can list the commands in the other series by entering their series number:
*Enter 200 to list the Decision Service Functions command set
*Enter 300 to list the Monitoring Functions command set
*Enter 400 to list the CcServer Functions command set
*Enter 100 to again list the Common Functions command set
Note: After you enter a transaction, the result is displayed followed a restating of the current command set. You might need to scroll back a bit to see your results.
Since we have not deployed any Ruleflows yet, we will use an administrative method to test if Corticon Server is correctly installed as a SOAP service inside our web server. A good administrative method to call is transaction #121, Get CcServer current info. This choice corresponds directly to the API method getCcServerInfo().
To try this, confirm that IIS is running, and then enter 121 in the command window. The CcServerAxisTest class makes a call to the Corticon Server SOAP Servlet. It asks for a list of configuration parameters and returns them to the Windows console. The results of the call are shown in the following figure:
Figure 391. .NET Server remote API console response to command 121
The response verifies that our Corticon Server is running correctly as a SOAP Servlet and is listening for, and responding to, calls. At this stage in the deployment, this is all we want to verify.