You can start a subset of the agents, or no additional agents if you don't need their features. For instance, in a minimal WebServer configuration, only the WebServer and the HTTPFileServer agent are needed to serve static files.

This error is usually the result of problems with the classname prop. Check that your compiled assembly is in the same directory as the Neokernel executable, and that the classname prop uses the same lettercase and spelling as the class you wish to load.

1. If you can't find any problems, check the syntax of your classname prop. C# agents are loaded using the following syntax in the classname prop:

<assembly_name>.<classname>

Agent classes that are compiled into a Visual Basic.NET assembly require a different syntax to load the class from the assembly:

<assembly_name>.<namespace>.<classname>

2. Also, check to be sure that the assembly you are loading is in the same directory as the neokernel.exe or in a subdirectory of the executable's directory.

3. Thirdly, check in your agent's start() method to be sure it isn't trying to use agents that haven't been started yet. For instance, if you try to register() with the ServiceManager before the ServiceManager has started, you will see an error.

4. Finally, check to be sure that there aren't any conflicting versions of your assembly lying around in the references path.

The RequestAgent class contains important features for multithreading, Web I/O, and agent collaboration.

Yes. The Neokernel uses the ASP.NET runtime built into the .NET environment to execute ASP.NET files. Only files with the .aspx extension are handled by the ASP.NET runtime. Note: If your ASP.NET file references a .dll or assembly, that .dll must be in the /bin subdirectory of the folder where your .aspx file is located. If you want to use a web.config file with ASP.NET debugging properties, put that file in the same directory as your .aspx file.

This is a restriction imposed by the .NET environment to resolve the infamous problems of dll hell.

This is to maintain consistency with Neokernel platforms that are implemented using other languages.

Changing the bind_port is useful when running on a machine that has another Web Server running on it. The bind_port determines the port that the WebServer will listen for connections on. Only one process can be listening on a given port, so if you want to run several instances of the Neokernel in parallel on a single host, you must assign each Neokernel a unique bind_port to avoid conflicts. HTTP connections are routed to port 80 by default, so if you don't specify a bind_port property the server will listen on port 80.

If you put a configuration file (neokernel_props.xml ) in the startup directory, you can specify the bind_port in the WebServer section of this file.

Alternatively, you can create a com.neokernel.props.Props containing each of the properties for the webserver and start the server programmatically from your code.

This property is used for performance tweaking under extremely heavy server loads; usually it should remain unchanged.

The refuse_requests prop is used by the WebServer as a blacklist;if any of the strings on this blacklist appear in any part of an incoming request, that request is dropped. This is useful if you want to block clients using a specific browser or coming from a specific IP range.

The max_file_size property defines the maximum size (in bytes) that a log file can grow to before the server starts a fresh log file. This property is supported by agents that perform logging.

Install a copy of the neokernel.dll and a copy of your license with each installation of your software.

Yes, if you bought a license for redistribution then you may redistribute the Neokernel.dll with your application.

Please contact the sales department for a quote at sales@neokernel.com or (412) 682-5282.

The localhost_cert.pfx certificate is tied to the domain name localhost. It is intended ONLY as an example; if you want to buy a production certificate for your domain name, contact the sales department.

The executable directory or any sub-directory of the executable directory.

You can use any technique or component that you prefer. The Neokernel works with any database access method supported by the .NET framework.

nkhttpd.exe was the name of the executable in release 1.0 of the Neokernel. This has been changed.

Yes. You can comment a line using the syntax '##'.

Double check to be sure you deleted the extra copy of WebTutorials.dll from the Neokernel's root directory.

One way to accomplish this is by using ASP.NET pages as described in this article: http://www.aspfree.com/c/a/ASP.NET/Creating-an-ASPNET-Webservice-Part-1-of-2/

The Neokernel web server passes your ASP.NET page to the ASP.NET compiler, which generates the output for the requestor.

Another way is to create ASMX/WSDL files describing your web service applications and serve these just like other static files, using the Neokernel web server. You must add the neccessary MIME types to the MIME types configuration file, for example:

xml=text/xml

asmx=text/xml

wsdl=text/xml

The field RequestHeaders in the HTTPAgentRequest method contains the all headers in the request in one string. The following sample code will print the headers passed by the browser:

using System;

using com.neokernel.nk;

using com.neokernel.httpd;

public class HeadersPage:RequestAgent

{

public override void handleRequest(AgentRequest request)

{

string headers = (HTTPAgentRequest)request.RequestHeaders;

request.println("<HTML><P> Incoming Request Headers:"

+ headers +

}

}

Set the value of the agent's log_dir prop to the directory you want to output your logs to. You can do this with the XML startup file OR by setting the agent's prop from your code. By default, the log_dir prop is set to System.Windows.Forms.Application.ExecutablePath + /logs./logs".

The com.neokernel.io.ServiceReporter is used to log information when running as a service. Errors will appear in the windows event log by default, and the ServiceReporter's printEventLogEntry() and debugEventLogEntry() methods can be used to output non-error information to the event log, as in the following example:

if (NK.DefaultReporter is ServiceReporter) {

ServiceReporter logger = (ServiceReporter)NK.DefaultReporter;

logger.printEventLogEntry(this, This message will have an info icon. );

logger.debugEventLogEntry(this, This message will have a warning icon. );

}

The ASP.NET runtime will only work if the assemblies it needs are in the \bin subdirectory of the folder where the ASP.NET file (.aspx) is located. When the Neokernel loads the ASP.NET runtime, it tries to create this subdirectory and populate it with the needed assemblies. If the Neokernel doesn't have the neccessary write priveleges to create this directory, the ASP.NET Runtime won't be loaded and you'll see this error:

!HTTPFileServerAgent! ASP.Net Runtime couldn't start.

The workaround is to manually create this directory and copy the neokernel.exe and any other assemblies used by your ASP.NET file into the /bin subdirectory of the directory where your ASP.NET file is located. In the case of the ASP.NET demo installed with the product, you must put a copy of the neokernel.exe file at [NEOKERNEL_INSTALLATION_FOLDER]\demos\asp.net\bin\neokernel.exe

Add the following section to your neokernel.props file, and replace newLogFilePrefix with the prefix you want for your sequentially numbered log files.

<props>

<classname>com.neokernel.io.FileLoggerAgent</classname>

<service_name>logger_agent</service_name>

<startup>true</startup>

<log_file_prefix>newLogFilePrefix</log_file_prefix>

<logs_per_file>10000</logs_per_file>

<log_dir>logs</log_dir>

</props>

Note: the logs_per_file property specifies the number of log entries that will be written to each log file before a new one is created.

Your Neokernel event log may be full; try clearing your Neokernel event log using the Event Viewer, and restart the service.

No, the Neokernel Web Server does not submit static files (like images, movies and .html files) to the ASP.NET processor, static data is served using the Neokernel's internal thread management for faster performance.

Yes. Please check out these demos: C# Application Bootstrapping, http://www.neokernel.com/content.agent?page_name=Demo&name=024 and VB Application Bootstrapping Example http://www.neokernel.com/content.agent?page_name=Demo&name=038 .