When multiple server instances are configured to run as a VirtualServer, a third-party (non-FileNet) load balancing mechanism must exist if you want to distribute incoming requests among the server instances. This could be a Java™ Platform Enterprise Edition (Java EE) application server's clustering implementation, or it could be an external hardware or software load balancing product. In either case, an administrator, using the third-party's load balancing configuration tools, is responsible for configuring the load balancing for a VirtualServer.
VirtualServer objects are created dynamically during system initialization and startup based on the configured topology of the application server or via specific system properties. They cannot be created via the API. You can retrieve a persisted VirtualServer object by calling GetInstance or FetchInstance on the Factory.VirtualServer class.
Assembly: FileNet.Api (in FileNet.Api.dll)
Syntax
Visual Basic (Declaration) |
---|
Public Interface IVirtualServer _ Implements IIndependentlyPersistableObject, IIndependentObject, IEngineObject, ICloneable |
C# |
---|
public interface IVirtualServer : IIndependentlyPersistableObject, IIndependentObject, IEngineObject, ICloneable |
Visual C++ |
---|
public interface class IVirtualServer : IIndependentlyPersistableObject, IIndependentObject, IEngineObject, ICloneable |
JavaScript |
---|
FileNet.Api.Admin.IVirtualServer = function(); FileNet.Api.Admin.IVirtualServer.createInterface('FileNet.Api.Admin.IVirtualServer'); |
Remarks
Metadata
Auditable: false
AllowsInstances: false
AllowsSubClasses: false
ClassDefinitionName: None
IsDependent: false
IsHidden: false
Searchable: false
StorageType: Domain
SuperclassName: GenericObject