TN - IT - 26092208 Converting a Published InTouch Application into a Managed InTouch Application

• Document Version: 001
• Applies to Version(s): AVEVA Application Server 2020 +

Description  

This technical note describes how to convert a published InTouch application into a managed InTouch application.

Overview

A published (compiled) InTouch application cannot be natively re-imported or "un-published" back into an Integrated Development Environment (IDE) template because its source ties are stripped during compilation. Attempting to manage a published application typically triggers a lock error in WindowMaker: "Application is a Published application. Please edit the source application and republish."

This Tech Note details the procedure to successfully import a standalone published application into an AVEVA System Platform Galaxy, bypass the publication lock, and convert it permanently into a Managed InTouch Application ($InTouchViewApp).

Prerequisites & Requirements

• Access to the primary Galaxy Repository (GR) node with Administrator privileges.
• The published application's runtime folder directory.
• AVEVA System Platform IDE and InTouch HMI matching or exceeding the application’s original version.
• The Application is NOT using ArchestrA graphics.

Solution Steps:

Step-by-Step Conversion Procedure

Step 1: Locate the Source Application Folder

1. Launch the InTouch Application Manager from the Windows Start Menu.
2. Identify the published application in the list.
3. Note the exact file directory listed in the Path column.

Step 2: Strip the Publication Folder Marker

1. Open Windows File Explorer and navigate to the directory path identified in Step 1.
2. Open the root of the application folder.
3. Locate the subfolder named ArchestraASymbols or Symbols
4. Backup and then Delete the ArchestraASymbols folder entirely.
   (Note: This folder serves as a marker that locks the application. Deleting it allows the ArchestrA IDE import wizard to recognize the folder layout.)

Step 3: Initialize the Managed Template ($InTouchViewApp)

1. Open the ArchestrA IDE and connect to your target Galaxy.
2. In the Template Toolbox or Derivation View, locate the system base template named $InTouchViewApp.
3. Right-click $InTouchViewApp and select New > Derived Template. Rename this template to your desired application object name.

4. 

5. Double-click the newly derived template to launch the InTouchViewApp Initialization wizard.
6. Select Import Existing Application and click Next.
7. Click the ellipsis button, browse to and highlight your application folder, and complete the import wizard.

Step 4: Inject the Permanent Editing Override

WindowMaker caches local deployment files and will often attempt to re-lock a published database upon a close or save cycle. To permanently bypass this, you must apply a technical override parameter to the Galaxy configuration files.

1. Completely close WindowMaker, InTouch Application Manager, and the ArchestrA IDE.
2. Navigate to the centralized file repository on your GR Node:(Backup both the Checkin and Checkedout directories prior to completing this procedure)
   C:\Program Files (x86)\ArchestrA\Framework\FileRepository\<YourGalaxyName>\ObjectFileStorage\<YourApplicationObjectName>\
3. Inside this directory, locate the CheckedIn folder. Open the INTOUCH.ini file with Notepad.
4. Scroll to the very bottom line of the file, create a new line, and input exactly:
    

AllowPubAppEdit=1

1. Save and close the file.
2. Copy this modified INTOUCH.ini file and overwrite the matching file located in the adjacent CheckedOut directory folder.

Step 5: Purge Local Engineering Cache

To force the engineering workstation to pull the updated initialization parameter instead of reading a locked local cache:

1. Navigate to the local working path:
   C:\ProgramData\Archestra\ManagedApp\ or C:\Users\Username\AppData\Roaming\ARCHESTRA\ManagedApp
2. Locate the folder matching your specific application object name.
3. Delete the entire contents of that folder.(Do not delete the ManagedApp folder, only its contents.)

Step 6: Perform a Clean Verification Save

1. Launch System Platform IDE.
2. Right-click your modified $InTouchViewApp template and select Check In to commit the .ini override changes to the master database.
3. Double click the template again to Open it In WindowMaker.
4. Once the application loads successfully without errors, perform a minor graphic change (e.g., move a text field or single component by 1 pixel).
5. Click File > Save.
6. Exit the program cleanly by selecting File > Exit.

Do not use Windows Task Manager or the red "X" window close button to exit. Navigating to File > Exit forces WindowMaker to execute a graceful save cycle, overwriting the internal compiled markers with clean, un-published master configuration baselines.

                                     _____________________________________________________________________________________________________