Enclosure13_Appian_Shared_Platform_Deployment_Instructions_IntSep2020_Redacted Update.pdf

Comptroller of the Currency Office of Management

Operations Program Management Office

Appian Shared Platform Deployment Document

9/11/2020 September 2020 Platform Deployment

Appian Shared Platform Deployment Document

Operations Program Management Office 1

Document Control

Platform Name Appian Shared Platform Platform Acronym APPN Document Title Deployment Document Document Date March 26, 2018 Document Version

Client Organization Information Technology Services (ITS)

Operations Program Management Office 2

Table of Contents

1 Introduction

2 Build Preparation

2.1 Check-Out APPN repository from Rational Team Concert

3 Pre-Application Deployment

3.1 Deploy Appian 20.2 HF C

4 Application Deployment

4.1 What’s New in the APPN Internal September 2020 Release

4.2 Shutdown All Services

4.3 Shared Platform Appian configuration

4.4 Application Import

5 Post-Deployment Procedures

5.1 Take Full App Exports

5.2 Restart App Server

Appendix A Acronyms

Deployment Document .

Operations Program Management Office 3

1 Introduction This document provides guidance in the deployment of releases, hot-fixes and data-fixes. The guide is broken down to different sections for database deployment, Appian application deployment, and post-import procedures.

There are multiple sections in this document that require various types of files. To obtain those files the people doing the install will need to access them through JAZZ.

Operations Program Management Office 4

2 Build Preparation The Platform deployment files will need to be checked out of JAZZ onto each server that is being deployed to before running the Appian configuration script.

2.1 Check-Out APPN repository from Rational Team Concert

This steps need to be performed on your local workstation. For detailed instructions on working with Rational Team Concert please contact the Rational Support Team.

1. Open Rational Team Concert

2. Ensure that it is connected to the Small Applications (Change Management) repository connection (Work with Rational Support Team if this is not setup).

3. Navigate to Small Applications (Change Management) Builds

4. Expand the appropriate build for the environment you are deploying to (i.e.

“Production Deploy – P04”)

5. Right click on the build that represents the specific server you wish to deploy to, and select “Request Build”

Operations Program Management Office 6

3 Pre-Application Deployment The steps outlined in this section are steps that need to be completed before the Ap-plication is imported.

3.1 Deploy Appian 20.2 HF C

Note: this section should be deleted if there are no upgrades, patches or hotfixes to deploy.

Follow the instructions in the Appian documentation to install Appian version num-ber. Perform this step on each server that has Appian installed. Note that for Appian to start properly, the build configurations in the D:\repo directory must be rede-ployed, which will be performed in section 4.4.

Operations Program Management Office 7

4 Application Deployment The steps outlined in this section will walk you through deploying applications to the Appian Shared Platform.

4.1 What’s New in the APPN Internal September 2020 Release

There are no database changes for the September 2020 release on Internal Produc-tion.

4.2 Shutdown All Services

1) On the Tomcat server: Shut down the Tomcat service, and verify that the java process has stopped

2) Stop the Appian Search service.

3) On the Appian server: Stop Appian by running . When the command finishes, verify that no k processes are active and no Java processes are running (except for the one where you are shown as the User in taskmgr, all other java processes would have service account user).

4.3 Shared Platform Appian configuration

IInstallation Perform the following steps to apply the hotfix:

1. Stop Appian. See Starting and Stopping Appian for detailed instructions:

1. Shut down the application server.

2. Shut down the search server.

3. Shut down the data server.

4. Shutdown all Appian Engines, ensuring that the engines are check-pointed upon shutdown.

2. Back up your existing Appian instance. See Backing Up Your Existing Ap-pian Instance for instructions.

3. Unzip the contents of the HHotfix_Package. archive into your <AP- PIAN_HOME> directory.

4. Run the ddeleteFiles script (deleteFiles.bat on Windows, deleteFiles.sh on Linux) that is now located in your <APPIAN_HOME> directory.

Operations Program Management Office 8 o If the script reports that some files were not deleted, address the rea-son for the failure (common causes listed below), and run it again until it no longer reports failed deletions.

o Common causes of failed file deletion include:

o The file is open in another window or process o The file is locked o You do not have permission to delete the file

5. Unzip the contents of the uupdates.zipp archive that is now located your <AP- PIAN_HOME> directory.

6. Run the iinstallJdk script (installJdk.bat on Windows, installJdk.sh on Linux).

7. If you maintain customized or overridden Spring Security .xml files, merge them with the associated base files in the /deployment/web.war/WEB- INF/conf/security/ directory.

8. Delete the ddeleteFiles scripts, the iinstallJdk scripts, the OOpenJDK ..tar.gz and ..zip files, and uupdates.zip.

9. If you are using a Web server, copy the content of <APPIAN_HOME>/deploy-ment/web.war to the folder where the Web server is getting the static re-sources. See Copy Static Resources to the Web Server for more information.

10.Run the configure script to deploy your environment's configuration

11.Start Appian:

0. Start the Appian Engines.

1. Start the data server.

2. Start the search server.

3. Start the application server.

To determine if Appian 20.2 Hotfix Package C is deployed, open the bbuild.info file located in <APPIAN_HOME>/conf/.

4.4 Application Import

There are no apps to import for the September 2020 release on Internal Production

Operations Program Management Office 9

Operations Program Management Office 10

5 Post-Deployment Procedures After applications have been imported into Appian, the Administrator may need to perform several additional activities to complete the application configuration or to update running process to reflect changes made during the sprint.

All actions must be completed a System Administrator.

5.1 Take Full App Exports

We must ensure that each product has a full application containing all pertinent ob-jects which is exported and checked into our version control system, Jazz. These need to exclude any “Common Objects”.

For each app deployment import that was done this release, please do the following as a system administrator in the design interface:

1) Identify the correct full application for the product (It is usually named with just the acronym of the product, i.e. “EMS”) and open it.

2) Click on “Add Existing”, and choose “Application Contents”

3) Add the release application that was imported in the Application Import sec-tion for this Product.

a. Do nnot add the common objects application, or any application that was not specific to this product

4) Export the product application

5) Check it into the repository under APPN/Products/<Product Name>/Prod-uct_Applications

a. Overwrite the existing app there with the same name.

6) Check in and deliver the applications in Rational Jazz

5.2 Restart App Server

Before running post deployment steps, the Tomcat Application Server should be re-started. This is recommended by Appian in order to ensure that the cache is refreshed after importing many objects.

Operations Program Management Office 11

Appendix A Acronyms Acronym Definition CCO Chief Counsel’s Office IE ESC Internet Explorer Enhanced Security IIS Internet Information Services ISAPI Internet Server Application Programming Interface JDK Java SE Development Kit OPMO Operations Program Management Office RAM Random Access Memory URL Uniform Resource Locator