SAP Master Data Management Guide

Installation Guide SAP NetWeaver Master Data Management Global Data Synchronization Option 2.1 Target Audience ‡Ù˜Š Technical Consultants ‡Ù˜Š System Administrators

PUBLIC ‡Ù˜ð3Xï“7¼l©K4Ø¥ˆTÍs[XeÃ\fØ÷sŒÜ¹ëíòö�°5.¡gfix)�“æW¯¯…ıßæÞt‹’´9z

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document. You can find the latest version at the following location: http://service.sap.com/ instguides. The following table provides an overview of the most important document changes. Version

Date

Description

1.0 1.1 1.2

2010-05-31 2011-12-07 2012-06-30

Initial version Support Package 2 version. Help Portal paths corrected. Other updates. Updates in chapter Editing in Application Properties.

2/38

PUBLIC

2012-06-30

Table of Contents

Chapter 1

SAP NetWeaver MDM GDS: GDS Console Installation Guide . . . . . . . . . . 5

Chapter 2

GDS Console Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 3

Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 4 4.1 4.2 4.2.1 4.2.2 4.3 4.3.1 4.3.2 4.4 4.5

Installing the GDS Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the GDS Console in Standalone Mode . . . . . . . . . . . . . . . . . . . . . . . Installing the GDS Console in Portal Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the GDS Console in Distributed Portal Mode . . . . . . . . . . . . . . . . . . Installing the GDS Console in Non-Distributed Portal Mode . . . . . . . . . . . . . . Deploying the GDS Console Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deploying the GDS Console in Standalone Mode . . . . . . . . . . . . . . . . . . . . . . Deploying the GDS Console in Portal Mode . . . . . . . . . . . . . . . . . . . . . . . . . . Editing the Application Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring Portal Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 5

Configuring Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 6

Checking the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Chapter 7

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter A A.1

Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 The Main SAP Documentation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2012-06-30

PUBLIC

11 11 12 12 13 14 14 15 15 21

3/38

This page is left blank for documents that are printed on both sides.

1

SAP NetWeaver MDM GDS: GDS Console Installation Guide

1 SAP NetWeaver MDM GDS: GDS Console Installation Guide

The GDS Console is a mandatory component of the SAP NetWeaver MDM GDS business scenario, enabling users to: ø£½o˛D Retrieve information from back end SAP ERP or MDM systems, for processing on the GDS Console ø£½o˛D Create, enhance, maintain, and store specific data on the GDS Console ø£½o˛D Register and publish data to the data pools and the Global Registry ø£½o˛D Manage publication of item data between suppliers and their trade partners This manual describes how to install the SAP NetWeaver MDM GDS Console.

2012-06-30

PUBLIC

5/38

This page is left blank for documents that are printed on both sides.

2

GDS Console Overview

2 GDS Console Overview

Use

The GDS Console is a Java-based application running on the SAP NetWeaver Application Server (Web AS) Java, which is the main interface of SAP NetWeaver MDM GDS. Connected to the back-end system through SAP NetWeaver Process Integration (PI) connectors, the GDS Console imports item data for enhancement and storage, registration with the data pools and Global Registry, and subsequent publication to trade partners. Components

The GDS Console operates with the following components to execute processes within the SAP NetWeaver MDM GDS business scenario: 1æ¤fiN MDM Server and Database The GDS Repository is stored on the MDM Server. It includes the functionality required for backup and restoration, and metadata management. 1æ¤fiN MDM Console An MDM application used to administer and monitor the MDM Server software, and for creating, backing up, and restoring repositories on MDM. 1æ¤fiN SAP NetWeaver Process Integration (PI) non-central J2EE Adapter Engine and PI AS2 Adapter (by Seeburger) Responsible for the secure transfer and synchronization of messages between the GDS Console and the data pools. SAP NetWeaver PI is also used to transfer data between the back-end system and the GDS Console. 1æ¤fiN ERP Back End System Creates the items and transfers the initial data and item status changes to the GDS Console through a system of messages. 1æ¤fiN SAP EHP1 for SAP NetWeaver CE 7.1 Java Stack (with SAP NetWeaver Portal Core - optional) The GDS application runs on the SAP NetWeaver Java stack as a Web Dynpro application. The GDS portal content can be deployed to the server if you select the “Portal Core” option. GDS is made available as a workset in SAP NetWeaver Portal Core, thereby utilizing the portal features of single sign-on and role based access. This is optional. The GDS application can also run in standalone mode without the SAP NetWeaver Portal Core. The figure below illustrates a typical minimum SAP NetWeaver MDM GDS technical landscape:

2012-06-30

PUBLIC

7/38

2

GDS Console Overview

mhD;?Luflšfiõžþ*–Op⁄“

8/38

PUBLIC

2012-06-30

3

Preparing for Installation

3 Preparing for Installation

Before installing the GDS Console, be sure that you have performed all prerequisite procedures outlined in the master guide for SAP NetWeaver MDM GDS. For more information, see SAP Service Marketplace at http://service.sap.com/instguides Industry Solutions Industry Solution Guides SAP for Consumer Products SAP MDM GDS 2.1 . NOTE

The versions of all MDM components must be compatible with the required version of the GDS Console. The minimal system requirements for the GDS Console are listed in the following table: CPU Memory Storage Network topology Operating system AS Java

Dual Xeon 2.0 GHz with 533 MHz + FSB 2 GB RAM 18 GB TCP/IP-based network All SAP EHP1 for SAP NetWeaver PI 7.1 released operating systems and databases Installed as part of SAP NetWeaver PI Adapter Engine Version must be at least SAP EHP1 for SAP NetWeaver PI 7.1 Adapter Engine SP04 P1 Installed as part of SAP NetWeaver PI Adapter Engine J2EE Adapter Engine (component of SAP NetWeaver Version must be at least SAP EHP1 for SAP NetWeaver PI 7.1 Adapter Engine Process Integration) SP04 P1 CAUTION

EP Basis (Enterprise Portal Basis components - Optional – only if the user uses the application in portal mode)

The GDS Console must be installed on the same server. Installed as part of SAP EHP1 for SAP NetWeaver CE 7.1 SP04 P1 CAUTION

The GDS Console must be installed on the same server.

Before you begin installing the GDS Console, perform these preparatory steps: 1. Check that all the files required for installing the GDS Console are available on your installation media. For more information, see Deploying the GDS Console Application [page 14]. 2. Ensure that the MDM Server is running. 3. Create an MDM repository on the MDM Server that will be used by the GDS Console to store trade items and other application data, as follows: 1. Copy the repository archive file \\DATA_UNITS\MDM_CONTENT_GDS \GDS_21__INITIAL_REPOSITORY.A2A from the installation media to the Archives

2012-06-30

PUBLIC

9/38

3

Preparing for Installation

folder of your MDM Server. On a Windows platform, you can find this folder in the following path: \\\sapmnt\\MDS\mdm\archive NOTE

2. 3.

4.

There are two repositories delivered as part of MDM content, one for 1Sync data pool and other one for SA2 data pool. Choose the right repository based on which data pool you want GDS to interact with. Start the MDM Console, mount the MDM Server, and unarchive the repository archive. Connect to the repository with the following credentials: CÿÈô&E User name: Admin CÿÈô&E Password: abc123 Load the repository with indexes.

NOTE

For more information, see the console reference guide on SAP Service Marketplace at http:// service.sap.com/installmdm SAP NetWeaver MDM 7.1 Reference Documentation MDM 7.1 Console Reference Guide .

10/38

PUBLIC

2012-06-30

4

Installing the GDS Console

4.1

Installing the GDS Console in Standalone Mode

4 Installing the GDS Console

You can install the GDS Console in standalone and Portal mode. Procedure

Installing the GDS Console entails performing the following procedures: 1. Deploying the GDS Console Application [page 14] 2. Editing the Application Properties [page 15] 3. Configuring Portal Settings [page 21]

4.1 Installing the GDS Console in Standalone Mode If you are installing the GDS Console in standalone mode, you can access it without the Portal. The figure below summarizes the system installation in standalone mode.

I:t¥@cŽv�»z'¦ Õ²=ˇÓb

If you are using GDS in standalone mode, you must install the SAP NetWeaver J2EE Adapter Engine. The non-central J2EE Adapter Engine is an SAP NetWeaver Process Integration component. Additionally, the following prerequisites apply:

2012-06-30

PUBLIC

11/38

4

Installing the GDS Console

4.2

Installing the GDS Console in Portal Mode

Xõ ã>( SAP EHP1 for SAP NetWeaver PI 7.1 Adapter Engine stack are installed and configured according to the installation guide provided for SAP NetWeaver PI Adapter Engine. For more information, see http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver Process Integration 7.1 Installation Installation - Standalone Engines Adapter Engine (Java EE) on for SAP NetWeaver 7.11 . Xõ ã>( Once the J2EE adapter engine is installed, patch the system to SAP EHP1 for SAP NetWeaver PI 7.1 SP04 Patch 1 or higher according to the SAP NetWeaver patch guides. For more information about patch guides, see http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver Process Integration 7.1 Maintenance .

4.2 Installing the GDS Console in Portal Mode If you install the GDS Console in Portal mode, you can access it through the Portal. GDS supports two installation options in Portal mode.

4.2.1 Installing the GDS Console in Distributed Portal Mode The figure below summarizes the system installation recommended by SAP in distributed Portal mode.

Xõ ˙ás– C3|oflgÞ$ ÿ

In distributed Portal mode, the SAP NetWeaver Portal Core component and the GDS UI can be deployed on one J2EE server (GDS Portal instance), and GDS core and other required components can be deployed on another J2EE server (GDS standalone instance). GDS UI deployed on the Portal instance remotely communicates with the GDS standalone instance. NOTE

When you install SAP NetWeaver CE, the ’CompPlatform Standard System’ installation includes the Enterprise Portal Basis (EP Basis) components, so no separate portal installation is required.

12/38

PUBLIC

2012-06-30

4

Installing the GDS Console

4.2

Installing the GDS Console in Portal Mode

The EP Basis components are part of usage type 'Composition Platform'. For more information, see SAP Note 1229080. If you use GDS in distributed Portal mode, first install the GDS standalone instance as described in Installing the GDS Console in Standalone Mode [page 11]. Then, make sure that the following prerequisites are fulfilled for the GDS Portal instance: NÞsXdü SAP EHP1 for SAP NetWeaver CE 7.1 is installed and configured as described in the installation guide provided for SAP NetWeaver composition environment. For more information, see http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver Composition Environment SAP EHP1 for SAP NetWeaver CE 7.1 Installation Installing the CE Server (64-Bit) . NÞsXdü Once SAP NetWeaver Composition Environment is installed, patch the system to SAP EHP1 for SAP NetWeaver CE 7.1 SP04 Patch 1 or higher according to the SAP NetWeaver patch guides. For more information about patch guides, see http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver Composition Environment SAP EHP1 for SAP NetWeaver CE 7.1 Maintenance .

4.2.2 Installing the GDS Console in Non-Distributed Portal Mode The figure below summarizes the system installation recommended by SAP in non-distributed Portal mode.

NÞs¾A5 Š¨ÂzA«ŸÎ×)6q

2012-06-30

PUBLIC

13/38

4

Installing the GDS Console

4.3

Deploying the GDS Console Application

In non-distributed Portal mode, SAP NetWeaver Portal Core component, GDS UI, GDS core, and other required components are deployed on single J2EE server. NOTE

When you install SAP NetWeaver CE, the ’CompPlatform Standard System’ installation includes the Enterprise Portal Basis (EP Basis) components, so no separate portal installation is required. The EP Basis components are part of usage type 'Composition Platform'. For more information, see SAP Note 1229080. If you use GDS in non-distributed Portal mode, the following prerequisites apply: ã½ Â+¹ SAP EHP1 for SAP NetWeaver CE 7.1 is installed and configured as described in the installation guide provided for SAP NetWeaver composition environment. For more information, see http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver Composition Environment SAP EHP1 for SAP NetWeaver CE 7.1 Installation Installing the CE Server (64-Bit) . ã½ Â+¹ Once J2EE adapter engine is installed, patch the system to SAP EHP1 for SAP NetWeaver CE 7.1 SP04 Patch 1 or higher according to the SAP NetWeaver patch guides. For more information about patch guides, see http://service.sap.com/instguides SAP NetWeaver SAP NetWeaver Composition Environment SAP EHP1 for SAP NetWeaver CE 7.1 Maintenance . ã½ Â+¹ Deploy XI Adapter Framework, XI Adapter Framework Component, and Messaging System Service components located at http://service.sap.com/instguides Downloads SAP Support Package Support Packages and Patches - Entry by Application Group SAP NetWeaver SAP NetWeaver SAP EHP1 for SAP NW PI 7.1 Entry by Component Adapter Engine (Java EE) .

4.3 Deploying the GDS Console Application 4.3.1 Deploying the GDS Console in Standalone Mode Using the SAP Java Support Package Manager (JSPM), deploy the GDS Console application to the GDS host. NOTE

You must deploy the GDS Console application using the JSPM tool. Choose the option New Software Component. Procedure

Use the following files, in the following order, to deploy the GDS Console application to the GDS host: 1. GDSCORE00_0.sca 2. GDSUI00_0.sca

14/38

PUBLIC

2012-06-30

4

Installing the GDS Console

4.4

Editing the Application Properties

3. 4.

GDSTOOLS00_0.sca GDSDDIC00_0.sca CAUTION

If you have an existing GDS 1.0 or GDS 2.0 installation, do not deploy this SCA.

4.3.2 Deploying the GDS Console in Portal Mode Procedure Deploying the GDS Console in Distributed Mode

In the GDS standalone instance, deploy the files as described in Deploying the GDS Console in Standalone Mode [page 14]. In the GDS Portal instance, deploy the following files: GDSUI00_0.sca GDSPORTAL00_0.sca Deploying the GDS Console in Non-Distributed Mode

Deploy the files as described in Deploying the GDS Console in Standalone Mode [page 14], followed by the following file: GDSPORTAL00_0.sca

4.4 Editing the Application Properties Prerequisites

The GDS application has been installed on the J2EE engine. Procedure

1. Log on to SAP NetWeaver Administrator at http://:/nwa. 2. Choose Configuration Management Infrastructure Java System Properties . 3. Select the Applications tab in the Details section 4. Filter the table for is~gds~core~app. 5. Set the parameters for the application properties file according to the table below and edit data. To ensure that changes take effect in the SAP NetWeaver Administrator, restart the J2EE engine. NOTE

Application properties marked bold are mandatory to be set by the customer in order to get the GDS Console up and running. Application Properties

2012-06-30

PUBLIC

15/38

4

Installing the GDS Console

4.4

Editing the Application Properties

Application Property

Default

Description

AUTOMATIC_PUBLICATION_RESTRICTIONS_

ßÆ¥r‰ TMDataInformationProvi der ßÆ¥r‰ GlobalDataBrandName ßÆ¥r‰ GlobalDataGlobalItemClassifi cation true

List of fields on which the user can specify restrictions against a partner or partner group for automatic publication.

MDM_FIELDS

AutomaticRegistrationFlag

DataPoolTimeZone DestinationDataPoolGln

GDS.CatalogManagementEnabled

GDS.DataPoolType GDS.FieldsToPropagate

GDS.IS_AUTOMATIC_PUBLISHING_ENABLED

GDS.MAX_PASSWORD_LENGTH

GDS.MIN_PASSWORD_LENGTH

GDS.PropagateBasedOnMaterialNumber

Example

Flag for automatic true registration UTC Datapool time zone The GLN of the source data pool for which the current GDS instance is configured false Show the button true required for catalog maintenance 1Sync Datapool type ßÆ¥r‰ 1Sync ßÆ¥r‰ SA2 List of fields for which ßÆ¥r‰ GlobalDataBrandName changes can be propagated when an ßÆ¥r‰ GlobalDataBrandOwner item at the top level is TMDatamodified. Note that an ßÆ¥r‰ CountryOfOrigin asterisk (*) means propagating all ßÆ¥r‰ TMDataFunctionalName attributes. ßÆ¥r‰ TMDataPartnerSpecificDa taStartAvailabilityD ate true Flag to enable or disable ßÆ¥r‰ true automatic publication ßÆ¥r‰ false at system level 12 Maximum length of the password 5 Minimum length of the password true Flag to indicate whether ßÆ¥r‰ true values for the fields ßÆ¥r‰ false specified in application property GDS.FieldsToPropagate

should be propagated based on items with the

16/38

PUBLIC

2012-06-30

4

Installing the GDS Console

4.4

Editing the Application Properties

Application Property

GDS.SA2ContentVersion GDS.SA2TransactionSchemaLocation

GDS.SchemaLocation

GDS.Server

GDS.SystemUser

GDS.SystemUserPassword GDS.VALIDATION_AUTOMATIC_PUBLISHING_ IS_ITEM_AUTOMATIC_PUBLISHABLE

GDS.VALIDATION_AUTOMATIC_PUBLISHING_ IS_PUBLICATION_TYPE_INITIAL_LOAD

GDS.Version GDSN_HEADER_VERSION

GDSN_PROVIDER_GLN GDSN_PROVIDER_ID LOCAL_EJB_ACCESS_ENABLED

LOCKED_DOWN_ATTRIBUTES

MDM.AdminName

MDM.AdminPassword

2012-06-30

Default



Description

http://www.preprod. 1sync.org/schemas/ item/1.0/ CatalogueRequestProx y.xsd localhost Location of the GDS Server GDSAdmin Special technical user of the GDS application abc123 Password of the GDS system user VALIDATION_TO_BE Name of the validation _ that identifies items that USED_ONLY_BY_ must be published AUTOMATIC_ automatically PUBLICATION VALIDATION_TO_BE Name of the validation _ that specifies which USED_ONLY_BY_ publication type must AUTOMATIC_ be used in automatic PUBLICATION publication 2.1 Version of GDS 1.0 GDSN Header information version GDSN Provider GLN GDSN Provider ID true Flag for enabling EJB access GlobalData;BaseUnitIn List of locked down dicator;GlobalData;Qt attributes yOfNextLevelItems;Gl obalData;ConsumerU nitIndicator;GlobalDat a;SpecialItemCode Admin Name of the MDM Administrator abc123 Password of the MDM Administrator

PUBLIC

Example

same material number or on all the items under it. SA2 content version SA2 transaction schema location 1Sync Schema location

localhost

2.0 1.0

true

17/38

4

Installing the GDS Console

4.4

Editing the Application Properties

Application Property

Default

Description

MDM.AdminRole

Admin

MDM.DatabaseServer

localhost

MDM.DatabaseType

MS_SQL

MDM.Import.DateFormat

MM/dd/yyyy

MDM.Import.DateTimeFormat

yyMMddHHmmss

MDM.Import.MuliValueFlatLookup

A

MDM.Import.MuliValueQualifiedLookup

A

MDM.Import.R3SystemID

R3 5

Name of the MDM Administrator role Location of the MDM server Type of the MDM pV7œP2 MS_SQ database L pV7œP2 MaxDB pV7œP2 IBM_D B2 Date format in which data come from ERP Date-time format in which data come from ERP Multivalue lookup A append (A) or Overwrite (O) Qualified lookup A append (A) or Overwrite (O) ID of the R3 system Maximum number of 5 failed password attempts Name of the region Name of the repository Location of the MDM server Location of the PI server Version of the PI server 7.1 Time in minutes to wait for the response message from the data pool before setting the status to error Delay time starting the 5000 automatic registration process after processing the import message. Time in milliseconds to 60000 wait after sending out an automatic publication after having received a correct response from the Data Pool (useful for

MDM.NumberOfFailedPasswordRetries

MDM.repositoryName

English [US] gds

MDM.server

localhost

PI.Server

localhost 7.1 15

MDM.RegionName

PI.Version TIME_IN_MINUTE_TO_WAIT_FOR_RESPONSE_ FROM_DATAPOOL

GDS.AUTO_REG_DELAY_AFTER_IMPORT

0

GDS.AUTO_PUB_DELAY_AFTER_CORR_RESPONSE

300000

18/38

PUBLIC

Example

2012-06-30

4

Installing the GDS Console

4.4

Editing the Application Properties

Application Property

UI.ResultList.DefPageSize

UNITTEST.initialcontextserverhostname

UNITTEST.initialcontextserverport

VALIDATION.GTIN

VALIDATION.PUBLICATION_VALIDATION_ROLE

VALIDATION.REGISTRATION_VALIDATION_ROL E VALIDATION.PRICE_TYPE_PUBLICATION_ VALIDATION_ROLE

VALUE_RESTRICTIONS_MDM_FIELDS

VALUE_RESTRICTIONS_OPERATIONSLIST

2012-06-30

Default

Description

Example

example to wait for the registration of the whole hierarchy before automatic publication takes place) 500 The default page size on the result list of the Item Maintenance screen. Possible values: 100, 500, and 0; where 0 means unlimited page size. 127.0.0.1 Host name of unit test initial context server 53004 Port number of unit test initial context server { External validation for OneSyncValidationsBe validating GTIN format an}validateGtin default value is empty Restrict the external Admin validations executed before publication to the validations of the role specified here default value is empty Registration validation role default value is empty Contains the name of Admin the role containing the validations before the price type publication is started List of fields (only from sŒi¿  TMDataInformationProvi the TMData and der GlobalData tables) on which you want to sŒi¿  TMDataTargetMarket define value restrictions. You may add or remove sŒi¿  GlobalDataBrandName fields. GlobalDatasŒi¿  BrandOwner sŒi¿  MODIFY_ITEM Allowed list of GDS sŒi¿  PUBLISH_ITEM operations for which a sŒi¿  REGISTER_ITEM value restriction can be sŒi¿  REPUBLISH_ITE specified M sŒi¿  UNPUBLISH_ITE M

PUBLIC

19/38

4

Installing the GDS Console

4.4

Editing the Application Properties

Application Property

Workflow.CorrectError

Workflow.CreateNewTradeItem

Workflow.GSDNItemRegistrationError

Workflow.ImportTradeItemToCorrect

Workflow.ImportTradeItemToRegister

Workflow.ItemAuthorizationError

Workflow.LinkError

Workflow.ModifyRegisteredTradeItem

Workflow.PublishError

Workflow.RegisterError

Workflow.RepublishError

Workflow.ReviewTradeItems

20/38

Default

Description

Example

°lÓ�2ç LAUNCH_WORK FLOW °lÓ�2ç CORRECT_ITEM °lÓ�2ç ITEM_VISIBILITY GDS_CORRECT_ITE Correct Error triggers M GDS_CORRECT_ITE M workflow GDS_REGISTER_ITE Create New Trade Item M triggers GDS_REGISTER_ITE M workflow GDS_CORRECT_GDS GDSN Item Registration N Error triggers GDS_CORRECT_GDS N workflow GDS_CORRECT_ITE Import Trade Item to Correct M triggers GDS_CORRECT_ITE M workflow GDS_REGISTER_ITE Import Trade Item to M Register triggers GDS_REGISTER_ITE M workflow GDS_CORRECT_AU Item Authorization Error THORIZATION triggers GDS_CORRECT_AUT HORIZATION workflow GDS_LINK Link Error triggers GDS_LINK workflow GDS_CORRECT_ITE Modify Registered Trade M Item triggers GDS_CORRECT_ITE M workflow GDS_PUBLISH Publish Error triggers GDS_PUBLISH workflow GDS_REGISTER_ITE Register Error triggers M GDS_REGISTER_ITE M workflow GDS_REPUBLISH Republish Error triggers GDS_REPUBLISH workflow GDS_REVIEW_ITEM Review Trade Item triggers GDS_REVIEW_ITEM workflow

PUBLIC

2012-06-30

4

Installing the GDS Console

4.5

Configuring Portal Settings

Application Property

Default

Workflow.SyncError

GDS_CORRECT_SYN Sync Error triggers GDS_ C CORRECT_SYNC workflow GDS_UNLINK Unlink Error triggers GDS_UNLINK workflow GDS_UNPUBLISH Unpublish Error triggers GDS_UNPUBLISH workflow default value is empty Name of host of the price validation EJB default value is empty JNDI path of the price validation EJB

Workflow.UnlinkError

Workflow.UnpublishError

PRICEXVALID.EJB.server

PRICEXVALID.EJB.jndi

XVALID.WEIGHT_TOLARANCE_PERCENT

default value is empty

XVALID.EJB.jndi.1

XVALID.EJB.no_of_servers

sap.com/ is~gds~core~app/ ExternalValidatorsEJB Bean 1

XVALID.EJB.server.1

127.0.0.1:53004

gds.helpURL

http://help.sap.com false

gds.logon.enableUserListDropDown

Description

Example

127.0.0.1:5010 4 sap.com/ is~gds~cust om~price~a pp/ ExternalPric eValidatorsE JBBean Tolerance for 1Sync Net 0.1 weight and Gross weight attributes in a hierarchy Location of XVALID EJB

Number of external validation server EJBs Location of XVALID EJB server URL of help Flag for enabling the selection of users from a dropdown list at logon.

NOTE

If there is no need to start a workflow for a particular trigger, remove the workflow name value for that trigger property.

4.5 Configuring Portal Settings Set up the trusted connection between the GDS Portal instance and the MDM server by completing the following steps.

2012-06-30

PUBLIC

21/38

4

Installing the GDS Console

4.5

Configuring Portal Settings

Procedure

1. 2.

Create an allow.ip text file in the \usr\sap\MDM\MDS\exe folder. Add the IP address of the server where GDSCORE is deployed in this file. NOTE

3. 4.

If you use GDS in distributed portal mode, add the IP address of the GDS standalone instance. Log in to the Portal with Portal Administrator and create your new GDS portal user. Add the following GDS portal role to the new GDS portal user: Name

pcd:portal_content/com.sap.pct/specialist /SAP_NetWeaver_MDM_GDS/Roles/SAP_MDM_GDS

Now you can access the SAP GDS workset with the new users. If the GDS portal user with the pcd:portal_content/com.sap.pct/specialist/SAP_NetWeaver_MDM_GDS/Roles/ SAP_MDM_GDS role has been created, the new GDS portal user has to log in to GDS in the portal mode and choose the SAP NetWeaver MDM global data synchronization option tab. At the same time, a new user with the same name as the GDS portal user is created in the GDS Console with the Everyone role. NOTE

The new GDS portal user has only the rights defined in the Everyone role. Administrator users can assign additional roles to the new GDS user. NOTE

If your GDS portal user name is 'GDSAdmin', 'Admin', or 'Administrator', the new user gets 'Admin' role in MDM. Otherwise, it gets only the 'Everyone' role and the administrator can extend the access rights. NOTE

If you use GDS in distributed Portal mode, set the appropriate values for the following application properties in the GDS portal instance for application is~gds~ui~model: Property Name

Default Value

Comments

GDSCORE.nwserverhostname

127.0.0.1

GDSCORE.nwserverport

50304

GDSCORE.nwsystemuser

Administrator

GDSCORE.nwsystemuserpassword

abc123

IP address for the GDS standalone instance P4 port for the GDS standalone instance J2EE 'Admin' user for the GDS standalone instance Password of user specified in GDSCORE.nwsystemuser

GDSCORE.mdmsystemuserpassword

GDSAdmin abc123

GDSCORE.nwhttpport

50300

GDSCORE.mdmsystemuser

22/38

PUBLIC

MDM administrator user Password of MDM user 'GDSAdmin' http port for the GDS standalone instance

2012-06-30

4

Installing the GDS Console

4.5

Configuring Portal Settings Property Name

Default Value

Comments

GDSCORE.nwlogviewerlocation

/webdynpro/dispatcher/sap.com/ tc~lm~itsam~ui~lv~client_ui/ LVApp

Location of the Log Viewer application on the remote server. Do not change the default value.

NOTE

Check that everything has been set as described in the Editing the Application Properties [page 15] section.

2012-06-30

PUBLIC

23/38

This page is left blank for documents that are printed on both sides.

5

Configuring Languages

5 Configuring Languages

You can define the languages you want your item to be published in for a selected target market. For more information about configuring languages, see SAP Library for GDS 2.1 Console on SAP Help Portal at http://help.sap.com/mdm-gds SAP Library GDS Metadata Management Defining Languages for Target Markets .

2012-06-30

PUBLIC

25/38

This page is left blank for documents that are printed on both sides.

6

Checking the Installation

6 Checking the Installation

To ensure that the GDS Console has been successfully installed and configured, perform the following installation test. Procedure

1.

Log on using one of the following URLs: Standalone Portal mode

2.

http://:/GDS/Console http://:/irj/portal/go/gds

On the site logon screen, enter a valid user name and password, and choose the Log On pushbutton. The initial logon name is Admin, and the password is abc123. NOTE

3.

If you change the password, you must change it in the application property as well and restart the application and the MDM connector using the Visual Admin Deploy service. After a successful logon, your browser displays the GDS Console dashboard.

2012-06-30

PUBLIC

27/38

This page is left blank for documents that are printed on both sides.

7

Troubleshooting

7 Troubleshooting

Procedure

If your logon fails or if error messages are displayed in your browser, perform the following steps to troubleshoot the installation: 1. If an error is displayed on the user interface, follow the specific instructions for troubleshooting. 2. Verify the application properties. For more information, see Editing the Application Properties [page 15]. 3. Open the Deploy service of the Web AS using the SAP NetWeaver Administrator and verify that the sap.com/is~gds~core~app application is running (marked with blue). For more information about navigating the Deploy service, see steps 1, 2, and 3 in Restarting the GDS Console in the solution operations guide for GDS on SAP Service Marketplace at http:// service.sap.com/instguides Industry Solutions Industry Solution Guides SAP for Consumer Products SAP MDM GDS 2.1 Application Operations Guide . 4. If the problem is not solved, restart the MDM connector and the GDS Console. For more information about restarting the MDM connector and the GDS Console, see Restarting the GDS Console in the solution operations guide for GDS on SAP Service Marketplace at http:// service.sap.com/instguides Industry Solutions Industry Solution Guides SAP for Consumer Products SAP MDM GDS 2.1 Application Operations Guide . 5. Use the Log Viewer service of the Web AS SAP NetWeaver Administrator to search for general errors. For more information about using the Log Viewer service, see Viewing the GDS Console Log in the solution operations guide for GDS on SAP Service Marketplace at http://service.sap.com/ instguides Industry Solutions Industry Solution Guides SAP for Consumer Products SAP MDM GDS 2.1 Application Operations Guide .

2012-06-30

PUBLIC

29/38

This page is left blank for documents that are printed on both sides.

A

Reference

A.1

The Main SAP Documentation Types

A Reference

A.1 The Main SAP Documentation Types The following is an overview of the most important documentation types that you need in the various phases in the life cycle of SAP software. Cross-Phase Documentation

SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30 languages, as well as many glossary entries in English and German. èØ`߬ Target group: èØ`߬j Relevant for all target groups èØ`߬ Current version: èØ`߬j On SAP Help Portal at http://help.sap.com Glossary èØ`߬j In the SAP system in transaction STERM SAP Library is a collection of documentation for SAP software covering functions and processes. èØ`߬ Target group: èØ`߬j Consultants èØ`߬j System administrators èØ`߬j Project teams for implementations or upgrades èØ`߬ Current version: èØ`߬j On SAP Help Portal at http://help.sap.com (also available as documentation DVD) The security guide describes the settings for a medium security level and offers suggestions for raising security levels. A collective security guide is available for SAP NetWeaver. This document contains general guidelines and suggestions. SAP applications have a security guide of their own. èØ`߬ Target group: èØ`߬j System administrators èØ`߬j Technology consultants èØ`߬j Solution consultants èØ`߬ Current version: èØ`߬j On SAP Service Marketplace at http://service.sap.com/securityguide Implementation

The master guide is the starting point for implementing an SAP solution. It lists the required installable units for each business or IT scenario. It provides scenario-specific descriptions of preparation,

2012-06-30

PUBLIC

31/38

A

Reference

A.1

The Main SAP Documentation Types

execution, and follow-up of an implementation. It also provides references to other documents, such as installation guides, the technical infrastructure guide and SAP Notes. D ÷Ѐ& Target group: D ÷ЀI Technology consultants D ÷ЀI Project teams for implementations D ÷Ѐ& Current version: D ÷ЀI On SAP Service Marketplace at http://service.sap.com/instguides The installation guide describes the technical implementation of an installable unit, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration. D ÷Ѐ& Target group: D ÷ЀI Technology consultants D ÷ЀI Project teams for implementations D ÷Ѐ& Current version: D ÷ЀI On SAP Service Marketplace at http://service.sap.com/instguides Configuration Documentation in SAP Solution Manager – SAP Solution Manager is a life-cycle platform. One of its main functions is the configuration of business scenarios, business processes, and implementable steps. It contains Customizing activities, transactions, and so on, as well as documentation. D ÷Ѐ& Target group: D ÷ЀI Technology consultants D ÷ЀI Solution consultants D ÷ЀI Project teams for implementations D ÷Ѐ& Current version: D ÷ЀI In SAP Solution Manager The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system. The Customizing activities and their documentation are structured from a functional perspective. (In order to configure a whole system landscape from a process-oriented perspective, SAP Solution Manager, which refers to the relevant Customizing activities in the individual SAP systems, is used.) D ÷Ѐ& Target group: D ÷ЀI Solution consultants D ÷ЀI Project teams for implementations or upgrades D ÷Ѐ& Current version: D ÷ЀI In the SAP menu of the SAP system under Tools Customizing IMG Production Operation

The technical operations manual is the starting point for operating a system that runs on SAP NetWeaver, and precedes the application operations guides of SAP Business Suite. The manual refers

32/38

PUBLIC

2012-06-30

A

Reference

A.1

The Main SAP Documentation Types

users to the tools and documentation that are needed to carry out various tasks, such as monitoring, backup/restore, master data maintenance, transports, and tests. =3žÿ¦ Target group: =3žÿÉ System administrators =3žÿ¦ Current version: =3žÿÉ On SAP Service Marketplace at http://service.sap.com/instguides The application operations guide is used for operating an SAP application once all tasks in the technical operations manual have been completed. It refers users to the tools and documentation that are needed to carry out the various operations-related tasks. =3žÿ¦ Target group: =3žÿÉ System administrators =3žÿÉ Technology consultants =3žÿÉ Solution consultants =3žÿ¦ Current version: =3žÿÉ On SAP Service Marketplace at http://service.sap.com/instguides Upgrade

The upgrade master guide is the starting point for upgrading the business scenarios and processes of an SAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of an upgrade. It also refers to other documents, such as upgrade guides and SAP Notes. =3žÿ¦ Target group: =3žÿÉ Technology consultants =3žÿÉ Project teams for upgrades =3žÿ¦ Current version: =3žÿÉ On SAP Service Marketplace at http://service.sap.com/instguides The upgrade guide describes the technical upgrade of an installable unit, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration. =3žÿ¦ Target group: =3žÿÉ Technology consultants =3žÿÉ Project teams for upgrades =3žÿ¦ Current version: =3žÿÉ On SAP Service Marketplace at http://service.sap.com/instguides Release notes are documents that contain short descriptions of new features in a particular release or changes to existing features since the previous release. Release notes about ABAP developments are the technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide (IMG). =3žÿ¦ Target group:

2012-06-30

PUBLIC

33/38

A

Reference

A.1

The Main SAP Documentation Types

qs>g# Consultants qs>g# Project teams for upgrades qs>gL Current version: qs>g# On SAP Service Marketplace at http://service.sap.com/releasenotes qs>g# In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)

34/38

PUBLIC

2012-06-30

Typographic Conventions

Example

Description



Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your ”. Arrows separating the parts of a navigation path, for example, menu options

Example Example Example Example

http://www.sap.com /example

123456 Example

Example

EXAMPLE

EXAMPLE

2012-06-30

Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note, for example, SAP Note 123456 €lÈ⁄ˆ˘ Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options. €lÈ⁄ˆ˘ Cross-references to other documentation or published works €lÈ⁄ˆ˘ Output on the screen following a user action, for example, messages €lÈ⁄ˆ˘ Source code or syntax quoted directly from a program €lÈ⁄ˆ˘ File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools 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 Keys on the keyboard

PUBLIC

35/38

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com

© Copyright 2012 SAP AG. 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 AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/ OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Oracle and Java are registered trademarks of Oracle and its affiliates. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc. HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc. IOS is a registered trademark of Cisco Systems Inc. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc. INTERMEC is a registered trademark of Intermec Technologies Corporation. Wi-Fi is a registered trademark of Wi-Fi Alliance. Bluetooth is a registered trademark of Bluetooth SIG Inc. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.

36/38

PUBLIC

2012-06-30

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group 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. Disclaimer

Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way. Documentation in the SAP Service Marketplace

You can find this document at the following address: http://service.sap.com/instguides

2012-06-30

PUBLIC

37/38

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com

© Copyright 2012 SAP AG. 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 AG. The information contained herein may be changed without prior notice.