Versioning/Source Control

What tool are people using to version/source control changes made to the OBIA and what components are being source controlled?
We are setting up an OBI EE+ installation and have bought a number of the OBI Applicationes eg Financial Analytics etc.
I am wondering whether people are using a single tool to source control all the components from ETL, DAC, Presentation Layer etc or whether people are using separate source control tools eg Informatica versioning for ETL, another tool for DAC, Presentation etc.

This is a useful link: http://www.rittmanmead.com/2009/01/22/simple-version-control-for-obiee-using-subversion-visualsvn-server-and-tortoisesvn/
You should be thinking about WHY you are version controlling. If it's to have a consistent copy of your BI environment at a given point in time (and I'd suggest that's a good idea) then splitting version control throughout the tools is not such a good idea and you should be looking to something like SVN to centralise version control.
The trouble you have is that several files are binary so cannot be merged by the version control tool. There's no silver bullet for this problem, or if there is I'd love to hear about it!

Similar Messages

APEX Version/Source control

Hi,
I would like to know how other people are managing this. We have developed our own way which works 99% of the time however there are some flaws.
We require that more than one user be working on an application at a time and that these different pages can be released to production at different times.
We have some pretty large applications, some business critical.
1) We export the full application into our CVS application
2) We export each page individually and assign module numbers as we do with apps forms etc
3) Initially the full application is released to prod
4) Any subsequent page changes are done to the page export and that page only is released. The revision is increased on that page module.
5) If any changes to shared components are made then the full application is released.
All updates are stored in packages which we manage as per our normal apps packages without any problems. Our problems are with apex applications.
Let's say user A has exported page 1 of an application and is working on a large change.
User B is also working on a very small change which involves adding a new item to a list.
User B wishes to release his change but cannot do so at page level because of the shared component - he must release either full app or do a separate export for that component.
He cannot release the full app because user A is still using it.
The only thing he can do is do an export of the components and then import that. This is then not version controlled. It is not acceptable for us to have to export and manage every single component individually (I know you can do them as one whole but then if two users are modifying shared components then the issue arises again!)
There is always a mis-match between the application full export and the pages. If we ever had to recover an app, our strategy is to install the full app and then the individual pages. This isn't ideal however so long as we keep things up to date then we have to accept it.
Does anyone have any better procedures than this?? With APEX becoming more and more popular then I believe it needs to become a little more formal in this area. Or perhaps I am just missing something?
I've read the thread Source/version control with APEX? but it doesn't really relate to the issue above.

Hello Chris,
I'm not sure how you organized your project, but a typical APEX project for me has different components:
- PL/SQL where all business logic is in
- External JavaScript files to do some client side things
- External CSS files to handle the look and feel
- APEX application(s)
So for all of the above you want source control. We use Subversion. For the first three (plsql, javascript, css) I guess it's trivial how do this as they are just files.
For APEX you can export your application every night (and even split it into different components if you want). So that gives you one or more files as well which can be loaded in Subversion.
If you want to do team development in APEX; we use following features:
- Locking of Page
- Build Options
- Entering Comments
If it's a very big project you might want to split your APEX application in multiple ones which can work together (same Authentication scheme, same Theme etc. by Publish and Subscribe option).
APEX itself is also build in APEX, and they use different applications as well, but you don't see it in APEX itself, you just see it by the changing APP number in the url.
I'm not sure how familiar you are with all of the above, but this is roughly the way we do it.
Hope that helps and give you a clearer view.
Regards,
Dimitri
http://dgielis.blogspot.com/
http://www.apex-evangelists.com/

Version Source Control

Hi,
We're planning to develop applications with APEX in a team environment. I'm wondering what is the "best practice" for Version or Source Control? Note, we're going to use version 3.0
I do know about the java export tool which is very handy when you are a single developer. However, it does present a problem when working in a team. If they're multiple people working on an application, development will need to be stopped when an application moves from dev -> test -> prod so that testing and fixes can be performed for that specific version.
Though not ideal, I did try to export a page from one application into another and got an error stating: "This page was exported from a different application or from an application in different workspace. Page cannot be installed in this application"
Any ideas would be greatly appreciated. Please note that I'm not looking for help with tools such as cvs and svn.
Thank you,
Martin

I just tested 2 cases here's my results:
- Export from DevWS App 100, P3
- Change references from 100 to 102
- Import to DevWS App 102
- I get the following error message:
ORA-20001: GET_BLOCK Error. ORA-20001: Execution of the statement was unsuccessful. ORA-00001: unique constraint (FLOWS_030000.WWV_FLOW_PAGE_PLUGS_PK) violated <pre>declare s varchar2(32767) := null; l_clob clob; l_length number := 1; begin s := null; wwv_flow_api.create_page_plug ( p_id=> 1054801262233595 + wwv_flow_api.g_id_offset, p_flow_id=> wwv_flow.g_flow_id, p_page_id=> 3, p_plug_name=> 'Form 1', p_region_name=>'', p_plug_template=>
TEST 2
- Export from DevWS App 100, P3
- Change references from 100 to 104
- Import to TestWS App 104
- I get the following error message: This page was exported from a different application or from an application in different workspace. Page cannot be installed in this application.
Martin

Version / Souce Control software and ODI

Hi all,
Does anyone use 3rd party version/source control alongside ODI that they access using ODI (through the 3rd party's APIs)?
If so are there recommendations / warnings for particular products?
I would be looking to create an ODI package to perform backups that are then pushed up into e.g. SourceSafe or PVCS. That kind of thing....
TIA
S.

One answer, Perforce. Check it out at www.perforce.com. I am told that NI uses that for the LabVIEW source code itself as well as their own VIs. Also, LabVIEW 6.1 Pro has built-in support for Perforce.
Enjoy,
Daniel L. Press
PrimeTest Corp.
www.primetest.com

Can i use subfolders with source control for developer ?

We'd like to use the repository as source control for our developer files.
We planned to use the following structure in the repository:
- Application Container
- Folder
- Files
We uploaded the files in the repository.
Now if we open the file through the ron the file will open in form builder, which is pretty good.
The following thing I'de like to do is a checkout of the file ... ok ...i'm going to file - administration - checkout - the message occurs: no versionable object exists ! ... ? :-(.
So I go to file - administration - source control options .. i'd like to say forms that it has to look for the file in a subfolder of the application system .. ok.
After changing this i try again - the same message.
If I return to source control options the container entry has been changed to the application folder.
Are Subfolders not supported by the source control for developer ?
Does anybody have the same effects ?
Background informations ?
Thanks in advance
Mario
null

<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by [email protected]:
Did you check the file in first? When you first put files in Repository, they are initially unversioned until the first checkin...
Brian<HR></BLOCKQUOTE>
Hello Brian
Sorry, for the delay. I worked for some day for another customer.
Yes, i did.
I'm working like this:
- upload file with check in Folder which is under an application Folder (app - fmb )
- then i check out the fmb in the repository
- doubleclick in repository, which opens the form in form builder
- change the file
- File - Administration - check-in - connect to repository - choosing the workarea - and defining the folder (app - fmb ).
- The file will be check-in, but directly under the folder app.
Thanks in advance
Mario
null

Robo HTML 9 will not open our project from Source Control after initial start.

We have a project in version control that we have been using forever, since 2003 or so and many versions of RH. Now that we have upgraded to 9, this project will open the first time in version control and work normally. Once you close the project and attempt to reopen from the starter screen, it opens just great, just not in version control. The files are still set to read only. I have done this several times and the only way i can work on my project in version control is to act like i am opening a project from scratch, then it needs to overwrite all of my local files with the server files. It would not be so bad but I am 3000 miles away from the server and 13 hops plus a slow firewall on the other end. While this has never been a problem in the past it is a big problem because it takes hours for all the files to download and overwrite my local files.
This only happens with RH9 and Version Control 3.1. RH8 works no problem. So, I don't know if this is a RH9 starter problem or a Source Control Problem. Maybe I will make a similar thread in the RH area. I'll wait to see if I get any useful hits from this one first.
It is very strange, I had RH9 open for several days because I was afraid to close the project for this reason and yesterday I published for the month so the heat is less right now but today, it opened with no source control. If I go to Source Control the only thing i can select is put project in source control. That is how it got into source control after converting to RH9.
We have another project that seems to open from version control normally but we can only save topics in HTML view. No useful answers to that topic after a week.
Got any ideas???
I have tried different folder names, different paths, etc.
Thanks,
dv

Ok, here is a wierd one, I used the add to version control icon in the menu bar, It already knew the path so I figured I'm the only one who has been editing these files for the past few days so I clicked add to version control. It added it. I closed and reopeded and still had the same files checked out. Closed, checked in all, then reopened and it is working in SourceControl. Strange that after opening from source control and closing that you need to reopen and tell it to put the project into source control. Obviously some flag is not getting set somewhere. This might help others having problems reopening source control files.
dv

Multi-authoring with source control with RH10 and RH11

Situation:
Writer A is running RH10. Writer A opens Project A, from Visual Studio Source Control, which is connected to a Team Foundation Server.
A new employee, Writer B, has been given RH11.
Writer A can't install RH11 until after mid-June because of tight schedules (can't afford any upgrade problems).
Writer B is supposed to work on the same Help project. (We know that RoboHelp does not support checking out the same file at the same time.)
If Writer B configures her version of RH11 to work with TFS and Source Control, can she open Project A and work on it (from Source Control) without causing problems for Writer A?
Thanks.
Carol Levine

If Writer B is not using Source Control or it is competely separate from Writer A, possibly but I still would not be comfortable.
I think I would rather upgrade Writer A and I note your reservations. It's your call but it's like being between the devil and the deep blue sea. Neither is ideal.
So far it looks like Rh11 upgrades have been OK.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

How to use a 3rd party source control tool with RoboHelp?

Hello,
I would like to set our RoboHelp users up with source control. They are using RoboHelp HTML 8.0.
Our software developers are using the AccuRev scm system; I'd like the doc team to use AccuRev, too.
Can someone direct me to RoboHelp documentation that explains how to set up and use a 3rd party scm system with RoboHelp?
Thank you,
Marilyn

It appears that RoboHelp 7 only sees the first SCC provider listed in the Windows Registry and ignores the rest. I was able to get RoboHelp to display the File | Version Control menu for SourceGear Vault by setting the following two Registry keys and removing keys for other SCC providers (SourceSafe, Surround SCM, and others I am evaluating).
HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider
     ProviderRegKey = \Software\SourceGear\Vault Client
HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders
     SourceGear Vault VS2003 Compatible Client = SOFTWARE\SourceGear\Vault Client
If I create a new RoboHelp project, save it, then select File | Version Control | Add to Version Control, RoboHelp does the following:
     - pops up the Select Version Control Provider dialog and displays SourceGear Vault Classic Client.
     - I select that, check "Make this my default selection" checkbox, and click OK.
     - RoboHelp crashes.
I'm using SourceGear Vault 5.02 under Windows 7 Ultimate 32-bit. A search of the SourceGear Vault knowledge base reveals that they do not support RoboHelp because of its incorrect behavior and instability. It's so sad that RoboHelp can't work properly with industry standard SCC providers. Vault is by far the best SourceSafe replacement out there, and very affordable.

What files should not be checked into Source Control?

Good afternoon.
Running RoboHelp 11, integrated with Team Foundation Server and Visual Studio 2010.
When my two colleagues recently "got" the latest project files from Source Control, they also got items that had been removed or deleted. For example, I had removed all conditional build tags from my project, but their version still included the build tags. Eventually, thanks in part to an old post from Peter Grainge, we realized that the PSS in Source Control contained a lot of that old information. We deleted the PSS and stopped checking it into Source Control. Problem solved. No more conditional build tags or unwanted Single Source Layouts, etc. (I think the PSS got checked in by our Release Engineer when he was trying to solve some other problem. Two years ago it was not being checked in.)
I vaguely remember reading something somewhere once upon a time about not checking certain RoboHelp project management files into Source Control. So far I've not found any such information in the RoboHelp Help or online.
Does anyone know where I can find a list of RoboHelp HTML project management files, such as the PSS file, that should never be checked into Source Control?
Many thanks.
Carol Levine

Look in Snippets on my site.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Project management + Source Control

we are using labview 8.5 and not well known source control in a team environment. I'm not sure if it is the souce control that I'm using or other searsons, but I had so much trouble using those combination. I want to know what others thought about project management and/or source control in general.
Thanks,
- Jimmy
- Jimmy

Hi!
   Actually, I've never merged, since I'm the only LabView guy on our development team
   I absolutely agree with the fact that SVN is a good tool, but I should confess that I didn't spend much time in evaluating many other tools (never tried MS tools), for this I rely on my colleagues' opinion.
   I can report that SVN is being used in a graphic studio for pictures versioning of course, they don't need to merge images There's virtually no limit in SVN use...
graziano

How to move a project in source control

I messed up & need your advice. I put my first RH project, "core", at the root level of my VSS project:
$
rh_projects
   core
Unfortunately, my "core" RH project is now a child project in a merged help system. I also put the "parent" project at the root level, so now it looks like this in VSS:
$
rh_projects
     core
     parent
... but my VSS folder structure really should reflect my real folder structure, so that other writers can use the same structure when they open the project.
So I want to change my VSS folder structure to this:
$
rh_projects
    parent
    projects
       core
So here's my question (finally!): what's the best way to move the core project in VSS?
* In RH, remove the core project from source control, then put it back under source control at the new folder level, OR
* In VSS, add the new "projects" folder structure and move the "core" folder underneath it, then open it in RH as a "new" project?
thanks,
Jenny

Either way should work.
Method 1 will ensure the source control path in the RH files points to the correct VSS location
Method 2 will keep your change history if this is important to you. However, it is trickier to do. Zip up a copy of your project just in case.
Method 2 details
If you use this method, you need to manually change the VSS path listed in the .xpj file.
Look for something similar to the following. It may be different depending on your versions of RH and VSS. The below is from RH6 and VSS2005. '[' represents and angle bracket.
[matchedpair]
           [name]vc::cookie[/name]
           [value]"$/Dev/Source/Documentation/MyProject", ZTZQBAAA[/value]
[/matchedpair]
You will need to change the [value] line: change the path beginning with $ to your project location.
I don't think you need to change the 8 character code after the comma, but I was never quite sure what it meant. If want to be safe or things don't work, create a temporary new project and add it to VSS at the same level as your project. Copy the bit in green from the temp project and paste it into your real one. Delete the temp project.
Also make sure you delete the .cpd file before opening the project as this sometimes remembers the old location.
HTH,
Amebr
Message was edited by: Amebr
Couldn't get colours to work so changed to words. Hopefully it's clear enough.

Anyone using source control AND cloud sharing?

Hi. I'm curious if anyone has any experience or tips to share about a RoboHelp environment that uses BOTH source control and cloud sharing.
My company uses perforce. I'm purchasing a couple copies of TCS5, one for me in California, one for writer colleague in Europe. I'd like to use Perforce for version control/backup, but use Dropbox for RH asset sharing and sync. Is this workabout? I'm guessing that the Dropbox/sync mechnism won't work if one or both of us has not checked out a file that needs to be (automatically via sync) updated. ("Not checked out" = file is in read only state.)
If RH automatically checks files in/out of perforce in order to complete a cloudshare sync, that would be most cool!
Thanks in advance for your ideas!
-Kurt

Hi Kurt
Have you tried the scenario with RH 11?
It should automatically check-out the file or should prompt for it based on the settings Tools -> Options -> Version Control
I tried with Robo Source Control and SharePoint. And it is working for me. Check-in has to be done mannually.
Please try and let us know the result.
Thanks

Looking For Guidance: Best Practices for Source Control of Database Assets

Database Version: 11.2.0.3
OS: RHEL 6.2
Source Control: subversion
This is a general question aimed at database professionals, however, it is not specific to any oracle version, etc. Its a leadership question for other Oracle shops regarding source control.
The current trunk, in my client's source control, is the implementation of a previous employee who used ER Studio. After walking the batch scripts and subordinate files , it was determined that there would be no formal or elegant way to recreate the current version of the database from our source control - the engineers who have contributed to these assets are no longer employed or available for consulting. The batch scripts are stale, if you will.
To clean this up and to leverage best practices, I need some guidance on whether or not to baseline the current repository and how to move forward with additions of assets; tables, procs, pkgs, etc. I'm really interested in how larger oracle shops organize their repository - what directories do you use, how are they labeled...are they labeled with respect to version?
Assumptions:
1. repository (database assets only) needs to be baselined (?)
2. I have approval to change this database directory under the trunk to support best practices and get the client steered straight in terms of recovery and
Knowns:
1. the current application version in the database is 5.11.0 (that's my client's application version)
2. this is for one schema/user of a database (other schemas under the database belong to different trunks)
This is the layout that we currently have and for the privacy of the
client I've made this rather generic. I'd love to have a fresh
start...how do I go about doing that...initially, I like using
SqlDeveloper's ability to create sql scripts from a connected target.
product_name
|_trunk
     |_database
       |_config
       |_data
       |_database
       |_integration
       |_patch
       |   |_5.2A.2
       |   |_5.2A.4
       |   |_5.3.0
       |   |_5.3.1
       |
       |_scripts
       |   |_config
       |   |_logs
       |
       |_server
Thank you in advance.

HiWe are using Data ONTAP 8.2.3p3 on our FAS8020 in 7-mode and we have 2 aggregates, a SATA and SAS aggregate. I want to decommission the SATA aggregate as I want to move that tray to another site. If I have a flexvol containing 3 qtrees CIFS shares can I use data motion (vol copy) to move the flex vol on the same controller but to a different aggregate without major downtime? I know this article is old and it says here that CIFS are not supported however I am reading mix message that on the version of data ONTAP we are now on does support CIFS and data motion however there will be a small downtime with the CIFS share terminating. Is this correct? Thanks

Source Control continued...

Using the Repository hooks, one can trap workspace integrations and create
.cex and .pex files of the changed objects, which can be read into the SCM
tool. Right?
But how do you handle the situation where a class has been renamed? How do
you deal with all those other classes that have attributes that are of this
renamed class type? What if you want the full source code of 6 weeks ago,
before several big changes including class renames? Can you then recreate a
complete .wex file, where all the changes before 6 weeks ago are included,
but all changes since 6 weeks ago are excluded?
Is is perhaps more feasible to create a full .wex file every day, or every
week, and store that in an SCM tool? But then, what's the use of these
repository hooks?
Pascal Rottier
Atos Origin Nederland (BAS/West End User Computing)
Tel. +31 (0)10-2661223
Fax. +31 (0)10-2661199
E-mail: Pascal.Rottiernl.origin-it.com
++++++++++++++++++++++++++++
Philip Morris (Afd. MIS)
Tel. +31 (0)164-295149
Fax. +31 (0)164-294444
E-mail: Rottier.Pascalpmintl.ch

It sounds like you simply store the whole repository file in your SCM. How
else do you store partitioning schemes, which can't be exported as far as I
know.
Pascal Rottier
Atos Origin Nederland (BAS/West End User Computing)
Tel. +31 (0)10-2661223
Fax. +31 (0)10-2661199
E-mail: Pascal.Rottiernl.origin-it.com
++++++++++++++++++++++++++++
Philip Morris (Afd. MIS)
Tel. +31 (0)164-295149
Fax. +31 (0)164-294444
E-mail: Rottier.Pascalpmintl.ch
-----Original Message-----
From: Roland Ottersbach [mailto:roparcs.de]
Sent: Monday, November 27, 2000 9:06 PM
To: Rottier, Pascal
Cc: 'Forte Users'
Subject: Re: (forte-users) Source Control continued...
Hi everyone,
I'd like to take part of this discussion, as we developed a integration to
continuus configuration management suite
from continuus software. This integration goes beyond simple version control
system. It handles the software
issues as any other integration using the SCM-Hook. But it overs a lot more:
As Continuus overs as one of a few providers task based CM we support full
support of task based CM as
simple as it gets. The more we handle different releases of software
products.
The integration takes care of partition informations as well, so that with
your
sources the deployment information
and the application information is stored and can be restored any time.
Guess
you have to go back to a former
release of your product and you have released this software to certain
customers: You would like to restore your
software at that point completely, including partition information. We can
do
this.
But the best thing about this integration is, that you don't care about
retrieving your software out of the CM Tool manually
and place it back in a production repository. The integration cares for this
too. By a click you get a brand new repository
at any release you've integrated before and want to go back to as a manner
of
maintanance or merging.
Fell free to contact me, if you like.
We've choosen Continuus, because we know it a long time. Is very powerful
but
sometimes a little bit sophisticated
too. Nevertheless it overs a lot of things you would like to use, if you go
deep into configuration and change management.
Regards
Roland Ottersbach
Workflow and Change Management
parcs IT-Consulting GmbH (ww.parcs.de)
Birlenbacher Strasse 14 K
Germany
eMail roparcs.de
Mobile 0049 (0) 171 374 5171
Telefon 0049 (0) 271 870 6421
"Rottier, Pascal" schrieb:
Using the Repository hooks, one can trap workspace integrations and create
.cex and .pex files of the changed objects, which can be read into the SCM
tool. Right?
But how do you handle the situation where a class has been renamed? How do
you deal with all those other classes that have attributes that are ofthis
renamed class type? What if you want the full source code of 6 weeks ago,
before several big changes including class renames? Can you then recreatea
complete .wex file, where all the changes before 6 weeks ago are included,
but all changes since 6 weeks ago are excluded?
Is is perhaps more feasible to create a full .wex file every day, or every
week, and store that in an SCM tool? But then, what's the use of these
repository hooks?
Pascal Rottier
Atos Origin Nederland (BAS/West End User Computing)
Tel. +31 (0)10-2661223
Fax. +31 (0)10-2661199
E-mail: Pascal.Rottiernl.origin-it.com
++++++++++++++++++++++++++++
Philip Morris (Afd. MIS)
Tel. +31 (0)164-295149
Fax. +31 (0)164-294444
E-mail: Rottier.Pascalpmintl.ch
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com--
Roland Ottersbach
Workflow and Change Management
Parcs IT-Consulting GmbH (www.parcs.de)
Birlenbacher Strasse 14K
57078 Siegen, Germany
Phone 49 (0) 271 870 6421
Mobile 49 (0) 171 374 5171
Email roparcs.de

Component Source Control

Has anyone out there come up with a Source Control solution for UCM component development?
I am looking for check out/in and version control of resources so that we can better control the development effort.
We have inadvertantly propmoted several changes to components recently because of multiple developers working on the same resource.
Cheers

We've used CVS in the past to control components. Not the best, but doable. You can create build files to generate a component zip/tag easily enough.

Versioning/Source Control

Similar Messages

Maybe you are looking for