Output Tibant .xml conifguration file format

when using TibAnt with .property files, after applying values from .properties files the output .xml file is a single-line file that is very unreadable if you want to verify if the values are assgined propeerly. Is there anything I could do this about ? I'd like this .xml to look similar to the .xml template file generated with -extract-properties macro.

Addittionally - is there any way TibAnt can perform deployments on the remote BW machines ?

On a separate note, I wouldn't suggest that you verify the output by eye-balling it. Instead I would use a test to verify it (Schematron would be a good fit for this), so they it get's verified every single time it's produced.

TIBant supports remote deployments in the same way that AppManage does by deploying to the machines specified in the machine element in each of the bindings. As TIBant uses AppMange, the machine it's being run on needs to be a member of the domain you are deploying to.

In situations where you want to trigger the deploy as part of your CI service, but you don't have a CI node that is a member of the domain you are trying to deploy to, we recommend that you use Chef or Puppet to run the ant script on a machine that is a member of the domain.

thanks for your response - it assured me that this is a normal behaviour ofTibant.

Additionally, I'd like to ask you one more question. Tibant has configuredmacros for extracting properties from .xml exported from an EAR file.(gvars, sdk, deploy). The Tibant documentation say that thosefunctionalities are useful especially for environments where currentlyconifguration is stored in .xml files. Also documentation states that thoseresult .properties files are suitable for use with Tibant. But it seems tome that when I do the extraction and then modify the value in the.properties file and try to load it to property set so that this change istaken into account during the deployment, Tibant does not accept the formatof this extracted file. Seems to me that when extraction is taking placesome prefix is added to the begining of each line of the extracted propertyfile. Was this done on purpose ? I can use a workaround by removing theadded prefix from each line of the .properties file, but I'm not surewhether this is the right way to do.

Let me tell you how I want to manage those property files.

1) At the moment my configuration is kept in .xml.2) I want to introduce Tibant, export application conifiguration to an .xmlfile, then use Tibant to create .properties file for each app for specificenviornment. Then I want to use those result files as my input files forany future deployments of those application.3) For any new application I want to export .xml config from .ear, thenextract properties from this .xml with Tibant and do the same thing asdescribed above.

The `extract-*-properties` macros are intended to be run with the xml files that you currently have, not the template XML created by `export-config`. Please have a look at the XMLtoProperties example and let us know if you have any more questions.

actually I'm in need of using Tibant in order to generate initial .properties file from the .xml file extracted from .ear and so far it's working. Let me tell you how it works in my workplace.

I receive an .ear file from the developer ->I'm extracting the .xml out of it -> I'm turning .xml into .properties files -> I'm parsing those files in order to get rid of prefixes that Tibant is adding at the beginning of each line -> I have my final properties files that I can use to load gvars when configuring the deployment.

In the meanwhile one question arose - is there anything I can do about Tibant not letting me the password properties be left blank ? Each time I try to load such properties (that in fact are not used, but I'd like to know about their existence and have them in the file) Tibant outputs an error - "" is not a valid password value.