Shifting to Software-Defined
Showing results for 
Search instead for 
Did you mean: 

HP OO and SCM Lock Mechanism – A glimpse into Multi-Authoring done right


HP Operations Orchestration 10 comes with an enhanced development model which is completely aligned with the concepts and methodologies that one would find in a modern development organization.

If you haven’t had the opportunity to meet HP Operations Orchestration (HP OO), it is a next-generation IT Automation solution that is designed from the ground up to increase automation adoption whether in a traditional data center or hybrid cloud environment.


In order to support this model OO 10 integrates with source control management (SCM) systems.

This post will focus on understanding a key feature of Multi-Authoring: The SCM Lock\Unlock Mechanism.


Development with OO 10

HP Operations Orchestration 10 provides a basic SCM solution based on Subversion (SVN).

HP OO’s flow authoring tool, Studio, works completely off-line and the Central does not interact with the repository that is stored in the SCM system. This is in accordance with the general practices for software and system development. Studio’s workspace is a local representation of the SCM repository.

I will not describe the SCM integration mechanism in this post, since it is described in details in the product’s documentation and in the SCM Tutorial—which you can download from the community here:


 You can download HP Operations Orchestration here to experience it for yourself.



The first task after the morning coffee – Update your local workspace!

The first thing we should do when starting to work on a project, assuming Studio is already connected to SVN, is to perform an update. We need to do this in order to retrieve the latest changes. This can be done for all projects as shown here:

 SCM update 


You can even narrow down to a specific project, by right-clicking the project folder:


 Update project


The update command then updates the local workspace which is confirmed in the SCM message window:

 SCM Messages


Tip: The SCM repository is not updated automatically. Make sure you always update your project before working on it. You can never know if you teammate or team leader has changed or added something.



You have performed an update? Good, now lock your flows!


Studio is not actively monitoring the SCM system for locks. In order to lock an item, the flow author must first try to obtain the lock in order to see if it unlocked.

HP OO 10.10 Studio introduces the “Enforce locking policy” feature”. The locking policy will allow you to edit a flow, only after you lock it. We recommend that this option is checked:
Locking policy


The flow will become “read only” again after you commit your changes to SCM. This enforces the practice of locking it in case you want to change it again. The locking policy automatically locks the item prior to delete, move, rename or revert to a previous version actions.


In some cases, acquiring the lock may fail. It can be due to several reasons:


  • In case the flow is locked by another user, try to reach the locking user before using the force unlock procedure which is described in the next section.
  • In case the lock fails because the item is not updated- it means you forgot to perform an SCM update before locking.


In any other case, we recommend contacting the SCM admin.


 SCM error message


In case the lock fails, a pop-up dialog will appear and you will be asked if you want to continue editing the item without having a lock. This is not recommended.

You do not want to get this message, right? So please update the project and lock the flow before starting your work.




Commit when done!

It is best to always assume that your teammate will wake up with a great idea in the middle of the night, and will perform an update in order to add something. He should get the latest and unlocked version. And you do not want to get the message box when you try to commit in the morning, right?


Well, it’s up to you– make it a habit to commit when done.


SVN Manager Tools

In the Tools section on the OO community front page you can find the SVN Manager Tools. These tools allow you to see reports of locks and updates as well as unlocking flows that are locked by other users. These tools are not required though, and the details are explained in the sections below.



Force Unlock

Sometimes there is a need to unlock flows that have been locked by other users. This can be done using the command line. OO 10 ships with SlikSVN and it is easy to perform a force unlock:

  1. From a prompt, go to the SlikSVN folder: <studio_dir>\SlikSvn\bin
  2. And execute this command: svn unlock <file_path> --force

Where <file_path> is the flow to unlock, for example:
C:\Users\frisenda\.oo\Workspace\My First Project\Content\Library\Shared Work Folder\Flow1.xml


You can also utilize the SlikSVN command line client in order to generate SVN log reports!

 The client is located in %install location%\HP Operations Orchestration\studio\SlikSvn\bin\. You can use it directly or with a RAS Operation in order to create log files in XML format (the details are available in the How to get started with SCM in OO 10 tutorial).


Then you can use Microsoft Excel in order to present the data. Go to Data\From Other Sources\From XML Data Import, and choose your XML file. Here are sample results:

SCM report



Learn More

I hope you liked this post. Learn more about other important updates such as new content packs for HP Operations Orchestration 10.x and 9.x, and then checkout the HP OO community for additional resources such as guides, tutorials, videos, content and more.

Take the next steps and download the HP Operations Orchestration Community Edition Free Trial to experience tangible benefits of Operations Orchestration in less than 30 days.If you have any requests, questions or feedback, you can also post them on the OO community forums.







0 Kudos
About the Author


As a provisioning addict for 20 years, I was involved in projects in EMEA and the US as engineer, solution architect and project manager. In the last 2 years I'm in the Operations Orchestrations Community Assistance Team in HP Software R&D.

June 19 - 21
Las Vegas, NV
HPE Discover 2018 Las Vegas
Learn about all things Discover 2018 in Las Vegas, Nevada, June 19 - 21, 2018.
Read more
See posts for dates
See posts for locations
HPE at 2018 Technology Events
Learn about the technology events where Hewlett Packard Enterprise will have a presence in 2018.
Read more
View all