No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

AMI Smart Meter Reading Solution V200R010C10 Planning and Design Guide

This document describes the overall and detailed design of functions and services in the AMI Smart Meter Reading Solution.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
EEM Database Configuration

EEM Database Configuration

The EEM supports both Oracle and MySQL databases. For details on how to select the database, see Software and Hardware Configurations of the EEM.

The EEM and DCP share the database, they use different database instances to exchange data with databases. The EEM and DCP support MySQL and Oracle databases. You can select the database based on the number of terminals and requirements. Using the MySQL database reduces costs, and the Oracle database provides many functions and has high reliability.

Oracle Database Configuration

In the AMI solution, the third-party application system, EEM, and DCP all support the Oracle database. You can deploy the Oracle database in the single-node system, Oracle RAC, and Oracle HA. Different deployment modes have different requirements for the software and hardware of the database server. You can select configurations according to the actual situation.

In server deployment mode, remote disaster recovery is supported. To ensure normal service switching, the database also needs to support remote disaster recovery. The Oracle database provides remote disaster recovery through Data Guard (DG). The Oracle database in the single-node system, Oracle RAC, or Oracle HA can be deployed in the production center and disaster recovery center. When there are more than 100,000 devices, Oracle RAC is recommended to ensure reliability. In the remote disaster recovery solution, it is recommended that application systems use the cluster deployment mode, so databases in active/standby or cluster mode need to be used. Oracle RAC is recommended.

Software Configuration of the Oracle Database
Table 2-11 describes the software configuration of the Oracle database.
Table 2-11  Software configuration of the Oracle database

Item

Number of Managed Devices

Solution Selection

Deployment Mode

Deployment Solution

Recommended Configuration

Remarks

Operating system

0 to 20,000

Small-sized AMI solution

Server deployment

  • Oracle database in the single-node system
  • Oracle RAC

Novell SuSE LINUX Enterprise Server 11.3

In server deployment mode, the EEM supports remote disaster recovery.

VM deployment

  • Oracle database in the single-node system
  • Oracle RAC

Novell SuSE LINUX Enterprise Server 11.3

In VM deployment mode, the EEM does not support remote disaster recovery.

Oracle HA

Windows Server 2008

0 to 6,000,000

AMR solution

Server deployment

  • Oracle database in the single-node system
  • Oracle RAC

Novell SuSE LINUX Enterprise Server 11.3

In server deployment mode, the EEM supports remote disaster recovery.

Standard AMI solution

Server deployment

  • Oracle database in the single-node system
  • Oracle RAC

Novell SuSE LINUX Enterprise Server 11.3

In server deployment mode, the EEM supports remote disaster recovery.

VM deployment

  • Oracle database in the single-node system
  • Oracle RAC

Novell SuSE LINUX Enterprise Server 11.3

In VM deployment mode, the EEM does not support remote disaster recovery.

Oracle HA

Windows Server 2008

Hardware Configuration of the Oracle Database
When the remote disaster recovery solution in server deployment mode is used, the database servers of the production center and disaster recovery center are similar. The hardware configuration in the production center is used as an example to describe the Oracle database hardware configuration. Table 2-12 describes the hardware configuration of the Oracle database.
Table 2-12  Hardware configuration of the Oracle database

Number of Managed Devices

Deployment Mode

Minimum Server Configuration

0 to 20,000

Oracle database in the single-node system

The Oracle database and application system are deployed on the same device.

PC12C64G*1

The Oracle database and application system are deployed separately.

Oracle RAC

PC12C64G*2

20,000 to 6,000,000

Oracle RAC

PC12C64G*2

0 to 6,000,000

Oracle HA

VM configuration:
  • Memory: 72 GB or more
  • Hard disk: 1200 GB or more
NOTE:

Three Windows Server 2008 VMs need to be configured. Two VMs are used as database servers, and one VM is used as the shared storage server.

Physical server configuration
  • PC14C72G

MySQL Database Configuration

When there are no more than 100,000 terminals, the EEM and DCP support the MySQL database. You can deploy the MySQL database in the single-node system or configure MySQL HA. Different deployment modes have different requirements for the software and hardware of the database server. You can select configurations according to the actual situation.

In server deployment mode, remote disaster recovery is supported. To ensure normal service switching, the database also needs to support remote disaster recovery. The MySQL database supports data replication and recovery and can implement remote disaster recovery. In the remote disaster recovery solution, it is recommended that application systems use the cluster deployment mode, so databases in active/standby or cluster mode need to be used. MySQL HA can be configured. When there are at most 100,000 devices, the EEM can use the MySQL database to implement remote disaster recovery.

In the remote disaster recovery solution, the networking and configuration of application systems and databases in the disaster recovery center are similar to those of the production center. The production center is used as an example to describe the software and hardware configurations of the MySQL database. The software and hardware configurations of the MySQL database in the disaster recovery center are similar to those of the production center.

Software Configuration of the MySQL Database
Table 2-13 describes the software configuration of the MySQL database.
Table 2-13  Software configuration of the MySQL database

Item

Maximum Number of Managed Devices

Recommended Configuration

Operating system

0 to 100,000 access devices

Novell SuSE LINUX Enterprise Server 11.3

Hardware Configuration of the MySQL Database
Table 2-14 describes the hardware configuration of the MySQL database.
Table 2-14  Hardware configuration of the MySQL database

Maximum Number of Managed Devices

Deployment Mode

Minimum Server Configuration

0 to 100,000 access devices

MySQL database in the single-node system

The MySQL database and application system are deployed on the same device.

PC12C64G*1

The MySQL database and application system are deployed separately.

MySQL HA

PC12C64G*2

Translation
Download
Updated: 2019-03-07

Document ID: EDOC1100069579

Views: 6862

Downloads: 11

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next