Share:
The Deployment Automation Manager consists of two tools used for:
Although the tools are best used in conjunction, they can be used independently as well.
The Automated Versioning Manager is a tool that helps manage Appian applications and database DDL files in a version control system. Given an Appian application ZIP file, the Automated Versioning Manager performs the following actions:
The goal of this tool is to facilitate the adoption and usage of a version control system to perform configuration management of the Appian applications and database DDL files.
With the Automated Import Manager, users can automatically deploy applications and patch contents (either applications from Appian OR packages generated from the Automated Versioning Manager) to any environment. Users will have three options for deployment: the tool can either deploy from the tool’s user interface in one click, trigger the deployment from an external CI tool or deploy from the command line.
The Automated Import Manager automates the process of inspecting the application, executing DDL scripts, updating CDTs, republishing the appropriate datastores, and importing the application.
For more information, please visit: https://community.appian.com/w/the-appian-playbook/198/deployment-automation
Error: java.sql.SQLSyntaxErrorException: ORA-00900: invalid SQL statement
This only happen when I try to import a sql file with the following statement
CREATE OR REPLACE EDITIONABLE FUNCTION "DEMO" (p_list IN VARCHAR2) RETURN t_my_list AS l_string VARCHAR2(32767) := p_list || ','; l_comma_index PLS_INTEGER; l_index PLS_INTEGER := 1; l_tab t_my_list := t_my_list(); BEGIN LOOP l_comma_index := INSTR(l_string, ',', l_index); EXIT WHEN l_comma_index = 0; l_tab.EXTEND; l_tab(l_tab.COUNT) := TRIM(SUBSTR(l_string,l_index,l_comma_index - l_index)); l_index := l_comma_index + 1; END LOOP; RETURN l_tab; END DEMO; /
apparently it fails due to the first ";", I know this because the function is created till that part:
** NOTE: my DB is Oracle
This issue was supposed to be fixed already with the release June 2018 - Release 2.4.6: https://community.appian.com/w/the-appian-playbook/198/deployment-automation#Script_Execution1
any suggestion on how to overcome this issue?