Best practices for file architecture? I mainly have photos and music to organize.

I am moving my files from an old macbook pro to a newer one.
I want to make sure that I am more organized with this new computer than I was in the past.
Does anyone have suggestions re., how best to set up the file architecture?
Thanks!

Similar Messages

What are best practices for managing my iphone from both work and home computers?

What are best practices for managing my iphone from both work and home computers?

Sync iPod/iPad/iPhone with two computers
Although it isn't possible to sync an Apple device with two different libraries it is possible to sync with the same logical library from multiple computers. Each library has an internal ID and when iTunes connects to your iPod/iPad/iPhone it compares the local ID with the one the device normally syncs with. If they are the same you can go ahead and sync...
I have my library cloned to a small 1Tb USB drive which I can take between home & work. At either location I use SyncToy 2.1 to update the local copy with the external drive. Mac users should be able to find similar tools. I can open either of the local libraries or the one on the external drive and update the media content of my iPhone. The slight exception is Photos which normally connects to a specific folder on a specific machine, although that can easily be remapped to the current library if you create a "Photos" folder inside the iTunes Media folder so that syncing the iTunes folders keeps this up to date as well. I periodically sweep my library for new files & orphans withiTunes Folder Watch just in case I make changes at one location but then overwrite the library with a newer copy from the other. Again Mac users should be able to find similar tools.
As long as your media is organised within an iTunes Music or Tunes Media folder, in turn held inside the main iTunes folder that has your library files (whether or not you let iTunes keep the media folder organised) each library can access items at the same relative path from the library folder so the library can be at different drives/paths on different machines. This solution ensures I always have adequate backups of my library and I can update my devices whenever I can connect to the same build of iTunes.
When working with an iPhone earlier builds of iTunes would remove any file not physically present in the local library, even if there was an entry for it, making manual management practically redundant on the iPhone. This behaviour has been changed but it will still only permit manual management with a library that has the correct internal ID. If you don't want to sync your library between machines on a regular basis just copy the iTunes Library.itl file from the current "home" machine to any other you want to use, then clean out the library entires and import the local content you have on that box.
tt2

Best Practice for Use of ABAP in Customizing SRM and/or CRM

I was wondering if there is a document that defines best practices for the use of ABAP with the installation and customization of SRM and/or CRM. Such as amount of ABAP coding typically required, and best practices around the use of ABAP for customization and configuration.
Thanks.

Hi, Johnson
Sorry, Please don't mind, you are not at right place to ask the Question like this
Please read "The Forum Rules of Engagement" before posting! HOT NEWS!!
Thanks and Regards,
Faisal

Best Practices for File Organization/Project Explorer

So we are finally getting SCC at my organization to manage our LabVIEW development, and that is good!
Now, we are starting in on discussions about how we should organize our files on disk and how we should use the Project Explorer. When I started here about 3 years ago, I wasn't very familiar with the project explorer, so I read the article at http://zone.ni.com/devzone/cda/tut/p/id/7197. Two of the main things I took away from that article are:
1. Organize Files in a logical manner on disk. Whatever that is, it is not a flat file structure.
2. The top level VI should be separate from other source code. Preferably, it should reside in the application folder.
Push Back Against These Recommendations
Before I was hired, most, if not all LabVIEW development was done utilizing a flat file structure and the top level VI lived with the source code. Since we didn't have a proper SCC, each individual organized files as he saw fit. So I started using the Project Explorer (not even its use is totally accepted right now) and I began follow recommendations 1 and 2 above. I didn't always follow #1 very strictly, but I have been working towards it, and I have always followed #2 religiously.
Since we are starting these discussions on how we should organize files on disk I'm starting to get some push back to following these two recommendations.
The arguments I get in favor of using a flat file structure is that you always know where every file is; including the top-level VI. It is also argued that it is a lot of effort to organize and search for VIs when they all reside in different folders. I think the fear is that by getting "clever" and organizing our files in such a manner we'll make things complicated and we will somehow shoot ourselves in the foot.
The argument I get against separating the top level VI from the rest of the source code is that it:
(a) Won't be clear where it is (like it is buried within hundreds of VIs). However, it is argued, you can just put a "!" in front of the file name and then it is always the at top of the flat file structure.
(b) An extension of argument of (a) is that things either look or seem messy when VIs (including top level VI) don't live in a sub-folder and are just hanging out with the Project Explorer file.
(c) I think there may be some fear of breaking the VI by moving it and altering the dependencies for the VI.
Convincing Others its Good to Follow These Recommendations
So, if I want to follow NI's recommendations, I need to come up with reasons we should follow these recommendations. Also, I should state that I care about following these recommendations because its what NI recommends. They've been around the block a few times and I'm sure there are good reasons why these are best practices. However, I don't think I've given a very compelling case for why these recommendations should be followed.
So I'll tell you all what I think good reasons are for these recommendations and perhaps I can get some feedback or additional support? If I'm crazy for wanting to follow these recommendations maybe someone can point out why I'm crazy.
(a) Arguments for Following Both
I. I passed the CLAD a couple of weeks ago, and I have started studying for the CLD. Part of the CLD is following both of these recommendations (see page 6 of http://ftp.ni.com/evaluation/certification/cld/cld_exam_prep_guide_english.pdf). While this isn't a reason in and of itself, it suggests that if it important when being certified it is important in practice!
II. If we hire new developers that are familiar with LabVIEW, they will most likely be familiar with these recommendations, especially if they are certified. That will lead to increased productivity out of the door because they won't have to learn our special way of doing things.
(b) Arguments for Organized File Structure
I. Unused VIs are easier to identify and remove. Right now we never remove VIs because we don't know if they are used or not. This leads to a lot of VI bloat.
II. It is hard to know what a specific VIs function is in a flat file structure by looking at the name.
(c) Arguments for Separating Top Level VI from Source Code
I. Placing the top level VI is an intuitive place for this VI. As long as the top level VI is the only VI in the application folder there is no mistake it is the top level VI, especially once you open it. This makes it easy for new developers to find the top level VI. I'd argue it isn't very intuitive for new developers to know that a VI in the source code folder that is prefaced with a "!" is the top level VI.
Summary
So that is what I think so far. Is there anything else I am missing to support following those two recommendations or am I just being inflexible?
Thanks!

zenthoef,
As a CLA, I have struggled with file structure over the years. Here are my recommendations:
1. Put the top level VI and the project in the top-level folder. This makes it very clear where to begin.
2. Put the remaining user interface VIs in a separate folder. Again, it makes it very clear what the functionality of these VIs are.
3. If you are using object, put each object in a separate folder. Place the family of objects in one folder, with each object in a subfolder.
4. Keep the remaining VIs either in a single folder. This can contain a small number of subfolder if your project is large, but too many folders makes it hard to figure out where your VIs are. For example, you might have a DAQ subfolder, an Analysis subfolder, and a Report subfolder. But if you had a Test1 folder, a Test2 folder, and you had a VI that was used by both tests, where would it go? Keep it simple.
5. You inferred that it is hard to figure out what a VI does by its name. That implies that 1) you need better names, and 2) your VIs are too complicated. A VI should do a single function which can be adequately described by its name. That VI might be something like Analyze Data.vi, which would contain a bunch more subVIs (like Get 1st Harmonics.vi), but each VI would contain a single function. You wouldn't save the data to a report in the Analyze Data.vi, for example.
The most compelling reason for following these suggestions is that it is easier to figure out what the code is doing after you haven't looked at it for a while. Once you have an application that is working and bug free, you shouldn't have to touch the code until you want to add features. If that is even 6 months later, you will probably have forgotten how the code works. As a consultant, I have had to update other people's code, and just figuring how where to start can be a challenge.
Tom Brass
Certified LabVIEW Architect
Saint Bernard Engineering, Inc.
www.saintbernardengineering.com
Tom Brass
Certified LabVIEW Architect
Saint Bernard Engineering, Inc.
www.saintbernardengineering.com

Best practices for file I/O within producer/consumer loops

I'm looking to add file recording and playback functionality to a pre-existing data collection program. The original progam is based on a Moore-style state machine, which I have added four additional states to. They are: Record Start, Record Stop, Playback Start, and Playback Stop.
What I have done, and what has since been identified as poor programming practice, was to "initialize" (either create or load) the appropriate file within the state machine loop during the "Start" command (for record or playback functionality), and then provide the file reference as an indicator, which is linked to for the appropriate read or write operation(whether I'm playing back or recording). The actual I/O occurs within the the Consumer Loop. (screenshots attached).
This is my first labview project outside of tutorials or other small examples, so any advise and constructive criticisims are welcomed. Specifically with regards to file IO and refnum routing (it gets a little hairy in the consumer loop)!
I'm running Labview 8.6 on Vista business.
Attachments:
Playback Start.JPG ‏71 KB
Consumer_Loop.JPG ‏122 KB
File Playback subvi.JPG ‏14 KB

jamoore84 wrote:
Ben,
Thanks for the suggestion. I think it's a little outside my ken at this moment, but I'll look it over. Despite any grevious coding transgressions, I have experienced some limited success with the current setup. While the use of Action Engines/Functional Globals may constitute the best practice, I might revise my post to read "acceptable and/or easily absorbable practices" instead.
Are there any other opinions on this? Let me start by listing a problem and posing a question:
Problem: I am able to playback a file only once. Subsequent attempts at file playback do not work.
Thanks in advance,
jimmy
HI Jimmy,
I don't give up easy.
Let me try to exaplain the issue with race conditons with a contrived example, the
"Command by Mail box" case.
Imagine you had a job where you recieved your orders via an old fashioned mail box. You never really saw your supervisor but relied on getting orders via the mail box. Now imagine the mail box could only hold one message and any time a new message was inserted, the old one would fall into the trash.
So you come to work each day check your mail box do what was ordered and everyone is happy.
The next day you come in and without your knowing, you are assigned to do the work of two bosses. So as long as you check your mail box more often than the two of them assigne work everything is fine... until you take a day of vacation! So you come back in the day after vacation and check you mail box and work a way until you catch hell for ignoring orders !?! Wel it turn out the order from boss 1 was replaced by the order from boss 2 while you were on vacation. Oh bother!
How can we fix it?
1) Expand the mail box so it hold more than one order. You just process them in the oder they are recieved.
2) Change to mail box to not accept a new order until you have removed the old.
Now back to reality!
Local variables act like the funky mail box. The last message insterted over-rides the previous.
Multiple variable writer ar like multiple bosses.
Queues operate like an expanded mail box, letting you handle each message in order.
Action Engines operate like the "mutexed" mail box.
Why I don't want to encorage you to "just patch up" what you have.
All of the less than ideal solutions either over-sample (Check e-mail twice as often as bosses assign work, waste CPU, an exercise in futility if you are coding in a non-Real-Time envirionment like Windows) or use a mutex to control access to the shared resource ( in this case local varialbes).
LV offers mutexes through semaphores (found on the syncronization pallete) but...
WHY WORK SO HARD?
In my AE Nugget I explain that the exection of an AE is automatically protected by LV. So in the long run it will actually be easier to learn how to use the AE programming construct than it will be to learn how to solve the problem without them.
so GO FOR IT! Take the lazy route and learn how to use the AE construct. Use the Syncronization pallete for Queues.
Just trying to help,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Best practices for JavaFX architecture and patterns?

Hi,
I want to write reusable, easy to maintain JavaFX code for a larger UI project and wonder what are the best practices doing so.
1) Are there preferred UI patterns? MVC, MVP, Presentation Model, ...?
2) Does it make sense to use FXML to separate View from Logic? Or should I use 2-3 Java classes instead (one for View, one for Logic, one for Domain Model, depending on the pattern)
3) How to organize all the views? Should I use Dependency Injection? Or Singletons for each view? Spring or Guice framework, if at all?
Currently I use singletons for most views, so that I can use them from anywhere in my application. If a window is closed and opened again, I use the same instance for that, which still resists in memory.
For patterns, I try to lean on Presentation Model, since this is what I know from Flex development: Having a View layer, which contains all the UI stuff and an abstract view layer, which holds properties, that describe the View, e.g. submitButtonDisabledProperty. The View knows the abstract layer (Presentation Model), but not vice versa and the UI elements are bound to its properties.
I am unsure if this is appropriate for JavaFX, too (for Flex or Silverlight it is).
What are your recommendations / experiences for large UI projects?

You are correct that in 'pure' MVP the View should know as little about it's presenter implementation as possible. The view should just notify one or more 'listeners' that something has happened.
You can use event listeners for this, but I would highly recommend not exposing your Control-specific GUI events and instead create your own. So for example, don't expose ActionEvent or MouseEvent as these expose too much detail about your View's implementation, instead create 'semantic' events, so you might have something like 'sayHelloRequested' or 'printOptionSelected' (whatever naming system you want). This hides how the option is implemented, so you might have a 'print' button, a 'print' menu option, a CTRL+P print shortcut, or a double tap anywhere on your screen to print. The listener knows only that the view thinks 'print was requested by the user' - decoupling achieved.
Once you start doing this however you end up with an explosion of event listener interfaces. So say a view has 10 callbacks it wants to notify about, then you end up with 10 interfaces, and if you're being really pure you also end up with 10 'Event' beans (or DTOs) to encapsulate the details of that event. It starts to get ungainly even for a semi-purist like me. So the logical progression from there is usually just to define all 10 callbacks in one interface and call it something like MyViewListener.
There are two common ways to implement listeners, the traditional way is to allow an arbitrary number of listeners to be added. Whereas another option is to allow only a single listener to be added. In JFX you will notice that Button for example has a setOnAction() method not a addOnAction() method - it allows a single event handler only and let's face it this is generally fine in 95% of cases. For the remaining 5% you can just write your own aggregate event handler that dispatches the event to multiple listeners.
So if we go down the road of single event listeners, using an interface for all of the callbacks and not bothering with full 'Event' objects, you end up with something like this:
public interface MyViewListener {
    void printRequested();
    void doSomething(int someParam);
    void doSomethingElse(String someOtherParam);
}And if you look closely at the 'Purist' option in my MVP pattern where I define interfaces for everything, then you will see that this is pretty much the exact interface I've created for the 'Presenter'. You could just as easily rename this interface to MyViewListener in this pattern and have the same outcome.
So to wrap all that up, yes, the Presenter should be decoupled and I highly favour the 'purist' option in my blog and would definitely use it if FXML didn't dictate a impure design pattern (there are some ongoing discussions about this on the OpenJFX discussion group). And, yes, my 'purist' option could be even more pure if you went for the full-blown event callback model and if you go down that road you will have an extremely clean architecture but also an extremely large code-base - totally your call whether it's worth it.
It's also worth remembering in all this, that there are a lot of people from a lot of different backgrounds using JFX and some people hate (passionately) even my semi-pure option - especially those coming from other, less heavy-weight languages. They just don't get why you wouldn't build it all into one class and reduce the overheads. So what you have in my blog is my thoughts on it, other people will most definitely differ. I'm a big fan of developer's choice, and that's why I did the smorgasboard approach even though I personally would never use some of those implementations.
Also this video on GWT is an awesome reference on GUI design patterns: http://www.youtube.com/watch?v=PDuhR18-EdM
JFX Flow draws a lot from GWT as I think it is a very clean architecture (just such a shame that they put all that effort into hiding the horrid, sordid mess that is the web+html+css, instead of making something proper, like JFX).
Hope that helps,
zonski

Best Practice for attaching Meta Data, Organizing & Archiving Photos

I am about to start the daunting task of organizing and archiving ALL of my photos so that I can access them from an external hard drive (or two) when I need them. I want to know/understand the best way to do this before I start so that thousands of hours later I don't realize that I have not considered something critical. I have already spent hours trying to find this information online to no satisfactory avail. I have both iPhoto ('09 v8.1.2) and Aperture 3, which I am just learning to use. I am wanting to back up to my WD My Book. I have already transferred some pictures and realized that, though I had them nicely organized in Albums in iPhoto, that information doesn't transfer over to the My Book so the file names are unrecognizable as any type of descriptor. I believe that I need to assign some Meta Data (?) to each photo so that I can do searches to find particular people or subjects when needed.
Here are all of the things I want/need to know:
1. Which Mac program would be best to accomplish attaching MetaData or adjusting file names: iPhoto or Aperture 3?
2. What is the best way to attach MetaData to pictures so that the information is permanent? Tagging (allowing multiple search options)? Batch Name Change (allowing limited search capabilities)? Other?
a. If I TAG all of my photos and then try to use that information outside of iPhoto or Aperture 3 (from the external HD) will it still be accessible for searches?
3. After attaching all of this information, what do I need to know about transferring the photos to an external HD? Are there multiple copies of the same photo (original, edited) and if so, are both transferred? Are they both deleted when I move the pictures to the trash?
4. Is there anything else that I need to know??
Your expertise would be greatly appreciated.
Thank you.

You are trying to defeat the photo management of iPhoto - My suggestion is to learn iPhoto and use it of choose another program - iPhoto does not work well unless it manages the entire library and you access it using the tools build into the OS - click here for a discussion on the many correct and safe ways to access your iPhoto library photos.
Aperture may or may not be a better choice - try the Aperture forum for detailed info
Backing up iPhoto is trivial - simply drag the iPhoto library intact as a single entity to another hard drive - or use an incremental backup program to do it as changes are made - I use Time Machine to one backup drive and SuperDuper to another
I believe that I need to assign some Meta Data (?) to each photo so that I can do searches to find particular people or subjects when needed.
This is an integral part of iPhoto and one of its strengths
1. Which Mac program would be best to accomplish attaching MetaData or adjusting file names: iPhoto or Aperture 3?
iPhoto does a great job of this - file names are only adjusted when you export - and there is no need for them to be adjusted within the iPhoto library since you never should be going into it directly and never need to see the files directly
2. What is the best way to attach MetaData to pictures so that the information is permanent?
Exporting from iPhoto
Tagging (allowing multiple search options)?
Using iPhoto and the OS tools
Batch Name Change (allowing limited search capabilities)?
Done during export if desired
Other?
Depends
a. If I TAG all of my photos and then try to use that information outside of iPhoto or Aperture 3 (from the external HD) will it still be accessible for searches?
In iPhoto yes so long as you are not going directly into the iPhoto library but are using the provided tools
3. After attaching all of this information, what do I need to know about transferring the photos to an external HD?
Simply drag the iPhoto library intact as a single entity to the EHD - the database is a single entity and it will be the same there (so long as the EHD is formatted Mac OS extended (journaled)
Are there multiple copies of the same photo (original, edited) and if so, are both transferred?
Yes - Yes
Are they both deleted when I move the pictures to the trash?
You do not move photos to the trash - you select them in iPhoto and press the delete key then empty the iPhoto trash (iPhoto menu ==> empty iPhoto trash)
4. Is there anything else that I need to know??
Lots - if you are going to use iPhoto stop thinking of managing files and start thinking of using a SQL database which is what iPhoto is -- otherwise you need to use a different program
LN

Best Practices for File Management

I just wrote post about how I use Lightroom, Dropbox, and Crashplan to manage my photos. I'm curious if anyone here has a critique for my approach. I'm not a "pro" by any measure, so I'm not sure if this is a good approach, or if there are better ways to accomplish the same thing. In general, I just want a highly reliable, low pain workflow for keep track of my files. Thanks for any feedback you have!

Looks good - I run an almost identical system for my personal photos, using the same programs.

Using Liquid, what is the best practice for handling pagination when you have more than 500 items?

Right now I can only get the first 500 items of my webapp, and don't know how to show the rest of the items.
IN MY PAGE:
{module_webapps id="16734" filter="all" template="/Layouts/WebApps/Applications/dashboard-list-a.tpl" render="collection"}
IN MY TEMPLATE LAYOUT:
{% for item in items %}
<tr>
<td class="name"><a href="{{item.url}}">{{item.name}}</a></td>
<td class="status">Application {{item.['application status']}}</td>
</tr>
{%endfor%}

<a href="{{webApp.pagination.previousPageUrl}}">Previous Page</a>
Current Page: {{webApp.pagination.currentPage}}
<a href="{{webApp.pagination.nextPageUrl}}">Next Page</a>

Best practices for organizing a sudden batch of photos?

So, I just got ahold of hundreds (1000+) of slides from my early childhood, years 0-10. Pictures I had never seen before. (Plus 8mm and 16mm movies, reel to reel audio, and some prints.)
I'm going to get a slide scanner and scan some, but not all, of the photos in (I don't care about the vista shots). Have any of you done such an all-at-once type of project? What approach did you use to describe the photos?
How do you ID the people? Make keywords for people, or put names in the comments?
How do you deal with group photos? It would be nice if the names could attached to the faces, so a mouseover revealed the name.
Did you make a note somehwere (e.g., comments) of what box the images came from, when they were developed (since the photo date may not be known), which image no. in the series it was? (So you can find the original again if necessary.)
Do you have any tips to keep this under control?
I'm both excited by this and overwhelmed. I'd rather do it once and do it right. This is part of a bigger project to piece together this period of my life, so the more info I can track, the better.

switchbacker:
You might consider one of the new flatbed scanners that have the capability of scanning multiple sides at one time. My reasoning for this is that after you're finished with the project you'll end up with a useable piece of equipment instead of a nice doorstop if you get a dedicated slide scanner. That's what I have, a nice doorstop.
I recently got a Canon 8600F scanner that will do 4 slides at a time and put each in their own file after the scan is completed. I'm sure other scanner manufacturers have similar software that will separate multiple images in one scan into their own file. My standalone slide scanner was over 5 times as slow as the Canon scanner on a time per slide basis.
A bonus with the particular Canon scanner that I got was that Photoshop Elements 4 was bundled with it.
As far as organizing the resulting image files I use keywords to identify the elements within a photo, i.e people, places and things. I name the files, before importing into iPhoto, with the date of the photo using the international date format YYYY-MM-DD-001.jpg, -002, jpg, etc. This gives me excellent chronological sorting and searching capability. There are 3rd party applications like R-Name that will batch rename sequentially a folder of photos. Doing this before importing will assure that the original file will be names as you want it instead of something link Scan -01.jpg.
I did the same thing you did, scan about 5000 slides and 5000 photos to document the family history. I created iDVD slideshows for each year breaking the slideshows down by month. My brother had our parents 8 mm movies digitized and I digitized 100 hours of family VHS videos to add to the DVDs also. After burning the iDVD project to disk I would also burn the source files via the Finder to DVD disks and distributed a copy to each of our kids. That gave me multiple backups and gave them a way to preview the family history. My project spans 100+ years from 1906 to 2006 (yes, I'm a couple of years behind because with digital cameras in each of the kid's hands I have so many more photos per year to work with ). The recent years are taking 2-3 DVDs to cover each year. With iDVD it makes it so easy to create a really professional looking DVD. Here are screenshots of an early DVD of VHS videos and a later DVD of slideshows.
You will have fun!
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.
Don't despair, it's doable.

Best practice for Javadoc comments in both an interface and implementation

For the Spring project I'm writing, I have interfaces with typically 1 implementation class associated with it. This is for various good reasons. So I'm trying to be very thorough with my Javadoc comments, but I realize I'm basically copying them over from interface to implementation class. Shouldn't Javadoc have a setting or be smart enough to grab the comments from my interface if the implementation class doesn't have a comment? Unless of course there is interesting information about the implementation, it's rare the 2 sets of comments would be different.

Thanks Thomas!! Exactly what I was looking for. Here's the JavaSE 6 version of the page you provided:
http://java.sun.com/javase/6/docs/technotes/tools/windows/javadoc.html#inheritingcomments

I want to know name for an app. to copy movies,photos and music from computer to the ipad

v

when i have tried to copyy the files it said some of the items in the itunes library. including photo number 11 were not copy to the ipad because they could not be found !!!! what to do now??

Best Practices for E-Commerce

Hi Experts,
I was wondering if anybody has experience in installing and configuring SAP Best Practices for E-Commerce. I have downloaded and installed the ADD-ONs but when trying to configure IPC and webshop via XCM http://<server>:<port>/isauseradm/admin/xcm/init.do I am getting a 404 error "URL or resource not found".
Who knows what component I am missing and can put me in the right direction!
Thanks in advance!
Wolfgang

I am not sure I understand your question.
If you are using E-Commerce with CRM2007 (CRM6), not ERP, then use the [Best Practices Building Blocks|http://help.sap.com/bp%5Fcrmv12007/CRM%5FDE/html/] -> Technical Information -> Building Block Library
However, there STILL is not a BP for E-Commerce with CRM though.

Best practices for dealing with Exceptions on storage members

We recently encountered an issue where one of our DistributedCaches was terminating itself and restarting due to an RuntimeException being thrown from our code (see below). As usual, the issue was in our own code and we have updated it to not throw a RuntimeException under any circumstances.
I would like to know if there are any best practices for Exception handling, other than catching Exceptions and logging them. Should we always trap Exceptions and ensure that they do not bubble back up to code that is running from the Coherence jar? Is there a way to configure Coherence so that our DistributedCaches do not terminate even when custom Filters and such throw RuntimeExceptions?
thanks, Aidan
Exception below:
2010-02-09 12:40:39.222/88477.977 Oracle Coherence GE 3.4.2/411 <Error> (thread=DistributedCache:StyleCache, member=48): An exception (java.lang.RuntimeException) occurred reading Message AggregateFilterRequest Type=31 for Service=DistributedCache{Name=StyleCache, State=(SERVICE_STARTED), LocalStorage=enabled, PartitionCount=1021, BackupCount=1, AssignedPartitions=201, BackupPartitions=204}
2010-02-09 12:40:39.222/88477.977 Oracle Coherence GE 3.4.2/411 <Error> (thread=DistributedCache:StyleCache, member=48): Terminating DistributedCache due to unhandled exception: java.lang.RuntimeException

Bob - Here is the full stacktrace:
2010-02-09 13:04:22.653/90182.274 Oracle Coherence GE 3.4.2/411 <Error> (thread=DistributedCache:StyleCache, member=47): An exception (java.lang.RuntimeException) occurred reading Message AggregateFilterRequest Type=31 for Service=DistributedCache{Name=StyleCache, State=(SERVICE_STARTED), LocalStorage=enabled, PartitionCount=1021, BackupCount=1, AssignedPartitions=205, BackupPartitions=204}
2010-02-09 13:04:22.653/90182.274 Oracle Coherence GE 3.4.2/411 <Error> (thread=DistributedCache:StyleCache, member=47): Terminating DistributedCache due to unhandled exception: java.lang.RuntimeException
2010-02-09 13:04:22.653/90182.274 Oracle Coherence GE 3.4.2/411 <Error> (thread=DistributedCache:StyleCache, member=47):
java.lang.RuntimeException: java.lang.ClassNotFoundException: com.edmunds.vehicle.Style$PublicationState
 at com.edmunds.common.coherence.EdmundsEqualsFilter.readExternal(EdmundsEqualsFilter.java:84)
 at com.tangosol.io.pof.PortableObjectSerializer.initialize(PortableObjectSerializer.java:153)
 at com.tangosol.io.pof.PortableObjectSerializer.deserialize(PortableObjectSerializer.java:128)
 at com.tangosol.io.pof.PofBufferReader.readAsObject(PofBufferReader.java:3284)
 at com.tangosol.io.pof.PofBufferReader.readAsObjectArray(PofBufferReader.java:3328)
 at com.tangosol.io.pof.PofBufferReader.readObjectArray(PofBufferReader.java:2168)
 at com.tangosol.util.filter.ArrayFilter.readExternal(ArrayFilter.java:243)
 at com.tangosol.io.pof.PortableObjectSerializer.initialize(PortableObjectSerializer.java:153)
 at com.tangosol.io.pof.PortableObjectSerializer.deserialize(PortableObjectSerializer.java:128)
 at com.tangosol.io.pof.PofBufferReader.readAsObject(PofBufferReader.java:3284)
 at com.tangosol.io.pof.PofBufferReader.readAsObjectArray(PofBufferReader.java:3328)
 at com.tangosol.io.pof.PofBufferReader.readObjectArray(PofBufferReader.java:2168)
 at com.tangosol.util.filter.ArrayFilter.readExternal(ArrayFilter.java:243)
 at com.tangosol.io.pof.PortableObjectSerializer.initialize(PortableObjectSerializer.java:153)
 at com.tangosol.io.pof.PortableObjectSerializer.deserialize(PortableObjectSerializer.java:128)
 at com.tangosol.io.pof.PofBufferReader.readAsObject(PofBufferReader.java:3284)
 at com.tangosol.io.pof.PofBufferReader.readObject(PofBufferReader.java:2599)
 at com.tangosol.io.pof.ConfigurablePofContext.deserialize(ConfigurablePofContext.java:348)
 at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.readObject(Service.CDB:4)
 at com.tangosol.coherence.component.net.Message.readObject(Message.CDB:1)
 at com.tangosol.coherence.component.net.message.requestMessage.distributedCacheRequest.partialRequest.FilterRequest.read(FilterRequest.CDB:8)
 at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$AggregateFilterRequest.read(DistributedCache.CDB:4)
 at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:117)
 at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.onNotify(DistributedCache.CDB:3)
 at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:37)
 at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassNotFoundException: com.edmunds.vehicle.Style$PublicationState
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:169)
 at com.edmunds.common.coherence.EdmundsEqualsFilter.readExternal(EdmundsEqualsFilter.java:82)
 ... 25 more
2010-02-09 13:04:23.122/90182.743 Oracle Coherence GE 3.4.2/411 <Info> (thread=Main Thread, member=47): Restarting Service: StyleCacheOur code was doing something simple like
catch(Exception e){
 throw new RuntimeException(e);
}Would using the ensureRuntimeException call do anything for us here?
Edited by: aidanol on Feb 12, 2010 11:41 AM

Best Practices for Team Collaboration using Adobe Captivate

With a team of 6 Instructional Designers, how can Adobe Captivate be approached where we can collaborate while producing e-learning material while maintaining a consistent look and feel of the e-learning we produce?
What are the best practices for a team of 6 IDs working and creating e-learning material in Captivate? Is there anything build-in that allows us to connect to the same libraries, templates, etc to share?
Please advise.
Thank you!
Susanne

Only some tips, never collaborated with someone else, being the solo teacher. You didn't mention which version you are using, what I write here is meant for CP7.
Be sure to prepare a theme and/or a template that will be used by everyone. A theme consists of master slides, object styles, skin editor. Master slides can have custom navigation shape buttons. In a template you can eventually also prepare different slides with placeholders, and eventually advanced actions etc. For CP6 and earlier that is the only way to reuse advanced actions, in Captivate 7 you can export shared actions that can be imported in any project for reuse.
A feature that few users know about are the external libraries. You can open the library of any project as an external library in another project. That is a good idea to store assets that you want to use in different projects: images, audio clips, video clips, eventually equations. The shared actions in a library can not (yet?) be used in another project however.
If you are on CP7 you have automatically the roundtripping with source Adobe Photoshop files and source Audition files, both from CC. That can also make collaboration lot easier if those assets are prepared in those applications. Will not expand on that, because I'm not sure you have the Creative Cloud applications.
Those are my two cents.
Lilybiri

Best practices for file architecture? I mainly have photos and music to organize.

Similar Messages

Maybe you are looking for