Settings
This reference information describes settings that you can view and configure on the pages of the product administrative console and elsewhere.
Custom properties are documented separately. They are name-value pairs that you can enter on specific console pages if you know what to specify.
Subtopics
Access intent assembly settings
Access intent policies contain data-access settings for use by the persistence manager. Default access intent policies are configured on the entity bean.Access point group collection
Use this page to view the sets of access point groups. Access point groups define the set of core groups that communicate with each other. Access point groups that connect multiple cells must have one core group access point and a single peer access point for each remote cell. Access point groups that provide communications between core groups in the same cell must contain only core group access points.Access point group settings
Use this page to modify the core group access points and the peer access points that belong to an access point group. An access point group defines the set of core groups that can communicate with each other.Acknowledgement state collection
The ranges of message sequence numbers received from the WS-ReliableMessaging source. If more than one range is displayed, this indicates a gap in the messages received. If "In-order delivery" is selected for the sequence manager, messages with a sequence number greater than the lowest gap cannot be delivered to the application until the gap is closed.Activation specification collection
A JMS activation specification is associated with one or more message-driven beans and provides the configuration necessary for them to receive messages. The default messaging provider and the WebSphere® MQ messaging provider both support use of activation specifications.Active key history collection
Use this page to manage key alias references.ActivitySession service settings
Use this page to configure the properties of the ActivitySession service. The ActivitySession service is a unit-of-work service to coordinate one-phase resources or to extend the activation and passivation of an enterprise bean.Actor [Settings]
Defines the Actor URI to be included in the WS-Security headers of a generated message.Actor [Settings]
Defines the Actor URI to be included in the WS-Security headers of a generated message.Actor [Settings]
Defines the Actor URI to be included in WS-Security headers of generated response.Actor roles settings
Use this page to define settings for SOAP actor roles. The SOAP actor, also known as the SOAP role, defines the intermediary or ultimate recipient of a message.Add asset settings
Use this page to add one or more assets to a business-level application.Add a transport to the list of permitted transports [Settings]
Add a transport to the list of permitted transports.Add a user or group to the bus connector role [Settings]
Create a user or group in the bus connector role.Add a Windows based node as a Windows service
Use this page to run the node agent as a Windows service.Add composition unit settings
Use this page to specify options for the composition unit to be added to the business-level application. The product assigns a default value for an option when you do not specify a value.Add created time stamp [Settings]
Specifies whether a time stamp will be added to any sent message. The time stamp may also contain an expires value.Add federated repository settings
Use this page to specify the configuration for access to a file repository.Add Installation Manager installation kits
Use this page to specify an IBM® Installation Manager installation kit that you want to add to your list of Installation Manager installation kits.Additional Common Secure Interoperability inbound authentication settings
Use this page to configure additional authentication settings for requests that are received by this server using the Object Management Group (OMG) Common Secure Interoperability authentication protocol.Additional Common Secure Interoperability outbound authentication settings
Use this page to configure additional authentication settings for requests that are received by this server using the Object Management Group (OMG) Common Secure Interoperability authentication protocol.Add key alias reference settings
Use this page to access key alias reference information.Add managed node settings
A managed node is a node with an application server and a node agent that belongs to a deployment manager cell. Use this page to add an application server node to a deployment manager cell.Add received time stamp [Settings]
Specifies whether a time stamp will be added to any received message.Add signer certificate settings
Use this page to add a signer certificate in a certificate file to the keystore in the security configuration.Add time stamp [Settings]
When add time stamp is specified for a consumer, a time stamp is added indicating when the message was consumed. For a generator, a time stamp is added indicating when the message was generated.Add time stamp [Settings]
When add time stamp is specified for a consumer, a time stamp is added indicating when the message was consumed. For a generator, a time stamp is added indicating when the message was generated.Add time stamp [Settings]
When add time stamp is specified for a consumer, a time stamp is added indicating when the message was consumed. For a generator, a time stamp is added indicating when the message was generated.Add time stamp [Settings]
When add time stamp is specified for a consumer, a time stamp is added indicating when the message was consumed. For a generator, a time stamp is added indicating when the message was generated.Administered objects settings
Use this panel to view or change the configuration properties of the selected administered objects.Administered subscribers [Collection]
An administered subscriber provides a mechanism for the WS-Notification service point to subscribe to an external notification producer at server startup time.Administered subscribers [Collection]
An administered subscriber provides a mechanism for the WS-Notification service point to subscribe to an external notification producer at server startup time.Administered subscribers [Settings]
An administered subscriber provides a mechanism for the WS-Notification service point to subscribe to an external notification producer at server startup time.Administration service settings
Use this page to view and change the configuration for an administration service.Administrative agent settings
Use this page to configure the administrative agent and view its properties.Administrative Authorization Group collection
Use this page to create, delete or to edit an existing administrative authorization group.Administrative console: Resources for learning
Use the following links to find relevant supplemental information about the IBM WebSphere Application Server administrative console. The information resides on IBM and non-IBM Internet sites, whose sponsors control the technical accuracy of the information.Administrative console actions with command assistance
Using command assistance, you can view wsadmin scripting commands in the Jython language for the last action that runs in the administrative console. This topic lists the administrative console actions that have wsadmin commands available in the command assistance option of the Help portlet.Administrative console browser support
Several web browsers are supported for use with Integrated Solutions Console.Administrative console buttons
This page describes the button choices that are available on various pages of the administrative console, depending on which product features you enable.Administrative console page features
This topic provides information about the basic elements of an administrative console page, such as the various tabs.Administrative console preference settings
Use the preference settings to specify how you want information to display on an administrative console panel. The preference settings vary from one administrative console panel to another.Administrative console scope settings
Use this page to specify the level at which a resource is visible on the administrative console page. By changing the value for Scope, you see only the resources that are defined at that scope. The contents of the collection table might change. A resource can be visible in the administrative console collection table at the cell, node, or server scope. For multiple-server products, a resource also can be visible at the cluster scope.Administrative group roles and CORBA naming service groups
Use the Administrative Group Roles page to give groups specific authority to administer application servers through tools such as the administrative console or wsadmin scripting. The authority requirements are only effective when administrative security is enabled. Use the Common Object Request Broker Architecture (CORBA) naming service groups page to manage CORBA Naming Service groups settings.Administrative roles
The Java™ Platform, Enterprise Edition (Java EE) role-based authorization concept is extended to protect the WebSphere Application Server administrative subsystem.Administrative roles for business level applications
The Java 2 Platform, Enterprise Edition (J2EE) role-based authorization concept is extended to protect the WebSphere Application Server administrative subsystem. This protection applies to those administrative roles associated with business level applications.Administrative topology: Resources for learning
Use the following links to find relevant supplemental information about WebSphere Application Server administrative topologies and distributed administration. The information resides on IBM and non-IBM Internet sites, whose sponsors control the technical accuracy of the information.Administrative user password settings
Use this page to set a password for the administrative user who manages the product resources and user accounts.Administrative user roles settings and CORBA naming service user settings
Use the Administrative User Roles page to give users specific authority to administer application servers through tools such as the administrative console or wsadmin scripting. The authority requirements are only effective when global security is enabled. Use the Common Object Request Broker Architecture (CORBA) naming service users settings page to manage CORBA naming service users settings.Advanced Lightweight Directory Access Protocol user registry settings
Use this page to configure the advanced Lightweight Directory Access Protocol (LDAP) user registry settings when users and groups reside in an external LDAP directory.Advanced resource adapter properties
Use this page to specify advanced settings for resource adapters that comply with the Version 1.5 and 1.6 Java Platform, Enterprise Edition (Java EE) Connector Architecture (JCA) specification.Advice configuration settings
Use this page to select the advice you wish to enable or disable.Algorithm mapping collection
You can view a list of custom uniform resource identifier (URI) algorithms for digest value calculation, signature, key encryption, and data encryption. The application server maps these algorithms to an implementation of the algorithm factory engine interface. With algorithm mappings, service providers can extend the cryptographic algorithms for XML digital signature and XML encryption.Algorithm mapping configuration settings
Use this page to view a list of custom uniform resource identifier (URI) algorithms for digest value calculation, signature, key encryption, and data encryption. The application server maps these algorithms to an implementation of the algorithm factory engine interface. With algorithm mappings, service providers can extend the cryptographic algorithms for XML digital signature and XML encryption.Algorithms settings
Use this page to view the supported cryptographic and canonicalization algorithms. Algorithms are used to reconcile XML differences.Algorithm URI collection
Use this page to view a list of uniform resource identifier (URI) algorithms for XML digital signature or XML encryption that are mapped to an algorithm factory engine class. With algorithm mappings, service providers can use other cryptographic algorithms for digest value calculation, digital signature signing and verification, data encryption and decryption, and key encryption and decryption.Algorithm URI configuration settings
Use this page to specify the algorithm uniform resource identifier (URI) and its usage type.Destination defaults [Settings]
Properties to be applied when applications use destinations on this foreign bus when there is no explicit foreign destination definition.Appliance collection
Use this page to add, change, or remove a DataPower® appliance in the DataPower appliance manager. You can also use this page to view information about the DataPower appliances that are in the appliance manager. Adding appliances to a DataPower appliance manager enables you to automatically keep synchronized the settings for all of the appliances that are in a DataPower appliance manager managed set.Appliance manager settings
Use this page to specify global settings for the DataPower appliance manager. You can also use this page to shutdown the appliance manager.Appliance settings
Use this page to change the settings for a DataPower appliance. Appliances are added to the DataPower appliance manager to synchronize the firmware, shareable appliance settings and managed domains of a group of appliances called a managed set.Application binary settings
Use this page to configure the location and distribution of application binary files.Application policy sets collection
Use this page to manage policy sets. You can create, copy, export, and import policy sets. You can also view or delete existing policy sets. You can use policy sets, or assertions that define services, to simplify your web services configuration because policy sets group security and other web services settings into reusable units.Application policy set settings
Use this page to view, create, enable or disable your policy sets. You can use policies, or assertions that define services, to simplify your web services configuration.Application profile collection
Use this page to view application profiles and manage tasks associated with application profiles.Application profile settings
Use this page to modify application profile settings.Application profiling service settings
Use this page to enable or disable the application profiling service.Application resources for this destination
This pane provides an expandable tree view of all the applications and messaging resources that reference the current destination, both directly and indirectly. As many of the references as possible are resolved to links to the associated configuration panel for the referenced object.Application routing order settings
Use this page to specify whether the Default SIP Application Router (DAR) must rely on the basic application startup order or advanced application routing rules (DAR configuration).Application scoped resources
Use this page to view brief descriptions of the resources that are bundled with your application. You can view individual resource settings by clicking the resource name.Application server cluster mapping settings
You can configure settings for an application server cluster mapping. Application server cluster mappings are specified only for an application server cluster custom advisor.Application Server property settings for a web server plug-in
Use this page to view or change application server settings for a web server plug-in.Application server settings
Use this page to configure an application server or a cluster member template. An application server is a server that provides services required to run enterprise applications. A cluster member template is the set of application server configuration settings that are assigned to new members of a cluster.Application startup order settings
Use this page to define the order in which Session Initiation Protocol (SIP) requests are routed to applications.ARM application properties and transaction context data
Request metrics provides build-in instrumentation to monitor transaction flows. The data that is collected by request metrics can be sent to a supported Application Response Measurement (ARM) agent.Asset collection
Use this page to view a list of assets in the asset repository and to manage those assets. After importing an asset, you can add the asset to a business-level application.Asset settings
Use this page to specify options for the registration of an asset with the asset repository. Default values for the options are used if you do not specify a value. If the asset is an OSGi application, additional information about bundle download status is displayed.Asymmetric signature and encryption policies settings
Use this page to create the trust context, message integrity and confidentiality, to use asymmetric tokens. You can create the trust context by specifying which token type to use for the initiator and recipient signature as well as the initiator and recipient encryption.Asynchronous request dispatching settings
Use this page to enable the asynchronous request dispatcher (ARD), which enables servlets and JSP pages to make standard include calls concurrently on separate threads.Auditable security events
Auditable security events are security events that have audit instrumentation added to the security run time code to enable them to be recorded. Event filters are configured to specify which auditable security events are recorded to the audit log files.Audit encryption keystores and certificates collection
The Audit encryption keystores and certificates panel allows the auditor to manage the keystores and certificates used for audit encryption.Audit event factory configuration collection
The Audit event factory configuration page displays a list of all currently configured audit event factory implementations. This page allows a user with the auditor role to manage their configured audit event factories. This includes the ability to configure a new implementation, which is done using the New button on this page.Audit event factory settings
The Audit event factory settings page displays the details of a specific audit event factory. The auditor uses this page to manage and create audit event factory configurations.Audit monitor collection
Use this page to configure audit subsystem failure notifications. The Auditor monitor page lists the existing notification configurations and is the gateway for creating new notification configurations and for managing the existing notification configurations.Audit notification settings
Use this page to create and manage notification configurations that define how auditors are made aware of audit subsystem failures.Audit record encryption configuration settings
Use this page to enable encryption for your audit records. Encrypting your audit records ensures only a user given access to the certificate used for encryption is allowed to view the audit records.Audit record keystore settings
The Audit record keystore page is used by an auditor to define the keystores used for storing the encryption certificate used to encrypt the audit records. Keystores used for auditing are managed outside of other keystores being used on the system to facilitate separation of the authority of the auditor for the authority of the administrator.Audit record signing configuration settings
Use this page to enable signing for your audit records. Signing audit records ensures tamper-proof recording of the auditable events. Both the auditor and administrator roles are required to configure the signing of your audit data.Audit service provider collection
The Audit service provider page displays a listing of all configured audit service provider implementations. Using this page, a user can define a new audit service provider implementation, delete an existing implementation, and display or modify the fields associated with an existing implementation.Audit service provider settings
Use this page to define the implementation details of the audit service provider. There are three types of audit service providers: binary file-based, third party and SMF.Authentication cache settings
Use this page to specify your authentication cache settings.Authentication generator or consumer token settings
Authentication tokens are used to prove or assert an identity. Use the administrative console to add authentication token settings for message parts when you are editing a general binding.Authentication protocol settings for a client configuration
You can use settings in the sas.client.props file to configure Security Authentication Service (SAS) and Common Secure Interoperability Version 2 (CSIv2) clients.Authentication protocol support
Use this page to reference information regarding supported authentication protocols.Available resources
Use this page to select configured resources that you want to bind to the resource references of the enterprise beans or web modules in your application.Backup cluster settings
Use this page to configure a backup server cluster. The backup server cluster is used if the primary server cluster fails.Bidirectional support options
Use the Bidirectional support options page to specify bidirectional (Bidi) text preferences for the administrative console.Bind EJB business settings
Use this administrative console page to specify Java Naming and Directory (JNDI) name bindings for each enterprise bean with a business interface in an EJB module. Each enterprise bean with a business interface in an EJB module must be bound to a JNDI name. For any business interface that does not provide a JNDI name, or if its bean does not provide a JNDI name, a default binding name is provided. If its bean provides a JNDI name, the default JNDI name for the business interface is provided in addition to it's bean JNDI name by appending the package-qualified class name of the interface.Bind listeners for message-driven beans settings
Use this page to specify bindings for message-driven beans in your application or module.Bootstrap address collection
Use this page to manage bootstrap addresses for a foreign cell binding. Multiple bootstrap addresses can enhance the failover support provided by clusters.Bootstrap address settings
Use this page to specify one or more bootstrap addresses for a foreign cell binding. Multiple bootstrap addresses can enhance the failover support provided by clusters.Bootstrap members [Collection]
Bus members, servers and clusters that client applications can target to bootstrap into the given bus.Bridge interface collection
Each core group access point has a collection of bridge interfaces. This collection defines the interfaces on the set of servers that provide access to the core group. All the servers in this collection have the core group bridge service enabled.Bridge interface creation
A bridge interface specifies a particular node and server that runs the core group bridge service. A bridge interface is defined by a unique combination of a node, a server, and a transport chain. A transport chain represents a network protocol stack that is operating within an application server.Bridge interface settings
Use this page to specify the bridge interfaces that provide access to the core group access point. A bridge interface is a server that runs the core group bridge service. The core group bridge service is the service that establishes communication between core groups.Broker profile subscriptions [Collection]
The list of current broker subscriptions for this broker profile.Buses [Collection]
A service integration bus supports applications using message-based and service-oriented architectures. A bus is a group of interconnected servers and clusters that have been added as members of the bus. Applications connect to a bus at one of the messaging engines associated with its bus members.Buses [Settings]
A service integration bus supports applications using message-based and service-oriented architectures. A bus is a group of interconnected servers and clusters that have been added as members of the bus. Applications connect to a bus at one of the messaging engines associated with its bus members.Business-level application collection
Use this page to view and manage business-level applications.Business-level application settings
Use this page to configure a business-level application.Bus members [Collection]
Bus members are the servers, IBM MQ servers and clusters that have been added to the bus.Bus members [Settings]
Bus members are the servers, IBM MQ servers and clusters that have been added to the bus.Caching action settings
You can configure caching action settings for a proxy server. Caching actions are set to determine whether a response is cached. A caching action specifies the last modified factor and the default expiration to define how a response is cached.Callback handler configuration settings for JAX-RPC
Use this page to specify how to acquire the security token that is inserted in the Web Services Security header for JAX-RPC within the SOAP message. The token acquisition is a pluggable framework that leverages the Java Authentication and Authorization Service (JAAS) javax.security.auth.callback.CallbackHandler interface for acquiring the security token.Callback handler settings for JAX-WS
Use this page to configure callback handler settings for JAX-WS, which determine how security tokens are acquired from messages headers.Caller [Collection]
Specifies the security token, signed part or encrypted part used for authentication. If a signed or encrypted part is used, the value of the part attribute must be the name of a defined required integrity or required confidentiality constraint. If a stand-alone security token is used for authentication, then the URI and local name attributes must define the type of security token used for authentication.Caller [Collection]
Specifies the security token, signed part or encrypted part used for authentication. If a signed or encrypted part is used, the value of the part attribute must be the name of a defined required integrity or required confidentiality constraint. If a stand-alone security token is used for authentication, then the URI and local name attributes must define the type of security token used for authentication.Caller [Settings]
Specifies the security token, signed part or encrypted part used for authentication. If a signed or encrypted part is used, the value of the part attribute must be the name of a defined required integrity or required confidentiality constraint. If a stand-alone security token is used for authentication, then the URI and local name attributes must define the type of security token used for authentication.Caller [Settings]
Specifies the security token, signed part or encrypted part used for authentication. If a signed or encrypted part is used, the value of the part attribute must be the name of a defined required integrity or required confidentiality constraint. If a stand-alone security token is used for authentication, then the URI and local name attributes must define the type of security token used for authentication.Caller collection
The caller specifies the token or message part that you want to use for authentication. Use this administrative console page to access, view and configure the caller settings for message parts.Caller settings
Use this page to configure the caller settings. The caller specifies the token or message part that is used for authentication.Cell custom properties
You can configure name-value pairs of data, where the name is a property key and the value is a string value that you can use to set configuration properties for a cell. Defining a new custom property for a cell enables you to configure a setting beyond that which is available in the administrative console. This topic lists custom properties that are available to configure a cell.Cell settings for deployment managers
Use this page to set the discovery protocol and address end point for an existing cell. A cell is a configuration concept, a way for an administrator to logically associate nodes according to whatever criteria make sense in the administrator's organizational environment.Certificate authority (CA) client configuration
Use this page to create, modify, and configure a certificate authority (CA) client.Certificate authority (CA) client configuration collections
Use this page to define and manage certificate authority (CA) clients or view and modify existing CA clients.Certificate request settings
Use this page to verify the properties of a personal certificate request.Certificate revocation list collection
Use this page to determine the location of the certificate revocation list (CRL) known to the application server. The Application Server checks the CRL to determine the validity of the client certificate. A certificate that is found in a certificate revocation list might not be expired, but is no longer trusted by the certificate authority (CA) that issued the certificate. The CA might add the certificate to the certificate revocation list if it believes that the client authority is compromised.Certificate revocation list configuration settings
Use this page to specify a list of certificate revocations that check the validity of a certificate. The application server checks the certificate revocation lists (CRL) to determine the validity of the client certificate. A certificate that is found in a certificate revocation list might not be expired, but is no longer trusted by the certificate authority (CA) that issued the certificate. The CA might add the certificate to the certificate revocation list if it believes that the client authority is compromised.Certificate store settings
Use this page to specify the location where certificates are stored. You can reference certificate revocation for service generators or consumers.Change log and trace mode settings
Use this page to choose the mode your system uses for logging and tracing.Change state specification
Use this panel to add a Diagnostic Provider and its attributes to the specification for collecting state data.Checkpoint settings
Use this page to view configurations of a checkpoint. Repository checkpoints represent saved images of the repository before configuration changes are made. Checkpoints can be either full or delta images.Class loader collection
Use this page to manage class-loader instances on an application server. A class loader determines whether an application class loader or a parent class loader finds and loads Java class files for an application.Class loader settings
Use this page to configure a class loader for applications that reside on an application server.Class loader viewer service settings
Use this page to configure the server to start the class loader viewer service when the server starts. The Class Loader Viewer helps you diagnose problems with class loaders.Class loader viewer settings
Use this page to examine the class loaders visible to a web module (.war file) or enterprise bean (.ejb file) in an installed enterprise application. This page helps you to determine which class loaders loaded files of a module and to diagnose problems with class loaders.Class loading and update detection settings
Use this page to configure use of class loaders by an application.Client connections [Collection]
The connection between a IBM MQ client and the bus.Client module property settings
Use this page to configure the deployment mode of a deployed client module.Client module settings
Use this page to configure a deployed client module.Cluster member collection
Use this page to view and manage application servers that belong to a cluster. You can also use this page to change the weight of any of the listed application servers.Cluster member settings
Use this page to manage the members of a cluster. A cluster of application servers are managed together and participate in workload management.Cluster member templates collection
Use this page to view the list of cluster member templates that exist for this cluster. To edit the server properties of a template, click the name of that template.Cluster topology
Use this page to display, in a tree format, a list of all of the application server clusters defined for your WebSphere Application Server environment. The list shows all of the nodes and cluster members that are included in each cluster contained in a cell.CMP connection factories collection
Use this page to view existing container managed persistence (CMP) connection factories settings.CMP connection factory settings
Use this page to view the settings of a connection factory that is used by a container-managed persistence (CMP) bean to access any database server. Because the connection factory is created and managed automatically, the settings of the connection factory cannot be modified.Collection certificate store collection
Use this page to view a list of certificate stores that contains untrusted, intermediary certificate files awaiting validation. Validation might consist of checking to see if the certificate is on a certificate revocation list (CRL), checking that the certificate is not expired, and checking that the certificate is issued by a trusted signer.Collection certificate store configuration settings
Use this page to specify the name and the provider for a collection certificate store. A collection certificate store is a collection of non-root, certificate authority (CA) certificates and certificate revocation lists (CRLs). This collection of CA certificates and CRLs is used to check the signature of a digitally signed SOAP message.Common Secure Interoperability Version 2 and Security Authentication Service (SAS) client configuration
A secure Java client requires configuration properties to determine how to perform security with a server.Common Secure Interoperability Version 2 inbound communications settings
Use this page to specify the features that a server supports for a client accessing its resources.Common Secure Interoperability Version 2 outbound communications settings
Use this page to specify the features that a server supports when acting as a client to another downstream server.Compensation service settings
Use this page to manage the compensation service. The compensation service supports server-level configuration for compensation enablement and logging.Composition unit settings
Use this page to view composition unit settings and to change the configuration properties of a composition unit. The specific settings that are available for configuration can vary, depending upon the contents of the composition unit. For example, there are additional configuration settings if the asset contained in the composition uni is an OSGi application.Confidentiality [Collection]
Specifies the confidentiality constraints applied to generated messages. This includes specifying which message parts within the generated message must be encrypted, and the message parts to attach encrypted Nonce and time stamp elements to.Confidentiality [Collection]
Specifies the confidentiality constraints applied to generated messages. This includes specifying which message parts within the generated message must be encrypted, and the message parts to attach encrypted Nonce and time stamp elements to.Confidentiality [Settings]
Specifies the confidentiality constraints applied to sent messages. Indicates which parts of the message will be encrypted.Confidentiality [Settings]
Specifies the confidentiality constraints applied to generated messages. This includes specifying which message parts within the generated message must be encrypted, and the message parts to attach encrypted Nonce and time stamp elements to.Confidentiality [Settings]
Specifies the confidentiality constraints applied to generated messages. This includes specifying which message parts within the generated message must be encrypted, and the message parts to attach encrypted Nonce and time stamp elements to.Configuration data
Use this panel to view the current configuration data for a Diagnostic Provider on a selected server or cluster. Not necessarily every piece of configuration data appears, but data that can be helpful in problem determination is shown.Configuration data quick link or server selection
Use this panel to select a Diagnostic Provider server for viewing run time configuration data.Configuration document descriptions
Most configuration documents have XML content. The table describes the documents and states whether you can edit them using an administrative tool or must edit them directly.Configuration entry settings for Java Authentication and Authorization Service
Use this page to specify a list of Java Authentication and Authorization Service (JAAS) login configurations for the application code to use, including Java Platform, Enterprise Edition (Java EE) components such as enterprise beans, JavaServer Pages (JSP) files, servlets, resource adapters, and message-driven beans (MDBs).Configuration problem settings
Use this page to identify and view problems that exist in the current configuration.Configure security domains
Use this page to configure the security attributes of a domain and to assign the domain to cell resources. For each security attribute, you can use the global security settings or customize settings for the domain.Configuring new connection factories for resource adapters for the client
Use the Application Client Resource Configuration Tool (ACRCT) to configure new connection factories for resource adapters for the client.Connection factory collection
A JMS connection factory is used to create connections to the associated messaging provider of JMS destinations, for both point-to-point and publish/subscribe messaging. Use connection factory administrative objects to manage JMS connection factories for the default messaging provider, the WebSphere MQ messaging provider or a third-party messaging provider.Connection factory JNDI name practices
Observe the conventions of the Java Naming and Directory Interface (JNDI) service in WebSphere Application Server when you create connection factory JNDI names.Connection pool (Version 4) settings (deprecated)
Use this page to create a connection pool for a Version 4.0 data source.Connection pool advanced settings
Use this page to specify connection pooling related settings.Connection pool settings
Use this page to configure connection pool settings.Connection Properties [Collection]
Connection properties define the manner in which an endpoint listener connects to the service integration bus.Connection Properties [Settings]
Connection properties define the manner in which an endpoint listener connects to the service integration bus.Console accessibility
There are many accessibility features built into Integrated Solutions Console.Console identity
Use Console Identity to define a string (keyword, name, or phrase) to be displayed in the console banner. This string can be used to distinguish this console from other console instances.Console layout
This topic describes the layout of the user interface for Integrated Solutions Console.Console navigation
This topic describes how to navigate pages and tasks in the Integrated Solutions Console.Console preferences settings
Use the Console Preferences page to specify how you want features of the administrative console workspace to behave.Context object fields
Each auditable event has an associated set of information that is available for logging. This information is grouped into specific context objects. The context objects that are available for logging a specific event are specified by the event type. This topic details the information that exists for each context object and specifies whether the information is logged by default or is only logged when the verbose logging option is enabled.Context objects for security auditing
Each event has an associated set of information that is available for logging. This information is grouped into specific context objects. The context objects that are available for logging a specific event are specified by the event type. All event types have the sessionContextObj, eventContextObj, accessContextObj, propogationContextObj, processContextObj and registryContextObj objects. This topic specifies which additional context objects are available for each event type.Context properties [Collection]
Context information used to enable correct processing of messages. This information adds to the context information derived from processing the message header.Context properties [Settings]
Context information used to enable correct processing of messages. This information adds to the context information derived from processing the message header.Context root for web modules settings
Use this page to specify the context root for web modules during or after installation of an application onto a WebSphere Application Server deployment target.Convert certificates
Use this page to convert certificates to the selected security standard. All certificates in keystores associated with an Secure Socket Layer (SSL) configuration are converted.Cookie settings
Use this page to configure cookie settings for session management.Copy of default policy set and bindings settings
Use this page to copy a policy set that you select from a list of available policy sets.Copy policy set binding settings
Use this page to view and copy general policy set bindings for either a single security or a multiple security domain environment.CORBA object binding settings
Use this page to configure a new name binding of a CORBA object binding, or to view or edit an existing CORBA object binding.Core group access point collection
Use this page to configure your set of core group access points. Core group access points define the set of servers that provide access to the core group. At least one core group access point must be defined for each core group in the local cell.Core group access point settings
Use this page to configure your core group access points. The core group access point defines the set of core group bridge servers that provide access to the core group. A core group bridge server is an application server that is configured to run the core group bridge service. Each core group access point has a collection of bridge interfaces. See Bridge interface settings for more information about bridge interfaces.Core group bridge custom properties
Use these custom properties for advanced configurations for core groups and core groups that communicate with the core group bridge.Core group bridge settings
The core group bridge is the service that enables communication between core groups. A core group is a statically defined component of the high availability manager. Use this page to view the structure of your access point groups and tunnel access point groups.Core group collection
Use this page to view the core groups that are defined for your system. A core group is a component of the high availability manager function. A default core group, called DefaultCoreGroup, is created for each cell in the product environment. A core group can contain stand-alone servers, cluster members, node agents and the deployment manager. A core group must contain at least one node agent or the deployment manager.Core group custom properties
Use these custom properties for advanced configurations for core groups.Core group policies
Use this page to create or update the various high availability group policies. For a given high availability group, the associated policy determines which members of the group should be made active.Core group policy settings
Use this page to define a policy for a high availability group. A policy is defined at the core group level. It only applies to matching high availability groups contained within this core groupCore group server move options
Use this page to move one or more core group servers to a different core group. You must stop a core group server before you move it.Core group servers collection
Use this page to view a list of the servers that are part of a core group. A core group server can be an application server, a deployment manager, or a node agent that is a member of a high availability core group. Use this page to move servers into a different core group. All members of a cluster must be in the same core group. If you select one or more members of a cluster, all of the members of that cluster must be moved.Core group server settings
Use this page to view the servers that are part of a core group and to define or edit custom properties for a core group server.Core group service settings
Use this page to set up the application server properties that relate to core groups.Core group settings
Use this page to create a core group or to edit an existing core group. A core group is a component of the high availability manager function. It can contain stand-alone servers, cluster members, node agents, administrative agents, and the deployment manager.Correct use of the system identity
Use this page to manage the system identity properties for the Enterprise JavaBeans (EJB) method in your application.Create a schedule
Use the wizard to create a schedule of events that occur for a job.Create UDDI Publishers
Use this page to register one or more existing WebSphere Application Server users as UDDI publishers.Creating a cluster: Basic cluster settings
Use this page to enter the basic settings for a cluster.Creating a cluster: Create additional cluster members
Use this page to create additional members for a cluster. You can add a member to a cluster when you create the cluster or after you create the cluster. A copy of the first cluster member that you create is stored as part of the cluster data and becomes the template for all additional cluster members that you create.Creating a cluster: Create first cluster member
Use this page to specify settings for the first cluster member.Creating a cluster: Summary settings
Use this administrative console page to view and save settings when you create a cluster or cluster member.Creating a proxy cluster: Basic proxy cluster settings
Use this page to enter the basic settings for a proxy cluster.Creating a proxy cluster: Create additional proxy cluster members
Use this page to create additional members for a proxy cluster. You can add a member to a proxy cluster when you create the proxy cluster or after you create the proxy cluster. A copy of the first proxy cluster member that you create is stored as part of the proxy cluster data and becomes the template for all additional proxy cluster members that you create.Creating a proxy cluster: Create first proxy cluster member
Use this page to specify settings for the first proxy cluster member.Creating a proxy cluster: Summary settings
Use this administrative console page to view and save settings when you create a proxy cluster or proxy cluster member.Creating new or configuring existing general binding settings
Use this page to create a new client or provider policy set binding. You can also use this page to configure an existing general binding. Empty bindings will be deleted. Scoping a binding to a security domain constrains the configuration options to those applicable to that domain and limits use of the binding to the specified domain.Custom advisor policy settings
You can configure settings for a custom advisor policy. Custom advisor policies allow for more specific determination of target application server availability by sending protocol level requests to back-end servers. Custom advisor policies are unique based on the combination of the business-level application ID and the composition unit ID.Custom advisors collection
Use this page to administer custom adviser policies. With custom advisors, you can determine the availability of a specific target application server by sending protocol level requests to back-end servers. Custom advisor policies are unique based on the combination of the business-level application ID and the composition unit ID.Custom authentication methods [Collection]
Specifies custom authentication methods this service will accept.Custom authentication methods [Settings]
Specifies custom authentication methods this service will accept.Custom finder SQL dynamic enhancement properties
Use this page to modify custom finder SQL dynamic enhancement properties settings.Custom keystore settings
Use this page to configure custom keystore files. Custom keystore files are alternatives to the key management support built into the WebSphere Application Server. The callback handler uses the custom version of the keystore configuration that includes keys.Custom monitoring level
Use this page to enable and disable specific PMI counters for individual PMI statistics.Custom object pool collection
An object pool manages a pool of arbitrary objects and helps applications avoid creating new Java objects repeatedly. Most objects can be created once, used and then reused. An object pool supports the pooling of objects waiting to be reused. These object pools are not meant to be used for pooling Java Database Connectivity connections or Java Message Service (JMS) connections and sessions. WebSphere Application Server provides specialized mechanisms for dealing with those types of objects. These object pools are intended for pooling application-defined objects or basic Developer Kit types.Custom object pool settings
An object pool manages a pool of arbitrary objects and helps applications avoid creating new Java objects repeatedly. Most objects can be created once, used and then reused. An object pool supports the pooling of objects waiting to be reused. These object pools are not meant to be used for pooling Java Database Connectivity connections or Java Message Service (JMS) connections and sessions. WebSphere Application Server provides specialized mechanisms for dealing with those types of objects. These object pools are intended for pooling application-defined objects or basic Developer Kit types.Custom Properties (Version 4) collection (deprecated)
Use this page to view properties for a WebSphere Application Server Version 4.0 data source.Custom properties [Collection]
Use this page to specify an arbitrary name and value pair. The value that is specified for the name and value pair is a string that can set internal system configuration properties.Custom properties [Collection]
Use this page to specify an arbitrary name and value pair. The value that is specified for the name and value pair is a string that can set internal system configuration properties.Custom properties [Settings]
Arbitrary name-value pairs of data, where the name is a property key and the value is a string value that can be used to set internal system configuration properties. Defining a new property enables you to configure a setting beyond that which is available in the administrative console.Custom property (Version 4) settings (deprecated)
Use this page to add properties for a WebSphere Application Server Version 4.0 data source.Custom property collection
Use this page to view and manage arbitrary name-value pairs of data, where the name is a property key and the value is a string value that can be used to set internal system configuration properties.Custom property collection for the job scheduler
Use this page to view and manage arbitrary name-value pairs of data, where the name is a property key and the value is a string value that is used to set internal system configuration properties.Custom property settings
Use this page to specify the attributes of custom properties that might be required for resource providers and resource factories.Custom property settings
Use this page to configure arbitrary name-value pairs of data, where the name is a property key and the value is a string value that can be used to set internal system configuration properties. Defining a new property enables you to configure a setting beyond that which is available in the administrative console.Custom property settings for the job scheduler
Use this page to configure arbitrary name-value pairs of data, where the name is a property key and the value is a string value that can be used to set internal system configuration properties. You can define a new property to configure a setting beyond what is available in the administrative console.Custom repository details for federated repositories
Use this panel to specify the configuration for access to a custom repository.Custom service collection
Use this page to view a list of services available to the application server and to see whether the services are enabled. A custom service provides the ability to plug into an application server and define code that runs when the server starts or shuts down.Custom service settings
Use this page to configure a service that runs in an application server.Data access tuning parameters
For better application performance, you can tune some data access resources through the WebSphere Application Server administrative console.Database settings
Use this page to specify the settings for database session support.DataPower appliance manager tasks collection
Use this page to view the status of a task. A task is a long running request that you have asked the DataPower appliance manager to process. You can remove a task from the list of pending tasks. However, removing a task from that list does not prevent that task from running.DataPower appliance manager transport channel settings
Use this page to view and configure a DataPower appliance manager transport channel. This type of transport channel handles events from managed DataPower appliances.Data replication domain settings
Use this page to configure a data replication domain. Use data replication domains to transfer data, objects, or events for session manager, dynamic cache, or stateful session beans among the application servers in a cluster.Data source (WebSphere Application Server V4) collection (deprecated)
Use this page to view the settings of a WebSphere Application Server Version 4.0 data source (deprecated).Data source (WebSphere Application Server Version 4) settings (deprecated)
Use this page to create a Version 4.0 style data source. This data source uses the WebSphere Application Server Version 4.0 connection manager architecture. All Enterprise JavaBeans (EJB) 1.x modules must use a Version 4.0 data source.Data source collection
Use this page to view configured data sources, which are the resources that provide connections to your relational database.Data source minimum required settings, by vendor
These properties vary according to the database vendor requirements for Java Database Connectivity (JDBC) driver implementations. You must set the appropriate properties on every data source that you configure.Data source minimum required settings for Apache Derby
These properties vary according to the database vendor requirements for JDBC driver implementations. You must set the appropriate properties on every data source that you configure. These settings are for Apache Derby data sources.Data source minimum required settings for DB2 on z/OS and an application server on z/OS
These properties vary according to the database vendor requirements for JDBC driver implementations. You must set the appropriate properties on every data source that you configure. These settings are for a DB2® data source that is running on z/OS® and will be accessed by applications in an application server that is also running on z/OS.Data source minimum required settings for DB2 Universal Database for IBM i
These properties vary according to the database vendor requirements for JDBC driver implementations. You must set the appropriate properties on every data source that you configure. These settings are for a DB2 UDB data source.Data source minimum required settings for DB2 with the application server on AIX, HP-UX, Linux, Solaris, or Windows
These properties vary according to the database vendor requirements for JDBC driver implementations. You must set the appropriate properties on every data source that you configure. These settings are for a DB2 data source that is connecting to an application server that is running on AIX®, HP-UX, Linux, Solaris, or Windows systems.Data source minimum required settings for Informix
These properties vary according to the database vendor requirements for JDBC driver implementations. You must set the appropriate properties on every data source that you configure. These settings are for Informix® data sources.Data source minimum required settings for Microsoft SQL Server
These properties vary according to the database vendor requirements for Java Database Connectivity (JDBC) driver implementations. You must set the appropriate properties on every data source that you configure. These settings are for Microsoft SQL Server data sources.Data source minimum required settings for Oracle
These properties vary according to the database vendor requirements for JDBC driver implementations. You must set the appropriate properties on every data source that you configure. These settings are for Oracle data sources.Data source minimum required settings for Sybase
These properties vary according to the database vendor requirements for JDBC driver implementations. You must set the appropriate properties on every data source that you configure. These settings are for Sybase data sources.Data source properties for application clients
Use this page to create or modify the data sources.Data source provider settings for application clients
Use this page to create a data source under a JDBC provider which provides the specific JDBC driver implementation class.Data source settings
Use this page to edit the properties of a data source.Data store [Settings]
The persistent store for messages and other state managed by the messaging engine.DB2 tuning parameters
Read this topic for parameters that you can configure for better database performance.DCS transport channel settings
Use this page to view and configure an DCS transport channels. This type of transport channel handles inbound Distribution and Consistency Services (DCS) messages.Debugging Service details
Use this page to view and modify the settings used by the Debugging Service.Default access roles [Settings]
This pane shows the role type assignments for the default access.Default application router rule collection
Use this page to view or modify default application router (DAR) routing rules or import a new DAR configuration file. The DAR is a Session Initiation Protocol (SIP) application router that you can use to select the order in which SIP applications are triggered.Default application router rule settings
Use this page to edit the details of an application router rule.Default bindings and runtime properties for Web Services Security
Use this page to configure the settings for nonce on the server level and to manage the default bindings for the signing information, encryption information, key information, token generators, token consumers, key locators, collection certificate store, trust anchors, trusted ID evaluators, algorithm mappings, and login mappings.Default bindings and security runtime properties
Use this page to specify the configuration on the cell level in a WebSphere Application Server, Network Deployment environment. In addition, use this page to define the default generator bindings, default consumer bindings, and additional properties such as key locators, the collection certificate store, trust anchors, trusted ID evaluators, algorithm mappings, and login mappings.Default Java Persistence API settings
To increase the portability of your applications, use this page to configure the default Java Persistence API (JPA) settings for applications running on this server instead of defining the <provider> element in each persistence unit in your applications.Default messaging provider [Settings]
A JMS provider enables messaging based on the Java Messaging Service (JMS). It provides Java EE connection factories to create connections for JMS destinations. This panel is used to manage the default messaging provider and its JMS resources.Default messaging provider queue [Settings]
A JMS queue is used as a destination for point-to-point messaging. Use JMS queue destination administrative objects to manage JMS queues for the default messaging provider.Default messaging provider queue connection factory [Settings]
A JMS queue connection factory is used to create connections to the associated JMS provider of JMS queues, for point-to-point messaging. Use queue connection factory administrative objects to manage JMS queue connection factories for the default messaging provider.Default messaging provider topic [Settings]
A JMS topic is used as a destination for publish/subscribe messaging. Use topic destination administrative objects to manage JMS topics for the default messaging provider.Default messaging provider topic connection factory [Settings]
A JMS topic connection factory is used to create connections to the associated JMS provider of JMS topics, for publish/subscribe messaging. Use topic connection factory administrative objects to manage JMS topic connection factories for the default messaging provider.Default messaging provider unified connection factory [Settings]
A JMS connection factory is used to create connections to the associated JMS provider of JMS destinations, for both point-to-point and publish/subscribe messaging. Use connection factory administrative objects to manage JMS connection factories for the default messaging provider.Default policy set bindings collection
Use this page to specify the service provider and client default bindings. The specified service provider and client bindings are used at the cell (global security) level unless these specified bindings are overridden at the attachment point, at the server, or at a security domain.Default Provider connection factory settings
Use this panel to view or change the configuration properties of the selected JMS connection factory for use with the internal product Java Message Service (JMS) provider that is installed with WebSphere Application Server. These configuration properties control how connections are created between the JMS provider and the service integration bus that it usesDefault Provider queue connection factory settings
Use this panel to view or change the configuration properties of the selected JMS queue connection factory for use with the internal product Java Message Service (JMS) provider that is installed with WebSphere Application Server. These configuration properties control how connections are created between the JMS provider and the service integration bus that it usesDefault Provider queue destination settings
Use this panel to view or change the configuration properties of the selected JMS queue destination for use with the internal product Java Message Service (JMS) provider that is installed with WebSphere Application Server.Default Provider topic connection factory settings
Use this panel to view or change the configuration properties of the selected JMS topic connection factory for use with the internal product Java Message Service (JMS) provider that is installed with WebSphere Application Server. These configuration properties control how connections are created between the JMS provider and the service integration bus that it uses.Default Provider topic destination settings
Use this panel to view or change the configuration properties of the selected JMS topic destination for use with the internal product Java Message Service (JMS) provider that is installed with WebSphere Application Server.Denial of service protection settings
Use these settings to define denial of service protection for the proxy server. The buffer chunk sizes are used to provide protection against denial of service attacks. It is very important to tune these settings to balance the level of protection with the performance impacts that can be experienced.Deploying JavaServer Pages and JavaServer Faces files
Deployment manager settings
Use this page to stop the deployment manager, and to link to other pages that you can use to define additional properties for the deployment manager. A deployment manager provides a single, central point of administrative control for all of the elements in the WebSphere Application Server distributed cell.Destination defaults [Settings]
Properties to be applied when applications use destinations on this foreign bus when there is no explicit foreign destination definition.Destinations [Collection]
A bus destination is defined on a service integration bus, and is hosted by one or more locations within the bus. Applications can attach to the destination as producers, consumers, or both to exchange messages.Destinations access roles [Collection]
This pane displays a list of all destinations known by the bus: aliases, foreign destinations, ports, queues, temporary destination prefixes, topic spaces and web services.Destinations access roles [Settings]
This pane displays the role type assignments for the selected destinations.Detailed state specification
Use this panel to view the attributes and descriptions of the Diagnostic Provider that you have selected.Diagnostic Providers (selection)
Use this panel to select a Diagnostic Provider from the selected server or cluster.Diagnostic Provider XML example
Here is an example of the Diagnostic Provider Extensible Markup Language (XML).Diagnostic trace service settings
Use this page to configure diagnostic trace service settings.Discovery and failure detection settings
Use this page to configure the discovery and failure detection settings for a core group. These settings are used to monitor the health of core group members. The discovery protocol establishes network connectivity between core group members of the core group. The failure detection protocol monitors the established network connections. Both the default discovery protocol and the default failure protocol run at regularly scheduled intervals on all started core group members.Display module build ID settings
Use this page to view the build identifier of a module in a Java Platform, Enterprise Edition (Java EE) enterprise archive (EAR file). The build identifier for a module is shown if the MANIFEST.MF file of a module or application specifies a build identifier.Distributed environment settings
Use this page to specify a type for saving a session in a distributed environment.Distributed identity filters configuration in z/OS security
Before you can map distributed identities to System Authorization Facility (SAF) users, you must first configure distributed identity filters in the z/OS security product for WebSphere Application Server.Domain bootstrap address settings
Use this page to specify the bootstrap address host and port of the deployment manager that contains the backup cluster. You must specify a value for the Host and Port fields and configure a core group bridge before you can use the backup cluster function.Domain default bindings settings
Use this page to specify the default policy set bindings for this security domain.Domain history collection
Use this page to view the domain history for DataPower appliance manager. A domain version is an automatically generated copy of a managed domain.Domain history detailed information
Use this page to view detailed information about a specific domain version for a managed domain in a managed set. A domain version is an automatically generated copy of an existing domain.Download SQLJ profile group
Use this page to download the group file for the Structured Query Language in Java (SQLJ) profiles that are bound together as a single package on the DB2 database server. You can use the file when performing future customization or binding work on the application. Click the link that is provided to download the profile group to your local file system. The group file has a filename extension of .grp and a HTTP Content-Type of text/plain. Your web browser settings might cause the browser to display the file contents rather than prompting you for a download destination. If this happens, you can manually copy and paste the contents into your own .grp file.Dynamic cache MBean statistics
The dynamic cache service provides an MBean interface to access cache statistics.Dynamic cache PMI counter definitions
The dynamic cache statistics interface is defined as WSDynamicCacheStats under the com\ibm\websphere\pmi\stat package.Dynamic cache service settings
Use this page to configure and manage the dynamic cache service settings.Dynamic inbound and outbound endpoint SSL configurations collection
Use this page to manage dynamic endpoint Secure Sockets Layer (SSL) configurations, which represent associations between Secure Socket Layer (SSL) configurations and their target protocol, host, and port.Dynamic member attributes collection
Use this page to manage Lightweight Directory Access Protocol (LDAP) dynamic member attributes.Dynamic member attributes settings
Use this page to configure Lightweight Directory Access Protocol (LDAP) dynamic member attributes.Dynamic outbound endpoint SSL configuration settings
Use this page to set properties for dynamic outbound endpoint SSL configurations, which represent associations between SSL configurations and their target protocol, host, and port.Dynamic role caching properties
The dynamic role cache holds role memberships that expire.Edge cache statistics
Cache monitor provides a view of the edge cache statistics.Edit membership for a managed set
Use this page to add appliances to the managed set, remove appliances from the managed set, or mark an appliance as the master appliance for the managed set. All of the appliances in a managed set must have the same appliance type, model type and licensed features.EJB asynchronous methods settings
Use this page to modify settings on the work manager used in support of Enterprise JavaBeans asynchronous methods.EJB binding settings
Use this page to configure a new enterprise bean (EJB) binding, or to view or edit an existing EJB binding.EJB cache settings
Use this page to configure and manage the cache for a specific Enterprise JavaBeans (EJB) container. To avoid errors from attempting to overload the cache, determine the cache absolute limit. Multiply the number of enterprise beans active in any given transaction by the total number of concurrent transactions expected. Then, add the number of active session bean instances. This value is the limit that the cache will hold.EJB container settings
Use this page to configure and manage the EJB container of this application server.EJB container system properties
In addition to the specific EJB container settings that are accessible from the administrative console, you can set EJB system properties as Java virtual machine (JVM) custom properties.EJB endpoint URL syntax
An Enterprise JavaBeans (EJB) endpoint URL is used to access a web service with the EJB Remote Method Invocation over Internet Inter-ORB Protocol (RMI-IIOP) transport. The URL specifies the EJB endpoint, including the EJB home class, the EJB Java Naming and Directory Interface (JNDI) name, and optional properties.EJB JNDI names for beans
Use this page to view and modify the Java Naming and Directory Interface (JNDI) names of non-message-driven enterprise beans in your application or module.EJB module settings
Use this page to configure and manage a specific deployed EJB module.EJB references
Use this page to view and modify the Enterprise JavaBeans (EJB) references to the enterprise beans. References are logical names used to locate external resources for enterprise applications. References are defined in the application's deployment descriptor file. At deployment, the references are bound to the physical location (global Java Naming and Directory Interface (JNDI) name) of the resource in the target operational environment.EJB timer service settings
Use this page to configure and manage the Enterprise JavaBeans (EJB) timer service for a specific EJB container.Enabling secure hashing
By default, secure hashing is set to false. Enabling secure hashing might have a minor affect on performance.Encrypted message part settings
Use this page to define the elements of an encrypted part of a message. Encrypted parts are used to protect message confidentiality, and in this case, the encrypted parts are being defined as part of the policy set process. A message part is a named set of one or more message elements.Encryption information collection
Use this page to specify the configuration for the encrypting and decrypting parameters. This configuration is used to encrypt and decrypt parts of the message, including the body and user name token.Encryption information configuration settings: Message parts
Use this page to configure the encryption and decryption parameters. You can use these parameters to encrypt and decrypt various parts of the message, including the body and the token.Encryption information configuration settings: Methods
Use this page to configure the encryption and decryption parameters for the signature method, digest method, and canonicalization method.Endpoint listeners [Collection]
An endpoint listener receives requests from service requester applications within a specific application server or cluster.Endpoint listeners [Settings]
An endpoint listener receives requests from service requester applications within a specific application server or cluster.Ensure all unprotected 1.x methods have the correct level of protection
Use this page to verify that the unprotected Enterprise JavaBeans (EJB) Version 1.x methods have the correct level of protection before you map users to roles.Ensure all unprotected 2.x methods have the correct level of protection
Use this page to verify that the unprotected Enterprise JavaBeans (EJB) Version 2.x methods have the correct level of protection before you map users to roles.Enterprise application collection
Use this page to view and manage enterprise applications.Enterprise application settings
Use this page to configure an enterprise application.Enterprise application topology
Use this page to see where modules reside in a topology of enterprise applications. Knowing where a module resides helps you to determine which class loader loaded a module and to diagnose problems with class loaders.Entry mapping repository settings
Use this page to configure an entry mapping repository that is used to store data for managing profiles on multiple repositories.Environment entries collection
Use this page to view and manage arbitrary name-value pairs of data, where the name is a environment entry key and the value is a string value that can be used to set internal system configuration environment entries.Environment entries for application settings
Use this page to configure the environment entries of applications that are deployed as enterprise archive (EAR) files.Environment entries for client modules settings
Use this page to configure the environment entries of application client modules that are deployed as Java archive (JAR) files.Environment entries for EJB modules settings
Use this page to configure the environment entries of Enterprise JavaBeans (EJB) modules such as entity, session, or message driven beans.Environment entries for web modules settings
Use this page to configure the environment entries of Web modules such as servlets and JavaServer Pages (JSP) files.Environment entries settings
Use this page to configure arbitrary name-value pairs of data, where the name is an environment entry key and the value is a string value that can be used to set internal system configuration environment entries. Defining a new environment entry enables you to configure a setting beyond that which is available in the administrative console.Event type filters collection
The Event type filters page displays a listing of all configured audit specifications with their unique names, the state of their enablement, and the event types and event outcomes that are specified for each configuration.Event type filter settings
The Event type filter settings page is used by an auditor to manage and create event type filters. Default event type filters have been included, this panel allows additional event type filters to be added. Existing event type filters are also managed using this page.Export certificate to a keystore file or a managed keystore
Use this page to specify a personal certificate to export to a keystore file or a managed keystore.Export messages settings
Export the messages from the selected sequences to ZIP files.Export policy sets bindings settings
This task only applies to general client or provider bindings. Use this page to export either a client or provider policy set binding for reuse.Extended data source properties
Use this page to set the extended data source properties for a DB2 database. You can use these properties to allow an application to extend the custom properties for a data source or override any non-core properties that already exist for that data source.Extended repository service settings
Use this page to configure the repository checkpoint location and to enable automatic checkpoints. The extended repository service enables you to back up and restore the configuration repository. The configuration repository contains documents that manage the product configuration.Extension MBean collection
You can configure Java Management Extension (JMX) MBeans to extend the existing WebSphere Application Server managed resources in the administrative console. Use this page to register JMX MBeans. Any MBeans that are listed have already been registered.Extension MBean Providers collection
Use this page to view and change the configuration for JMX extension MBean providers.Extension MBean Provider settings
Use this page to view and change the configuration for a JMX extension MBean provider.Extension MBean settings
Use this page to view and configure Java Management Extension (JMX) MBeans.External authorization provider settings
Use this page to enable a Java Authorization Contract for Containers (JACC) provider for authorization decisions.External cache group collection
Use this page to define sets of external caches that are controlled by WebSphere Application Server on web servers such as IBM Edge Server and IBM HTTP Server.External cache group member collection
Use this page to define specific caches that are members of a cache group.External cache group member settings
Use this page to define a single cache that is controlled by WebSphere Application Server.External cache group settings
Use this page to configure sets of external caches that are controlled by WebSphere Application Server on web servers, such as IBM Edge Server and IBM HTTP Server.External Java Authorization Contract for Containers provider settings
Use this page to configure the application server to use an external Java Authorization Contract for Containers (JACC) provider. For example, the policy class name and the policy configuration factory class name are required by the JACC specification.External realm name
Use this page to add a WebSphere Application Server realm that is external to this cell. The realm is initially not trusted. Use the Trusted authentication realms - inbound page to establish trust.Extract certificate
Use this page to extract the signer from the personal certificate and store it in a file. The certificate can be added to a trust store for trust verification. When extracting the signer from a chained personal certificate, the signer at the top level of the chain is extracted.Extract certificate request
Use this page to extract a certificate request to a file so it can be sent to a certificate authority (CA).Extract signer certificate
Use this page to extract a signer certificate from the keystore to a file so that it can be added elsewhere.Federated repository wizard settings
Use this security wizard page to complete the basic requirements to connect the application server to a federated repository.Foreign bus [Settings]
This pane shows the role type assignments for the selected foreign buses.File synchronization service settings
Use this page to specify that a file set on one node matches that on the central deployment manager node and to ensure consistent configuration data across a cell.File transfer service settings
Use this page to configure the service that transfers files from the deployment manager to individual remote nodes.Filter values collection
Use this page to specify the values for source IP, URI, web services, Java Message Service (JMS), or Enterprise JavaBeans (EJB) request metrics filters. When multiple filter values are enabled, a request will pass the filter as long as it matches one of the filter values.Filter values settings
Use this page to specify the values for source IP, URI, web services, Java Message Service (JMS), or Enterprise JavaBeans (EJB) method name request metrics filters.Find target resources
Use this page to find target resources for resource job parameters when you submit a job through the job submission wizard. This page is used for job types such as start server, stop server, and start cluster.Find targets
Use this page to build a list of targets that you can use to choose the targets on which you want the job to run. You can also find targets to add to a group of targets.Firmware collection
Use this page to add a new firmware version to the appliance manager, view existing firmware versions, or delete a firmware version from the appliance manager. A firmware version must exist in the appliance manager before that version can be designated as the active firmware version for a managed set.Firmware settings
Use this page to specify firmware settings for a firmware version in the DataPower appliance manager. A firmware version is a firmware image of a specific level that is used with a specific appliance type, model type, and set of licensed features.Foreign bus [Settings]
This pane shows the role type assignments for the selected foreign buses.Foreign bus connections [Collection]
A foreign bus connection allows communication with another bus. The foreign bus can represent another Service Integration Bus, an instance of IBM MQ, or an indirect connection to another foreign bus.Foreign bus connections [Settings]
A foreign bus connection allows communication with another bus. The foreign bus can represent another Service Integration Bus, an instance of IBM MQ, or an indirect connection to another foreign bus.Foreign cell binding collection
Use this page to manage foreign cell bindings.Foreign cell binding settings
Use this page to configure a foreign cell binding.Foreign destination [Settings]
The name by which this foreign destination is known for administrative purposes.Gateway services [Collection]
A gateway service provides the configuration of the web service enablement of a service destination, along with the information that maps to one or more target destinations.Gateway services [Settings]
A gateway service provides the configuration of the web service enablement of a service destination, along with the information that maps to one or more target destinations.Generic JMS connection factory settings for application clients
Use this panel to view or change the configuration properties of the selected Java Message Service (JMS) connection factory for use with the associated JMS provider. These configuration properties control how connections are created between the JMS provider and the messaging system that it uses.Generic JMS destination settings for application clients
Use this panel to view or change the configuration properties of the selected JMS destination for use with the associated JMS provider.Generic server cluster mapping settings
You can configure settings for a generic server cluster mapping. Generic server cluster mappings are specified only for a generic server cluster custom advisor.Generic server cluster members
After defining the generic server cluster name, use this page to define the members of the cluster.Generic server cluster ports collection
After defining the generic server cluster name, use this page to create, delete, and configure the members of the cluster.Generic server cluster route action settings
You can configure a generic server cluster route action for a proxy server. Add a generic server cluster route action to define routes for inbound requests to specific generic server clusters.Generic server clusters collection
Use this page to create, delete or modify a generic server cluster. Creating a generic server cluster is the next step towards generating the ability to route requests to a non-IBM application server, after creating the proxy server.Generic server clusters configuration
Use this topic to configure a generic server cluster. Creating a generic server cluster is the next step, after creating the proxy server, towards generating the ability to route requests to a non-IBM application server.Generic server settings
Use this page to view or change the settings of a generic server.Global deployment settings
Use this page to manage settings that apply to all applications or to a subset of application types.Global directives
Use this page to configure the global directives for your web server.Global security settings
Use this page to configure administration and the default application security policy. This security configuration applies to the security policy for all administrative functions and is used as a default security policy for user applications. Security domains can be defined to override and customize the security policies for user applications.Group attribute definition settings
Use this page to specify the name of the group membership attribute. Every Lightweight Directory Access Protocol (LDAP) entry includes this attribute to indicate the group to which this entry belongs.Handler class properties with JAX-RPC
Handler class properties using Java API for XML-based RPC (JAX-RPC) are described.High availability group members collection
Use this page to view information about the individual members of a high availability group. This page lists the current members of the selected high availability group.High availability groups collection
Use this page to view information about the high availability groups contained in a core group.Host alias collection
Use this page to manage host name aliases defined for a virtual host. An alias is the DNS host name and port number that a client uses to form the URL request for a web application resource.Host alias settings
Use this page to view and configure a host alias.HPEL log configuration settings
Use this page to configure High Performance Extensible Logging (HPEL) log settings.HPEL logging and trace settings
Use this page to view and configure High Performance Extensible Logging (HPEL) logging and trace settings for the server.HPEL text log configuration settings
You can configure High Performance Extensible Logging (HPEL) settings for text log.HPEL trace configuration settings
Use this page to configure High Performance Extensible Logging (HPEL) trace settings.HTTP basic authentication collection
Use this page to specify a user name and password for transport-level basic authentication security for this port. You can use this configuration when a web service is a client to another web service.HTTP compression action settings
You can configure settings for an HTTP request compression action or an HTTP response compression action for a proxy server. Compression actions are set to compress the request message to the server or response message to the client.HTTP error, FRCA, and NCSA access log settings
Use this page to configure the global HTTP error log, and National Center for Supercomputing Applications (NCSA) access log settings for an HTTP inbound channel. If you are running the product on z/OS, you can also use this page to configure the global Fast Response Cache Accelerator (FRCA) log settings for an HTTP inbound channel. A FRCA log is a specialized form of a NCSA log and can only be created in a z/OS environment.HTTP header action settings
You can configure settings for an HTTP request header action or an HTTP response header action for a proxy server. Use header modification actions to add, modify, or delete request and response headers.HTTP plug-in cluster properties
Use this page to view or change HTTP plug-in properties that apply to the cluster.HTTP proxy inbound channel settings
Use this page to view and configure an HTTP proxy inbound channel. This type of transport channel provides the HTTP proxy capabilities.HTTP SSL Configuration collection
Use this page to configure transport-level Secure Sockets Layer (SSL) security. You can use this configuration when a web service is a client to another web service.HTTP transport bindings settings
Use this page to define the HTTP transport bindings for the HTTP transport policy.HTTP transport channel custom properties
If you are using an HTTP transport channel, you can add any of the following custom properties to the configuration settings for that channel.HTTP transport channel settings
Use this page to view and configure an HTTP transport channel. This type of transport channel handles HTTP requests from a remote client.HTTP transport collection
Use this page to view or manage HTTP transports. Transports provide request queues between web server plug-ins and web containers in which the web modules of applications reside. When you request an application in a web browser, the request is passed to the web server, then along the transport to the web container.HTTP transport policy settings
Use this page to define HTTP transport policy configuration. HTTP features and HTTP connection policies are applied to outbound messages. Any changes to the HTTP transport policy from this console page affects all Java API for XML-Based Web Services (JAX-WS) applications to which this custom HTTP transport policy is attached.HTTP transport settings
Use this page to view and configure an HTTP transport. The name of the page might be that of an SSL setting such as DefaultSSLSettings. This page is not available if you do not have an HTTP transport defined for your system.HTTP Tunnel transport channel custom properties
If you are using an HTTP Tunnel transport channel, you can add the following custom properties to the configuration settings for that channel.HTTP tunnel transport channel settings
IBM proprietary JMS endpoint URL syntax (deprecated)
A Java Message Service (JMS) endpoint URL is used to access Java API for XML Web Services (JAX-WS) or Java API for XML-based RPC (JAX-RPC) web services with the JMS transport. This proprietary URL specifies the Java Message Service (JMS) destination and connection factory, as well as the port component name for the web service request. This endpoint URL is similar to the HTTP endpoint URL, which specifies the host and port as well as the context root and port component name.IBM service log settings
Use this page to configure the IBM service log, also known as the activity log.ID assertion [Settings]
Specifies the signature method and trust mode to use when ID Assertion is set as an authentication method.Import certificate from a key file or managed keystore
Use this page to specify a personal certificate to import from a keystore or key file.Import policy set bindings settings
Use this page to specify a service client or provider policy set binding to import for your service.Import policy sets from a selected location settings
Use this page to specify a policy set to import from a selected location.Import policy sets from default repository settings
Use this page to specify a policy set to import from a default repository. You can import predefined policy sets from the default repository.Inbound and outbound custom properties
Use this page to set additional properties for inbound and outbound messages. You can specify custom properties that apply to both inbound and outbound messages or custom properties that apply to inbound messages only or outbound messages only.Inbound message collection
The messages on the inbound sequence.Inbound messages [Collection]
The inbound message streams from the remote queue point.Inbound Ports [Collection]
An inbound port describes the web service enablement of a service destination on a specific endpoint listener, with associated configuration.Inbound Ports [Settings]
An inbound port describes the web service enablement of a service destination on a specific endpoint listener, with associated configuration.Inbound sequence collection
This page displays the collection of inbound sequences for the current scope. Each inbound sequence is used to receive messages that have been transmitted reliably.Inbound sequences settings
This page displays the collection of inbound sequences for the current scope. Each inbound sequence is used to receive messages that have been transmitted reliably.Inbound services [Collection]
An inbound service describes the web service enablement of a service destination. It provides the configuration of endpoint listeners within a port.Inbound services [Settings]
An inbound service describes the web service enablement of a service destination. It provides the configuration of endpoint listeners within a port.Inbound WS-Security configuration [Settings]
WS-Security configuration for an inbound request. This defines WS-Security requirements for the request consumed from the client and the response generated. The objects created may be applied to one or more inbound ports.Inbound WS-Security configuration [Settings]
WS-Security configuration for an inbound request. This defines WS-Security requirements for the request consumed from the client and the response generated. The objects created may be applied to one or more inbound ports.Indirect lookup binding settings
Use this page to configure a new indirect lookup name binding, or to view or edit an existing indirect lookup binding.Indirect routing properties [Settings]
The routing definition for the next service integration bus in a sequence of connected buses.Initial parameters for servlets settings
Use this page to specify initial parameters that are passed to the init method of web module servlet filters. You can specify initial parameter values for servlets in web modules during or after installation of an application onto a WebSphere Application Server deployment target. The <param-value> values specified in <init-param> statements in the web.xml file of web modules are used by default.Installation Manager installation kits
Use this page to specify where you want to store your IBM Installation Manager installation kits. After you have specified the installation kit location, you can view a detailed list of the installation kits that are available in that location and add or delete installation kits from the list.Install RAR
Use this page to install a resource archive (RAR) file in one of two ways. You can either upload a RAR file from the local file system, or specify an existing RAR file on a server. The RAR file must be installed at the node level, and you can select the node on this page.Integrity [Collection]
Specifies the integrity constraints applied to generated messages. This includes specifying which message parts within the generated message must be digitally signed, and the message parts to attach digitally signed Nonce and time stamp elements to.Integrity [Collection]
Specifies the integrity constraints applied to generated messages. This includes specifying which message parts within the generated message must be digitally signed, and the message parts to attach digitally signed Nonce and time stamp elements to.Integrity [Settings]
Specifies the integrity constraints applied to sent messages. Indicates which parts of the message will be digitally signed.Integrity [Settings]
Specifies the integrity constraints applied to generated messages. This includes specifying which message parts within the generated message must be digitally signed, and the message parts to attach digitally signed Nonce and time stamp elements to.Integrity [Settings]
Specifies the integrity constraints applied to generated messages. This includes specifying which message parts within the generated message must be digitally signed, and the message parts to attach digitally signed Nonce and time stamp elements to.Intelligent Management: administrative roles and privileges
Roles and privileges vary depending on your administrative role and the component.Intelligent Management: HTTP operands
Use the HTTP operands in the subexpression utility builder, an optional tool that helps you build complex rule conditions from subexpressions by using AND, OR, NOT and parenthetical grouping.Intelligent Management: IIOP operands
Use IIOP operands and their associated protocols in the subexpression utility builder, an optional tool that helps you build complex rule conditions from subexpressions by using AND, OR, NOT and parenthetical grouping.Intelligent Management: port number settings
Identify the default port numbers used in the various configuration processes to avoid port conflicts.Intelligent Management: request classification operators
Intelligent Management supports operators in the rules expressions. These operators are also referred to as predicates in Structured Query Language (SQL) terminology because they appear inside of a WHERE or HAVING clause. Operators are case insensitive.Intelligent Management: routing and service policies
Two types of policies are applied to a request: routing and service. You can create routing policies for HTTP and SOAP requests, and you can create service policies for HTTP, IIOP, SOAP, JMS, and SIP requests. Additionally, work classes can contain classification rules for both policy types with the exception of JMS. Classification rules are not supported for JMS work classes.Intelligent Management: SIP operands
You can use the SIP operands and their associated protocols in the subexpression utility builder, an optional tool that helps you build complex rule conditions from subexpressions by using AND, OR, NOT and parenthetical grouping.Intelligent Management: SOAP operands
Use SOAP operands in the subexpression utility builder, an optional tool that helps you build complex rule conditions from subexpressions by using AND, OR, NOT and parenthetical grouping.Intelligent Management: subexpression builder operands
Intelligent Management routing and service policy rules use the subexpression builder. The subexpression builder is an optional tool that helps you build complex rule conditions from subexpressions by using AND, OR, NOT and parenthetical grouping. An expression can be built from several subexpressions using logical operators.Internationalization service settings
Use this page to enable or disable the internationalization service. The internationalization service manages the implicit propagation and scoping of locale and time zone information, called internationalization context, within application components. When the service is enabled, application components can use the internationalization context API to programmatically manage locale and time zone information. In turn, components can use that locale and time zone information with the Java Platform, Standard Edition (JSE) Internationalization API to perform localizations. If internationalization support is not required on the server, disabling the service can improve performance.IP version considerations for cells
There are compatibility issues to consider when configuring the IP version for cells.J2C Activation Specifications collection
A list of Java 2 Connector (J2C) activation specifications for a resource adapter configuration is shown here and is used to create new J2C activation specifications, to select J2C activation specifications for configuration changes, or to delete J2C activation specifications.J2C Activation Specifications settings
Use this page to specify the settings for a Java 2 Connector (J2C) activation specification.J2C Administered Objects collection
This page contains a list of Java 2 Connector Architecture (JCA) administered objects for a resource adapter configuration. This page is also used to create JCA administered objects, select J2C administered objects for configuration changes, or to delete J2C administered objects.J2C Administered Object settings
Use this page to specify the settings for a Java 2 Connector (J2C) administered object.J2C Connection Factories collection
Use this page to view Java 2 Connector (J2C) connection factories, which represent sets of connection configuration values.J2C connection factories settings
Use this page to specify settings for a connection factory.J2C Connection Factory advanced settings
Use this page to specify settings for a Java 2 Connector (J2C) connection factory.JAAS configuration settings
Use this page to specify the name of the Java Authentication and Authorization Service (JAAS) configuration that is defined in the JAAS login panel.JACC provider configuration properties for Tivoli Access Manager
The JACC provider configuration properties that are detailed in the following section may require configuration.JASPI authentication enablement for applications
Use this page to enable or disable Java Authentication SPI (JASPI) authentication for an application or web module, and to specify the name of a JASPI authentication provider to be used for authenticating messages for the application or web module.JASPI authentication provider details
Use this page to provide configuration details for your custom Java Authentication SPI (JASPI) authentication service provider.JASPI authentication providers collection
The Java Authentication Service Provider Interface (JASPI) for Containers Version 1.1 specification defines standard system programming interfaces that enable developers to write a pluggable custom authentication provider that can handle Java EE web authentication mechanisms as well as any extended authentication processing. The WebSphere Application Server runtime uses these standard system programming interfaces to invoke the JASPI authentication provider.Java 2 Connector authentication data entry settings
Use this page as a central place for administrators to define authentication data, which includes user identities and passwords. These values can reference authentication data entries by resource adapters, data sources, and other configurations that require authentication data using an alias.Java dump and core collection
Use this page to generate various Java dumps and cores from within the administrative console.Java EE default resource settings
Use this page to specify the resource to which a Java Platform, Enterprise Edition (Java EE) default resource is bound.Java EE resource provider or connection factory custom properties collection
Use this page to view the custom properties of a Java Platform, Enterprise Edition (Java EE) resource provider or connection factory.JavaMail system properties
Use this information to set custom Java virtual machine (JVM) system properties that provide additional character encoding options for your JavaMail implementation.Java Management Extensions (JMX) connectors
Use this page to view and change the configuration for Java Management Extensions (JMX) connectors, which make connections between server processes. The types of JMX connectors are Simple Object Access Protocol (SOAP), Remote Method Invocation (RMI), JMX Remote application programming interface (JSR 160) Remote Method Invocation (JSR160RMI), and Inter-Process Communications (IPC).Java Management Extensions connector properties
You can specify or set a property in the administrative console, the wsadmin tool, Application Server commands, the scripts that run from a command-line interface, or a custom Java administrative client program that you write. You can also set SOAP connector properties in the soap.client.props file and IPC connector properties in the ipc.client.props file.Java SDK collection
Use this page to specify the default software development kit (SDK) for a node. This page lists the software development kits that are installed on the node. A node can have one default SDK. Servers on the node use the default SDK unless a server overrides the SDK selection and specifies a different SDK.JavaServer Pages (JSP) runtime reloading settings
JavaServer Pages files can be translated and compiled at run time when the JSP file or its dependencies are modified. This is known as JSP reloading.Java virtual machine (JVM) log settings
Use this page to view and modify the settings for the Java virtual machine (JVM) System.out and System.err logs.Java virtual machine cache settings
Use this page to set Java virtual machine (JVM) custom properties to maintain cache entries that are saved to disk.Java virtual machine custom properties
You can use the administrative console to change the values of Java virtual machine (JVM) custom properties.Java virtual machine settings
You can view, and change the Java virtual machine (JVM) configuration settings of a process for an application server.JAX-RPC Handler Lists [Collection]
A JAX-RPC handler list defines an ordered list of JAX-RPC handlers to be invoked against requests and responses.JAX-RPC Handler Lists [Settings]
A JAX-RPC handler list defines an ordered list of JAX-RPC handlers to be invoked against requests and responses.JAX-RPC Handlers [Collection]
A JAX-RPC handler provides customization of web service request or response handling.JAX-RPC Handlers [Settings]
A JAX-RPC handler provides customization of web service request or response handling.JAX-RPC Header [Collection]
Defines the JAX-RPC headers against which this handler operates.JAX-RPC Header [Settings]
Defines the JAX-RPC headers against which this handler operates.JAX-RPC web services enabled module - deployment descriptor settings (ibm-webservices-bnd.xmi file)
The ibm-webservices-bnd.xmi file is a deployment descriptor for a Java API for XML-based RPC (JAX-RPC) web services-enabled web module or an Enterprise JavaBeans (EJB) module. This file contains information for the web services run time that is required by WebSphere Application Server..JAX-WS Handler Lists [Collection]
A JAX-WS handler list defines an ordered list of JAX-WS handlers to be invoked against requests and responses.JAX-WS Handler Lists [Settings]
A JAX-WS handler list defines an ordered list of JAX-WS handlers to be invoked against requests and responses.JAX-WS Handlers [Collection]
A JAX-WS handler provides customization of web service request or response handling.JAX-WS Handlers [Settings]
A JAX-WS handler provides customization of web service request or response handling.JCA life cycle management
Use this page to perform JCA life cycle management operations on data source and connection factory MBeans. With these management operations, you can control the runtime status of the corresponding data source and connection factory resources.JDBC provider collection
Use this page to view JDBC providers. The JDBC provider object encapsulates the specific JDBC driver implementation class for the data sources that you define and associate with the provider.JDBC provider settings
Use this page to modify the settings for a JDBC provider.JDBC provider summary
JDBC providers are prerequisites for data sources, which supply applications with the physical connections to a database.JFAP inbound channel [Settings]
A channel which can be used in combination with the TCP Channel - or other channels that support the same application interface to accept inbound connections to a WebSphere system integration bus messaging engine.JMS activation specification [Settings]
A JMS activation specification is associated with one or more message-driven beans and provides the configuration necessary for them to receive messages.JMS endpoint URL syntax
As part of an emerging industry-standard SOAP over JMS protocol, a Java Message Service (JMS) endpoint URL syntax has been defined. A JMS endpoint URL is used to access Java API for XML Web Services (JAX-WS) or Java API for XML-based RPC (JAX-RPC) web services with the JMS transport. This URL specifies the JMS destination and connection factory, as well as the port component name for the Web service request. This endpoint URL is similar to the HTTP endpoint URL, which specifies the host and port as well as the context root and port component name.JMS providers collection
Use this panel to list JMS providers, or to select a JMS provider to view or change its configuration properties.JMS provider settings
Use this panel to view the configuration properties of a selected JMS provider.JMS provider settings for application clients
Use this page to configure properties of the Java Message Service (JMS) provider, if you want to use a JMS provider other than the default messaging provider or the IBM MQ as a JMS provider.JMS resource provider selection panel
Select the messaging provider with which to create this JMS activation specification, connection factory or destination.JMS transport bindings
Use this page to define the Java Message Service (JMS) transport provider or client bindings configuration.JMS transport policy settings
Use this page to configure settings for the Java Message Service (JMS) transport policy. You can configure a client that is using the JMS transport policy to exchange request and response messages with the server.JMX connector settings
Use this page to view the configuration for a Java Management Extensions (JMX) connector, which makes connections between server processes.JNDI cache settings
Various Java Naming and Directory Interface (JNDI) cache property settings follow. Ensure that all property values are string values.Job manager collection
Use this page to view the job managers to which this node is registered. The job managers enable you to asynchronously submit and administer jobs, such as manage applications, for this node.Job manager settings
Use this page to view the Universal Unique Identifier (UUID) of the job manager, specify the polling interval to check for jobs on the job manager, and specify the web address of the job manager.Job manager settings
Use this page to configure the job manager server and view its properties. You can specify the default job expiration, the job manager web address, and the mail session Java Naming and Directory Interface (JNDI) name.Job scheduler classification rule settings
Use this page to create and manage rules that are used by the scheduler to perform job classification based on the rules or conditions that are defined.Job scheduler configuration
Use this page to set up persistence of job information to the external job database. Configuration settings include the deployment target of the job scheduler, the data source, the database schema name, and the endpoint job log location.Job scheduler job class collection
Use this page to manage your job classes. Every batch job is associated with a job class. If you do not define a class in the job, the default job class is used.Job scheduler job class settings
Use this page to create, edit, and delete job classes. Every batch job is associated with a job class. If you do not define a class in the job, the default job class is used.Job status collection
Use this page to display information about submitted jobs, including the job ID, description, state, activation time, expiration time, and status summary. Jobs are submitted to administer targets that have been registered with the job manager.Job status history collection
Use this page to display the job status of the target at various stages of the job for the target.Job status settings
Use this page to display the job status such as success, partial success, or failed, at each target of the job. Job information, including the job ID, description, activation time, and expiration time, is also displayed.JPA system properties
In addition to the settings that are accessible from the administrative console, you can set Java Persistence API (JPA) system properties by using command-line scripting.JSF engine configuration parameters
In WebSphere Application Server, you can configure the JavaServer Faces (JSF) engine configuration parameters for optimal performance in a production server environment and in a development environment.JSP and JSF option settings
Use this page to configure the class reloading of web modules such as JavaServer Pages (JSP) files and to select a JSF implementation to use with this application.JSP class loading settings
You can configure a JavaServer Pages (JSP) class to be loaded by either the JSP engine's class loader or by the web module's class loader.JSP engine configuration parameters
In WebSphere Application Server, you can configure the JavaServer Pages (JSP) engine configuration parameters for optimal performance in a production server environment and for the needs of developers in a development environment.JSP run time compilation settings
By default, the JavaServer Pages (JSP) engine translates a requested JSP file, compiles the .java file, and loads the compiled servlet into the run time environment. You can change the JSP engine default behavior by indicating that a JSP file must not be translated or compiled at run time, even when a .class file does not exist.Kerberos authentication settings
Use this page to configure and to verify Kerberos as the authentication mechanism for the application server.Key collection
Use this page to view a list of logical names that is mapped to a key alias in the keystore file.Key configuration settings
Use this page to define the mapping of a logical name to a key alias in a keystore file.Key information collection
Use this page to view the configurations that are currently available for generating or consuming the key for XML digital signatures and XML encryption.Key information configuration settings
Use this page to specify the related configuration need to specify the key for XML digital signature or XML encryption.Key information reference configuration settings
Use this page to specify a reference to the message parts for signature and encryption that is defined in the deployment descriptors.Key information references collection
Use this page to view the key information references that are needed for encryption or signing.Key information settings
Use this page to configure the key information for the selected policy set binding. Key information attributes define how cryptographic keys are generated or consumed.Key locator collection
Use this page to view a list of key locator configurations that retrieve keys from the keystore for digital signature and encryption. A key locator must implement the com.ibm.wsspi.wssecurity.config.KeyLocator interface.Key locator configuration settings
Use this page to specify the settings for a key locator configuration. The key locators retrieve keys from the keystore file for digital signature and encryption. This product enables you to plug in a custom key locator configuration.Key managers collection
Use this page to define the implementation settings for key managers. A key manager is invoked during a Secure Sockets Layer (SSL) handshake to determine which certificate alias is used. The default key manager (WSX509KeyManager) performs alias selection. If more advanced function is desired, define a custom key manager on the Manage endpoint security configurations panel.Key managers settings
Use this page to define key managers implementation settings. A key manager gets invoked during an Secure Sockets Layer (SSL) handshake to determine the certificate alias to be used. The default key manager (WSX509KeyManager) performs alias selection. If more advanced function is desired, a custom key manager can be specified here and selected in the SSL configuration.Keys and certificates
Use this page to link to key and certificate binding configuration panels. This panel defines key and certificate bindings for JAX-WS web services only. These keys and certificates can be centrally managed by the product or in an external keystore.Key set groups collection
Use this page to manage groups of public, private, and shared keys. These key groups enable the application server to control multiple sets of Lightweight Third Party Authentication (LTPA) keys.Key set groups settings
Use this page to create new key set groups.Key sets collection
Use this page to manage key sets, which control a set of key instances of the same type for use in cryptographic operations. The keys can either be generated using a custom class or reference keys that already exist in a keystore.Key sets settings
Use this page to set the properties for a new key set.Keystores and certificates collection
Use this page to manage keystore types, including cryptography, Resource Access Control Facility (RACF®) , Certificate Management Services (CMS), Java, and all truststore types.Keystores and certificates exchange signers
Use this page to extract the signer part of a personal certificate from one keystore and add it to another keystore as a signer certificate. Signer certificates can also be listed, and they will be added to the other keystore as well.Key store settings
Use this page to create all keystore types, including cryptographic, Resource Access Control Facility (RACF), Certificate Management Services (CMS), Java, and all truststore types.Known link transmitter inbound streams [Collection]
This pane displays the inbound message streams from messaging applications that are connected to the remote messaging engine, and that are producing messages to this IBM MQ link sender channel transmitter.Known link transmitters [Collection]
This pane displays the inbound receiver queues for messaging applications connected to remote messaging engines, that are producing messages to this IBM MQ link sender channel transmitter.Known link transmitter stream messages [Collection]
This pane displays current messages on the inbound message stream.Known remote publication points [Collection]
The remote messaging engines that have remote producers connected to this publication point.Known remote publication points [Settings]
The remote messaging engines that have remote producers connected to this publication point.Known remote queue points [Collection]
The remote messaging engines that have remote producers or consumers connected to this queue point.Known remote queue points [Settings]
The remote messaging engines that have remote producers or consumers connected to this queue point.Known remote subscription points [Collection]
The remote messaging engines that have remote consumers connected to this subscription point.Known remote subscription points [Settings]
The remote messaging engines that have remote consumers connected to this subscription point.Language versions offered by this product
This product is offered in several languages, as enabled by the operating platform on which the product is installed.Last participant support extension settings
Use this page to configure settings for last participant support. Last participant support is an extension to the transaction service that enables a single one-phase resource to participate in a two-phase transaction with one or more two-phase resources. Values on this panel are ignored if you select Use configuration information in binary on the Application binaries panel.Lightweight Directory Access Protocol entity types collection
Use this page to list Lightweight Directory Access Protocol (LDAP) entity types that are supported by the member repositories or to select an LDAP entity type to view or change its configuration properties.Lightweight Directory Access Protocol entity types settings
Use this page to configure Lightweight Directory Access Protocol (LDAP) entity types that are supported by the member repositories.Lightweight Directory Access Protocol performance settings
Use this page to minimize impacts to performance by adding opened connections and contexts to internally maintained pools and reusing them. Also minimize performance impacts by maintaining internal caches of retrieved data.Lightweight Directory Access Protocol repository configuration settings
Use this page to configure secure access to a Lightweight Directory Access Protocol (LDAP) repository with optional failover servers.Library reference collection
Use this page to view and manage library references that define how to use global libraries. For example, you can use this page to associate shared library files with a deployed application.Library reference settings
Use this page to define library references, which specify how to use global libraries.Lightweight Directory Access Protocol attributes collection
Use this page to add, modify, or delete the configuration of supported, unsupported, and external LDAP attributes in a federated repositories configuration.Link receivers [Collection]
A link can have multiple link receivers. For applications that use point-to-point messaging, there is one link receiver for each messaging engine in the foreign bus, that is, the bus that sends messages across the link. For applications that use publish/subscribe messaging, there is one link receiver for each topic space in the foreign bus. The link receiver acts as an inbound receiver queue for a messaging engine that has applications attached and that is producing messages across this service integration bus link.Link receiver stream messages [Collection]
This pane displays the current messages on the link receiver stream.Link receiver streams [Collection]
This pane displays the inbound message streams from messaging applications on the foreign bus for the link receiver.Link transmitters [Collection]
A link can have multiple link transmitters. For applications that use point-to-point messaging, there is one link transmitter on each messaging engine in the source bus. For applications that use publish/subscribe messaging, there is one link transmitter for each topic space in the source bus. The link transmitter acts as a transmission queue where produced messages are persisted before transmission across the service integration bus link or IBM MQ link to the foreign bus.Link transmitter stream messages [Collection]
This pane displays the outbound messages to the foreign bus link, on the link transmitter stream.Link transmitter streams [Collection]
This pane displays the outbound message streams, by quality of service, for the link transmitter.Listener port settings
A listener port defines the association between a connection factory, a destination, and a deployed message-driven bean. This association enables deployed message-driven beans associated with the port to retrieve messages from the destination.Local operating system settings
Use this page to configure local operating system registry settings.Local operating system wizard settings
Use this security wizard page to configure local operating system registry settings.Log and Trace extensions
The High Performance Extensible Logging (HPEL) capability in the application server provides a way for developers to add extension fields to log and trace records, and a corresponding way for you to filter log and trace records by extension value.Log and trace settings
Use this page to view and configure logging and trace settings for the server.Logging in
Enter your user ID and password to access the console.Login bindings configuration settings
Use this page to specify the Java Authentication and Authorization Service (JAAS) login configuration settings that are used to validate security tokens within incoming messages.Login configuration [Settings]
Specifies the authentication methods this service supports. Custom authentication methods can also be defined.Login configuration [Settings]
Specifies the authentication methods this service supports. Custom authentication methods can also be defined.Login configuration for Java Authentication and Authorization Service
Java Authentication and Authorization Service (JAAS) is a new feature in WebSphere Application Server. JAAS is WebSphere Application Server strategic application programming interface (API) for authentication that replaces the Common Object Request Broker Architecture (CORBA) programmatic login API.Login configuration settings for Java Authentication and Authorization Service
Use this page to configure application login configurations.Login mapping configuration settings
Use this page to specify the Java Authentication and Authorization Service (JAAS) login configuration settings that are used to validate security tokens within incoming messages.Login mappings collection
Use this page to view a list of configurations for validating security tokens within incoming messages. Login mappings map an authentication method to a Java Authentication and Authorization Service (JAAS) login configuration to validate the security token. Four authentication methods are predefined in the WebSphere Application Server: BasicAuth, Signature, IDAssertion, and Lightweight Third Party Authentication (LTPA).Login module order settings for Java Authentication and Authorization Service
Use this page to specify the order in which the application server processes the login configuration modules.Login module settings for Java Authentication and Authorization Service
Use this page to define the login module for a Java Authentication and Authorization Service (JAAS) login configuration.Log levels
Levels control which events are processed by Java logging. WebSphere Application Server controls the levels of all loggers in the system.Log level settings
Use this topic to configure and manage log level settings.Log viewer settings
Use this page to view your High Performance Extensible Logging (HPEL) log, trace, System.out, and System.err content.Look up users
Use this page to select and to map users, groups and special subjects for security roles.LTPA
Use this page to specify the shared keys and configure the authentication mechanism that is used to exchange information between servers. You can also use this page to specify the amount of time that the authentication information remains valid and specify the single sign-on configuration.Mail provider collection
Use this page to view available JavaMail service providers, also known as mail providers. The mail provider encapsulates a collection of protocol providers, which implement the protocols for communication between your mail application and mail servers.Mail provider settings
Use this page to edit mail provider properties or configure a new mail provider. The mail provider encapsulates a collection of protocol providers, which implement the protocols for communication between your mail application and mail servers.Mail provider settings for application clients
Use this page to implement the JavaMail API and create mail sessions.Mail service providers and mail sessions
A mail service provider is a driver that supports mail interaction with mail servers that use a particular mail protocol. The application server includes service providers, which are also known as protocol providers, for mail protocols.Mail session collection
Use this page to view mail sessions that are defined under the parent mail provider.Mail session configuration settings
Use this page to configure mail sessions.Mail session settings for application clients
Use this page to configure mail session properties.Main policy and bootstrap policy settings
Use this page to specify how message security policies are applied to requests and enforced on responses, as defined by the main policy settings and the bootstrap policy settings. Assertions for Web Services Security (WS-Security) versions are already generated based on assertions in the policy set. If the policy set includes a Web Services Security Version 1.1 assertion, then Web Services Security Version 1.1, itself, is asserted.Manage certificate expiration settings
Use this page to configure the certificate expiration monitor.Managed domain settings
Use this page to view the settings for a managed domain. You can also use this page to view the version history for this managed domain, or to view the managed domains that exist for a specific appliance.Managed set collection for a DataPower appliance
Use this page to add, view, or delete a managed set. A managed set is a group of appliances whose firmware, shareable appliance settings and managed domains are all kept synchronized.Managed set firmware settings
Use this page to change the firmware on a managed set. You can upload a file from a local or remote file system. The firmware for a managed set, must have the same value for appliance type, model type and licensed features as the devices in the managed set.Managed set settings
Use this page to view the general properties for the managed set, and a list of the appliances that are part of this managed set. You can also use this page to view lists of the shareable appliance settings versions, and managed and unmanaged domains that can be used with this managed set.Manage endpoint security configurations
Use this page to select a Secure Socket Layer (SSL) configuration from the Local Topology hierarchy, which includes cells, nodes, node groups, servers, and clusters.Manage FIPS
Use this page to disable Federal Information Processing Standards (FIPS) or to enable security standards that are required by the government.Manage foreign bus access roles [Collection]
A foreign bus is another bus with which this bus can exchange messages.Manage message endpoints
Use this panel to manage situations where messaging providers fail to deliver messages to their intended destinations. For example, a provider might fail to deliver messages to a message endpoint when its underlying message driven bean attempts to commit transactions against a database server that is not responding.Manage modules settings
Use this page to specify deployment targets where you want to install the modules that are contained in your application. Modules can be installed on the same deployment target or dispersed among several deployment targets.Manage repositories collection
Use this page to list repositories that are configured in the system or to select a repository to view or change its configuration properties. You can add or delete external repositories.Map a registry principal to a System Authorization Facility user ID using a Java Authentication and Authorization Services login module
You can use a Java Authentication and Authorization Services (JAAS) login module to map a registry principal to the System Authorization Facility (SAF) user ID.Map data sources for all 1.x CMP beans
Use this page to designate how the container-managed persistence (CMP) 1.x beans of an application map to data sources that are available to the application.Map data sources for all 2.x CMP beans
Use this page to set the default data source mapping for EJB modules that contain 2.x container-managed persistence (CMP) beans. Unless you configure individual data sources for your 2.x CMP beans, this default mapping applies to all beans within the module.Map data sources for all 2.x CMP beans settings
Use this page to map container-managed persistence (CMP) 2.x beans of an application to data sources that are available to the application.Map default data sources for modules containing 1.x entity beans
Use this page to set the default data source mapping for EJB modules that contain 1.x container-managed persistence (CMP) beans. Unless you configure individual data sources for your 1.x CMP beans, this default mapping applies to all beans within the module.Mapping-configuration alias
This panel allows you to select a mapping configuration alias for the resource that you are configuring. This panel is only available when security domains are defined. Security domains allow you to isolate mapping configuration aliases between servers. The tree view is useful in determining the security domain to which an alias belongs, and the tree view can help you determine the servers that will be able to access each authentication alias. The tree view is tailored for each resource, so domains and aliases are hidden when you cannot use them. For example, a cell-scoped security domain will be hidden from the tree if all servers and clusters in the tree have defined their own security domain. If you are looking for an alias that is not visible in the tree, it is because the alias cannot be used by any servers that have visibility to this resource. In this case, you must define the alias at the global scope or in a different security domain that is visible to this resource.Mapping properties for a custom login or trusted connection configuration
Use this page to view and manage the mapping properties for a custom login configuration or a trusted connection configuration.Map target settings
Use this page to map a composition unit to a deployment target. The product assigns a default target when you do not specify a target.Match criteria collection
Use this page to view the match criteria that are defined for a policy.Match criteria settings
Use this page to define a match criterion for a policy.Mediation execution points [Collection]
Mediation execution points for the processing of messages from mediation message points that are on a IBM MQ server.Mediation points [Collection]
Bus member (server or cluster) where the mediations for the destination run.Mediation points [Collection]
Bus member (server or cluster) where the mediations for the destination run.Mediation points [Collection]
Bus member (server or cluster) where the mediations for the destination run.Mediation points [Settings]
Bus member (server or cluster) where the mediations for the destination run.Mediation points [Settings]
Bus member (server or cluster) where the mediations for the destination run.Mediations [Collection]
A mediation that is associated with a bus destination to apply processing to messages on that destination.Mediations [Settings]
A mediation that is associated with a bus destination to apply processing to messages on that destination.Mediation thread pool [Settings]
The thread pool used to allocate threads for the execution of mediation handlers.Member attributes collection
Use this page to list Lightweight Directory Access Protocol (LDAP) member attributes or to select a member attribute to view or change its configuration properties.Member attributes settings
Use this page to configure Lightweight Directory Access Protocol (LDAP) member attributes.Memory-to-memory replication settings
Use this page to configure memory-to-memory sessions for failure recovery.Message body [Settings]
The contents of the message body.Message destination reference settings
If your application uses message-driven beans, use this page to specify the Java Naming and Directory Interface (JNDI) name of the J2C administered object to bind the message destination reference to the message-driven beans. You must map each message destination reference that is defined in your application to an administered object.Message details
Use the Message Details panel of the administrative console to view detailed information about errors, warnings, and informational messages.Message expiration settings
Use this page to define settings for message expiration, if and when messages expire. When you specify message expiration, the message expires after the specified interval of time passes.Message layer authentication
Defines the credential information and sends that information across the network so that a receiving server can interpret it.Message listener port collection
The message listener ports configured in the administrative domainMessage listener service
The message listener service is an extension to the JMS functions of the JMS provider. It provides a listener manager that controls and monitors one or more JMS listeners, which each monitor a JMS destination on behalf of a deployed message-driven bean.Message listener service custom properties
Use this panel to view or change custom properties of the message listener service.Message listener service on z/OS
On the z/OS platform, the message listener service implementation uses the scalable server architecture to divide the listener port functions between the controller and servant processes.Message part protection settings
Use this page to define the message parts that you want protected and how that protection is provided.Message parts [Collection]
Identifies a specific message part according to the specified dialect and keyword.Message Parts [Settings]
Identifies a specific message part according to the specified dialect and keyword.Message points [Collection]
Queue points and publication points for the messaging engine.Message requests [Collection]
A snapshot of the current message retrieval requests from the remote message point.Message Requests [Collection]
A snapshot of the current message retrieval requests from the message point.Messages [Collection]
A snapshot of the current outbound messages for the message point.Messages [Collection]
A snapshot of the current outbound messages for the message point.Messages [Collection]
The messages on the message point.Messages [Settings]
The properties for a message on the message point.Messages [Settings]
The properties for a message on the message point.Messages [Settings]
The properties for a message on the message point.Message settings
The details of an individual message.Message store collection
This page displays the collection of reliable messaging storage managers for the current scope.Messaging engine policy maintenance [Collection]
This pane shows all the messaging engine policies for this cluster and their current settings, that is, the settings that determine messaging engine behavior. This list of policies comprises all the core group policies that are associated with the messaging engines in the cluster. If required, you can make a messaging engine policy conform to the currently selected messaging engine policy assistance type. You can also access the associated core group policy settings, although you should not change these settings unless you already have experience of doing so.Messaging engines [Collection]
A messaging engine is a component, running inside a server, that manages messaging resources for a bus member. Applications are connected to a messaging engine when they access a service integration bus.Messaging engines [Settings]
A messaging engine is a component, running inside a server, that manages messaging resources for a bus member. Applications are connected to a messaging engine when they access a service integration bus.Messaging resources for this application
This pane provides an expandable tree view of all the references to messaging resources declared in the deployment descriptors for the current application. As many of the references as possible are resolved to links to the associated configuration panel for the referenced object.Metadata for module settings
Use this page to instruct a Java Platform, Enterprise Edition (Java EE) enterprise bean (EJB) deployment descriptor, web module deployment descriptor, or JCA resource adapter archive (RAR) module to ignore annotations that specify deployment information.MIME type collection
Use this page to view and configure multi-purpose internet mail extensions (MIME) object types and their file name extensions.MIME type settings
Use this page to configure a multi-purpose internet mail extensions (MIME) object type.Monitoring policy settings
Use this page to view or change settings that control how the node agent monitors and restarts a process.Multi-broker replication domain settings
Use this page to configure a multi-broker replication domain. This administrative console page applies only to replication domains that were created with a previous version of the product. Replication domains use the data replication service (DRS).My tasks
Create and edit a task view in the console navigation.Name server settings
Use this page to configure Naming Service Provider settings for the application server. On multiple-server products, you also can configure Naming Service Provider settings for a deployment manager or node agent.Name space binding collection
Use this page to configure a name binding of an EJB, a CORBA CosNaming NamingContext, a CORBA leaf node object, an object that you can look up using Java Naming and Directory Interface (JNDI), or a constant string value.Native processes
Use this page to view and modify properties of the JMS Integral Provider native processes.New Administrative Authorization Group
Use this page to create a new administrative authorization group and to specify the associated administrative resources.New appliance settings for the DataPower appliance
Use this page to specify the settings for an appliance that you are adding to the DataPower appliance manager.New business-level application settings
Use this page to name and describe a new business-level application.New core group policy definition
Use this page to create a new policy for a high availability group.New firmware version settings
Use this page to upload a new firmware version from either a local or remote file system.New repository checkpoint settings
Use this page to create a full checkpoint of the configuration repository. A full checkpoint is a copy of the entire configuration repository, including applications and connectors. Use a full checkpoint to restore the entire configuration repository back to the state it was in at the time the full checkpoint was made.New Resource environment provider
Use this page to define the configuration for a library that provides the implementation for a environment resource factory.New target settings
Use this page to register a remote computer as a target with the job manager. To register a target with the job manager, you must be authorized for the administrator role.Node agent collection
Use this page to view information about node agents. Node agents are administrative agents that monitor application servers on a host system and route administrative requests to servers. A node agent is the running server that represents a node in a Network Deployment environment.Node agent server settings
Use this page to view information about and to configure a node agent. A node agent coordinates administrative requests and event notifications among servers on a machine. A node agent is the running server that represents a node in a WebSphere Application Server, Network Deployment environment.Node collection
Use this page to manage nodes in the WebSphere Application Server environment. Nodes group managed servers. The table lists the managed and unmanaged nodes in this cell. The first node is the deployment manager. Add new nodes to the cell and to the list by clicking Add Node.Node collection for the administrative agent
Use this page to view the application server nodes that are registered to the administrative agent. The administrative agent provides a single interface to the registered nodes.Node group collection
Use this page to manage node groups. A node group is a collection of WebSphere Application Server nodes. A node group defines a boundary for server cluster formation.Node group member collection
Use this page to manage node groups members. A node group member is a WebSphere Application Server node.Node group member settings
Use this page to view the configuration or topology settings for a node group member.Node group settings
Use this page to view or change the configuration or topology settings for a node group instance.Node installation properties
Use this page to view read-only installation properties for this node. These properties provide information about the capabilities of the node that are collected during product installation time, such as the operating system name, architecture and version, or WebSphere Application Server product levels that are installed on the node.Node settings
Use this page to view or change the configuration or topology settings for either a managed node instance or an unmanaged node instance.Nonce [Collection]
Attaches a Nonce element to the message part specified by the dialect and keyword attributes. Nonce is a randomly generated value.Nonce [Settings]
Attaches a Nonce element to the message part specified by the dialect and keyword attributes. Nonce is a randomly generated value.Notification email parameters
Use this page to modify the cell-wide task notification email parameters.Notifications
Use this page to specify the generic notification definitions that are used in certificate expiration monitors.Notifications settings
Use this page to set properties for new notifications used in certificate expiration monitors or for security audit subsystem failures.Object cache instance collection
Use this page to configure and manage object cache instances, which in addition to the default shared dynamic cache, can store, distribute, and share data for Java Platform, Enterprise Edition (Java EE) applications. Use cache instances to give applications better flexibility and tuning of the cache resources.Object cache instance settings
An object cache instance is a location, in addition to the default shared dynamic cache, where any Java Platform, Enterprise Edition (Java EE) application can store, distribute, and share data. This gives applications greater flexibility and better tuning of the cache resources. Use the DistributedMap programming interface to access this cache instance. See the API documentation for more information.Object caching properties
The object cache is used to cache all Tivoli® Access Manager objects, including their extended attributes. This bypasses the need to query the Tivoli Access Manager authorization server for each resource request.Object names: What the name string cannot contain
When you create a new object using the administrative console or a wsadmin command, you often must specify a string for a name attribute.Object pool managers collection
An object pool manages a pool of arbitrary objects and helps applications avoid creating new Java objects repeatedly. Most objects can be created once, used and then reused. An object pool supports the pooling of objects waiting to be reused. These object pools are not meant to be used for pooling Java Database Connectivity connections or Java Message Service (JMS) connections and sessions. WebSphere Application Server provides specialized mechanisms for dealing with those types of objects. These object pools are intended for pooling application-defined objects or basic Developer Kit types.Object pool managers settings
An object pool manages a pool of arbitrary objects and helps applications avoid creating new Java objects repeatedly. Most objects can be created once, used and then reused. An object pool supports the pooling of objects waiting to be reused. These object pools are not meant to be used for pooling Java Database Connectivity connections or Java Message Service (JMS) connections and sessions. WebSphere Application Server provides specialized mechanisms for dealing with those types of objects. These object pools are intended for pooling application-defined objects or basic Developer Kit types.Object pool service settings
Use this page to enable or disable the object pool service, which manages object pool resources used by the server.Object Request Broker custom properties
There are several ways to configure an Object Request Broker (ORB). For example, you can use ORB custom property settings, or system property settings to configure an ORB, or you can provide objects during ORB initialization. If you use the following ORB custom properties to configure an ORB, remember that two types of default values exist for some of these properties: the Java SE Development Kit (JDK) default values and the WebSphere Application Server default values.Object Request Broker service settings
Use this page to configure the Java Object Request Broker (ORB) service.Object Request Broker tuning guidelines
Use the guidelines in this document any time the Object Request Broker (ORB) is used in a workload.ORB services advanced settings on the z/OS platform
Use this topic to support Object Request Broker (ORB) service advanced settings. This support includes ORB listener keep alive, ORB Secure Sockets Layer (SSL) listener keep alive, control threads, and workload profile.ORB service transport channel settings
Use this page to view and configure an Object Request Broker (ORB) Service transport channels. This type of transport channel handles CORBA and RMI/IIOP inbound messages for the ORB Service. It enables clients to make requests and receive responses from servers in a network-distributed environment.Other context properties settings
Use this page to specify properties to be passed to the javax.naming.InitialContext constructor for an indirect Java Naming and Directory Interface (JNDI) lookup name binding. Completion of this page is optional. The properties are in addition to the basic properties specified for an indirect namespace binding.Outbound message collection
The messages on the outbound sequence.Outbound messages [Collection]
The outbound message streams from this remote message point to the remote localized message point.Outbound Ports [Collection]
An outbound port represents a single port for a WSDL-defined service provider. It provides the configuration of invocation of the web service.Outbound Ports [Settings]
An outbound port represents a single port for a WSDL-defined service provider. It provides the configuration of invocation of the web service.Outbound sequence collection
This page displays the collection of outbound sequences for the current scope. Outbound sequences are used to transmit messages reliably from the local application to the remote endpoint. Each sequence has a unique identifier.Outbound sequences settings
This page displays the collection of outbound sequences for the current scope. Outbound sequences are used to transmit messages reliably from the local application to the remote endpoint. Each sequence has a unique identifier.Outbound services [Collection]
An outbound service represents a WSDL-described service.Outbound services [Settings]
An outbound service represents a WSDL-described service.Outbound WS-Security configuration [Settings]
WS-Security configuration for an outbound request. This defines WS-Security requirements for the request generated and response consumed from the target. The objects created may be applied to one or more outbound ports.Outbound WS-Security configuration [Settings]
WS-Security configuration for an outbound request. This defines WS-Security requirements for the request generated and response consumed from the target. The objects created may be applied to one or more outbound ports.Part reference collection
Use this page to view the message part references for signature and encryption that are defined in the deployment descriptors.Part reference configuration settings
Use this page to specify a reference to the message parts for signature and encryption that are defined in the deployment descriptors.Peer access point collection
Use this page to view all of the peer access points that are defined on your system. You can include one or more of these access points in an access point group. Only one peer access point should be defined for a remote cell.Peer access point selection
Use this page to control which peer access points are associated with this access point group. You can also use this page to create new peer access points for this access point group, or delete existing peer access points.Peer access point settings
Use this page to configure a peer access point. Each peer access point is used to communicate with core groups in other cells. A peer access point corresponds to a core group access point in the peer cell. The peer access point communication settings are specified by using one or more peer endpoints or a proxy peer.Peer core group collection
Use this page to view the peer core groups that are defined for your system. You can also use this page to define a new peer core group or delete an existing peer core group.Peer core group settings
Use this page to create a peer core group. Peer core groups are core groups that reside in different cell. The local core group bridge attempts to establish communication between peer core groups in the order in which they appear in the list of peer core groups.Peer port collection
Use this page to define the peer ports for the peer access point. Each peer port identifies a bridge interface of a core group bridge service in the peer cell. Each peer access point that does not have a proxy peer must have one or more peer ports.Peer port settings
Use this page to configure a peer port. A peer port identifies the host name and port of an application server that is a bridge interface in another cell. This application server is using the core group bridge service to communicate with other core groups. Each peer access point can have one or more peer ports. Each port identifies a bridge interface of a core group bridge service in the peer cell.Performance advisor report in Tivoli Performance Viewer
View recommendations and data from the performance advisor in Tivoli Performance Viewer by clicking the Advisor link in Tivoli Performance Viewer for a server.Performance and Diagnostic Advisor configuration settings
Use this page to specify settings for the Performance and Diagnostic Advisor.Performance Monitoring Infrastructure collection
Use this page to configure Performance Monitoring Infrastructure (PMI).Performance Monitoring Infrastructure settings
Use this page to specify settings for performance monitoring, including enabling performance monitoring, selecting the Performance Monitoring Infrastructure (PMI) module and setting monitoring levels.PerfServlet output
The PerfServlet input and output is used for simple end-to-end retrieval of performance data that any tool, provided by either IBM or a third-party vendor, can handle.Permanent topic namespace [Settings]
A topic namespace is a grouping of topics that allows information to be shared between applications.Permanent topic namespaces [Collection]
A topic namespace is a grouping of topics that allows information to be shared between applications.Permitted transports [Collection]
A permitted transport is a transport mechanism that this bus will allow remote clients to use.Personal certificate requests collection
Use this page to manage personal certificate requests. Personal certificate requests are temporary place holders for certificates that will be signed by a certificate authority (CA).Personal certificate requests settings
Use this page to create a new certificate request that can be extracted and sent to a certificate authority (CA).Personal certificates collection
Use this page to manage personal certificates.Plug-ins: Resources for learning
Use the following links to find relevant supplemental information about web server plug-ins. The information resides on IBM and non-IBM Internet sites, whose sponsors control the technical accuracy of the information.Policies applied settings
Use this panel to view and change whether the policy configuration of a WebSphere Application Server service client is configured dynamically, based on the policies supported by its service provider. You can view or change how the client obtains the policy of the service provider; the client can use an HTTP GET request or a Web Services Metadata Exchange (WS-MetadataExchange) request. You can specify a policy set and binding to provide message-level security for WS-MetadataExchange requests or to specify HTTP transport and SSL transport configuration for HTTP GET requests.Policy groups
You can access the detailed settings information for every policy group that you can configure for a UDDI registry node.Policy set bindings settings
Use this page to view or define general, application specific, or trust service specific bindings configuration information for policies that you can associate with the selected policy set. This bindings configuration information is specific to a system. Use the links on this page to work with bindings for each specific policy.Policy set bindings settings for Custom properties
Use this page to view, define, or configure general bindings or application specific bindings, for the Custom properties policy.Policy set bindings settings for WS-Security
Use this page to view, define or configure general bindings and application specific properties for the WS-Security policy. You can configure the main policy or the secure conversation bootstrap policy by editing the general bindings.Policy sharing settings
Use this pane to view and change whether the policy configuration of a web services service provider is shared. You can configure the service provider to include the policy configuration in its Web Services Description Language (WSDL) so that it can be accessed using an HTTP Get request, or published. You can also make the policy configuration available to a Web Services Metadata Exchange (WS-MetadataExchange) request.Port [Settings]
Portlet container custom properties
You can configure name-value pairs of data, where the name is a property key and the value is a string value that you can use to set internal system configuration properties. Defining a new property enables you to configure a setting beyond that which is available in the administrative console. The following is a list of the available Portlet container custom properties.Portlet container settings
Use this page to configure and manage the portlet container of this application server.Ports collection
Use this page to view and manage communication ports used by runtime components running within a process. Communication ports provide host and port specifications for a server.Ports settings
Use this to view and change the configuration for a communication port used by run-time components running within a process. A communication port provides host and port specifications for a server.Preferred coordinator servers settings
Use this page to define an ordered list of preferred core group servers. This list indicates where the high availability manager coordinators will run.Preferred port mappings
Use this page to view and manage a preferred portType mapping for a web service.Preferred servers
Use this page to define the ordered list of preferred servers for the selected policy. The policy gives preference to the servers in this list when activating group members.Preparing for application installation binding settings
Use this page to select whether to view all installation options and to change the existing bindings for you application or module during installation. You can choose to generate default bindings for any incomplete bindings in the application or module or to assign specific bindings during installation.Preparing for application installation settings
Use this page to specify an application or module to install.Preparing for application update settings
Use this page to update enterprise applications, modules or files already installed on a server.Process definition settings
Use this page to configure a process definition. A process definition includes the command line information necessary to start or initialize a process.Process definition type settings
Use this page to view or change settings for a process definition type. This page only displays if you are running the product on z/OS.Process execution settings
Use this page to view or change the process execution settings for a server process.Process logs settings
Use this page to view or change settings for specifying the files to which standard out and standard error streams write.Profiles: File-system requirements
A minimum amount of space must be available in the directory where you create a profile.Programmatic session cookie configuration collection
Use this page to secure cookies by prohibiting programmatic configuration.Property [Settings]
Use this page to specify an arbitrary name and value pair. The value that is specified for the name and value pair is a string that can set internal system configuration properties.Property collection
Custom properties for the type of service integration resource. Type the name and value of any custom properties that you need.Property extension repository settings
Use this page to configure a property extension repository that is used to store attributes that cannot be stored in existing repositories.Property settings
Custom properties for the type of service integration resource. Type the name and value of any custom properties that you need.Protection token settings (generator or consumer)
Use this page to configure protection tokens. Protection tokens sign messages to protect integrity or encrypt messages to provide confidentiality.Protocol providers collection
Use this page to select or add a protocol provider that supports interaction between your mail application and mail servers. For example, your application might require the Simple Mail Transfer Protocol (SMTP), which is a popular transport protocol for sending mail. Selecting that protocol provider allows your mail application to connect and send mail through the server.Protocol providers settings
Use this page to set properties of a protocol provider, including SMTP, IMAP and POP3, which provides the implementation class for a specific protocol to support communication between your mail application and mail servers.Provide HTTP endpoint URL information
Use this page to specify endpoint URL prefix information for web services accessed by HTTP. Prefixes are used to form complete endpoint addresses included in published Web Services Description Language (WSDL) files.Provide JMS and EJB endpoint URL information
Use this page to specify Java Message Service (JMS) and Enterprise JavaBeans (EJB) endpoint URL fragments for web services accessed through SOAP and Java Message Service (JMS) or directly as enterprise beans. Fragments are used to form complete endpoint addresses included in published Web Services Description Language (WSDL) files.Provide JNDI names for JCA objects settings
Use this page to configure Java Naming and Directory Interface (JNDI) name values for J2C objects (J2CConnectionFactory, J2CActivationSpec, and J2CAdminObject) in your application or modules. If your application contains an embedded resource archive (RAR) file, specify the name and JNDI name of each JCA connection factory, administered object, and activation specification.Provide options to compile JavaServer Pages settings
Use this page to specify options to be used by the JavaServer Pages (JSP) compiler.Provide options to perform the EJB Deploy settings
You can specify options for the enterprise bean (EJB) deployment tool. The tool generates code that is needed to run enterprise bean files. You can specify extra class paths, Remote Method Invocation compiler (RMIC) options, database types, and database schema names to be used while running the EJB deployment tool.Provide options to perform the web services deployment settings
Use this page to specify options for web services deployment.Proxy actions collection
Use this page to administer actions for the proxy server. Proxy actions include creating, modifying, or deleting rules that affect caching, compression, headers, rewriting, and routing for the proxy server. The Proxy actions collection panel allows you to configure proxy actions from one interface.Proxy cluster member settings
Use this page to manage the members of a proxy cluster. A proxy cluster of proxy servers is managed together and participate in workload management.Proxy cluster member templates collection
Use this page to view the list of proxy cluster member templates that exist for this proxy cluster.Proxy cluster member template settings
Use this page to modify proxy cluster member template attributes.Proxy rule expressions collection
Use this page to administer proxy rule expressions for the proxy server. Proxy rule expressions allow you to make configuration rules more granular in scope by specifying information within the rule. A proxy rule expression is associated with a virtual proxy host and consists of operands and operators that are defined by an administrator. When an expression evaluates to true, the proxy action rules associated with that proxy rule expression are performed.Proxy rule expression settings
You can configure settings for a proxy rule expression. A proxy rule expression consists of operands and operators that are defined by an administrator. If a proxy rule expression evaluates to true, then all proxy actions configured for that rule expression are run.Proxy security level properties
These settings describe the attributes and policies that define the security level of a secured proxy server. The overall security level of the secured proxy server is set to the weakest level of security assigned to any of the individual settings.Proxy server cluster collection
Use this page to view information about and change configuration settings for a proxy server cluster. A proxy cluster consists of a group of proxy servers.Proxy server cluster member collection
Use this page to view and manage proxy servers that belong to a proxy cluster.Proxy server cluster settings
Use this page to view a list of the proxy server clusters that are defined for your system, and the status of each of these clusters. You can also use this page to view or change the configuration settings for a specific proxy server cluster or to view the local topology of a specific proxy server cluster.Proxy server collection
This topic lists the proxy servers in the cell. A proxy server resides within a node.Proxy server configuration
You can modify an existing proxy server to perform advanced routing options, such as routing requests to a non-WebSphere Application Server cell, and to perform caching. The options to configure the proxy server from this panel are under Proxy server properties.Proxy server settings
Use this topic to perform advanced configuration on a proxy server. Proxy settings enable the system administrator to fine tune the behavior of the proxy server. In particular, you can configure the connections and requests to the application server, enable caching, configure the requests that must be rejected, define how error responses are handled, and specify the location of the proxy logs.Proxy services [Collection]
A proxy service provides the configuration of the web service enablement of a service destination that is able to act as a proxy for a variety of providers.Proxy services [Settings]
A proxy service provides the configuration of the web service enablement of a service destination that is able to act as a proxy for a variety of providers.Proxy virtual hosts collection
Use this page to administer proxy virtual hosts. A proxy virtual host allows a single proxy server to host multiple domains or ports on a single IP or port. Each proxy virtual host consists of a domain name and a port.Proxy virtual host settings
You can configure settings for a proxy virtual host. A proxy virtual host allows a single proxy server to host multiple domains or ports on a single IP or port. Each proxy virtual host consists of a domain name and a port.Proxy virtual host settings details
Use this panel to override some proxy server scoped settings with values to be used for the proxy virtual host.Publication points [Collection]
The message point for a topic space, for publish/subscribe messaging.Publication points [Collection]
The message point for a topic space, for publish/subscribe messaging.Publication points [Settings]
The message point for a topic space, for publish/subscribe messaging.Publish/subscribe broker profiles [Collection]
Profiles used to define the topic mappings and transactionality for publishing and receiving (by subscription) topics across the publish/subscribe bridge between WebSphere Application Server and a message broker in a IBM MQ network.Publish/subscribe broker profiles [Settings]
Profiles used to define the topic mappings and transactionality for publishing and receiving (by subscription) topics across the publish/subscribe bridge between WebSphere Application Server and a message broker in a IBM MQ network.Publisher registrations [Collection]
The set of applications that are currently registered as publishers with the notification broker.Publish WSDL compressed files settings
Use this page to publish Web Services Description Language (WSDL) files.Publish WSDL files to ZIP file [Settings]
Publish the WSDL files for this service to a .zip filePull points [Collection]
This collection lists the pull points that have been created on the associated bus member or members by WS-Notification applications. Use this panel to view the information about a pull point, such as the subscription with which it is associated and the time at which it is currently set to expire. You can also delete a pull point using the button provided.Quality of protection (QoP) settings
Use this page to specify security level, ciphers, and mutual authentication settings for the Secure Socket Layer (SSL) configuration.Queue [Settings]
A queue for point-to-point messaging.Queue collection
A JMS queue destination is used for point-to-point messaging. Use this panel to create or delete queue destinations, or to select a queue destination to view or change its configuration properties.Queue connection factory collection
A queue connection factory is used to create connections to the associated JMS provider of the JMS queue destinations, for point-to-point messaging.Queue points [Collection]
The message point for a queue, for point-to-point messaging.Queue points [Collection]
The message point for a queue, for point-to-point messaging.Queue points [Settings]
The message point for a queue, for point-to-point messaging.Realm configuration settings
Use this page to manage the realm. The realm can consist of identities in the file-based repository that is built into the system, in one or more external repositories, or in both the built-in, file-based repository and one or more external repositories.Receive certificate from CA
Use this page to import your personal certificate from the certificate authority (CA). The imported certificate replaces the temporary certificate associated with the public/private keys in the certificate request that is stored in the key store.Recover managed node settings
Use this page to recover an existing managed node of a deployment manager cell. The node must be at the deployment manager level.Redundant core group policies [Collection]
This pane shows all the core group policies that are associated with this cluster through their match criteria, but that are not associated with any messaging engine in this cluster. Use this pane to delete redundant core group policies that you do not want.Referenceables collection
Use this page to view configured referenceables, which encapsulate the class name of the factory that converts information in the name space into a class instance for a physical resource.Referenceables settings
Use this page to set the class name of the factory that converts information in the name space into a class instance of a physical resource.Registered nodes settings
Use this page to view properties for a node registered to the administrative agent. The properties are name, unique ID, and poll jobs from job manager.Register or unregister with job manager settings
Use this page to either register a node to a job manager or unregister a node from a job manager. The node can be a deployment manager or a node registered to an administrative agent.Relationship options settings
Use this page to specify relationship options for deployable or composition units in an asset deployed as part of a business-level application. Specifying a relationship declares a dependency relationship that a deployable unit or composition unit has on another asset deployed as a shared library in the same business-level application.Reliable messaging state settings
This page provides an overview of the WS-ReliableMessaging runtime state. Use this page to manage reliable messaging at run time.Remote dispatcher property settings
Use this page to configure the sending of include requests between the application and remote resources.Remote mediation points [Collection]
The remote mediation points that are producing messages to mediation points on remote messaging engines.Remote mediation points [Settings]
The remote mediation points that are producing messages to mediation points on remote messaging engines.Remote Publication Points [Collection]
The remote publication points that are producing messages to publication points on remote messaging engines.Remote Publication Points [Settings]
The remote publication points that are producing messages to publication points on remote messaging engines.Remote queue points [Collection]
The remote queue points that are producing or consuming messages to or from queue points on remote messaging engines.Remote queue points [Settings]
The remote queue points that are producing/consuming messages to/from queue points on remote messaging engines.Remote subscription [Collection]
The subscription that has been made from this messaging engine to a subscription home on a remote messaging engine.Remote subscription [Settings]
The subscription that has been made from this messaging engine to a subscription home on a remote messaging engine.Remote web server management
Use this page to configure a remote IBM HTTP Server web server.removeMapPlatformSubject script
If you want to use distributed identity mapping for System Authorization Facility (SAF), use the removeMapPlatformSubject Jython script that is provided to remove the unnecessary Java Authentication and Authorization Service (JAAS) login module, MapPlatformSubject, from the security configuration.Replace a certificate
Use this page to specify two certificates: the first selected certificate is replaced by the second selected certificate. The replace function replaces all the old signer certificates in key stores that are managed throughout the cell with the new signer from the new certificate. The same level of trust that was established with the old certificate is maintained. All places the certificate's alias is referenced in the security configuration will be replaced with the certificate's alias. The alias could be referenced on a security object like the SSL configuration, the dynamic outbound endpoint SSL configuration and key set groups.Replication domain collection
Use this page to configure a list of replication domains that are used by the following components: Session Manager for session failover, EJB for stateful session bean failover, SIP for failover, and dynacache for cache replication. All components that need to share information must be in the same replication domain. Data replication domains replace multi-broker replication domains that were available for replication in prior releases. Migrated application servers use multi-broker replication domains which are collections of replicators. You should migrate any multi-broker replication domains to be data replication domains.Replicator entry collection
Use this page to view and manage replicator entries. Replicator entries are for use only with multi-broker replication domains. Each multi-broker replication domain consists of one or more replicator entries.Replicator entry settings
Use this page to view and configure a replicator entry, or replicator. Replicators are used with multi-broker replication domains.Repository checkpoint collection
Use this page to create, delete, restore, and export checkpoints. Repository checkpoints represent saved images of the repository before configuration changes are made. Checkpoints can be either full or delta images. A full checkpoint is created manually by an administrator and is a copy of the entire configuration repository, including applications and connectors. A delta checkpoint is created automatically when the configuration is changed and contains copies of the affected configuration documents before the changes are made. Use checkpoints to restore the configuration repository back to a prior state.Repository reference settings
Use this page to configure a repository reference. A repository reference is a single repository that contains a set of identity entries that are referenced by a base entry into the directory information tree.Repository service custom properties
Use this page to add custom properties for the repository service.Repository service settings
Use this page to view and change the configuration for an administrative service repository.Request consumer (receiver) binding configuration settings
Use this page to specify the binding configuration for the request consumer.Request consumer binding [Settings]
WS-Security binding for the consumption of inbound requests from the caller.Request generator (sender) binding configuration settings
Use this page to specify the binding configuration for the request generator.Request generator binding. [Settings]
WS-Security binding for the generation of outbound request to a target.Request metrics
Use this page to enable request metrics, select the components that are instrumented by request metrics, set trace levels, enable standard logs, enable Application Response Measurement (ARM), specify the type of ARM agent, and specify the ARM transaction factory implementation class name.Request metrics filters
Use this page to view a list of request metrics filters.Request metrics filter settings
Use this page to specify filters that define whether or not trace is enabled for inbound requests. Note that the filters will only be checked for inbound requests. For intra-process and outbound calls, filters will not be checked. If an inbound request passes the relevant filters, the request will be instrumented as it moves through WebSphere Application Server. If an inbound request does not pass the relevant filters, the request will not be instrumented for its entire code path in WebSphere Application Server.Request metrics performance data
Use this page to learn how to interpret performance data for request metrics in trace record format.Request metrics trace filters
When request metrics is active, trace filters control which requests get traced. The data is recorded to the system log file or sent through Application Response Measurement (ARM) for real-time and historical analysis.Request or Response token policies collection
Use this page to define policies that specify supporting security tokens and properties.Request receiver [Settings]
Draft 13 WS-Security binding for the consumption of inbound requests from the caller.Request receiver binding collection
Use this page to specify the binding configuration to receive request messages for Web Services Security.Request sender [Settings]
Draft 13 WS-Security binding for the generation of requests to an outbound target.Request sender binding collection
Use this page to specify the binding configuration to send request messages for Web Services Security.Required confidentiality [Collection]
Specifies the confidentiality constraints consumed messages must meet. This includes specifying which message parts within the incoming message must be encrypted, and the message parts to which attached encrypted Nonce and time stamp elements are expected.Required confidentiality [Collection]
Specifies the confidentiality constraints consumed messages must meet. This includes specifying which message parts within the incoming message must be encrypted, and the message parts to which attached encrypted Nonce and time stamp elements are expected.Required confidentiality [Settings]
Specifies the confidentiality constraints applied to sent messages. Indicates which parts of the message will be encrypted.Required confidentiality [Settings]
Specifies the confidentiality constraints consumed messages must meet. This includes specifying which message parts within the incoming message must be encrypted, and the message parts to which attached encrypted Nonce and time stamp elements are expected.Required confidentiality [Settings]
Specifies the confidentiality constraints consumed messages must meet. This includes specifying which message parts within the incoming message must be encrypted, and the message parts to which attached encrypted Nonce and time stamp elements are expected.Required integrity [Collection]
Specifies the integrity constraints consumed messages must meet. This includes specifying which message parts within the incoming message must be digitally signed, and the message parts to which attached digitally signed Nonce and time stamp elements are expected.Required integrity [Collection]
Specifies the integrity constraints consumed messages must meet. This includes specifying which message parts within the incoming message must be digitally signed, and the message parts to which attached digitally signed Nonce and time stamp elements are expected.Required integrity [Settings]
Specifies the integrity constraints received messages must meet. Indicates which parts of the message must be digitally signed.Required integrity [Settings]
Specifies the integrity constraints consumed messages must meet. This includes specifying which message parts within the incoming message must be digitally signed, and the message parts to which attached digitally signed Nonce and time stamp elements are expected.Required integrity [Settings]
Specifies the integrity constraints consumed messages must meet. This includes specifying which message parts within the incoming message must be digitally signed, and the message parts to which attached digitally signed Nonce and time stamp elements are expected.Required security token [Collection]
Specifies accepted stand-alone security tokens within a consumed message. Stand-alone security tokens are those not already used for signature or encryption. Defining a required security token means that messages containing a token of that type will be processed according to the usage assertion. The security token will not be used for authentication unless it is also specified within a caller.Required security token [Collection]
Specifies accepted stand-alone security tokens within a consumed message. Stand-alone security tokens are those not already used for signature or encryption. Defining a required security token means that messages containing a token of that type will be processed according to the usage assertion. The security token will not be used for authentication unless it is also specified within a caller.Required security token [Settings]
Specifies accepted stand-alone security tokens within a consumed message. Stand-alone security tokens are those not already used for signature or encryption. Defining a required security token means that messages containing a token of that type will be processed according to the usage assertion. The security token will not be used for authentication unless it is also specified within a caller.Required security token [Settings]
Specifies accepted stand-alone security tokens within a consumed message. Stand-alone security tokens are those not already used for signature or encryption. Defining a required security token means that messages containing a token of that type will be processed according to the usage assertion. The security token will not be used for authentication unless it is also specified within a caller.Resource adapter connection factory settings
Use this panel to view or change the configuration properties of the selected resource adapter connection factory.Resource adapter properties
Use this page to configure the IBM MQ resource adapter that underlies the IBM MQ messaging provider.Resource adapters collection
Use this panel to perform the following actions on stand-alone resource adapters: view the list of resource adapter instances, install additional resource adapter archives (RAR), create additional resource adapter instances from installed RARs and delete resource adapter instances.Resource adapter settings
Use this page to specify settings for a resource adapter.Resource adapter settings
Use this panel to view or change the configuration properties of the resource adapter. These configuration properties control how resource adapters are created.Resource environment entries collection
Use this page to view configured resource environment entries. Within an application server name space, the data contained in a resource environment entry is converted into an object that represents a physical resource. This resource is frequently called an environment resource.Resource environment entry settings
Use this page to configure resource environment entries. Within an application server name space, the data contained in a resource environment entry is converted into an object that represents a physical resource. Rather than represent a connection factory, which provides connections to a resource, this object directly represents a resource. This design can make the resource available to application modules that do not run entirely on the application server. Examples include some application clients and web modules.Resource environment entry settings for application clients
Use this page to specify resource environment entry properties.Resource environment provider collection
Use this page to view resource environment providers, which encapsulate the referenceables that convert resource environment entry data into resource objects.Resource environment provider settings
Use this page to create settings for a resource environment provider.Resource environment provider settings for application clients
Use this page to specify resource environment entry properties.Resource environment references
Use this page to designate how the resource environment references of application modules map to remote resources, which are represented in the product as resource environment entries.Resource references
Use this page to designate how the resource references of application modules map to the actual resources that are configured for the application.Response consumer (receiver) binding configuration settings
Use this page to specify the binding configuration for the response consumer.Response consumer binding [Settings]
WS-Security binding for consumption of responses from outbound target.Response generator (sender) binding configuration settings
Use this page to specify the binding configuration for the response generator or response sender.Response generator binding configuration [Settings]
WS-Security binding for generation of responses to caller.Response receiver [Settings]
Draft 13 WS-Security binding for consumption of responses from a target.Response receiver binding collection
Use this page to specify the binding configuration for receiver response messages for Web Services Security.Response sender [Settings]
Draft 13 WS-Security binding for generation of responses to a caller.Response sender binding collection
Use this page to specify the binding configuration for sender response messages for Web Services Security.Retrieve from port
Use this page to retrieve a signer certificate from a remote SSL port. The system connects to the specified remote SSL host and port and receives the signer during the handshake using an SSL configuration.Review results
Use this panel to review the results from the customization and binding process for the Structured Query Language in Java (SQLJ) profiles or pureQuery bind files. Use SQLJ or IBM Optim™ PureQuery Runtime to develop data access applications that connect to DB2 databases. SQLJ is a set of programming extensions that enable a programmer to use the Java programming language to embed statements that provide SQL (Structured Query Language) database requests. IBM Optim PureQuery Runtime provides an alternate set of APIs that can be used instead of JDBC to access the DB2 database.Rewrite action settings
You can configure settings to implement a rewrite action for outbound responses handled by the proxy server. Rewriting actions define how the proxy server rewrites elements of the uniform resource locators, such as URLs in an HTML page or the redirect link in the response. Rewrite actions are often done to mask the back-end server identity with that of the proxy server.Rewriting rules collection
Use this page to define how to rewrite URLs in a request or response.Rewriting rules configuration
Rewriting rules define how the proxy server rewrites URLs. Responses that have been redirected by target servers typically return a 302 status code with a location header that defines the URL that the client should be redirected to. Rewriting this URL is necessary if the target server is not aware of the proxy servers. The redirected URL is modified to correctly point clients to the proxy server instead of directly to a target server that may not be visible to clients. Use the following properties to configure the URL rewriting rules for a proxy serverRole-based policy framework properties
Although it is very unlikely that you will need to change these properties, use this file to reference supported properties within the role-based policy framework.Route action settings
You can configure settings for a route action for a proxy server. Add a route action to define routes to local file system resources for static file serving.Routing rules
Use this topic to set the advanced configuration routing rules to ensure work requests arrive at the proper generic server cluster. From this topic you can create, delete, or modify a routing rule.Routing rules configuration
Use this topic to create the advanced configuration routing rules to ensure that work requests arrive at the proper generic server cluster.RSA token authentication settings
Use this page to configure RSA token authentication.Runtime events
Use the Runtime event pages of the administrative console to view the events published by application server classes.Runtime tasks collection
Tasks are generated by runtime components . When a task generates, information is provided so that you can accept or deny the suggested action plan. There are various types of tasks, depending on the task actions and status.Save a job
Use the page to save a job definition to the job repository.Save changes to the master repository
Use this topic to update the master repository with your administrative console changes, to discard your administrative console changes and continue working with the master repository, or to continue working with your administrative console changes that are not saved to the master repository.Scalable Vector Graphics problems
Consult this topic for problems and solutions for Scalable Vector Graphics.Scheduler configuration or topology
The scheduler uses a database to persist information concerning which tasks to run and when. Errors might occur when changing the application server topology or when changing the application or server configuration. When you change the configuration or topology, carefully consider how this action affects the scheduler.Schedulers collection
Use this page to manage scheduler configurations. Schedulers are persistent and transactional timer services that can run business logic. Each scheduler runs tasks independently and has a programming interface accessible from Java Platform, Enterprise Edition (Java EE) applications using the Java Naming and Directory Interface (JNDI). You can also manage schedulers using a Java Management Extensions (JMX) MBean. See the scheduler documentation in the Information Center for details on how to configure and use schedulers.Schedulers settings
Use this page to modify scheduler settings.Scheduler table definition
Schedulers require database tables and indices with a table prefix. This page provides reference information about the tables.Scheduler table management functions
The administration console and the WASSchedulerConfiguration MBeans provide simplified methods for creating scheduler tables and schema, verifying that the scheduler tables and schema are setup properly and are accessible and removing scheduler tables and schema.Search attached applications collection
Use this page to search for applications and other resources that are attached to a specific policy set or to search for applications and other resources that have attached service resources.Search settings
Use this page to search for information about class loaders visible to a web module (.war file) or enterprise bean (.ejb file) in an installed enterprise application. This page helps you diagnose problems with class loaders.Secure Authentication Service inbound transport settings
Use this page to specify transport settings for connections that are accepted by this server using the Secure Authentication Service (SAS) authentication protocol. The SAS protocol is used to communicate securely to enterprise beans with previous releases of the application server.Secure Authentication Service outbound transport settings
Use this page to specify transport settings for connections that are accepted by this server using the Secure Authentication Service (SAS) authentication protocol.Security Auditing detail
The Security auditing subsystem can be enabled and configured from this page, by users assigned the auditor role.Security cache settings
Use this page to configure the Web Services Secure Conversation (WS-SecureConversation) security local and distributed cache settings using the administrative console.Security custom property collection
Use this page to view and manage arbitrary name-value pairs of data, where the name is a property key and the value is a string value that can be used to set internal system configuration properties.Security custom property settings
Use this page to configure arbitrary name-value pairs of data, where the name is a property key and the value is a string value that can be used to set internal system configuration properties. Defining a new property enables you to configure a setting beyond that which is available in the administrative console.Security domain configuration. [Settings]
Configure the security settings for the security domain to which your service integration bus is assigned.Security domains collection
Security domains provide a mechanism to use different security settings for administrative applications and user applications. They also provide the ability to support multiple security settings so different application servers can use different security attributes like user registry or login configurations.Security for bus bus_name [Settings]
Configure the security settings for your service integration bus.Security role references in web applications
Web application developers or Enterprise JavaBeans (EJB) providers must use a role-name in the code when using the available programmatic security Java Platform, Enterprise Edition (Java EE) application programming interfaces (APIs) isUserInRole(String roleName) and isCallerInRole(String roleName).Security role to user or group mapping
Use this page to specify the users and groups that are mapped to the security roles that are used with the enterprise application.Security settings
Use the administrative console to modify the security settings for all applications.Security Token [Collection]
Specifies stand-alone security tokens to insert into the generated message. Stand-alone security tokens are those not already used for signature or encryption. Standard and custom security tokens may be defined by URI and local name.Security Token [Collection]
Specifies stand-alone security tokens to insert into the generated message. Stand-alone security tokens are those not already used for signature or encryption. Standard and custom security tokens may be defined by URI and local name.Security Token [Settings]
Specifies stand-alone security tokens to insert into the generated message. Stand-alone security tokens are those not already used for signature or encryption. Standard and custom security tokens may be defined by URI and local name.Security Token [Settings]
Specifies stand-alone security tokens to insert into the generated message. Stand-alone security tokens are those not already used for signature or encryption. Standard and custom security tokens may be defined by URI and local name.Select a J2C authentication alias
Use this page to select a Java 2 Connector (J2C) authentication alias for the resource that you are configuring. This page is available only when at least one security domain is defined and assigned a scope that is applicable to the resource that is being edited. Additionally, that security domain must contain at least one JAAS J2C Authentication alias. Security domains isolate J2C authentication aliases between servers.Select a server to configure logging and tracing
Use this page to select the server for which you want to configure logging and trace settings.Select current backend ID settings
Use this page to select a backend identifier for container-managed persistence (CMP) beans that contain mappings for multiple backend databases.Selecting a server and changing monitoring status
Use this page to start and stop monitoring for each server and to select a server for Tivoli Performance Viewer. You can also view the collection status for each server.Select installation options settings
Use this page to specify options for the installation of a Java Platform, Enterprise Edition (Java EE) application onto a WebSphere Application Server deployment target. Default values for the options are used if you do not specify a value. After application installation, you can specify values for many of these options from an enterprise application settings page.Self-signed certificates settings
Use this page to create self-signed certificates.Sender channel transmitters [Collection]
This pane displays the transmission queue for a IBM MQ link sender channel.Server cluster collection
Use this page to view information about and change configuration settings for a cluster. A cluster consists of a group of application servers. If one of the application servers fails, requests are routed to other members of the cluster.Server cluster settings
Use this page to view or change the configuration of a server cluster instance, and to view the local topology of a server cluster instance.Server collection
Use this topic to learn how to navigate within the administrative console to the pages where you can view information about the application servers, generic servers, Java message service (JMS) servers, and web servers that are defined for your system.Server component collection
Use this page to view information about and manage the types of server components that a specific application server uses during application processing. The list of server components varies according to the type of applications a specific application server processes.Server component settings
Use this page to view or configure a server component instance.Server configuration files: Resources for learning
Use the following links to find relevant supplemental information about administering WebSphere Application Server configuration files. The information resides on IBM and non-IBM Internet sites, whose sponsors control the technical accuracy of the information.Server default binding settings
Use this page to specify the server default bindings if you want to override the default bindings that are specified for the cell (global security) or the security domain to which the server is deployed.Server instance settings
Use this page to view and manage servant instance settings. These settings control the number of servant processes that are allowed.Server-level security settings
Use this page to enable server-level security and specify other server-level security configurations.Servers with active members collection
Use this page to determine how many high availability group members are active on a particular application server.Server template options
Use this page to select the server that you want used to create a new server template. Server templates are copies of server configuration data that can be used as a starting point for creating new servers.Server templates collection
Use this page to view the list of server templates that exist on your system.Server template settings
Use this page to specify a name and description for the new server template that you are creating. The new template is created based on the configuration of the selected server.Server Version 6.1 default policy set bindings
Use this page to specify the server Version 6.1 default policy set bindings for this server. These default bindings are used for client and provider policy set attachments for applications that are deployed to Version 6.1 servers, and for Version 6.1 applications that are deployed to Version 7.0 servers. The default bindings are used for Version 6.1 attachments unless overridden at the attachment point.Service client collection at the cell level
Use this page to view and manage service clients at the cell level. Server-based Java API for XML-Based Web Services (JAX-WS) service clients are the only clients that are displayed in this view. Java API for XML-based RPC (JAX-RPC) service clients are not displayed in this view.Service client or provider policy set bindings collection
Use this page to create, copy, and manage general policy set bindings, such as the service client or provider bindings. These bindings provide system-specific configuration, and can be reused across policy set attachments. You can select the general default bindings, create new general bindings, or use existing bindings for an attached policy set.Service client policy set and bindings collection
Use this page to attach and detach policy sets to an application, a service client, its endpoints, or operations. You can select the default bindings, create new application-specific bindings, or use existing bindings for an attached policy set. You can view or change whether the client uses the policy of the service provider.Service clients collection at the application level
Use this page to view and manage service clients at the application level.Service client settings
Use this administrative console page to manage the settings for your service clients. You can attach and detach policy sets to a service, its endpoints, or operations. You can select default bindings, create new application-specific bindings, or use existing bindings for an attached policy set. You can view or change whether the client uses the policy of the service provider.Service integration bus link routing properties [Settings]
The routing properties for a service integration bus link to a foreign service integration bus.Service integration bus links [Collection]
This pane displays links between this messaging engine and messaging engines in foreign service integration buses.Service integration bus links [Settings]
This pane displays links between this messaging engine and messaging engines in foreign service integration buses.Service integration bus subscriptions [Collection]
This collection lists the service integration bus subscriptions associated with the previously selected WS-Notification subscription.Service provider policy sets and bindings collection
You can attach and detach policy sets to an application, a service provider, its endpoints, or operations. You can select the default bindings, create new application-specific bindings, or use bindings that you created for an attached policy set. You can view or change whether the service provider can share its current policy configuration.Service providers collection at the application level
Use this page to view and manage service providers at the application level.Service providers collection at the cell level
Use this page to view and manage service providers at the cell level. Java Application Programming Interface (API) for XML-Based Web Services (JAX-WS) service providers are displayed in this view. Java API for XML Remote Procedure Call (JAX-RPC) service providers are not displayed in this view.Service provider settings
Use the Service provider settings page to manage the settings for your service providers. You can attach and detach policy sets to an application, its service, endpoints or operations. You can create new bindings, or use bindings that you have already created for an attached policy set. You can view or change whether the service provider can share its current policy configuration.Service reference settings
Use this administrative console page to manage the settings for your service references. Service references can inherit the policy sets and bindings of the service client or you can specify policy sets and bindings that are different from those of the service client.Servlet cache instance collection
A servlet cache instance is a location, in addition to the default shared dynamic cache, where dynamic cache can store, distribute, and share data. By using servlet cache instances, your applications have greater flexibility and better tuning of the cache resources. The Java Naming and Directory Interface (JNDI) name specified for the cache instance is mapped to the name attribute in the <cache-instance> tag in the cachespec.xml configuration file.Servlet cache instance settings
A servlet cache instance is a location, in addition to the default shared dynamic cache, where dynamic cache can store, distribute, and share data. By using servlet cache instances, your applications have greater flexibility and better tuning of the cache resources. The Java Naming and Directory Interface (JNDI) name specified for the cache instance is mapped to the name attribute in the <cache-instance> tag in the cachespec.xml configuration file.Session Initiation Protocol (SIP) container inbound channel settings
Use this page to configure the SIP container inbound channel settings.Session Initiation Protocol (SIP) inbound channel settings
Use this page to configure the SIP inbound channel settings.Session management custom properties
You can specify additional settings for session management through setting custom properties.Session management settings
Use this page to manage HTTP session support. This support includes specifying a session tracking mechanism, setting maximum in-memory session count, controlling overflow, and configuring session timeout.Session management tuning
WebSphere Application Server session support has features for tuning session performance and operating characteristics, particularly when sessions are configured in a distributed environment. These options support the administrator flexibility in determining the performance and failover characteristics for their environment.Session pool settings
Use this page to configure session pool settings.Session tracking options
HTTP session support also involves session tracking. You can use cookies, URL rewriting, or Secure Sockets Layer (SSL) information for session tracking.Set options settings
Use this page to specify options for the composition unit to be added to the business-level application. The product supplies default values for the options if you do not specify a value.Settings history collection for a DataPower appliance manager
Use this page to view the settings history for a DataPower appliance manager. A settings version is an automatically generated copy of the sharable appliance settings for the master appliance in a managed set.Settings version Collection
Use this page to view detailed information about a specific settings version for the appliances in a managed set. A settings version is an automatically generated copy of the shareable appliance settings for the appliances in a managed set.Shared library collection
Use this page to define a list of shared library files that deployed applications can use.Shared library reference and mapping settings
Use the Shared library references and Shared library mapping pages to associate defined shared libraries with an application or web module. A shared library is an external Java archive (JAR) file that is used by one or more applications. Using shared libraries enables multiple applications deployed on a server to use a single library, rather than use multiple copies of the same library. After you associate shared libraries with an application or module, the application or module class loader loads classes represented by the shared libraries and makes those classes available to the application or module.Shared library relationship and mapping settings
Use the Shared library relationship and Shared library relationship mapping pages to specify relationship identifiers and composition unit names for shared libraries that modules in your enterprise application reference. When installing your enterprise application, the product creates a composition unit for each shared library relationship in the business-level application that you specified on the Select installation options page of the application installation wizard.Shared library settings
Use this page to make a library file available to deployed applications.SIB service [Settings]
The service that provides service integration functions.Signed or Encrypted message part settings
Use this page to configure or create new signed or encrypted message parts. Message part bindings define how the part (which is defined in a policy set) is handled.Signed part reference default bindings settings
Use this administrative console page to configure the signed part reference general bindings and the uniform resource locator (URL) for the transform algorithms that are needed to protect the message part.Signed part settings
Use this page to define the elements of a signed part. Signed parts are used to protect message integrity and, in this case, the signed parts are being defined as part of the policy set process.Signer certificates collection
Use this page to manage signer certificates in key stores. Signer certificates are used by Java Secure Socket Extensions (JSSE) to validate certificates sent by the remote side of the connection during a Secure Sockets Layer (SSL) handshake. If a signer does not exist in the trust store that can validate the certificate sent, the handshake fails and generates an "unknown certificate" error.Signer certificate settings
Use this page to verify the general properties of the selected signer certificate.Signing information collection
Use this page to view a list of signing parameters. Signing information is used to sign and validate parts of a message including the body, time stamp, and user name token. You can also use these parameters for X.509 validation when the authentication method is IDAssertion and the ID type is X509Certificate in the server-level configuration. In such cases, you must fill in the certificate path fields only.Signing information configuration settings
Use this page to configure new signing parameters.Signing parameter configuration settings
Use this page to configure new signing parameters.Single sign-on settings
Use this page to set the configuration values for single sign-on (SSO).SIP application router collection
Use this page to create and delete SIP application routers. The Session Initiation Protocol (SIP) application router allows you to select the order in which SIP applications are run at an initial SIP request.SIP application router settings
Use this page to configure SIP application router container settings. The Session Initiation Protocol (SIP) application router allows you to select the order in which SIP applications are triggered. You can use the default application router (DAR) or specify a custom application router adhering to the SIP Servlet specification.SIP container settings
Use this page to configure the SIP container settings for Session Initiation Protocol (SIP).SIP digest authentication settings
Use this page to configure Session Initiation Protocol (SIP) digest authentication settings; these settings allow the SIP container to authenticate secured applications.SIP external domains
The external domain detail panel configures the properties for external domain routing.SIP external domains collection
The external domain collection panel provides create, remove and update capabilities for the external domain routing configuration.SIP proxy inbound channel detail
This panel displays the configuration details of the SIP proxy inbound channel.SIP proxy settings
The SIP proxy settings page contains general configuration items that affect outbound transport configuration, toleration of IP Sprayer devices, and access logging configuration.SIP routing rules collection
Routing rules enable an administrator to direct Session Initiation Protocol (SIP) traffic to a specific cluster when there is more than one cluster running SIP applications in a WebSphere Application Server Network Deployment cell.SIP routing rules detail
The routing rule detail panel provides the ability to create and modify individual rules. Since the structure of conditions is complex, the user will need to utilize a different set of panels to change the conditions associated with a rule.SIP routing rules set order
It is possible that a SIP message can match more than one routing rule but the SIP proxy will stop evaluating at the first match. Routing rules are evaluated in the order that they appear in the configuration file. The set order routing rule panel enables the administrator to change this ordering.SIP rule condition collection
Each rule contains a list of conditions that are combined using a logical AND operator. This means that all of the conditions need to be true for the rule to apply. This panel enables the user to manage the set of conditions.SIP rule condition detail
Routing rules direct SIP requests that match the condition to the selected cluster. The condition setting specifies which SIP messages match the rule. Rules only apply to the initial message of a SIP conversation and not all SIP traffic. Use this panel to create or modify a rule.SIP stack settings
Use this page to configure values for the Session Initiation Protocol (SIP) stack settings that are different from those specified in RFC 3261. The default values are the same as those specified for RFC 3261.SIP timers settings
Use this page to set values for the Session Initiation Protocol (SIP) timers that are different from those specified in RFC 3261. SIP timers provide a mechanism for session expiration.The default values are the same as those specified for RFC 3261.SIP timer summary
Request for Comments (RFC) 3261, "SIP: Session Initiation Protocol," specifies various timers that SIP uses.Situation information
The situation information is used to classify the condition that is reported by an event into a common set of situations.SOAP Roles [Collection]
Defines the SOAP roles in which this handler actsSOAP Roles [Settings]
Defines the SOAP roles in which this handler actsSpecify binding type settings
Use this page to select the type of namespace binding that you want.Specify extent of protection wizard settings
Use this security wizard page to determine whether to enable application security and restrict access to local resources. When you use the wizard, admin security is enabled by default.Specifying how much data to collect
This topic describes how to set the trace level to generate trace records in the administrative console.SPNEGO TAI custom properties configuration (deprecated)
The Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) trust association interceptor (TAI) custom configuration properties control different operational aspects of the SPNEGO TAI. You can specify different property values for each application server.SPNEGO web authentication enablement
You can enable the Simple and Protected GSS-API Negotiation (SPNEGO) as the web authenticator for WebSphere Application Server.SPNEGO web authentication filter values
The Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) web authentication filter values control different aspects of SPNEGO. Use this page to specify different filter values for each application server.SQLJ profiles and pureQuery bind files settings
Use this page to do customization and binding for the Structured Query Language in Java (SQLJ) profiles for DB2 that are included in this application. You can also use this page to do binding for pureQuery bind files in the application. You can view SQLJ profiles for other database types, but you cannot change these profiles. PureQuery bind files are only valid for DB2. Use SQLJ or pureQuery to develop data access applications that connect to DB2 databases. SQLJ is a set of programming extensions that enable a programmer to use the Java programming language to embed statements that provide SQL database requests. PureQuery provides an alternate set of APIs that can be used instead of JDBC to access the DB2 database.SSL certificate and key management
Use this page to configure security for Secure Socket Layer (SSL) and key management, certificates, and notifications. The SSL protocol provides secure communications between remote server processes or endpoints. SSL security can be used for establishing communications inbound to and outbound from an endpoint. To establish secure communications, a certificate and an SSL configuration must be specified for the endpoint.SSL configurations collection
Use this page to define a list of Secure Sockets Layer (SSL) configurations.SSL configuration settings
Use this page to define Secure Sockets Layer (SSL) configuration properties.SSL configurations for selected scopes
Use this page to display Secure Socket Layer (SSL) configurations for selected scopes, such as a cell, node, server, or cluster. From this page you can navigate to configuration panels for the following: SSL configurations, dynamic inbound and outbound endpoint SSL configurations, key stores, key sets, key set groups, key managers, and trust managers.SSL inbound channel
Use this page to determine which SSL inbound channel options to specify for the application server.Secure Sockets Layer performance tips
Use this page to learn about Secure Sockets Layer (SSL) performance tips. Be sure to consider that performance issues typically involve trade-offs between function and speed. Usually, the more function and the more processing that are involved, the slower the performance.SSL transport security policy settings
Use this page to define the secure sockets layer (SSL) transport policy configuration for policy sets.SSL transport security settings
Use this page to define the secure sockets layer (SSL) transport policy binding configuration.Stand-alone application server cluster mapping settings
You can configure settings for a stand-alone application server cluster mapping. Stand-alone application server cluster mappings are specified only for a stand-alone application server cluster custom advisor.Stand-alone custom registry settings
Use this page to configure the stand-alone custom registry.Stand-alone custom registry wizard settings
A wizard page exists in the administrative console to aid in viewing the basic settings necessary to connect the application server to an existing stand-alone custom registry. After you have viewed the basic settings, you can also modify the existing stand-alone customer registry configuration using the administrative console.Standalone LDAP registry settings
Use this page to configure Lightweight Directory Access Protocol (LDAP) settings when users and groups reside in an external LDAP directory.Standalone LDAP registry wizard settings
Use this security wizard page to provide the basic settings to connect the application server to an existing Lightweight Directory Access Protocol (LDAP) registry.Startup beans service settings
Use this page to enable startup beans that control whether application-defined startup beans function on this server. Startup beans are session beans that run business logic through the invocation of start and stop methods when applications start and stop. If the startup beans service is disabled, then the automatic invocation of the start and stop methods does not occur for deployed startup beans when the parent application starts or stops. This service is disabled by default. Enable this service only when you want to use startup beans. Startup beans are especially useful when used with asynchronous beans.Startup behavior settings
Use this page to configure when an application starts compared to other applications and to the server, and to configure whether MBeans for resources are created when an application starts.State data
Use this panel to view the current state data for a Diagnostic Provider on a selected server or cluster.State Data Quick Link or Server Selection
Use this panel to select a server or cluster to either view collected state data, or to configure state data to collect for a Diagnostic Provider.Stateful session beans failover settings (applications)
Each Enterprise JavaBeans (EJB) container provides a method for stateful session beans to fail over to other servers. Use this method to specify whether failover occurs for the stateful session beans in this application. You can also override the stateful session bean failover settings on a particular module.Stateful session beans failover settings (EJB modules)
Each Enterprise JavaBeans (EJB) container provides a method for stateful session beans to fail over to other servers. Use this method to specify whether failover occurs for the stateful session beans in this module. You can also override the stateful session bean replication settings of the parent object for this module.Static cache rules collection
This topic lists the static cache rules for a proxy server. From this topic you can create, delete, or modify a static cache rule.Static cache rule settings
Use this topic to configure a cache rule that is associated to a URI group for the proxy server. HTTP 1.1 defines a set of rules for proxy servers to cache content. Static cache rules enable these default rules to be overridden for a given address space. Before the rules have any meaning, you must enable caching on the Servers > Server Types > WebSphere proxy servers > proxy_server_name > HTTP Proxy Server Settings > Proxy settings administrative console page.Static group servers collection
Use this page to designate for a static policy which high availability group members should be made active.Static role caching properties
The static role cache holds role memberships that do not expire.String binding settings
Use this page to view or configure a string binding.Subexpression builder settings
Use this page to create and manage rules that are used by the scheduler to perform job classification based on the rules or conditions defined.Submit a job
Use this page to submit a job by specifying the job definition. The job definition can originate from the local file system.Subscriptions [Collection]
The active subscriptions for the topic space.Subscriptions [Collection]
This collection lists the subscriptions that have been created on the associated bus member or members by WS-Notification applications. Use this panel to view the information about a subscription, such as the topic on which the subscription is registered and the time at which it is currently set to expire. You can also delete a subscription using the button provided.Subscriptions [Settings]
The active subscriptions for the topic space.Sun HotSpot JVM tuning parameters (Solaris and HP-UX)
Tuning a Sun HotSpot Java virtual machine (JVM) is an iterative process where the JVM configuration is developed, data is gathered, primarily the verbosegc data, and then analyzed. Any configuration revisions are then applied on the next cycle.Supported entity types collection
Use this page to list entity types that are supported by the member repositories or to select an entity type to view or change its configuration properties.Supported entity types settings
Use this page to configure entity types that are supported by the member repositories.Symmetric signature and encryption policies settings
Use this page to create the trust context to use symmetric tokens. Using the same token for signing and validating messages and encrypting and decrypting messages increases performance. Use symmetric tokens within a trust context.System-dependent configuration properties
Do not change these system-dependent configuration properties. These properties are included for reference only.System login configuration entry settings for Java Authentication and Authorization Service
Use this page to specify a list of Java Authentication and Authorization Service (JAAS) system login configurations.System policy set collection
Use this panel to create and manage policy sets. A policy set is a named collection of policies. System policy sets, or assertions about how services are defined, are used to configure access to the trust service.System policy set settings
Use this panel to create a new system policy set or to edit information about an existing custom system policy set. System policy sets, or assertions about how services are defined, are used to configure access to the trust service.Target collection for Find results
Use this page to find targets for jobs. The page displays target names and version numbers based on the results of the Find option. You can additionally display target resources for targets that you select.Target group collection
Use this page to create and view groups of targets. Target groups make job submission easier because you can submit a job for a group of targets instead of a separate job for each target.Target group settings
Use this page to view and set the description and members of a group of targets. Target groups make job submission easier because you can submit a job for a group of targets instead of a separate job for each target.Target property settings
Use this page to view and change the properties and property values for a particular target.Target resource properties
Use this page to display a read-only view of the properties for a particular target resource as a name-value pair. Updates that you make to the target resource properties must be done at the administrative agent.Target resources collection
Use this page to display resources on targets or target groups such as servers, applications, cluster, and profiles.Target resources for targets collection
Use this page to display the status of specific resources at each target, and includes the resource ID, the name of the target, and the resource status.Target services [Collection]
A target service is one of a set that may be routed to from a gateway service.Target services [Settings]
A target service is one of a set that may be routed to from a gateway service.Target specific application status
Use this page to view mappings of deployed applications or modules to servers.Task collection
Use this page to manage tasks.Task details
This page defines information about the runtime task, the objects that the task targets, and the action plan for the task.Task settings
Use this page to modify task settings.TCP transport channel custom properties
If you are using a TCP transport channel, you can use TCP transport channel custom properties to configure internal TCP transport channel properties.TCP transport channel settings
Use this page to view and configure a TCP transport channels. This type of transport channel handles inbound TCP/IP requests from a remote client.Temporary destination prefixes [Collection]
A temporary destination prefix is a user-defined string that is used to create a temporary destination. When messaging security is enabled, users and groups require authority to create messages and send them to temporary destinations. The authority is configured in the temporary destination prefix.Temporary destination prefixes [Settings]
This pane displays the role type assignments for the selected temporary destination prefixes.Test result details
Use this panel to see additional attributes for the selected test result.Test Results
Use this panel to see the results from the server or cluster members for the selected test.Test selection
Use this panel to select one of the tests that are available for the chosen Diagnostic Provider on the chosen server or cluster.Tests Quick Link or Server Selection
Use this panel to select a Diagnostic Provider server for diagnostic tests.Third-party JMS connection factory settings
Use this panel to browse or change the configuration properties of a JMS connection factory configured for use with a third-party non-JCA messaging provider. These configuration properties control how connections are created to the JMS destinations on the provider.Third-party JMS destination settings
Use this panel to browse or change the configuration properties of the selected JMS destination for use with an associated third-party non-JCA messaging provider.Thread pool collection
Use this page to view and manage the thread pools that an application server uses. A thread pool enables components of the server to reuse threads, which eliminates the need to create new threads at run time. Creating new threads expends time and resources.Thread pool settings
Use this page to configure a thread pool that an application server uses. A thread pool enables components of the server to reuse threads, which eliminates the need to create new threads at run time. Creating new threads expends time and resources.Tier collection
You can view a list of the available tiers for the UDDI node. You can create new tiers, modify tiers, set the default tier, and delete tiers.Time mapping settings
You can configure time mapping settings for the proxy server that set routing rules to be in effect during specific time intervals. These settings can be specified for application server members or for generic server cluster members.Timer manager collection
Use this page to view the configuration properties of timer managers, which enable applications to schedule future timer notifications and to receive timer notification callbacks to application-specified listeners within a Java Platform, Enterprise Edition (Java EE) environment. The timer manager binds to the Java Naming and Directory Interface (JNDI) name space.Timer manager settings
Use this page to modify timer manager settings. Timer managers enable applications to schedule future timer notifications and to receive timer notification callbacks to application-specified listeners within a Java Platform, Enterprise Edition (Java EE) environment. The timer manager binds to the Java Naming and Directory Interface (JNDI) name space.Time stamp [Collection]
Attaches a time stamp element to the message part specified by the dialect and keyword attributes.Time stamp [Settings]
Attaches a time stamp element to the message part specified by the dialect and keyword attributes.Time zone IDs that can be specified for the user.timezone property
The following table lists the time zone IDs that you can specify for the user.timezone property.Tivoli Access Manager JACC provider configuration
You can configure the Java Authorization Contract for Containers (JACC) provider for Tivoli Access Manager to deliver authentication and authorization protection for your applications or for authentication only. Most deployments that use the JACC provider for Tivoli Access Manager to configure Tivoli Access Manager provide both authentication and authorization functionality.Tivoli Access Manager JACC provider settings
Use this page to configure the Java Authorization Contract for Container (JACC) provider for Tivoli Access Manager.Tivoli Performance Viewer summary report types
Token consumer collection
Use this page to view the token consumer. The information is used on the consumer side only to process the security token.Token consumer configuration settings
Use this page to specify the information for the token consumer. The information is used at the consumer side only to process the security token.Token generator collection
Use this page to view the token generators. The information is used on the generator side only to generate the security token.Token generator configuration settings
Use this page to specify the information for the token generator. The information is used at the generator side only to generate the security token.Token type settings
Use the administrative console to define the details about the token types. This panel is displayed differently for each different token type. Policies can be defined that specify which types of security tokens are supported as well as properties for the token type.Topic [Settings]
This pane displays the role type assignments for a topic. You can use this pane to add new assignments, and to modify and remove existing assignments.Topic collection
A JMS topic destination is used for publish and subscribe messaging. Use this panel to create or delete topic destinations, or to select a topic destination to view or change its configuration properties.Topic connection factory collection
A JMS topic connection factory is used to create connections to the associated messaging provider of JMS topic destinations, for publish and subscribe messaging.Topic Mapping [Collection]
The mapping between a topic on the service integration bus and a stream queue and subscription point provided by a IBM MQ broker.Topic Mapping [Settings]
The mapping between a topic on the service integration bus and a stream queue and subscription point provided by a IBM MQ broker.Topic namespace document [Collection]
A topic namespace can optionally have topic namespace documents applied to it that define the structure of the topics that are permitted within the namespace.Topic namespace document [Settings]
A topic namespace can optionally have topic namespace documents applied to it that define the structure of the topics that are permitted within the namespace.Topic namespace document [Settings]
A topic namespace can optionally have topic namespace documents applied to it that define the structure of the topics that are permitted within the namespace.Topics [Collection]
Topics are defined hierarchically within topic spaces. To view a topic's access roles, select the topic from the hierarchical list of topics below.Topics [Collection]
The topics that have been subscribed to from this remote messaging engine.Topic space [Settings]
A topic space is a location for publish/subscribe messaging.Topic space map entries [Collection]
The mapping between a topic space in the local bus and a topic space in the foreign bus.Topic space map entries [Settings]
The mapping between a topic space in the local bus and a topic space in the foreign bus.Topic space mapping [Settings]
The mapping between topic spaces in the local bus and topic spaces in the foreign bus.Topic spaces [Collection]
Topics are defined hierarchically within topic spaces. To view the access roles for a topic, first select the topic space that contains the topic to be viewed.Transaction resources
Use this page to review resources used by a transaction.Transaction service custom properties
WebSphere Application Server allows you to configure a number of custom properties for transaction services.Transaction service settings
Use this page to specify settings for the transaction service. The transaction service is a server runtime component that can coordinate updates to multiple resource managers to ensure atomic updates of data. Transactions are started and ended by applications or the container in which the applications are deployed.Transactions imported and prepared
Use this page to review transactions that have been imported and prepared but not yet committed.Transactions needing manual completion
Use this page to review transactions that need manual completion.Transactions retrying resources
Use this page to review transactions with resources being retried.Transactions with heuristic outcome
Use this page to review transactions that completed with a heuristic outcome.Transform algorithms settings
Use this administrative console page to select the uniform resource locator (URL) for the transform algorithms that are needed to protect the message part.Transforms collection
Use this page to view the transform algorithm that is used for processing the Web Services Security message.Transforms configuration settings
Use this page to specify the transform algorithm that is used for processing the Web Services Security message.Transport chains collection
Use this page to view or manage transport chains. Transport chains enable communication through transport channels, or protocol stacks, which are usually socket based.Transport chain settings
Use this page to view a list of the types of transport channels configured for the selected transport chain. A transport chain consists of one or more types of channels, each of which supports a different type of I/O protocol, such as TCP, HTTP, or DCS.Transport header properties best practices
You can set the REQUEST_TRANSPORT_PROPERTIES property and RESPONSE_TRANSPORT_PROPERTIES property on a Java API for XML-based RPC (JAX-RPC) client Stub, a Call instance, or a Java API for XML-Based Web services (JAX-WS) BindingProvider's RequestContext instance to enable a web services client to send or retrieve transport headers.Trust all realms
Use this page to configure which realms to grant inbound or outbound trust to.Trust anchor collection
Use this page to view a list of keystore objects that contain trusted root certificates. These objects are used for certificate path validation of incoming X.509-formatted security tokens. Keystore objects within trust anchors contain trusted root certificates that are used by the CertPath API to validate the trust of a certificate chain.Trust anchor configuration settings
Use this information to configure a trust anchor. Trust anchors point to keystores that contain trusted root or self-signed certificates. This information enables you to specify a name for the trust anchor and the information that is needed to access a keystore. The application binding uses this name to reference a predefined trust anchor definition in the binding file (or the default).Trust anchor settings
Use this page to specify the trust anchor configuration. These trust anchor certificates are used to validate the X.509 certificate that is embedded in the SOAP message.Trust and key managers settings
Use this page to specify trust and key managers for the selected SSL configuration.Trust association interceptor collection
Use this page to specify trust information for reverse security proxy servers.Trust association interceptor settings
Use this page to specify trust information for reverse security proxy servers.Trust association settings
Use this page to enable trust association, which integrates application server security and third-party security servers. More specifically, a reverse proxy server can act as a front-end authentication server while the product applies its own authorization policy onto the resulting credentials passed by the proxy server.Trusted ID evaluator collection
Use this page to view a list of trusted identity (ID) evaluators. The trusted ID evaluator determines whether to trust the identity-asserting authority. After the ID is trusted, the application server issues the proper credentials based on the identity, which are used in a downstream call for invoking resources. The trusted ID evaluator implements the com.ibm.wsspi.wssecurity.id.TrustedIDEvaluator interface.Trusted ID evaluator configuration settings
Use this information to configure trust identity (ID) evaluators.Trust managers collection
Use this page to define the implementation settings for the trust manager. A trust manager is a class that is invoked during a Secure Sockets Layer (SSL) handshake to make trust decisions about the remote end point. A default trust manager is used to validate the signature and expiration of the certificate. Custom trust managers can be plugged in to perform an extended certificate and host name check.Trust managers settings
This page enables you to view and set definitions for trust manager implementation settings. A trust manager is a class that gets invoked during a Secure Sockets Layer (SSL) handshake to make trust decisions about the remote end point. A default trust manager is used to validate the signature and expiration of the certificate. Custom trust managers can be plugged in to perform an extended certificate and hostname check.Trust Method [Settings]
Defines a trust method used to validate the identity of a trusted intermediary asserting an ID on a downstream message. When a trust method is configured, the security token defined by the caller is expected to contain an identity to be asserted.Trust Method [Settings]
Defines a trust method used to validate the identity of a trusted intermediary asserting an ID on a downstream message. When a trust method is configured, the security token defined by the caller is expected to contain an identity to be asserted.Trust service attachments collection
Use this page to view information about or manage system policy set attachments and bindings. Endpoints with at least one operation directly attached to a policy set are displayed.Trust service attachments settings
Use this page to create a new attachment to the current Trust Service Defaults policy set and binding for the four token operations: cancel, issue, renew, and validate.Trust service targets collection
Use this page to view a list of targets, which are application server service endpoints. You can manage tokens by specifying which token is to be issued when access to a specific endpoint is requested.Trust service targets settings
Use this page to specify a custom service endpoint Universal Resource Locator (URL) and to assign a custom token type to the endpoint URL.Trust service token providers collection
Use this page to view information about or manage token providers for the trust service.Trust service token provider settings
Use this page to modify information for an existing token provider.Tuning parameter custom settings
Use this page to customize tuning parameters for distributed sessions.Tuning parameter hot list
The following hot list contains recommendations that have improved performance or scalability, or both, for many applications.Tuning parameter settings
Use this page to set tuning parameters for distributed sessions.Tuning sessions
Tunnel access point group collection
Use this page to view the tunnel access point groups that are defined for your core groups. The tunnel access point group includes core group access points and tunnel peer access points for enabling communication between a DMZ Secure Proxy Server for IBM WebSphere Application Server and a WebSphere Application Server, Network Deployment cell.Tunnel access point group settings
Use this page to modify the tunnel peer access points and the core group access points that belong to this access point group. A tunnel access point group defines the access points that a set of core groups use to communicate with each other, even though they reside on opposite sides of a firewall. Access points can be either tunnel peer access points or core group access points. The core group access points enable core groups in the same cell to communicate with each other. Tunnel peer access points enable core groups residing outside of the firewall to communicate with core groups residing inside of the firewall.Tunnel peer access point collection
Use this page to view the tunnel peer access points that are defined for your core groups. Tunnel peer access points define the set of servers that provide access to core groups that reside in different cells, and one cell is located on a DMZ Secure Proxy Server for IBM WebSphere Application Server, while the other cell is located inside of the firewall. At least one tunnel peer access point must be defined for each cell, that is located on the DMZ Secure Proxy Server for IBM WebSphere Application Server, that needs to communicate with one or more of the core groups that are located inside of the firewall.Tunnel peer access point selection
Use this page to control which tunnel peer access points are associated with this tunnel access point group. You can also use this page to create new tunnel peer access points for this tunnel access point group, or delete an existing tunnel peer access points.Tunnel peer access point settings
Use this page to configure a tunnel peer access point. A tunnel peer access point is used to establish communication between core groups that are in different cells, when one of the cells is located on a DMZ Secure Proxy Server for IBM WebSphere Application Server, and the other is located inside of the firewall. A tunnel peer access point corresponds to a core group access point in the peer cell. The tunnel peer access point communication settings are specified by using one or more peer endpoints or a proxy peer.Tunnel templates collection
Use this page to view a list of the tunnel templates that are defined for a tunnel access point group. You can also use this page to create a new template, delete an existing template, or export relevant settings from the cell that is inside of the firewall to the cell that is outside of the firewall.Tunnel templates settings
Use this page to edit the properties of a tunnel access point group template.UDDI data custody policy settings
You can view or edit the data custody settings for a UDDI registry node.UDDI keying policy settings
You can view or edit the UDDI keying settings for a UDDI registry.UDDI node API policy settings
For UDDI Version 3, you can view or edit the API settings for a UDDI registry node.UDDI node collection
You can manage the UDDI nodes in this cell. Each UDDI node represents an individual UDDI registry application. A UDDI node is displayed in this list only if its underlying UDDI application is started. The status of the UDDI node can indicate whether the node is activated (available to accept API requests), deactivated (not allowing user requests), or not initialized. UDDI nodes that are not initialized require some properties to be set before they can be initialized and activated.UDDI node miscellaneous settings
You can view and edit settings for a UDDI node.UDDI node settings
You can configure the general properties for a UDDI node.UDDI Publication [Collection]
Describes the manner in which the WSDL describing an inbound service is published to a UDDI registry.UDDI Publication [Settings]
Describes the manner in which the WSDL describing an inbound service is published to a UDDI registry.UDDI Publisher collection
You can view the users that are currently registered as UDDI publishers. You can create a UDDI publisher, register a user as a UDDI publisher, assign a UDDI publisher to a tier, and delete a UDDI publisher.UDDI Publisher settings
You can view and edit the entitlements and publication limits tier for a UDDI publisher, or create a new UDDI publisher.UDDI References [Collection]
A UDDI reference describes the parameters necessary to connect to a particular UDDI registry.UDDI References [Settings]
A UDDI reference describes the parameters necessary to connect to a particular UDDI registry.UDDI Tier settings
You can configure the general properties of a UDDI publisher tier.UDDI user policy settings
You can view or edit the user policy settings for a UDDI registry node.UDDI value set policy settings
You can view or edit the value set policy settings for a UDDI registry node.Unknown user or group [Settings]
This panel lists users and groups that do not exist in the user repository but have access role definitions.Unknown users and groups [Collection]
The users and groups displayed here are not defined in the user registry, but do have roles defined. This could be because they were removed from the user repository after the role assignments were made.Update asset settings
Use this page to select whether you want replace an entire asset or update its contents. You can update asset contents by adding, deleting, or updating a single file or module in the asset, or by merging multiple files or modules into an asset. Updating an asset registers the updated files with the product management domain.Update schedule
Use this page to view or update a job and its schedule.Update the global web server plug-in configuration setting
Use this page to create or update a global plug-in configuration file. The configuration settings this file contains are based on the topology of the cell that contains the applications servers that use this web server plug-in. The web server plug-in configuration file settings determine whether an application server or the web server handles user requests.Upload asset settings
Use this page to specify the asset to register with the asset repository. You can add registered assets to a business-level application.URI group configuration
Use this topic to configure a URI group that can be mapped back to generic server clusters. When creating a URI group, ensure that you are planning for URIs that form a logical collection.URI groups
A group of URI patterns, which you define, that can be mapped back to generic server clusters. When creating a URI group, verify that you are planning for URIs that form a logical collection. From this topic, you can create, delete, or modify a URI group.URL configurations collection
Use this page to view existing Uniform Resource Locator (URL) configurations, which are sets of properties that define WebSphere Application Server connections to URLs. URLs are location names that represent electronically accessible resources, such as a directory file on a machine in a network or a document stored in a database.URL configuration settings
Use this page to define connections to Uniform Resource Locators (URLs), which are location names that represent electronically accessible resources. A collection of URL connection properties is often called a URL configuration in the WebSphere Application Server environment. The targeted resources are remote to your Application Server installation.URL provider collection
Use this page to view existing URL providers, which supply the implementation classes that are necessary for WebSphere Application Server to access a URL through a specific protocol. The default URL provider provides connectivity through protocols that are supported by the IBM Developer Kit for the Java™ Platform, compatible with the Java 2 Standard Edition Platform 1.3.1. These protocols include HyperText Transfer Protocol (HTTP) and File Transfer Protocol (FTP), which work for must URLs.URL provider settings
Use this page to configure URL providers, which support WebSphere Application Server connections to a URL over a specific protocol.URL provider settings for application clients
Use this page create new URL providers.URL providers for the Application Client Resource Configuration Tool
A URL provider implements the function for a particular URL protocol, such as HyperText Transfer Protocol (HTTP). This provider, comprised of a pair of classes, extends the java.net.URLStreamHandler and java.net.URLConnection classes.URL settings for application clients
Use this page to implement the function for a particular URL protocol, such as Hyper Text Transfer Protocol (HTTP).URLs for application clients
A Uniform Resource Locator (URL) is an identifier that points to an electronically accessible resource, such as a directory file on a machine in a network, or a document stored in a database.Usage model for using ActivitySessions with HTTP sessions
This topic describes how a Web application that runs in the WebSphere Web container can participate in an ActivitySession context.User attribute mapping for federated repositories
Use this page to set or to modify the mapping for user or group attributes of a user registry to the federated repository properties in the current realm.User Datagram Protocol (UDP) Inbound channel settings
Use this page to configure the UDP Inbound channel settings.User RunAs collection
Use this page to map a specified user identity and password to a RunAs role. This panel enables you to specify application-specific privileges for individual users to run specific tasks using another user identity.Users and groups in the bus connector role [Collection]
Users in the bus connector role are able to connect to the bus to perform messaging operations. Users can have this role either by specifically having that role, or because they are in a group with that role.Value set collection
You can view and configure the value sets that are installed in a UDDI node.Value set settings
You can view the attributes of a value set in a UDDI node.Version 6.1 default policy set bindings
Use this page to specify Version 6.1 default policy set bindings for the cell (global security). These bindings are used for both client and provider policy set attachments within Version 6.1 applications and attachments to service applications that are deployed to a Version 6.1 server. These default bindings are used for Version 6.1 attachments unless they are overridden at the attachment point or by a Version 6.1 server default binding.Viewing Data Recorded by Tivoli Performance Viewer
Use this page to view logged data from Tivoli Performance Viewer.Viewing Data with the Tivoli Performance Viewer
Use this page to view and refresh performance data for the selected server, change user and log settings, view summary reports, and information on specific performance modules.View job log
Use this page to view job log information of all jobs submitted to the job scheduler, and to download a job log to your local system.View jobs
Use the page to view the list of all jobs submitted to the job scheduler and to view information about the jobs.View saved job content
Use the page to view the xJCL content of a saved job. You might view the save content to determine if it is correct or if you must make adjustments.View saved jobs
Use the page to view the list of all jobs saved to the job repository.View schedules
Use this page to view schedule information or to cancel job schedules.View web services client deployment descriptor
Use this page to view your client deployment descriptor.View web services server deployment descriptor
Use this page to view your server deployment descriptor settings.Virtual host collection
Use this page to create and manage virtual hosts. A virtual host is a configuration that enables you manage a single server on a single machine as if the server were multiple servers each on their own host machine.Virtual host settings
Use this page to configure a virtual host instance.Virtual hosts settings
Use this page to specify virtual hosts for web modules contained in your application. Web modules can be installed on the same virtual host or dispersed among several virtual hosts.Web authentication settings
Use this page to specify the web authentication settings that are associated with a web client.Web container advanced settings
Use this page to support web container advanced settings. This support includes Network QoS and transaction class mappingWeb container custom properties
You can configure name-value pairs of data, where the name is a property key and the value is a string value that you can use to set internal system configuration properties. Define a new property to configure a setting beyond what is available in the administrative console. Following is a list of some available web container custom properties.Web container inbound transport channel settings
Use this page to view and configure a web container inbound channel transport. This type of channel transport handles inbound web container requests from a remote client.Web container request attributes
A web container provides three custom HttpServletRequest attributes that can be used to provide a servlet or a trust association interceptor (TAI) with the certificate information for a request.Web container settings
Use this page to configure the web container settings.Web container transport chain custom properties
Use this page to set custom properties for a web container transport channel.Web module deployment settings
Use this page to configure an instance of web module deployment.Web module proxy server configuration settings
Use this page to specify proxy server configuration settings for the web module.Web server collection
Use this page to configure, manage, and view information about your web servers.Web server configuration
Use this page to configure web server properties.Web server configuration file
Use this page to view or modify the contents of the Web server configuration file in your web browser. To view this administrative console page click Servers > Server Types > Web Servers > web_server_name. Under Additional Properties, click Configuration File.Web server custom properties
Use this page to view and manage arbitrary name-value pairs of data, where the name is a property key and the value is a string value that can be used to set internal system configuration properties.Web server log file
Use this page to view the log file for your web server.Web server plug-in caching properties
Use this page to view or change the caching properties for a web server plug-in.Web server plug-in configuration properties
Web server plug-in configuration properties are set on various panels of the administrative console. The table provided indicates on which panel a particular property is set.Web server plug-in configuration service property
Use this page to view or change the configuration settings for the web server plug-in configuration service.Web server plug-in properties
Use this page to view or change the settings of a web server plug-in configuration file. The plug-in configuration file, plugin_cfg.xml, provides properties for establishing communication between the Web server and the Application Server.Web server plug-in request and response optimization properties
Use this page to view or change the request and response optimization properties for a web server plug-in.Web server plug-in request routing properties
Use this page to view or change the request routing properties for a web server plug-in.Web server plug-in tuning tips
Important tips for web server plug-in tuning include how to balance workload and improve performance in a high stress environment. Balancing workloads among application servers in a network fronted by a web server plug-in helps improve request response time.Web server virtual hosts collection
Use this page create or edit virtual hosts for your Web server.Web server virtual hosts detail
Use this page create or edit virtual hosts for your Web server.Web service [Settings]
Web service gateway instances [Collection]
A web services gateway allows you to configure specific endpoint listeners and deploy gateway and proxy services to those listeners.Web service gateway instances [Settings]
A web services gateway allows you to configure specific endpoint listeners and deploy gateway and proxy services to those listeners.Web services: Client security bindings collection
Use this page to view a list of application-level, client-side binding configurations for Web Services Security. These bindings are used when a web service is a client to another web service.Web services: Server security bindings collection
Use this page to view a list of server-side binding configurations for Web Services Security.Web Services Addressing policy set binding
Use this page to modify the endpoint reference binding for Web Services Addressing (WS-Addressing). The product enforces this binding on JAX-WS web service applications that use WS-Addressing. This panel applies only to the WebSphere Application Server, Network Deployment version of the product.Web services client bindings
The client bindings define the Web Services Description Language (WSDL) file name, preferred ports and other port information. Use this page to specify the client bindings and the port mappings for the web services in a module.Web services client port information
Use this page to specify a request timeout, override an endpoint, and override a binding namespace for a web services client port.Web services implementation scope
Use this page to view and manage the scope of the ports of a Web service application.Web services security custom properties
You can configure name-value pairs of data, where the name is a property key and the value is a string value that you can use to set internal system configuration properties. Defining a new property enables you to configure a setting beyond that which is available through options in the administrative console.Web services security generic security token login module custom properties
When you configure a generic security token login module, you can configure name-value pairs of data, where the name is a property key and the value is a string value that you can use to set internal system configuration properties. You can use these configuration properties, along with the options provided in the administrative console, to control how the token is generated or consumed.Web Services Security property collection
Use this page to a view a list of additional properties for the configuration.Web Services Security property configuration settings
Use this page to configure additional security properties.Web services security SAML token custom properties
When you configure a web services security SAML token, you can configure name-value pairs of data, where the name is a property key and the value is a string value that you can use to set internal system configuration properties. You can use these configuration properties, along with the options provided in the administrative console, to control how the SAML token is generated or consumed.Web services update runtime settings
Use this page to confirm that the web services trust service runtime should be updated with the most recent configuration changes.WebSphere Application Server data source properties
Use this page to set advanced data source properties in the application server. These properties activate and configure services that the application server applies to data sources to customize connections within an application server. These properties do not affect connections within the database.WebSphere grid endpoints
Use this page to view servers or clusters that host grid applications and the data source Java Naming and Directory Interface (JNDI) names used by the WebSphere grid endpoints.IBM MQ client connection [Settings]
The connection between a IBM MQ client and the bus.IBM MQ client link [Settings]
A IBM MQ client link presents the messaging engine, and therefore the bus, as a IBM MQ queue manager to which IBM MQ clients can attach. This behavior enables WebSphere Application Server Version 5 JMS clients to use messaging resources on the bus.IBM MQ client link advanced properties [Settings]
Advanced configurable properties, such as message reliability and broker queue names, for the IBM MQ client link.IBM MQ client links [Collection]
A IBM MQ client link presents the messaging engine, and therefore the bus, as a IBM MQ queue manager to which IBM MQ clients can attach. This behavior enables WebSphere Application Server Version 5 JMS clients to use messaging resources on the bus.IBM MQ link [Settings]
The IBM MQ link connects the messaging engine as a queue manager to IBM MQ, providing a bridge between the bus and a IBM MQ network.IBM MQ link MQFAP inbound channel [Settings]
A channel that can be used in combination with the TCP Channel or other channels within the confines of IBM MQ support to facilitate communications between a WebSphere system integration bus and a IBM MQ client or queue manager.IBM MQ link receiver channel [Collection]
The receiver channel that receives messages from the gateway IBM MQ queue manager. The receiver channel communicates with a IBM MQ sender channel on the gateway queue manager, and converts MQ format messages to service integration bus messages.IBM MQ link receiver channel [Settings]
The receiver channel that receives messages from the gateway IBM MQ queue manager. The receiver channel communicates with a IBM MQ sender channel on the gateway queue manager, and converts MQ format messages to service integration bus messages.IBM MQ link receiver channel connections [Collection]
A connection that exists on the receiver channel of the IBM MQ link.IBM MQ link receiver channel connections [Settings]
A connection that exists on the receiver channel of the IBM MQ link.IBM MQ link routing properties [Settings]
The routing properties for a link to a foreign bus that represents a IBM MQ network.IBM MQ links [Collection]
The IBM MQ link connects the messaging engine as a queue manager to IBM MQ, providing a bridge between the bus and a IBM MQ network.IBM MQ link sender channel [Collection]
This pane displays the sender channel that sends messages to the gateway queue manager. The sender channel communicates with a IBM MQ receiver channel on the gateway queue manager, and converts service integration bus messages to MQ format messages.IBM MQ link sender channel [Settings]
This pane displays the sender channel that sends messages to the gateway queue manager. The sender channel communicates with a IBM MQ receiver channel on the gateway queue manager, and converts service integration bus messages to MQ format messages.IBM MQ link sender channel transmitter messages [Collection]
This pane displays the messages queued for transmission across the WebSphere MQ link sender channel.IBM MQ mediation points [Collection]
A IBM MQ mediation point is a location from which a mediation takes messages.IBM MQ mediation points [Settings]
A IBM MQ mediation point is a location from which a mediation takes messages.IBM MQ messaging provider activation specification advanced properties
Use this panel to view or change the advanced properties of the selected activation specification for use with the IBM MQ messaging provider. These advanced properties control the behavior of connections made to IBM MQ messaging provider destinations.IBM MQ messaging provider activation specification broker properties
Use this panel to view or change the broker settings of the selected activation specification for use with the IBM MQ messaging provider. These broker settings determine how the IBM MQ messaging provider interacts with a broker for the purposes of publishing messages and subscribing to topics. Updates to the settings take effect when the server is restarted.IBM MQ messaging provider activation specification client transport properties
Use this panel to view or change the client transport properties of an activation specification for use with the IBM MQ messaging provider. These properties affect how a client connection is established with a IBM MQ queue manager or queue-sharing group. Updates to the properties take effect when the server is restarted.IBM MQ messaging provider activation specification settings
Use this panel to view or change the configuration properties of the selected activation specification for use with the IBM MQ messaging provider. These configuration properties control how connections are created to associated queues and topics.IBM MQ messaging provider connection factory advanced properties
Use this panel to view or change the advanced properties of the selected connection factory for use with the IBM MQ messaging provider. These advanced properties control the behavior of connections made to IBM MQ messaging provider destinations.IBM MQ messaging provider connection factory broker properties
Use this panel to view or change the broker settings of the selected connection factory, or topic connection factory, for use with the IBM MQ messaging provider. These broker settings determine how the IBM MQ messaging provider interacts with a broker for the purposes of publishing messages and subscribing to topics. Updates to the settings take effect when the server is restarted.IBM MQ messaging provider connection factory client transport settings
Use this panel to view or change the client transport settings of a connection factory, queue connection factory, or topic connection factory for use with the IBM MQ messaging provider. Client transport properties affect how a client connection is established with a IBM MQ queue manager or queue-sharing group. Updates to the settings take effect when the server is restarted.IBM MQ messaging provider connection factory settings
Use this panel to view or change the configuration properties of the selected connection factory for use with the IBM MQ messaging provider. These configuration properties control how connections are created to associated JMS queues and topics.IBM MQ messaging provider queue and topic advanced properties settings
Use this panel to view or change the advanced properties for the selected queue or topic destination for use with the IBM MQ messaging provider. These advanced properties control the behavior of connections made to IBM MQ messaging provider destinations.IBM MQ messaging provider queue connection factory advanced properties
Use this panel to view or change the advanced properties of the selected queue connection factory for use with the IBM MQ messaging provider. These advanced properties control the behavior of connections made to IBM MQ messaging provider destinations.IBM MQ messaging provider queue connection factory settings
Use this panel to view or change the configuration properties of the selected queue connection factory for use with the IBM MQ messaging provider. These configuration properties control how connections are created to associated JMS queue destinations.IBM MQ messaging provider queue settings
Use this panel to view or change the configuration properties of the selected queue destination for point-to-point messaging with WebSphere MQ as a messaging provider.IBM MQ messaging provider topic connection factory advanced properties
Use this panel to view or change the advanced properties of the selected topic connection factory for use with the IBM MQ messaging provider. These advanced properties control the behavior of connections made to IBM MQ messaging provider destinations.IBM MQ messaging provider topic connection factory settings
Use this panel to view or change the configuration properties of the selected topic connection factory for use with the IBM MQ messaging provider. These configuration properties control how connections are created to the associated JMS topic destination.IBM MQ messaging provider topic settings
Use this panel to view or change the configuration properties of the selected JMS topic destination for publish/subscribe messaging with IBM MQ as a messaging provider.IBM MQ Provider queue connection factory settings for application clients
Use this panel to view or change the configuration properties of the selected queue connection factory for use with the IBM MQ Java Message Service (JMS) provider. These configuration properties control how connections are created between the JMS provider and IBM MQ.IBM MQ Provider queue destination settings for application clients
Use this panel to view or change the configuration properties of the selected queue destination for use with the IBM MQ product Java Message Service (JMS) provider.IBM MQ Provider topic connection factory settings for application clients
Use this panel to view or change the configuration properties of the selected topic connection factory for use with the IBM MQ Java Message Service (JMS) provider. These configuration properties control how connections are created between the JMS provider and IBM MQ.IBM MQ Provider topic destination settings for application clients
Use this panel to view or change the configuration properties of the selected topic destination for use with the IBM MQ product Java Message Service (JMS) provider.IBM MQ queue connection properties
Use this panel to specify how to connect to the queue manager that hosts the queue.IBM MQ queue points [Collection]
A IBM MQ queue point is used when sending messages to and receiving messages from a IBM MQ queue.IBM MQ queue points [Settings]
A IBM MQ queue point is used when sending messages to and receiving messages from a IBM MQ queue.IBM MQ receiver channel saved batch status [Collection]
The runtime status of message batches for the receiver channel of the IBM MQ link.IBM MQ resource custom properties settings
Use this page to specify custom properties that your enterprise information system (EIS) requires for the resource providers and resource factories that you configure. For example, most database vendors require additional custom properties for data sources that access the database.IBM MQ sender channel saved batch status [Collection]
The saved status of message batches for the sender channel saved for transmission to IBM MQ. You can choose to commit or rollback each batch.IBM MQ server [Settings]
A IBM MQ server represents a IBM MQ queue manager or (for IBM MQ for z/OS) queue-sharing group. Use this panel to view or modify the details of a IBM MQ server definition.IBM MQ server bus member [Settings]
A WebSphere MQ server bus member is used for assigning queue points and mediation points to IBM MQ queues.IBM MQ servers [Collection]
A IBM MQ server represents a IBM MQ queue manager or (for IBM MQ for z/OS) queue-sharing group.WebSphere relational resource adapter settings
Use this page to view the settings of the WebSphere relational resource adapter. This adapter is preinstalled in the product to provide access to relational databases.WebSphere variables collection
Use this page to view and change the defined product variables with their values. You can also use this page to create a new variable, or delete an existing variable. These variables are name and value pairs that are used to provide the settings for the string data type configuration attributes that are contained in one of the XML formatted configuration files that reside in the product repository.WebSphere variables settings
Use this page to define the name and value of a WebSphere variable. A WebSphere variable is a name and value pair that is used to provide the setting for one of the string data type attributes contained in one of the XML formatted configuration files that reside in the product repository.Welcome
Display products that are installed that use the Integrated Solutions Console for administrative tasks.Welcome to the job management console
The job management console is a stand-alone web interface for users to perform job operations.Where to perform WebSphere Application Server operations
Administering WebSphere Application Server involves the use of both the MVS™ console and the WebSphere Application Server administrative console.Work area partition collection
Use this page to manage the work area service.Work area partition settings
Use this page to modify the work area partition settings.Work area service settings
Use this page to manage the work area service.Work manager collection
Use this page to view the collection properties of work managers, which contain a pool of threads bound into the Java Naming and Directory Interface.Work manager settings
Use this page to modify work manager settings. Work managers contain a pool of threads that are bound into Java Naming and Directory Interface.Writable SAF Keyring settings
Use this page to manage existing writable System Authorization Facility (SAF) keyrings on the z/OS platform.WS-Addressing policy settings
Use this page to define the appropriate WS-Addressing policy assertions for this policy set.WS-Notification Service client settings
Use this page to manage policy sets and bindings or to access additional information for this WS-Notification service client.WS-Notification service points [Collection]
A WS-Notification service point defines access to a WS-Notification service on a given bus member through a specified web service binding (for example SOAP over HTTP). Applications use the bus members associated with the WS-Notification service point to connect to the WS-Notification service.WS-Notification service points [Settings]
A WS-Notification service point defines access to a WS-Notification service on a given bus member through a specified web service binding (for example SOAP over HTTP). Applications use the bus members associated with the WS-Notification service point to connect to the WS-Notification service.WS-Notification services [Collection]
A WS-Notification service provides access to service integration bus resources for web services publish and subscribe clients.WS-Notification services [Settings]
A WS-Notification service provides access to service integration bus resources for web services publish and subscribe clients.WS-ReliableMessaging policy binding
To configure a web service application to use WS-ReliableMessaging, you attach a policy set that contains a WS-ReliableMessaging policy type. This policy type offers a range of qualities of service: managed persistent, managed non-persistent, or unmanaged non-persistent. The managed qualities of service, managed persistent and managed non-persistent, are supported by the service integration bus. Use this page to select the bus and messaging engine to use for the reliable messaging protocol state.WS-ReliableMessaging settings
For the WS-ReliableMessaging policy you can configure the version of the WS-ReliableMessaging standard that you want to use, the order in which messages are delivered, and the required quality of service (the reliability level) for message delivery. The product can enforce these policies on inbound messages and applies them to outbound messages.WS-Security authentication and protection
Use the links on this page to configure authentication, protection, signature, and encryption information that the policy requires.WS-Security authentication and protection for application specific bindings
Use the links on this page to configure authentication, signature, and encryption information that the policy requires when using application specific bindings.WS-Security authentication and protection for general bindings
Use the links on this page to configure authentication, protection, signature, and encryption information that the policy requires when using general bindings.WS-Security bindings [Collection]
WS-Security bindings for consumption and generation of requests and responses.WS-Security configurations [Collection]
WS-Security configurations for inbound and outbound services.WS-Security policy settings
Use this page to configure the WS-Security policy and apply a message security WS-Security profile to requests. WS-Security policies are applied to requests and enforced on responses to support inter-operability.WS-Transaction policy settings
Use this page to specify the policies for the WS-AtomicTransaction (WS-AT) and WS-BusinessActivity (WS-BA) protocols. WS-AT supports coordination of activities so that either all the activities occur, or none of them occur. WS-BA supports coordination of activities that are more loosely coupled than atomic transactions, and that therefore, require a compensation process if an error occurs.X.509 certificate configuration settings
Use this page to specify a list of untrusted, intermediate certificate files. This collection certificate store is used for certificate path validation of incoming X.509-formatted security tokens.X.509 certificates collection
Use this page to view a list of untrusted, intermediate certificate files. This collection certificate store is used for certificate path validation of incoming X.509-formatted security tokens.z/OS location service daemon settings
In a cell, one location service daemon definition exists for each sysplex node group. A location service daemon process runs on each system that has a node in a sysplex node group in that cell. When a client makes a remote call to an enterprise bean, a location service daemon determines which server or servers are eligible to process the request, and routes the request to the selected server. An example of a system is the z/OS operating system on a logical partition (LPAR).z/OS Profile Management Tool security settings
The z/OS Profile Management Tool allows you to specify System Authorization Facility (SAF) profile prefixes (previously referred to as z/OS security domains) for your WebSphere Application Server for z/OS configuration.z/OS System Authorization Facility authorization
Use this page to configure the System Authorization Facility (SAF) and the SAF Authorization properties.z/OS Secure Authentication Service settings
Use this page to specify authentication settings for requests that are received and sent by a server that uses the z/OS authentication protocol. Use the z/OS Secure Authentication Service (z/SAS) protocol to communicate securely to enterprise beans.z/OS security options
Use this page to determine which Global security options to specify for the application server for z/OS.


File name: welc_ref_adm_help.html