These reference pages document EAServer properties as they are stored in the configuration repository. Typically, if you configure EAServer using EAServer Manager, you do not need to work with properties in this format. You will edit properties in this format if:
You use jagtool or jagant to configure EAServer, as described in Chapter 12, “Using jagtool and jagant.”
You use an EAServer XML configuration file to configure properties inside a J2EE archive file, as described in “Using EAServer configuration files in J2EE archives”.
You use the Advanced tab in EAServer Manager to configure properties that cannot be set any other way.
You write applications that use the Jaguar::Management and Jaguar::Repository interfaces to programmatically configure properties. For information on these interfaces, see the generated HTML Interface Repository documentation, located in the html/ir subdirectory of your EAServer installation.
You can define additional properties that are not listed here. For example, if you are implementing CORBA components, you can define additional properties that are read by the component implementation.
If a property name ends in .e,
values for the property are encrypted when stored in the EAServer
configuration repository. You can use this feature to encrypt user-defined
properties. You cannot rename properties that are used internally
by EAServer to use encryption, because EAServer will continue to look
up the property with the original name.
Some properties include a section called “See also,” which directs you to a location where you can find more information. Cross-references to other properties within this appendix do not include a page number, because the properties are listed alphabetically. Cross-references to other chapters in this book include either the chapter number or the page number.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|