Best practice to rendering components in latest jDEV 11.1.1.3

All,
I am working on jDEV 11.1.1.3. One of my requirement is to disable / rendering the fields depending on the status of the column in the database. I would like what would be best practice to implement this. Do we need to add the logic in the "beforePhase" or in the application module? If it's in the application module how can we get the handle to the components on the page? I am getting exceptions when I added the logic in the "beforePhase" method ("Target can not be reachable") even though I have added the managed bean adfc-config file.
Thanks

Hi,
for the lable -->shortDesc just bind it to a variable on the managed bean and set whatever you want for it.
If I get your question correctly you want to change the state of a componet in view dynamically base on some Database logic on model.
this case is possible but not very easy.
for example the hidden attirbute for a component can be set in the model in the control hint.
if you want to dynamically render or not render a component you have to override the controlhint of the view.
in the control-hint you will return true o false programmically, I have done this for updateble attribute of the componet so my field on the view would be programmically be updateble if I set some attibute on the view. (it is totally independed to the ADF-Faces and the viewcontroller) it is based on the logic on model.
but this kind of topic are advance and not easiy handled.
if you want more information about it I hope to be able to help you.
Thanks.

Similar Messages

Best practices for adding components in a composite custom component

Hello,
I am developing a custom, composite JSF component need to dynamically add child components in my renderer class. I've noticed that people add components to a custom component in many different ways. I'd like to follow JSF best practices when developing this component - of the following approaches, which would you recommend? Or is there yet another approach I should be using?
1) in the encodeBegin method of my renderer class, create a new component, add it to the component tree, and let the page life cycle take care of the rendering:
HtmlDataList dimensionStateGroupDataList = (HtmlDataList) app.createComponent( HtmlDataList.COMPONENT_TYPE );
//set properties on dimensionStateGroupDataList
component.getChildren().add(dimensionStateGroupDataList);
2) in either the encodeBegin or encodeEnd method, create a component and encode it:
HtmlDataList dimensionStateGroupDataList = (HtmlDataList) app.createComponent( HtmlDataList.COMPONENT_TYPE );
//set properties on dimensionStateGroupDataList
dimensionStateGroupDataList.encodeBegin();
dimensionStateGroupDataList.encodeEnd();
Both of these methods are functional, and I prefer the first (why encode children if you don't have to?), but I am interested in other people's take on how this should be done.
Thanks for your help.
-Christopher

My bad, sorry, wasnt concentrating, Im afraid I have no experience with portlets, but I would have thought that you can mimic the outputLinkEx in you renderer by encoding your own links?
If you were to bind a backing bean variable to an outputLinkEx what would it be? Not understanding portlets, or knowing what an outputLinkEx is may be hindering me, but you should be able to create an instance of it in code like (this example uses HtmlOutputLink, you would need to know which component to use):
HtmlOutputLink hol = new HtmlOutputLink();
hol.set....Then set any attributes on it, and explicitly call its encodeStart, encodeEnd functions. Is that way off the mark.

View State Best Practice for Hiding Components?

When changing states and hiding components, what is the best practice?
Set Height/Width=0?
Set Visible/IncludeInLayout=False?
Or is there a better way?

Good point. That's what I thought but I'm working through 'Adobe Flex 3 Training from the Source' and they explicitly set width/height to 0 in the new state so I thought I was not doing it correctly.

Best Practice for module components based on API's

Hi all,
is there a white paper/other documents which outline best
practice for using table/module component api's and best
approaches to get around restrictions?
I would also appreciate war stories about using this method of
Forms development bearing in mind i would be using this as the
foundation of a web deployed based application (intranet first -
ultimately internet).
Thanks
Mark
null

You cannot add agents to skills dynamically; however, you can queue the caller into more than one CSQ based on statistics. You would use the Get Reporting Statistics and an If step within the Queued branch of your first Select Resource step. If the condition is met (e.g. Contacts Waiting >= 10) then exectue a second Select Resource step within the queued branch of the first. The contact would then be waiting in both CSQs waiting for an agent.

Best Practices? Rendering to Flash for streaming web....

I am always impressed with the flash based videos I see streaming on YouTube, FastCompany.Tv and other sites....
My question... can you please either explain or point me in the right direction for streaming video best practices? Specifically, I am looking for info on best settings to produce the flash video (codecs and/or FCP render settings) and then what do people use as a flash player on their websites to show the end result.
My goal is to create internal instructional videos for corporate training and then host them on my site (or streaming from Akamai). I would like people to be able to watch it in a flash player embedded on my site (and have it look good even if they click on a full screen button) or download to their iPod.
Examples of what I like, but I don't know how to do:
http://www.fastcompany.tv/video/getting-government-work
Thank you in advance for your expertise and insight.
-Steven

I would like people to be able to watch it in a flash player embedded on my site (and have it look good even if they click on a full screen button) or download to their iPod.
Use the H.264 setting for iPod in Compressor. The h.264 file will play in a JW Flash Player and it's able to be downloaded for iPod viewing.

Best Practices ADF Business Components

Hi all,
I'm reading the Dev Guide of ADF Business Components, and I've some questions:
a) In the business tier, Which is the best way to create new rows in the db? I've found two ways: Using a ViewObject and then call create and insert or using the EntityDefinitionImpl object and call the createInstance2 function.
b) In the business tier, which is the best way to search for a row in the db? I've found two ways: Using findByKey on the ViewObject or using the findByPrimaryKey on the EntityDefinitionImpl object.
Thanks!

Hi,
a) use a ViewObject
b) also I would think its the ViewObject
Frank

What's the best practice to get App Module on Jdev 10.1.3 using Struts/ADF?

Hi,
I read Mr. Muench's post stating that the best way to execute an App. Module method is to make the method part of the client interface and then drag and drop it on a form as a button ...
In another post Muench says that a another way to get the App Module is using getDataProvider() method, I tried and found that this worked in:
// standard event handler interface
// on PageController class
public class MyFormPageController extends PageController
public void onUpdate(PageLifecycleContext ctx)
AMServImp am;
am = (AMServImpl)ctx.getBindingContext().getDefaultDataControl().getDataProvider();
am.myMethod( ... );
am.getTransaction().commit();
I really like the second option because is closer to what I used to do in 10.1.2 with an event handler receiving DataActionContex parameter. Besides, is not clear to me in the former method with the drag and drop how the form inputs are assigned to the method parameters ....
I would like to know however what is the best way and why ?
Any comments ?
-OM
Message was edited by:
omar71

According to JSR 227, which ADFm is implementing, the view/controller portions of your application aren't really supposed to be touching the business services, or even the data controls, at all. They're supposed to do all model manipulation entirely through the databindings.
This is just another bit of "code separation"--much like MVC code separation--that should make the application a bit easier to maintain. Your application module could change dramatically--maybe even be replaced by an EJB session bean--and all you have to do is change the .dcx file and your page model files, rather than searching through your code. Maintainability and readability is the advantage here; I don't think there could possibly be any slowdown by calling ctx.getBindingContext().getDefaultDataControl().getDataProvider(), since that's what the bindings would do anyway.
Well, of course there's the "ADF supports going this way declaratively", which is not to be sneezed at as an advantage.
As to how to put the form values in to the method binding: Look up the <af:setActionListener> tag (e.g., using full-text search in the help). You can nest that into your commandButton or commandLink tags and use it to set method parameters.
Best,
Avrom

SAP Best practice Installation for IS-H

Hi ,
We are implementing SAP IS-H module for one of the client.We configured SAP Best Practice for Beseline package US with EHP 5 with V1.605 version.Now we are trying to configure SAP Best practice for Industry specific package for Health Care (IS-H).But in service market we got the best practice for IS-H with latest version of EHP 3 with version V1.603.I am not sure whether we can install successfully BP for ISH with verison V1.603 in a system which already has SAP BP with baseline package verison V1.605.Please clarify the same.
Thanks,
Vigneswaran S

Need your inputs experts.
Thanks,
Lasya.

Best Practice : Creating Custom Renderer for Standard Component

I've been reading the docs and a few threads about Custom Renderers. The best practice seems to be to create a Custom Component where you need a Custom Renderer. Is this the case?
See [this post|http://forums.sun.com/thread.jspa?forumID=427&threadID=520422]
I've created several Custom Renderers to override the HTML provided by the Standard Components, however I can't see the benefit in also creating a Custom Component when the behaviour of the standard component is just fine.
Thanks,
Damian.

It all depends on what you are trying to accomplish. Generally speaking if all you need is for the user interface output to be changed then a renderer will work just fine. A new component is usually made in order to provide some fundamental change in server side functionality not related to the user interface. - Ponderator

What is best practice for conditional rendering?

i have a set of radio buttons that conditionally render another set, which in turn conditionally render a 3rd set.
i am doing this by using a valueChangeListener on an h:selectOneRadio
when i click yes on the 1st set it renders the 2nd set.
when i click yes on the 2nd set it renders the 3rd set.
when i click no on the 1st set now it correctly removes the 2nd & 3rd sets, the method also nulls the values.
when i click yes on the 1st set, it renders the 2nd set with the old values even though they were nulled. and i can see in the debugger they are still null.
so there seems to be an issue updating the model, but i dont know what that issue is. im sure it just has something to do with the way i am trying this conditional render. please see below for my first field and my valueChangeListener method.
any help with what is a best practice for this scenario would be greatly appreciated.
<h:panelGrid id="grid20a" columns="1">
                         <h:outputText value="Does this consult pertain to a specific "/>
                         <h:outputText value="planned or ongoing research project?: *"/>
                    </h:panelGrid>
                    <h:selectOneRadio id="specificResearch1" value="#{ethicsConsultBacking.bean.specificResearch}"
                         layout="lineDirection" required="true"
                         valueChangeListener="#{ethicsConsultBacking.processValueChangeSpecificResearch}">
                              <f:selectItems value="#{ethicsConsultBacking.yesNoMap}" />
                              <a4j:support event="onclick" reRender="form"/>
                    </h:selectOneRadio>
                    <h:message for="specificResearch1" styleClass="redText" />
public void processValueChangeSpecificResearch(ValueChangeEvent e) throws AbortProcessingException
          String newValue = e.getNewValue().toString();
          //reinitialize
          this.setRenderHumanSubjectResearch(false);
          this.setRenderIrbSection(false);
          this.setRenderIrbProtocolNumber(false);
          this.getBean().setHumanSubjectResearch(null);
          this.getBean().setPrimaryIrb(null);
          this.getBean().setIrbStatus(null);
          this.getBean().setIrbProtocolNumber(null);
          //check condition
          if (newValue.equalsIgnoreCase(this.YES))
               this.setRenderHumanSubjectResearch(true);
           * Clearing validation messages.
           * This will get around the issue with having a field
           * on the form that is both required & immediate.
          Iterator it = this.getFacesContext().getMessages();
          while (it.hasNext())
               it.next();
               it.remove();
          this.getFacesContext().renderResponse();
     }i also tried doing this another way by just using an action method attached to the a4j:support tag, but that introduced a different set of issue. so ill leave that out for now unless that is the direction someone would like to direct my issue in.
Thanks in advance

Similar issue is covered and explained here: [http://balusc.blogspot.com/2007/10/populate-child-menus.html]. Not sure if it solves your problem as you're using ajax4jsf whereas I don't, but it might give new insights. To the point you might need to bind the component(s) and use setValue(null) or setSubmittedValue(null).

"Best practice" for components calling components on different panels.

I'm very new to Swing. I have been learning from tutorials, but these are always relatively simple interfaces , in which every component and container is initialised and added in the constructor of a main JFrame (extension) object.
I would assume that more complex, real-world examples would have JPanels initialise themselves. For example, I am working on a project in which the JFrame holds multiple JPanels. One of these Panels holds a group of JToggleButtons (grouped in a ButtonGroup). The action event for each button involves calling the repaint method of one of the other Panels.
Obviously, if you initialise everything in the JFrame, you can simply have the ActionListener refer to the other JPanel directly, by making the ActionListener a nested class within the JFrame class. However, I would like the JPanels to initialise their own components, including setting the button actions, by using an extension of class JPanel which includes the ActionListeners as nested classes. Therefore the ActionListener has no direct access to JPanel it needs to repaint.
What, then, is considered "best practice" for allowing these components to interact (not simply in this situation, but more generally)? Should I pass a reference to the JPanel that needs to be repainted to the JPanel that contains the ActionListeners? Should I notify the main JFrame that the Action event has fired, and then have that call "repaint"? Or is there a more common or more correct way of doing this?
Similarly, one of the JPanels needs to use a field belonging to the JFrame that holds it. Should I pass a reference to this object to the JPanel, or should I have the JPanel use "getParent()", or some other method?
I realise there are no concrete answers to this query, but I am wondering whether there are accepted practices for achieving this. My instinct is to simply pass a JPanel reference to the JPanel that needs to call repaint, but I am unsure how extensible this would be, how tightly coupled these classes would become.
Any advice anybody could give me would be much appreciated. Sorry the question is so long-winded. :)

Hello,
nice to get feedback.
I've been looking at a few resources on this issue from my last post. In my application I have been using the Observer and Observable classes to implement the MVC pattern suggested by T.PD.(...)
Two issues (not fatal, but annoying) with this are:
-Observable is a class, not an interface; since most of my Observers already extend JPanel (or some such), I have had to create inner classes.
-If an Observer is observing multiple Observables, it will have to determine which Observer called its update() method (by using reference equality or class comparison or whatever). Again, a very minor issue, but something to keep in mind.I don't deem those issues are minor. The second one in particular, is rather annoying in terms of maintenance ("Err, remind me, which widget is calling this "update()" method?").
In addition to that, the Observable/Observer are legacy non-generified classes, that incurr a loosely-typed approach (the subject and context arguments to the update(Observable subject, Object context) methods give hardly any info in themselves, and they generally have to be cast to provide app-specific information.
Note that the "notification model" from AWT and Swing widgets is not Observer-Observable, but merely EventListener . Although we can only guess what reasons made them develop a specific notification model, I deem this essentially stems from those reasons.
The contrasting appraoches are discussed in this article from Bill Venners: The Event Generator Idiom (http://www.artima.com/designtechniques/eventgenP.html).
N.B.: this article is from a previous-millenary series of "Design Techniques" articles that I found very useful when I learned OO design (GUI or not).
One last nail against the Observer/Observable model: these are general classes that can be used regardless of the context (GUI/non-GUI code), so this makes it easier to forget about Swing threading rules when using them (essentially: is the update method called in the EDT or not).
If anybody has any information on the performance or efficiency of using Observable/ObserverI would be very surprised if this had any performance impact. If it had, that would mean that you have either:
- a lot of widgets that are listening to one another (and then the Mediator pattern is almost a must to structure such entangled dependencies). And even then I don't think there could be any impact below a few thousands widgets.
- expensive or long-running computation in the update methods. That's unrelated to the notification model itself.
- a lot of non-GUI components that use the Observer/Observable to communicate among themselves - all the more risk then, to have a GUI update() called outside the EDT, see remark above.
(or whether there are inbuilt equivalents for Swing components)See discussion above.
As far as your remark 2 goes (if one observer observes more than one subjects, the update() method contains branching logic) : this also occurs with the Event Delegation model indeed: for example, it is quite common that people complain that their actionPerformed() method becomes unwieldy when the same class listens for several JButtons.
The usual advice for this is, use anonymous listeners, each of which handles the event from only one source (and generally very close in code to the definition of that source), and that simply translates the "generic" event notification method into a specific method call of a Controller or Mediator .
Best regards.
J.
Edited by: jduprez on May 9, 2011 10:10 AM

SAP BO Dashboards 4.1 best practice on layout and components

Dear SCN,
I have requirement to create a BO 4.1 dashboard with data & Visualization based on a excel sheet which is currently in use as a Mgmt dashboard. The current excel dashboard is having more than 100 KPIs in one view which is readable only if you put in on a slide and view it in full screen by running a slideshow.
Question 1:
1. Being the suggested size of the Xcelsius canvas not more than 1024 X 768 so that it is viewable with out scroll bar in BI launchpad or in any browser or in pdf, I am trying to confirm in this forum that the canvas size of 1024 X 768 is the recommended maximum size for the dashboard to get the clear view in any browser/BI launchpad . Pls confirm as it will help me in doing the design for the KPIs and its visualization.
Question 2:
1. I am using the BICS connection and accessing the source data from BW. Because the no. of KPIs are more and ranging between 10 cubes and 40 queries as the data is across different modules, I would like to know what is the recommended no. of connections for queries /cubes in dashboard using BICS connectivity which does not affect the performance
2. For the same dashboard using BICS connection, What is ideal number of components like Charts/Scorecard/Spreadsheet table that is recommended to use to ensure better performance?
I appreciate your answers which can help the finalization of the dashboard design for this dashboard of data and visualization requirements which is very high when compared to the normal dashboards.
Thanks and Regards
Jana

Hi Suman,
Thanks for your answers.You answers and links which you have attached are helpful and It answered my questions related to canvas size and Connections.
I am expecting some benchmark numbers as per the best practices with respect to the No. of components to be used to ensure the better loading of the dashboard. As the increase in number of components increase the size of the dashboard and also it requires more time to load the data for the components, I am looking for the number as per the best practice by considering the below points.
1. When I say the no. of components, I am not considering the components like label, text box,combo box or list box. I am considering the components which is used for visualization and interactive drill down on top of the visualized charts ( For Eg. Column charts, Pie charts, Gauges ).
2.I am not going to use more calculations/formulas in my dashboards as the values and structure are almost the same with the BEx query.
3.Having around 10 to 12 connections.
4.The data sets are not more than 900 rows totally. For any control, we will be binding only 100 rows at the max as the data for the KPIs are summarized at the year/month level at the BW layer.
Since the KPIs are more, the Visualizations are more and we can't re-use the Visualization charts for most of the KPIs. Currently I am ending up with ~35 charts/ gauges along with other label and selection controls which I will be using to show 100 KPIs with unique visualization requirements and I am going for the tab-wise layout with more dynamic to accommodate and separate logically.
Hope these details will give clear picture of why I am looking for the Benchmark on No. of components .
I appreciate your help!
Thanks and Regards
Jana

Best Practice For ID value On Components

I was just wondering what the best practice was for setting the ID value on ADF components. I have seen that on naming containers they recommend the length of the ID value be 7 characters or less to minimize the amount of HTML that has to be sent to the client. Should we just keep all ID fields as their default values which are relatively short or is it better to give them meaningful values? Any guidance would be appreciated.
Thanks.

Hi,
It depends on the usage. If you are using client listeners, where you want to get the id of the component to process, you can name them to have some meaning. However, there is no harm in keeping the default id as it is.
-Arun

SAP ASE Best Practice latest update

Hello experts,
just wondering if somebody already reviewed thoroughly latest guide for best practices on SAP Sybase ASE?
I am talking about the document from note 1680803 - SYB: Migration to SAP Adaptive Server Enterprise - Best Practice (former note 1722359 - SYB: Running SAP applications on SAP ASE - Best Practice).
The guide for normal runtime operation was merged with the guide for migration, but there are some contradictory statements.
Apart from that the study case is again designed for server with huge memory and lot of CPU cores (so not so real case normally, I wonder who setup so often such huge servers...), I have found some inconsistencies.
E.g. in part "Reconfigure Engines and Parallel Processing", they talk about to limit ASE engines to 16, but the command configures 32.
alter thread pool syb_default_pool with thread count = 32, idle timeout = 2000
No change to the previous setup for migration. Is this just typo? I understand it should be 16, and then also number of network tasks for normal operation would be 4 (as mentioned in the beginning of guide that normally you set up 1 per 3-4 engnes). If this is not typo, then number of network tasks is wrong as it should be 8.
Also they introduced idle timeout, but only talking about ERP and possible lower value for Solman - does this mean that for BW you keep default value (which if I am not mistaken is 100)? As per ADM540 you should even decrease this timeout when SAP system is sharing server with database - I know that document is old, but is again contradictory, not saying that it is wrong, but not well explained.
If anybody checked new version of guide, please let me know, I think it is bit messed up and is bit difficult to distinguish what you should set up for migration case and what for normal operation case.
Thanks!
Regards,
Matus

Actually, quite a few customers run with that many engines/memory.   In fact, it is difficult these days to even buy a server with less than 128GB of memory and 16 cores/32 threads.    Pretty much the only time we see less is when the install is in a VM.   Interestingly, we had comments from the first version suggesting the numbers were not realistic given the typical size of systems being deployed were much larger....    In addition, in my experience with customers on SAP systems, they were not aware of how much memory was necessary to really support medium to large systems based on the configurations they were attempting.
I am sorry that you feel some of the examples are contradictory. You are correct in pointing out that the text refers to 16 engines and the example configures 32....   So yes, for that specific example, it should have been 16.
Secondly, not having seen ADM540, but I think there is a bit of a problem if they suggest that.   I my opinion (and I have spent a lifetime tuning ASE), the idle timeout for ERP and BW should likely both be 1000+ and 2000 is not unreasonable.   The comment in ADM540 is likely due to if ASE and a NW CI are sharing the same cores - e.g. you have a 4 core box and ASE is running on 2 cores (we will ignore threads for this discussion) and you have 30 NW worker processes - which obviously will need to bump ASE off the cpu in order to run.   This may be fine in a test/dev or even a solution manager system, but bumping ASE off the core is NOT a good thing for a production system. In fact, I would encourage using numactl or similar to fence off the the cores used for ASE from NW worker processes if at all possible.   We have seen cases of overloaded NW installations with multiple CI instances with hundreds of worker processes each starving cpu away from ASE......sooo....I would tend to actually be a bit more than firm on suggesting that 100 is a very bad starting point.   Given the number of client side joins that SAP uses to avoid [DBMS proprietary] temp tables, it is critical that ASE's (or any DBMS) response time be minimized as much as possible.....having ASE yield the core practically as soon as it gets done processing one task (and puts it to sleep pending an IO) just really causes things to run slow.   Think of a typical query that returns 10 rows - say wide enough that each row fills 1 packet.   If the packet transmit time (and client ACK) takes more than 100 microseconds on CPU (almost a given for network interactions...as clock ticks are in nanoseconds and networking is minimally milliseconds - 1000 microseconds), ASE would yield the CPU every time it sent a packet.    When the client wanted the next packet, the OS would have to wake up the ASE process (an interrupted sleep) which is a nasty heavy weight operation.   Hence it is best for ASE to hang out on the CPU until reasonably sure that nothing more is going to happen very soon....and on current cpus...and having it run for 1-2ms (1000-2000 microseconds) shouldn't be a hardship.     If you created a separate thread pool for batch worker processes, then I could see maybe using a lower idle timeout such as 200 or 250......100 is just plain too low in my mind...it is like saying ASE is expecting an odd query every few seconds vs. a steady workload. Basically at that level, there had better be a task in the ASE job queue or one on the way on the network already, or that engine is going to sleep.
While I state that with regards to ADM540 itself, I have not seen the class (perhaps)...one customer did show me the notebook of a class (ASE Sys Admin) they went to and it was really targeted at non-SAP installations more than SAP installations - from a reality/experience aspect.   Part of the issue with the class the customer showed me was it borrowed liberally from the old SY classes as a starting point, but at the point the class was developed there was not a lot of experience with running SAP installations on ASE to really point out the fine tweaking areas such as idle timeout.
However, the document was really aimed primarily at Business Suite vs. BW systems or a Solution Manager install (which are much smaller) - there are a lot of other considerations for BW the guide doesn't get into - although some of the sizing is a better start than the defaults provided by SAPINST
The former runtime guide essentially was just merged in to the Post-Migration Steps section.
May do a quick refresh in the near-future (due to some recent experiences), so if you have other specific examples of the text and SQL not aligning - please let me know.

Best practice - classes folders from components

Hi all,
I have a question regarding which would be the best practice for the following scenario:
I have a customer, multiple components have to be developed(including java custom components), how does it make sense better:
to have one classes folder for all the components(maybe another component specially build just for making that classes folder available to the rest of the components), or each component with its classes folder. Which would fit best from the development point of view, and from the CS point of view(loading resources, priority, order etc.) ?
What problems could appear?
Hope I made myself understandable!
regards,
Vlad

In my opinion, I would go the route of having each component with their own classes folder. It's cleaner and you don't have to worry about having dependent features/components (advanced build settings). If you distribute/reuse it (the whole point of custom components), you don't have to worry about remembering to include any dependents either. Plus, who knows how reliable un/installing components with dependent features/components is. Most components I've seen don't have any dependents. Lastly, I'm a believer in knowing exactly which classes a component uses. I hate having to sift through classes that, in the end, aren't even used by the component.
The only real reason I can see having a separate component that stores all your classes is if they are HUGE and taking up valuable disk space, and if multiple components use those same classes.
Hope this helps.

Best practice to rendering components in latest jDEV 11.1.1.3

Similar Messages

Maybe you are looking for