Difference between revisions of "Edge Server Configuration"
From RifidiWiki
(New page: This page explains the various configuration options of the Rifidi Edge Server =RifidiEdgeServer.ini= The RifidiEdgeServer.ini is a property file that contains options for various options ...) |
|||
| Line 1: | Line 1: | ||
This page explains the various configuration options of the Rifidi Edge Server | This page explains the various configuration options of the Rifidi Edge Server | ||
=RifidiEdgeServer.ini= | =RifidiEdgeServer.ini= | ||
| − | The RifidiEdgeServer.ini is a property file that contains options for various options when the edge server starts up. By default it looks like this: | + | The RifidiEdgeServer.ini is a property file that contains options for various options when the edge server starts up. |
| + | ==Default .ini file== | ||
| + | By default it looks like this: | ||
<pre> | <pre> | ||
-os | -os | ||
| Line 25: | Line 27: | ||
-Dorg.rifidi.edge.ale.port=8081 | -Dorg.rifidi.edge.ale.port=8081 | ||
-Dorg.rifidi.edge.ale.host=127.0.0.1 | -Dorg.rifidi.edge.ale.host=127.0.0.1 | ||
| − | |||
-Dorg.rifidi.edge.jms.hostname=127.0.0.1 | -Dorg.rifidi.edge.jms.hostname=127.0.0.1 | ||
-Dorg.rifidi.edge.jms.port=1100 | -Dorg.rifidi.edge.jms.port=1100 | ||
| Line 31: | Line 32: | ||
-Dorg.aspectj.osgi.verbose=true | -Dorg.aspectj.osgi.verbose=true | ||
</pre> | </pre> | ||
| − | + | ==Console== | |
;-console | ;-console | ||
:This starts up the OSGi console so that you can interact with the edge server from the command line. For a list of commands that are available see [[Edge Server Commands]]. If you would like the console to be available over the network, supply a port after the -console (e.g. -console 2020). Now it is possible to telnet into the server at the given port. It is recommended that you use ssh tunneling for security reasons (i.e. first ssh to the machine that is running the edge server, then telnet to the console). One thing to note is that after you telnet to the OSGi console, you cannot use the <tt>exit</tt> command as you normally would to close the telnet session. This is because <tt>exit</tt> will be caught by the OSGi console and will perform a System.exit(). Instead, to exit the telnet session while keeping the server running, just close the telnet window. | :This starts up the OSGi console so that you can interact with the edge server from the command line. For a list of commands that are available see [[Edge Server Commands]]. If you would like the console to be available over the network, supply a port after the -console (e.g. -console 2020). Now it is possible to telnet into the server at the given port. It is recommended that you use ssh tunneling for security reasons (i.e. first ssh to the machine that is running the edge server, then telnet to the console). One thing to note is that after you telnet to the OSGi console, you cannot use the <tt>exit</tt> command as you normally would to close the telnet session. This is because <tt>exit</tt> will be caught by the OSGi console and will perform a System.exit(). Instead, to exit the telnet session while keeping the server running, just close the telnet window. | ||
| + | ==VMArgs== | ||
| + | VMArgs must follow the <tt>-vmargs</tt> flag in the .ini file. They must start with <tt>-D</tt>. Default values can be found in the <tt>bundle.properties</tt> file in the spring directory for the appropriate option. Important VM args: | ||
;-Dorg.rifidi.edge.configuration | ;-Dorg.rifidi.edge.configuration | ||
:This is the path to the persistence file. See [[#rifidi.ini]]. | :This is the path to the persistence file. See [[#rifidi.ini]]. | ||
Revision as of 19:29, 14 September 2009
This page explains the various configuration options of the Rifidi Edge Server
RifidiEdgeServer.ini
The RifidiEdgeServer.ini is a property file that contains options for various options when the edge server starts up.
Default .ini file
By default it looks like this:
-os
${target.os}
-ws
${target.ws}
-arch
${target.arch}
-nl
${target.nl}
-console
-vmargs
-Declipse.ignoreApp=true
-Dosgi.noShutdown=true
-Dorg.rifidi.edge.configuration=test.ini
-Dosgi.clean=true
-Dorg.osgi.framework.bootdelegation=javax.xml.ws
-Dcom.sun.management.jmxremote.port=2021
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Djava.rmi.server.hostname=127.0.0.1
-Dorg.rifidi.edge.core.rmi.port=1101
-Dorg.rifidi.edge.ale.port=8081
-Dorg.rifidi.edge.ale.host=127.0.0.1
-Dorg.rifidi.edge.jms.hostname=127.0.0.1
-Dorg.rifidi.edge.jms.port=1100
-Dosgi.framework.extensions=org.eclipse.equinox.weaving.hook
-Dorg.aspectj.osgi.verbose=true
Console
- -console
- This starts up the OSGi console so that you can interact with the edge server from the command line. For a list of commands that are available see Edge Server Commands. If you would like the console to be available over the network, supply a port after the -console (e.g. -console 2020). Now it is possible to telnet into the server at the given port. It is recommended that you use ssh tunneling for security reasons (i.e. first ssh to the machine that is running the edge server, then telnet to the console). One thing to note is that after you telnet to the OSGi console, you cannot use the exit command as you normally would to close the telnet session. This is because exit will be caught by the OSGi console and will perform a System.exit(). Instead, to exit the telnet session while keeping the server running, just close the telnet window.
VMArgs
VMArgs must follow the -vmargs flag in the .ini file. They must start with -D. Default values can be found in the bundle.properties file in the spring directory for the appropriate option. Important VM args:
- -Dorg.rifidi.edge.configuration
- This is the path to the persistence file. See #rifidi.ini.
- -Dcom.sun.management.jmxremote.port
- The port to open up JMX on. This is important if you are using a program like VisualVM to profile the server
- -Djava.rmi.server.hostname
- The hostname to open up the RMI registry at. Default is 127.0.0.1
- -Dorg.rifidi.edge.core.rmi.port
- The port of the RMI registry Default is 1101
- -Dorg.rifidi.edge.ale.host
- The hostname to publish the ALE webservices at. Default is 127.0.0.1
- -Dorg.rifidi.edge.ale.port
- The port to publish the ALE webservices at. Default is 8081
- -Dorg.rifidi.edge.ale.read
- The service name of the ALE reading service. Default is ALEService
- -Dorg.rifidi.edge.ale.logicalreader
- The service name of the ALE logical reader service. Default is ALELRService
- -Dorg.rifidi.edge.jms.hostname
- The hostname to use for JMS. Default is 127.0.0.1
- -Dorg.rifidi.edge.jms.port
- The port to use for JMS. Default is 1100
- -Dorg.rifidi.edge.jms.topic.tags
- The topic name that JMS will publish all tag read events at. Default is org.rifidi.edge.external.tags
- -Dorg.rifidi.edge.jms.topic.notifications
- The topic name that JMS will publish all notification events (such as when a reader is added or a session is started). Default is org.rifidi.edge.external.notifications
