OWB Development Version Control

Hi
CAn anybody throw some light on Version controlling in OWB, I mean how we can do the verion control for the mappings and transformation that are developed in OWB.
Any response for this is greatly appreciated
Thanks
Balaji

Hi Balaji,
What release are you running?
In version 9.0.4 and higher you can use snapshots to do version management within OWB itself. You can research this in the documentation under Snapshots.
Jean-Pierre

Similar Messages

OWB 11gR2 - Version Control ?

OWB 11gR2 - Version Control ?
=======================================
I am using OWB 11gR2 (11.2.0.1) on Win XP 32 bit. We have our OWB repository is on Unix server.
I am thinking of implementing version control of OWB artifacts.
I searched the past posting of this forum/Google. I find some hits, which were posted awhile ago.
What is your solution for OWB 11gR2 version control ? I need to find that kind of solution too.
Any best practices suggestions are welcome.
Thanks in helping this thread alive.

We are using Subversion where folder structure copys OWB tree structure. Every object is exported to separate mdl file. Also we store all DML scripts in separate forlder. After developers have finished their changes they manually gather affected objects to collection. We have written build/export/import tool (OMB+, ActiveTcl, ANT, SQLPlus) that they use next to export OWB objects aumatically from OWB structure to Subversion structure. Changelist with links to exported objects is aumatically maintained. Based on that release package is created at buildtime containig mdl files from Subversion. Release package is also stored in Subversion. When installing release to another environment (TEST, PROD) package is aumatically downloaded from Subversion, mdl files imported to OWB and deployed, DMLs executed in database.

OWB Change Management/Version Control Best Practice

Hi
I am about to start developing a data warehouse using OWB 10g R2, and I've been doing quite a lot of research into the various deployment/change management/version control techniques that can be used, but am still unsure which is the best to use.
We will have 2-3 developers working on the project, and will be deploying from Development, to Test, to Production (each will have a separate repository). We want to be able to easily identify changes made between 1 release and the next to have a greater degree of control and awareness of what goes into each release. We also wish to use a source control system to track changes (we'll probably use SVN, but I don't think that the actual SCS tool makes a big difference to our decision at this point).
The options available (that I'm aware of), are:
1. Full MDL export/import.
2. Snapshot MDL export/import.
3. Manual coding of everything using OMB Plus.
I am loath to use the full MDL export/import functionality since it will be difficult, if not impossible, to identify easily the changes made between 1 release and the next.
The snapshot MDL export/import functionality is a little better at comparing releases, but it's still difficult to see exactly what has changed between 1 version and the next - particularly when a change to a transformation has been made. It also doesn't cope that well with tracking individually made changes to different components of the model.
The manual coding using OMB Plus seems like the best option at the moment, though I keep thinking "What's the point of using a GUI tool, if I'm just going to code everything in scripts anyway?".
I know that you can create OMB Plus code generation scripts to create your 'creation' scripts, but the code generation of the Alteration scripts seems that it would be more complicated than just writing the Alteration scripts manually.
Any thoughts anyone out there has would be much appreciated.
Thanks
Liffey

Well, you can also do per-object MDL exports and then manage those in your version control system. With a proper directory structure it would be fairly simple to code an OMB+ Script that scans a release directory tree and imports the objects one by one. I have done this before, although if you are using OWB as the primary metadata location for database objects then you have to come up with some way to manage object dependency order issues.
The nice thing about this sort of system is that a patch can be easily shipped with only those objects that need to be updated.
And if you force developers to put object-level MDL into your version control system then your system should also have pretty reporting on what objects were changed for a release and why.
At my current job we do full exports of the project MDL and have a deployment script that drops the pre-existing deployed version of the project before importing and deploying the new version, which also works quite well - although as you note the tracking of what has changed in a release then needs to be carefully managed elsewhere. But we don't deploy any of our physical database objects through OWB. Those are deployed from Designer, and our patch script applies all physical changes first before we replace the mappings from the OWB project. We don't even bother synching the project metadata for tables / views / etc. at deployment. If the OWB project's metadata for database objects is not in sync with Designer, then we wind up with deployment errors. But on the whole it works pretty well.

OWB 10g/11g version control

I am using OWB 10g release 2 but there is no feature for version control. The snapshot feature and export/import can help but Its very difficult with big project.
Is there any new feature with OWB 11g release 1 or 2 for version control ? Do you have any proposition for version control in 10g ?
Robin
Edited by: user451399 on 2009-06-12 08:07

Hi Robin,
In the repository there can be only one version at the moment. If you have to work on an older release, you have to load it into another repository.
We proceed as follows:
1. Build a collection containing all objects that belong to the release
2. Export that collection
3. Check the file into CVS
4. Import the file into production repository (in production db)
5. Deploy from the production repository to the production target schema
That way the release that is currently deployed on production is also in the production repository. You may do hotfixes directly here or just have a look at what is currently deployed.
In our development repository we can work on new features.
I gave a talk about automating this process on DOAG 2008. You may request the presentation here [http://www.metafinanz.de/leistungen/leistungsbereiche/bi-reporting/data-warehousing/kontaktformular/|http://www.metafinanz.de/leistungen/leistungsbereiche/bi-reporting/data-warehousing/kontaktformular/]
Though the slides are in german they show the architecture and should give you some idea.
Regards,
Carsten.

OWB Process Flow - How is the best version control tool ??

HI all,
I just start work with OWB and I have a question to know how is the best way to do something.
Imagine the scenario below:
If I have 2 or more requests for example:
Request 1: Create a Dimension City.
Request 2: Create a Dimension Products.
I Have ONE process flow and i need put my changes inside. This is my problem.
In my scenario I don't know what Request goes to Prod First.
If I put the Request 1 and Request 2 in my PROCESS FLOW, maybe I need change is someone decide change MY REQUEST PRIORITY.
There is something in OWB to "control the version or changes" ?? For a mapping I export the MDL and commit on SVN, but I dont know haw can i do with the process flow.
Something to agree multiples peoples work in different mappings and a SAME PROCESS FLOW ??
What is best way to work with process flow and version control.
What are the best practices when it comes to version control?
Thanks.

Amit,
Are you really doing this in 10.1.3.x and not 11g?
At any rate, I don't see how #2 and #3 relate whatsoever to your choice of a version control system. OK, maybe in #2 if there is some "maintenance" activity to be done against the version control server. Subversion is the open source alternative that you listed there and is pretty commonly used. If your company is already using one of the mentioned tools, why change? About the only thing I'd mention is to advise you NOT to use CVS for well documented reasons (JDev does support it) - if you would have picked CVS otherwise, choose Subversion. As far as question #1 - I've only used Subversion (well, I did use CVS for a while) with JDeveloper, so I can say it was "effective enough for me." In 10.1.3.x, I also used the external svn tools for doing lots of things like merging and so forth; in 11g, the support is much much better.
Best,
John

Development backup and version control questions

Two question I want to ask as an Oracle XE beginner:
1.How to backup my work (database objects and application pages) each day?
2.What is the best practice for version control for the Oracle XE development projects? Does anyone use CVS?
Thank you.

Two question I want to ask as an Oracle XE beginner:
1.How to backup my work (database objects and
application pages) each day?Take a look at the backup script in the product directory.
C.

Is it possible to develop the control charts in WAD.

Hi Gurus and Experts
We need your suggestions to go futhure with our requirement.
Right now KPI's are currently displayed in graphical form with the
ability to drill down into WO's( Work orders) from the graph page. our
new requirement is to get exactly the same set of information captured
and presented in control chart form. This is to be an adjunct. to, not
replace, the existing graphical set of data. Upper and lower control
limits will be set initially by the business, and the same drill down
functionality should be available from the control chart. The charts
can be displayed seperately from the exisiting set of charts if this
makes it easier.
Can you please suggest us whether is it possible to develop the control
charts and also have the functoinalities of the existing dashboards
(example drill down of WO's using the control charts) in WAD or through
viusal composer
Waiting for your responses..
Thanks
Ravi...

Hello dj_page!
Thanks for the answer, but I know this already.
My problem is, that the small picture in the side panel and the histogram in LR5 are bigger than in LR4.
The two pictures are showing the difference between the versions.
On the left hand (LR4) you can see a smaller preview and histogram than on the right hand (LR5).
In each version you can change the size of the side panel only as small as the preview-window is.
The pictures are also showing the smallest size of the side panel in each version.

Regarding version control

Hi,
Could u please help me out in giving some ideas of version control in sap?
First let me give some example as follows:
First if i develop something in the developement server then later when i transfer to the QA server and later to production server then is there any change in version.
Please give me a details of this issue????
Thanks,
Batista....

hi priya,
Version Control
Version control is a mechanism that helps maintaining the revision history of a development resource and tracking the changes done to it. It defines a set of constraints on how a development resource can be changed. A development resource that complies with the constraints defined by the version control is called a versioned resource. When a versioned resource is modified or deleted, a new version is created for the resource. A unique sequence number is associated with each version of the resource created in a particular workspace. This sequence number identifies the order in which the versions were created in that workspace. The DTR graphically represents the relationship between the different versions of a versioned resource in the form of a version graph.
For the representation of version graphs, this document follows the conventions shown in this figure.
The figure shows the meaning of the symbols in the version graph.
The following changes are tracked by the version control mechanism of the DTR:
·        Addition of the resource to the repository
·        Modification of the resource in the repository
·        Deletion of the resource from the repository
In all the above cases, a new version of the resource is created.
Production Delivery
Packaging
To deliver your product, you have first to package it. There are different packages you can use for shipping your product to your customers:
●      Software Component Archives (SCAs) this is the standard way to deliver software for the SAP NetWeaver platform.
●      Software Deployment Archives (SDAs) for top-level applications you can deliver only the executable part of the software. You can directly deploy the SDA file.
●      Public Part Archives (PPAs) in Development Component Interface Archives (DCIAs) for reusable components (Java EE server libraries, Web Dynpro components, Visual Composer components and so on). You can deliver only the metadata of the components. DCIA can be included in SCA file too.
How to do that?
Using the command line tool provided with the SAP NetWeaver Composition Environment you can:
●      package a collection of components into an SCA including only the deployable archives. This is required if you do not want others to reuse the delivered components.
●      package a collection of components into an SCA including the deployable archives and the corresponding interface archives. This allows customers to develop against these components. Those customers can directly import the SCA into their own SAP NetWeaver Development Infrastructure (NWDI) or into an SAP NetWeaver Developer Studio local installation.
●      package the public parts of a component together with the required metadata into a DCIA (and further into an SCA).
●      include source code into an SCA.
●      unpack a deliverable archive and drop the result into an existing version control system for example, or directly import them into an existing Design Time Repository (DTR).
Delivery of Source Code for Further Customization
In addition, you can deliver source code to your customers to allow further customizing or add-on development. The deliverable archive may contain sources for:
●      individual development components (DCs).
●      a collection of development components, for example a whole software component (SC).
Example
A customer can add a new source compartment to an existing configuration, and then locate that compartment in the file system where it is accessible by the version control system in charge. Then he or she extracts the sources with the command line tool to the compartments root directory and refreshes the configuration in the SAP NetWeaver Developer Studio. The compartment tree is populated with components from the archive. Afterwards, the customer may put those components under version control. Deliverables that contain only individual components may be treated accordingly.
This mechanism may also be used for other purposes, for example for setting up a simple backup and restore mechanism for components in Developer Studio, or sharing DC sources without having a central version control system: a developer may pack a compartment and store the resulting SCA on a central share or backup system. Another developer may take that SCA and import it.
Limitations
Note the following limitations connected with this kind of source code delivery:
●      There is no support for handling conflicts when different actors in a delivery chain develop independently in the same source code. You cannot prevent the customer from modifying delivered sources. When you ship a new version of the sources, there is no special support for updating and no support for merging the update with modifications done by the customer. You and the customer have to agree on a process how those conflicts are handled. For example, the customer can decide not to import the update you deliver directly into the active development line, but to unpack the delivered sources to some unconnected sandbox system and perform the required merges manually.
●      When you deliver source code to customers, it is important that you also deliver the required libraries and generators that are needed to build these sources. For example, it may be necessary to ship some archive compartments that contain used components.
●      There is no support for delivering deletions in a new version. If a source file was deleted, the customer has to manually ensure that the file is also deleted in the Developer Studio or source code management system.
●      If a customer prefers to work with the SAP NetWeaver Development Infrastructure (NWDI), this customer cannot directly import the source delivery package into the NWDI landscape. Between NWDI landscapes at different places, sources usually are exchanged through a more sophisticated export format that contains not only the pure source code, but also the versioning meta information of the exporting DTRs. This ensures that the importing repository can detect conflicts that arise due to modifications. If this versioning information is not available, the only way to import source deliveries is to unpack them to a file system and manually put them under version control with the Design Time Repository perspective of the Developer Studio. In case of an update, the customer would have to check out all affected files, merge them with the new versions from the source delivery, and finally check them in as a new version.
More information: Composition Environment Command Line Tool
see this url
http://www8.sap.com/businessmaps/0134713B1D6046C59DE21DD54E908318.htm
thanks
karthik
reward me if usefull

Oracle Service Bus Configurations version control and deployment automation

Hi,
Currently we have OSB10gR3 installed and we use the web based sbconsole to create projects and proxy services. It's all working well and good!!
We are at the state where we need to think about source control, migration of artifacts from dev to test and to prod.
I'm looking for pointers to version control the artifacts of OSB projects, what could be version controlled (no binaries) and how do we extract those artifacts?
How do we customize those artifacts while migrating to different environments in an automated fashion?
Please point me to best practices and gotchas that we should be aware of while dealing with deploying OSB proejcts from test to Prod.
Thanks in Advance!!

After reading the threads mentioned by Deba, I'm able to get this all worked out with SBConsole itself. Experts, please review my approach below and let me know if I have overlooked anything.
Simple advantage I see in using sbconsole is that it requires less maintenance, i.e. avoids rolling out another IDE (Eclipse -Workshop plug-in) to IT developers and at the same time provides the functionality that we are looking for. Currently, JDeveloper is our primary IDE, so we thought it's best to wait till OSB development gets integrated into JDev.
This is the deployment workflow which worked for us,
Developer:
1)Develops Proxy services using SBconsole in Dev environment.
2)Creates sbconfig.jar by using the export functionality available in System Administration link in sbconsole
3)Checks-in ALL the files present in the above jar into version control under the proxy service project name
4) Creates customization file using the customization file link in System Administration and modifies the value for each environment i.e. creates two files test_customfille, prod_customfile
5)Checks-in the customization files into version control under the same proxy service project
Promotion to Test and Prod
1) From the source control, service proxy is built (actually the jar file of all files including the custom file is created)
2) SCP proxy_sbconfig.jar file to Test or Prod box
3) Follow the steps mentioned in Auto deploy of ALSB/OSB artifacts - Proxy, WSDL and webservices...
4) Depending on the server, test or prod, pick the right customization file and deploy using ANT.
Thanks!!

Oracle 10g R2 - Metadata Issue With Version Controlled Resources

We are trying to utilize the Oracle 10g R2 feature that allows user-defined metadata to be attached to XML DB resources. However, we are encountering errors when we try to append/attach metadata to a version-controlled resource (VCR). The following steps were followed:
1. Register a new schema to be used for metadata (XMLSCHEMA.registerSchema).
2. Add a new resource to to the XML DB and make it version controlled (DBMS_XDB.createResource and DBMS_XDB_VERSION.makeVersioned).
3. Checkout the newly created version-controlled resource (DBMS_XDB_VERSION.checkout)
4. Add metadata to the version-controlled resource (DBMS_XDB.appendResourceMetadata)
However, after step 4, the errors shown below are encountered:
========================================================
begin
ERROR at line 1:
ORA-00600: internal error code, arguments: [qmxStrCopy: INLOB 2], [], [], [],
ORA-06512: at "XDB.DBMS_XDB", line 890
ORA-06512: at line 2
========================================================
The steps followed for adding metadata to a resource were taken from Chapter 26 of the "Oracle XML DB Developer's Guide 10G Release 2" (http://download-east.oracle.com/docs/cd/B19306_01/appdev.102/b14259/xdb_repos_meta.htm#sthref2302).
Is is possible to append and maintain metadata to an XML DB version controlled resource (VCR)? If so, what are the correct steps to do this? Note that if this is tried with a resource that is not version controlled, then no errors are encountered.
Thanks,
Steve

It appears that this issue has been solved in the next release of the database
QL> spool testcase.log
SQL> --
SQL> connect &1/&2
Connected.
SQL> --
SQL> var schemaURL varchar2(256)
SQL> var schemaPath varchar2(256)
SQL> var resourcePath varchar2(256)
SQL> --
SQL> begin
2    :schemaURL := 'metadata.xsd';
3    :schemaPath := '/public/metadata.xsd';
4    :resourcePath := '/public/metadataTest.txt';
5 end;
6 /
PL/SQL procedure successfully completed.
SQL> call dbms_xmlSchema.deleteSchema(:schemaURL,4)
2 /
Call completed.
SQL> declare
2    res boolean;
3    xmlSchema xmlType := xmlType(
4 '<?xml version="1.0" encoding="UTF-8"?>
5 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb" elementFormDefault="qualified" attributeFormDefault="unqualified" xdb:storeVarrayAsTable="true">
6          <xs:element name="root" type="rootType" xdb:defaultTable="METADATA_TABLE"/>
7          <xs:complexType name="rootType" xdb:SQLType="METADATA_ROOT_T">
8                  <xs:sequence>
9                          <xs:element name="child" type="childType"/>
10                  </xs:sequence>
11          </xs:complexType>
12          <xs:complexType name="childType" xdb:SQLType="METADATA_CHILD_T">
13                                  <xs:sequence>
14                                          <xs:element name="Child1" type="xs:string"/>
15                                          <xs:element name="Child2" type="xs:string"/>
16                                  </xs:sequence>
17          </xs:complexType>
18 </xs:schema>
19 ');
20 begin
21    if (dbms_xdb.existsResource(:schemaPath)) then
22      dbms_xdb.deleteResource(:schemaPath);
23    end if;
24    res := dbms_xdb.createResource(:schemaPath,xmlSchema);
25 end;
26 /
PL/SQL procedure successfully completed.
SQL> begin
2    dbms_xmlschema.registerSchema
3    (
4      :schemaURL,
5      xdbURIType(:schemaPath).getClob(),
6      TRUE,TRUE,FALSE,TRUE,
7      enableHierarchy=>DBMS_XMLSCHEMA.ENABLE_HIERARCHY_RESMETADATA
8    );
9 end;
10 /
PL/SQL procedure successfully completed.
SQL> declare
2    res boolean;
3 begin
4    if dbms_xdb.existsResource(:resourcePath) then
5      dbms_xdb.deleteResource(:resourcePath,4);
6    end if;
7    res := dbms_xdb.createResource(:resourcePath,'Mary Had a Little Lamb');
8 end;
9 /
PL/SQL procedure successfully completed.
SQL> commit
2 /
Commit complete.
SQL> select xdbUriType(:resourcePath).getClob()
2 from dual
3 /
XDBURITYPE(:RESOURCEPATH).GETCLOB()
Mary Had a Little Lamb
SQL> declare
2    resid raw(16);
3 begin
4    resid := dbms_xdb_version.makeVersioned(:resourcePath);
5 end;
6 /
PL/SQL procedure successfully completed.
SQL> commit
2 /
Commit complete.
SQL> begin
2    dbms_xdb_version.checkout(:resourcePath);
3 end;
4 /
PL/SQL procedure successfully completed.
SQL> commit
2 /
Commit complete.
SQL> set long 10000 pages 0 lines 150
SQL> --
SQL> select r.res.getClobVal()
2    from resource_view r
3   where equals_path(res,:resourcePath) = 1
4 /
<Resource xmlns="http://xmlns.oracle.com/xdb/XDBResource.xsd" Hidden="false" Inv
alid="false" VersionID="1" ActivityID="0" Container="false" CustomRslv="false" V
ersionHistory="false" StickyRef="true">
<CreationDate>2006-06-10T05:01:25.355009</CreationDate>
<ModificationDate>2006-06-10T05:01:25.355009</ModificationDate>
<DisplayName>metadataTest.txt</DisplayName>
<Language>en-US</Language>
<CharacterSet>UTF-8</CharacterSet>
<ContentType>text/plain</ContentType>
<RefCount>1</RefCount>
<ACL>
    <acl description="Public:All privileges to PUBLIC" xmlns="http://xmlns.oracl
e.com/xdb/acl.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:sch
emaLocation="http://xmlns.oracle.com/xdb/acl.xsd                           http:
//xmlns.oracle.com/xdb/acl.xsd">
      <ace>
        <grant>true</grant>
        <principal>PUBLIC</principal>
        <privilege>
          <all/>
        </privilege>
      </ace>
    </acl>
</ACL>
<Owner>SCOTT</Owner>
<Creator>SCOTT</Creator>
<LastModifier>SCOTT</LastModifier>
<SchemaElement>http://xmlns.oracle.com/xdb/XDBSchema.xsd#binary</SchemaElement
>
<Contents>
    <text>Mary Had a Little Lamb</text>
</Contents>
<VCRUID>15DE79F263F7CC00E040578C2A0656F8</VCRUID>
</Resource>
SQL> begin
2    dbms_xdb.appendResourceMetadata(:resourcePath,xmltype(
3 '<root xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
4         xsi:noNamespaceSchemaLocation="metadata.xsd">
5      <child>
6        <Child1>AAA</Child1>
7        <Child2>BBB</Child2>
8      </child>
9 </root>'));
10 end;
11 /
PL/SQL procedure successfully completed.
SQL> commit
2 /
Commit complete.
SQL> select r.res.getClobVal()
2    from resource_view r
3   where equals_path(res,:resourcePath) = 1
4 /
<Resource xmlns="http://xmlns.oracle.com/xdb/XDBResource.xsd" Hidden="false" Inv
alid="false" VersionID="0" ActivityID="0" Container="false" CustomRslv="false" V
ersionHistory="false" StickyRef="true">
<CreationDate>2006-06-10T05:01:25.355009</CreationDate>
<ModificationDate>2006-06-10T05:01:25.558913</ModificationDate>
<DisplayName>metadataTest.txt</DisplayName>
<Language>en-US</Language>
<CharacterSet>UTF-8</CharacterSet>
<ContentType>text/plain</ContentType>
<RefCount>1</RefCount>
<ACL>
    <acl description="Public:All privileges to PUBLIC" xmlns="http://xmlns.oracl
e.com/xdb/acl.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:sch
emaLocation="http://xmlns.oracle.com/xdb/acl.xsd                           http:
//xmlns.oracle.com/xdb/acl.xsd">
      <ace>
        <grant>true</grant>
        <principal>PUBLIC</principal>
        <privilege>
          <all/>
        </privilege>
      </ace>
    </acl>
</ACL>
<Owner>SCOTT</Owner>
<Creator>SCOTT</Creator>
<LastModifier>SCOTT</LastModifier>
<SchemaElement>http://xmlns.oracle.com/xdb/XDBSchema.xsd#text</SchemaElement>
<Contents>
    <text>Mary Had a Little Lamb</text>
</Contents>
<VCRUID>15DE79F263F7CC00E040578C2A0656F8</VCRUID>
<Parents>15DE79F263F8CC00E040578C2A0656F8</Parents>
<root xmlns="" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNam
espaceSchemaLocation="metadata.xsd">
    <child>
      <Child1>AAA</Child1>
      <Child2>BBB</Child2>
    </child>
</root>
</Resource>
SQL> quit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.0.0 - Alpha
With the Partitioning and Data Mining options
I've filed bug 5313655 for the 10.2.x behavoir. If this is important to you you might want to consider signing up for the forthcoming beta program for the next release of the database

Application size in terms of pages and performance and Version Control

Currently I'm looking into the best way to version control our APEX applications. From other threads, it seems it's an area that leaves much to be desired. We are on the verge distributing a large APEX project commercially but I cannot find a suitable versioning method to support bug fixes and new development happening at the same time to the same set of applications. I just hope everyone out there realises versioning is a vital area of the development process and VOTES for it in the V3 poll.
Anyway, enough of the my whinging. I did have a brain wave (quite rare !). What would the drawback be to have only 1 or 2 pages per application. This would allow a developer to always import the application at the start of work (ie from versioning software such as VSS or PVCS) and then export it at the end back into say PVCS. The application has everything self contained and correct versions etc.
This would allow more developers to work on different areas at the same time as opposed to having many pages in the one application where developers could step on each others toes etc. I've considered importing/exporting pages but the fact you cannot lock shared objects means there is a possibility that if many developers are working on the same application someone will change something that affects pages other than their own. It would also be a nightmare to tie up different versions of of pages, shared objects, applications etc. Would there a performance problem with this method ? Incidentally, why can't TABS be shared/subscribed across applications. It means they have to be created separately in each application whereas things like Nav Bars and Templates can be shared across applications.
Currently, my thoughts are that: bug fixing for a production release has to be in a separate stream (apex installation) from say new development work for the same set of applications BUT what this means is that the bug fixes have also to be manually applied in the new development stream - which is a considerable overhead (ie twice the work).
Thanks for hearing me out - assuming you survived to the end !
Any encouraging comments would be appreciated !

Wim,
I don't entirely understand the behavior. There should be little/no difference between the two cases. I'm assuming you have no indexes, which isn't recommended for such large containers anyway. Can you make your document set available to me so I can see if I can reproduce the behavior and look at it more closely? A single container, or dbxml_dump of a container is sufficient (both compress well).
Contact me directly at george dot feinberg at you know where.
George

Best practice for version control B2B, ESB and BPEL

Hello,
we are setting up a new system using B2B, ESB and BPEL. The development team is more experienced working with PL/SQL, Oracle Workflow and we are worried that Jdeveloper generates changes to the source files during development and that we might have problems with the version control.
Is there any best practice for setting up version control for these systems? Do we need to take anything in particular into consideration when setting up the projects?
We are using Serena Dimensions 9.1 for version control with the add-on in Jdeveloper.
Thanks in advance!

I believe JDeveloper has a plugin for Dimensions.
I havent used it but to get it, go to tools (It may be help I don't have JDeveloper on this machine to confirm) check for updates.
If you select the thrid party check box - next, you will see an entry for dimentions.
Configure the connection and develop as you would any other project.
cheers
James

Version Control for OSB Proxy/Business Services ?

Dear all
I've used the browser-based osb console to expose a legacy web-service as follows :
1. Create a Session
2. Create a BusinessService based on the legacy web-service WSDL
3. Create a ProxyService based on the BusinessService WSDL
4. Activate the Session
I now have two further questions :
1. How do we version control the OSB "code" ? (we use Subversion for other code)
2. How do we implement it in other environments (TEST, PROD, etc.)
Thanks,
Peter.

>
Are there other reasons why you say it's not the most ideal way of development ?
>
Versioning binary files is always a pain. You can't compare them, you can't merge them ... Another point, if you put your jar archive with OSB artifacts under version control, you will most probably face issue related to end of line styles (mac, unix, windows).
However, the most important point is usability. I want to version .proxy and .biz services to see right in IDE that I changed something and I should check that in for the others. I don't want to risk that I forget something. And I also want to see what other users committed, what sources they work on ... You loose all of that by versioning jar file. I would never go this way.

Version control tool for Mac OS X?

Hi all
If using labview on Mac OS X,
do you have some version control tools to recommend?
Thanks a lot

As far as i know, LV for Mac does not integrate with source code control provider. LV for Windows has two requirements for this:
a) Professional Development Environment
b) A source code control provider compatible to the Microsoft Source Interface
There is still always (Mac, Linux and Windows alike) the possibility to control source files using the SCC providers client software.
Many open source project SCCs like CVS or Git integrate, at least in Windows, in the File Explorer.
I recommend you to research possible solutions like this for Mac.
The next question is if you want to use a distributed SCC or a local one. Depending on this, you will have to setup a network server with compatible provider (e.g. RhodeCode).
LV provides both a Diff and Merge tool as EXE (Professional). I am not sure if this is also true for the Mac version, so look for "LVCompare" and "LVMerge".
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

The main develop module controls have disappeared from the develop window. How do I recover them?

The main develop module controls have disappeared from the develop window. How do I recover them? I'm working with Lightroom 5.3. The missing controls are the sliders for exposure, contrast, clarity, etc. I must have inadvertantly clicked something that made them disappear but nothing I've tried brings them back. I've never had this experience in the years I've been using Lightroom (since version 1.1).

Right-click on any other item Tone Curve for ex., and check on "Basic" if that's what you are missing.
If you miss the complete Develop module right-click any other item Library for ex and put a check on Develop

OWB Development Version Control

Similar Messages

Maybe you are looking for