Showing posts with label architecture. Show all posts
Showing posts with label architecture. Show all posts

Sunday, December 30, 2018

SAP PowerDesigner (SAP PD)

Apart of SAP Enterprise Architecture Designer (EAD) in are of enterprise architecture (EA) there is one more product in SAP's portfolio. It is the product called SAP PowerDesigner (PD) which has a long history. SAP gained it through acquisition of Sybase in 2010.

It enables data modeling and metadata management for following enterprise IT architecture areas: data, information and enterprise architecture. The PD enables impact analysis, design-time change management and metadata management techniques to enterprise IT projects.

The PD tool can help to visualize, understand, and manage impact of change to enterprise system before it happens. It supports end-to-end modeling by so called model-driven architecture (MDA) design with industry-standard modeling techniques, a powerful metadata repository, and unique Link and Sync technology. The PD has a capability of metadata repository that supports collaboration and communication between all the enterprise IT project stakeholders. Also it facilitates responses across teams involved to contributes to the business agility.

Difference between PowerDesigner and Enterprise Architecture Designer 
This may sound familiar if you read my other blog regarding SAP Enterprise Architecture Designer (EAD). The two products are overlapping in some areas. The difference between the two is mostly with regards to customization of the tools. Whereas the PowerDesigner is more customizable in case of the EAD the customization is limited. Source for this information can be found hereOther difference and more obvious one is that SAP EAD is a natural progression of PowerDesigner targeting on customers who want to move to a cloud-first SaaS solution for enterprise architecture. The EAD is SAP's strategic solution for enterprise architecture now.

More information:
BC-SYB-PD (PowerDesigner) - SAP support site component
2494295 - Overview and information about SAP PowerDesigner

Friday, December 28, 2018

SAP Enterprise Architecture Designer (EA Designer or EAD)

Within the SAP HANA Data Management Suite (HDMS) there is a central tool which serves as single point of design, documentation and reference from enterprise architecture (EA) point of view.
It can be used for capturing, analyzing, present of many artefacts important in architecting of IT objects. These objects can be landscapes, systems, strategies, data, biz processes, requirements, application modeling and other used in the IT environments. Depicting the mentioned objects by industry standards, using metadata and diagrams enables proper understanding of the EAD’s outcomes in different stages of the IT projects.

Short example of different diagram types that are supported by the tool:

- Business Process diagrams (e.g. BPMN 2.0: descriptive and executable)
- Conceptual Data, Physical data modeling & data architecture: Tables & Views, Virtual table definitions, Data Movement Models (Flowgraphs), Native DataStore Objects, HANA CDS associations
- Data Movement Diagram
- Enterprise Architecture Diagram
- NoSQL Document Schema (JSON)
- Process Map
- Requirements List

Here are few examples of capabilities that are supported by the tool:

Integrated design - Translate business strategy to technical implementation requirements
Development automation - Generate architecture and technical artifacts automatically
Corporate knowledge - Drive collaboration from a single point of truth for all stakeholders
Flexible deployment - Deploy artifacts to SAP HANA or SAP Cloud Platform

The tool is web based so user is using web browser all the time while using the tool. It aims to support comprehensive end-to-end modeling experience. It has reverse engineering capabilities too. It supports model comparison, lineage and impact analysis. It saves generated SAP HANA HDI compatible files to either local ZIP files (for later import to SAP Web IDE) or to Git Repository (for Git integration to SAP Web IDE).

The tool has its place in data warehousing are as it is used in SAP SQL Data Warehousing solution. Here it servers during design phase where the new SQL based DWH is being modeled in the tool. The models that are needed for such a DWH includes: Conceptual Data Model (CDM), Physical Data Model (PDM), LifeCycle Metamodel, CalcView, Data Movement Model.

Monday, December 15, 2014

LSA++ as successor of LSA

There are few options when it comes to modeling of EDW design. SAP recommends so called Layered Scalable Architecture (LSA). This one I covered in my post here. Such architecture gives a guide for implementing new models in BW. Means what kind of layers are supposed to be used for that particular model.

The (E) DW Layer consists of the first 4 layers. The Architected DataMart Layer or BI Layer consists of the last 3 layers. Here are reference Layers:

·        Data Acquisition Layer (DWH)
·        Harmonization & Quality Layer (DWH)
·        Corporate Memory Layer (DWH)
·        Propagation Layer (DWH)
·        Business Transformation Layer (BI)
·        Reporting Layer (BI)
·        Virtual Layer (BI)

With HANA coming into the scope of BW which is known as BW on HANA (BoH) the LSA got renewed. Basically also HANA optimized objects are incorporated into the architecture. Because of nature of HANA data persistency is less needed across different layers of LSA. This leads to reduction of the layers. Basically this new reference architecture built for BW on HANA is called Layered Scalable Architecture (LSA++)
These are following new InfoProvider objects incorporated into LSA++:

Open ODS View – is object designed to consume external sources with a given semantic. There are no InfoObjects needed to define analytic semantics. Instead it allows field-based modeling. This is in line with agile data modeling suitable e.g. for rapid prototyping. An analytic functionality can be employed on top of (external) data structures due to different interfaces like SAP HANA smart data access. External data (not residing in BW) can be combined with SAP BW data (master and transaction data). It is virtual object – data is not persistent. The Open ODS View object is equivalent of PSA layer in LSA.

Advanced DataStore object (ADSO) – is standard persistent InfoProvider, supports analytic queries, in future also planning apps, capable of calculating data changes within data flow, consolidates different types of IProv: classic DSO, w/o DSO, InfoCube. The consolidation of different objects can be done on the fly by switching its behavior without deleting the data. Modeling of ADSO is done only in Eclipse environment. The data is persistent in the ADSO.

(new) Composite Provider (ComProv) – this is meant for new composite provider available in BW 74 on Hana not the one available in BW 7.3. The new one is successor of MultiProv and Infosets. It is modeling object for both: joins and unions, can consolidate existing InfoProv (VirtualProv base on SAP HANA models, InfoSets, MultiProv, etc). Modeling of the new ComProv is done in Eclipse environment. It fits to Virtual(ization) layer of LSA++.

More information:

LSA++ for SAP NetWeaver BW on SAP HANA – SCN article by Juergen Haupt, EIM203 session