Application property
names are prefixed with com.sybase.jaguar.application.
You can configure application properties in EAServer Manager using
the Application Properties Dialog box and the folders displayed
under the application icon.
Specifies the comma-separated list of J2EE application clients that are installed in this application.
appclient1, appclient2, ...
Where appclient1, appclient2, and so forth are names of J2EE application clients.
In EAServer Manager, set this property by selecting the application’s Application Clients folder and using the File menu.
Specifies how the custom class loader (version 2) resolves version conflicts when you specify the same class at multiple levels in the class loader hierarchy.
One of the following values:
ParentFirst (the
default) to delegate to the parent class loader before attempting
to load the class at the level of this entity.
ParentLast to
attempt to load the class at the level of this entity before delegating
to the parent.
The value is ignored unless using version 2 of the custom class loader; that is, com.sybase.jaguar.server.jvm.classloader must be set to JaguarClassLoaderv2.
com.sybase.jaguar.server.jvm.classloader, com.sybase.jaguar.component.classloaderpolicy, com.sybase.jaguar.package.classloaderpolicy, com.sybase.jaguar.webapplication.classloaderpolicy
Chapter 30, “Configuring Custom Java Class Lists,” in the EAServer Programmer’s Guide.
Contains a text description of the application.
desc
Where desc is the descriptive text.
In EAServer Manager, set this property using the Description field on the General tab of the Application Properties dialog box.
Specifies the class name for a custom DOM XML parser factory class.
The class name. Either the class name, or, if the class is in a JAR file, the JAR file name, must be listed in the com.sybase.jaguar.application.java.classes property, and the file must be placed in either the EAServer java/classes or java/lib directory.
com.sybase.jaguar.application.SAXfactory, com.sybase.jaguar.application.XSLTfactory
Specifies Java classes and JAR files to be loaded by the application’s custom class loader.
A comma-separated list of Java classes, packages, and JAR files. You can specify all classes in a package using wildcards, as in this example:
com.xyz.MyPackage.*
You can specify all classes in a JAR file by specifying the JAR file name, as in this example:
MyEntityBean.jar
The JAR file must be deployed in the EAServer java/classes subdirectory.
See “Custom class lists for packages, applications, or servers” in Chapter 30, “Configuring Custom Java Class Lists,” in the EAServer Programmer’s Guide.
In EAServer Manager, set this property using the Java Classes tab in the Application Properties dialog box.
com.sybase.jaguar.package.java.classes, com.sybase.jaguar.component.java.classes, com.sybase.jaguar.server.classloader.debug, com.sybase.jaguar.server.java.classes, com.sybase.jaguar.webapplication.java.classes
Specifies the name of an icon file to represent the Web application. This property is not used in EAServer, but is preserved in applications that are imported from a J2EE EAR file.
icon-file
Where icon-file is the name of the icon file.
In EAServer Manager, use the Advanced tab to set this property.
Specifies the application name.
app-name
Where app-name is the application name.
In EAServer Manager, the application name is set when creating or importing an application and cannot be changed.
Specifies the comma-separated list of packages that are installed in this application.
package1, package2, ...
Where package1, package2, and so forth are names of packages.
In EAServer Manager, set this property by selecting the Application’s Packages folder and using the File menu.
Specifies the class name for a custom SAX XML parser factory class.
The class name. Either the class name, or, if the class is in a JAR file, the JAR file name, must be listed in the com.sybase.jaguar.application.java.classes property, and the file must be placed in either the EAServer java/classes or java/lib directory.
com.sybase.jaguar.application.DOMfactory, com.sybase.jaguar.application.XSLTfactory
Specifies the list of trusted identities used for incoming component invocations when propagating client credentials from another server.
t1,t2,t3,...
Where t1, t2, and so forth are identity names that are defined in the repository.
com.sybase.jaguar.application.security.identity, com.sybase.jaguar.server.security.identities, Security properties
Specifies the identity used for outgoing component invocations when propagating client credentials to another server.
The name of an identity that is defined in the repository.
com.sybase.jaguar.application.security.identities, com.sybase.jaguar.server.security.identity, Security properties
Specifies a mapping from a J2EE role name used in the application to a role defined in the EAServer repository.
com.sybase.jaguar.application.security-role.j2ee-role=jag-role
Where:
j2ee-role is the role name used in the application and listed in the com.sybase.jaguar.application.security-roles property.
jag-role is the role name defined in the EAServer repository.
In EAServer Manager, set this property using the Role Mapping tab in the Application Properties dialog box.
Role names can also be specified at the package, component, or Web application level.
com.sybase.jaguar.application.security-roles, com.sybase.jaguar.package.security-role.<j2ee-role>, com.sybase.jaguar.package.security-roles, com.sybase.jaguar.webapplication.security-role.<j2ee-role>, com.sybase.jaguar.webapplication.security-roles, com.sybase.jaguar.component.security-role-ref.<j2ee-role-ref>, com.sybase.jaguar.component.security-role-refs
Specifies logical J2EE role names used in the application.
role1, role2, ...
Where role1, role2, and so forth are of the form:
(description=role-desc, name=role-name)
Where role-desc is an optional description of the role, and role-name is the name used in the application.
In EAServer Manager, set this property using the Role Mapping tab in the Application Properties dialog box. Each J2EE role name must be mapped to an EAServer role name by setting or creating the corresponding com.sybase.jaguar.application.security-role.<j2ee-role> property.
J2EE role names can also be specified at the package, component, or Web application level.
com.sybase.jaguar.application.security-role.<j2ee-role>, com.sybase.jaguar.webapplication.security-roles, com.sybase.jaguar.package.security-roles com.sybase.jaguar.package.security-role.<j2ee-role>, com.sybase.jaguar.component.security-role-ref.<j2ee-role-ref>, com.sybase.jaguar.component.security-role-refs
Specifies the name of an icon file to represent the Web application. This property is not used in EAServer, but is preserved in applications that are imported from a J2EE EAR file.
icon-file
Where icon-file is the name of the icon file.
In EAServer Manager, use the Advanced tab to set this property.
Specifies the comma-separated list of Web applications that are installed in this application.
webapp1, webapp2, ...
Where webapp1, webapp2, and so forth are names of Web applications.
In EAServer Manager, set this property by adding or removing items from the application’s Web Applications folder.
Specifies the class name for a custom XSLT XML parser factory class.
The class name. Either the class name, or, if the class is in a JAR file, the JAR file name, must be listed in the com.sybase.jaguar.application.java.classes property, and the file must be placed in either the EAServer java/classes or java/lib directory.
com.sybase.jaguar.application.DOMfactory, com.sybase.jaguar.application.SAXfactory
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
