Websphere Application Server

Rating

Version 22.3.1
Updated 2022-10-12
Version 22.3.1
Updated 2022-10-12

IBM WebSphere Application Server (WAS) is a fast, flexible Java application server runtime environment. The WebSphere Application Server integration for the Digital.ai DevOps Products can:

Steps

  • was.UnmanagedWebServer: WebShere Configured with Unmanaged Web Server

  • was.WmqServer: A WebSphere MQ server provides a direct client connection between a service integration bus and queues on a WebSphere MQ queue manager or (for WebSphere MQ for z/OS) queue-sharing group.

  • was.EarModule: EAR with values configured for a deployment.

  • was.WarModule: WAR with values configured for a deployment.

  • was.EjbModule: EJB with values configured for a deployment.

  • was.EmbeddedWebModule: WebShere Configured with Embedded Web Module

  • was.EmbeddedEjbModule: WebShere Configured with Embedded EJB Module Spec for deployment

  • was.SessionManager: Session manager properties to control the behavior of Hypertext Transfer Protocol (HTTP) session support.

  • was.ResRef: WebShere Configured with Extensible Embedded Deployed

  • was.EjbRef: Allows you to specify JNDI names of EJBs that are bound to ejb-refs.

  • was.ResourceEnvRef: Allows you to specify JNDI names of resources defined in WebSphere Application Server configuration that are bound to resource-env-refs.

  • was.ResourceRef: Allows you to specify JNDI names of resources defined in WebSphere Application Server configuration that are bound to resource-refs.

  • was.Resource: Base class for all deployed JEE resource configuration items.

  • was.ConfigResource: Base class for all deployed JEE AdminConfig resource configuration items .

  • was.JmsResource: Base class for all deployed JMS resource configuration items.

  • was.JmsConnectionFactory: WebShere Configured with JMS Connection Factory for deployment

  • was.V5DefaultQueue: Queue destinations provided for point-to-point messaging by the internal WebSphere JMS provider. Use WebSphere Queue Destination administrative objects to manage queue destinations for the internal WebSphere JMS provider. NOTE: The queue name must also be added to the list of queue names in the configuration of the JMS server(s) where the queue is to be hosted.

  • was.V5DefaultTopic: Specifies the topic destinations for publish and subscribe messaging by the internal WebSphere JMS provider. Use WebSphere topic destination administrative objects to manage topic destinations for the internal WebSphere JMS provider.

  • was.V5DefaultQueueConnectionFactory: Specifies a topic connection factory, which is used to create connections to the associated JMS provider of JMS queue destinations for point-to-point messaging. Use WebSphere queue connection factory administrative objects to manage queue connection factories for the internal WebSphere JMS provider.

  • was.V5DefaultTopicConnectionFactory: Specifies a topic connection factory, which is used to create connections to the associated JMS provider of JMS topic destinations for publish and subscribe messaging. Use WebSphere topic connection factory administrative objects to manage topic connection factories for the internal WebSphere JMS provider.

  • was.WmqDestination: WebShere Configured with WmqDestination

  • was.WmqQueue: Queue destinations provided for point-to-point messaging by the WebSphere MQ JMS provider. Use WebSphere MQ queue destination administrative objects to manage queue destinations for the WebSphere MQ JMS provider.

  • was.WmqTopic: Topic destinations provided for publish and subscribe messaging by the WebSphere MQ JMS provider. Use WebSphere MQ topic destination administrative objects to manage topic destinations for the WebSphere MQ JMS provider.

  • was.WmqConnectionFactory: WebShere Configured with Wmq Connection Factory

  • was.WmqQueueConnectionFactory: Queue connection factory is used to create connections to the associated JMS provider of JMS queue destinations, for point-to-point messaging. Use WebSphere MQ queue connection factory administrative objects to manage queue connection factories for the WebSphere MQ JMS provider.

  • was.WmqTopicConnectionFactory: Topic connection factory is used to create connections to the associated JMS provider of JMS topic destinations, for publish and subscribe messaging. Use WebSphere MQ topic connection factory administrative objects to manage topic connection factories for the WebSphere MQ JMS provider.

  • was.WmqActivationSpecification: Specifies a WMQ Activation Specification. Resource valid only with WAS 7.0 and later application servers.

  • was.JmsProvider: Specifies a JMS Provider.

  • was.GenericJmsDestination: WebShere Configured with Generic JMS Destination

  • was.GenericJmsQueue: Specifies a queue (for point-to-point messaging).

  • was.GenericJmsTopic: Specifies a topic (for Publish and subscribe messaging) provided by the selected generic JMS provider.

  • was.GenericJmsConnectionFactory: WebShere Configured with Generic JMS Connection Factory

  • was.GenericJmsQueueConnectionFactory: Specifies a JMS connection factory that is used to create connections to the associated JMS provider for JMS destinations.

  • was.GenericJmsTopicConnectionFactory: Specifies a JMS connection factory that is used to create connections to the associated JMS provider for JMS destinations.

  • was.SibResource: Base class for all deployed SIB resource configuration items.

  • was.SibJndiResource: Base class for all deployed SIB JNDI resource configuration items.

  • was.SibQueue: 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.

  • was.SibTopic: JMS topic is used as a destination for publish/subscribe messaging.

  • was.SibConnectionFactory: WebShere Configured with SIB Connection Factory

  • was.SibQueueConnectionFactory: 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.

  • was.SibTopicConnectionFactory: 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.

  • was.SibDestination: Base class for all deployed SIB destionation configuration items.

  • was.SibQueueDestination: Queue for point-to-point messaging.

  • was.SibTopicSpaceDestination: Topic space is a location for publish/subscribe messaging.

  • was.J2CResourceAdapter: Specifies and installs a stand-alone resource adapter archive (RAR) file.

  • was.J2CResource: Base type for all WebSphere J2C objects.

  • was.J2CAdminObject: Specifies the admin object definitions for the resource adapter.

  • was.J2CActivationSpecification: Specifies the activation specification definitions for the resource adapter.

  • was.J2CConnectionFactory: Specifies the connection factory definitions for the resource adapter.

  • was.Datasource: Base class for all deployed data source configuration items.

  • was.DB2Datasource: Base class for all deployed DB2 data source configuration items.

  • was.DB2Type2Datasource: DB2 type 2 data source object supplies your application with connections for accessing the database.

  • was.DB2Type4Datasource: DB2 type 4 data source object supplies your application with connections for accessing the database.

  • was.OracleDatasource: Oracle data source object supplies your application with connections for accessing the database.

  • was.MsSqlDatasource: MsSql data source object supplies your application with connections for accessing the database.

  • was.DerbyDatasource: Derby data source object supplies your application with connections for accessing the database.

  • was.JaasAlias: Specifies a user identity and password for Java(TM) 2 connector security to use. Targets Global Security.

  • was.VirtualHost: Virtual host with a unique set of Web access ports. Such a configuration lets a single host machine resemble multiple host machines. Each virtual host has a logical name and a list of one or more domain name system (DNS) aliases by which it is known.

  • was.SharedLibrary: Container-wide shared library that can be used by deployed applications.

  • was.JdbcProvider: WebShere Configured with JDBC provider for deployment

  • was.OracleJdbcProvider: WebShere Configured with Oracle JDBC Provider

  • was.OracleXaJdbcProvider: WebShere Configured with Oracle XaJDBC Provider

  • was.ListenerPort: Specifies listener ports upon which message-driven beans listen for messages. Message listener ports must be configured at the server scope.

  • was.ThreadPool: A thread pool enables server components to reuse threads instead of creating new threads at run time.

  • was.WorkManagerProvider: Specifies a work manager that contains a pool of threads that are bound into the Java(TM) Naming and Directory Interface (JNDI).

  • was.WorkManager: A work manager is a thread pool created for Java Platform, Enterprise Edition (Java EE) applications that use asynchronous beans.

  • was.TimerManager: Timer manager enables applications to schedule future timer notifications and receive timer notification callbacks to application-specified listeners.

  • was.Scheduler: Schedulers are persistent and transactional timer services that can run business logic.

  • was.ResourceEnvironmentEntry: Within an application server name space, the data contained in a resource environment entry is converted into an object that represents a physical resource.

  • was.ResourceEnvironmentProvider: Specifies a resource environment provider, which encapsulates the referenceables that convert resource environment entry data into resource objects.

  • was.ServicePolicy: WebShere Configured Service Policy

  • was.Variable: Variables specify a level of indirection for some system-defined values

  • was.CustomService: Custom services defines a class that is loaded and initialized whenever the server starts and shuts down.

  • was.StringNameSpaceBinding: Specifies a String namespace binding.

  • was.IndirectNameSpaceBinding: Specifies a name binding of an object which can be looked up using JNDI.

  • was.EjbNameSpaceBinding: Specifies a name binding of an enterprise bean home that has already been configured on a server within the cell.

  • was.ServletCacheInstance: A servlet cache instance is a location, in addition to the default shared dynamic cache, where dynamic cache can store, distribute, and share data.

  • was.MailProvider: Specifies the mail provider that the application server uses.

  • was.MailSession: Specifies a mail Session.

  • was.URLProvider: Specifies the URL providers to access URL resources through different protocols.

  • was.URL: Specifies uniform resource locators (URLs), which point to electronically accessible resources, such as a directory file on a machine in a network or a document stored in a database.

  • was.HealthBaseConditionSpec: Base Condition for Health Policy conditions.

  • was.HealthBaseCondition: Base Condition for Health Policy conditions.

  • was.HealthConditionAge: Tracks the amount of time that the server is running. If the amount of time exceeds the defined threshold, the health actions run.

  • was.HealthConditionWorkload: Specifies a number of requests that are serviced before policy members restart to clean out memory and cache data.

  • was.HealthConditionMemoryLeak: Tracks consistent downward trends in free memory that is available to a server in the Java heap. When the Java heap approaches the maximum configured size, you can perform either heap dumps or server restarts.

  • was.HealthConditionExcessiveMemory: Tracks the memory usage for a member. When the memory usage exceeds a percentage of the heap size for a specified time, the health actions run.

  • was.HealthConditionExcessiveResponseTime: Tracks the amount of time that requests take to complete. If the time exceeds the defined response time threshold, the health actions run.

  • was.HealthConditionExcessiveRequestTimeout: Specifies a percentage of HTTP requests that can time out. When the percentage of requests exceeds the defined value, the health actions run.

  • was.HealthConditionStormDrain: Tracks requests that have a significantly decreased response time.

  • was.HealthConditionGarbageCollectionPercentage: Monitors a Java virtual machine (JVM) or set of JVM’s to determine whether they spend more than a defined percentage of time in garbage collection during a specified time period.

  • was.HealthBaseActionSpec: Base Health Action.

  • was.HealthBaseAction: Base Health Action.

  • was.HealthActionRestartServer: Health action to restart a server.

  • was.HealthActionHeapDump: Health action to take heap dumps.

  • was.HealthActionThreadDump: Health action to take thread dumps.

  • was.HealthActionSetMaintenanceMode: Health action to put a server into maintenance mode.

  • was.HealthActionSetMaintenanceModeBreakAffinity: Health action to put a server into maintenance mode and break HTTP and SIP request affinity to the server.

  • was.HealthActionSetMaintenanceModeStop: Undocumented.

  • was.HealthActionUnsetMaintenanceMode: Health action to take a server out of maintenance mode.

  • was.HealthActionSendSnmpTrap: Health action to generate a SNMP (Simple Network Management Protocol) trap.

  • was.HealthPolicy: Health policies define a condition and a set of actions to undertake when the condition is breached.

  • was.HealthPolicyMembership: Marks a container member of a health policy.

  • was.Keystore: Defines keystore types, including cryptography, Resource Access Control Facility (RACF??), Certificate Management Services (CMS), Java, and all trust store types.

  • was.CopiedKeystoreFile: Specifies Copied Keystore File for deployment

  • was.SSLConfig: The SSL protocol provides secure communications between remote server processes or endpoints.

  • was.DynamicSSLConfigSelection: Dynamic endpoint configuration scopes represent an association between an Secure Sockets Layer (SSL) configuration and target protocol, host, and port.

  • was.SiBus: 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.

  • was.SiBusMember: Bus members are the servers, WebSphere MQ servers and clusters that have been added to the bus.

  • was.ConfigurationResource: Base class for all container configuration CIs.

  • was.ServerConfigurationResource: Base class for all Server configuration CIs.

  • was.NodeConfigurationResource: Base class for all NodeAgent configuration CIs.

  • was.ApplicationServer: Server-specific Application Settings.

  • was.ServerPort: Specifies the TCP/IP ports this server uses for connections. Name the CI after the endpoint name you want to modify.

  • was.ORBService: Specifies settings for the Object Request Broker service.

  • was.TransactionService: Specifies settings for the transaction service, as well as manage active transaction locks.

  • was.EJBContainer: Configure and manage the EJB container of this application server.

  • was.WebContainer: Configure and manage the EJB container of this application server.

  • was.PMIService: Specifies the PMIService configuration for Server.

  • was.JavaProcessDefinition: Configure and manage the process definition of this application server.

  • was.LoggingAndTracing: Configure and manage the logging and tracing settings of this application server.

  • was.CoreGroupService: Configure and manage the core group service of this application server.

  • was.ServerSessionManager: Session manager properties to control the behavior of Hypertext Transfer Protocol (HTTP) session support.

  • was.TransportChain: Configure and manage transport chains which represent network protocol stacks that are operating within a client or server.

  • was.TransportChannelSpec: Base class for all transport channel subtypes.

  • was.TransportChannel: Base class for all transport channel subtypes.

  • was.HTTPInboundChannel: Configure a channel for handling inbound HTTP requests from a remote client.

  • was.FileSynchronizationService: Service ensures that configuration changes made to the cell repository are propagated to the appropriate node repositories.

  • was.CustomProperties: Specifies custom properties for a WebSphere container except was.Cluster.

  • was.CoreGroup: A core group is a grouping of WebSphere(R) Application Server cell processes. A core group can contain stand-alone servers, cluster members, node agents, and the deployment manager.

  • was.HAManagerPolicy: Base type for all HAManagerPolicy subtypes.

  • was.AllActivePolicy: Specifies a policy that automatically activates all group members.

  • was.NoOpPolicy: Specifies a policy in which no group members are automatically activated.

  • was.StaticPolicy: Specifies a policy that activates group members on all of the servers in the list.

  • was.OneOfNPolicy: Specifies a policy that keeps one group member active at all times.

  • was.MOfNPolicy: Specifies a policy that keeps a number of group member active at all times.

Authored By

Digital.ai

Digital.ai support

We would be happy to help you!