WebSphere Commerce Architecture - Bemol
WebSphere Commerce Architecture1Unit 1:WebSphere Commerce ArchitectureCopyrighted material
Unit Objectives2This unit was designed to enable you to: Start a development project that implements WebSphere Commerce V7. Describe the Runtime architecture of WebSphere Commerce. Describe the development model for WebSphere Commerce. Explain the application of Struts in WebSphere Commerce. Describe the presentation layer for WebSphere Commerce by using bothstandard JSP files and Web 2.0-enabled JSP files. Summarize the Business Logic and Persistence Layers. Describe the benefits of EJBs, Access beans, and the Data Service Layer,and describe what role each plays in persistence. Summarize the elements and utilities available in access control. Explain the development environment and how to effectivelytroubleshoot and debug WebSphere Commerce applications.
Getting Started with WebSphere Commerce V73After completing this topic, you should be able todescribe the: New features and functionality in WebSphereCommerce V7. Programming specifications of WebSphereCommerce V7. Establishing a team and develop a process forimplementing a solution by using WebSphereCommerce V7.
What is new in WebSphere Commerce V7 Multi-channel Precision MarketingMobile CommerceSocial CommerceEfficient data loading utilityStarter Stores that are enabled by Web 2.0 technologyIBM Management Center enhancementsMigration assistance utilitiesDeveloper infrastructure improvements4
Programming Specifications5 WebSphere Commerce Version 7.0 uses a number of programmingspecifications: Dojo 1.3.1EJB Version 2.1EMF Version 2.2JavaMail 1.4JAX-RPC 1.1JEE 5JDK and JRE Server and Client Tools 1.6JMS 1.1JSP support (from WebSphere Application Server) 2.1OpenLaszlo 4.2.0.3SDO 2.0Struts 1.2.9Sun Java Servlet Version 2.5XMLXSD 1.1XSTL
Development Process: The Development CycleStage 1: ModelGather requirements, design, simulate,and optimize business modelsTeam: Architects, Business Analysts6Stage 2: AssembleDiscover, assemble, testTeam: Architects, ProjectManagers, Development teamsStage 4: ManageBusiness monitoring forco-ordinated interaction,analytics, and optimizationTeam: Architects,AdministratorsStage 3: DeployIntegrated deployment of processesTeam: Project Managers,Administrators Copy right
WebSphere Commerce Architecture7After completing this topic, you should be able to describethe: WebSphere Commerce V7 Runtime architecture. WebSphere Commerce V7 Application Layers. The WebSphere Commerce V7 Runtime. Core components of WebSphere Commerce. Multi-channel support in WebSphere Commerce V7. Framework interactions in the Web channel. Copy right
WebSphere Commerce Runtime Architecture8 Copy right
WebSphere Commerce Application Layers Business models9 Represents a sample business situation ordescribes a scenario.Business processes Represents sample business functions andcases.Presentation layer Responsible for displaying results.Serv ice layer Segregates implementation of business logic. Implemented by using OAGi messages.Business logic Implements business rules independent ofthe presentation. Implemented by using a command pattern.Persistence layer Records the data and operations. Represents entities within the Commercedomain. Encapsulates data-centric logic.Database schema Designed specifically for e-commerceapplications. Copy right
WebSphere Commerce V7 Runtime10Presentation LayerStorefrontSales CtrPortalMgmt CtrJSPEclipsePortlets.lzxSales CtrPortletStrutsController LayerStrutsBusiness Logic LayerServices InterfaceNVP cmdsBOD cmdsPersistence LayerAccess beansEJB beansData ServiceLayer Copy right Presentation layer Flexible architecture includesPortal and Management Center. Controller layer Enhanced to include support forPortal and Management Center. Web channel offers support forSDO tag library. Business logic layer Supports NVP commandframework. Supports processing commandsfor BODs. Persistence layer Supports EJB 1.1 – EJB 2.0 Supports component services byusing the Data Service Layer asan abstract, SOA-compatiblepersistence solution over thedatabase.
Core ComponentsWebSphereC ommerceAcceleratorAdministrationC OrganizationAdministrationC onsoleBusinessIntelligenceOrderManagementC onfigurationManagerIBM ManagementC enterC atalogManagementC ustomer ServiceToolsAnalyticsConfigurable Business ProcessesRoles ss Context EngineFoundation andToolsBusinessIntegration11 Copy rightWebSphere Platform
Multi-Channel Support in WebSphere CommerceStrutsPortalSales CtrKioskMgmt CtrOtherWebSphereCommerce Server12 Presentation Layer is decoupledfrom the Business Logic Layerthrough the Services interface. Multiple types of Sales Channelscan be connected to theWebSphere Commerce Server withthe Services interface. Business Logic LayerEach sales channel can support itsown unique architecture. Access to the database from theServices WebSphere Commerce Server isimplied through the PersistenceLayer. Copy right
Presentation Layer13 ServletPortletClient JSPWeb ContainerLibrariesJSPPortlet ContainerWebAppMgmt Center Business Logic LayerEJB Container Copy rightW ebSphere Com merce supports multiplePr esentation Layers Use a n appropriate Presentation Layert h at is based on y our businessr equ irem ents.Bot h t he Struts and Portal PresentationLa y ers follow the Model-View-Controller(MV C) design pattern.In W ebSphere Portal: Br ow ser request that are routed t o acon troller (portlet). Por t let calls client libraries ( Javacla sses). Client library sends a service request forpr ocessing. Por t let dispatches rendered data t o a JSPpa g e in the portlet container. JSP pa ges client libraries tags to r etrieveda t a.In St ruts: Br ow ser request is r outed to a servlett h at acts as a controller. Con troller calls the model for processing Con troller dispatches the appropriatev iew to render data. Model en capsulates all business logic (ascom m ands) . JSP pa ges retrieve data from theda t abase by using Data beans.
Development Layers of WebSphere Commerce14After completing this topic, you should be able todescribe the: Business Logic Layer: Name-value pair processing commandsBOD processing commandsPersistence Layer: Access beans and Enterprise JavaBeansData Service Layer Copy right
Business Logic Layer15 Business Logic Layer supports two methodsof command processing: Traditional name-value pair processing SOA-compliant processing of Business Object Documents (BODs) Both name-value processing and BOD processing Both methods use the WebSphere Commerce command framework Name-value pair processing Controller commands Task commands BOD processing Get, Change, Process, SyncServices interfaceName-valuepair commandprocessingBODcommandprocessing Copy right
Differences in Business Logic Layer Processing (1 of2)16JSPEJB Taskcommandcommandcommand Name-value pair processing: Request for execution fromPresentation Layer. Business token that is passed toBusiness Context service from Databean. Façade calls appropriate controllercommand (or commands) which calltask command (or commands). Controller and task commands callAccess beans which delegate to EJBbeans.AccessBean Copy right
Differences in Business Logic Layer Processing (2of 2)17EJB rControllerBODcommandcommandcommand BOD processing: Request for execution fromPresentation Layer in SDO format. Leverages Business Context service. Pre-built BOD processing commands. Commands call Data Service Layer toaccess database.Data servicefaçadeBOMservicePhys. Obj.PersistenceData Service Layer Copy right
Data Service Layer18 Abstraction for data access Independent of the physical schema Purpose: Functions independent of the framework. Transforms data that is retrieved fromdatabase into Java objects (implemented asSDO). Offers bidirectional transformation betweenphysical SDOs (schema) and logical SDO(classes). Allows user to perform CRUD operations onphysical or logical SDOs. Services of the DSL: Data service façade: Interface foraccessing data. Business object mediation: Initializesclasses (mediators) that transform physicalto logical data. Physical object persistence: Providesmediators access to physical data, translatingXPath to SQL. Copy calobjectpersistence
Subsystem Data Models in WebSphereCommerce Catalog Catalogs, categories, products,attributes, groupings Marketing Promotions, rules server, productadvisor, WebSphere CommerceAnalyzer Member Access control, authentication,member (participants) Order management ATP, calculation, pricing, payment,procurement store, shipping, tax System Collaboration, command, flow,scheduler, messaging, system, usertraffic19 Payment Tables that are related to theWebSphere Commerce PaymentsMultipayment framework and thePayments subsystem. Workspaces Relationship of database tables thatare used in workspace. Gift Center (optional) Relationship of database tablespertinent to the IBM Gift Centerapplication. Store Locator (optional) Search (optional) Search Engine optimization Trading Auctions, contract, RFQ Copy right
WebSphere Commerce Supporting Services20After completing this topic, you should be able todescribe the: Purpose and function of the Business Contextservice. Purpose and function of Web services in WebSphereCommerce. Basics of security and access control. Copy right
Business Context Services Business contexts Contexts establish an executionenvironment that affects theoutput of a businesscomponent. Contexts are not directlyinvoked by clients; businesscomponents use theinformation present in acontext to fulfill operations. Benefits Enablement of genericcomponents. Tailored content andexperience. Precisely targeted offers. Enforcement of businesspolicies. Appropriate prices,entitlements, and terms for aparticular user.21 Copy right
Web Services in WebSphere CommerceWeb serviceclientWebSphere Commerce Server22WebSphere CommerceWeb service lient codeBusinesslogicfaçade WebSphere Commerce as aservice provider: JSPcomp.serviceWeb service controller Webserviceengine Copy rightEnabling business operationsas externally accessible Webservices makes WebSphereCommerce a service provider.Web service deploymentmodels usually have a centralserver with published WSDLdefining the services.External clients, Webapplications, or rich clientapplications connect to thecentral server and invokeservices that are defined by thepublicly available WSDL.
Advantages of Web Services in WebSphereCommerce23 Uses WebSphere Application Server Web serviceengine: Reuses existing WebSphere Commerce assets: Existing programming modelExisting integration technologyDesigned for customization: Hides the complexity of SOAPXML request message mappingJSP response buildingInbound and outbound Web serviceimplementations. Copy right
Elements of Access Control24 Users People that use the system. Grouped into relevant access groups (UserGroup). Roles are used to determine membership in an access group. Roles are assigned to users on a per organization basis. Actions Activities that Users can perform on a Resource. Actions can be grouped into relevant groups (ActionGroup). Resources Entities, such as JSPs and commands, that are protected Can be grouped into relevant groups (ResourceGroup). Relationships Define connection between Users and Resources (such as Owner,Editor, Reader). Copy right
WebSphere Commerce Feature Pack Updates25After completing this topic, you should be able todescribe the: Catalog programming model updates. WC search enhancements. Sterling/CM integration. Data load updates. Coremetrics Integration. Copy right
Storefront Programming Model and the Goal ofFeature Pack 3 Program model before Feature Pack 3:26 Data beans SOI and SOA-based services.Understand different programming models when usingcatalog services in the store front.Storefront catalog programming model solution inFeature Pack 3: Provide a consistent SOA-based programming model for thestore front .Move store front catalog service that is currently based onJava beans and SOI to SOA.The solution uses the existing WC Search framework and thesearch CatalogNavigationView noun. Copy right
Solution Data tagServiceJSPCatalogNavigationViewNoun Copy rightDatabase
Sterling Configurator Integration28 Provide an end-to-end Dynamic Kits authoring and shoppingflows. Integrate with Sterling Visual Modeler (VM). Allow product managers define models for Dynamic Kits. Integrate with Sterling Configurator (SC) Allow Product Managers to pre-configure Dynamic Kits inManagement Center . Allow shoppers to configure or reconfigure Dynamic Kits from theStorefront. Except the data, product, catalog, and price information for themodel are kept and managed in WebSphere Commerce. Sterling products must be purchased separately. Feature Pack 3 does not support Sterling DOMintegration and Sterling Configurator integrationworking together. Copy right
Enhancements for Sterling Configurator Integration29 Management Center updates: Launch the Visual Modeler and Sterling Configurator withautomatic sign-on. Define models reference for Dynamic Kit. Search and browse model by using integrated Utility view. Create pre-configuration for Dynamic Kit. Manage prices for Dynamic Kits. Storefront enhancements: Show Dynamic Kits in the following area: Catalog pagese-Marketing SpotMerchandising associationsAllow the shopper to configure a Dynamic Kit. Copy right
Sterling Configurator Integration Main Flows30Staging environmentProduction environmentSterling WebSterling WebConfiguratorConfiguratorVisual ModelerCreate new models /create model referenceReconfigurePre-configureManagement CenterStoreShop dynamic kitCreate dynamic kits, pricesStage PropDynamic kit ,Configuration, PriceShopperProduct manager Copy right
Data Load in ReviewIntroduced in V7 to reduce total cost of data loading. Streamline and load data in a single command. 31 CSV file to databaseLoading based on business objects. Benefits: More scalableBetter performanceBusiness rule enforcedBetter diagnostics and error reportingIn V7 business objects supported: CatalogPriceInventory Copy right
Updates to Dataload32Support loading of workspace data by using dataload framework – Feature Pack 1. Support loading of member data by using data loadframework: – Feature Pack 3 PersonOrganizationMemberGroupData load utility command-line support only. Sample member loader mapping configuration andCSV files. Customization tutorial Copy right
Data Load Utility - User Interaction Diagram33 Copy right
Command-line Utilities34 Command-line utilities ideal for messaging command design patternimplementations. txttransform This utility transforms data between a character-delimited format and an XML dataformat. xmltransform This utility transforms XML data into alternative XML formats. dtdgen This utility generates a DTD based on the target database. idresgen This utility generates identifiers for XML elements. massload This utility loads data into the WebSphere Commerce database. fileloader This utility loads managed files into the WebSphere Commerce database massextract This utility extracts data from a database as an XML document. Copy right
Coremetrics Integration35 Integration of Coremetrics andWebSphere CommerceManagement Center. Store Tagging Update: Coremetrics Store tagging API updateSolr search with facet attributesNew cm:element tagNew cm:conversion tag Coremetrics Intelligent Offer integration enhancements: New store function “Enable Intelligent Offer Integration” Flat file import enhancements Intelligent Offer Data Extraction Utility– Coremetrics Profile Segments tool import enhancements. Copy right
Implementing Coremetrics for Commerce36 STEP 1: Apply FP3, Install FEP3, enable store-enhancements,Publish store, and enhancements sar files. STEP 2: Configure site to communicate with Coremetrics. Configure bi-config.xml file STEP 3: Generate Category Definition File to capture cataloghierarchy. STEP 4: Enable pretagged analytics tags in Madisons/Elitestarter stores. STEP 5: [For new stores only] Tag store JSP files with page viewtag. Run auto tagging utility STEP 6: [For new stores only] Tag store pages for Coremetrics. Copy right
Versions of the Coremetrics JavaScript Library37 Standard Coremetrics library: Uses the hosted libs.coremetrics.com/eluminate.js libraryfile version 4.7.4H or later versions that ends with letter HDoes not require hosting a cmcustom.js or cmdatatagutils.jsfile to support WebSphere Commerce customizations.Custom Coremetrics library: Uses an eluminate.js library file version that does not endwith the letter H, for example, version 4.7.4 or 4.7.5Requires site to host a cmcustom.js or cmdatatagutils file tosupport WebSphere Commerce customizations. Copy right
WebSphere Commerce DevelopmentEnvironment38After completing this topic, you should be able to describe the: WebSphere Commerce development environment. Contents of the default workspace. Tools available with WebSphere Commerce Developer. Purpose and function for WebSphere Commerce workspaces. Process for determining problems and troubleshootingWebSphere Commerce. Tiers of WebSphere Commerce for troubleshooting. Logs and trace files with WebSphere Commerce. Function of IBM Support Assistant in maintaining WebSphereCommerce. Copy right
WebSphere Commerce Development Environment Rational Application Developer39V7.5.5.1 Rational ApplicationDeveloper V7.5.5.1 WebSphere CommerceDeveloper V7Note: Rational Software ArchitectV7.5.5.1 can be installed instead ofRational Application Developer.Eclipse-based developmentenvironment. WebSphere Commerce Developer V7 Leverages tools from RationalApplication Developer. Leverages WebSphere ApplicationServer V7 test server. Development database Stores development artifacts. Can be DB2, Oracle, or Apache Derby(default).WCDEV(DB2) Lotus Expeditor V6.2 Optional Used when developing and runningIBM Sales Center for WebSphereLotus Expeditor V6.2Commerce.(IBM Sales Center) Copy right
WebSphere Commerce DevelopmentEnvironment40 Installing WebSphere Commerce V7 Developer provides a fullyconfigured Rational Application Developer workspace. The following projects are included: WC: contains the core WebSphere Commerce EAR file.CommerceAccelerator: contains assets for Commerce Accelerator.LOBT ools: customizable assets for IBM Management Center for WebSphere.CommerceOrganizationAdministration: assets for the Organization AdministrationConsole.SiteAdministration: assets for the Administration Console.Stores: module for sample store assets.WebSphereCommerceServerExtensionsData: create custom enterprisebeans and other data assets.WebSphereCommerceServerExtensionsLogic: create new logic, such asJava classes.WebServicesRouter: create custom Web service assets Copy right
WebSphere Commerce Tools41 WebSphere Commerce Administration Console WebSphere Commerce Organization AdministrationConsole User Administration functions, maintain security.WebSphere Commerce Accelerator Administration functions for maintaining a site or anynumber of stores.User Console for making high-level modifications toStorefronts.IBM Management Center for WebSphere Commerce Suite of tools to support Merchandising and Marketing tasks. Copy right
Workspaces Secure work area for developers to makeand preview changes to managed42assets. Does not affect production environment: Similar to having a private copy of managed production assets. Workspaces offer the following features: Task groups and tasks for dividing work within workspaces. Defined roles for managing workspaces, approvals, and content. Separate tool for creating and administering workspaces. Locking policies to control changes. Various forms of commit and publish. Controls how data is moved from development to production. Copy right
WebSphere Commerce Problem Determination43 Available resources: WebSphere Commerce Information Center: IBM Education Assistant: Supplemental technical information.IBM developerWorks: Provides self-help modules.Offers some voice recordings and visual assistance.Technical documents: Contains migration, installation, configuration information and more.Contains several self-help tutorials.Offers specific examples.Redbooks: Highly technical deep-dives into specific tasks. Copy right
Problem Areas for Examination44 Runtime issue could be anywhere alongthe path: Browser: client side JavaScript, AJAX requests, cookie acceptance, cookie, or URLlimits, pop-ups. Web Server: virtual hosts, SSL certificate, rewrites, redirects, ports. WebSphere Application Server plug-in: mapped modules, cluster, loadbalancing, transports, virtual hosts. Application Server: servlet filters, Commerce servlets, caching. Database: connections, SQL, contention, data itself.BrowserWeb serverApplication server(WebSphere Commerce Server) Copy rightDatabase server
WebSphere Commerce Logs45 Web server log: httpd.conf defines the virtual hosts WebSphere Application Server plug-in: Check the plugin-cfg.xml file Application server and WebSphere Commerce default files: native stderr.log: contains text written to the stderr stream. native stdout.log: contains text written to the stdout stream. startServer.log: written when starting the server. stopServer.log: written when stopping the server. SystemErr.log: any system error while the server is running. SystemOut.log: system output file while the server is running. activity.log: logs continuous activity. trace.log: If trace is enabled, logs the components trace messageswhile the service is running. Copy right
IBM Support Assistant for WebSphereCommerce46 Ties to many key sites such as WebSphere Commerce Zone.Offers problem determination, product flashes, andtechnotes.Alerts user of APARs, fixes, and utilities.News and preventive service planning.Contains: Product documentationPublicationsCommerce newsPreventive service planningUpcoming Webcasts Automated Commerce data collectors. Copy right
IBM Support Assistant Data Collectors47Data collection can be tedious for some components. Automated collectors within ISA help this process: Commerce collectors are one aspect of the Commerce plug-indownload for ISA.In-line with Commerce “MustGather” documents forIBM Support. Other products include WebSphere Application Server, DB2,and WebSphere Portal.Speeds up initial data collection and ensures that acomplete set of data is collected. WebSphere Commerce collectors for IBM SupportAssistant gather all relevant logs from application Copy right
Checkpoint481. Name some of the features andenhancements availablewith WebSphere Commerce V7.2. List the Application Layers of WebSphere Commerce.3. The Business Logic Layer supports which two methods ofcommand processing.4. True or false: A task command can be composed of anynumber of controller commands.5. List the three pieces of the Data Service Layer Copy right
Checkpoint Solutions491. Multi-channel precision marketing,Mobile, and SocialCommerce, efficient Data Loading utility, new Starter Storesthat are enabled by Web 2.0 technology (EliteB2B), IBMManagement Center enhancements, ANT-based migrationassistance utilities, developer infrastructure improvementsfor Rational Application Developer V7.5.2. Business Models, Business Processes, Presentation Layer,Service Layer, Business Logic, Persistence Layer, andDatabase Schema.3. Name-value pair processing and BOD processing4. Data service facade, business object mediation service,physical object persistence service. Copy right
Exercise Introduction50 Introduction to the WebSphereCommerce DevelopmentEnvironment. In this lab exercise, you will: Copy rightStart the WebSphere Commercedevelopment environment.Identify common projects that areused in the development process.Locate store artifacts to customize.Launch the WebSphere Commercetest server.Analyze server logs for debugging anderror handling.
Unit SummaryThis unit has been designed to enable you to: Start a development project that implements WebSphereCommerce V7. Describe the runtime architecture of WebSphere Commerce. Describe the development model for WebSphere Commerce. Explain the application of Struts in WebSphere Commerce. Describe the presentation layer for WebSphere Commerce byusing both standard JSP files and Web 2.0-enabled JSP files. Summarize the Business Logic and Persistence Layers. Describe the benefits of EJBs, Access beans, and the DataService Layer, and describe what role each plays in persistence. Summarize the elements and utilities available in AccessControl. Explain the development environment and how to effectivelytroubleshoot and debug WebSphere Commerce applications.51 Copy right
References52 WebSphere Commerce V7 Information help/v7r0m0/index.jsp Apache Struts:http://struts.apache.org Open Application Group (OAGi) Business Object Documentarchitecture:http://www.oagi.org Dojo Foundation Toolkit 1.3.1:http://www.dojotoolkit.org OpenLaszlo:http://www.openlaszlo.org Service Data Objects (SDO):http://www.osoa.org Copy right
References53 IBM Support Assistant:http://www.ibm.com/software/support/isa/ IBM Education Assistant for WebSphere ieduasst/v1r1m0/index.jsp?topic /com.ibm.iea.wcs/plugin coverpage.html IBM Support Portal:http://www.ibm.com/support/entry/portal/ WebSphere Commerce ones/commerce IBM Redbooks:http://www.redbooks.ibm.com
Unit Objectives 2 This unit was designed to enable you to: Start a development project that implements WebSphere Commerce V7. Describe the Runtime architecture of WebSphere Commerce. Describe the development model for WebSphere Commerce. Explain the application of Struts in WebSphere Commerce. Describe the presentation layer for WebSphere Commerce by using both
In the three volumes of the IBM WebSphere Portal V4.1 Handbook, we cover WebSphere Portal Enable and Extend. The IBM WebSphere Portal V4.1 Handbook will help you to understand the WebSphere Portal architecture, how to install and configure WebSphere Portal, how to administer portal pages using WebSphere Portal; it will also discuss the
WebSphere Commerce Line-of-Business Tooling Customization Rufus Credle Jeff Coster Steffen Eckardt Girish Gopinathan Vani Mittal Juha Nevalainen Ramya Rajendiran Customizing Management Center for WebSphere Commerce Optimizing the day-to-day activities of the business users Demonstrating customization scenarios Front cover. WebSphere Commerce .
WebSphere 8. Welcome to the F5 Deployment Guide for IBM WebSphere. This document provides guidance for deploying the BIG-IP Local Traffic Manager (LTM) with IBM WebSphere 8. The BIG-IP system can optimize IBM WebSphere at many layers: in front of the IBM HTTP . Servers, between HTTP Servers and WebSphere Application Servers, or to eliminate .
Download and install WebSphere MQ 2. Configure WebSphere MQ 3. Install OEG Gateway . Oracle Enterprise Gateway 6 / 30 4. Configure Gateway to send messages to WebSphere MQ 5. Configure Gateway to listen for messages from WebSphere MQ queue 6. Test Setup 2. Setting up the WebSphere MQ environment
WebSphere Application Server WebSphere MQ Use the most appropriate protocol C .net Java C JMS COBOL Java Jacl JMS Jython Web-Sockets C# HTTP WebSphere Application Server is a fully compliant Java Enterprise Edition (JEE) application server. The Java Message Service (JMS) is the JEE application messaging protocol. WebSphere MQ provides a fully
Figure 2 WebSphere Manages the Middle Tier in a Three-Tier Model One of the WebSphere products, WebSphere Portal, manages a variety of enterprise applications and supports application development and delivery. In the Lean Retail WebSphere Solution, content development and document management functions of WebSphere Portal were tested.
IBM WebSphere Portal Version 5 Family Enable WebSphere Application Server IBM HTTP server WebSphere Portal Server Out-of-the-Box Portlets Collaboration Services API Portal Toolkit WebSphere Translation Server WebSphere Studio Site Developer Content Management Personalization Portal Document Manager
Rumki Basu, Public Administration: Concepts and Theories, Sterling Publishers, New Delhi, 2009. 20. S.P. Naidu, Public Administration: Concepts and Theories, New Age International, New Delhi, 2015. 21. Abdul Quayum, Nazmo Nasq-e-Amma, Nisab Publishers, Hyderabad 2018. CBCS BA Public Administration 2020 MANUU, Department of Public Administration 4 Course Code Course Title Semester BAPA201CCT .
