Websphere commerce server faq

  • View

  • Download

Embed Size (px)


Websphere commerce server faq

Text of Websphere commerce server faq

  • 1. What is WAS Provides the infrastructure for running applications that run your business. Common environment and programming model for your applications.Platform for developing and Deploying web services and SOA based apps Secure, Scalable, reliable transaction engine for ERP IBM WebSphere is architected to enable you to build business-critical applicationsfor the Web WebSphere includes a wide range of products that help you develop and serveWeb applications. They are designed to make it easier for clients to build, deploy, and managedynamic Web sites more productively WAS implements J2EE specificationWebSphere Application Server provides the environment to run your Web-enabled e-businessapplications. An application server functions as Web middleware or a middletier in a three-tier e-business environment. The first tier is the HTTP server thathandles requests from the browser client. The third tier is the business database (forexample, DB2 UDB for iSeries) and the business logic (for example, traditionalbusiness applications, such as order processing). The middle tier is WebSphereApplication Server, which provides a framework for a consistent and architected linkbetween the HTTP requests and the business data and logic.

2. With the Base and Express packages, you are limited to single application serverenvironments. The Network Deployment package allows you to extend thisenvironment to include multiple application servers that are administered from asingle point of control and can be clustered to provide scalability and high availabilityenvironments.The typical application flow is as follows:1. A Web client requests a URL in the browser (input page).2. The request is routed to the Web server over the Internet.3. The Web server immediately passes the request to the Web server plug-in.All requests go to the Web server plug-in first.4. The Web server plug-in examines the URL, verifies the list of host namealiases from which it will accept traffic based on the virtual host information,and chooses a server to handle the request.5. A stream is created. A stream is a connection to the Web container. It ispossible to maintain a connection (stream) over a number of requests. TheWeb container receives the request and, based on the URL, dispatches it tothe proper servlet.6. If the servlet class is not loaded, the dynamic class loader loads the servlet(servlet init(), then doGet() or doPost()).7. JNDI is used for lookup of either datasources or EJBs required by the servlet.8. Depending upon whether a datasource is specified or an EJB is requested,the JNDI directs the servlet: To the corresponding database and gets a connection from its connection 3. pool in the case of a data source. To the corresponding EJB container, which then instantiates the EJB whenan EJB is requested.9. If the EJB request involves an SQL transaction, it goes back to the JNDI tolook up the datasource.10.The SQL statement is executed and the retrieved data is sent back either tothe servlet or to the EJB.11.Data beans are created and handed off to JSPs in the case of EJBs.12.The servlet sends data to JSPs.13.The JSP generates the HTML that is sent back through the plug-in to the Webserver.14.The Web server sends the output page (output HTML) to the browser.Functionality of WASWebSphere Application Server supports asynchronous messaging through the useof a JMS provider and its related messaging system.(JMS 1.1 MessagingProvider)WebSphere Application Server provides authentication and authorizationcapabilities to secure administrative functions and applications, using LDAPWebSphere Application Server works with a Web server (such as the IBM HTTPServer) to route requests from browsers to the applications that run inWebSphere Application Server. Web server plug-ins are provided forinstallation with supported Web browsers. The plug-ins direct requests to theappropriate application server and perform workload balancing among serversin a cluster.Web services enable businesses to connect applications to other businessapplications, deliver business functions to a broader set of clients andpartners, interact with marketplaces more efficiently, and create new businessmodels dynamically.Delivers a high performance and extremely scalable transaction engine fordynamic e-business applicationsPackagingWebSphere Application Server is available in multiple packaging options.WebSphere Application Server - Express V6.0 Single Server environment.(No Clustering or multi server management) J2EE 1.4 supportMedium-sized business 4. Contains Rational Web Developer application tool Doesnt handle EJB and JCA Limited to 2 CPUsWebSphere Application Server V6.1 (Base)Slightly differs in packaging and licensing Contains Application Server toolkit Includes a trial version of Rational Application DeveloperUnlimited CPUsWebSphere Application Server Network Deployment V6Extends Base versionClustering capabilitiesEdge Components which provide high performance and availability (Caching Proxyand Load Balancer)HA for distributed configurationsLarge Enterprise applicationsScalability, Availability and PerformanceWeb Server plug-in supports weighted WLMAll V6 application servers have the same core and base functionalityWebSphere Application Server - Express V6 node can be upgraded to a WebSphereApplication Server V6 node(.Can be done without any software upgrades .Only apaper license upgrade is required)WebSphere Application Server- Express V6 and WebSphere Application Server V6node can be federated into a WebSphere Application Server - Network DeploymentV6 cell (Can be done without any software upgrades .Only a paper license upgrade isrequired)Differences b/n WAS VersionWAS 5: J2EE 1.2/1.3 supportJDK 1.3 supportWeb Services based on Apache engineWAS 6.0: J2EE 1.2/1.3/1.4 supportJDK 1.4 support (JDK 1.4.2)Web Services based on J2EE 1.4High Availability ManagerJava Based Messaging Engine 5. EJB 2.1, JMS 1.1, JCA 1.5, Servlet 2.4, and JSP 2.0Supports Java Server Faces (JSF)Creates Archive of the existing WAS configurations and the archive canbeused to create new configurations.Profiles and all profiles use same WebSphere binaries(Less storage)Node groupsService integration functionality provides both message-oriented andserviceOriented applicationsWAS 6.1: J2EE 1.2/1.3/1.4 supportJDK 5.0 supportJSF-a framework for Web applicationsIntegrated ConsoleSecurity changesSecure and Scalable runtimeEdge ComponentsUsing Edge components can reduce Web server congestion, increase contentavailability, and improve Web server performance. As the name indicates, Edgecomponents usually run on machines that are close (in a network configurationsense) to the boundary between an enterprises intranet and the Internet.Web containerA Web container, which processes HTTP requests, servlets, and JavaServer Pages(JSPs) Web container transport chains:Requests are directed to the Web container using the Web container inboundtransport chain. The chain consists of a TCP inbound channel that provides theconnection to the network, an HTTP inbound channel that serves HTTP 1.0 and 1.1requests, and a Web container channel over which requests for servlets and JSPs aresent to the Web container for processing Servlet processingWhen handling servlets, the Web container creates a request object and a responseobject, then invokes the servlet service method. The Web container invokes theservlets destroy method when appropriate and unloads the servlet, after which theJVM performs garbage collection. HTML and other static content processingRequests for HTML and other static content that are directed to the Web containerare served by the Web container inbound chain. However, in most cases, using anexternal Web server and Web server plug-in as a front-end to a Web container ismore appropriate for a production environment. 6. _Session managementSupport is provided for the javax.servlet.http.HttpSession interface as described inthe Servlet application program interface (API) specification._ Web services engineWeb services are provided as a set of APIs in cooperation with the J2EE applications.Web services engines are provided to support Simple Object Access Protocol (SOAP).EJB ContainerThe Enterprise JavaBeans (EJB) container provides all the runtime services that areneeded to deploy and manage enterprise beans. It is a server process that handlesrequests for both session and entity beans.The enterprise beans, packaged in EJB modules, installed in an application serverdo not communicate directly with the server. Instead, the EJB container provides aninterface between the enterprise beans and the server. Together, the container andthe server provide the enterprise bean runtime environment.The container provides many low-level services, including threading andtransaction support. From an administrative viewpoint, the container manages datastorage and retrieval for the contained enterprise beans. A single container can hostmore than one EJB Java archive (JAR) file.WAS ServicesJ2EE Connector Architecture servicesTransaction serviceDynamic cache serviceMessage listener serviceObject Request Broker serviceAdministrative service (Java Management Extensions)Diagnostic trace serviceDebugging serviceName service (Java Naming Directory Interface)Performance Monitoring Interface serviceSecurity service (JAAS and Java 2 security)Service Integration Bus serviceThe Web server:A Web server handles the HTTP protocol. When the Web server receives an HTTPrequest, it responds with an HTTP response, such as sending back an HTML page. Toprocess a request, a Web server may respond with a static HTML page or image,send a redirect, or delegate the dynamic response generation to some other programsuch as CGI scripts, JSPs (JavaServer Pages), servlets, ASPs (Active Server Pages),server-side JavaScripts, or some other server-side technology. Whatever their 7. purpose, such server-side programs generate a response, most often in HTML,