What can be customized?
Installation on Unix Systems
Installation on Windows NT
Integrate your custom server into Community Server
Example:
The following line would be added to chstart if the installation directory is
/home/blaxxun, the custom server is called myserver, running
on port 2030 and our idserver is running on port 2000.
/home/blaxxun/bin/myserver -p 2030 -BSIROOT /home/blaxxun -i localhost:2000
#define APNT_SERVICE_NAME "apserver"Edit the file apevent.c
// this is the name of your NT service and also the registry
// prefix for the "apserverPort" reg value.
#define APNT_REGVAL_IDSERVER "apserverIdserverHostPort"
// this is the name of the registry key for the idserver port
modify the existing event handler functions to your needs.
Open the makefile apserver.mak in VC++ 4.2.
Compile and build the executable release/apserver.exe
If you rename the servicename you should
also rename the exe file.
Register the apserver.exe file under
NT with the command line tool bin/sinstall.exe. Use the same servicename
as entered in the H-file before for APNT_SERVICE_NAME.
Enter an absolute pathname for the exepath.
Usage: sinstall servicename servicedisplayname
exepath
Enter two new values in the registry:
Start the NT Service Control Manager
and start your new service. The new process writes a log file under C:\BlackSun\CommServ\log\
You can unregister the service using
the command bin/sdelete.exe
APISERVER host:port
where host is the hostname of the machine your customized server runs on and port is the port it listens to. Then hit the Apply button to apply the changes.
Example:
The following line would be added to the configuration file if your custom server
runs on the same machine as the community server (which is the most common and
default setup) and listens to port 2030:
APISERVER localhost:2030
Now your must restart the Community Server (by clicking on the Restart button) and your custom server will apper as one of the running processes in the status list of the administrator console.