I typically use a database for production use due to the need to configure the environment for production (different logon user id, password, region). The Connection Information Set is embedded in the gxz, so it can’t be updated either. With the database repository, I can update expired passwords without having to migrate to a staging database, update, export and migrate back.
There’s a bit more risk of unintended updates to production, but managing the userids and passwords (don’t let anyone have the Administrator password, give all prod support users their own user ids) helps.
I did put in a change enhancement request (http://tech.forums.softwareag.com/viewtopic.php?t=15550&start=0&postdays=0&postorder=asc&highlight=&sid=da65280f1d974bfb78baeee628331075[/url]) to provide external configuration files so we could use the gxz in production.
#webMethods#Mainframe-Integration#ApplinX