Even when the user attempts to upgrade server components only (and thus not the database schema), the upgrade installer will prompt for and require the correct Oracle system password. If it is not provided the installation will fail.
Similar tests in Support took about 20 minutes but this is still a long time. SDP trace of the operation showed the file being transfered from client to server very quickly, within a minute. Then nothing occurred in the log for 15 minutes until it started to update the database.
There is a deployment area attached for the Java code (with a filter), and a z/OS deployment area for the z/OS items (again with a filter). When these deployment areas are attached to the project and populated, the Java area gets populated on a decentralised server in around one-and-a-half hours, which is quite good. However, the z/OS area takes around nine hours to finish, and this is for not even half the items.
2) Choose a project (e. g. ACCTS:ACCTS) and use the web client to fetch all files; 3) The files are transferred successfully, but the messages generated are not informative. The server command run is: -
MDHBLD4208122E Failing step is 1 MDHBLD4208239I Processing rc: 8; Highest Significant Subtask Rc: 0 MDHBLD4208240I Of the 1 tasks requested; 0 succeeded, 1 failed, and 0 were skipped, and 0 were omitted (by optimisation)
Running the above command will produce output concerning the certificate, and the "Validity" section of the output will begin with ("Not Before") and end ("Not After") dates of the certificate are shown. 3. Generating A New Certificate
The ALM web services (VaultService, DVMUtilService, and ReleaseRequestService for example) don't work if the process app is promoted from one environment to another because the Composer does not update the correct endpoint and the web service call ends up going to the wrong server . This is because the SOAP 1.1 endpoint was not selected for the port when the WSDLs were imported into the process apps.
If an orch workflow calls a sequence of operations on a particular web service and multiple instances of that orch workflow run concurently then it is possible and perhaps likely that the orchestration will occasionally build and send the wrong content for one or more of its web service requests. The request operation will be correctly set but the message content will be missing expected values.
jboss instances running the orchestration engines we get a FATAL error each time jboss is started. This only occurs when there is no mashup manager installed on this jboss instance.
