Install View

From SAD

Jump to: navigation, search


Primary Presentation


Visio file


  • In this diagram, unnamed packages are used just to simplify representation of multiple <<manifest>> dependencies.
  • Only the most important artifacts are shown. We use '...' to indicate where there are other artifacts not in the diagram (the comment box indicates what artifacts are those).

Element Catalog




Standard Java EE deployment descriptor for ear files. Each ear has its own application.xml file with corresponding deployment configuration values.



OrderFacade, CatalogFacade, UserMgmtFacade

See Consumer Website Multi-tier View




Library of utilities that implement the Service Locator pattern.


Library that contains the Web Application Framework. It corresponds to package waf in the Top Level Module Uses View.



SignOnFilter, sign-on-config.xml, MainServlet, mappings.xml, TemplateServlet, screendefinitions.xml, index.jsp, SignOnNotifier,

See Consumer Website Multi-tier View


The enterprise archive that represents the OPC application. It is deployable on any Java EE compliant application server.


Standard EJB jar file that contains all EJBs that comprise the OPC application, except for ProcessManagerBean and ManagerBean.

PoEndPointBean, OtEndPointBean, WorkFlowManagerBean, PurchaseOrderBean, ActivityBean, TransportationBean, LodgingBean, CreditCardBean, OrderFillerBean, BrokerRequestorBean, BrokerServiceBean, CRMBean

See OPC C&C View

OpcPurchaseOrderService.wsdl, WebServiceBroker.wsdl, OpcOrderTrackingService.wsdl

These wsdl files contain the interface specifications for the SOAP web services that the OPC application provides. These web services are implemented and provided by components internal to the OPC application. These interfaces can be seen in the OPC C&C View.

LodgingPurchaseOrderService.wsdl, ActivityPurchaseOrderService.wsdl, CreditCardService.wsdl, AirlinePurchaseOrderService.wsdl,

These wsdl files contain the interface specifications for the SOAP web services that the OPC application requires. These web services are implemented and provided by external partners. These interfaces can be found in the OPC C&C View.


Standard EJB jar file that contains ProcessManagerBean and ManagerBean.

ProcessManagerBean, ManagerBean

See OPC C&C View

Context Diagram

TODO: Add here a context diagram that graphically shows the scope of the part of the system represented by this view. A context diagram typically shows the part of the system as a single, distinguished box in the middle surrounded by other boxes that are the external entities. Lines show the relations between the part of the system and the external entities.

Variability Guide

TODO: Describe here any variability mechanisms used in the portion of the system shown in this view, along with how and when (build time, deploy time, run time) those mechanisms may be exercised. Examples of variability include: optional components (e.g., plug-ins, add-ons); configurable replication of components and connectors; selection among different implementations of an element or different vendors; parameterized values set in build flags, .properties files, .ini files, or other config files.


The entire Adventure Builder system is deployed as two ear files (consumerwebsite.ear and opc.ear). Having two separate ear files allows to deploy the two corresponding applications on different application server instances and different machines. These separate target runtime environments can then be configured according with the processing and communication needs of each application. TODO: why ProcessManagerBean and ManagerBean are deployed in a separate EJB jar file (processmanager-ejb.jar)

TODO: Describe here the rationale for any significant design decisions whose scope is limited to this view. Also describe any significant rejected alternatives. This section may also indicate assumptions, constraints, results of analysis and experiments, and architecturally significant requirements that affect the view.

Related Views


Personal tools