SAP Enhancement Package 8 for SAP ERP 6

Installation GuideDocument version: 1.0 – 2016-01-20

SAP Enhancement Package 8 for SAP ERP 6.0Java and ABAP

PUBLIC

Document History

CautionBefore you start the implementation, make sure you have the latest version of this document. For the latest

version, see service.sap.com/instguides .

The following table provides an overview of the most important document changes.

Table 1

Version Date Description

1.0 2016-01-20 Initial version

2

PUBLIC© Copyright 2016 SAP SE or an SAP affiliate company.All rights reserved.

SAP Enhancement Package 8 for SAP ERP 6.0Document History

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Finstguides

Content

1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 Essential Information: Process and Documentation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3 Installation (ABAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.4 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.5 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1 Dual-Stack Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.2 Installation Process for SAP HANA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.1 Implementing SAP ERP ABAP Add-On Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.2 Extended Configuration Management (XCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.3 Basic Settings for ERP E-Commerce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Creating a Back-End User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Checking the Connection to the ABAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Configuring the TREX Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3.4 Basic Settings for Java-Based Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Checking the Availability of SAP ERP Biller Direct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Checking the Availability of SAP ERP Utility Customer E-Services . . . . . . . . . . . . . . . . . . . . . . . . 23 Checking the Availability of Mobile Web Dynpro Java Applications for SAP Retail Store . . . . . . . . . 23 Checking and Configuring the Installation of SAP ERP Learning Solution – Content Player . . . . . . 24

SAP Enhancement Package 8 for SAP ERP 6.0Content

PUBLIC© Copyright 2016 SAP SE or an SAP affiliate company.

All rights reserved. 3

4

PUBLIC© Copyright 2016 SAP SE or an SAP affiliate company.All rights reserved. SAP Enhancement Package 8 for SAP ERP 6.0

Only valid for: ABAP;Java |

1 Getting Started


This section of the guide contains important information that you need to read before starting your installation process.

End of: ABAP;Java |


1.1 Essential Information: Process and Documentation Overview


This guide contains information specific to SAP ERP only, but you need additional information to perform your installation correctly.

End of: ABAP;Java |


SAP NetWeaver Server Installation Guides

Specifically, you need to use the SAP NetWeaver server Installation Guides (ABAP or Java versions) in parallel to the Installation Guide for SAP ERP 6.0 Including Enhancement Package 8 ABAP and Java. The SAP NetWeaver server Installation Guides contain information on the overall process, tools, the operating system and database, while this guide contains the application-specific information.

The SAP NetWeaver server Installation Guides are organized by database and operating system. For the

installation guides, see SAP Help Portal at help.sap.com/sltoolset System Provisioning Installation Option

End of: ABAP;Java |

Master Guide

● Make sure that you also read the Master Guide for SAP Enhancement Package 8 for SAP ERP 6.0. The Master Guide provides you with the overall view of the implementation process, meaning installation, upgrade or update processes, and with references to important information during implementation.

● Make sure that you collect all the information about planning and implementation processes that is contained in the Master Guide before starting your installation, upgrade, or update project.

● Make sure that you have downloaded the latest version of the Master Guide SAP Enhancement Package 8 for

SAP ERP 6.0 from SAP Service Marketplace at service.sap.com/erp-ehp8-inst .

SAP Enhancement Package 8 for SAP ERP 6.0Getting Started



http://help.sap.com/disclaimer?site=https%3A%2F%2Fhelp.sap.com%2Fsltoolset

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Ferp-ehp8-inst

More Information

You can access documentation for all maintained product releases on SAP Help Portal at help.sap.com/erp

.

Target Release Documentation

The documentation for the target release is not available online in your system until you have completed the upgrade and the installation procedure for the online documentation.

Before the upgrade, ensure that you can read the DVD offline. After the upgrade, you need to install the documentation for the target release.

For SAP Library for SAP ERP 6.0 including SAP enhancement package 8, see SAP Help Portal at help.sap.com/

erp .

SAP Fiori Apps

For more information regarding SAP Fiori apps, see SAP Fiori for SAP ERP in the documentation of SAP ERP on

SAP Help Portal at help.sap.com/erp .

End of: ABAP;Java |


1.2 Installation Information

In addition to the SAP NetWeaver Installation Guides and the application-specific guide, you need to consider the following information specific to SAP Enterprise Resource Planning (SAP ERP):

Media List for SAP Enhancement Package 8 for SAP ERP 6.0

The Media List contains the list of relevant installation media that you need to have available when you start the installation.

For the Media List, see service.sap.com/erp-ehp8-inst Media List for SAP enhancement package 8 for SAP ERP 6.0 .

SAP ERP Server Java installation

NoteYou need to use the Installation Guide - SAP Systems Based on the Application Server Java of SAP NetWeaver 7.5 on <OS>: <DB> in parallel with this guide.

For the SAP NetWeaver server Installation Guides, see help.sap.com//sltoolset Documentation section: System Provisioning Guides for Systems Based on SAP NetWeaver 7.1 and Higher .

End of: ABAP;Java |

6



http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Ferp




http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Ferp-ehp8-inst

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2F%2Fsltoolset

Only valid for: ABAP |

1.3 Installation (ABAP)

In EHP8 there is only one technical usage Central Applications, which contains all new business functions.

End of: ABAP |

1.4 Important SAP Notes


Table 2

Note Number Title Comment

1816819 Dual Stack Support for Business Suite systems

Contains information about a dual-stack split required for the upgrade to SAP Business Suite 7i2016 or SAP NetWeaver 7.5.

2258099 Enhancement package 8 for SAP ERP 6.0: Required SWC

Contains information about the update of required software components.

998833 Release Restrictions SAP ERP 6.0 - Enhancement Packages

Provides information about the limitations for SAP enhancement packages for SAP ERP 6.0.

2171334 EHP8 for SAP ERP 6.0 SP Stacks - Release & Information Note

Contains information and references to SAP Notes for applying Support Package (SP) Stacks of SAP enhancement package 8 for SAP ERP 6.0.

1976498 HRSP Information for HR Renewal 2.0 Provides information on HR Support Packages of SAP enhancement package 8 for SAP ERP 6.0.

774615 Support Package Levels for SAP ERP / SAP ECC Installations and Upgrades

None

1258912 PLM Core 7.00 Release Notes and Information

None

1592495 Information for Portal Content Contains a list of new portal roles and functions that are delivered with SAP enhancement package 6 for SAP ERP 6.0.

1627166 Information about NWBC roles Contains a list of roles for the SAP NetWeaver Business Client (NWBC)




http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2F~form%2Fhandler%3F_APP%3D01100107900000000342%26_EVENT%3DREDIR%26_NNUM%3D1816819%26_NLANG%3Den%26_NVERS%3D0










that are delivered by SAP enhancement package 6 for SAP ERP 6.0.

2167814 SAP Enhancement Package 8 for SAP ERP 6.0: Compatible Add-ons

Contains points to consider when planning to run SAP enhancement package 8 for SAP ERP 6.0 together with an add-on on the same system.

1514967 SAP HANA: Central Note Central SAP Note for SAP In-Memory Appliance (SAP HANA).

1514966 SAP HANA 1.0: Sizing SAP In-Memory Database

Contains information about sizing for the SAP In-Memory Database (SAP HANA).

1793345 Sizing for Suite on HANA Contains suite-specific sizing information for the SAP In-Memory Database (SAP HANA).

1681092 Multiple SAP HANA databases on one appliance

Contains support information and special considerations for multiple SAP HANA databases on a single SAP HANA appliance.

1826100 Multiple applications SAP Business Suite powered by SAP HANA

Contains support information and special considerations for multiple applications on a single SAP HANA system within SAP Business Suite.

1785057 Recommendations for migrating suite systems to SAP HANA

Contains recommendations for migrating suite systems to SAP HANA.

1794297 Secondary Indexes for the business suite on HANA

Contains information about when using secondary indexes is beneficial.

1798895 Additional information for manual ABAP-on-HANA correction process

Contains additional information for manual ABAP-on-HANA corrections.

1855666 Suite on HANA: 3rd party Add-ons Contains information about running specific SAP HANA product versions together with a 3rd party add-on on the same system.

1781986 Business Suite on SAP HANA Scale Out Contains information about scale out scenarios when migrating the SAP Business Suite from any database to SAP HANA Release SPS5.

1881281 Business Suite on SAP HANA content activation problems

Contains information on solutions for SAP HANA content activation problems that occur when nstallating or updating Business Suite on SAP HANA releases.

8
















2048896 Hana Content activation check Contains information about checks to ensure that SAP HANA content is activated correctly.

End of: ABAP;Java |

1.5 Naming Conventions


SAP ECC System and SAP System

In this document, the term “SAP system” means the same as “SAP ECC system”. “SAP” is also used as a synonym for “SAP ECC” in terms such as “SAP start profile” or “SAP system language”.

End of: ABAP |


SAP System ID

In this document, the SAP system ID is abbreviated as “SAPSID” or “sapsid”. If “<sapsid>” is used, your SAP system ID must be in lowercase, for example “prd”. If “<SAPSID>” is used, it must be in uppercase, for example “PRD”.

End of: ABAP |


SAP R/3 Enterprise and SAP ERP Central Component

SAP ERP Central Component is the successor of SAP R/3 Enterprise. It consists of the SAP ERP Central Component Core with SAP ERP Central Component Extension Set. In this document, the following short forms are used:

● “SAP ECC” for “SAP ERP Central Component”

● “SAP ECC Core” for “SAP ERP Central Component Core”

● “SAP ECC Extension Set” for “SAP ERP Central Component Extension Set”

End of: ABAP |


SAP NetWeaver Application Server, SAP Web Application Server, and SAP Basis

SAP NetWeaver 7.0 renames SAP Web Application Server as SAP NetWeaver Application Server. In releases before 6.10, the component was called SAP Basis. In this document, the terms are used as follows:

● The term “SAP NetWeaver Application Server” (or the short form “SAP NetWeaver AS”) is used when referring to Release 7.0 and higher.

● The term “SAP Web Application Server” (or the short form “SAP Web AS”) is used when referring to releases between 6.10 and 6.40.

End of: ABAP |






Usage of Release Names

Unless otherwise specified, the term “release” is used in this document to refer to the release of the SAP ECC system or SAP ERP system. The titles of product-specific sections start with the name of the product, for example, “SAP ECC: Backing Up UI Conversion Classes in ESS”.

The following table explains which release of SAP Basis, SAP Web Application Server, and SAP NetWeaver Application Server corresponds to which release of SAP R/3, SAP ECC and SAP ERP:

Table 3

SAP Basis / SAP Web Application Server / SAP NetWeaver Application Server

SAP ERP

SAP Web Application Server 6.40 SAP ERP 5.0

SAP NetWeaver Application Server 7.0 SAP ERP 6.0

SAP NetWeaver Application Server 7.0 including enhancement package 1

SAP ECC 6.04


SAP ERP 6.05


SAP ERP 6.06



End of: ABAP |

Only valid for: Java |

Instance Name

In this document, <instance_name> is used as a placeholder for the instance name in the instance directory path of your system.

For standalone Java systems, <instance_name> is substituted with J<xx> for the central or dialog instance, where <xx> stands for the instance number.

ExampleIf your instance number is <00>, then the Java instance number is J00.

End of: Java |

End of: ABAP;Java |

10



Only valid for: SAP ERP | ABAP;Java |

2 Process

This section of the guide contains information about process-related application-specific tasks (in some cases, there are no application-specific tasks).

2.1 Dual-Stack Split

Dual-stack systems are no longer supported for the upgrade target SAP enhancement package 8 for SAP ERP 6.0. If your SAP ERP system is currently implemented as a dual-stack system, you need to perform a split. For information on how to perform a dual-stack split, see the following:

● SAP Note1686144

● SAP Note1655335

● Toolset Guides at help.sap.com/sltoolset Documentation section: System Provisioning Split Option .


2.2 Installation Process for SAP HANA

This section provides an overview of the installation process steps for SAP enhancement package 8 for SAP ERP 6.0 to run on SAP HANA. It also provides references to the documentation required for the process steps.

The following table contains definitions of the most important terms used in this section.

Table 4

Term Definition

Installation New installation of an SAP system including an enhancement package. Note that this is different from an update; see definition below.

Update Installation of an enhancement package on an existing SAP system.

The installation process consists of the following steps:

1. Installation of SAP HANA

The SAP HANA appliance software can only be installed by certified hardware partners on validated

hardware running a specific operating system. For more information, see help.sap.com/hana SAP HANA Appliance System Administration and Maintenance Information SAP HANA Technical Operations Manual (TOM) .

SAP Enhancement Package 8 for SAP ERP 6.0Process





http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fsltoolset

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fhana

NoteFor initial sizing, use the Quick Sizer results for database size (DB Disk) and CPU requirements (DB SAPS) as input for SAP HANA Main Memory, disk space and CPU sizing. For the Quick Sizer, see SAP Service

Marketplace at service.sap.com/quicksizer .

Use the Quick Sizer results in combination with the information contained in SAP note 1793345 .

2. Installation of Application Function Libraries (AFLs)

Install the AFLs as described in the SAP HANA Update and Configuration Guide at help.sap.com/hanaSAP HANA SAP HANA Platform Installation and Upgrade Information .

3. Installation of SAP Enhancement Package 8 for SAP ERP 6.0

General Information

○ SAP enhancement package 8 for SAP ERP 6.0, version for SAP HANA is based on SAP NetWeaver 7.5 – Application Server ABAP.

SAP Note 2197259 describes all additional information that you require when upgrading to SAP NetWeaver 7.5.

○ The installation uses Software Provisioning Manager 1.0. Use the latest Software Provisioning Manager 1.0 SP level, which is included in the latest available SL Toolset 1.0 SPS version (see SAP Note 1563579

for SL Toolset 1.0).

○ With SAP enhancement package 8 for SAP ERP 6.0, the HANA content is activated automatically only with SAP NetWeaver AS ABAP 7.5 in combination with SAP HANA.

HANA content is specific to the ABAP stack.

ABAP-specific Information

The installation ABAP Load (export from DVD) contains already all software components on EHP8 Level.

Related Guides

The following table lists the guides you need to use for the installation and where to find them:

Table 5

Guide Use Location

Master Guide for SAP Enhancement Package 8 for SAP ERP 6.0

Contains information on system setup (including how to deploy components not released for SAP HANA, such as Java components).

service.sap.com/erp-inst SAP enhancement packages for SAP ERP

6.0 SAP enhancement package 8 for

SAP ERP 6.0

Software Provisioning Manager 1.0 guide Describes the tool-specific steps needed to perform the installation.

Note that the Software Provisioning Manager has replaced SAPinst as the installation tool.

help.sap.com/sltoolsetDocumentation section: System

Provisioning Installation Option: Guides for Systems Based on SAP

NetWeaver 7.1 and Higher

End of: ABAP;Java |

End of: SAP ERP | ABAP;Java |

12


SAP Enhancement Package 8 for SAP ERP 6.0Process

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fquicksizer


http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fhana



http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Ferp-inst

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fsltoolset

3 Follow-Up Activities

This section of the guide describes application-specific steps that have to be performed after the update or upgrade process is complete.

This section of the guide describes application-specific steps that have to be performed after the installation process is complete.Only valid for: ABAP |

3.1 Implementing SAP ERP ABAP Add-On Components

You can install several add-on components to your SAP ERP ABAP system.

More Information

For a detailed description of how to implement each available SAP ERP add-on component, see the related SAP

Notes on SAP Service Marketplace at service.sap.com/erp-inst SAP ERP 6.0 SAP Enhancement Packages for SAP ERP 6.0 SAP Notes (Enhancement Packages) .End of: ABAP |


3.2 Extended Configuration Management (XCM)

You use Extended Configuration Management (XCM) to configure Web applications once you have installed the Web components. You use it to make configuration settings needed at runtime.

The Web applications are used in the following scenarios:

● ERP E-Commerce

● Auctioning via Web Shop in CRM and ERP

● Utilities Customer E-Services (UCES)

● Interaction Center WebClient

You only need to set up XCM configuration settings for those Web applications that are relevant to the scenarios and processes you are using.

NoteTo be able to use XCM for ERP E-Commerce, you need to have a JCo destination. As of E-Commerce 7.54, JCo connection properties are no longer maintained within XCM. These properties are now specified for a so-called destination that can be created within SAP NetWeaver Administrator (NWA). However, a reference to the respective destination is needed in XCM. The XCM JCo component has been re-designed to support that purpose. The destination can be selected now from a list of destinations that have been created before using

SAP Enhancement Package 8 for SAP ERP 6.0Follow-Up Activities



http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Ferp-inst

NWA. Guide JCo 3.0 in Web Channel 7.54 - Configuration & Migration Help available from SAP Service Marketplace at http://service.sap.com/crm-inst SAP CRM 7.0 Enhancement Package 4 Operatedocuments the configuration steps in more detail.

The XCM user interface is used to configure the Web application in Java. You need to maintain two setting types in XCM:

● General settings

Once set, these settings are valid for the whole Web application. You make these settings in the XCM tool under Start General Application Settings Customer .

● Additional Web application configuration settings

Web applications can have multiple configurations with different settings. Depending on the configuration used, the application behaves differently at runtime. You can define a default configuration or select the configuration to be used at runtime.

CautionNot all applications support multiple application configurations. Some support general settings only.

Some Web applications can run different configurations in different client sessions simultaneously.

Each Web application provides one or more configurations predefined by SAP, which you can find under Start Application Configurations SAP .

You can create a new customer configuration based on these predefined configurations and adjust it to suit your requirements. You then locate your customer configuration under Start Application Configurations Customer . Each customer configuration contains the following:

○ A name for the configuration

○ Base configurations (from SAP on which you base your configuration)

○ A number of configuration parameters with associated values, which you adjust

The final Web application configuration is composed of the combination of these two setting types.

Procedure

The following steps explain how to configure a Web application in XCM, assuming you have installed the application.

Starting XCM

1. You access the XCM tool at http://<host>:<port>/<web app name>/admin/xcm/init.do.

NoteYou can also start XCM in accessibility mode (according to Section 508 of the Rehabilitation Act) at the following URL: http://<host>:<port>/<web app name>/admin/xcm/init.do?sap-accessibility=x.

2. Enter a user and password. If you are logging on for the first time, use the administrator user and password that you defined when installing SAP NetWeaver.

14



RecommendationFor the administration of Web applications, we recommend that you create new users with an authorization level lower than the administrator.

3. When the application opens, a closed UI element tree is displayed on the left-hand side of the screen. A screen containing help information is displayed on the right-hand side.

In XCM, you can use edit mode (change settings) or display mode (view settings). You use the button in the top right corner of the screen to switch between modes. When you switch to edit mode, a database lock is set, meaning that only that user can edit the settings at that time. The lock is released when the user switches back to display mode or after session timeout (default timeout is 30 minutes).

Changing the language

This section describes how to change the language of your application.

You can change the language of your application either by using the XCM UI configuration or by adjusting the web.xml file.

XCM UI Configuration

1. Start the Extended Configuration Management (XCM) Administration page.

2. Select Application Configuration Customer <your application configuration> .

3. Choose Display to display all advanced settings parameters.

4. Choose ui and then, in the language parameter, specify the language you want to use.

5. Restart the application.

Adjusting the web.xml File

1. Navigate to the directory where the application has been deployed.

2. Open the web.xml file (<folder-path-to-application>\servlet_jsp\<application>\root\WEB-INF\web.xml).

3. Check whether the language.isa.sap.com parameter is available. If this parameter is available, the application uses the language specified there.

4. If you want to change the language, you have to define the new language in the language.isa.sap.com parameter and restart the application.

Printable Help

There is a printable help function for the configuration of the application and components. To access it, select Help in the header area of the main XCM Administration window. The documentation contains hyperlinks to more detailed information. The documentation discusses the general settings separately.

General Settings

When you set the general settings, they are valid for the whole Web application. Proceed as follows:

1. Switch to edit mode and choose Start General Application Settings Customer .

The system displays the available nodes categorizing the general settings. Depending on the application, you will have one or more nodes. For more information about the possible settings, see the printable help.

2. Expand a configuration node and select the configuration node on the right-hand side to see possible configuration parameters in the window on the right-hand side.

3. Select a parameter and enter the values that meet your requirements. Each parameter contains a help description with information about what you need to enter.




Some parameters have default values set. When you change the values of these default parameters, the system displays them in orange. You can revert back to the original default entries by selecting R (revert).

4. Choose Save Configuration.

If your Web application does not support multiple configurations, you are now finished with the general settings section. To activate your changes, you can return to display mode and restart the Web application.

If your application supports multiple configurations, see the section “Multiple Application Configurations” below.

Multiple Application Configurations

Once you have made the general settings, you can configure the various configurations that you need.

Standard SAP Configuration

You need to identify which SAP application configurations are standard. In more complex applications, such as ERP E-Commerce, there are several pre-configured applications. In simpler applications, such as the user management application, there are normally fewer application configurations; possibly only one. You display the list of pre-configured scenarios under Start Application Configurations SAP in the UI element tree. Search the configurations and choose the one that most suits your requirements.

Create a Customer Application Configuration

Once you have selected a configuration, switch to Edit mode.

1. Enter a configuration Name and choose Create.

2. Link configuration data to the configuration parameters. The last column of the parameter table contains a description of the scenario of each configuration parameter.

NoteDuring installation, only those parameters that are needed to get the application running need to be displayed. To view and edit optional parameters, choose Display Advanced Settings .

Configure a Customer Application Configuration

Once you have created the application configuration, you need to configure it by changing the parameter values.

1. Select Configuration Documentation to see a list of the parameters to be configured.

2. Select a parameter and use the dropdown list box to assign a value. Choose the ? help button next to the dropdown list box to display a description of possible values. If there are other detailed descriptions for a parameter, an additional ? button is displayed.

3. There are two value types:

○ Static values

Values that can be selected from a dropdown list box.

These values do not have a button in the Component Configuration column.

○ Values based on component configuration

You must first configure a component, such as a connection to your SAP CRM system, before you can assign the configured value to the parameter. These parameters have a button in the Component Configuration column. For example, there is a jco button for configuring connection parameters to the SAP system.

If no value is assigned to these parameters, you need to create a new component configuration. For more information, see the section “Creating a New Component Configuration”.

If a value is assigned, it is likely that you will not need to make any changes during the installation.

Creating a New Component Configuration

16



A component is an independently configurable part of the application (for example, the jco component that enables connections between the SAP system and the Web application). A component can have several configurations, for example, for different systems and clients. You assign one of the component configurations to the parameter in the application configuration. We recommend that you create the component configuration at the same time as you set up the application configuration.

1. Select an empty entry in the dropdown list box for the parameter, or choose ** Select to create component configuration **. The system switches to the component creation screen. The correct component (for example, jco) is selected automatically and the system displays a description of the use of the component.

2. Enter a name for the component configuration (for example, Q5C_505 for the Q5C system in client 505) and choose Create. The application switches to the component configuration details screen.

3. Select a base configuration from the Base Configuration dropdown list box. Choose the ? button, to display a description.

4. Enter values for the component configuration parameters and choose Save Configuration. Test your values in the Configuration Test area.

Testing a Component Configuration

Once you have created the component configuration, save it and test it as follows:

1. Select the test for the configuration from the Select Test dropdown list box. Choose the ? button, to display a description.

2. Choose Run Test.

3. The system displays the test results in a new window. A red traffic light indicates that the test failed and you need redo the configuration. A green traffic light indicates that the test was successful.

4. Select Back to Application Configuration, to return to the application configuration. Select the newly created configuration from the dropdown list box, and assign it to the scenario parameter.

Defining a Default Application Configuration

You perform this step after you have assigned values to all configuration parameters. If you have only one application configuration, the system will use it automatically when you start the application. If you have more than one application configuration, you need to select the Default Configuration checkbox for one of the configurations so that the system will run this one as the default when you start the application.

NoteA green icon in the UI element tree indicates the default configuration.

Saving the Application Configuration

Once you have assigned values to all your application configuration parameters, you need to save the configuration.

1. Choose Save Configuration.

2. Select the Active Configuration checkbox to enable the configuration. If you do not select this checkbox, the configuration will be disabled and will not run when you start the application.

NoteA red icon indicates that the configuration is disabled.

3. The system saves the new application configuration to the SAP NetWeaver Application Server 7.0 and it can then be displayed in the customers section of the UI element tree in XCM.

Activating the Application Configuration




Before a new application configuration can become active, you need to either stop and restart the Web application or restart the SAP NetWeaver Application Server Java.

1. Go to SAP NetWeaver Administrator using the following URL: <hostname_of_Java

EE_Engine_Server>:<Instance_Number>00/nwa

2. Go to the Operations tab.

3. Choose Start & Stop.

○ To start and stop Java applications, go to the Java Applications tab.

○ To start and stop Java application server instances, go to the Java Instances tab.

Running the Web Application

When you run the Web application, if there is more than one application configuration, you need to specify which one is to be used. You can specify this as follows:

● Use the default configuration. Start the application and the configuration you set as the default will be used. If you have only one configuration, it will be the default automatically. For example, if you want to call the default configuration for the B2B Web shop, the corresponding URL is: http://<host>:<port>/b2b/b2b/init.do.

● Specify the application configuration name as a request parameter. In this case, you run the application using an application configuration that is not the default. You use the request parameter scenario.xcm to transfer the name of the application configuration when you call the application. The scenario name is case sensitive. For example, if you want to call the application configuration B2BCRM, the corresponding URL is: http://<host>:<port>/b2b/b2b/init.do?scenario.xcm=B2BCRM.

● Display a home page that contains links to all active configurations and uses the appropriate link to start the specific application configuration.

CautionThe home page is disabled after installation. You use the following XCM parameters to enable it: StartGeneral Settings < Web application name> show.start.jsp .

Uploading and Downloading XCM Settings

You can upload and download application configurations. In XCM, choose Start XCM Settings and you can view the upload and download sections. Each section refers to the following two objects:

● Component configuration data

● Application configuration data

These two objects make up the application configuration of a Web application.

Downloading XCM Configurations

This enables you to download an XCM configuration from the SAP NetWeaver Application Server 7.0 database to XML files. Proceed as follows:

1. Choose the download button for the component configuration data file. The system generates a file named config-data.xml that contains all component configuration data saved for the Web application.

2. Choose the download button for the application configuration data file. The system generates a file named scenario-config.xml that contains all application configuration data saved for the Web application.

Uploading XCM Configurations

18



http://help.sap.com/disclaimer?site=http%3A%2F%2F%3Chostname_of_Java%20EE_Engine_Server%3E%3A%3CInstance_Number%3E00%2Fnwa

http://help.sap.com/disclaimer?site=http%3A%2F%2F%3Chostname_of_Java%20EE_Engine_Server%3E%3A%3CInstance_Number%3E00%2Fnwa

This function enables you to upload XCM configuration data from XML files to the SAP NetWeaver Application Server 7.0 server. Proceed as follows:

1. Choose Edit.

2. The system displays two file input fields in the Upload section.

3. Specify the config-data.xml (component configuration) and scenario-config.xml (application configuration) files, with complete file system paths for both files, and choose Upload.

NoteFor the B2B and B2C Web applications in ERP E-Commerce, the XCM administration tool provides a switch to a separate maintenance view for the IPC-specific part of the application (see “IPC Switch for XCM Configuration of ERP E-Commerce”, below). When switching to IPC, you can upload and download the IPC application configuration and component configuration. The IPC application configuration file is ipcscenario-config.xml; the component configuration file is ipcconfig-data.xml.

CautionAfter migrating XCM settings from an older to a newer Web application version, you need to check whether any of the customer XCM settings are obsolete (see “Indication of Obsolete XCM Settings” below). The new version may require you to change XCM settings, or give you the option of maintaining additional XCM settings. You add these settings manually, as described in the section “Configure a Customer Application Configuration” above.

4. Assign passwords to the individual files.

After you have uploaded the config-data.xml file, you have to enter the XCM passwords anew. Otherwise you cannot perform the test successfully.

Indication of Obsolete XCM Settings

After migrating XCM settings from an older version to a newer Web application version, some settings may no longer be supported in the new version. If these settings were made by the customer, meaning that they have been changed from the default values provided by SAP, the system will highlight them in yellow to indicate them as obsolete. The following parameters can be specified as obsolete:

● Application configurations (exclamation mark on a yellow background)

● Application configuration parameters (highlighted in yellow)

● Components (exclamation mark on a yellow background)

● Component configurations (exclamation mark on a yellow background)

● Component parameters (highlighted in yellow)

IPC Switch for XCM Configuration of ERP E-Commerce

The ERP E-Commerce B2B and B2C Web applications each support two application configurations that must be maintained separately:

● The E-Commerce application configuration, which allows the configuration of the overall application

● The IPC application configuration, which allows additional configuration of the IPC-specific part of the application

When you start the XCM administration tool for B2B or B2C, a dropdown list box is displayed in the upper left-hand corner of the screen. This dropdown list box enables you to switch between the maintenance views for the E-Commerce and IPC application configurations. All features of the XCM administration tool, meaning the




maintenance, upload, and download of application configurations, can be used separately for both the E-Commerce and IPC application configurations.

End of: Java |


3.3 Basic Settings for ERP E-Commerce


3.3.1 Creating a Back-End User

You need service users to provide the anonymous remote function call (RFC) stateless connection between your back-end system and your Web-based applications.

Prerequisites

You have installed and configured ERP E-Commerce Web-based applications.

Procedure

You create a service user in your back-end ERP system and assign it to the Web-based application as follows:

1. In your ABAP back-end system, from the SAP Easy Access Menu, choose Tools Administration User Maintenance Users (transaction SU01).

2. Create a user of the type Service User and enter all required data.

3. Assign the appropriate service user authorization role to the user on the Roles tab. For a list of service user roles for the various Web-based applications, see the following table:

Table 6

Application Authorization Role for Service User

B2C SAP_ISA_B2C_RFC

B2R SAP_ISA_B2B_RFC

Shop Management SAP_ISA_SHOPMGMT_RFC

User Management SAP_ISA_UADM_RFC

4. Save your entries.

End of: Java |

20




3.3.2 Checking the Connection to the ABAP System

This section describes how to check the connection to the ABAP system.

Prerequisites

To be able to test the connection to the ABAP system, you need to create a user [external document] on this system.

Procedure

1. Open the user interface for the Extended Configuration Management (XCM) Administrator as follows:

1. Open a Web browser and enter the following URL:

http://<J2EE_host>:<J2EE_port>/<context root>/admin/xcm/init.dowhere <context root> is the context root of the application.

To find information about the components that can be configured, choose help.

2. Log on with the previously created user.

3. Choose Start Component .

You can find information about configuration of components on the right-hand side of the screen.

4. To create a JCo component, follow the instructions provided above.

5. Execute the run test operation for the JCo component. If this is successful, the ABAP system can be reached from the Java system.

More Information

For more information about using Extended Configuration Management (XCM) to configure your application, see Extended Configuration Management (XCM) [external document].

End of: Java |


3.3.3 Configuring the TREX Service

You need to configure and check the Search and Classification (TREX) service.




Procedure

To configure the TREX service, you have to do the following:

1. Start SAP NetWeaver Administrator (NWA).

2. Choose tab Configuration Infrastructure Java System Properties .

3. Choose tab Service and filter for TREX Service.

4. Maintain the values for nameserver.address and nameserver.backupserverlist in the details table.

For more information, see Specifying the Address of the TREX Name Server in the TREX installation guide at:

service.sap.com/instguides SAP NetWeaver SAP NetWeaver <version> Installation Installation - Standalone Engines SAP NetWeaver Search and Classification TREX Installing and Updating TREX 7.1 Single Host .End of: Java |

End of: Java |


3.4 Basic Settings for Java-Based Web Applications


3.4.1 Checking the Availability of SAP ERP Biller Direct

After installing your SAP system, you check the availability of SAP ERP Biller Direct (BD).

Procedure

Open a Web browser and enter the following URL:

http://<J2EE_host>:<J2EE_port>/bd.

A message is displayed asking you to configure the application using Extended Configuration Management (XCM). This message also indicates that BD is available.

NoteIf you want to configure BD using XCM, enter the following URL in your browser:

http://<J2EE_host>:<J2EE_port>/bd/admin/xcm/init.do

More Information

Biller Direct is used in various electronic bill presentation and payment processes, such as FI-AP: Electronic Bill Presentment and Payment or FI-AR: Electronic Bill Presentment and Payment (B2B)

22



http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Finstguides

For more information about how to configure BD using XCM, see the configuration documentation for these processes in SAP Solution Manager.

This documentation is also available in SAP Library at help.sap.com SAP ERP SAP ERP Enhancement Packages <language> SAP ERP Central Component Financials SAP Financial Supply Chain Management (FIN-FSCM) Electronic Bill Presentment and Payment .

.End of: Java |


3.4.2 Checking the Availability of SAP ERP Utility Customer E-Services

After installing your SAP system, you check the availability of SAP ERP Utilities Customer E-Services (UCES).

Procedure


http://<J2EE_host>:<J2EE_port>/bdisu.

A message is displayed asking you to configure the application using Extended Configuration Management (XCM). This message also indicates that UCES is available.

NoteIf you want to configure UCES using XCM, enter the following URL in your browser:

http://<J2EE_host>:<J2EE_port>/bdisu/admin/xcm/init.do.

For more information about UCES, see SAP Note 1251875 .End of: Java |


3.4.3 Checking the Availability of Mobile Web Dynpro Java Applications for SAP Retail Store

After installing your SAP system, you check the availability of mobile Inventory Management applications with Web-Dynpro Java for SAP Retail Store (IS-R-SRS).

Procedure


http://<J2EE_host>:<J2EE_port>/webdynpro/dispatcher/sap.com/is~isr~srs~men~app/MainApp.




http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com


If the start page of IS-R-SRS appears in the browser, this indicates that IS-R-SRS are available.

NoteIf you want to configure IS-R-SRS, enter the following URL in your browser:

http://<host>:<port>webdynpro/dispatcher/sap.com/tc~wd~tools/Explorer

For more information about IS-R-SRS, see SAP Note 1070682 .End of: Java |


3.4.4 Checking and Configuring the Installation of SAP ERP Learning Solution – Content Player

To check whether the installation of SAP ERP Learning Solution – Content Player (LSOCP) was successful, you need to make sure that you can access the Configuration Content Player Web page. Then you can configure LSOCP.

Procedure

Performing the Installation Check

1. Open a Web browser.

2. Enter the following URL:

http://<J2EE_host>:5<Instance_Number>00/lms/mediator/config.

If the installation was successful, you see the Configuration Content Player Web page.

You can now start configuring LSOCP.

Accessing Configuration Documentation

For extensive configuration documentation, see SAP Solution Manager <project name> SAP ERPScenarios Human Capital Management Processes in ERP Business Processes Managing Enterprise Learning Strategies .End of: Java |

End of: Java |

24




Typographic Conventions

Table 7

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.

Example Example Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ● Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

● Cross-references to other documentation or published works

Example ● Output on the screen following a user action, for example, messages

● Source code or syntax quoted directly from a program

● File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

SAP Enhancement Package 8 for SAP ERP 6.0Typographic Conventions



http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.sap.com



26

PUBLIC© Copyright 2016 SAP SE or an SAP affiliate company.All rights reserved. SAP Enhancement Package 8 for SAP ERP 6.0

www.sap.com

© Copyright 2016 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. All other product and service names mentioned are the trademarks of their respective companies. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

http://www.sap.com

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

Documents

SAP Enhancement Package 8 for SAP ERP 6