WebSphere Commerce common interview Questions.
1) Difference between static and dynamic include?
Ans: The syntax for
static include is <%@ include file=”filename.jsp” %>
dynamic include is <jsp:include page=”filename.jsp” />
Static include is an inline inclusion (the contents of the file will be included at translation phase) like a copy and paste. During the translation or compilation phase all the included JSP pages are compiled into a single Servlet. Use “static includes” when a JSP page does not change very often.
In case of dynamic include the response of the file will be included to the original response at runtime. The file will be processed separately and only the response will become the part of the original files’ response. The dynamically included JSP is compiled into a separate Servlet. It is a separate resource, which gets to process the request, and the content generated by this resource is included in the JSP response.
Static include cannot accept a parameter . But dynamic include can accept a parameter.
2) What is opt counter column significance in commerce tables?
Ans: WebSphere Commerce uses an optimistic locking scheme that allows the database transaction isolation level to be lowered from repeatable read to read committed. Using that scheme, database rows not normally accessed concurrently are not locked with an intent to update when they are read. Instead, when the update is eventually made, the row is checked to make sure it has not been updated concurrently since it was read. If it has been updated concurrently, then the transaction is rolled back and the command may be restarted from the beginning in a new transaction, if appropriate.
In this scheme, performance is improved when concurrent updates do not normally occur, because the relatively expensive process of obtaining the database locks with intent to update is avoided. On the other hand, for those operations where concurrent updates are more likely to occur, pessimistic locking, whereby intent to update locks are obtained when the row is read, continues to be used, thus avoiding the more expensive process of rolling back and re-starting from the beginning in a new transaction.
Refer Link: Read Full Info
3) Difference between controller command and task command?
In commerce controller commands and task commands follows "Command Design Pattern". Request may come from different applications or diff sources. All requests are handled by the controller layer and translated into a common format then it can be understood by commerce server commands. Based on the design pattern commerce implements controller and task commands.
1) Difference between static and dynamic include?
Ans: The syntax for
static include is <%@ include file=”filename.jsp” %>
dynamic include is <jsp:include page=”filename.jsp” />
Static include is an inline inclusion (the contents of the file will be included at translation phase) like a copy and paste. During the translation or compilation phase all the included JSP pages are compiled into a single Servlet. Use “static includes” when a JSP page does not change very often.
In case of dynamic include the response of the file will be included to the original response at runtime. The file will be processed separately and only the response will become the part of the original files’ response. The dynamically included JSP is compiled into a separate Servlet. It is a separate resource, which gets to process the request, and the content generated by this resource is included in the JSP response.
Static include cannot accept a parameter . But dynamic include can accept a parameter.
2) What is opt counter column significance in commerce tables?
Ans: WebSphere Commerce uses an optimistic locking scheme that allows the database transaction isolation level to be lowered from repeatable read to read committed. Using that scheme, database rows not normally accessed concurrently are not locked with an intent to update when they are read. Instead, when the update is eventually made, the row is checked to make sure it has not been updated concurrently since it was read. If it has been updated concurrently, then the transaction is rolled back and the command may be restarted from the beginning in a new transaction, if appropriate.
In this scheme, performance is improved when concurrent updates do not normally occur, because the relatively expensive process of obtaining the database locks with intent to update is avoided. On the other hand, for those operations where concurrent updates are more likely to occur, pessimistic locking, whereby intent to update locks are obtained when the row is read, continues to be used, thus avoiding the more expensive process of rolling back and re-starting from the beginning in a new transaction.
Refer Link: Read Full Info
3) Difference between controller command and task command?
In commerce controller commands and task commands follows "Command Design Pattern". Request may come from different applications or diff sources. All requests are handled by the controller layer and translated into a common format then it can be understood by commerce server commands. Based on the design pattern commerce implements controller and task commands.
- Controller commands
- These implement business tasks such as user registration and allocation of inventory. Use these to implement high-level process logic for the business task.
- Task commands
- These implement discrete pieces of a business task such as address verification or ensuring passwords comply to the defined password policies. For example, during executing of the Registration controller command a callout may be made to a task command to validate the address entered.
- Refer this Link for detailed information
Common Questions :
- what is the smart databean? need for that.
- what is use of punchouts? can we use punchouts in B2c ? how to configure them ?
- Do you involved in creating Data Load? How to load data?
- what’s the role for you in project and sub systems you worked?
- What’s are the main tables in member subsystem?
- If we create a user what are all the tables gets effected? or register?
- If we want save Address/ how can we maintain multiple addresses ?
- why refreshcopyhelper() and commitcopyhelper() needed. what it will do.
- what are all the catalog tables you worked?
- Relation ship between catalog? where we will store attributes and attribute values?
- Can we use task command in Jsp?
- what are all the tables in promotion? use of calcode table?
- why we use access control policies? where we maintain it?
- can we restrict a user from accessing a particular controller command?
- what is the significance of cmdreg table?
More Interview Questions :
- What are the different types of members? Diff between member and user?
- Have can you restrict access to groups? Where can you define it.
- Have you been part of integration with other systems? Types of other systems you used.
- How can we maintain different implementations for store?
- What is the need for task command however we have Controller command, so why cant we use controller instead of task command?
- Does task command return response properties like controller command?
- Have you worked Multi lingual stores. Like if we have a new store for japan, so how can we publish a store with new language.
- Scenario: On the product level if we need to display a text box where user can enter a text, that text has to be saved against the product for that user, On the checkout page the same text has to appear for that added product/item as a non editable text.
- What are the commands you need to customize? Can you name them.
- Promotion tables? How the promotion works? On which promotions you worked.
- Have you published store? .sar files?
- What are all the tables you aware of Order sub system? Which tables you worked on Order sub systems?
No comments:
Post a Comment