You can use source control management with your multiuser development environment.
This section provides a general outline of how you might use both processes together.
For example, if you have an existing repository under multiuser development and you want to begin using source control management, you might follow the steps described in the following subsections:
Use this procedure to put the MUD master repository and MUD log file under source control.
mhlconverter command-line utility to convert your MUD log file (*.mhl) to an XML file.
See Saving an Existing Repository File in MDS XML Formatto convert your master MUD RPD to a set of MDS XML files on the file system.
mhlconverterwith the input MHL file name and path, and the output XML file name and path. For example:
mhlconverter -I C:\MUD\mud_repository.mhl -O C:\MUD\mud_repository.xml
After creating and checking in the initial version of the master MUD repository, you need to check in updated versions of the MUD master repository on an ongoing basis.
This section describes two different ways to perform this task.
Use these steps to manually check in changes to the master RPD and log file that have occurred as part of the multiuser development process.
Consider using the automated check-in method described in Using a Script to Check In the Updated MUD Master Repository and Log File if you have a large repository. See Creating an SCM Configuration File.
Open the latest copy of the master RPD in the Administration Tool.
Create or select the appropriate SCM configuration file.
Select File, then select Source Control, then select Link to Source Control. Select the directory that contains the MDS XML version of the master MUD repository.
Using Link to Source Control is not recommended for large repositories and might cause time-outs.
Click Save to save changes from the master MUD repository into the MDS XML files under source control. The Administration Tool determines which files to add, check out, modify, and delete and issues the commands to your SCM system.
Close the Administration Tool.
Follow these steps to update the MUD log file:
In your SCM system, check out the XML-format MUD log file.
mhlconverter utility to overwrite the XML-format MUD log file with the latest changes from the
Check in the latest XML-format MUD log file to your SCM system.
Check all changes into your SCM system.
It is recommended that you perform the steps in this section regularly to avoid having too many changes in a single transaction.
As an alternative to manually checking in changes, you can create a script to perform the check-in tasks and then schedule it to run at regular intervals.
Identify the latest copy of the master RPD that you want to check into your SCM system.
Identify the last version of the master RPD that was checked into the SCM system. You can review the latest XML-format MUD log file under source control to determine this version.
If you do not have the last checked-in version of the master repository in RPD format, you can use the
biserverxmlexec utility with the -D option to read the latest MDS XML files checked into source control and re-create an RPD version.
comparerpd utility with the
-M option to compare the latest copy of the master RPD, the modified version, with the version that was last checked in, the original version. An MDS XML format diff is generated.
Create a script that does the following:
Reads the MDS XML diff directory to identify which files are present.
Issues commands in source control to check out the identified files or add new files.
Copies the latest version of the files from the MDS XML diff directory to the source control directory.
oracle\bi\server\base\DeletedFiles.txt file inside the MDS XML diff directory to determine which files to delete.
Issues commands in source control to delete the appropriate files.
Checks out the MDS XML-format MUD log file, runs the
mhlconverter utility to convert the latest MHL-format log file to XML format, overwrites the existing MDS XML-format MUD log file with the new one, and checks it in.
Performs all necessary check-in steps in the SCM system.