(n.) A specification defined by the Open Mobile Alliance that allows a mobile device to communicate its capabilities to a network server.
(Universal Description, Discovery, and Integration) (n.) Provides worldwide registry of web services for discovery and integration. An industry initiative to create a platform-independent, open framework for describing services, discovering businesses, and integrating business services using the Internet, as well as a registry. It is being developed by a vendor consortium.
(n.) A 16-bit character set defined by ISO 10646 and the Unicode Consortium that maps digits to characters in languages around the world. Because 16 bits covers 32,768 codes, Unicode is large enough to include all the world's languages, with the exception of ideographic languages that have a different character for every concept, such as Chinese. All source code in the Java programming environment is written in Unicode. For more information, see http://www.unicode.org/.
(n.) The concept of using a single message store for email, voicemail, fax, and other forms of communication. Java Enterprise System Messaging Server provides the basis for a complete unified messaging solution.
(n.) The process of removing a software component in its entirety.
(n.) The value for a logged-in user that includes the login name combined with the domain to which the user belongs. For example, a user bill in domain example.com has the Universal Principal Name of firstname.lastname@example.org. Also known as UPN.
(n.) A schema that classifies and identifies commodities. It is used in sell-side and buy-side catalogs and as a standardized account code in analyzing expenditure.
(n.) A general entity that contains something other than XML. By its nature, an unparsed entity contains binary data.
(n.) Unrequested and unwanted email sent from bulk distributors usually for commercial purposes. Also known as spam.
(n.) Indicates the directory server that holds the naming context above your directory server’s naming context in the DIT.
(uniform resource identifier) (n.) A globally unique identifier for an abstract or physical resource. A URL is a kind of URI that specifies the retrieval protocol (http or https for Web applications) and physical location of a resource (host name and host-relative path).
(n.) A process that repairs and updates a URL database that has been damaged by a software failure, a system crash, a disk breakdown, or a full file system.
(n.) The process of mapping a document directory’s physical path name to a user-defined alias so that files within the directory need only refer to the directory’s alias instead of the file’s full physical path name. Instead of identifying a file as usr/JES/servers/docs/index.html, you could identify the file as /myDocs/index.html. This mapping provides additional security for a server by eliminating the need for users to know the physical location of server files.
(n.) The part of a URL passed by an HTTP request to invoke a servlet. A URL path consists of the context path, servlet path, and path info, as follows:
The context path is the path prefix associated with a servlet context of which the servlet is a part. If this context is the default context rooted at the base of the web server's URL namespace, the path prefix will be an empty string. Otherwise, the path prefix starts with a / character but does not end with a / character.
The servlet path is the path section that directly corresponds to the mapping that activated this request. This path starts with a / character.
The path info is the part of the request path that is not part of the context path or the servlet path.
(n.) The list of URLs for the robot to process. When the robot starts, the URL pool consists of the starting points, but the pool is quickly augmented with any resources found during enumeration.
(uniform resource name) (n.) A unique identifier that identifies an entity but doesn't tell where it is located. A system can use a URN to look up an entity locally before trying to find it on the web. It also allows the web location to change, while still allowing the entity to be found.
(n.) A specific end-user task or set of tasks performed by a distributed enterprise application, and used as a basis for designing, testing, and measuring the performance of the application.
(1) (n.) A person or service which uses an application. Programmatically, a user consists of a user name, password, and set of attributes that enables an application to recognize a user.
(2) (n.) An individual (or application program) identity that has been authenticated. A user can have a set of roles associated with that identity, which entitles the user to access all resources protected by those roles. See also principal, group, and role.
(n.) An account for accessing a server maintained as an entry on a directory server.
(n.) For Portal Server Mobile Access, a property that refers to the HTPP user-agent header. The user-agent header is often unique to a particular mobile device and can be used to detect and retrieve data for a client type.
(n.) The client component, such as NetscapeTM Communicator, that allows users to create, send, and receive mail messages. Also known as UA.
(n.) Indicates how data between a client and a web container should be protected. The protection can be the prevention of tampering with the data or prevention of eavesdropping on the data.
(n.) Fields that describe information about each user, required and optional. Examples are distinguished name, full name, title, telephone number, pager number, login name, password, home directory, and so on. Also known as user profile.
(n.) A user’s email mailboxes.
(n.) The group to which the user of a Message Queue client belongs for purposes of authorizing access to Message Queue message server resources, such as connections and destinations.
(n.) A Directory Server that maintains information about users and groups in an organization.
(n.) The amount of space configured by the system administrator that is allocated to a user for email messages.
(n.) The process by which services are made available to end users or by which end users are provided with access to services. Provisioning involves identity, policy, and user account management activities, such as creating an account in a directory for each end user and populating the account with the user-specific information needed by various services.
(n.) A series of user application interactions that are tracked by the server. Sessions maintain user state, persistent objects, and identity authentication.