Version Control

I have RoboHelp HTML Version 7. We use RoboHelp for publishing our procedures; we use our Word documents for making reviews, updates, etc. and then just reimport and republish as necessary. Our company is asking us to use version control on our procedures. Since we cannot use the version control in RoboHelp, does anyone know of a version control app that can be used where we can import our docs from that app into RoboHelp? Version 7 only allows importing of Word, PDF, and HTML docs from folders on our computers or shared drives. I'm not sure if Version 8 has additional features.

Hi Karen
Attaching will not work. If you want to supply samples, you will need to make them available some other way such as Acrobat.com or YouSendIt.com.
Cheers... Rick
Helpful and Handy Links
RoboHelp Wish Form/Bug Reporting Form
Begin learning RoboHelp HTML 7 or 8 moments from now - $24.95!
Adobe Certified RoboHelp HTML Training
SorcererStone Blog
RoboHelp eBooks

Similar Messages

How do I fix project after "Remove From Version Control" corrupted it?

I am using RoboHelp 9.0.1 and installed both Tortoise SVN 1.6.9 and latest PushOK SVNSCC then added my large RoboHelp project to SVN. I was able to check in and out files from SVN but had several issues with it:
1) Super super slow. Working with folders or any renames would take 10 seconds per file and up to 1 hour if needed to refresh the root folder.
2) I could not perform some actions at all, such as delete, rename, or move folders. I kept getting COM errors.
I therefore decided that working with SVN and RoboHelp is not practical, at least not on my VPN so I decided to disconnect the project from source control and just work locally. The only option that I saw that sounded like it would do that was the "Remove from Version Control". This started a process that lasted for several hours. At the end of it, I now have several significant issues:
1) The order of the files and folders in my Project Manager is completely wrong now. I have almost 1000 topics and reordering all of them is not possible.
2) The Table of Contents, Glossary, and Index files appear empty. They had content before.
2) A couple of the Single Source Layouts I had created are completely missing.
3) Many, but not all, of the folders have tons of files with the extension ending in "_temp_removed_by_svn"
4) Many, but not all, of the files are actually gone from SVN so I can't recover a clean image. There was no warning that this command would actually delete the files from SVN (I thought it would just remove the version control connection).
5) Who know what other issue exist that I haven't seen.
Any idea how I can fix this?
Thanks in advance,
Dan

Are the "_temp_removed_by_svn" files in your local folder or SVN? Let us know how you get on with the new project. It sounds like something is wrong with SVN. Can you use the SVN Log command to see whether there is a different version you can restore. This might also give you an indication of what might have caused the problem. You could try deleting your CPD file. It gets rebuilt it is isn't there anyway. This file can become bloated and it is good practice to delete it when it gets close to 2mb in size. Your project is fairly large and has a lot of folders and may affect performance. Have you considered splitting them and merging the output? I know you probably don't want to consider this right now, but I think it may be a better long term solution.
The RoboColum(n)
@robocolumn
Colum McAndrew

Can I have a library of PDF docs with version control? Can it cope with version nos. embedded in the file name?

I manage a set of documents which are edited in Word but "published" as PDFs (using Word 2010's save to PDF capability).
I want to create a library for them on SharePoint (my company has SharePoint Online via its Office 365 subscription).
I'm pretty much a SharePoint novice but even I can see it's easy to upload the documents to a simple library. The things that are giving me a headache are:
Can I tell SharePoint what the version number of the uploaded PDF document is? The version number as understood by the library needs to match the version number written into the document (where it is called a revision number and increments in whole numbers
starting from zero).
How do I handle replacing the uploaded PDF documents with new versions? If they were Word documents I could edit them by opening them from the SharePoint library, checking them out if necessary, and SharePoint would handle version control.
But since the PDFs are generated from editable masters (Word documents) which are NOT on SharePoint I would need to edit the local Word document on my PC then generate a PDF version then upload it to replace the existing PDF document in the
library. Is it easy to upload a new document over the top of an old in a SharePoint library?
Hoping someone can give me some answers.
Regards,
Bruce Officer

hi Bruce,
1. It sounds like what you need is to set the starting version number since your revision number increments in whole numbers, it would match up to SharePoint once the starting version number is set. You can potentially create a new custom field in the
library to manually track the version of the uploaded PDF document, but this might not match up with SharePoint's own version number and could get confusing. Another possibility is to upload dummy versions of the PDF document until the SP version
matches with the revision version and then delete these dummy versions.
2. When you upload the PDF document again into the library, it should prompt you to see if you want to replace the existing. If you proceed with the upload, it should replace and increment the SharePoint version number.
Please Mark Answered if my reply solves your problem. Thanks!
Jeff Thai
Technical Solutions Architect, AvePoint
http://www.AvePoint.com

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

Hi.
I'm setting up a file share, and want some sort of version control on the file share. What's the best practice method for this sort of thing?
I'm coming at this as a subversion server administrator, and in subversion people keep their own copy of everything, and occasionally "commit" their changes, and the server keeps every "committed" version of every file.
I liked subversion because: 1) users have their own copy, if they are away from the office or make a big oops mistake, it doesn't ever hit the server, and 2) you can lock a file to avoid conflicts, and 3) if you don't lock the file and a conflict (two simultaneous edits) occur, it has systems for dealing with conflicts.
I didn't like subversion because it adds a level of complexity to things -- and many people ended up with critical files that should be shared on their own hard drives. So now I'm setting up a fileshare for them, which they will use in addition to the subversion repository.
I guess I realize that I'll never get full subversion-like functionality in a file share. But through a system of permissions, incremental backups and mirroring (rsync, second-copy for windows users) I should be able to allow a) local copies on user's hard drives, b) control for conflicts (locking, conflict identification), and keeping old versions of things.
I wonder if anyone has any suggestions about how to best setup a file share in a system where many people might want to edit the same file, with remote users needing to take copies of directories along with them on the road, and where the admin wants to keep revisions of things?
Links to articles or books are welcome. Thanks.

Subversion works great for code. Sort-of-ok for documents. Not so great for large data files.
I'm now looking at using the wiki for project-level documentation. We've done that before quite successfully, and the wiki I was using (mediawiki) provides version history of pages and uploaded files, and stores the uploaded files in the file system.
Which would leave just the large data files and some working files on the fileshare. Is there any way people can lock a file on the fileshare, to indicate to others that they are working on it and others shouldn't be modifying it? Is there a way to use unix permissions (user-group-other) permissions, "chmod oa-w" to lock a file and indicate that one is working on it?
I also looked at Alfresco, which provides a CIFS (windows SMB) view of data files. I liked it in principle, but the files are all stored in a database, not in the file system, which makes me uneasy about backups. (Sure, subversion also stores stuff in a database, not a file system, but everyone has a copy of everything so I only lose sleep about backups regarding version history, not backups on the most recent file version.)
John Abraham
[email protected]

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.

How to turn off Check Out prompt in RH7 for VSS version control.

Using RH7 HTML, and VSS version control. Have been using without problem for 2 years. Now I had to get a new computer
set up, VSS seems to be correctly set up with RoboHelp, and asks to 'get latest' when I open a project, in the usual way.
However, each time I try to edit a topic in RH now, I am prompted to check out the topic.This should happen automatically. the RH tip that displays says:
"To turn off prompts when performing version control tasks manually, clear the option on the version control tab. Files are then checked out automatically.
Note: Files not selected in the list cannot be checked out."
this is unclear - there IS no version control tab, and which option are they saying to clear? there is a version control toolbar, and File>Version Control menu, neither of which has a 'prompt checkout' option.
I need not to check out manually every time!

Use the Tools > Options menu. There should be a "Version Control" tab in that dialog box.

Version Control for adobe forms

Dear All,
We have a situation where we already go live with version 0 of our adobe form. Now, we have an enhancement to the form i.e.: some new functionalities and new field. Previously we have tried to transport the new changes to the production without any version control and those processes that have been already started prior to the new changes encounter error when the user continues the process.
I am wondering how do the version control works and any documentation on how to configure it?
Thanks in advance
Regards,
Bryan

Hi Brian,
Here is some information that I found in the IMG on Create ISR Scenario...
Create ISR Scenario
Use
In this IMG activity, you create an ISR scenario that has a one-to-one relationship with a form scenario. To be able to use a form scenario in a process, one ISR scenario must exist for each form scenario. The ISR scenario and the form scenario must be linked with each other. You make this setting in Customizing for HR Administrative Services in the IMG activity Link ISR Scenario with Form Scenario.
In the form scenario, you define primarily the basic set of form fields and their processing through the backend services. In the ISR scenario, you specify the definition of the user interface. You also specify which form is used for the display and how the layout of this interactive form is designed. You use interactive forms based on Adobe software to create and process the forms.
ISR scenarios and form scenarios are version dependent. The version numbers of the ISR scenario are assigned automatically. Note that a form scenario must have exactly the same version as the linked ISR scenario. For this reason, you should always create a new version in the ISR scenario first and then use the same version number when you create a version in the form scenario manually.
Note
If an ISR scenario or form scenario (with an existing version) has already been used in a productive process, you should not change the configuration. If you want to make changes to a process or an ISR scenario or form scenario, you should always create a new version, and only ever use that new version in the future. In this way, processes that have been started can be concluded with the old version and new processes can be started simultaneously with the new version.
This is from the Create Form Scenario documentation...
Create version
Form scenarios are version dependent, which means that there is at least one version of each form scenario. Versions are linked with processes. Since processes can vary, you must also be able to adjust the associated scenarios. To be able to provide different forms for process variants, you create versions.
You can still process and change an existing version at a later point in time. Once a version has been used to execute a process, you should not make any more changes to this version; instead, you should create a new version.
The form scenario and the (linked) ISR scenario are both version dependent. They must always have exactly the same version numbers. Note that the version number of the ISR scenario is generated and cannot be entered manually. When you create a new version in the form scenario, you therefore have to use the version number generated in the ISR scenario.
If you have already made extensive Customizing settings for the form scenario and want to create a new version based on the settings, you should use the IMG activity Manage Form Scenario.
Hope this helps...
Cheers,
Kevin

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

Can we use RoboHelp with Eclipse as version control?

Im am using RoboHelp 7 in the Tech Comm Suite in a Windows XP environment.
I see a lot of information on using RoboSource as versionn control, but I'm not seeing a lot of information on other third-pary version control software. I did see one posting that suggested that if you are planning to use third-party software, you should uninstall RoboSource first. I can't seem to figure out the following:
How do you determine if your version control (Eclipse) supports Microsoft SCC API?
How do you get RH to recognize Eclipse? Even though I uninstalled RoboSource Control 3, it still shows up in the Select Version Control Provider
Are there step-by-step instructions anywhere that show how to get RoboHelp to recognize third-party software?
As always, thanks for your assistance.

Colum,
Thanks for recommending that I visit Peter's web site. It has a great page on Eclipse. Wish I had read it before I was shoved kicking and screaming into using it. However, it did stop short of providing me with information to troubleshoot the problems I'm having with Eclipse and RH 7. I sent him an e-mail from the site and hope that he will be able to answer it.

Version Control in RoboHelp 9: Changing projects

I am using Robohelp version 9. We had originally set up the internal Version Control to point to a particular project in our Team Forge. Now we have a new project that we need to point to and we cannot figure out how to change the location of where we are checking files into. We can see the path in the Version Control properties dialog box, but no way to edit the path. Any suggestions on how to switch from one project in Team Forge to another?
Thanks!

I am a dope! I meant Version 8!!!

New to JDeveloper/ADF, need to create a UI Mockup for a Version Control app

Hi,
I have experience with Java/J2EE, however I'm new to both JDeveloper and ADF and was hoping someone could point me in the right direction with what I'm trying to accomplish/start. We are working on a new application for a client and to kick start things I need to come up with a User Interface Mockup of a Version Control system we're going to create. It should be nothing fancy, and not very functional (for the time being) but should use some dummy data (preferably from a text file - just for demo purposes), be a one-page layout, and use Oracle ADF components (folder tree, datagrid, data view, xml view to be specific). Of course, it is requested that this all be done using JDeveloper/Oracle ADF. I was able to install both of these (it seems ADF is bundled with JDev), however that's about as far as I got. What steps do I need to take in order to come up with something simple like this? When I loaded up JDeveloper there are alot of options when creating a new project and I'm not sure what to choose. ANY help would be appreciated.

Thanks! This is exactly what I was looking for.
However, I'm having some trouble figuring out how to set up my Data Controls for the dummy data. I'd basically like to set up the entire page as follows:
A column on the left that displays a tree as follows:
Folder 1
     ...File 1
     ...File 2
     ...File 3
Folder 2
     ...File 1
     ...File 2
Folder 3
     ...File 1
     ...File 3
     ...File 4
     ...File 5
..etc
The right side of the screen will have 3 "columns" or borders that will take up the entire screen, from top to bottom:
List of Versions (large column)
Version Data (smallest column)
Version Text (large column)
List of Versions:
When the user selects a "File" from the tree, a datagrid will appear that displays all versions of the selected file with columns like "File Name", "Version", "Date", and a checkbox to select a row.
Version Data:
When the user selects a row using the checkbox, some relevant version info will display here. This info will come from the database when the final version of the app is written using various fields from the "Files" tables
Version Text:
When the user selects a row using the checkbox, some relevant version CODE (possible to display code neatly?) will display here. This info will come from the database when the final version of the app is written using a field from the Files table that has not been seen yet
How would I go about setting something like this up? Using the sample you provided earlier, the example just has main categories on the left. I'm confused how to set up a fell fledged tree and then to incorporate the functionality I described above.
ANY help would be appreciated.

Version Control

Similar Messages

Maybe you are looking for