How To Avoid BPM Studio Project File Lock When Using CVS (Doc ID 1353587.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Business Process Management Suite - Version: 10.3.2 and later   [Release: AS10gR3 and later ]
Information in this document applies to any platform.

Goal

You are storing BPM projects opened in Studio against a source code repository, like CVSNT.

After creating or modifying local BPM resources like Engine Preferences, Project Preferences, BAM preferences or Business Rules, you could face popup messages like the following one:

"Could not write to <file_name>"

<file_name> could be any of the following: bam.xml, engine.xml, preferences.xml, publication.xml, .project.xpdl

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms