Automation Engine
9
Specifics per DBMS
Connecting to a Microsoft SQL Server
Connecting to a database server via ODBC
If the database manufacturer does not provide a JDBC driver, you can connect to the database using an ODBC link.
When the name of your system data source is for example '
ProductionDetails
', then enter it in the
Database
name field as ' jdbc:odbc:ProductionDetails
'.
Note:
32-bit versus 64-bit ODBC:
• On 32-bit hardware (for example Windows Server 2003), Automation Engine tools that use these database links can only work with
32-bit Windows ODBC Data Sources
. You need to add the Data Source using the 32-bit ODBC Administrator tool (
%systemdrive%\Windows\
\SysWoW64\Odbcad32.exe
).
• On 64-bit hardware (for example Windows Server 2008 R2), Automation Engine tools that use these database links can only work with
64-bit Windows ODBC Data Sources
. You need to add the Data Source using the 64-bit ODBC Administrator tool (
%systemdrive%
\Windows\System32\Odbcad32.exe
).
Note:
As of Automation Engine 14.1 (2015), Esko only supports 64-bit systems for the
Automation Engine server(s).
Connecting to an Oracle Server
73
9
Automation Engine
Connecting an "Other" DBMS
Other
DBMS can be accessed if you can get the necessary drivers and information on how to access the DBMS via standard JDBC technology.
• Download the JDBC driver (a jar file) from the manufacturer’s website into a
Container
that is accessible to the Automation Engine (Master) server..
• Enter the required configuration fields. See an example:
• Check your JDBC driver manual for more details.
9.13.10 External Web Services
Using the
Interact with Web Service task
, Automation Engine can communicate with web services from external systems.
74
