Intland's free requirements, development and test management hosting.
This server hosts 110,000+ users on the cloud!

Configuring an OMS model project for triggered publication to the Component Library

This documentation describes how to configure an OMS modeling project to automatically publish component description to an OMS component library Codebeamer project.

1. To begin, create a Codebeamer project for the OMS Modeling Project. To do this privilege to create projects on a codebeamer server is required. Go to the projects tab, and select "New Project". Provide all required project properties, then press the "Source Code" button to prepare to upload model source code.

2. Select the "Subversion" Source code server type. These instructions describe how to setup a subversion source code repository. It may be possible to use other repository types (CVS, Mercurial, etc.) but these instructions only describe how to proceed if using subversion.

3. Select "create new managed repository". If the OMS project already has source code in a subversion repository on the codebeamer server then it should be possible to use existing sources.

4. Specify a new, unique repository name. Write this down, as this will be the repository name that will be used to download and work with oms project sources files using a subversion client.

5. From a local subversion client checkout the project source files. If working on the server the project URL will be where (repository_name) is the name given to the source code repository in step 4. If working on a codebeamer server other than check with the server administrator if help is required to determine the project URL.

6. A subversion project is initially created with 3 main directories: branches, tags, and trunk. The OMS model source code should be uploaded under the "trunk" directory. This will be considered as the "main branch" of the project. Other branches could later be created under the branches directory.

7. Copy an existing OMS modeling project source tree to the "trunk" directory. If this project was previously under subversion control, or control by another version control system hidden directories may exist throughout. These old hidden directories must be removed before committing the new source code and directories under trunk. However DO NOT remove the .svn hidden directory under "trunk". This is the newly created .svn directory for tracking changes for the trunk directory. All files and directories copied under trunk, can be added from the command line by "svn add <file/dir>".

to be continued