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
Did you try setting forceImport=true?
Is there any setting wherein even if inspection fails, we can continue with import? Currently, when inspection fails, our script stops over there.
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?
You need to make sure you're running the script from the same directory the other artifacts are in. See https://community.appian.com/w/the-appian-playbook/198/deployment-automation#Deploy_from_the_Command_Line_Script for more details
Error: Could not find or load main class com.appiancorp.ps.plugins.automatedimport.remote.DeployApplication
Any idea about this error, got this wehn i executed the script
How are you using the folder listener and what was the error message?
When I run version-application.bat in Git Bash, it works for me and deploys my code to the repository.
However, I'm interested in using the Folder Listener functionality, but when I try this, the deployment fails with an error message. It's a similar error message that I get when I try to run the version-application.bat file within a Windows Command prompt instead of Git. Is there any suggested solution for this, or configuration steps I'm missing? I'm having a hard time finding sufficient documentation on this.
I am trying to run the below command
version-application -action addContents -vc_username **** -vc_password *** -application_path "C:\Users\kowsalya\App.zip" -ddl_ds jdbc/AppianAnywhere -ddl_path "C:\Users\kowsalya\Script.sql" -commit_message "Commit by @Kowsalya"
but it says not a recognized command. Please help.
'Versioning' is not recognized as an internal or external command,operable program or batch file.Picked up JAVA_TOOL_OPTIONS: -agentlib:jvmhookPicked up _JAVA_OPTIONS: -Xbootclasspath/a:"C:\Program Files (x86)\HPE\Unified Functional Testing\bin\java_shared\classes\jasmine.jar"Error: Could not find or load main class com.appiancorp.ps.automatedversioning.AutomatedVersioningManager
the solution was to override the order of the authentication methods by adding the following on the version-appliation.bat "DEFAULT_JVM_OPTS=-Dsvnkit.http.methods=Basic" in case the svn has Basic authentication. Or we can use any of the other options like this "DEFAULT_JVM_OPTS=-Dsvnkit.http.methods=Basic,Digest,Negotiate,NTLM" it will depend on your needs
while testing this with svn I faced an issue like this "org.tmatesoft.svn.core.SVNAuthenticationException: svn: E170001: Negotiate authentication failed: 'No valid credentials provided'
The only change we have made is to fix the bug in executing DDL scripts:July 2019 - Release 2.5.8
A couple questions.
1. What changes were made in the July update?
2. Is there an issue with the automation manager pushing code to GIT?
I use PortableGit to push Appian Applications to BitBucket. Last month I noticed that the automation manager unzips my application into the appropriate files locally and sends a commit message to Bitbucket but it no longer pushes the files. I thought it was because I was still on client version 2.5.7 but its still happening with version 2.5.8. My current work around is to manually add all changes and push it to my branch using git. Does anyone else experience this? How can I troubleshoot this as none of my configurations in version-manager.properties have changed?
Is there an example application and database configuration that might demonstrate how this is meant to work? I think that would go a long way to solve the problem.
I am having difficulty getting Flyway to work with the import. I created a community post (https://community.appian.com/discussions/f/administration/17152/flyway-implementation) and have an issue open with Appian Support (477952) with details and files. I believe now that the issue is with the version-manager configuration, as the zip file does not look quite right.
Through DAM application fails to deploy. Is there any way to publish data stores through the deployment automation as it deploys whole app.
© 2020 Appian. All rights reserved.