Best practices of revision control

Similar Questions

• Best practices for controlling Remote Sites ESX servers

  Hi all

  I was wondering what the best practices or the options are for the management of the ESX servers in remote offices or branch.  I know that you can always use the VI to control on the site server, but what happens if you want to use some of the functions of the virtual Center?  How remotely manage and leverage capacity of Virutal Center in remote sites or branch offices, since you can't have Virutal Center installed in a domain.

  Other then a VPN dedicated to all remote offices or a branch is there another way to use Virtual Center to remotely manage the ESX servers in remote offices or branch?

  What are your current plans DR if the main site is going to host VC?

  You can run your VC in a VM and have power clone on a remote site or both incase of total failure.

  Then with the help of RCL etc. under the texiwill recommend and/or vMotion VM VC to other sites if necessary.

  Andy, VMware Certified Professional (VCP), http://www.vmadmin.co.uk/

  If you have found this information useful please give points by using the buttons at the top of the page accordingly.

• Request for advice: generally speaking, what is the best practice for managing a paid and a free application?

  Hi all

  I recently finished my first app of cascades, and now I want to inspire of having a more feature rich application that I can then sell for a reasonable price. However, my question is how to manage the code base for both applications. Any have any "best practices", I would like to know your opinion.

  You use a revision control system? This should be a prerequisite...

  How the different versions of the application will be?

  Generally if you have two versions that differ only in terms of having a handful of features disabled in the free version, you must use exactly the same code base. You could even just it for packaging (build command) was the only difference, for example by adding an environment variable in one of them that would be checked at startup to turn paid options.

• common components of jar, naming, best practices

  11.1.2.1 forms

  I added a few components of pot. For example, Directprint.jar

  As they have dependencies on other common components, you must download and add in the formsweb.cfg

  For example, Directprint must fontbox, pdfbox and commons-logging

  This components are alive, so change their versions.

  Well, now I have java in 1.6-1.8 guests, so I used it to upgrade some components of the jar.

  For example from pdfbox - 1.8.6.jar to pdfbox - 1.8.11.jar

  The question is: what is the best practice? The version of the name of band (rename just pdfbox.jar) so I don't have to change formsweb.cfg or preserve the name and line archive file formsweb.cfg?

  If you rename the file... you have to do before everything that manifests properties adding and signing a hassle?

  I guess it's a matter of taste and requirement. Personally I don't like the version numbers in the file names, because ultimately I don't like what version I am running a certain file... as long at it works. I certainly do not want to change the file name in each config file I do and do not remember to add it.

  However; If you want to be able to move forward and backward between the versions I guess it's easier to have a version number in the file name. If you encounter a no - Go in the current version just swap the file name in the configuration files. Of course, if you implement version control, you can update to revision until the problem is introduced, generating the .jar file from scratch and redeployed. If you don't have version control, you can only hope that you have a backup of your file.

  By simply adding a version number in the file name, you will need to update the formsweb.cfg whenever you add a new version of your jar file. By not doing this you will not have to do.

  Both have their advantages and disadvantages, you will have to decide for yourself what best suits your needs.

  If you rename the file... you have to do before everything that manifests properties adding and signing a hassle?

  Yes. The manifest must not care about the file name, but the process of signing only.

  see you soon

• Best practices Upgrade Path - Server 3 to 5?

  Hello

  I am trying a migration and upgrade of a server in the Profile Manager. I currently run an older mac mini Server 10.9.5 and Server 3 with a vast installation of Profile Manager. I recently successfully migrated the server itself out of the old mac mini on a Xserve end 2009 of cloning the drive. Still of double controls everything, but it seems that the transition between the mini and the Xserve was successful and everything works as it should (just with improved performance).

  My main question is now that I want to get this software-wise at day and pass to the Server 5 and 10.11. I see a lot of documentation (still officially Apple) best practices for the upgrade of the Server 3 to 4 and Yosemite, but can't find much on the Server 5 and El captain, a fortiori from 3 to 5. I understand that I'll probably have to buy.app even once and that's fine... but should I be this staging with 10.9 to 10.10 and Server 4... Make sure that all is well... and the jump off 10.11 and Server 5... Or is it 'safe' (or ok) to jump 3 to 5 Server (and 10.9.5 to 10.11.x)? Obviously, the AppStore is pleased to make the jump from 10.9 to 10.11, but once again, looking for best practices here.

  I will of course ensure that all backups are up-to-date and make another clone just before any which way that take... but I was wondering if someone has made the leap from 3-5... and had things (like the Profile Manager) still work correctly on the other side?

  Thanks for any info and/or management.

  In your post I keep the Mini running Server 3, El Capitan and Server 5 install the Xserve and walk through setting up Server 5 by hand. Things that need to be 'migrated' as Open directory must be handled by exporting the mini and reimport on Xserve.

  According to my experience, OS X Server facilities that were "migrated" always seem to end up with esoteric problems that are difficult to correct, and it's easier to adopt the procedure above that to lose one day try.

  YMMV

  C.

• Code/sequence TestStand sharing best practices?

  I am the architect for a project that uses TestStand, Switch Executive and LabVIEW code modules to control automated on a certain number of USE that we do.

  It's my first time using TestStand and I want to adopt the best practices of software allowing sharing between my other software engineers who each will be responsible to create scripts of TestStand for one of the DUT single a lot of code.  I've identified some 'functions' which will be common across all UUT like connecting two points on our switching matrix and then take a measure of tension with our EMS to check if it meets the limits.

  The gist of my question is which is the version of TestStand to a LabVIEW library for sequence calls?

  Right now what I did is to create these sequences Commons/generic settings and placed in their own sequence called "Functions.seq" common file as a pseduo library.   This "Common Functions.seq" file is never intended to be run as a script itself, rather the sequences inside are put in by another top-level sequence that is unique to one of our DUT.

  Is this a good practice or is there a better way to compartmentalize the calls of common sequence?

  It seems that you are doing it correctly.  I always remove MainSequence out there too, it will trigger an error if they try to run it with a model.  You can also access the properties of file sequence and disassociate from any model.

  I always equate a sequence on a vi and a sequence for a lvlib file.  In this case, a step is a node in the diagram and local variables are son.

  They just need to include this library of sequence files in their construction (and all of its dependencies).

  Hope this helps,

• Best practices on how to code to the document?

  Hello

  I tried to search the web tutorials or examples, but could not get to anything. Can anyone summarize some of their best practices in order to document the LabVIEW code? I want to talk about a quite elaborate program, built with a state machine approach. It has many of the Subvi. Because it is important, that other people can understand my code, I guess that the documentation is quite large, but NEITHER has yet a tutorial for it. Maybe a suggestion ?

  Thank you for your time! This forum has been a valuable Companion already!

  Giovanni

  PS: I'm using LabVIEW 8.5 btw

  Giovanni,

  Always:

  Fill in the "Documentation" in the properties of 'VI '.

  Add description to the controls of its properties

  Long lines label

  Label algorithm, giving descriptions

  Any code that can cause later confusion of the label.

  Use the name bundle when clusters

  Add a description tag in loops and cases. Describing the intention of the loop/case

  Follow the good style guide as will make reading easy and intuitive vi.

  I'm sure there are many others I can't think...

  I suggest you to buy "LabVIEW style book", if you follow what this book teaches you will produce good code that is easy to maintain.

  Kind regards

  Lucither

• encoding issue "best practices."

  I'm about to add several command objects to my plan, and the source code will increase accordingly. I would be interested in advice on good ways to break the code into multiple files.

  I thought I had a source file (and a header file) for each command object. Does this cause problems when editing and saving the file .uir? When I run the Code-> target... file command, it seems that it changes the file target for all objects, not only that I am currently working on.

  At least, I would like to have all my routines of recall in one file other than the file that contains the main(). Is it a good/bad idea / is not serious? Is there something special I need to know this?

  I guess what I'm asking, what, how much freedom should I when it comes to code in locations other than what the editor of .uir seems to impose? Before I go down, I want to assure you that I'm not going to open a can of worms here.

  Thank you.

  I'm not so comfortable coming to "best practices", maybe because I am partially a self-taught programmer.

  Nevertheless, some concepts are clear to me: you are not limited in any way in how divide you your code in separate files. Personally, I have the habit of grouping panels that are used for a consistent set of functions (e.g. all the panels for layout tests, all the panels for execution of / follow-up... testing) in a single file UIR and related reminders in a single source file, but is not a rigid rule.

  I have a few common callback functions that are in a separate source file, some of them very commonly used in all of my programs are included in my own instrument driver and installed controls in code or in the editor of the IUR.

  When you use the IUR Editor, you can use the Code > target file Set... feature in menu to set the source file where generated code will go. This option can be changed at any time while developing, so ideally, you could place a button on a Panel, set a routine reminder for him, set the target file and then generate the code for this control only (Ctrl + G or Code > Generate > menu control reminders function). Until you change the target file, all code generated will go to the original target file, but you can move it to another source after that time.

• Best practices using clusters to create the queue/notifier/bundles?

  I'm in a block diagram, a queue, the notifier and several instances of cluster of bundle

  that all use the same data structure.   There is a typedef of cluster for the data structure.

  Of course, each of these objects (define the queue, set notifier, bundle)

  you want to know how do you define the cluster.

  What is considered best practices?

  (1) create a dummy instance of the cluster across data structure

  definition is necessary (and hide all on the public Service)

  (2) create only one instance and son at all places, it is necessary

  But there is no stream on this thread: it's only the cluster * definition *.

  which is used, so this seems to clutter the comic.

  (3) create only one instance of the cluster control and use local variables

  everywhere else the definition of cluster is required.  It's _value_ is never

  assigned or given read-so no problem with race conditions.

  (4) another way?

  If you were to clean up someone else's code, how do you expect

  See this Treaty?

  It occurred to me during this writing that here where I

  "unbundle...... code bundle" I could wire the original beam to the

  the two "unbundle" and "bundle" - but that would be too complicated

  and the size of the comics with useless thread?

  Thank you and best regards,

  -- J.

  Hi Jeff,

  I think that this question is about "sharing" the typedef and not how share data (?)  If the cluster control is registered as a typedef (or a strict typedef) but NOT SIMPLY as a CONTROL, then when a Diagram-constant of the typedef is created, it will be updated when you update the .ctl typedef!  (and there is no FP control to hide )  Of course if the typdef is already available "close" if necessary, you will be able to use instead - save a spacer of diagram.

  See you soon.

• Best Practice Guide for stacked N3024 switches

  Is there a guide to BP for the configuration of the 2 N3024s stacked for the connections to the server, or is the same eql iscsi configuration guide.

  I'm trying to:

  1) reduce to a single point of failure for rack.

  (2) make good use of LACP for 2 and 4 nic server connections

  (3) use a 5224 with it's 1 lacp-> n3024s for devices of unique connection point (ie: internet router)

  TIA

  Jim...

  Barrett pointed out many of the common practices suggested for stacking. The best practice is to use a loop for stacking and distributing your LAG on multiple switches in the stack, are not specific to any brand or model of the switch. The steps described in the guides of the user or the white papers generally what is the recommended configuration.
  http://Dell.to/20sLnnc

  Many of the best practices scenarios will change of network-to-network based around what is currently plugged into the switch, and the independent networks needs / requirements of business. This has created a scenario where the default settings on a switch are pre-programmed for what is optimal for a fresh switch. Then recommended are described in detail in white papers for specific and not centralized scenarios in a single document of best practices that attempts to cover all scenarios.

  Express.ypH N-series switches are:
  -RSTP is enabled by default.
  -Green eee-mode is disabled by default.
  -Frother is enabled by default.
  -Storm control is disabled by default.

  Then these things can change based on the towed gear and needs/desires of the whole of society.

  For example, Equallogic has several guides that recommendations of configuration detail to different switches.
  http://Dell.to/1ICQhFX

  Then on the side server, you would like to look more like the OS/server role. For example a whitepaper VMware that has some network settings proposed when running VMware in an iSCSI environment.
  http://bit.LY/2ach2I7

  I suggest making a list of the technology/hardware/software, which is used on the network. Then use this list to acquire white papers for specific areas. Then use these white papers best practices in order to ensure the switch configuration is optimal for the task required by the network.

• Connecting two 6224 separate batteries best practices LAG?

  Hello

  I wonder how I should configure LAG between two powerconnect 6224 batteries (2 x powerconnect 6224 by battery) for iSCSI against 4 members EQL traffic, I intend to use the 4 ports of each stack (stack cross-possible LAG on 6224?) and equallogic documentation leaves me in two minds when it wants to run LACP or not?

  I wonder what reviewed best practices in this scenario?

  Cross-stack, LACP and no PLEASE or am I better of without LACP?

  Thanks in advance

  Cree

  The ports connecting the two piles together will be configured differently than the ports of connection of the battery to the EQL appliance. During the connection of the control unit switch EQL is when you might want to disable STP on that specific port.

  «Do not use of Spanning Tree (STP) on switch ports that connect to the terminal nodes (iSCSI initiators or storage array network interfaces).» However, if you want to use STP or Rapid STP (preferable to STP), you must enable port settings available on some switches that allow the port immediately transition to PLEASE State reference to link up. This feature can reduce network interruptions that occur when devices to restart, and should only be enabled on switch ports that connect the nodes. "

  With the network cards on the EQL devices according to me, there is only one active port, and the other is pending. So on the switch ports that are plug on the EQL will be in access mode for your iSCSI VLANS. Maybe someone more about EQL can chime to confirm.

  Here are some good white pages.

  www.dell.com/.../Dell_EqualLogic_%20iSCSI_Optimization_for_Dell_Power_onnect_%20Switches.pdf

  docs.danielkassner.com/.../ISCSI_optimization_EQL.pdf

  www.Dell.com/.../EQL-8024f-4-Switch.pdf

• Best practices for designing a view in PlayBook

  Hello world

  I'm new to BlackBerry PlayBook development and I would like to know how to make a user interface appropriate for playbook, what would be the best practice to do and it will be helpful to me if someone can post sample code here

  Thanks in advance

  A few tips:

  * Views extend Sprite

  * Views should be resizable, IE have a setSize() method

  * views should 'PIN' children at some edges of the screen, from when they are resized it runs correctly.

  * a parent class must listen to the scene for Event.RESIZE and call of resizing on the view.

  * Use the component of QNX, set if possible

  * Implement native controls, like sliding down to the options

• Best practices storage or advice

  I try to develop a Java of BB application, currently appearing on local storage. The app will be for public use.

  Someone has advice on when it is best to use the SD vs the persistent store? Is there a good best practices or document advice out there somewhere?

  This application will have two types of data: preferences and what would be the data files on a desktop system.

  I read on using the persistent store, and it seems to be a good option because of the level of control over the data for synchronization and such. But I noticed that some OSS BB applications use the SD card, not the persistent store.

  If I'm going to deploy the application to the general public, I know that I'm working with many configurations as well as with the limits set by the policy of the company (assuming that these users can even install the app). So any advice on navigating these issues regarding the storage would be greatly appreciated.

  Thank you!

  The persistent store is fine for most cases.

  If the transient data is very large, or must be copied to the device via the USB cable, then maybe the SD card should be considered.

  However, many / most of the people do not have an SD card.

• Is have RAID (1 + 0) so that Failgroups for all ASM ASM starts is a well-known best practice?

  Dear Experts,

  Is have RAID (1 + 0) so that Failgroups for all ASM ASM starts is a well-known best practice?

  Having both is the best practice

  • RAID (1 + 0)
  • ASM Failgroups for all ASM starts

  Thank you

  IVW

  You can create groups of ASM disks with normal or high redundancy or specify external redundancy. It depends on your reliability requirements and storage performance. Remember that ASM is not RAID and redundancy is the base file. ASM uses alternating devices. Oracle is generally recommended to have redundancy of storage. If you have RAID redundancy at the level of hardware controller or storage, Oracle recommends to configure ASM disks with external redundancy groups. Redundancy of the DSO is only between groups of disk failure and by default, each device's own failure group. Of course, you always want to make sure that you do not rely on redundancy of data between logical devices or partitions residing on a single physical unit. Compared to external RAID redundancy redundancy ASM using will give the DBA more control and transparency on the setting of the underlying.

• [ADF, JDev12.1.3] Best practices for maintaining a form validation

  Hallo,

  in my application, I need to create a registration form which contains fields that must be validated (for example they should follow a format like e-mail, phone number, tax code,...).

  If the data inserted by the user are ok, a new record in my custom db table Users will be created.

  I would like to know which are the best practices for maintaining the validation, which means the place where the controls must be made and a message to the user who fills out the form when something goes wrong.

  The best vo or EO or managed bean? Or some controls should be put in the OS, others in the VO and other in the managed bean?

  I would be happy if you could give me some examples.

  Thank you

  Federico

  Assuming you want the validation on the value of the field to any screen data can be entered in (and possibly web services that rely on the same BC ADF) then put the validation on the definition of the attribute in the EO.

  If you want to add a little more friendliness and eliminate some of the network traffic to the server, you can also implement the validation client in your page - for example by using the regular expression validator.

  https://blogs.Oracle.com/Shay/entry/regular_expression_validation