WebSphere XD provides extended qualities of services (QOS) for WebSphere Platform. Operation policies, goals based workload management, autonomic management of server processes, application partitioning and enhanced administration controls are the foundational features of WAS XD.

	Heavy long-running applications
	Memory leakage and heap dump problems
	Very slow and deadly response
	Manually start/stop servers
	Limited admin console visualization

How to overcome all these problems in WebSphere Application Server Network Deployment?

Answer is WAS-XD (Websphere XD).

The Evolution of the WebSphere Extended Deployment family of Products

Benefits of WebSphere Extended Deployment (Websphere XD) include:

• Provides virtualization capabilities that can dynamically match available resources to changing workload demands
• Provides fast application performance using powerful distributed cache to speed application access to data
• Increase application availability, resiliency, and performance improving quality of service
• Deliver resources dynamically to your highest priority applications
• Features virtualization, and workload and health management for PHP, BEA WebLogic, JBoss, Apache Tomcat and WebSphere Application Server Community Edition application environments
• Achieve interruption-free application upgrades by running multiple production versions
• Offers enhanced capabilities in job scheduling, monitoring and management for batch-type workloads
• Avoid costly duplication of resources by combining transactional and batch-type workloads on distributed platforms, increasing operational efficiency and resource utilization.
• Delivers customizable health policies and actions to help enhance manageability of applications
• Supports innovative and highly scalable data fabrics to accelerate data-intensive application performance
• Provides flexible purchase options to give you choices in satisfying your business requirements.
• High availability and fault tolerance

Common Extended Services FAQs asked to our gurus

Question # 1: What is Dynamic Cluster introduced in WAS-XD and how it valuable for my current WebSphere Application Server environment.

Answer: Dynamic operations features enable a virtualized, dynamic environment for goal-oriented workload management, to take better advantage of hardware resources in a distributed environment. It provides several advanced features for enhanced administration, including the ability to manage and seamlessly roll out multiple editions of an application. The dynamic cluster feature will automatically start and stop application server energies based on varying workload and the service policy that has been assigned to the workload

Question # 2: How to overcome memory leakage problem in WebSphere Application Server, is it possible in WAS-XD?

Answer: One of the features of WAS-XD is to provide health policies, which monitor the health of your applications and application servers by defining default policy or custom policy. In order to set-up a health policy, you can configure it to take action like restart server, take jvm heap dumps and also define detection level in which administrator will be notified, both in the console and via e-mail in case of memory leakage. You can enable these policies on server/node, Clusters, Dynamic Cluster and Cell.  

Question # 3: I have different application server WebSphere and non-WebSphere, currently working in my environment, how I can manage that through centralized administration consol.

Answer: You required WAS-XD using WebSphere XD Virtual Enterprise to manage your all WebSphere and non-WebSphere application like BEA, Tomcat, JBoss, WebSphere Community Edition and .NET in one administrator console. You can also create a cluster for these servers into a WebSphere Virtual Enterprise dynamic cluster.  

Question # 4: How checkpoint and repositioning information is persisted? Is it updated within the same unit-of-work as the business data? What does the developer have to do to leverage checkpoint and restart functions?

Answer: First to level-set: "checkpointing" is the idea of committing work periodically and keeping track of how much work has been completed; "restart" is the idea of resuming a job from its last checkpoint. This is important for batch because we're dealing with the processing of large volumes of data. If near the end of the processing the batch job fails, we should not be forced to start the work from scratch, but rather we should resume the work from some saved point in time. Checkpointing and job restartability are fundamental qualities of service within the domain of batch processing; the challenge isn't necessarily to simply provide these features, but to do so in a way that is transparent and non-intrusive to the application (and therefore the developer).

A checkpoint interval is a single JTA transaction where multiple records are processed under same global transaction context. The checkpoint algorithm specified demarcates the checkpoint interval. There are two checkpoint algorithms provided out-of-the-box: record-based, where the JTA transaction is committed after N records have been processed; and time-based, where the JTA transaction is committed after at least N seconds have elapsed. By implementing a Websphere XD Compute Grid interface and referencing the new algorithm's implementation class in the xJCL job description, users can create custom checkpoint algorithms if they wish.

For more information, please dial 1-630-355-6292 (Monday - Friday: 8AM to 6PM), alternatively you can email us at info@royalcyber.com or Contact us and our team of consultants will assist you further