Help Please!! Best Practices for building an NDS Project...

We are doing a Proof of Concept on using NDS to develop non-SAP Java applications. We are attempting to determine if we can replace our current Java development tools with NDS/WAS.
We are struggling with SAP's terminology and "plumbing" for setting up/defining Java projects. For example, what is and when do you define Tracks, Software Components, Development Components, etc. All of these terms are totally foreign to us and do not relate to our current Java environment (at least not that we can see). We are also struggling with how the DTR and activities tie in to those components.
If any one has defined best practices for setting up Java projects or has struggled with and overcome these same issues, please provide us with some guidance. This is a very frustrating and time-consuming issue for us.
Thank you!!

Hello Peggy,
this is my first post but I hope it helps you anyway.
To learn the SAP "language" I additionally used the a SAP Presentation regarding the SAP JDI.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/java development infrastructure real world use webinar.pdf
I think this one is quite useful as an addon to the other links for information you already got. Your name also indicates that your mother-tongue language is German. If so, the german version of the book (Java-Programming with the SAP WAS) is already available for purchase and really useful. Then, you can also use the information provided by the University of Potsdam. They have an introduction about how to setup a track in the SLD and then how to setup SCs.
http://epic.hpi.uni-potsdam.de/nwlab/SC+Track.html
Hope this helps...

Similar Messages

SAP Best Practices for Building construction industry

Hi All:
Is there any best practices available in the building/house construction industry? Can you please guide me through that?
Thank you.
Regards,
- Rohan

Yes they do
Look here:
http://www.simplysap.com/sap-news/sap-articles/sap-adds-60-offerings-family-of-sap-best-practices.htm
http://www.sap.com/industries/eng_construct/index.epx
http://download.sap.com/download.epd?context=D6B5CC86EFFB6EF10CE24BDC2B076371A3E006D336E32EFF63C3CD11CF5450FDA274E617019330E191ABE803C04F532DCFB4A0F8A50E3F32

Best practice for building extra navigation bar?

I've been away from Captivate for a few years.
What's the best method to build this navigation system (shown below) with on states, over states? The Captivate nav bar will appear at bottom.
The menu UI will be repurposed across several lessons and units.
I prefer to keep it in Captivate, but could use Flash if needed.
Disappointed that Master slides do not include buttons.
Use custom buttons in a Template?
Or is a Flash widget the best method? How to handle the coding?
Thanks SO much for your suggestions.

Apparently I forgot to mention the buttons widget. It is a static widget and can be used on a master slide. It doesn't have all functionalities of the normal buttons, and you are limited about its layout but navigation is within its dropdown list with possible actions.
I couldn't detect which version you are using? In CP5.0 this button comes only as a static widget (Buttons) and has a pausing point at about 10secs (you cannot change this pausing point). In CP 5.5 it comes in a static (you need this) and an interactive (you cannot use that on master slide) version. They do not have a pausing point. If you want the static button widget with a pausing point, you can download a version from my blog:
What I (dis)like in CP65.5

Best practices for building menus using resource bundles?

Greetings; I am curious to find out what the current best practices people are using to build menus/menu bars using resource bundles, specifically ListResourceBundle.
What I am trying to figure out is how best to write my Swing application so it does not need to know what menu items it needs to grab from the resource bundle.
The only idea I have come up with is this:
class MyBundle extends ListResourceBundle {
private Object[][] contents = {
{"menubar", { {"menu.file.item", "blah"}, ....} }
}Inside the GUI class:
Object[][] menubar = resourceBundle.getObject("menubar");I would then iterate over the menu bar items and build the menu. I would have to use a naming scheme and then parse appropriately to know when to start a new menu, when a submenu occurs, etc.
Is this the common practice, or does anyone know of a more clever way of doing this? I've searched various FAQs and googled about, but I have yet to come across any sort of tutorial or page that covers this.

Anyone have any input on this? Am I close to the solution people are
using out in real production environments?

Best practice for moving images between projects?

Hey all,
I have a project that has an album inside of it. I want to move the album, containing all of the photographs to a new project. If I drag the photos individually to the new project it moves them successfully although they now don't belong to an album in their new project. If I drag the album itself it moves the album and photographs but leaves the photos in the original project as well.
Does anyone have some best practice ideas for this scenario?
Thanks in advance for any help!

As you have discovered if the drop target is the project the images move projects. If the drop target is an album the images show up in the album but do not actually move anywhere. Moving albums does nothing to move masters. So...
Select all of the images in the album. Drag them to the new project and then drag the album to the new project. Simple enough.
RB

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

FAQ: Are there best practices for building projects within the 20 page/state limit?

The 20 page/state limit in Flash Catalyst is there to prevent Catalyst (and your finished application) from running slowly. You can however build efficient applications that have more than 20 states by using custom components. Custom components can contain states as well; so by creating an app that has several states, and using custom components that have states, you can get more unique views of your app while keeping it efficiently built.
Try this:
1. Select some of your arwork where you need more states. Right click and choose "Convert to Custom Component"
2. Double-click to edit the custom component. Note that you can now create states in the custom component. Try creating a few states here.
3. To exit editing the component, double click a blank area on the artboard.
4. If you try creating an "On click transition to state" interaction now you will see that you can choose from both the states of the application as well as the states of the custom component.
Answered by: Ty Voliter. See entire discussion.
More help:
Video tutorial on custom components
Video/demo discussing the benefits of "pushing interactivity down" into custom components, by Ian Giblin @ MAX 2009
(jump to the 11:15 mark, and watch through to about 20:30)
Another forum post by Ty:
Here's an ASCII diagram to illustrate one way of pushing application or top-level pages/states down into a custom component:
Before:
State1     State2     State3     State4     State5     State6     State7...
After (project refactored to push three top-level states down into a custom component):
State1     State2     State3      State7...
                    |
Custom Component
State4     State5     State6
For some projects this can be an inconvenient workaround, and for others it can really clean things up by reducing complexity. If you have several top-level pages in your app that are completely different than other pages (for example, they don't share any objects with the other states) than pushing these down into a custom component makes things a lot more manageable in Catalyst. The layers panel, for example, shows all objects across all states-- this is useful when your states share many objects. If however, your states don't share a lot of objects, the layers panel can get a bit unmanageable. Refactoring into a custom component allows you to fix this by grouping content into a container.

The 20 page/state limit in Flash Catalyst is there to prevent Catalyst (and your finished application) from running slowly. You can however build efficient applications that have more than 20 states by using custom components. Custom components can contain states as well; so by creating an app that has several states, and using custom components that have states, you can get more unique views of your app while keeping it efficiently built.
Try this:
1. Select some of your arwork where you need more states. Right click and choose "Convert to Custom Component"
2. Double-click to edit the custom component. Note that you can now create states in the custom component. Try creating a few states here.
3. To exit editing the component, double click a blank area on the artboard.
4. If you try creating an "On click transition to state" interaction now you will see that you can choose from both the states of the application as well as the states of the custom component.
Answered by: Ty Voliter. See entire discussion.
More help:
Video tutorial on custom components
Video/demo discussing the benefits of "pushing interactivity down" into custom components, by Ian Giblin @ MAX 2009
(jump to the 11:15 mark, and watch through to about 20:30)
Another forum post by Ty:
Here's an ASCII diagram to illustrate one way of pushing application or top-level pages/states down into a custom component:
Before:
State1     State2     State3     State4     State5     State6     State7...
After (project refactored to push three top-level states down into a custom component):
State1     State2     State3      State7...
                    |
Custom Component
State4     State5     State6
For some projects this can be an inconvenient workaround, and for others it can really clean things up by reducing complexity. If you have several top-level pages in your app that are completely different than other pages (for example, they don't share any objects with the other states) than pushing these down into a custom component makes things a lot more manageable in Catalyst. The layers panel, for example, shows all objects across all states-- this is useful when your states share many objects. If however, your states don't share a lot of objects, the layers panel can get a bit unmanageable. Refactoring into a custom component allows you to fix this by grouping content into a container.

Best practice for building OLAP cubes??

Hi All,
I have to build about 10 cubes as minimum for 50 GB database that share some dimensions, these cubes for 6 business areas.
I want to know whether to build all cubes on one analytical workspace or what??
Regards,
Gado

If the cubes are going to share dimensions, then yes I would recommend putting them all in the same analytic workspace.

Best Practices for Publishing your Captivate Project

Come join RealEyes tomorrow for a session on publishing Captivate projects. We will be discussing each method of publishing, and the benefits and drawbacks of publishing that way. We will also cover some of the common things missed that can make a better experience for your viewers when accessing your project.
Come here to join us: http://cyourteam.com/realeyesconnect/ev … te-project
The session is from 11A-12P Mountain Time.

Ok, we finally have a version of this session to post up here.
Enjoy! http://cyourteam.com/realeyesconnect/ev … and-tricks

Best practices for organizing a large "project" with multiple programmers

should i put everyone in one application? should everyone get their own applcation? my understanding (limited) is the level of granularity for CVS is the application. sounds to me like multiple developers checking the same application in and out would be a disaster. if every developer has there own application what problems will i have deploying. how do i handle my configuration (navigation) diagram? any thoughts would be appreciated.

Have a read through these:
http://download.oracle.com/docs/html/B25947_01/team_productivity.htm#BABBEFFF
http://brendenanstey.blogspot.com/2006/11/tips-for-using-cvs-with-jdeveloper.html

Best Practices for Defining NDS Java Projects...

We are doing a Proof of Concept on using NDS to develop non-SAP Java applications. We are attempting to determine if we can replace our current Java development tools with NDS/WAS.
We are struggling with SAP's terminology and "plumbing" for setting up/defining Java projects. For example, what is and when do you define Tracks, Software Components, Development Components, etc. All of these terms are totally foreign to us and do not relate to our current Java environment (at least not that we can see). We are also struggling with how the DTR and activities tie in to those components.
If any one has defined best practices for setting up Java projects or has struggled with and overcome these same issues, please provide us with some guidance. This is a very frustrating and time-consuming issue for us.
Thank you!!

Hi Peggy,
In Component Model we divide software projects into small components.Components can use other components in well defined manner.
A development object is a part of a component that can be changed or developed in some way; it provides the component with a certain part of its functionality. A development object may be a Java class, a Web Dynpro view, a table definition, a JSP page, and so on. Development objects are always stored as sources in a repository.
A development component can be defined as a frame shared by a number of objects, which are part of the software.
Software components combine components (DCs) to larger units for delivery and deployment.
A track comprises configurations and runtime systems required for developing software component versions.It ensures stable states of deliverables used by subsequent tracks.
The Design Time Repository is for versioning source code management. Distributed development of software in teams. Transport and replication of sources.
You can also find lot of support in SDN for the above concepts with tutorials.
Refer this Link for a overview on Java development Infrastructure(JDI)
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/java/java development infrastructure jdi overview.pdf
To understand further
Working with Net Weaver Development Infrastructure :
http://help.sap.com/saphelp_nw04/helpdata/en/03/f6bc3d42f46c33e10000000a11405a/content.htm
In the above link you can find all the concepts clearly explained.You can also find the required tutorials for development.
Regards,
Vijith

What is the Best practice for ceramic industry?

Dear All;
i would like to ask two questions:
1- which manufacturing category (process or discrete) fit ceramic industry?
2- what is the Best practice for ceramic industry?
please note from the below link
[https://websmp103.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000409682008E ]
i recognized that ceramic industry is under category called building material which in turn under mill product and mining
but there is no best practices for building material or even mill product and only fabricated meta and mining best practices is available.
thanks in advance

Hi,
I understand that you refer to production of ceramic tiles. The solution for PP was process, with these setps: raw materials preparation (glazes and frits), dry pressing (I don't know extrusion process), glazing, firing (single fire), sorting and packing. In Spain, usually are All-in-one solutions (R/3 o ECC solutions). Perhaps the production of decors have fast firing and additional processes.
In my opinion, the curiosity is in batch determination in SD, that you must determine in sales order because builders want that the order will be homogeneus in tone and caliber, and he/she can split the order in diferents deliveries. You must think that batch is tone (diferents colours in firing and so on) and in caliber.
I hope this helps you
Regards,
Eduardo

Is there a list of best practices for Azure Cloud Services?

Hi all;
I was talking with a Sql Server expert today and learned that Azure Sql Server can take up to a minute to respond to a query that normally takes a fraction of a second. This is one of those things where it's really valuable to learn it when architecting as
opposed to when we go live.
Cloud Services are not Sql Server (obviously) but that led to the question - Is there a list of best practices for Azure Cloud Services? If so, what are they?
We will be placing the cloud services in multiple datacenters and using traffic manager to point people to the right one. The cloud service will set between an IMAP client & server, pretending to be the mail client to the server, and the server to the client.
Mostly it will pass all requests & responses across from one to the other.
thanks - dave
What we did for the last 6 months -
Made the world's coolest reporting & docgen system even more amazing

hi dave,
>>Cloud Services are not Sql Server (obviously) but that led to the question - Is there a list of best practices for Azure Cloud Services? If so, what are they?
For this issue, I have collected some blogs and document about best practices for azure cloud service, you can view them, but I am not sure they are your need.
http://msdn.microsoft.com/en-us/library/azure/xx130451.aspx
http://gauravmantri.com/2013/01/11/some-best-practices-for-building-windows-azure-cloud-applications/
http://www.hanselman.com/blog/CloudPowerHowToScaleAzureWebsitesGloballyWithTrafficManager.aspx
http://msdn.microsoft.com/en-us/library/azure/jj717232.aspxhttp://azure.microsoft.com/en-us/documentation/articles/best-practices-performance/
>>The cloud service will set between an IMAP client & server, pretending to be the mail client to the server, and the server to the client. Mostly it will pass all requests & responses across from one to the other.
For your scenarioes, If you'd like to communicate with each instances, I recommend you refer to this document (
http://msdn.microsoft.com/en-us/library/azure/hh180158.aspx ). And generally, if we want connect the client to server on Azure, the service bus is a good choice (http://azure.microsoft.com/en-us/documentation/articles/cloud-services-dotnet-multi-tier-app-using-service-bus-queues/
If I misunderstood, please let me know.
Regards,
Will
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Best practice for putting together scenes in a Flash project?

Hi, I'm currently working on a flash project with the following characteristics:
using a PC
2048x1080 pixels
30 fps
One audio file that plays (once) continuously across the whole project
there are actions that relate to the audio, so the timing is important
at least 10 scenes
about 7 minutes long total
current intent is for it to be played in a modern theater as a surprise
What is the best practice for working on this project and then compiling it together?
Do it all in one project file?
Split the work into different project (xfl) files for each scene and then put it together when all the scenes are finalized?
Use one project file but create different "scenes" for each respective scene? I think this is the "classic" way (?).
Make the scenes "movie clips" and then insert them into the timeline with the audio as its own layer?
Other?
I'm currently working on it by having it all in one project file. But I've noticed that there's some lag (or it gets choppy) at certain parts during playback and the SWF history shows 3.1 MB with a yellow triangle with exclamation point symbol. Thanks in advance.

you would only do that if it makes your job easier. generally speaking, it would not.
when trying to sync sound and animation i think most authors find it easiest to use graphic symbols because you can see their animation when scrubbing the main timeline. with movieclips you only see their animation when testing.
however, if you're going to use actionscript to control some of your symbols, those symbols should be movieclips.

Best practices for ARM - please help!!!

Hi all,
Can you please help with any pointers / links to documents describing best practices for "who should be creating" the GRC request in below workflow of ARM in GRC 10.0??
Create GRC request -> role approver -> risk manager -> security team
options are : end user / Manager / Functional super users / security team.
End user and manager not possible- we can not train so many people. Functional team is refusing since its a lot of work. Please help me with pointers to any best practices documents.
Thanks!!!!

In this case, I recommend proposing that the department managers create GRC Access Requests. In order for the managers to comprehend the new process, you should create a separate "Role Catalog" that describes what abilities each role enables. This Role Catalog needs to be taught to the department Managers, and they need to fully understand what tcodes and abilities are inside of each role. From your workflow design, it looks like Role Owners should be brought into these workshops.
You might consider a Role Catalog that the manager could filter on and make selections from. For example, an AP manager could select "Accounts Payable" roles, and then choose from a smaller list of AP-related roles. You could map business functions or tasks to specific technical roles. The design flaw here, of course, is the way your technical roles have been designed.
The point being, GRC AC 10 is not business-user friendly, so using an intuitive "Role Catalog" really helps the managers understand which technical roles they should be selecting in GRC ARs. They can use this catalog to spit out a list of technical role names that they can then search for within the GRC Access Request.
At all costs, avoid having end-users create ARs. They usually select the wrong access, and the process then becomes very long and drawn out because the role owners or security stages need to mix and match the access after the fact. You should choose a Requestor who has the highest chance of requesting the correct access. This is usually the user's Manager, but you need to propose this solution in a way that won't scare off the manager - at the end of the day, they do NOT want to take on more work.
If you are using SAP HR, then you can attempt HR Triggers for New User Access Requests, which automatically fill out and submit the GRC AR upon a specific HR action (New Hire, or Termination). I do not recommend going down this path, however. It is very confusing, time consuming, and difficult to integrate properly.
Good luck!
-Ken

Help Please!! Best Practices for building an NDS Project...

Similar Messages

Maybe you are looking for