Ee0 nw740 bb_config_guide_en_xx

SAP Fiori

October 2014

English

Version 1.0

Installation and configuration of common components of SAP Fiori (EE0)

Building Block Configuration Guide

SAP SE Dietmar-Hopp-Allee 16 69190 Walldorf Germany

SAP Best Practices

Installation and configuration of common components of SAP Fiori (EE0): Configuration

Guide

© SAP SE Page 2 of 16

Copyright

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark

SAP Best Practices


Guide


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade, and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the

ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

SAP Best Practices


Guide


Content

1 Purpose .............................................................................................................................. 5

2 Preparation ......................................................................................................................... 5

3 Installation .......................................................................................................................... 5

3.1 Technical system landscape .................................................................................... 5

3.1.1 Transactional Apps Landscape ........................................................................... 5

3.1.2 Fact Sheets Landscape ....................................................................................... 6

3.1.3 Analytical Apps Landscape .................................................................................. 7

3.2 Fiori Add-on installation ............................................................................................ 8

4 Post-Installation .................................................................................................................. 9

4.1 Connecting SAP NetWeaver Gateway to SAP Business Suite ............................. 10

4.1.1 Creating Trusted RFC in NetWeaver Gateway to SAP Business Suite ............ 10

4.1.2 Defining Trust between SAP Business Suite and SAP NetWeaver Gateway ... 11

4.1.3 Creating System Alias on Gateway ................................................................... 12

4.1.4 Activating SAP NetWeaver Gateway ................................................................. 12

4.2 Configuring SAP Web Dispatcher .......................................................................... 12

4.3 Installing and configuring Apache Reverse Proxy ................................................. 13

4.4 Implementing Important SAP Notes ....................................................................... 15

4.4.1 Releasing Information Notes for SAP Fiori ........................................................ 15

4.4.2 Product-specific Release Information Notes (RIN) ............................................ 16

SAP Best Practices


Guide


Installation and configuration of common components of SAP Fiori

1 Purpose There are two purposes of this document: the first one is to describe the general configuration steps required to manually set up the configuration within the system landscape; the other one is to provide the information about the software installation. We have three scenarios for Fiori: Transactional apps, Analytical apps and Fact sheets. Each scenario has its specific systems or software to be installed. By reading through this document, you should be able to setup your own Fiori landscape based on the required system environment.

2 Preparation For the following Fiori landscape, you must match the boundary conditions to make sure your landscape runs successfully:

HANA first, which means that all of the Fiori apps must best run on HANA.

The Fiori Shell is the central service for making all Fiori apps available to users.

3 Installation

3.1 Technical system landscape SAP Fiori has three app types, each distinguished by their focus and infrastructure requirements:

Transactional apps

Fact sheets

Analytical apps (smart business apps and Non – smart business apps)

When installing Fiori apps, we recommend separating the front-end components with the UI layer from the back-end components that contain the business logic and the back-end data.

3.1.1 Transactional Apps Landscape These are mainly apps that run best on HANA but can also be ported to other databases with reasonable efforts and acceptable performance. These scenarios are typically transactional and represent views on and interaction with existing business processes and solutions.

These apps let you perform transactional tasks, such as creating a leave request for an employee. They represent simplified views and interaction with existing business processes and solutions. They run best on an SAP HANA database.

The figure below shows the System Landscape for Transactional Apps.

SAP Best Practices


Guide


3.1.2 Fact Sheets Landscape These apps display contextual information about central objects used in your business operations. Fact sheets are designed to be intuitive and harmonized. From a fact sheet area (tile), you can drill down into its details. You can easily navigate from one fact sheet to its related fact sheets. For example, you can navigate from a document to the related business partner or to the master data. From fact sheets, you can also access related transactions in operational systems. For example, from a document fact sheet, you can access the back-end system to display document details or to edit the document.

Fact sheets run only on an SAP HANA database and require an ABAP stack. They cannot be ported to the SAP HANA live (2-tier) architecture.

The figure below shows the System Landscape for Fact Sheets.

SAP Best Practices


Guide


3.1.3 Analytical Apps Landscape Purely, analytical apps that will only run on HANA following the HANA Live (2-tier) architecture using virtual data models (VDM). Typical representatives are Analytical (KPI Cockpits) but also other analytical, predictive and planning applications. These apps are not intended for being ported to any other database (Any DB).

SAP Analytical apps allow you to get a role-based insight into real-time operations of your business by collecting and displaying key figures directly in your browser. To do this, they combine the data and analytical power of SAP HANA with the integration and interface components of SAP Business Suite. They provide holistic real-time information on big volume data in a simplified front end for enterprise control. With SAP Analytical, your company is able to closely monitor your most important KPIs in real time and react immediately on changes in market conditions or operations.

The figure below shows the System Landscape for Analytical Apps:

SAP Best Practices


Guide


3.2 Fiori Add-on installation

Prerequisites Before installing the add-ons for fiori, please make sure that the software in the table below with correct versions are installed to set up the environment for transactional apps, fact sheets and analytical apps:

Software Version

SAP HANA

SAP HANA 1.0 SPS08 Revision 81

SAP HANA Live for SAP Business Suite Support Package Stack 04

SAP NetWeaver

Back-end server:

SAP NetWeaver 7.40 SPS07

Front-end server:

SAP NetWeaver 7.40 SPS07

Business Suite product EHP7 FOR SAP ERP 6.0 SP04

Depending on the SAP NetWeaver Gateway release on your front-end server, you need either to install specific UI components or to ensure that these UI components are in place.

Fiori Add-on Installation Fiori supports three archetypes. Though the generic landscape are the same: Frontend Server, Business Suite on HANA with underlying HANA database, there’re different add-ons to be installed to enable respective archetype

SAP Best Practices


Guide


Some of the add-ons are included in Support Packages of corresponding products like ERP6.07, or HANA live, some of the add-ons need additional installation.

For certain archetype apps, there’re required general components, archetype specific components, and apps themselves.

App specific components consist of two parts, one is the UI part, installed on Frontend Server, the other is the backend part (services, roles, functions), installed on either Business Suite on HANA (Transactional apps and Fact sheets), or HANA database (Analytical apps).

Below is the brief summary of what’s needed for which:

General Components

UI 5 libraries and services, required on Frontend Server, delivered with SAP_UI add-on, which is installed in NW7.40 as default

Launchpad, including UI and unified shell service, delivered with SAP_UI add-on, which is installed in NW7.40 as default

Archetype Specific Components

Transactional archetype doesn’t have specific components

Analytical archetype need KPI modeler for KPI and generic drill down application creation, also need models/views delivered with HANA live

Fact sheets archetype need Search engine and C’estBON framework from NW to work properly, as well as Search models that are delivered with SP of Suite on HANA

App Themselves

Transactional and Fact sheets apps are bundled together in delivery, the UI part is in add-on by backend systems (ERP, CRM and so on), and the backend part is included in SP2 of Suite on HANA.

Analytical apps use KPI modeler as generic UI, and the backend part is in add-on by modules.

From execution perspective, the following add-ons should be installed by system administrator:

Fiori Add-On Component

Software Component System Applied for App Types

UI for EHP7 for SAP ERP 6.0

UIEAAP01 100 Front-End Transactional Apps and Fact Sheets

FIORI ERP APPLICATIONS X1 1.0

UIX01EAP 1.0 Front-End Transactional apps

KPI MODELER 1.0

UISKPI01 100 Front-End Analytical

KPI MODELER S 100 HANA Analytical

HANA CONTENT HBA AF CORE 100 HANA Analytical(new

version of Smart Business)

SAP Smart Business for ERP 1.0

HANA Content HBA SOFM S 100

HANA Analytical

HANA Content HBA PS S 100

HANA Cont.Reuse SAP ERP 100

HANA Content HBA SAP ECC 100

HANA Cont.Reuse SAPAPPL604 100

4 Post-Installation

SAP Best Practices


Guide


This section includes the post-installation steps that you have to perform for the following:

Configuring SAP Web Dispatcher

Install and configure Apache Reverse Proxy

Connecting SAP NetWeaver Gateway to SAP Business Suite

Implementing Important SAP Notes

4.1 Connecting SAP NetWeaver Gateway to SAP Business Suite

4.1.1 Creating Trusted RFC in NetWeaver Gateway to SAP Business Suite

You define the trust relationship between your SAP Business Suite system and the SAP NetWeaver Gateway host by configuring the SAP NetWeaver Gateway host to be the trusting system, the SAP Business Suite system (backend system) to be the trusted system.

NOTE

This is a RFC destination used to establish the trust which will be used during runtime.

Procedure

1. In gateway system, access the activity using one of the following navigation options:

Transaction code SM59

SAP CRM GUI menu Architecture and Technology System Administration

Administration Network RFC Destinations

2. Choose Create (F8).

3. In the RFC Destination field, enter the RFC destination name in the following

format: <system id >CLNT<Client>.

4. In the Connection Type field, enter 3.

5. In the Description 1 field, enter an explanatory text, for example, RFC Destination to

SAP Business Suit.

6. Save your settings.

7. On tab Technical Settings tab, Enter the parameters according to the table below:

Field name Entry

Load Balancing Status No

Target Host <Server name of Business suit system>

xxx.wdf.sap.corp

System Number < Business Suit System number>

00

8. On tab Logon & Security, enter the following parameters.

Field name Entry

Language EN

Client <Client of Business Suit system>

SAP Best Practices


Guide


Field name Entry

080

User Check current user

9. For Trust Relationship, activate Yes.

10. Save you settings.

4.1.2 Defining Trust between SAP Business Suite and SAP NetWeaver Gateway

You define the trust relationship between your SAP Business Suite system and the SAP NetWeaver Gateway host by configuring the SAP Business Suite system (backend system) to be the trusting system, and the SAP NetWeaver Gateway host to be the trusted system.

NOTE

This is a RFC destination used to establish the trust which will be used during runtime.

Procedure

1. In your Business Suite system, access the activity using one of the following navigation options:

Transaction code SM59

SAP CRM GUI menu Architecture and Technology System Administration

Administration Network RFC Destinations

2. Choose Create (F8).

3. In the RFC Destination field, enter the RFC destination name in the following

format: <system id >CLNT<Client>.

4. In the Connection Type field, enter 3.

5. In the Description 1 field, enter an explanatory text, for example, RFC Destination to

SAP NetWeaver Gateway.


7. On tab Technical Settings tab, Enter the parameters according to the table below:

Field name Entry

Load Balancing Status No

Target Host <Server name of Gateway System >

xxx.wdf.sap.corp

System Number < Gateway System number>

00

8. On tab Logon & Security, enter the following parameters.

Field name Entry

Language EN

Client <Client of Gateway system>

080

SAP Best Practices


Guide


Field name Entry

User Check current user

9. Save you settings.

10. In transaction SMT1 choose Create.

11. Proceed with the steps outlined in the wizard. In the RFC Destination field, enter the RFC destination you created. An RFC logon to the SAP NetWeaver Gateway host takes place and the necessary information is exchanged between the systems.

12. Log on to the SAP NetWeaver Gateway host using your administrator user and password.

The trusted entry for the SAP NetWeaver Gateway host displays.


End users must have authorization object S_RFCACL assigned to them before

they can use a trusted connection. For more information, see RFC Trusted/Trusting Systems.

4.1.3 Creating System Alias on Gateway

1. Access the activity using one of the following navigation options:

Transaction code SPRO

SAP GW GUI menu SAP NetWeaver Gateway Odata Channel

Configuration Connection Settings SAP NetWeaver

Gateway to SAP SystemManage SAP System Aliases

2. Choose New Entries.

3. Enter the following parameters.

Field name Entry

SAP System Alias <your RFC destination name>

RD7CLNT180

Description Description of your system

RFC Destination <your RFC destination name>

RD7CLNT180

Software Version DEFAULT

4. Choose Save.

4.1.4 Activating SAP NetWeaver Gateway 1. In the ABAP Front-End Server, access the activity using the following navigation options:

Transaction code SPRO

SAP Reference IMG menu

SAP NetWeaver Gateway OData Channel

Configuration Connection Settings Activate or Deactivate SAP NetWeaver Gateway

2. Choose Activate. A message is displayed informing you of the current status.

4.2 Configuring SAP Web Dispatcher SAP Fiori client applications are HTML5 applications that access multiple back-end systems. However, JavaScript code is constrained by the Same-origin Policy. For this reason, all

http://aiokeh.wdf.sap.corp:50000/SAPIKS2/contentShow.sap?IWB_INDUSTRY=ERP-BFS&RELEASE=7101&_CLASS=IWB_EXTHLP&_LOIO=D35B5C8AC5A93941B9F4E2F09B50BEB4&TMP_IWB_TASK=PREVIEW2&_SLOIO=299A5652D8C3725FE10000000A441470&LANGUAGE=EN&_SEQNUM=18&_SCLASS=XDP_STRUCT

http://aiokeh.wdf.sap.corp:50000/SAPIKS2/contentShow.sap?IWB_INDUSTRY=ERP-BFS&RELEASE=7101&_CLASS=IWB_EXTHLP&_LOIO=D35B5C8AC5A93941B9F4E2F09B50BEB4&TMP_IWB_TASK=PREVIEW2&_SLOIO=299A5652D8C3725FE10000000A441470&LANGUAGE=EN&_SEQNUM=18&_SCLASS=XDP_STRUCT

SAP Best Practices


Guide


systems are exposed to the browser through the SAP Web, which brings them into a common origin (combination of protocol, hostname, and port). In addition to solving the same origin problem, this enables you to control which services are effectively exposed to the client, reducing the system attack surface. You must implement and configure SAP Web Dispatcher as an SSL client in the system landscape.

Since SAP Web Dispatcher is a comprised component of SAP NetWeaver, so below we’ll use underlying SAP Web Dispatcher of the Front-End Server. Incoming sources include the Front-End Server, (several) Back-End XSEs, (several) Back-End Enterprise Searches; below we’ll just have one ERP on HANA for example.

If you intend to install a standalone SAP Web Dispatcher instance, you can refer to

http://service.sap.com/installnw74 3 – Installation – Standalone Engines Installation:

Web Dispatcher for SAP NetWeaver 7.1 or Higher

For more information regarding SAP Web Dispatcher, please refer to http://help.sap.com

SAP NetWeaver SAP NetWeaver Platform Function Oriented View Application

Server Application Server Infrastructure Components of SAP NetWeaver Application

Server SAP Web Dispatcher.

1. Access the Operating System of SAP Web Dispatcher, edit its Instance Profile webdispatcher.pfl.

Since Web Dispatcher uses a different System Number from SAP NetWeaver, so if you use Front-End Server underlying Web Dispatcher, the profile is not the one you can see in RZ10.

2. To enable HTTPS for web dispatcher, make sure that you have sapcrypto.dll file installed already. Add following profile parameters in the instance profile webdispatcher.pfl.

DIR_INSTANCE = <SECUDIR_Directory>

ssl/ssl_lib = <Location_of_SAP_Cryptographic_Library>

ssl/server_pse = <Location_of_SSL_server_PSE>

ssl/client_pse = < Location_of_SSL_client_PSE >

wdisp/ssl_encrypt = 1

wdisp/ssl_auth = 1

wdisp/add_client_protocol_header = 1

wdisp/ping_protocol = https

icm/HTTPS/verify_client = 1

3. Add following profile parameters for ICM ports:

icm/server_port_0 = PROT=HTTPS,PORT=<Web Dispatcher Port>,TIMEOUT=120

4. Add following profile parameters for Web Dispatcher routes:

wdisp/system_0 = SID=<Front-End SID>, MSHOST=<Front-End Hostname>, MSPORT=<Front-End Messaging Port>, SRCSRV=*:<Web Dispatcher Port>,

SRCURL=/sap/opu/;/sap/public/;/sap/bc/;/sap/saml2/;/ui2/nwbc/, CLIENT=<Front-End client>

wdisp/system_1 = SID=<Back-End SID>, MSHOST=<Back-End Hostname>, MSPORT=<Back-End Messaging Port>, SRCSRV=*:<Web Dispatcher Port>,

SRCURL=/sap/es/, CLIENT=<Back-End client>

wdisp/system_2 = SID=<HANA SID>, EXTSRV=<HANA XS URL>,

SRCSRV=*:<Web Dispatcher Port>, SRCURL=/sap/hba/;/sap/hana/

5. Save the Instance Profile and restart the Web Dispatcher process.

6. Test the Web Dispatcher URLs using web browser:

https://<Web Dispatcher Hostname>:<Web Dispatcher Port>

4.3 Installing and configuring Apache Reverse Proxy

http://service.sap.com/installnw74

http://help.sap.com/

SAP Best Practices


Guide


Only transactional SAP Fiori apps are supported for consumption by Internet clients. This can include mobile devices that are not connected to the corporate intranet, for example when a user is travelling.

We recommend keeping the SAP Web Dispatcher for SAP Fiori and the SAP NetWeaver Gateway in the intranet zone and deploying an additional Reverse Proxy (can be another SAP Web Dispatcher) in the DMZ. This additional Reverse Proxy should allow only requests that will be routed to the common ICF services or to the apps that must be exposed. Below we will use Apache Reverse Proxy.

Apache HTTP Server latest version is 2.4, which integrates mod_proxy_html as built-in module, and also other improvements. However, by now there’s no official Windows binary, so if you’re using Windows OS on DMZ machine, you can download Apache HTTP Server binary from 3rd party sites. Below we’ll use Apache 2.4.6 VC11 Win64 binary from http://www.apachelounge.com/download/.

1. Install Apache HTTP Server in the DMZ machine, it’s better you install it in a high level folder such as C:\Apache24\.

2. Edit the \conf\httpd.conf in the Apache installation folder.

Uncomment these lines to load required proxy and SSL modules:

LoadModule filter_module modules/mod_filter.so

LoadModule headers_module modules/mod_headers.so

LoadModule proxy_module modules/mod_proxy.so

LoadModule proxy_html_module modules/mod_proxy_html.so

LoadModule proxy_http_module modules/mod_proxy_http.so

LoadModule substitute_module modules/mod_substitute.so

LoadModule xml2enc_module modules/mod_xml2enc.so

3. Add the following conditional include to your httpd.conf file:

<IfModule proxy_html_module>

Include conf/extra/proxy-html.conf

</IfModule>

proxy-html.conf file should contain some default apache configurations.

4. Add these lines to enable HTTP proxy, please change values according to your system values, since angle brackets <> are used in the file, so below we’ll use square brackets [] as placeholder.

Listen [Reverse Proxy port]

<VirtualHost *:[Reverse Proxy port]>

#If you need to use some proxy for DMZ machine to access Intranet

ProxyRemote https://[Web Dispatcher host]:[port]/ http://[proxy]:[port]

# Ensure non-ASCII URL parameters can be passed

AllowEncodedSlashes On

<Location />

# Disable compression in order to enable rewrite rules

RequestHeader unset Accept-Encoding

# Requests to / are forwarded to https://[Web Dispatcher]:[Port]/

ProxyPass https://[Web Dispatcher host]:[port]/ nocanon

# Rewrite response headers (for example. for redirections)

ProxyPassReverse https://[Web Dispatcher host]:[port]/

# Rewrite Set-Cookie directives

ProxyPassReverseCookiePath / /

ProxyPassReverseCookieDomain [Web Dispatcher host] [Reverse Proxy host]

# Enable HTML rewriting to fix URL's in HTML document

ProxyHTMLEnable On

http://www.apachelounge.com/download/

SAP Best Practices


Guide


ProxyHTMLURLMap https://[Web Dispatcher host]:[port] http://[Reverse Proxy host]:[port]

# We must also rewrite URL's in XML and JSON responses from Gateway.

# We do so through crude mod_substitute filter

AddOutputFilterByType SUBSTITUTE text/xml application/xml application/json

Substitute"s|https://[Web Dispatcher host]:[port]| http://[Reverse Proxy host]:[port]|i"

</Location>

</VirtualHost>

5. Use Command Prompt to run below command to create corresponding Windows service:

cd C:\Apache24\bin

httpd.exe -k install -n ApacheReverseProxy

6. Start the Apache Reverse Proxy service.

7. Validate the configuration by opening a browser and testing the URL: http://<Reverse Proxy>:<HTTP Port>/sap/bc/ping/?sap-client=<Front-End client>

4.4 Implementing Important SAP Notes

4.4.1 Releasing Information Notes for SAP Fiori The table below lists the central SAP notes for these three archetypes in Fiori.

System Area SAP Note

Note Type Description

Front-End Server

Mobile 1958586 Information Telecommunication Network Prerequisites for SAP Fiori

Front-End Server

UI 2029407 Central Central Note for SAP Fiori Launchpad - UI Add-On 1.0 SP09

Front-End Server

UI 2051051 Activation SAPUI5 upgrade to version 1.22.6

Front-End Server

UI 2019136 Collection Corrections for SAP NetWeaver UI Add-On 1.0 SP09

Note

Upgrade SAPUI5 to 1.22.6 or higher version would also be fine.

Front-End Server

Performance

2031444 Manual Cleanup of expired Fiori personalization data on the frontend server

Front-End Server

Launchpad

2043432 Maunal Browser cache is not invalidated after version or patch update of SAP Fiori components

Front-End Server

UI 1935915 Information Fiori for Business Suite: Browser / Devices / OS Information

Front-End

UI 2019430 Manual Display error message in Fiori applications when security session has expired

SAP Best Practices


Guide


System Area SAP Note

Note Type Description

Server

Front-End Server

UI 1919137 Information Release Information Note: SAP Fiori Analytical Applications incl. SAP Smart Business

Back-End ERP

Fiori Search

1976027 Information Release Information Note for SAP NetWeaver Embedded Search in SAP Fiori

Back-End ERP

Fiori Search

2028711 Manual + Collective Activation

Report for composite SAP note 2028712

Back-End ERP

Fiori Search

2028712 Manual + Collective Activation

SAPKB74007: Composite SAP Note 1

Back-End ERP

Fact Sheets

1861013 Information HANA-Enabled Search Models for SAP Business Suite -- Enable Fiori Search and Fact Sheets

4.4.2 Product-specific Release Information Notes (RIN) As we have many products specific apps in Fiori landscape, the table below listed these products specific SAP notes.

Product SAP Note Number

Description

ERP 1737650 EHP7 for SAP ERP 6.0 SP Stacks - Release & Information Note

1914499 Release Information Note: UI FOR EHP7 FOR SAP ERP 6.0

Education

Ee0 nw740 bb_config_guide_en_xx