Automic Workload Automation

Hi

I am trying to install AWA 12.2 on Linux with a Postgres database on a separate server.

Installation instructions are not very clear for Postgres installation.

Questions:

1. Can AWA run with Postgres database on a separate server?

2. If Yes. Can it be used in a production environment?

The reason for the question is that the customers' primary operating system is Linux.

They don't want to use Oracle.

So Postgres is the only other option.

Thanks in advance

Regards

Klaus

Hi.

AWA is Automic Workload Automation, which is the Automation Engine and it's associated components (like agents and the web interface). The Automation Engine does not support PostGreSQL as it's sole/core database. It only supports Oracle, MS SQL Server or DB2. Or at least that's my current knowledge.

The PostgreSQL database is an additional database which you need to provide only if you additionally want to use the product called "Analytics". That's an "add-on" product, which provides extended statistical and other functionalities.

Hth,

As of 12.2 the AWA can run with Postgres as the core DB. I've tested in a sandbox environment and it works as expected

Hi Michael

What procedure did you follow?

Install Postgres rpm or Yum

Postgres - which version

DB connection string

DBLoad

etc

Thanks

Klaus

Hey Klaus,

I actually did this on Windows. However, the configuration in terms of how the AE is setup should be the same regardless of OS version. This was all done via the Automic Docu and Postgresql Docu. I've yet to install on Linux but I can give that a try when I get some spare time.

Version:

PostgreSQL 10.4

Connection String:

sqlDriverConnect=ODBCVAR=NNJNIORP,host=****** port=5432 dbname=aedb user=automic password=??? connect_timeout=10

DBLoad:

U00003545 UCUDB: Opening database ...
U00029112 UCUDB - Length of the DB-History area: 100
U00029115 UCUDB - OPEN Database handles DB-HENV: 0 DB-HDBC: 0
U00003535 DB INFO: 'DATABASE-NAME = aedb'
U00003535 DB INFO: 'DBMS-NAME = PostgreSQL'
U00003535 DB INFO: 'DBMS-VER = PostgreSQL 10.4, compiled by Visual C++ build 1800, 64-bit'
U00003535 DB INFO: 'ODBC-VER = ODBC not used'
U00003535 DB INFO: 'DRIVER-NAME = PostgreSQL Access Library'
U00003535 DB INFO: 'DRIVER-ODBC-VER ='
U00003535 DB INFO: 'DRIVER-VER ='
U00003535 DB INFO: 'ODBC-API-CONFORMANCE ='
U00003535 DB INFO: 'TXN-CAPABLE ='
U00003535 DB INFO: 'DEFAULT-TXN-ISOLATION ='
U00003535 DB INFO: 'TXN-ISOLATION-OPTION ='
U00003535 DB INFO: 'POS-OPERATIONS ='
U00003535 DB INFO: 'POSITIONED-STATEMENTS ='
U00003535 DB INFO: 'SCROLL-CONCURRENCY ='
U00003535 DB INFO: 'SCROLL-OPTIONS ='
U00003535 DB INFO: 'STATIC-SENSITIVITY ='
U00003535 DB INFO: 'LOCK-TYPES ='
U00003535 DB INFO: 'ODBC_TRACE = 0'
U00003532 UCUDB: Checking data source ...
U00003533 UCUDB: Check of data source finished: No errors. Performance CPU/DB: '62059222'/'1210 (1000/0.825881 s)'
U00003544 UCUDB: Reference values tested with Windows 2003 on XEON 1500 MHz: CPU 813865, DB 470
U00003524 UCUDB: ===> Time critical DB call! OPC: 'OPEN' time: '2:812.477.299'
U00038091 Change application directory to '..\db\'.
U00038042 DB-Version = 12.2/R
U00038084 Processing completed.

Good to know. The compatibility matrix these days confirms that, at least for Postgres 10.