Hello
I'm an intern in an company using TIBCO products and I would like advice about possible solutions on this problem :
Currently, XML deployment configuration file of the EAR are modified maually according to the deployment environments. Are there ways to industrialize the management of these configuration files according to different environments.
I am here for any questions.
Thanks
Lorris
Nobody has a little advice on this, please?
I am a beginner with TIBCO products so all advice are welcome!
Thank you
Lorris
Who is responsible for management of XML deployment configuration file in your organization? Is it Developer or Administrators?
I wish I can say there is an industry standard, but there is not. I can almost understand Tibco wanting to stay out of the discussion because every company has a tendency to do it there own way, Tibco just provides the mechanism.
I can speak for my organization.
The Developers are required to manage the appmanage xml deploy files per environment. They actually keep copies of this files for each deployable environment. Administrators and deploy administrators are required to take the tagged xml files from the archive system and apply them to the appropriate environments.
I orginally build an XSLT and ant filter proces to manage ths, but it was deemed to hard to maintain for non-ant xsl development communities. So a raw version of each is currently in the archive system.
- By the way, you will have a similar issue with Hawk rule and schedule bases as well.
I don't have an elegant answer for this.
I hope this helps...
Tony McClay
Tony,
Thank you very much for your response.
There is actually no standard way that even Tibco can recommand to manage environment specific as most companies wants to use build and deployment of application very quickly via automated scripts. XML deployment configuration files makes very easy for build and deployment team to perform task.
In my organization we ended up with following exact same procedure. Initially we tried to create framework which would convert global variables in .properties file where each global variables would display in <name>=<value> pairs. Developers are responsible for generating this .properties file using custom ant framework. But we faced exact same problem as you did with teaching method to non-ant development community. Eventually rather than convincing and providing training during each deployment cycle, XML deployment files maintained by developers and putting into repository satisfied excting organizational build and deployment process. However, developer community still complains too much about maintaining deployment configuration file.
Let's hope that someone has better alternative than our same approach.
-Divyesh Patel