tiradoj
Well Known Member
Gotta love Oracle's Marketing Machine: they make it all sound SOOOOO simple.
Folks, it is not.
You cannot download and deploy software updates out of the box with 9.2.7.1
You have to create database user ids, create a separate tablespace (Oracle), run a Report to create the tables in the tablespace
And how is a CNC supposed to manage the change control process with a random tablespace (JDUPDATE) floating outside the well establish DV>PY>PD promotion cycle?
Why aren't we deploying updates to DV Central Objects as usual?
Also, be aware, you may have to enable/check several items/settings in E1 Server Manager (jas, jdbj files for example) for web deploy because some might not enabled by default or ready for the web deployment process.
One fun example of this was the requirement for OCM mappings for the JDEP920 environment. Whoa! Where did that come from?
I guess in a way it makes sense but ok where is the FULL documentation on this? Do we need to copy these OCM mappings to server map table too?
I am trying to DEPLOY an ESU via P96470W and OF COURSE it is not working. It is giving me a 'Verify_Package_Deployment" error (see below)
So what happened to the BUILD step in web deployment? Is that not necessary now? if not, which objects and where is it not necessary and when? SMH
What the heck for? What is the value add of this functionality?
Why would a company who already has an established scheduled routine (at some considerable expense of time and money and trial and error) with set hours and dates (like I had with Honeywell) and has "trained" users to be aware of this want to risk disruption to their operations to do all this extra setup because there is SOME (supposedly) ZERO downtime for SOME OBJECTSCOMPONENTS (not all)?
The package deployment process at sites I worked out was never debilitating to a customer's productivity
Yes it is "neat" to be able to deploy a package from the web just not sure the of the VALUE ADD here.
Some customers require 24 hour uptime? Ok which ones? what percentage are JDE customers absolutely have to have 24/7 uptime or will fade into obscurity without it?
Banks? Manufacturing companies? Customers with operations all over the world? Maybe they would be willing to spend the money to configure and thoroughly vet out the process but the rest....not so sure.
What about UDOs and the zip format they are in? Are UDOs supposed to be deployed via Change Assistant? (mine are failing half way through deploy phase saying they cannot find the properties of a UDO or a manifest--the manifest is in the same folder the UDO is in (doh!) ) Through JDEPLAN environment on Deployment Server? via the WEB version P96470W?
Also, I have zip files within zip files for these UDOs. You can deploy zip files via P96470W?
And what about par files? Can't Oracle make up it's mind what compression format it wants to stick with? Right someone will say par is for one purpose zip another
I know the purpose: it is to obscure confuse and complicate.
So here's an Oracle link
First off the Software Update Status cool graphic doesn't appear on MY screen (oh yes I am sure SOMETHING ELSE SOMEWHERE has to be set up for that to work- God forbid it works out of the box)
Second this web doc makes the web deploy process seem so peachy keen easy.
Where is the screen shot I get when I try to deploy? (see attached)
it says this under that graphic
Note: If the Software Update Status window does not appear, select Software Update Status History from the Layout drop-down menu.
there is no "Software Update Status History" drop down on my screen either (I believe this is a FEATURE which will not show up until you ENABLE the feature security which is NOT setup by default)
I need to get some breakfast before coming back to untangle this mess
Folks, it is not.
You cannot download and deploy software updates out of the box with 9.2.7.1
You have to create database user ids, create a separate tablespace (Oracle), run a Report to create the tables in the tablespace
And how is a CNC supposed to manage the change control process with a random tablespace (JDUPDATE) floating outside the well establish DV>PY>PD promotion cycle?
Why aren't we deploying updates to DV Central Objects as usual?
Also, be aware, you may have to enable/check several items/settings in E1 Server Manager (jas, jdbj files for example) for web deploy because some might not enabled by default or ready for the web deployment process.
One fun example of this was the requirement for OCM mappings for the JDEP920 environment. Whoa! Where did that come from?
I guess in a way it makes sense but ok where is the FULL documentation on this? Do we need to copy these OCM mappings to server map table too?
I am trying to DEPLOY an ESU via P96470W and OF COURSE it is not working. It is giving me a 'Verify_Package_Deployment" error (see below)
So what happened to the BUILD step in web deployment? Is that not necessary now? if not, which objects and where is it not necessary and when? SMH
What the heck for? What is the value add of this functionality?
Why would a company who already has an established scheduled routine (at some considerable expense of time and money and trial and error) with set hours and dates (like I had with Honeywell) and has "trained" users to be aware of this want to risk disruption to their operations to do all this extra setup because there is SOME (supposedly) ZERO downtime for SOME OBJECTSCOMPONENTS (not all)?
The package deployment process at sites I worked out was never debilitating to a customer's productivity
Yes it is "neat" to be able to deploy a package from the web just not sure the of the VALUE ADD here.
Some customers require 24 hour uptime? Ok which ones? what percentage are JDE customers absolutely have to have 24/7 uptime or will fade into obscurity without it?
Banks? Manufacturing companies? Customers with operations all over the world? Maybe they would be willing to spend the money to configure and thoroughly vet out the process but the rest....not so sure.
What about UDOs and the zip format they are in? Are UDOs supposed to be deployed via Change Assistant? (mine are failing half way through deploy phase saying they cannot find the properties of a UDO or a manifest--the manifest is in the same folder the UDO is in (doh!) ) Through JDEPLAN environment on Deployment Server? via the WEB version P96470W?
Also, I have zip files within zip files for these UDOs. You can deploy zip files via P96470W?
And what about par files? Can't Oracle make up it's mind what compression format it wants to stick with? Right someone will say par is for one purpose zip another
I know the purpose: it is to obscure confuse and complicate.
So here's an Oracle link
First off the Software Update Status cool graphic doesn't appear on MY screen (oh yes I am sure SOMETHING ELSE SOMEWHERE has to be set up for that to work- God forbid it works out of the box)
Second this web doc makes the web deploy process seem so peachy keen easy.
Deploying Software Updates (ESUs) Using the Web Client
This OBE shows you how to deploy application patches using the web client.
docs.oracle.com
Where is the screen shot I get when I try to deploy? (see attached)
it says this under that graphic
Note: If the Software Update Status window does not appear, select Software Update Status History from the Layout drop-down menu.
there is no "Software Update Status History" drop down on my screen either (I believe this is a FEATURE which will not show up until you ENABLE the feature security which is NOT setup by default)
I need to get some breakfast before coming back to untangle this mess