Environment planning for transactional batch applications and compute-intensive applications
When planning your batch environment, consider certain factors that can help you design your environment to best suit your needs.
Before you build your environment, carefully consider the goals that you want to accomplish. For example, you can configure your batch environment in an existing cell or build a new cell. Also, you must decide what relational database to use, the security you need, and what your availability requirements are. The following sections contain information about each of these considerations.
New or existing cell
You can choose to configure your batch environment in an existing WebSphere® Application Server cell or you can build a new cell entirely. Your choice depends on whether you want a new environment isolated from any existing WebSphere Application Server environment, or whether you want to add the capabilities of batch to an existing environment.
On the application server nodes where you want the job scheduler and batch container functions, use the administrative console to activate the functions. No action is necessary on the deployment manager node.
Job types
For all batch environments, you must deploy the job scheduler on a WebSphere Application Server server or cluster. To set up an environment to host transactional batch or compute-intensive job types, you must deploy the batch container to at least one WebSphere Application Server server or cluster. The transactional batch, compute-intensive applications, or both are installed on the same WebSphere Application Server server or cluster.
Relational database
The job scheduler and batch container both require access to a relational database. The relational database used is JDBC connected. Access to the relational database is through the underlying WebSphere Application Server connection management facilities. The relational databases supported are the same as those relational databases supported by WebSphere Application Server, including DB2®, Oracle, and others.
避免困難: When configuring an
EJB Timer/Scheduler, remember that the default scheduler uses the
simple file-based Apache Derby database by default so that you can
quickly get a functioning environment up and running. DO NOT use the
Derby database for production use. Moreover, the default Derby database
does not support a clustered job scheduler, nor a clustered batch
container.gotchaA highly available environment includes both a clustered job scheduler, and one or more clustered batch containers. Clustering requires a network database. Use production grade databases such as DB2for this purpose. Network Derby works also, but lacks the robustness necessary for production purposes. Do not use the network version in production.
避免困難: Application JPA settings always override the settings
on this page.gotchaSecurity considerations
Security for the batch environment is based on the following techniques:
High availability considerations
Use clustering for high availability of batch components. Deploy and operate on clusters using the job scheduler and batch container.
Use typical application clustering techniques with the job scheduler to ensure that it is highly available. The job scheduler supports multiple methods of access to its APIs: web application, command line, web service, and Enterprise JavaBeans (EJB). Ensuring that highly available network access to a clustered job scheduler depends on which job scheduler API access method. The batch container is made highly available by deploying it to a cluster. The job scheduler automatically recognizes the batch container is clustered and takes advantage of it to ensure a highly available execution environment for the batch jobs that run there.
概念主題