Current environments:
System B ( development ): z/VM 6.2, RHEL 6.3, CA View 12.1, CA Web Viewer 12.1.5, Build 65.
System A ( production ): z/VM 6.2, RHEL 6.3, CA View 12.1, CA Web Viewer 12.0.0, Build 46.
On development, Release 12.1 hangs off a directory which is just under the application instance:
[coxdavi@ch2ldomwv CA_OM_Web_Viewer]$ cd R121
[coxdavi@ch2ldomwv R121]$ ls -l
total 44
drwxr-xr-x. 9 root root 4096 Nov 26 2014 apache-tomcat-7.0.54
-rwxr--r--. 1 root root 130 Nov 26 2014 CAOMWebViewer_r12.url
drwxr--r--. 3 root root 4096 May 26 12:03 config
drwxr-xr-x. 3 root root 4096 Dec 3 2014 database
drwxr-xr-x. 8 root root 4096 Nov 26 2014 ddl
-rw-r--r--. 1 root root 1040 May 26 12:06 derby.log
-rwxr--r--. 1 root root 145 Nov 26 2014 InstallPackage.properties
drwxr--r--. 2 root root 4096 Jul 23 14:20 logs
drwxr--r--. 4 root root 4096 Nov 26 2014 sampleExits
drwxr-xr-x. 3 root root 4096 Nov 26 2014 uninstaller
drwxr-xr-x. 6 root root 4096 Nov 26 2014 util
[coxdavi@ch2ldomwv R121]$
I would like to propagate this 12.1 release from development to production. I have thought about doing it the same way on production as I did on development, however, I am not sure that this is the best setup for a release like 12.1 ( or any newer or future release ).
Suggestions or experiences welcome to add.
Thanks,
Dave