When you use Compute Grid, you might have questions about the functionality of some of its features.
Availability, capability and capacity. If you are using Compute Grid with Virtual Enterprise, existing workload on the endpoints will also be considered during endpoint selection.
Yes, you can have multiple active-active job scheduler instances. For this, you need to provide a network database (like DB2®) for the job scheduler to persist job and job definition information.
You need Virtual Enterprise if you want to balance OLTP and batch workloads on the same set of servers. The application placement controller component of Virtual Enterprise will monitor both types of workloads and will aid the job scheduler to dispatch to the appropriate endpoint.
Compute Grid provides a job console that you can use to submit, monitor and manage all jobs in the Compute Grid domain from a single location. This job management console also includes support for creating and managing job schedules (jobs that are run at a specific time or day once or repeatedly).
When you use Tivoli® workload Scheduler (TWS) with Compute Grid, TWS will behave like a meta-scheduler and Compute Grid's job scheduler will behave like an elemental scheduler. You can still monitor and manage jobs in Compute Grid using its job scheduler.