App Connect

App Connect

Join this online user group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.


#Applicationintegration
#App Connect
#AppConnect
 View Only

  • 1.  Versioning of Bar files

    Posted Mon September 21, 2020 08:18 AM
    Hello, 
    Is there a standard way to include the version number in the manifest of a BAR file. The version flag does not during build does not generate the version field in the manifest file. Is there any standard way or practice regarding this. Currently, we are using the $MQSI parameters in the flow descriptions. Interested to know this for IIB V10 as well. 
    Thanks

    ------------------------------
    Mainak
    ------------------------------


  • 2.  RE: Versioning of Bar files

    Posted Mon September 21, 2020 08:41 PM

    We tried to use  the Short and Long Descriptive Properties of an Application and/or /rest-api for saving version information.

    The only method we could find is via the api interface

    PATCH http://esbacsya:4414/apiv2/servers/IS-14100/applications/ESBStatus_v3.0.1

    or

    PATCH http://esbacsya:4414/apiv2/servers/{server}/services/{service}

    Using these api, with a payload of

    {

    "descriptiveProperties": {

    "lastModified": "2019-12-06 15:57:40",

    "locationOnDisk": "ESBStatus_v3.0.1",

    "longDesc": "A long Description",

    "shortDesc": "A short Description"

    }

    }

    But the PATCH does not work. Not yet implemented.

    The best we can use is to embed the version on locationOnDisk which is a build property or populated during the build.

     

    . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
    Hirschel Wasserman

     

    This email and any attachments are intended only for the named recipient and may contain confidential and/or privileged material. Any unauthorized copying, dissemination or other use by a person other than the named recipient of this communication is prohibited. If you received this in error or are not named as a recipient, please notify the sender and destroy all copies of this email immediately.

    Insurance Corporation of British Columbia | 151 W. Esplanade | North Vancouver | V7M 3H9
    Contact Us




    Original Message


  • 3.  RE: Versioning of Bar files

    Posted Tue September 22, 2020 04:04 AM
    I would use the -version flag of the mqsicreatebar command.
    Alternatively the manualOverrides flag in mqsiapplybaroverride for creating my own version system.
    If and how this reflects the manifest file I don't know.

    The IBMs documentation about bar files does not write much about the META-INF folder.
    https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/af14610_.htm


    ------------------------------
    Matthias Jungbauer
    ------------------------------

    Original Message


  • 4.  RE: Versioning of Bar files

    Posted Tue September 22, 2020 04:33 AM
    Edited by Martin Citron Tue September 22, 2020 04:36 AM
    Hello,

    we use keywords files according to this https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/ac26521_.html . The file contains this:
    $MQSI_VERSION=@ENV@-1.2.0 MQSI$​
    During build process (which includes applying properties) we replace ENV with target environment specification.

    Unfortunatelly I dont know how to insert keywords inside bar using IBM tools. We use build script which unpacks BAR (including innner appzip archive), copies the keywords file and then packs it back together.

    ------------------------------
    Martin Citron
    Prague
    ------------------------------

    Original Message


  • 5.  RE: Versioning of Bar files

    Posted Tue September 22, 2020 12:08 PM
    I was unable to find an IBM tool to embed the versioning metadata, so we are inserting the keywords.txt file into the .appzip META-INF folder after the build of the .bar with the following series of jar commands. We are building applications in ACE11 with mqsipackagebar. The keyword expansion is visible in the application's Keywords->Version property.

    jar xf *.bar
    jar uf *.appzip -C Versioning META-INF/keywords.txt
    jar uf *.bar *.appzip

    The Versioning folder is temporary and is generated by a script which populates $MQSI_VERSION and writes to META-INF/keywords.txt.

    ------------------------------
    Peter Moraza
    IT Engineer Application Integration
    Kaiser Permanente
    Pasadena CA
    626-564-7356
    ------------------------------

    Original Message


  • 6.  RE: Versioning of Bar files

    Posted Thu September 24, 2020 03:10 AM
    Thanks Hirschel, Matthias, Martin, Peter for your insights. 
    I think the gist of it is IIB commands does not natively do this and way out is to expand the bar file manually, include the necessary version information and then redo as the bar file, or have the information in the application in the first place. This is surely feature we all use and there is room for improvement. Are there any site where we can submit this as feature suggestion etc.

    ------------------------------
    Mainak
    London
    ------------------------------

    Original Message


  • 7.  RE: Versioning of Bar files

    Posted Thu September 24, 2020 04:39 AM

    Hi,

    You can post requests for product enhancements here.

    There is an existing related RFE,  Change mqsicreatebar command to include keywords.txt, however it did not receive many votes and has not been progressed currently.



    ------------------------------
    Martin Boag
    Software Developer
    IBM
    ------------------------------

    Original Message


Related Content