How to patch custom war-file using adpatch driver file uXXX.drv
Dear all,
we are using a solution called CPack, once developed by Oracle consulting which creates uXXXX.drv files containing our custom developed code (CEMLIs). This works perfectly well for pks/pkb, loader-files, publisher-templates, OAF personalizations and OAF pages etc. However, we never created our own non-OAF web applications that run within the eBS application server.
Now we want to start adding small web applications to our eBS application server. First of all: Should we do that? Or are there any support restrictions or technical reasons why we should leave the eBS appserver with the eBS alone?
If it is ok to do so: Does anyone know how an entry in a universal driver file needs to look like in order to deploy the war file using adpatch? Or do war-files need a different patching mechanism than adpatch?
we are using a solution called CPack, once developed by Oracle consulting which creates uXXXX.drv files containing our custom developed code (CEMLIs). This works perfectly well for pks/pkb, loader-files, publisher-templates, OAF personalizations and OAF pages etc. However, we never created our own non-OAF web applications that run within the eBS application server.
Now we want to start adding small web applications to our eBS application server. First of all: Should we do that? Or are there any support restrictions or technical reasons why we should leave the eBS appserver with the eBS alone?
If it is ok to do so: Does anyone know how an entry in a universal driver file needs to look like in order to deploy the war file using adpatch? Or do war-files need a different patching mechanism than adpatch?
Tagged:
0