Prerequisite Hardware/Software
Operating system software and hardware requirements vary depending on which components of ActiveBatch you choose to install, which is explained in detail in the Sizing section.
| Hardware | Minimum Requirements |
|---|---|
|
Computer |
Intel®, AMD® or compatible, 2-Ghz processor or higher. Multi-processors are supported and used by ActiveBatch if available. |
|
Memory (RAM) |
8 Gigabyte of memory (minimum) |
|
Hard Disk Space |
700 MB is required for a complete installation. An additional 350 Meg is also required temporarily during the installation. Database hard disk requirements start at 50 Meg and will increase based on the number of ActiveBatch objects (plans, jobs, schedules, etc.) that have been defined, the number of plan and job instances created and their history retention periods. |
|
Operating Systems |
See Operating Systems for details. |
|
Monitor |
Minimum recommended resolution for ActiveBatch Console is 1920x1080 |
The actual hardware requirements vary depending on the job scheduling workload you need to perform. In general, ActiveBatch attempts to use memory for greater performance, so memory utilization increases with the number of Plans and Jobs deployed.
| Software Component | Requirements |
|---|---|
|
All |
Microsoft Windows Scripting Host Version 5.6 or later Microsoft .Net Framework Version 4.8 Microsoft Universal C Runtime |
|
Job Scheduler |
The Job Scheduler manages the backend database. See Databases for a list of database types supported. |
|
Client |
See Operating Systems for details. |
|
Execution Agent |
See Operating Systems for details. Note: if you run any x86 (32-bit) jobs, you will need to install the x86 C++ Redistributable. This is because beginning with Windows Server 2008, all OSes are now 64-bit. |
If you don’t have a database for the Job Scheduler, you can install Microsoft’s SQL Express Edition product at no additional charge. SQL Server Express does have certain restrictions in terms of performance and database size. We recommend that you visit Microsoft’s website for more information. In addition, if using SQL Server Express, you must install it on the Job Scheduler system.
ActiveBatch V10 (or later) will use the Microsoft Exchange Web Services facility for message exchange. The EWS software requires that you have Microsoft Exchange 2013 (or later). If EWS is not available then Outlook 2003 (or later) and MAPI, in an unsupported fashion, will be used with reduced functionality. If EWS is available then Microsoft Outlook is not required.
ActiveBatch uses “open” databases allowing greater flexibility in choosing a database for ActiveBatch use in which you can leverage your existing database expertise and software. See Databases for a list of supported databases. You will want a reasonably powered server to handle your database performance requirements. Many customers deploy the Job Scheduler on one server and use an existing server farm to also provide ActiveBatch with access to its database. This approach may also solve any availability or disaster recovery issues concerning ActiveBatch and its impact to your business in the event of a server failure.
The ActiveBatch Job Scheduler requires the use of Microsoft’s OLE/DB drivers for access to an ActiveBatch SQL database. For Oracle, the Job Scheduler installation requires: Oracle Data Provider for .Net (part of ODAC), Oracle OLE/DB for Oracle and Oracle ODBC for Oracle.
Note: For Microsoft’s SQL Server family of products, ActiveBatch employs XML technology on the database machine. Microsoft’s XML technology cannot be used with “Use Windows NT fibers” support enabled (by default, this option under the SQL Server “Processor” properties is disabled).
Microsoft’s PowerShell V5.1 (or later) and Windows Scripting Host V5.6 (or later) are also required and freely available from Microsoft for download.
All ActiveBatch components require the use of TCP/IP communication.
The ActiveBatch Clients and Job Scheduler also require the use of Microsoft RPC. The ActiveBatch installation will check whether the RPC service has been started. The ActiveBatch Job Scheduler service indicates that RPCSS is a required service dependency (RPCSS is the Windows service that implements Microsoft RPC). ActiveBatch services are run using a specific administrator-level account.
ActiveBatch Client and Job Scheduler components use Microsoft’s Windows Management Instrumentation (WMI) software.
The Execution Agent image is a part of the standard ActiveBatch installation kit and is applicable to Microsoft Windows operating systems only. The other supported operating system platforms have their own installation kits and procedures.
Additional Software Pre-requisites for Oracle Job Steps and Oracle Event Triggers
If you plan on using the Oracle Job Steps the following software is required for both the Job Scheduler and target Execution Machine/Agent (target meaning the machine you intend to run the job step on):
Oracle Data Provider for .Net minimum version 11.2 (or later) for 11g. This software is part of the Oracle Data Access Components (ODAC) which is required.
If you plan on using the Oracle DB Trigger Event facility the following software is required for the Job Scheduler machine:
-
Oracle Data Provider for .Net minimum version 11.2 (or later) for 11g. This software is part of the Oracle Data Access Components (ODAC) which is required.
-
In addition, supplemental logging must be enabled, and the execution user must have a role of “DBA Access” due to security implications of processing the transaction log. Please note that Oracle’s Log Miner facility is used to process the transaction log.
The Oracle Job Steps and Oracle DB Trigger Event facility both require that TNSNAMES.ORA be properly populated. This file is enumerated as part of the “DataSource” dropdown helper provided by ActiveBatch.