Answer:
1) JMS (Java Message Service) is a standard API for accessing enterprise messaging systems.Specifically, WebLogic JMS
2) Enables Java applications sharing a messaging system to exchange messages.
3) Simplifies application development by providing a standard interface for creating, sending, and receiving messages.Using the Administration Console,
you define configuration attributes to:
1.. Create JMS servers and target a WebLogic Server instance or a Migratable Target where the JMS server will be deployed.
2. Create and/or customize values for JMS servers, connection factories, destinations (queues and topics), JMS templates, destination sort order (using destination keys), persistent stores (file or JDBC), paging stores, session pools, and connection consumers.
3. Define message and/or bytes thresholds and quotas, as well as a maximum allowable message size onyour JMS servers, destinations, and templates.Enable any desired WebLogic JMS features, such as:
Server clustering using multiple connection factories.
i) High availability and load balancing for destinations across a cluster by using distributed destinations.
ii) Persistent messages and durable subscribers.
iii) Paging out message bodies during peak load periods to free up memory
iv) Controlling message flow during peak load periods, including blocking message producers.
v)Establishing a message expiration policy to ensure that expired messages are cleaned up immediately.
vi)Preventing message quota errors by temporarily blocking message producers from sending messagesto a destination when it exceeds its specified maximum message quota.
vi) Concurrent message processing via session pools.
1) JMS (Java Message Service) is a standard API for accessing enterprise messaging systems.Specifically, WebLogic JMS
2) Enables Java applications sharing a messaging system to exchange messages.
3) Simplifies application development by providing a standard interface for creating, sending, and receiving messages.Using the Administration Console,
you define configuration attributes to:
1.. Create JMS servers and target a WebLogic Server instance or a Migratable Target where the JMS server will be deployed.
2. Create and/or customize values for JMS servers, connection factories, destinations (queues and topics), JMS templates, destination sort order (using destination keys), persistent stores (file or JDBC), paging stores, session pools, and connection consumers.
3. Define message and/or bytes thresholds and quotas, as well as a maximum allowable message size onyour JMS servers, destinations, and templates.Enable any desired WebLogic JMS features, such as:
Server clustering using multiple connection factories.
i) High availability and load balancing for destinations across a cluster by using distributed destinations.
ii) Persistent messages and durable subscribers.
iii) Paging out message bodies during peak load periods to free up memory
iv) Controlling message flow during peak load periods, including blocking message producers.
v)Establishing a message expiration policy to ensure that expired messages are cleaned up immediately.
vi)Preventing message quota errors by temporarily blocking message producers from sending messagesto a destination when it exceeds its specified maximum message quota.
vi) Concurrent message processing via session pools.
No comments:
Post a Comment