Chapter 2: Architecture
Section 1: Single System Landscape
WECO E-commerce can be deployed in SAP in one of two models, single-system or two-system landscape. In a single system landscape, the SAP core system (ECC or S/4) and the Netweaver Gateway (also know as Web Application Server) are the same system. In a two-system setup, the SAP core system (ECC or S/4) and the Netweaver gateway are two separate systems. In this model the core system has all WECO functionality both presentation and business layers, while the Netweaver Gateway has only the presentation layer. None of the core business logic resides on this device.
- SAP ECC or S/4 and the Netweaver Gateway (WAS) are on the same SAP system.
- All configuration is performed on this system and transported from DEV > QA > PRD
- Core and WAS configuration are still required to be configured but all happen on the one system.
- Technical development is still separated in transports as if a two-system landscape exists. This allows for easy migration to a two-system landscape in the future.
Section 2: Two-System Landscape
- SAP ECC or S/4 and the Netweaver Gateway (WAS) are separate SAP systems
- Core Configuration is performed on this system and transported from DEV > QA > PRD
- WAS configuration is performed on the WAS and transported from WAS-DEV > WAS-QA > WAS-PRD
- Technical development is performed ONLY on the Core system. Development is separated into separate transports for WAS or CORE. WAS transports are released on the Core system and then imported to the WAS and then transported from there to WAS-QA > WAS-PRD.
- IMPORTANT: No technical development is done directly on the WAS.
Section 3: Reverse Proxy
A Reverse Proxy has multiple purposes in a WECO E-Commerce landscape.
- Provides a layer of security shielding the internal SAP system netweaver domain name from external users.
- Handles rewrite rules for the WECO SEO module (up to version 7.08). In version 8.0 of WECO SEO rewrite rules are managed within WECO configuration.
- Can serve is the web server to hold WECO product manual content such as images, videos, PDFs, HTML pages, etc.
Section 4: Installation
As of WECO 6.0, the software is now SAP Certified and is installed using standard SAP transactions SAINT, for the initial packages, and SPAM for the WECO Service packs. When a client purchases the WECO modules for their implementation, a Software Request is submitted by CNBS. In the software request, a designated contact at the client is provided and they are given a link to download the software from WECO. Only the client is permitted to download software from their client login. The client SAP BASIS team is responsible for installation of the software. CNBS often will be involved to assist with these tasks if any issues arise. But in most cases, a knowledgeable BASIS person can do this if the documentation is properly followed. The attached installation guides provides further technical details.
Once the installation is complete, a number of post installation activities need to take place. These activities include:
- Activating services in SAP transaction SICF
- Creating external aliases
- Assigned WECO ICF User in the external aliases.
- Note: Prerequisite in section 2.5 for creating and assigning roles for the WECO ICF user.
Activating WECO Services: The three required services to be activated are highlighted below.
Creating external aliases:
- Execute transaction SICF
- Select the default host in the list of hosts/services
- Click the External Aliases button
In the external alias screen:
- Provide the text and a description for the external alias (e.g. /b2b, /b2c, etc.).
- Enter the username, password, and SAP client for the WECOICF Service user created in section 2.5
- On the Trg Element tab, navigate the weco service which this external alias will use.
Below shows a full internal URL for a WECO application. Highlighted in red demonstrates the relevance of the external alias.
Section 5: Service Users
WECO has two several types of users in the system which include Web Users, Reference Users, and Service Users. This section covers the WECO Service and Reference Users. WECO Web users are covered in detail in Chapter 6.
When the WECO software is delivered, during the installation, a number of user roles are created in the client system. These template users roles are the starting point and like any standard SAP object, it is advised to make a Z-version of the role and adjust it accordingly. Below is a brief description of these. The standard SAP transactions (SU01, PFCG, SUIM, etc.) are used for managing these Service users.
It is the responsibility of the WECO functional consultant to blueprint the requirements from the client to determine various types of users which will be needed to both support the application from an administrative perspective as well as from an end-user perspective. It is advised to create a matrix of these different types of users to determine how many unique user types will be required.
Technical and Administration Roles Users:
The following roles are typically assigned to the SAP user IDs at the client for those individuals who will have administrative control over the application.
/WECO/SHP_ADMIN_ALL: Authorizations which are needed by a shop administrator
/WECO/W_SHP_ADMIN_ALL: Authorizations which are needed by a shop administrator on the Web Application Server
The user role below is assigned to a service user to be assigned in transaction SICF in the external aliases created to support the WECO implementation.
/WECO/TECHN_USER_TEMPLATE: Authorizations which are needed by the RFC user (2-system landscape) or the technical user (1-system landscape)
Reference users linked to WECO Web Users:
The following template roles are used as the basis for Service Users created to act as Reference users. The reference users and the roles assigned reflect the users experience and what actions they are allowed to perform. For example, some users may be allowed to create orders while others are not. Some users may be allowed to see pricing. The relationship between a WECO Web User and WECO Reference user is many to one.
/WECO/SHP_B2B_ALL: Authorizations which are possible in a B2B scenario
/WECO/SHP_B2C_ALL: Authorizations which are possible in a B2C scenario
/WECO/SHP_B2B_ANONYM: Authorizations which are possible in an anonymous B2B scenario