Versioning best practices.

Howdy, community.
Are there any best practices for version control of FIM configuration?
I'm curious if someone using something different from TFS.

On 21.05.2011 00:27, Emily wrote:
> I would like to use API comparison outside eclipse in a build
> environment. Is this possible? If so, what are the prereq jars and
> APIs I can use? Any help is very much appreciated.
> The task I wish to accomplish is to compare two jars under different
> versions and make sure the package versions comply with the OSGi
> versioning best practices. For example, the package major version has
> changed if there are API breaking changes.
Maybe one of the API Tools Ant tasks can do this. Take a look at the
'API Tools Ant Tasks' reference documentation in the 'Plug-in
Development Environment Guide'.
Dani
>
>
> Thanks in advance!
>
> Emily

Similar Messages

Reason for creating New Version Best practice

Hello SAP Gurus,
We know we are creating new version of the DIR when it is required to make a change in the original keeping in tact the Older file also for reference,
we want to know when a new version of the document is getting created how can we specify, why and what made us to create this new Version, we would like to capture this reason in SAP so the user can easily come to know why this Version is created,
can you please let us know, where actually are we capturing this details while creating the new version,
i know there are lot of free entry fields like Generic object Text field, Long text field, change the description, place the text in the WR log field of the new Version,
which is the best practice so that the user can easily come to know the reason why this new version has been created,
may be they should see this reason details in CV04N search as well, or immediately when opening the new version.
Thanks and regards
Kumar

Hello Kumar
Hope following explanation will clarify your questions
We have to classify our documents broadly in two category 1) Controlled document --means which under goes various level of / Inspection / review / approval etc with in Organisation e.g. Engg Drawing , Standard Operating Procedure for business purpose, best way for this is use Engineering Change Management (ECM)Functiuon and when you make any up versions, you can track / write key docu ment history in ECM
also when you do up version let say in Micosoft word , you can maintain simple table to track what is purpose of change, in what location you are making chnage and its justification.
For Engineering drawing of 2D /3D we can use Redlining functions to createt the Lawyers to know reviwers observation so that next version thopse are taken care
2) Uncontrolled Document---Generally they are less significant from document Change Control point of view
Hope this is useful
Regards
GIRISH

5.0 version best practices

Hi,
Any body can send me 5.0 version 'IC web' and 'Internet sales' best practices documents or link to down load..
Will reward points..
Regards,
Reddy.

Hi Venu,
I have send you IC Web on your mail ID [email protected]
And for the Internet sales you can find the download link from the following link.
CRM Internet Sales - Docuemts or Training Material
Thanks & Regards
Aashish Garg
aashish garg

Cellular Video versions, best practices

Any suggestions for transcoding a video to cellular specs? I have tried Compressor 4 and 4.1 and have not been able to meet the bit rate requirements for the cellular version. Also tried Quicktime 7

In compressor, you'll want to create a QuickTime Export Component by clicking the plus in the lower left to create a new setting.
In the window displayed, give it a name and make sure the format is "QuickTime Export Components"
choose the MPEG-4 in the Encoder-type drop-down menu and click the Configure button.
then fill out the appropriate settings for the encoding you want for Video:
for Audio:
and for Streaming:
You'll create a Cellular and Wifi setting for iPad and Cellular and Wifi setting for iPhone - 4 in total.
That should get you going. Please refer to the details provided by iAd for the exact settings for each of the panels above.
-Mark

Highly Required CRM 5.0 Best practices for CRM Service Module

Dear all,
I have been searching for CRM 5.0 version best practices in Internet quiete a long period, but could not find anywhere.
currently SAP is providing only best practices for SAP CRM 2007 version.
since most of configuration is differing because of Webclient Interface, I request you to refer a source from where I can get the CRM 5.0 Best Practices for Service module.
Your suggestions and help will be highly appreciated.
Best regards
Raghu ram

Hi Srini,
<removed by moderator>
Thank you & Best regards
Raghu ram
Edited by: Raghu Ram on Jul 16, 2009 6:09 AM
Edited by: Raghu Ram on Jul 16, 2009 6:11 AM
Moderator message please review the rules of engagement located here:
https://www.sdn.sap.com/irj/scn/wiki?path=/display/home/rulesofEngagement
Edited by: Stephen Johannes on Jul 16, 2009 8:12 AM

Best-practice on versioning a soa suite-application

Hi everyone,
I recently organised a seminar for customers concerning the Soa Suite Stack and one of the interesting questions asked that day was a versioning-question.
Let's say we've build a bpel/esb application interacting with different external and internal webservices and we've deployed this application to our production environment and we need to change an internal web service.
How can we add versioning to this heterogenous system in a consistent way? I know you can tell esb which version of the bpel process it needs to use, but what about the custom and external webservices that we've integrated with?
My 2 cents: You need to add a versioning-tag to you custom web services that you need to manage yourself, and use this versioning tag in the services your integrating with.
Could somebody point me out what best practice is, or what Oracle's development team is working out regarding versioning systems for SOA-applications?

Marc,
Are you saying versioning isn't supported in ESB now? I thought that ESB already uses the versioning tag from bpel when you're integrating bpel and esb?
During the development of my demo I've seen that the version-tag was used when invoking the bpel process through a soa service.

Best practice for migrating between environments and versions?

Hi to all,
we've got a full suite of solutions custom developed in SAP BPC 7.0, SP 7. We'd like to understand if
- there are best practice in order to copy this applications from an environment to another environment (another client)
- there are best practice in case the client has got a newer version of SAP BPC (they should install the 7.5, while we're still stucked with the 7.0).
Thank you very much
Daniele

Hi Daniele
I am not entirely sure, what you are asking, Please could you provide additional information.
Are you looking for best practice recommendations for Governance, for example: Change transports between DEV, QA and PRD in BPC 7.0?
What is the best method? Server Manager backup and restore, etc ?
And
Best Practice recommendations on how to upgrade to a different version of BPC, for example: Upgrading from BPC 7.0 to 7.5 or 10.0 ?
Kind Regards
Daniel

Delivering demo or trial versions of a product - best practice?

Hello there RoboHelp gang,
I am using RH8 HTML to create a knowledge product for commercial resale to clients and customers. One of the things I need to do is offer a 'trial' version of the end the end product. I imagine doing this by creating an instance of the knowledge product with selected areas freely available but with the bulk of the content 'locked down'.
I understand from the instructions that i can do this via condition conditional text function... the reason for posting to find out if anyone had any additional best practice comments, suggestions or tips on setting up and managing a demo or trial version of applications built in Robohelp 8 HTML? The end format of mine will be ADOBE AIR.
fyi - i've tried searching online and in these forums for more on this but can't find anything (... and that maybe because i've over-complicating it?!:)) but i'll happily post my findings (if any) once it's all set up to satisfaction.
Thanks,
DK
RH8 newbie from the UK

KeepItSimpleStupid!
That is, make it as functional as possible, but don't raise expectations needlessly with a lot of fancy foldarol; there'll be plenty of time to add cute stuff, and only as user feedback warrants. Yes, there are wonderful things you can add, but just because you can, doesn't mean you should.
Note also that the topics you have retained (not conditionalized away) must not contain links to the ones that are missing (you can try explaining away such broken links, but they'll leave a bad taste nonetheless). In addition, their Index entries will be missing, and the topics will not be included in a Search.
Good luck,
Leon

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

Best Practice for New Doc Version?

I'm a RH novice who needs to create a V1.1 doc based on the
V1.0 source topics, TOC, and images. I'm using RH HTML X5. What is
my best practice? The previous author left a unclear doc suggesting
something like the following:
Copy the current V1.xpj, V1.hhc, and V1.hhp files and rename
them as V1.1.xpj, V1.1.hhc, and V1.1hhp
Place the renamed files in the V1 root directory and open the
V1.1.xpj file.
Create and edit new content
Not understanding RH too well, this seemed reasonable. It
appears what he is suggesting will bring everything forward in a
new project, but leave the V1 structure intact. I tried this, and
it seemed to be working but I was confused by RH also making
changes to the OLD V1.cpd and V1.pss (I don't know that those files
are).
So, apparently the copied files contain references to at
least the old cpd and pss files (and maybe others). I'm concerned
that continuing down this path will corrupt V1 and leave me
mis-matched conventions. Some files being V1, and some being V1.1.
Is there a how-to somewhere that can help me create a new
version and not muddy up the old? Do any X5 gurus remember how they
did this?
Thanks in advance,
Keith

Peter,
Hopefully you'll see this. I tried you suggestion. Opened the
old file and renamed the project. About 10 links came up broken
that weren't broken before. Any ideas why this would happen. I
didn't make any changes other than the rename.
Thanks,
Keith

What is the best practice to manage versions in XI?

Hi!
Is there any <b>good</b> best practice ways to manage versions in XI.
Have a challenging scenario with many legacy systems and many interfaces per legacy system.
Should I put all the different interfaces for one legacy system under one namespace in the Integration Repository or should I make one own namespace for each interface.
Or is there other approaches, that I should consider to get a environment that is easily maintained.
br.samuli

Hi,
In our project we have defined our own naming conventions/namespaces.
For instance, we have agreed that we will group all interfaces (from all offices worldwide and different projects) into one single product version.
This global custom product will in turn be divided into different SWC (Software Components) and SWCV (Software Component versions).
So for each business scenario we will create separate SWC's and when necessary create new versions of these SWC's.
This means that each SWC should contain all the required objects to support a complete integration scenario i.e. inbound/outbound-interfaces, data types, msg types, business scenario's etc...
Regards,
Rob.

Best practice versioning XI szenario with java proxies

Our XI scenario includes services with java proxies.
By changing the message structure, java proxies have to be changed, too. But not all connected application can migrate to new message structure at the same time.
I need a solution to run different versions of the same scenario at same time. This is also a requirement to my java proxy service. Thus I need to run the java proxy service under different versions.
To maintain minor and major changes, what would be the best practice for versioning in XI scenarios and for java proxies?
Is there a better solution than use different namespaces inside the XI scenarios (e.g. add the version number) and use different EJB-names for the proxy services (e.g. include the version number in the name)?
Thanx,
Michael

Hi Michael,
I don't have a best practice for you, but...
In general, you tend to run into trouble when making incompatible changes to message structures. Since the Software Component Version is not used as part of the message key (only interface and namespace is used), you can't use this versioning mechanism to help you. Thus you are forced to create a new interface instead of a new version of the same interface. If you can think up a new name (that won't just cause confusion), fine. Otherwise you are forced to include an version identifier in either the interface name or the namespace. The latter is used in some public XML schema definitions e.g. xCBL. In other words: versioning via namespaces. Not exactly elegant, but perhaps your best bet.
Best regards,
Thorsten

Best practice when upstream does not provide version number

I'm currently preparing a package for the game Dreamfall Chapters, unfortunately the Developer does not (yet) provide a Version number.
What is the best practice for this? Just count the releases and set epoch when they finally provide one themselves?
thanks in advance!

If you are missing a version number, you could use the date. Prefix it with "r" in case you want to avoid epoch when upstream decides to start versioning.
pkgver=r20140122
If you have another release on the same day, increment another subversion
pkgver=r20140122.1
Counting the releases by hand is poor practice (you could miss one). Do it only if upstream provides the count.
Edit: To tie the version stronger to the release, you can also add a part of the archive hash, e.g. +m###### with the first 6 characters of the md5sum.
pkgver=r20140122+m23df1e
Edit: r as prefix is better, thanks rumpelsepp.
Last edited by progandy (2014-10-22 09:32:56)

Best Practice: SAPGUI Version and Patch Upgrades

Hello -
Does anyone have some thoughts/information on best practices relating to SAPGUI version and patch upgrades.
Obviously, sometimes upgrades are forced upon us (e.g. 7.10 for Vista) and in other cases it may just be considered "nice to have".
Either way - it always signifies regression test and deployment effort. How do we balance the benefit and cost?
Thanks, Steve

Hi Steve,
you're right for the first part, yes, we (usually) patch twice a year.
Now for the rest
An uninstall will only happen on release changes (6.20->6.40->7.10), i. e. about every 4-5 years as SAP releases them.
Patches are applied to the installation server and the setup on the client will only update changed program parts. For example, upgrading 6.40->7.10 took about 10 minutes (incl. uninstall), applying patch 1 less than 5 minutes.
I recommend, you read the "SAP Frontend Installation Guide - 7.10" which you find at SMP alias sapgui. Navigate to Media Library - Literature. It explains setup of the installation server (sounds like a big thing, but ain't much more than creating a share), creating packages, applying updates etc.
Peter
Points always appreciated

Versioning best practices.

Similar Messages

Maybe you are looking for