Standard Deployment
SAP NetWeaver can be deployed in the standard distributed mode and integrated mode, as shown in Figure 1 and Figure 2.
In these deployment modes, all main instances (except for SAP HANA DB instance) run on a separated ECS. The deployment mode is used for all the scenarios, except for PRD. SAP NetWeaver includes the following instances:
- ABAP Central Services instance (ASCS instance)
- SAP HANA database instance (DB instance)
- Primary application server instance (PAS)
Huawei Cloud can be connected to SAP NetWeaver servers through a NAT server (binding an EIP) or using a VPN.
- Figure 3 shows the access to the SAP NetWeaver servers through a NAT server.
The concepts involved in the preceding figure are as follows:
- VPC: All ECSs in the SAP NetWeaver system are deployed in a VPC to protect network security. SAP NetWeaver ECSs belong to a private subnet, and the NAT ECS belongs to a public subnet.
- Users can log in to the NAT ECS with an EIP bound using RDP or SSH and use SAP GUI on the NAT ECS to access SAP NetWeaver ECSs.
- Public subnet:
- NAT server: allows you to access SAP NetWeaver ECSs using Secure Shell (SSH).
- SAP GUI is installed on the NAT ECS and allows users to access SAP NetWeaver ECSs on the private subnet.
- Private subnet:
- Central instance is used to deploy the ASCS instance and PAS instance.
- SAP HANA database instance is used to deploy the SAP HANA database.
- Public subnet:
- Figure 4 shows the access to SAP NetWeaver ECSs using a VPN.
The concepts involved in the preceding figure are as follows:
- VPC: To ensure network security, all SAP NetWeaver ECSs are in the same VPC.
- The user uses SAP GUI or Web Browser to access SAP NetWeaver ECSs through the VPN.
- The user or technical engineer is responsible for building the VPN.
- The user can use the VPC to access SAP application ECSs from the internal network.
Table 1 shows the file systems planned for the standard deployment mode.
Mount Point |
File System Type |
Description |
---|---|---|
/usr/sap |
ext3 |
Stored on the local VM (for details, see section Data Planning). |
/sapmnt |
ext3 |
Stored on the local VM (for details, see section Data Planning). |
Select a proper deployment mode as required. Table 2 lists the recommended application scenarios.
Deployment Scenario |
Deployment Mode |
Access Mode |
---|---|---|
TRN POC TST |
Standard deployment |
EIP (NAT) |
DEV QAS |
Standard deployment |
VPN |
The NAT server functions as only jump server.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot