Accessing-the-MDM-System.pdf

P U B L I S H I N GP U B L I S H I N Gprofessional expert ise dist i l led

SAP NetWeaver MDM 7.1 Administrator’s Guide

Uday Rao

Chapter No. 3 "Accessing the MDM System"

In this package, you will find: A Biography of the author of the book

A preview chapter from the book, Chapter NO.3 "Accessing the MDM System"

A synopsis of the book’s content

Information on where to buy this book

About the Author Uday Rao is an Engineering graduate with a Bachelors of Engineering Degree in Information Technology from PESIT college, Visvesvaraya Technological University. He started his career as a Java programmer and soon started writing Enterprise Java Beans for the SAP MDM Enrichment Adapter.

He is a certified SAP NetWeaver MDM 5.5 Technology Consultant and is also certified in SAP ABAP with over four years of work experience in the IT industry including over three years work experience on SAP NetWeaver MDM.

Apart from the MDM core implementations, he has also worked on creating SAP NetWeaver MDM Enrichment adapters, incorporating MDM Java APIs, MDM ABAP APIs, developing SAP WebDynpro Java applications, and SAP MDM Portal integration. His experience on other SAP technologies include: working on SAP WebDynpro ABAP, creating and testing SAP ABAP programs for various support and development projects, performing product testing for SAP MDM 7.1 and SAP Master Data Governance.

For More Information: www.packtpub.com/sap-netweaver-mdm-7-1-administrators-guide/book

http://www.packtpub.com/sap-netweaver-mdm-7-1-administrators-guide/book

He has also published SAP SDN community network blog on the SAP MDM Enrichment Adapter titled SAP MDM Enrichment Adapter - more than just enrichment.

Contact Uday Rao:

E-mail: [email protected]

LinkedIn: http://www.linkedin.com/pub/uday-rao/7/9b5/9a

Thank you Leena, Rebecca, Vincila, Dhwani, Hyacintha, Sakina, and all the folks from Packt Publishing for giving me the opportunity to author this book. Finally and most importantly, I would like to thank my parents Poonam and Vittal, my brother Prateek, and my wife Deepika for their continuous support and encouragement to author this book.



SAP NetWeaver MDM 7.1 Administrator’s Guide SAP Master Data Management (SAP MDM) enables information integrity across the business network, in a heterogeneous IT landscape. SAP MDM enables the sharing of harmonized master data, formerly trapped in multiple systems, and ensures cross system data consistency. This book will guide you through all the aspects of this software making it possible for you to get optimum output.

This book is a step-by-step tutorial that shows you how to successfully administer SAP NetWeaver MDM 7.1.

You will learn to plan and manage master data with SAP NetWeaver MDM. It will highlight the best practices and life cycle implementation using MDM and the concepts behind various aspects of SAP MDM administration.

What This Book Covers Chapter 1, MDM Scenarios and Fundamentals, covers the fundamentals of Master Data Management and discusses the various IT and Business scenarios that exist for an MDM implementation within an organization. You will also find discussion about repository structure, the various types of tables and some key capabilities supported by an MDM repository.

Chapter 2, Getting to Know the MDM Console, discusses about saving the MDM server list to a console settings file and loading this file in three different ways. Later on, you will see how to analyze the MDM Console main window and understand its GUI comprising of panes and tabs. Finally, you will see brief discussion about various types of configuration settings available in MDM.

Chapter 3, Accessing the MDM System, you learn to mount and unmount the MDM Server in a step by step manner. Then you move on to starting and stopping the MDM server. You will understand the various properties of the MDM repository. Finally, you will learn the repository access operations which cover: mounting and unmounting, connecting and disconnecting, and loading and unloading an MDM repository.

Chapter 4, MDM Repository Maintenance, you learn how to how to work with MDM repositories, fields and tables. There is also a separate section which explains about the addition and deletion of a new table/field type Tuple introduced with MDM 7.



Chapter 5, MDM Repository Administration, teaches various commands operated on an MDM repository like Appropriate repository, Update repository, and Verify repository. In addition, this chapter also talks about methods to back-up a repository like duplicating a repository, Master/Slave concept, and repository Archive/Unarchive. This chapter also discusses techniques that can be used to replicate a schema of a repository (without the data) like Exporting/Importing Schema and the Change Transport System (CTS+).

Chapter 6, Server Administration, discusses the options available in configuring the settings of the MDM server, repositories, and the backend DBMS.

Chapter 7, Import Server Administration, familiarizes the concepts and techniques used by the MDIS for efficiently importing large source data with exception handling capabilities. You will also learn common troubleshooting tips and tricks for resolving problems while importing data using the MDM Import Server.

Chapter 8, Syndication Server Administration, covers the administration of the MDM Syndication Server. This chapter starts with the features of the MDM Syndication Server or the MDSS. Then we highlight the differences between the Syndicator and the MDSS. Next, we describe the procedure for utilizing the MDSS and monitoring its activities. Configuring the MDSS using the various standard and optional parameters is described next. The last section covers simple tips and tricks for troubleshooting the MDSS.

Chapter 9, MDM System Administration, gives an overview of the security features available in MDM 7.1. Some administrative features and functions of some system tables are also explained in this chapter.

Chapter 10, Security, discusses about the security features of SAP MDM 7.1. We will talk about the various aspects of security for accessing the MDM system keeping in mind the perspective of the end users, network, auditing, and the repository's content.

Chapter 11, MDM Integration Scenarios, discusses about the MDM integration scenarios with these SAP offerings: BI, PI/XI, and the Enterprise Portal.

Appendix, Getting Started with MDM, discusses the need for MDM and provides an overall understanding of its key capabilities.



Accessing the MDM SystemIn this chapter, you can learn how to access and control the states of the MDM Servers and repositories using the MDM Console application. These Console operations enable you to maintain the MDM server and its underlying repositories.

After going through this chapter, you will be able to:

Mount and unmount an MDM serverStart and stop an MDM serverMount and unmount a repositoryConnect and disconnect to a repositoryLoad and unload a repository

Accessing the MDM servers Before we can access an MDM repository, we fi rst need to have access to the MDM server that is hosting the repository. For this purpose we will fi rst talk about accessing the MDM server. Accessing an MDM server involves mounting and unmounting operations which we discuss in the following section.

Mounting and unmounting an MDM server MDM server installations are accessible on the console only after they have been mounted. Multiple servers can be mounted within a single console session. We have a choice of mounting only those servers which need to be accessed. The server may or may not be in a running state when mounted in your console session. No password is required to mount a server in your console session even if it is password protected.

•

•

•

•

•



Accessing the MDM System

[ 50 ]

The MDM Console provides the option of saving the list of currently mounted servers to an MDM Console Settings fi le . We can load this settings fi le in the console session and automatically get the previously saved server(s) list mounted as a group. Refer to Chapter 2, Getting to Know the MDM Console for a detailed explanation under the topic the MDM Console Settings fi le.

An MDM server can be mounted by multiple MDM Consoles. Once an MDM server is started from any console, it runs on the machine where it is installed and is seen as running by all MDM Consoles that have mounted it.

We can mount an MDM server as follows:

1. Right-click on the root node (SAP MDM Servers) in the hierarchy pane tree and choose Mount MDM Server… from the context menu:

2. Alternatively you many select the root node (SAP MDM Servers) and choose M DM Servers | Mount MDM Server… from the main menu:



Chapter 3

[ 51 ]

3. MD M opens the Mount MDM Server dialog prompting for the MDM Server input as displayed next:




[ 52 ]

4. In the drop-down list input the region displaying the text Enter or select an MDM Server, type the name of the MDM server (typically the name of the machine on which the server is running) you want mounted or select it from the drop-down list. Alternatively (for non-Windows installations), type the name or IP address of any remote machine into the edit box in the Mount MDM Server dialog.

5. Cli ck on the OK button:

The drop-down list of MDM Servers shows only those servers that you have previously mounted. If a specifi c server is not in the list, click on … (Browse) button to open the Select MDM Server dialog (see next) and select the machine on which the MDM Server has been installed from the list of Windows machines visible on the local network.

On s uccessful mounting of the MDM server, you will see a new server node added in the tree structure of the hierarchy pane. Depending on the state of the MDM server, the corresponding icon is displayed in the tree node. The different states and the respective icons of the server node are listed in the following table:



Chapter 3

[ 53 ]

Status icon State of MDM serverMDM server is stopped

MDM server is running

MDM server is in one of the following states*:Server InaccessibleCommunication ErrorStart Server FailedInvalid

•

•

•

•

If the MDM server is inaccessible via the console even after the server has been started, you can try unmounting and remounting the MDM server in the console to restore connectivity.

Next we see how to unmount an already mounted MDM server:

1. In the hierarchy tree, right-click on the MDM server that you want to unmount and choose Unmount MDM Server from the context menu. Alternatively, you may unmount the server by fi rst selecting its node in the tree and then clicking on MDM Servers | Unmount MDM Server from the main menu.

Unmounting an MDM server is also possible by using the MDM Servers pane (top-right) when the root node (SAP MDM Servers) is selected in the hierarchy tree. Then you can right-click on the MDM Server in the objects pane and select Unmount MDM Server from the context menu.

2. The MDM server node disappears from the tree in the hierarchy pane.

Unmounting a running MDM server while it is still running keeps the MDM repositories mounted and loaded even while the unmounted server remains disconnected from the console session.Unmounting and again re-mounting an MDM server within the same MDM Console session requires the MDM server's password to be re-entered to perform any server-level operations (like starting and stopping the server).




[ 54 ]

Starting and stopping an MDM serverAlong with the MDM Server, other auxiliary servers like MDM Import Server, MDM Syndication Server, and MDM Layout Server can be started and stopped using the MDM Console tool. However, starting and stopping the servers requires an OS user and password to be entered in the Web Service Authentication dialog box.

An MDM server in stopped state (red square) can be started by using the following steps:

1. Right-click on the stopped MDM server in the hierarchy pane and select Start MDM Server from the context menu. Alternatively, the server can also be started by selecting MDM Servers | Start MDM Server from the main menu.

Starting a stopped MDM server is also possible by using the MDM Servers pane (top-right) when the root node (SAP MDM Servers) is selected in the hierarchy tree. You can simply right-click on the MDM server having the status Stopped in the objects pane and select Start MDM Server from the context menu.

2. The console application prompts you to enter the OS level User and Password in the Web Service Authentication dialog box:

3. Enter the credentials and click on OK.4. The state of the MDM server changes to running with the server status icon

changing from a red square to a green triangle (as shown):



Chapter 3

[ 55 ]

When starting an MDM server, a check is performed on each of its mounted repositories. This requires the underlying DBMS server to be up and running.

Yo u can stop an MDM server when it is in running state (green triangle) as follows:

1. Stop the MDM server from the context menu by right-clicking on the server node in the hierarchy pane. Then click on the Stop MDM Server option in the co ntext menu displayed:




[ 56 ]

2. Alternatively, you may also stop the currently selected MDM server by choosing MDM Servers | Stop MDM Server from the main menu:

Stop ping a running MDM server is also possible by using the MDM Servers pane (top-right) when the root node (SAP MDM Servers) is selected in the hierarchy tree. You can simply right-click on the MDM server having the status Started in the objects pane and select Stop MDM Server from the context menu.

3. A po p-up SAP Instance Shutdown dialog box appears prompting for the type of shutdown. Select the shutdown type from the following choices:

Hard (SIGINT)Soft with timeout (SIGQUIT/SIGINT)Soft without timeout (SIGQUIT)

°

°

°



Chapter 3

[ 57 ]

4. If you have selected Soft with timeout as the shutdown type then also provide the timeout period in seconds in the input textbox.

5. Click on the OK button.6. MDM p rompts you to enter the OS user name and password in the

Web Service Authentication pop-up dialog box:

7. After entering the credentials click on OK.




[ 58 ]

8. The server status icon changes from the green triangle to a red square (as shown) indicating that the server is now stopped:

You can start or stop the auxiliary servers using the following steps:

1. Mount the auxiliary server by right-clicking on the node in the console hierarchy Auxiliary Servers:

2. Select the desired auxiliary server from the context menu option Mount. 3. In the d ialog box, select the auxiliary server from the drop-down menu:



Chapter 3

[ 59 ]

4. A new server node is appended below the Auxiliary Servers node:

5. To start t he auxiliary server (for example, Import Server), right-click on it and select the context menu option Start Auxiliary Server:




[ 60 ]

Similarly, you can stop the auxiliary server by selecting the context menu option Stop Auxiliary Server. A pop-up SAP Instance Shutdown dialog box appears prompting for the type of shutdown. This is the same pop-up that appears while stopping the MDM server as discussed previously.

In the next section, we will learn about the various properties of the MDM repositories and the DBMS server.

MDM repository propertiesOnce the MDM server is started, we can see the repositories that are available in it. Every repository has a set of properties associated with it.

In order to see the repositories, select the MDM server node in the hierarchy tree. The objects pane (top-right) having the title Repositories displays a list of mounted MDM repositories in a grid layout. Each repository in the list is a child of the corresponding MDM server node selected in the hierarchy pane.

You can view the repository properties for every repository displayed in the objects pane titled Repositories. When you select a repository in the object pane list, the object details pane displays additional repository properties under the Repository Detail tab. These properties are summarized as shown:

Property Description

Name The MDM repository name

Description The MDM repository description

DBMS Server The network ID of the DBMS server that is hosting the repository

DBMS Type The DBMS brand:

SQL ServerOracleDB2MaxDB

•

•

•

•Login The login name for the DBMS server

Password The password for the DBMS server

Port The TCP/IP port number on which to connect to the repository



Chapter 3

[ 61 ]

Property Description

Type The MDM repository type:

NormalMasterSlavePublication Slave

•

•

•

•

Languages The languages supported by the MDM repository.

Status The MDM repository status:

DisconnectedUnloadedLoadingLoadedRunning RemotelyOutdatedNewer than MDM ServerArchivingUnarchivingDuplicatingInvalidBusy

•

•

•

•

•

•

•

•

•

•

•

•

The Type and Port property is hidden by default in the Repositories pane; unhide to display.The Password property is not visible in either the Repositories or Repository Detail panes.The Status property is not visible in the Repository Detail pane.

A repository having the status Disconnected may only show values for the Name, DBMS Server, and DBMS Type properties. In order to see additional property values you must connect to the repository (See Connecting to and disconnecting from an MDM repository under the section Accessing MDM repository of this chapter).

We now discuss in detail the DBMS server and the repository port properties listed in the previous table.




[ 62 ]

DBMS server The DBMS Server property defi nes the network identifi cation string of the DBMS instance/machine/server that is used by the DBMS-specifi c client on the MDM server machine to connect to the DBMS.

The DBMS Type property displays the brand of the DBMS server on which the repository is running.

When two repositories with the same name, but located in different DBMS servers, are mounted on the same MDM server, MDM identifi es them in the hierarchy pane of the console by appending the name of the DBMS server in angular brackets to the repository name (for example, Test Repository <DBMS server>).

Repository port numbers The port property defi nes TCP/IP port numbers that the various MDM client applications, MDM APIs, and OCI connections use to connect to the repository. MDM uses three consecutive port numbers starting from the value specifi ed. So if you have given the port value as 2400, MDM will actually be using the ports 2400, 2401, and 2402. The starting port value can be chosen as any value in the range 2000 to 9999 as per your requirements, but be aware of the three consecutive port values actually used by MDM. It is recommended to provide at least a gap of 3 values while assigning port numbers to two or more repositories. It is recommended that each repository be assigned a unique port number as only one repository can be loaded on a port at a time.

You can assign or edit TCP/IP port numbers using the object details pane titled Repository Detail during any of the following operations:

Mounting a repositoryCreating a repositoryRepository duplicationUnarchiving a repository

•

•

•

•



Chapter 3

[ 63 ]

CAUTIONEven though MDM allows you to mount two repositories on the same port, it doesn't allow you to load them on the same port simultaneously. Hence, unique port numbers should be assigned to repositories. Users should be notifi ed promptly about any change in the port numbers.

Now that the MDM server has been mounted, let us move on to accessing the MDM repository.

Accessing the MDM repository You can access the MDM repository in your console session by fi rst mounting it.

After mounting the repository you need to connect to it in order to view the repository's current type and state. Then you can perform various administrative functions on it.

The MDM server must be mounted in your console session in the running state before we can mount any repositories under it.

When you select the MDM server node in the hierarchy tree, the objects pane titled Repositories shows the list of mounted repositories. It displays both the type and state of only connected repositories.

Let us see how we can mount, unmount, connect, disconnect, load, and unload repositories in the following sections.

Mounting and unmounting an MDM repositoryMultiple repositories can be mounted within a single console session. It is not necessary to mount all repositories; instead we can mount only those repositories which are of interest to us.

When mounting an MDM repository you are required to enter the user name and password of the underlying DBMS server in the pop-up dialog box.




[ 64 ]

Follow the steps given in order to mount an existing MDM repository:

1. Right-click on the MDM server node in the tree of the hierarchy pane and choose Mount Repository from the context menu:

2. A lternatively, you can select the server node and choose Repositories | Mount… from the main menu:



Chapter 3

[ 65 ]

3. In the Mount MDM Repository dialog box, you are prompted to enter the DBMS server, User name, and Password:




[ 66 ]

4. In the DBMS server drop-down list, select the server of the DBMS you want to connect:

If t he DBMS server is not available in the drop-down list, you can add a new DBMS server by clicking on the … button. MDM displays the Select DBMS Server pop-up as illustrated with the buttons Add, Remove, OK, and Cancel. By clicking on the Add… button, you can add a DBMS server and its corresponding DBMS type in the Add DBMS Server dialog box (see next). The newly added server henceforth appears in the DBMS Server drop-down list of the Mount MDM Repository dialog box.

5. After choosing the DBMS server, enter the DBMS User name having the system administrator privileges on the selected server and the corresponding user password. Then click on the Next button.

6. If th e credentials for the DBMS server are correct, MDM disables the DBMS server, User name, and Password fi elds, and enables the Repository name and Port fi elds:



Chapter 3

[ 67 ]

7. You can select the MDM repository you want to mount from the Repository name drop-down list.

8. Enter the TCP/IP port number in the Port textbox.9. Click on the Finish button to mount the MDM repository.10. A new node for the MDM repository gets added to the hierarchy tree as a

child of the MDM server node. The repository is added in a disconnected state with a gray lock (as shown) in the status icon in the hierarchy pane:

Next, let us see the reverse process that is unmounting an MDM repository. In order to unmount a repository, it must be in the unloaded state.

Follow the steps to unmount a mounted repository:

1. In the hierarchy tree, right-click on the MDM repository, and choose Unmount Repository from the context menu. Alternatively, you can also select the tree node and choose Repositories | Unmount from the main menu.

2. MDM rem oves the repository node from the hierarchy tree.

Once you unmount a repository, the port on which it was mounted is freed and can be used to mount other repositories.




[ 68 ]

Connecting to and disconnecting from an MDM repositoryOnce the MDM repository is mounted, you must connect to it for any further repository operations.

To conn ect to a disconnected MDM repository (gray lock):

1. Right-click on the MDM repository node in the hierarchy tree and choose Connect to Repository from the context menu:

2. Alternat ively, you can fi rst select the repository tree node and choose Repositories | Connect from the main menu:



Chapter 3

[ 69 ]

Connectin g to an MDM repository is also possible by using the Repositories pane (top-right) when the server node is selected in the hierarchy tree. You can simply right-click on the repository having the status Disconnected in the objects pane and select Connect to Repository from the context menu.

3. You are prompted to enter the repository User and Password credentials in the Connect to MDM Repository dialog box:




[ 70 ]

4. If the user and password are correct, the status icon of the MDM repository in the hierarchy tree changes to refl ect its current type and state.

5. The Tables and Table Detail panes are populated with table information for the connected MDM repository.

To disconn ect from an MDM repository:

1. In the hierarchy tree, right-click on the MDM repository and choose Disconnect from Repository from the context menu:



Chapter 3

[ 71 ]

2. Alternative ly, you may select the tree node and choose Repositories | Disconnect from the main menu:

3. The reposito ry status icon changes to a gray lock indicating that the repository is now disconnected from the Console:




[ 72 ]

Loading and unloading an MDM repositoryAfter an MDM repository has been mounted and connected, the next step is to load the repository before performing data entry activities by the clients on the network.

An MDM repository can be simultaneously mounted by multiple MDM servers. But once a repository has been loaded on a particular MDM server, it cannot be loaded on any other MDM server having the same repository mounted.

Only a single repository can be loaded on a TCP/IP port at a time. For instance, if Repository A has been loaded on port 2400, no other repository can be loaded on the same 2400 port.

After an MDM repository has been loaded, its structure cannot be modifi ed through the MDM Console. In order to do so it has to be fi rst unloaded.

In order to modify the structure of an MDM repository while preserving access to a current version, you can duplicate the repository and give it a new name, or use the same name and move it to another DBMS machine.

Follow the st eps given to load an unloaded MDM repository (red square):

1. Right-click on the repository you want to load in the hierarchy tree and choose Load Repository from the context menu:



Chapter 3

[ 73 ]

2. Alternatively, you may select the repository node in the hierarchy tree and choose Repository | Load from the main menu:




[ 74 ]

3. There are two o ptions to load the repository—Immediate or Update Indices.

When you choo se to load the repository using the Immediate option, MDM automatic ally updates the out of date indices as a result of changes made to the repository via the MDM Data Manager. On the other hand, if the structure of the repository has been modifi ed through the MDM Console, MDM cannot know precisely which indices need to be updated. In such situations, the Update Indices method for loading the repository should be used and not the load Immediate option.

4. While MDM loads the MDM repository, the load progress is displayed in the Status fi eld for the repository in the Repositories pane and the repository status icon changes to a blue arrow as illustrated:

5. After the loadin g process is completed the repository status icon changes to a green triangle. This process can take somewhere between fi ve minutes to fi ve hours depending upon the data stored in the repository:

Follow the steps given to unload a loaded MDM repository (green triangle):



Chapter 3

[ 75 ]

1. Right-click on th e MDM repository node in the hierarchy tree and choose Unload Repository from the context menu:




[ 76 ]

2. Alternatively, you may select the tree node and choose Repositories | Unload from the main menu:

3. You can choose the time out before unloading the MDM repository from the cascading menu:

Immediate1 Minute2 Minutes5 Minutes

°

°

°

°



Chapter 3

[ 77 ]

4. With the delayed unload option, the repository state changes to Unload scheduled: <time remaining> and a red square is added to the repository status icon:

The non-Immediate choice allows users of MDM client applications to fi nish using the MDM repository and exit before the repository is unloaded and no longer available. With the delayed options, each client application receives text messages at fi ve, two, and one minute intervals before shutdown.

5. After the selected w ait time elapses, the MDM repository gets unloaded and the repository status icon changes to a red square:

Once an MDM repository is unloaded:1. MDM server no longer serves the repository's data to any client.2. Any MDM clients using the repository will be automatically shut down.3. MDM client attempts to connect to the unloaded repository it will fail with the message: The repository is not loaded.




[ 78 ]

In order to cancel a scheduled unload:

1. Right-click on the MD M repository and select the Unload Repository | Cancel Unload from the cascading menu:

2. Alternatively, you may select the repository tree node and choose Repositories | Unload | Cancel Unload from the cascading main menu:



Chapter 3

[ 79 ]

3. The repository status c hanges from Unload Scheduled to Loaded Running in the Repositories pane. The status icon in the hierarchy tree also changes to a green triangle:

SummaryIn this chapter, we have seen the operations for accessing the MDM server and the MDM repository. In the beginning, we saw how to mount and unmount the MDM server in a step-by-step manner. Then we moved on to starting and stopping the MDM server. We understood the various properties of the MDM repository. Finally, we learned the repository access operations which cover: mounting and unmounting, connecting and disconnecting, loading and unloading an MDM repository.

In the next chapter, you will learn to perform MDM repository maintenance by adding, removing, and modifying the structure of the repository using the MDM Console.



Where to buy this book You can buy SAP NetWeaver MDM 7.1 Administrator’s Guide from the Packt Publishing website: http://www.packtpub.com/sap-netweaver-mdm-7-1-administrators-guide/book Free shipping to the US, UK, Europe and selected Asian countries. For more information, please read our shipping policy.

Alternatively, you can buy the book from Amazon, BN.com, Computer Manuals and most internet book retailers.

www.PacktPub.com

P U B L I S H I N GP U B L I S H I N Gprofessional expert ise dist i l led



http://www.packtpub.com/Shippingpolicy

Date post:	11-Jan-2016
Category:	Documents
Upload:	vjeet2001
View:	213 times
Download:	0 times

Accessing-the-MDM-System.pdf

Documents