OBM process versions are integral to Oracle development and are represented by three numbers dot separated, where the first two numbers are the Project Version and the last one is Project Revision.
When a project is published for the first time, all the processes are meant to be 188.8.131.52 version. When an already published project is re-published, the project minor version and project revision can vary. After a project is published, it has to be deployed so that it can be made available for production.
Exams with Life Time Access Membership at http://www.actualkey.com
Publishing and deployment of project
Although publishing and deployment are two related activities, but there does exists a difference between them. They can be sequential through the usage of the option of ‘Deploy processes after publishing them or first the project can be published and the process can be deployed later.
Once a project is published, it can be made available for deployment. The Oracle development project and all its processes are validated and then stored in the repository.
When a project is deployed it can be made available for production and if the project possesses many processes then all or some of it can be deployed. Only that process can be deployed, which has already been published or uses the ‘Deploy processes after publishing them’ option. The deployment process then becomes active.
When a particular process is un-deployed, it becomes Not Deployed but is still published. It is important that the administrator has to focus on the un-deploying processed because it eliminates the deployment history and all the instances of the process can be lost.
The administrators can un-publish when a project has none of the processes deployed. This eliminates the project and processes history and metadata from the repository.
Comprehending OBM Process Life Cycle
When a project is deployed the first time, all the processes will be ACTIVE and in the 1.0.0 version. Henceforth, when re-deployment and re-publishing takes place, there are two options through which the new process can either become compatible or incompatible with the old process.
Redeploying a compatible process:
In this instance, the new one replaces the old revision, which becomes the ACTIVE one and the project revision will be incremented through one. New process instances and the presently running instances can use the latest version of the process.
Redeploying of incompatible process:
In this particular instance, the new version of the process will be ACTIVE thereby establishing a new minor version, and the older version will be automatically deprecated. The new instances of the process use the new version of the process, while the old instances remain with the old version. There can only be one ACTIVE version of the process at one time but there can be a number of DEPRECATED versions running parallel.
Swapping project revisions:
When numerous revisions of a process is deployed and compatibility enables it, one can go back to previous revision. This process can be implemented through selecting the Modify option on the Deployment screen and activating the old-compatible revision of Oracle development life cycle from oracle consulting services providers.
For More : www.certkingdom.com