If we are using the App Manage utility to deploy a file adapter EAR vs. doing deployment through Admin GUI, how do we make the FA version selection using AppManage?

If we are using the App Manage utility to deploy a file adapter EAR vs. doing deployment through Admin GUI, how do we make the FA version selection using AppManage?

book

Article ID: KB0081484

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks Plug-in for Files for Unix and Windows -
Not Applicable -

Description

Description:
Title:
If we are using the App Manage utility to deploy a file adapter EAR vs. doing deployment through Admin GUI, how do we make the FA version selection using AppManage?

Description:
This solution lists how the choice of desired file adapter version can be made from command line deployment tool..

Issue/Introduction

If we are using the App Manage utility to deploy a file adapter EAR vs. doing deployment through Admin GUI, how do we make the FA version selection using AppManage?

Environment

All

Resolution

When the file adapter machine is added to the domain, the domain Hawk agent on the adfile machine picks all the versions of the adfile from _installinfo folder under <TIBCO_HOME> and updates them under administrator GUI->Installed software.

While deploying the applications, all valid containers for the deployment (all machines having FA) will be listed and you can make a choice  in the GUI.

By default, it should take the highest version. If the target FA version is higher than the design time, it should work but the best way is to open the file in the same version of TRA (Designer), re-create the EAR file and deploy it. This will help to include the new fixes and enhancements of the newer release.

For the command line, a simple way is to upload the EAR file into Admin GUI [not deployment] into thje lower environment and then export that file. The following section of exported file can be edited to suit other environment needs.

**

<binding name="">
                    <machine>%%FileAdapterConfiguration.aar-machine%%</machine>
                    <product>
                        <type>adfiles</type>
                        <version></version>
                        <location></location>
                    </product>

                    <description></description>

                    <contact></contact>

**