JDE E910_TR9.1.3.4 svrpkgbuild.log - What does it mean by this ?

Sun Aug 09 17:25:47  -  Copy successful

Sun Aug 09 17:25:47  -  Package deployed.

Sun Aug 09 17:25:48  - 

Sun Aug 09 17:25:48  -  Finalizing SO deploy on server MYJDEAPP.

Sun Aug 09 17:25:48  -  Process ID\Thread ID: 6936\6796

Sun Aug 09 17:25:48  -  Machine type retrieved OS = INTEL; Ver = 6.1

Sun Aug 09 17:25:48  -  Server initialized now sending message back to the build machine.

Sun Aug 09 17:25:48  -  Message sent.

Sun Aug 09 17:25:48  -  Clearing UBE specs.

Sun Aug 09 17:25:55  -  Persistant UBE cache deleted.

Sun Aug 09 17:25:55  - 

Sun Aug 09 17:25:55  -  Unlocking the server after Normal Package Deploy.

Sun Aug 09 17:25:55  -  Unlock server after Normal Deploy.

Sun Aug 09 17:25:55  -  Metadata kernel unlocked.

Sun Aug 09 17:25:55  -  UBE subsystem unlocked.

Sun Aug 09 17:25:55  -  Kernels unlocked.

Sun Aug 09 17:25:55  -  Server unlocked and ready for business.

Sun Aug 09 17:25:55  - 

Sun Aug 09 17:25:55  -  Transferring the SvrPkgBuild.log to the Deployment server.

According to Oracle :

The SvrPkgBuild.log file is unique for each Package (Full or Update). When the build happens on the Enterprise server, this file is created and all the activities are written in this log file. This includes the package build completion.

Now when you deploy this package, the information about locking / copying / unlocking and deployment status (Success / Failure) is written in this same log. There is no separate log file to mention about deployment process. The same file is updated, even if deployment is done from a non-build machine. Example, you built the package from Machine A, but deployed from Machine B. The deployment related lines are written on the same log file.

If the R98825D pdf and the SvrPkgBuild.log mentions success about the deployment, you can consider the deployment to be successful. It is not important if the deployment was done from the build machine or a different machine.

Hope that helps..