Best practice for initializing objects in a JSF backing bean?

Hi,
What is the best practice for initializing some objects in the JSF to-page backing bean before the to-page is displayed for the first time? The initialization would vary and depend upon a command link in the from-page.
Regards,
Al Malin

f:view has two new attributes in 1.2: beforePhase and afterPhase
which allows you to specify a phase listener method
which will be called before and after the view is processed.

Similar Messages

Best practices for initial data loads to MDM

Hi,
We need to load more than 300000 vendors from SAP into MDM production repository. Import server might take days to load that much if no error occurs.
Are there any best practices for initial loads to MDM available? What considerations must be made while doing the initial loads.
Harsha

Hello Harsh
With SP05 patch1 there is a file aggregation functionality in the import port. Is is supposed to optimize the import performance.
BTW, give me your mail address and I will send you an idoc packaging paper for MDM.
Regards,
Goekhan

Best Practice for Initial Load Data

Dear Experts,
I would like to know the best practices or factors to be concerned when performing initial load
For example,
1) requirement from business stakeholders for data analysis
2) age of data to meet tactical reproting
3) data dependency crossing sap modules
4) Is there any best practice for loading master data?

HI ,
check this links
Master Data loading
http://searchsap.techtarget.com/guide/allInOne/category/0,296296,sid21_tax305408,00.html
http://datasolutions.searchdatamanagement.com/document;102048/datamgmt-abstract.htm
Regards,
Shikha

Best Practice for Initial Load

Hello,
what is the best way of doing the initial load? is there a best practice somwhere that tells you what should be imported first?
I want to understand the order ex,
1. load Lookups,
2. Hierarchies,
3. taxonomy and attributes
last the main table
etc...
I dont understand the logic.
Thanks in advance

Hi Ario,
If you follow any SAP Standard business content for MDM Repositories like e.g. Material.
https://websmp130.sap-ag.de/sap/support/notes/1355137
In the SAP Note attachments, you will get MDM71_Material_Content.pdf
You will see Import of reference Data(look up table's data) 1st(step6) before import of Master data(step7).
During Import of Reference Data(look up data), Please follow the Import Sequence by using Processing level 0,1,2 etc.
Which take care of filling look up flat tables first then filling Hierarchies tables etc.
After that if you are maintaining Taxonomy, You need to fill taxonomy table in Taxonomy mode of Data Manager, in the sequence (Categories, Attributes, Linkage between Attributes and Categories and lastly Attribute Values)
After this I mean populating Reference data you need to populate Main table records along with tuples table data since now in MDM 7.1 Tuple has been replaced by Qualified table for most of the Master's but if you are still maintaining Qualified table you can import Mani table data along with Qualified table in a single step. Otherwise for Qualified table you can alos use this approach of populating Non-qualifeirs to Qualified table first before importing main table and then importing Main table data along with Qualifier's field of Qualified table.
This above entire process for exporting data from SAP R/3 system to MDM. If you are importing data into MDM from legacy system (Non-Sap systems too), Approach should be remain same Populating Lookup tables data and lastly main table data.
I dont understand the logic.
The logic is simple in your main table you have fields which are look up to Reference tables( e.g. field in main table which are look up to Lookup flat tables like Countries, Currencies etc, field in main table which is lookup to Hierarchy/Taxonomy table etc). So, if these values are not populated firstly, so during your Main table import you will have incomplete data for all of these fields from main table which are look up to some other tables as values in your lookup table you haven't populated before Main table import.
Kindly revert if you still have any doubts.
Regards,
Mandeep Saini

Best Practices for Initial Setup

Hi, I'm going to be helping a friend setup his new Time Capsule and Airport Express for his home network. I've been following some of the threads here about the nightmare problems some people are having with speed, connectivity, reliability, etc.
So I was thinking it might be helpful to have a list of steps to take among setting up that might avoid some pitfalls. Feel free to add stuff not mentioned.
1) Should firmware be updated first? What is current version?
2) Would doing a '7-Pass Erase' on the TC first potentially avoid some issues (seems like this has helped some folks)?
3) If you plan on storing other data on the TC yourself (not a TM backup), do you need to partition the drive first? What is the best method for this? Would this have any potential on slowing TM backups?
4) What is best method for determining best channel to set TC to? (ie, are there ways to test?)
5) Should you perform initial TM backups from each computer over ethernet before attempting wireless?
6) What tools are there to accurately check your wifi and/or file transfer performance? Are there listed standards that a good working TC 'should' be to compare against.
THANKS in advance. I'm trying to help them avoid some of the pitfalls people have encountered. Hopefully this can help others as well.

1) I would update first Airport Utility is 5.3.2 and firmware 7.3.2
2) not needed is over kill
3) partition is a waste of valuable space, Airport Utility is not going to do that; you'll need to pull the drive and do it then you'll run into unusual problem over the long term.
4) jump by at least 6

Best Practice for initial data

When installing a database onto a new server, I do not know what is the best solution to populate the database with the initial data that needs to exist before I can start running. I have sql scripts that take care of creating the tables, constraints, and triggers, but what is the best way to populate the database with my data?
I think that writing sql inserts seem a little complicated and writing a free standing program to interface with the database would take a little longer than I want. Is there a tool available to do my initial population?
Thanks in advance.

I have similar situation to yours where I have to install the database with starting data. What I have done to make this process easier is that I have set up a schema that is an exact replica of what is out in production. This schema has all of the required data in which the application needs to order to be functional. I keep this schema updated with all changes. When the time comes to create another database I just export this schema and import it into the new database. The seed data is small so the export is small as well. This approach has saved me a lot of time in the new deployments.

What is the recommended 'Best Practice' for retaining object instances

I have a window that is constructed in Interface Builder such that the 'File Owner' points to an instance of one of my classes. In this particular case, the entire interaction is between the window and the class instance (which has a file opened to a serial device with a radio at the other end which is being controlled).
Thee are other components of the application that have no interest in what goes on between the window and my class instance.
I'm also using 'garbage collection' memory management.
I can create the class instance which creates the window from the XIB definition and this works well. My understanding of what is happening in the background is that the application is keeping a reference to the window which in turn is keeping the 'File Owner' reference to my class instance. As long as the window is open, my class instance is also kept alive.
Now to my question: Is it OK to rely on this mechanism to keep my class instance alive, or should I also be retaining a pointer to my class instance from some other part of my program myself?
Thanks
Susan

Aussie Susan wrote:
Thanks for this etresoft - I've always maintained my own pointers, but an 'accident' while I was debugging some code (where I didn't set my own pointer but the class instance still remained, I'm assuming because of this mechanism) got me thinking as to whether this was a mechanism that could be relied on.
If you do some research on exactly how you are doing those connections, it may be safe. For example, when you call "NSThread detachNewThreadSelector:toTarget:withObject:" with a target of self, you can immediately release self because the thread will retain the pointer to self. When the thread goes away, the object that spawned it will be released. This is very handy.
I only do this because the documentation explicitly says this is what happens. In your case, I'm not so sure because you are dealing with Interface Builder elements such as the Window class. I'm not entirely sure what happens with a "one shot" window. There are details and options in Interface Builder that could impact your pointer lifetimes. It is safe only if you do the research and prove to yourself it is safe.
I only mentioned the garbage collection aspect because I knew that the retain/release calls do nothing (thanks for the reminder Orangekay) and I've stopped using them in my code. However, I wanted to avoid the "your instance will stay around until you 'release' it" answer.
You might want to consider leaving them in. If you leave them in, then the same code can be used in a non-garbage collected environment.

JSF - Best Practice For Using Managed Bean

I want to discuss what is the best practice for managed bean usage, especially using session scope or request scope to build database driven pages
---- Session Bean ----
- In the book Core Java Server Faces, the author mentioned that most of the cases session bean should be used, unless the processing is passed on to other handler. Since JSF can store the state on client side, i think storing everything in session is not a big memory concern. (can some expert confirm this is true?) Session objects are easy to manage and states can be shared across the pages. It can make programming easy.
In the case of a page binded to a resultset, the bean usually helds a java.util.List object for the result, which is intialized in the constructor by query the database first. However, this approach has a problem: when user navigates to other page and comes back, the data is not refreshed. You can of course solve the problem by issuing query everytime in your getXXX method. But you need to be very careful that you don't bind this XXX property too many times. In the case of querying in getXXX, setXXX is also tricky as you don't have a member to set. You usually don't want to persist the resultset changes in the setXXX as the changes may not be final, in stead, you want to handle in the actionlistener (like a save(actionevent)).
I would glad to see your thought on this.
--- Request Bean ---
request bean is initialized everytime a reuqest is made. It sometimes drove me nuts because JSF seems not to be every consistent in updating model values. Suppose you have a page showing parent-children a list of records from database, and you also allow user to change directly on the children. if I hbind the parent to a bean called #{Parent} and you bind the children to ADF table (value="#{Parent.children}" var="rowValue". If I set Parent as a request scope, the setChildren method is never called when I submit the form. Not sure if this is just for ADF or it is JSF problem. But if you change the bean to session scope, everything works fine.
I believe JSF doesn't update the bindings for all component attributes. It only update the input component value binding. Some one please verify this is true.
In many cases, i found request bean is very hard to work with if there are lots of updates. (I have lots of trouble with update the binding value for rendered attributes).
However, request bean is working fine for read only pages and simple binded forms. It definitely frees up memory quicker than session bean.
----- any comments or opinions are welcome!!! ------

I think it should be either Option 2 or Option 3.
Option 2 would be necessary if the bean data depends on some request parameters.
(Example: Getting customer bean for a particular customer id)
Otherwise Option 3 seems the reasonable approach.
But, I am also pondering on this issue. The above are just my initial thoughts.

Best practice for linking fields from multiple entity objects

I am currently transitioning from PHP to ADF. I'm looking for the best practice for linking data from multiple entity objects.
Example:
EO 'REQUESTS' has fields: req_id, name, dt, his_stat_id, her_stat_id
EO 'STATUSES' has fields: stat_id, short_txt_descr
'REQUESTS' is linked to EO 'STATUSES' on: STATUSES.stat_id = REQUESTS.his_status_id
'REQUESTS' is also linked to EO 'STATUSES' on: STATUSES.stat_id = REQUESTS.her_status_id
REQUESTS.his_status_id is independent of REQUESTS.her_status_id
When I create a VO for REQUESTS, I want to display: REQUESTS.name, REQUESTS.dt, STATUSES.short_txt_descr (for his_stat_id), STATUS.short_txt_descr (for her_stat_id)
What is the best practice for accomplishing this? It appears I could do it a few different ways:
1. Create the REQUESTS VO with a LOV for his_stat_id and her_stat_id
2. Create the REQUESTS VO with the join to STATUSES performed within the query for the VO. This would require joining on the STATUSES EO twice (his_stat_id, her_stat_id)
3. I just started reading about View Links - would that somehow do what I'm looking for?
I also need to be able to update his_status_id and her_status_id through the by selecting a STATUSES.short_txt_descr from a dropdown.
Any suggestions on how to approach such a stupidly simple task?
Using jDeveloper 11.1.2.2.0 if that makes a difference in the solution.
Thanks ahead of time,
CJ

CJ,
I vote for solution 1 as it's just your use case. As you said you what to update the his_status_id and her_status_id through the by selecting a STATUSES.short_txt_descr by a drop down. This is exactly the LOV solution.
ViewLinks are used fro master detail navigation (which you don't do here) and Joining the data make it difficult to update (and you still need a LOV for the drop down box.
Timo

Best Practices For Portal Content Objects Transport System

Hi All,
I am going to make some documentation on Transport Sytem for Portal content objects in Best Practices.
Please help in out and send me some documents related to SAP Best Practices for transport for Portal Content Objects.
Thanks,
Iqbal Ahmad
Edited by: Iqbal Ahmad on Sep 15, 2008 6:31 PM

Hi Iqbal,
Hope you are doing good
Well, have a look at these links.
http://help.sap.com/saphelp_nw04/helpdata/en/91/4931eca9ef05449bfe272289d20b37/frameset.htm
This document, gives a detailed description.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f570c7ee-0901-0010-269b-f743aefad0db
Hope this helps.
Cheers,
Sandeep Tudumu

Best practice for declaring and initializing String?

What is the best practice for the way Strings are declared in a class?
Should it be
private String strHello = "";
or should I have the initialization in the constructors?

The servlet constructor is usually called once, when the servlet is first accessed. But then again maybe something else happens, google servlet life cycle if you must know.
But let's take a step backwards here. It seems like you are trying to put fields into servlets. Don't do that. When two users fetch the servlet's URL at the same time, the fields are shared between the two hits. If you store something like HTTP parameters in the fields, the two hits' parameters will get mangled. The hits can end up seeing each other's parameter values.
The best way is not to have fields in servlets. (Except maybe "static final" constants, sometimes rarely something else.) Many concurrency worries go away, servlet life cycle worries go away, servlet constructors go away, init() usually goes away.

Seeking advice on Best Practices for XML Storage Options - XMLTYPE

Sparc64
11.2.0.2
During OOW12 I tried to attend every xml session I could. There was one where a Mr. Drake was explaining something about not using clob
as an attribute to storing the xml and that "it will break your application."
We're moving forward with storing the industry standard invoice in an xmltype column, but Im not concerned that our table definition is not what was advised:
--i've dummied this down to protect company assets
CREATE TABLE "INVOICE_DOC"
   (     "INVOICE_ID" NUMBER NOT NULL ENABLE,
     "DOC" "SYS"."XMLTYPE" NOT NULL ENABLE,
     "VERSION" VARCHAR2(256) NOT NULL ENABLE,
     "STATUS" VARCHAR2(256),
     "STATE" VARCHAR2(256),
     "USER_ID" VARCHAR2(256),
     "APP_ID" VARCHAR2(256),
     "INSERT_TS" TIMESTAMP (6) WITH LOCAL TIME ZONE,
     "UPDATE_TS" TIMESTAMP (6) WITH LOCAL TIME ZONE,
      CONSTRAINT "FK_####_DOC_INV_ID" FOREIGN KEY ("INVOICE_ID")
             REFERENCES "INVOICE_LO" ("INVOICE_ID") ENABLE
   ) SEGMENT CREATION IMMEDIATE
INITRANS 20
TABLESPACE "####_####_DATA"
       XMLTYPE COLUMN "DOC" STORE AS BASICFILE CLOB (
TABLESPACE "####_####_DATA" XMLTYPE COLUMN "DOC" STORE AS BASICFILE CLOB (
TABLESPACE "####_####_DATA" ENABLE STORAGE IN ROW CHUNK 16384 RETENTION
NOCACHE LOGGING
STORAGE(INITIAL 81920 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT))
XMLSCHEMA "http://mycompanynamehere.com/xdb/Invoice###.xsd" ELEMENT "Invoice" ID #####"
{code}
What is a best practice for this type of table? Yes, we intend on registering the schema against an xsd.
Any help/advice would be appreciated.
-abe

Hi,
I suggest you read this paper : Oracle XML DB : Choosing the Best XMLType Storage Option for Your Use Case
It is available on the XML DB home page along with other documents you may be interested in.
To sum up, the storage method you need depends on the requirement, i.e. how XML data is accessed.
There was one where a Mr. Drake was explaining something about not using clob as an attribute to storing the xml and that "it will break your application."I think the message Mark Drake wanted to convey is that CLOB storage is now deprecated and shouldn't be used anymore (though still supported for backward compatibility).
The default XMLType storage starting with version 11.2.0.2 is now Binary XML, a posted-parsed binary format that optimizes both storage size and data access (via XQuery), so you should at least use it instead of the BASICFILE CLOB.
Schema-based Binary XML is also available, it adds another layer of "awareness" for Oracle to manage instance documents.
To use this feature, the XML schema must be registered with "options => dbms_xmlschema.REGISTER_BINARYXML".
The other common approach for schema-based XML is Object-Relational storage.
BTW... you may want to post here next time, in the dedicated forum : {forum:id=34}
Mark Drake is one of the regular user, along with Marco Gralike you've probably seen too at OOW.
Edited by: odie_63 on 18 oct. 2012 21:55

Best practices for connecting to DB

Hi,
I am having 3 different java classes which will contact the DB for getting the data from the table. I wrote a separate java class for DB connection like this :
public class DBConnection {
private Connection con;
public Connection getConnection() {
try {
Class.forName("org.apache.derby.jdbc.ClientDriver");
con = DriverManager.getConnection("jdbc:derby://localhost:1527/StrutsDB", "username", "password");
} catch (SQLException ex) {
Logger.getLogger(DBConnection.class.getName()).log(Level.SEVERE, null, ex);
} catch (ClassNotFoundException ex) {
Logger.getLogger(DBConnection.class.getName()).log(Level.SEVERE, null, ex);
return con;
How to use this single connection object in all of the 3 classes? What are all the ways of doing so?
Is there any best practices for connecting to DB?
Thanks in advance,

The problem with "best practice" is it really depends on your situation. If you are creating a single user, desktop application then what you are doing will work but would be more efficient if the connection was declared as static and you used the singleton pattern.
public class DBConnection {
    private static final Connection con;
    private DBConnection() {
        try {
            Class.forName("org.apache.derby.jdbc.ClientDriver");
            con = DriverManager.getConnection("jdbc:derby://localhost:1527/StrutsDB", "username", "password");
        } catch (SQLException ex) {
            Logger.getLogger(DBConnection.class.getName()).log(Level.SEVERE, null, ex);
        } catch (ClassNotFoundException ex) {
            Logger.getLogger(DBConnection.class.getName()).log(Level.SEVERE, null, ex);
    public static Connection getConnection() {
        return con.
}The private constructor guarantees only one instance of the class will be created (since you can't use 'new' to create one) and initialized the database connection. Then any other object that require a connection simply call DBConnection.getConnection() and they will get the same database connection each time.
Note that this is a little simplistic and is not thread safe. If your classes will be executing on different threads you will need a more sophisticated approach. You will also need to make sure you commit or rollback any transactions when done or the next time you get the connection you may be in the middle of an existing transaction.

Best practice for multi-language content in common areas

I've got a site with some text in header/footer/nav that needs to be translated between an English and Spanish site, which use the same design. My intention was to set up all the text as content to facilitate. However, if I use a standard dialog with the component's path set to a child of the current page node, I would need to re-enter the text on every page. If I use a design dialog, or a standard dialog with the component's path set absolutely, the Engilsh and Spanish sites will share the same text. If I use a standard dialog with the component's path set relatively (eg path="../../jcr:content/myPath"), the pages using the component would all need to be at the same level of the hierarchy.
It appears that the Geometrixx demo doesn't address this situation, and leaves copy in English. Is there a best practice for this scenario?

I'm finding that something to the effect of <cq:include path="<%= strCommonContentPath + "codeEntry" %>" resourceType ...
works fine for most components, but not for parsys, or a component containing a parsys. When I attempt that, I get a JS error that says "design.path is null or not an object". Is there a way around this?

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

Best practice for initializing objects in a JSF backing bean?

Similar Messages

Maybe you are looking for