Hello all,
As Content Server has evolved, modules previously shipping as optional installations are now shipped as a part of the core Content Server installation. Some of these modules (e.g., Records Management) have historically shipped Content Web Services extensions via separate directories under <OTHOME>\webservices. We are considering merging these directories together for easier deployment and management, however, we would like community feedback on how you typically manage your deployments.
For .NET deployments, this would mean merging each of the <OTHOME>\webservices\dotnet subdirectories together, and merging all the separate web.config files into a single web.config file.
For Java deployments, this would mean merging each of the .war files into a single cws.war file, which would also mean that the various web.xml files within each .war file would be merged.
Would this merge proposal cause issues for you?
What is your standard process for managing updates to these services and redeploying (including web.config/web.xml handling)?
For .NET users, do you directly mount services from the <OTHOME>\webservices directory? Or do you relocate the binaries?
Your feedback is greatly appreciated.
Kyle Swidrovich
Product Manager | Content Suite
OpenText Corporation
