Deployment of application into OC4J 220.127.116.11.1 running inside Oracle9iAS 18.104.22.168.2
Posted on 2004-04-25
I have finished coding a servlet and jsp application, which my client has forced me to develop on OC4J 22.214.171.124.1 I did the development on OC4J 126.96.36.199.1 Standalone; deployment will be into his machine running OC4J 188.8.131.52.1 inside Oracle Oracle9iAS 184.108.40.206.2.
My plan is to ship him the .war file, and have him manually make the necessary changes to the configuration files (data-sources.xml. application.xml, and default-web-site.xml).
Now I know that in OC4J 9.0.4 inside Oracle9iAS 9.0.4, your're supposed to make changes to the configuration files only through Enterprise Manager or through the DCMCTL utility. Otherwise, you risk corrupting the infrastructure repository in which the configuration parameters are stored. If you do make manual changes to the configuration files, you are supposed to execute dcmctl -update Config -ct oc4j afterwards, to avoid corrupting the infrastructure repository. -- You can make manual changes to the configuration files only in the Standalone version.
If I understand correctly, however, OC4J 220.127.116.11.1 inside Oracle9iAs 18.104.22.168.2 is not nearly as tightly integrated with Oracle9iAS 22.214.171.124.2. So the OC4J-126.96.36.199.1-inside-Oracle9iAs-10.2.2.2 configuration parameters are not stored in the infrastructure repository. So it's possible to make manual changes to data-sources.xml and the other configuration files without worrying about possible corruption to the infrastructure repository or anything else. So my client can (or I can, if he ever gives me access to his box) make the changes to the configuration files and deploy the application into his part-of-Oracle9iAS-10.2.2.2-OC4J exactly the same way I deploy to my Standalone OC4J.
Is my understanding correct, or am I way off base?