Like Chuck said:
you can freely choose names and values you like. Choose your names
carefully to prevent collisions with properties used by other
components, e.g. you can start the name with your internet domain name
or similar.
Example
Property -Dorg.myorg.myapp.node1.http.port=8001
in server.xml:
<Connector port="${org.myorg.myapp.node1.http.port}" ...
Regards,
Rainer
Anna Nhan schrieb:
> Rainer,
>
> I've been searching the web for documented system properties to use to set
> up Catalina, but I am confused.
>
> How do I know which system properties to use? And where can I find proper
> documentation for it?
> Will setting these Catalina options be reflected in the server.xml?
>
> Thanks,
> Anna
>
>
>>> Hi Anna,
>>>
>>> Anna Nhan schrieb:
>>>> Hi,
>>>>
>>>> Is there a way to change the Connector element in server.xml without
>>>> manually editing the file? Could we, for example, change the
>>>> CATALINA_OPTS line using a script or C code to choose whether to use
>>>> HTTP or HTTPS, the file path to the keystore and keystore password,
>>>> and whether or not the server should require client authentication?
>>> Starting with TC 5.0 you can use system properties in server.xml, which
>>> you can set during startup as commandline arguments
>>> (-Dname.of.the.property=value).
>>>
>>> You refer to a system property in server.xml with ${name.of.the.property
>> }.
>>> If you don't like a very long command line, you can also set system
>>> properties by adding them to catalina.properties (e.g. the startup
>>> script could concatenate a master catalina.properties with additional
>>> lines coming out of the script).
>>>
>>> Those ideas don't really help for passwords though (i.e. they don't get
>>> more secret by this).
>>>
>>>> Thanks,
>>>> Anna
>>> Regards,
>>>
>>> Rainer
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
