While you were deploying the UBE+AAP package, users were unable to run any application from the HTML, However, after the package deployment was complete, users able to run the same application.
Wait, did the question mention anything about the enterprise server being locked? I must have missed that part. Oh well, I'm just going to go with B and hope for the best. At least the users could run the app after the deployment, right?
Hold up, did someone say 'HTML server'? I thought this was a JD Edwards question. Maybe the HTML server was just feeling a little left out and decided to put on a little show during the deployment. Either way, I'm going with D.
Haha, I'm picturing the server manager agent just taking a coffee break in the middle of the deployment. 'Sorry, folks, gotta recharge!' But seriously, I think option A is the way to go here.
Hmm, I'm going to have to go with C on this one. The HTML server restarting during the deployment seems like the most logical explanation for the users' inability to run the app. Gotta love those unexpected server restarts, am I right?
Ooh, I bet it's option D! The enterprise server getting locked during deployment and then becoming available again after the package is installed sounds like the most likely culprit. Package deployment can be tricky, but at least this one had a happy ending for the users.
I'm not sure, but option D) also seems plausible as the enterprise server being in a locked state could have prevented users from running applications.
Precious
30 days agoLavelle
1 months agoGail
5 days agoDwight
1 months agoDonette
2 days agoErin
17 days agoAudra
2 months agoNoe
13 days agoTuyet
14 days agoGoldie
17 days agoJina
24 days agoAlecia
1 months agoFranklyn
1 months agoBeata
2 months agoPamella
1 months agoWillow
1 months agoEdgar
2 months agoFrederica
2 months agoBelen
3 months ago