com.ibm.websphere.appserver.internal.jms-1.1 · com.ibm.websphere.appserver.internal.jms-1.1
Group: com.ibm.websphere.appserver.features - All Dependencies
bluemixUtility-1.0
23.0.0.8
Bluemix Utilities 1.0 · This feature has been stabilized and is discontinued in fix pack 20.0.0.7. The Bluemix Utility feature can be used to quickly and easily configure access to IBM Bluemix managed services.
batchManagement-1.0
19.0.0.7
Batch Management 1.0 · This feature provides managed batch support for the Java batch container. This includes the Batch REST management interface, job logging support, and a command line utility for external scheduler integration.
apiDiscovery-1.0
23.0.0.8
API Discovery 1.0 · Enables discovery and exposure of REST APIs within Liberty.
usageMetering-1.0
23.0.0.8
Usage Metering 1.0 · This feature has been stabilized. The usageMetering feature registers the software with IBM WebSphere Automation for server registration and usage reporting.
audit-1.0
19.0.0.1
Audit 1.0 · The Liberty Audit feature is used to report and track auditable events to ensure the integrity of your system. The Liberty Audit feature introduces an infrastructure which serves two purposes: - Confirming the effectiveness and integrity of the existing configuration - Identifying areas where improvement to the configuration may be needed The Liberty Audit feature has the ability to capture the following auditable events: - Basic authentication - Start and stop of the Audit service - Form login - Client certificate login - Servlet runAs delegation - Form logout - Servlet 3.0 login, logout and authenticate APIs The Liberty Audit feature supports the Cloud Auditing Data Federation (CADF) event model. The CADF model describes a data model and associated schema definitions for an audit event. The feature provides a default implementation, the AuditFileHandler, which emits human-readable audit records to a file-based log. Each audit record is emitted in JSON format.
zosSecurity-1.0
23.0.0.8
z/OS SAF Integration 1.0 · This feature enables the server to use the SAF Registry in the z/OS platform for authenticating users and authorizing access to applications.
wsSecuritySaml-1.1
19.0.0.7
WSSecurity SAML 1.1 · This feature enables the SAML Assertion in the Web Service Security version 1.1 function.
wsAtomicTransaction-1.2
19.0.0.12
WS-AT Service 1.2 · This feature enables support for Atomic Transaction for XML-Based Web Services 2.2.
wmqJmsClient-2.0
23.0.0.8
JMS 2.0 Client for IBM MQ · This feature provides applications with access to message queues hosted on IBM MQ through the JMS 2.0 API.
rtcommGateway-1.0
23.0.0.8
WebRTC Rtcomm Gateway 1.0 · This feature allows the Rtcomm framework to connect with SIP networks.
mediaServerControl-1.0
23.0.0.8
Media Server Control 1.0 · The Liberty Media Server Control feature (mediaServerControl-1.0) enables the ability to access media servers via the JSR309 API. For applications to use this API, a driver implementation of JSR309 must be installed.
mdb-3.1
23.0.0.8
Message-Driven Beans 3.1 · This feature enables the use of Message-Driven Enterprise JavaBeans. MDBs allow asynchronous processing of messages within a Java EE component.
jms-1.1
23.0.0.8
Java Message Service 1.1 · This feature enables the configuration of resource adapters to access messaging systems using the Java Message Service API. This also includes the configuration JMS connection factories, queues, topics and activation specifications. Any JMS resource adapter that complies with the JCA 1.6 specification can be used.
com.ibm.websphere.appserver.wss4j-1.0 · com.ibm.websphere.appserver.wss4j-1.0
com.ibm.websphere.appserver.requestProbeJDBC-1.0 · com.ibm.websphere.appserver.requestProbeJDBC-1.0
com.ibm.websphere.appserver.internal.mdb-3.1 · com.ibm.websphere.appserver.internal.mdb-3.1
clusterMember-1.0
23.0.0.8
Static Cluster Member 1.0 · This feature allows a collective member to participate in a static cluster.
heritageAPIs-1.0
23.0.0.8
WebSphere Application Server Heritage APIs · Some of these APIs were created prior to specification standards and are not strategic in their use for creating portable applications. We encourage developers to create applications that are as portable as possible by using specification standards. So we only encourage the use of the heritage APIs for the migration of existing applications from traditional WebSphere to Liberty and we discourage the use of these APIs for new applications or maintaining existing applications.
wmqMessagingClient-3.0
23.0.0.8
Messaging 3.0 Client for IBM MQ · This feature provides applications with access to message queues hosted on IBM MQ through the Jakarta Messaging 3.0 API.
heritageAPIs-1.1
23.0.0.8
WebSphere Application Server Heritage APIs · APIs from traditional WebSphere Application Server to aid in the migration of existing applications to Liberty. Many of these APIs were created before specification standards and are no longer strategic. We discourage the use of these heritage APIs for new development and recommend that specification standards and modern programming models be used instead.
scalingMember-1.0
23.0.0.8
Scaling Member 1.0 · The Scaling Member feature allows a Liberty clustered server to be managed by a Liberty Scaling Controller server. The Scaling Controller directs the Scaling Member to start and stop based on Scaling Controller policies.
scalingController-1.0
23.0.0.8
Scaling Controller 1.0 · The Scaling Controller feature manages Liberty clusters by starting and stopping servers based on Scaling Policy.
healthManager-1.0
23.0.0.8
Health Manager 1.0 · The Health Manager feature provides health monitoring and automatic actions based on Health Policy.
