管理者ガイド - help.sap.com

PUBLIC (公開)SAP Data Servicesドキュメントバージョン: 4.2 Support Package 14 (14.2.14.0) – 2022-01-28

管理者ガイド

© 2

021 S

AP S

E or

an

SAP affi

liate

com

pany

. All r

ight

s re

serv

ed.

THE BEST RUN

目次

1 Naming conventions and variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 Architecture overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1 Data Services and the SAP BI portfolio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.2 Standard components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Designer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Job Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Access Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Management Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Adapter SDK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.3 Management tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Manage license keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Repository Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Server Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

2.4 Operating systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.5 Distributed architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Host names and port numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.6 SAP applications integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.1 Data protection and privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263.2 Firewall for secure administrative functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.3 External DTD in XML documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.4 Message client library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.5 Temporary cache files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Encrypting temporary cache files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.6 SSL or TLS for Data Services components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Protected communication paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Default certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Copying certificates in a distributed environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Enable or disable SSL on select communication paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Using custom certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Generating keys and signing certificates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.7 Configure SSL for the CMS connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.8 SSL for Metadata Browsing and View Data Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Configuring SSL for Metadata Browsing and View Data Services. . . . . . . . . . . . . . . . . . . . . . . . 43

2PUBLIC公開

管理者ガイド

目次

Creating keystore file and certificates for default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443.9 Password encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Encryption key storage locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45Encrypt passwords manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3.10 Repository password required. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Accessing Data Services applications without repository credentials . . . . . . . . . . . . . . . . . . . . . 48

4 User and rights management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504.1 User management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504.2 Group management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Detailed application rights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Viewing application rights assigned to a group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Managing application rights for a group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5 Repository management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .575.1 Configuring a Data Services local repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575.2 Registering a repository in the CMC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605.3 Accessing repository user security in the CMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Viewing rights for a user or group on a repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Assigning users and groups to an access control list for a repository. . . . . . . . . . . . . . . . . . . . . .63Detailed repository rights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

5.4 Oracle TCPS protocol for repositories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Configurations in the java.security folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Configuring for JCE Cipher Suites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Configuring Oracle repository for TCPS protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

5.5 SAP HANA SSL/TLS protocol for repositories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

SAP HANA に対する CMC での SSL/TLS の設定. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .735.6 Editing the java.security file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

6 サーバの管理. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766.1 DSN-less and TNS-less connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776.2 Setting UNIX environment variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

6.3 Windows および Unix でのサービスの自動起動. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816.4 History retention and Job Server log retention. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

USPS-required log files and reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Setting the History Retention Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Setting the Job Server Log Retention Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86

6.5 UNIX および Linux のデータベース接続の設定. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

UNIX および Linux のデータベース接続. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

接続マネージャの使用. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

サーバ名 (DSN なし) 接続を使用したドライバの設定. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

データソース名 (DSN) 接続によるドライバの設定. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

管理者ガイド

目次

PUBLIC公開 3

DataDirect ODBC の設定. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1036.6 Using the ODBC Drivers Selector for Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1126.7 Using the License Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1136.8 Use the Server Manager on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Configuring Job Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Configuring runtime resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119

Access Server の設定. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

SSL パスの設定. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Job Server と Access Server の実行の確認. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1236.9 Using the Server Manager on UNIX systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Configuring Job Servers on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

ランタイムリソースの設定. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128

Access Server の設定. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

SSL パスの設定. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

サービスの開始または停止. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Configure SMTP email. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

6.10 Configuring Metadata Browsing Service and View Data Service . . . . . . . . . . . . . . . . . . . . . . . . . . .133

メタデータ参照サービスの設定パラメータ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Data Services の表示設定パラメータ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

6.11 Data Services CMC アプリケーション設定. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

7 Monitoring jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1407.1 Viewing overall status of executed jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1407.2 Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Viewing job statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Data flow statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

7.3 Ignoring error status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1457.4 Deleting batch job history data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1457.5 Stopping a running job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1467.6 Deleting trace, monitor, and error logs for a batch job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

8 Lifecycle migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1488.1 Development phases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

The design phase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150The test phase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150The production phase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

8.2 Migration tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

移行の命名規則. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

データストアとシステム設定. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1568.3 Migration mechanisms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Export and import migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

4PUBLIC公開

管理者ガイド

目次

Multi-user development migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162The best mechanism. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

8.4 Migrate with export and import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164The export editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Exporting objects to another repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Exporting objects to a file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Exporting a repository to a file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Importing objects or a repository from a file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

8.5 Back up repositories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1728.6 Mismatched locales and job performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

9 The Enhanced Change and Transport System (CTS+). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

10 Object promotion management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17710.1 Requirements for object promotion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Shared directory user rights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Sequential import of multiple objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

10.2 User rights for promotion management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18010.3 Export and import configuration requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Creating an export configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Creating an import configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Edit or delete configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

10.4 Before you export and import objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18510.5 Object promotion options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18610.6 Exporting objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18710.7 Importing objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18910.8 Export and import trace and error log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

11 Integration with SAP and SAP Solution Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19311.1 SAP System Landscape Directory (SLD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19311.2 Solution Manager Diagnostics (SMD) Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19411.3 SLD integration requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194

12 Data Services registration in the SLD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

13 Performance and availability monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19713.1 Solution Manager Diagnostics (SMD) overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19713.2 SMD Agent guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19913.3 Configure your system for SMD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19913.4 The Native Component Supportability (NCS) library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Enabling NCS library on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Enabling NCS library on Unix or Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

13.5 Heartbeat monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

管理者ガイド

目次

PUBLIC公開 5

13.6 Alert monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

14 Command line administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20514.1 ライセンスマネージャ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Starting License Manager in Unix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20714.2 Command line: Data Services Connection Manager (Unix). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20814.3 Command line: Repository Manager (Windows). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20914.4 Command line: Repository Manager (Unix). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21114.5 Command line: Server Manager (Unix or Linux). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Command line: Adding an Access Server (Unix or Linux). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Command line: Adding a Job Server (Unix or Linux). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216Command line: Adding runtime resources (Unix or Linux). . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

14.6 Command line: Server Manager (Windows). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Command line: Adding an Access Server (Windows). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220Command line: Adding a Job Server (Windows). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221Command line: Adding runtime resources (Windows). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

14.7 Command line: Password encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22314.8 al_engine options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

al_engine Export and Import options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

6PUBLIC公開

管理者ガイド

目次

1 Naming conventions and variables

This documentation uses specific terminology, location variables, and environment variables that describe various features, processes, and locations in SAP Business Objects and SAP Data Services.

Terminology

SAP Data Services documentation uses the following terminology:

● The terms Data Services system and SAP Data Services mean the same thing.● The term BI platform refers to SAP BusinessObjects Business Intelligence platform.● The term IPS refers to SAP BusinessObjects Information platform services.

注記

Data Services requires BI platform components. However, when you don't use other SAP applications, IPS, a scaled back version of BI, also provides these components for Data Services.

● CMC refers to the Central Management Console provided by the BI or IPS platform.● CMS refers to the Central Management Server provided by the BI or IPS platform.

Variables

The following table describes the location variables and environment variables that are necessary when you install and configure Data Services and required components.

Variables Description

INSTALL_DIR The installation directory for SAP applications such as Data Services.

Default location:

● For Windows: C:¥Program Files (x86)¥SAP BusinessObjects

● For UNIX: $HOME/sap businessobjects

注記

INSTALL_DIR isn't an environment variable. The installation location of SAP software can be different than what we list for INSTALL_DIR based on the location that your administrator sets during installation.

管理者ガイド

Naming conventions and variablesPUBLIC

公開 7


BIP_INSTALL_DIR The directory for the BI or IPS platform.

Default location:

● For Windows: <INSTALL_DIR>¥SAP BusinessObjects Enterprise XI 4.0

例C:¥Program Files (x86)¥SAP BusinessObjects¥SAP BusinessObjects Enterprise XI 4.0

● For UNIX: <INSTALL_DIR>/enterprise_xi40

注記

These paths are the same for both BI and IPS.

注記

BIP_INSTALL_DIR isn't an environment variable. The installation location of SAP software can be different than what we list for BIP_INSTALL_DIR based on the location that your administrator sets during installation.

<LINK_DIR> An environment variable for the root directory of the Data Services system.

Default location:

● All platforms<INSTALL_DIR>¥Data Services

例C:¥Program Files (x86)¥SAP BusinessObjects¥Data Services

8PUBLIC公開

管理者ガイド

Naming conventions and variables


<DS_COMMON_DIR> An environment variable for the common configuration directory for the Data Services system.

Default location:

● If your system is on Windows (Vista and newer):<AllUsersProfile>¥SAP BusinessObjects¥Data Services

注記

The default value of <AllUsersProfile> environment variable for Windows Vista and newer is C:¥ProgramData.

例C:¥ProgramData¥SAP BusinessObjects¥Data Services

● If your system is on Windows (Older versions such as XP)<AllUsersProfile>¥Application Data¥SAP BusinessObjects¥Data Services

注記

The default value of <AllUsersProfile> environment variable for Windows older versions is C:¥Documents and Settings¥All Users.

例C:¥Documents and Settings¥All Users¥Application Data¥SAP BusinessObjects¥Data Services

● UNIX systems (for compatibility)<LINK_DIR>

The installer automatically creates this system environment variable during installation.

注記

Starting with Data Services 4.2 SP6, users can designate a different default location for <DS_COMMON_DIR> during installation. If you can't find

管理者ガイド

Naming conventions and variablesPUBLIC

公開 9


the <DS_COMMON_DIR> in the listed default location, ask your System Administrator to find out where your default location is for <DS_COMMON_DIR>.

<DS_USER_DIR> The environment variable for the user-specific configuration directory for the Data Services system.

Default location:

● If you're on Windows (Vista and newer):<UserProfile>¥AppData¥Local¥SAP BusinessObjects¥Data Services

注記

The default value of <UserProfile> environment variable for Windows Vista and newer versions is C:¥Users¥{username}.

● If you're on Windows (Older versions such as XP):<UserProfile>¥Local Settings¥Application Data¥SAP BusinessObjects¥Data Services

注記

The default value of <UserProfile> environment variable for Windows older versions is C:¥Documents and Settings¥{username}.

注記

The system uses <DS_USER_DIR> only for Data Services client applications on Windows. UNIX platforms don't use <DS_USER_DIR>.

The installer automatically creates this system environment variable during installation.

10PUBLIC公開

管理者ガイド

Naming conventions and variables

2 Architecture overview

Use information about SAP Data Services architecture, system components, and service components to understand system essentials and to form a plan for system deployment, management, and maintenance.

Data Services and its architecture enables high performance across a broad spectrum of user and deployment scenarios.

例

Integrate Data Services into other technology systems in your organization by using the following tools:

● Web services● Java● .NET APIs

Use specialized tools and application to access, create, edit, and interact with Data Services projects and reports. Use the following applications for data and system management tools:

● Data Services Management Console● SAP BusinessObjects Central Management Console (CMC)● Data Services Server Manager● Data Services Repository Manager

To provide flexibility, reliability, and scalability, install Data Services components on one or across many machines using vertical or horizontal scaling:

● Vertical scaling: One computer runs several, or all, server-side processes. Use vertical scaling to reduce cost or to improve performance by distributing server processes between two or more networked machines.

● Horizontal scaling: Run multiple, redundant versions of the same server process on more than one machine, so that processing continues if the primary process encounters a problem.

Data Services and the SAP BI portfolio [page 12]The SAP BusinessObjects Business Intelligence (BI) Suite delivers insight through specialized end-user tools on a single, trusted, SAP BusinessObjects BI platform.

Standard components [page 13]SAP Data Services works with standard components in the SAP BusinessObjects Business Intelligence (BI) suite.

Management tools [page 19]SAP Data Services provides utilities to help you manage your repositories and servers.

Operating systems [page 21]SAP Data Services supports many types of operating systems and versions.

Distributed architecture [page 21]SAP Data Services offers flexibility to design your system using a distributed architecture.

SAP applications integration [page 23]

管理者ガイド

Architecture overviewPUBLIC

公開 11

SAP Data Services integrates with SAP applications and infrastructures with specific tools, such as the SAP System Landscape Directory (SLD) for lifecycle management of your SAP systems.

2.1 Data Services and the SAP BI portfolio

The SAP BusinessObjects Business Intelligence (BI) Suite delivers insight through specialized end-user tools on a single, trusted, SAP BusinessObjects BI platform.

SAP Data Services supports the entire SAP BusinessObjects BI platform. On top of Data Services, the SAP BusinessObjects BI Suite layers the most reliable, scalable, flexible, and manageable platform. The platform supports integrated end-user interfaces for the following features:

● Reports● Queries● Analyses● Performance management dashboards● Performance management scorecards● Performance management applications

SAP has created a data integration product that uses relational datastores and built-in intelligence for real time and batch data access. Data is from ERP systems and other sources. With these capabilities, leverage your ERP and enterprise application infrastructure for multiple uses.

With batch and real-time data integration, you can take advantage of analytic and supply-chain management applications. With data integration solutions, you can maintain a real-time, on-line dialogue with customers, suppliers, employees, and partners. Your company can provide customers, suppliers, employees, and partners with information for transactions and business analysis.

Parent topic: Architecture overview [page 11]

関連情報

Standard components [page 13]Management tools [page 19]Operating systems [page 21]Distributed architecture [page 21]SAP applications integration [page 23]

12PUBLIC公開

管理者ガイド

Architecture overview

2.2 Standard componentsSAP Data Services works with standard components in the SAP BusinessObjects Business Intelligence (BI) suite.

The following diagram shows how Data Services works with other user interfaces, platforms, repositories, and components in the BI suite.

注記

The basic components required by Data Services are also provided by SAP Information platform services as a scaled back version of the BI platform.

For a detailed list of supported environments and hardware requirements, see the Product Availability Matrix (PAM) on the SAP Support Portal.

Designer [page 14]Designer is the graphical user interface for SAP Data Services that enables you to define data management applications that consist of data mappings, transformations, and control logic.

Repository [page 15]An SAP Data Services repository contains data, such as user-created and predefined system objects, source and target metadata, and transformation rules.

Job Server [page 16]

管理者ガイド


公開 13

https://help.sap.com/viewer/disclaimer-for-links?q=https%3A%2F%2Fapps.support.sap.com%2Fsap%2Fsupport%2Fpam%3Fhash%3Dpvnr%253D67838200100900005703


The SAP Data Services Job Server starts the data movement engine that integrates data from multiple heterogeneous sources.

Access Server [page 17]The Access Server collects message requests, routes them to a real-time service, and delivers message replies within a user-specified time frame.

Management Console [page 17]The Management Console contains a collection of Web-based applications for administering multiple SAP Data Services features and objects.

Adapter SDK [page 18]The SAP Data Services Adapter SDK provides a Java platform for rapid development of adapters to other applications and middleware products such as EAI (Enterprise Application Integration) systems.


関連情報

Data Services and the SAP BI portfolio [page 12]Management tools [page 19]Operating systems [page 21]Distributed architecture [page 21]SAP applications integration [page 23]

2.2.1 Designer

Designer is the graphical user interface for SAP Data Services that enables you to define data management applications that consist of data mappings, transformations, and control logic.

Use the Designer to create applications such as the following:

● Work flows: Job execution definitions.● Data flows: Data transformation definitions.

To create jobs in designer, drag and drop objects into work flows and data flows. Configure the objects using various icons in flow diagrams, table layouts, and nested workspace pages. The objects represent metadata, which is stored in either a local or central repository.

注記

In our SAP Data Services documentation, when we refer to “Data Services” without specifically including the word “Designer”, we're referring to SAP Data Services Designer unless otherwise stated.

Parent topic: Standard components [page 13]

14PUBLIC公開

管理者ガイド


関連情報

Repository [page 15]Job Server [page 16]Access Server [page 17]Management Console [page 17]Adapter SDK [page 18]

2.2.2 Repository

An SAP Data Services repository contains data, such as user-created and predefined system objects, source and target metadata, and transformation rules.

Set up repositories on an open client—server platform to facilitate sharing data with other enterprise tools. Create each repository on an approved RDBMS and register each repository in the Central Management Console (CMC).

Associate your repository with one or more Job Servers, which run the jobs that you create. The following are the repository types in Data Services:

● Local repository: Required. Used by an application designer to store definitions of objects, like projects, jobs, work flows, and data flows. Also stores source and target metadata.

● Central repository: Optional. Used in a multiuser environment for version control. Stores a copy of all objects in a project, and preserves all versions so reversion is possible.Multiuser development includes other advanced features such as labeling and filtering to provide you with more flexibility and control in managing application objects.For more information about local and central repositories, see the Designer Guide.

● Profiler repository: Optional. Stores information generated by the Data Profiler, which helps you determine the quality of your data.


関連情報

Designer [page 14]Job Server [page 16]Access Server [page 17]Management Console [page 17]Adapter SDK [page 18]

管理者ガイド


公開 15

2.2.3 Job Server

The SAP Data Services Job Server starts the data movement engine that integrates data from multiple heterogeneous sources.

The Job Server performs complex data transformations, and manages extractions and transactions from ERP systems and other sources in batch and real-time modes. The Job Server delivers high data throughput and scalability through the following techniques:

● Distributed query optimization● Multi threaded processes● In memory caching● In memory data transformations● Parallel processes

When you initiate a job in Designer, the Job Server runs the job as follows:

● Retrieves the job information from the repository.● Starts the applicable engine to process the job.

In your production environment, the Job Server runs jobs triggered by a scheduler or by a real-time service managed by the Access Server.

In production environments, balance job loads by creating a Job Server group. Job Server groups consist of multiple Job Servers that run jobs according to overall system load.

Engine processes

When you run Data Services jobs, the Job Server starts engine processes to perform data extraction, transformation, and movement. The engine uses parallel processing and in-memory data transformations to deliver high data throughput and scalability.

Service

The Data Services service starts Job Servers and Access Servers when you restart your system. The installer installs the service when it installs the Job and Access Servers. The service name on Windows is SAP Data Services. The UNIX equivalent is a daemon named AL_JobService.


関連情報

Designer [page 14]Repository [page 15]

16PUBLIC公開

管理者ガイド


Access Server [page 17]Management Console [page 17]Adapter SDK [page 18]

2.2.4 Access Server

The Access Server collects message requests, routes them to a real-time service, and delivers message replies within a user-specified time frame.

The Access Server queues messages and sends them to the next available real-time service across any number of computing resources. This approach provides automatic scalability because the Access Server initiates additional real-time services on additional computing resources when traffic for a given real-time service is high. You can configure multiple Access Servers.

For more information about the Access Server, see the Post Installation section of the Installation Guide and see the Administrator section of the Management Console Guide.


関連情報

Designer [page 14]Repository [page 15]Job Server [page 16]Management Console [page 17]Adapter SDK [page 18]

2.2.5 Management Console

The Management Console contains a collection of Web-based applications for administering multiple SAP Data Services features and objects.

The Management Console administers the following Data Services processes:

● Executes jobs and services● Analyzes object relationships● Evaluates job execution performance● Confirms data validity● Generates data quality reports

Management Console includes several applications as described in the following table.

管理者ガイド


公開 17

Application Description

Administrator Manage your production environment, which includes, for example:

● Batch job execution● Real-time services● Web services● Adapter instances● Server groups● Central repositories● Profiler repositories

Impact and Lineage Analysis Analyze the end-to-end impact and lineage for source and target objects used within the Data Services local repository.

Operational Dashboard View dashboards that provide statistics for job execution, job status, and job performance for one or more repositories over a given time period.

Data Validation Dashboard Evaluate the reliability of your target data based on the validation rules that you created in your batch jobs. Quickly review, assess, and identify potential inconsistencies or errors in source data.

Auto Documentation View, analyze, and print graphical representations of all objects as depicted in the Designer including their relationships, properties, and more.

Data Quality Reports View and export reports for batch and real-time jobs, such as job summaries and data quality transform reports.

For details about the applications, and for more information about how to use the Management Console, see the Management Console Guide.


関連情報

Designer [page 14]Repository [page 15]Job Server [page 16]Access Server [page 17]Adapter SDK [page 18]

2.2.6 Adapter SDK

The SAP Data Services Adapter SDK provides a Java platform for rapid development of adapters to other applications and middleware products such as EAI (Enterprise Application Integration) systems.

18PUBLIC公開

管理者ガイド


Adapters use industry-standard XML and Java technology to ease the learning curve. Adapters provide all necessary styles of interaction including the following:

● Reading, writing, and request-reply from SAP Data Services to other systems.● Request-reply from other systems to SAP Data Services.

For detailed information about the Adapter SDK, see the Adapter SDK User Guide.


関連情報

Designer [page 14]Repository [page 15]Job Server [page 16]Access Server [page 17]Management Console [page 17]

2.3 Management tools

SAP Data Services provides utilities to help you manage your repositories and servers.


関連情報

Data Services and the SAP BI portfolio [page 12]Standard components [page 13]Operating systems [page 21]Distributed architecture [page 21]SAP applications integration [page 23]

管理者ガイド


公開 19

2.3.1 Manage license keys

Use the License Key manager in the Central Management Console or in a command line to manage your product activation keycodes.

Activation keycodes are alphanumeric codes that the system refers to each time you run certain applications, such as SAP Data Services Designer. You can't open or run Data Services without current license keys. For more information about the License Key manager, see the Information platform services Administrator Guide.

関連情報

ライセンスマネージャ [page 205]

2.3.2 Repository Manager

Use the Repository Manager to create repositories, upgrade repositories, and check the versions of repositories.

The Repository Manager is a utility for creating and managing repositories. When you create a local repository during installation, you don't have to use the Repository Manager. However, to create additional repositories, edit existing repositories, or update existing repositories, you use the Repository Manager.

関連情報

Configuring a Data Services local repository [page 57]

2.3.3 Server Manager

Use the Server Manager to add, delete, and edit the properties of Job Servers and Access Servers and to define links between Job Servers and repositories.

Use the server manager to perform the following tasks:

● Link multiple Job Servers on different machines to a single repository for load balancing.● Link one Job Server to multiple repositories to support individual repositories, for example, to separate a

test repository from a production repository.● Specify SMTP server settings for the smtp_to email function.● Add or edit System Landscape Directory (SLD) registration information for Data Services.

20PUBLIC公開

管理者ガイド


https://help.sap.com/viewer/latest/212dee6a944d49618dc87ade60db0207/4.3.2/en-US/46c957cc6e041014910aba7db0e91070.html?q=%22license%20key%22

関連情報

Use the Server Manager on Windows [page 114]Using the Server Manager on UNIX systems [page 123]

2.4 Operating systems

SAP Data Services supports many types of operating systems and versions.

Ensure that the operating system on which you install SAP Data Services is tested and approved by SAP. For a complete list of operating systems approved by SAP for SAP Data Services, see the Product Availability Matrix (PAM) on the SAP Support Portal.


関連情報

Data Services and the SAP BI portfolio [page 12]Standard components [page 13]Management tools [page 19]Distributed architecture [page 21]SAP applications integration [page 23]

2.5 Distributed architecture

SAP Data Services offers flexibility to design your system using a distributed architecture.

The architecture includes an Access Server, which can serve multiple Job Servers and repositories. The multi-user licensed extension allows multiple Designers to work from a central repository.

Distribute components across a number of computers to best support the traffic and connectivity requirements of your network. Design a system that is distributed minimally for developing and testing. Or, design a system distributed so that it scales with the demands of a production environment.

Adhere to the following rules when you distribute software components across multiple computers:

● Engine processes must run on the same computer as the Job Server that spawns them.● Adapters require a local Job Server.

The following diagram shows an example of Data Services Designer in a distributed architecture.

管理者ガイド


公開 21

https://help.sap.com/viewer/disclaimer-for-links?q=https://apps.support.sap.com/sap/support/pam?hash=pvnr%3D67838200100900005703


Host names and port numbers [page 22]Communication between your SAP Data Services systems occurs through TCP/IP connections that you specify by IP addresses (host names) and port numbers.


関連情報

Data Services and the SAP BI portfolio [page 12]Standard components [page 13]Management tools [page 19]Operating systems [page 21]SAP applications integration [page 23]

2.5.1 Host names and port numbers

Communication between your SAP Data Services systems occurs through TCP/IP connections that you specify by IP addresses (host names) and port numbers.

22PUBLIC公開

管理者ガイド


Communication in the Data Services system occurs between Web applications, the Access Server, the Job Server, and real-time services. If your network doesn't use static IP addresses, use the name of the computer as the host name. If your network uses static IP addresses, use the static IP number as the host name for Access Server and Job Server configurations.

To create a system that is scalable, ensure that each component maintains its own list of connections. Define the connections through the following components:

● Data Services Server Manager● Management Console Administrator● Data Services Repository Manager● Message Client library calls from the Web client

For a list of the default port numbers used by Data Services, see the Installation Guide.

Parent topic: Distributed architecture [page 21]

2.6 SAP applications integration

SAP Data Services integrates with SAP applications and infrastructures with specific tools, such as the SAP System Landscape Directory (SLD) for lifecycle management of your SAP systems.

The following table provides brief descriptions for each integration tool for your SAP environment.

Data Services integration tools

SAP tool Description

SAP System Landscape Directory (SLD) Central source for system landscape information for lifecycle management. Provides a directory with information about all installable software available from SAP.

Automatically updates data about installed systems in your landscape. Provides a foundation for tool support to plan software lifecycle tasks in your system landscape.

SAP Solution Manager Organizes SAP and non SAP solutions by implementing, supporting, operating, and monitoring the following:

● Integrated content● Tools● Methodologies

Change and Transport System (CTS+) Transports ABAP and non-ABAP objects, including Data Services objects, from source systems to target systems for lifecycle management.

管理者ガイド


公開 23

SAP tool Description

Monitoring with CA Wily Introscope Web application management product that enables monitoring and diagnosing performance problems that occur in Java-based SAP modules in production.

Provides visibility into custom Java applications and connections to back-end systems.

Isolates performance bottlenecks in Netweaver modules, such as the following:

● Individual Servlets● JSPs● EJBs● JCOs● Classes● Methods


関連情報

Data Services and the SAP BI portfolio [page 12]Standard components [page 13]Management tools [page 19]Operating systems [page 21]Distributed architecture [page 21]The Enhanced Change and Transport System (CTS+) [page 175]SAP System Landscape Directory (SLD) [page 193]Solution Manager Diagnostics (SMD) Agent [page 194]

24PUBLIC公開

管理者ガイド


3 Security

SAP Data Services addresses enterprise security concerns and provides administrators and system architects with answers to security questions.

Data Services relies on the Central Management Server (CMS) for authentication and security features.

For complete information about the security features provided by the CMS, see the SAP BusinessObjects BI Platform Administrator Guide or the SAP BusinessObjects Information Platform Services Administrator Guide.

Data protection and privacy [page 26]SAP provides specific features and functions to support compliance with relevant legal requirements, including data protection and privacy.

Firewall for secure administrative functions [page 27]Use a firewall to prevent unintended remote access to SAP Data Services and administrative functions.

External DTD in XML documents [page 28]An external DTD (Data Type Definition) in an XML document that you send to the SDK can increase security vulnerabilities.

Message client library [page 28]Some message client libraries with real-time services lack an authorization requirement.

Temporary cache files [page 29]Temporary cache files are not encrypted and cause a security risk when they contain confidential or other sensitive data.

SSL or TLS for Data Services components [page 31]Secure Sockets Layer (SSL), and its newer version, Transport Layer Security (TLS), are cryptographic protocols that provide security and data integrity for network communications.

Configure SSL for the CMS connection [page 41]Use the Secure Sockets Layer (SSL) protocol for all network communications between SAP Data Services clients and the SAP Central Management Server (CMS)

SSL for Metadata Browsing and View Data Services [page 42]Use Secure Sockets Layer (SSL) protocol for all network communications between SAP Data Services, back-end engines, and EIM Adaptive Processing Server services.

Password encryption [page 45]In the SAP Data Services system, all passwords are encrypted using the AES algorithm with 128-bit keys.

Repository password required [page 47]By default, the SAP Data Services system requires that you enter the repository user name and password when you log into applications that use the repository.

管理者ガイド

SecurityPUBLIC

公開 25

3.1 Data protection and privacy

SAP provides specific features and functions to support compliance with relevant legal requirements, including data protection and privacy.

Data protection is associated with numerous legal requirements and privacy concerns. In addition to compliance with applicable data privacy regulations, SAP considers compliance with industry-specific legislation in different countries. SAP doesn't give advice on whether the provided features and functions are the best method to support company, industry, regional, or country-specific requirements. Also, SAP-provided information doesn't give advice or make recommendations for additional features that are required in particular IT environments. Make your protection and privacy decisions on a case-by-case basis. Consider your system landscape and the legal requirements of your company, industry, region, or country.

注記

In the majority of cases, compliance with applicable data protection and privacy laws is not covered by an SAP product feature. SAP software supports data protection compliance by providing security features and specific data protection-relevant functions, such as simplified blocking and deletion of personal data. SAP doesn't provide legal advice in any form. SAP uses definitions and other terms in this document that aren’t from any given legal source.

SAP software places the data that you provide into trace logs, sample reports, repositories, and so on, as side-effect data. In other words, your data finds its way into places other than output files. It's your responsibility to delete this data.

In addition, Data Services doesn't run any virus scan applications on persisted data. To protect persisted data, we strongly recommend running your own virus scan software on any system that runs Data Services.

The following list contains a few examples of where Data Services uses customer data:

● Log files: When you enable the Trace all option, Data Services prints data in some log files.● Bulkload directory: If a job using bulk-load functionality fails, Data Services saves data files that contain

customer data in the bulkload directory so you can review and analyze the data. The default bulkload directory location is %DS_COMMON_DIR%/log/BulkLoader.

● Data Services repository: The smtp_to and mailer functions use mail ID numbers as input parameters, which Data Services saves in the repository.

● Data Services repository: Data Services places a sampling of customer data in the Data Services repository when the “full” option is enabled during side-effect data generation for Global Address Cleanse and Universal Data Cleanse.

● Sample Report: The Global Address Cleanse transform places a sample of user address data into the sample report.

Parent topic: Security [page 25]

関連情報

Firewall for secure administrative functions [page 27]External DTD in XML documents [page 28]

26PUBLIC公開

管理者ガイド

Security

Message client library [page 28]Temporary cache files [page 29]SSL or TLS for Data Services components [page 31]Configure SSL for the CMS connection [page 41]SSL for Metadata Browsing and View Data Services [page 42]Password encryption [page 45]Repository password required [page 47]

3.2 Firewall for secure administrative functions

Use a firewall to prevent unintended remote access to SAP Data Services and administrative functions.

In a distributed installation, configure your firewall so that the Data Services components are able to communicate with each other as needed.

For information about configuring ports on your firewall, see your operating system firewall documentation. For information about port assignments, see the Installation Guide.


関連情報

Data protection and privacy [page 26]External DTD in XML documents [page 28]Message client library [page 28]Temporary cache files [page 29]SSL or TLS for Data Services components [page 31]Configure SSL for the CMS connection [page 41]SSL for Metadata Browsing and View Data Services [page 42]Password encryption [page 45]Repository password required [page 47]Host names and port numbers [page 22]

管理者ガイド

SecurityPUBLIC

公開 27

3.3 External DTD in XML documents

An external DTD (Data Type Definition) in an XML document that you send to the SDK can increase security vulnerabilities.

A DTD contains information that defines a document type, such as an XML document. When it's defined separately (external) from an XML document, it can cause a security risk. Therefore, don't use external DTDs (data type definitions) in XML documents that you send to the SDK.

例

The following code example shows an XML document with a reference to an external DTD. The DTD file note.dtd is defined in a file in the system that is external to the XML document.

<?xml version="1.0" encoding="UTF-8" standalone="no" ?> <!DOCTYPE note SYSTEM "note.dtd"> <note> <to>Mr.X</to> <from>Mr.Y</from> <message>Stack Overflow is awesome</message></note>


関連情報

Data protection and privacy [page 26]Firewall for secure administrative functions [page 27]Message client library [page 28]Temporary cache files [page 29]SSL or TLS for Data Services components [page 31]Configure SSL for the CMS connection [page 41]SSL for Metadata Browsing and View Data Services [page 42]Password encryption [page 45]Repository password required [page 47]

3.4 Message client library

Some message client libraries with real-time services lack an authorization requirement.

The message client libraries, such as Java and C++ for real-time services don't require authorization to connect. Keep this security risk in mind when you use these libraries.

For more information about using the Message Client library, see the SAP Data Services Integrator Guide.

28PUBLIC公開

管理者ガイド

Security


関連情報

Data protection and privacy [page 26]Firewall for secure administrative functions [page 27]External DTD in XML documents [page 28]Temporary cache files [page 29]SSL or TLS for Data Services components [page 31]Configure SSL for the CMS connection [page 41]SSL for Metadata Browsing and View Data Services [page 42]Password encryption [page 45]Repository password required [page 47]

3.5 Temporary cache files

Temporary cache files are not encrypted and cause a security risk when they contain confidential or other sensitive data.

SAP Data Services generates temporary cache files for functions and operations, such as profiling, joins, and table comparisons. When you process confidential or other sensitive data, that data can end up in temporary cache files. Both pageable and persistent caches create data files that aren't encrypted.

Temporary file location

Secure your temporary files using the appropriate permissions at the operating system level.

Data Services stores temporary files, including cache files, in <DS_COMMON_DIR>¥log¥pCache¥<ServerName_RepositoryName>.

Pageable cache

The pageable cache option in a data flow enables the system to remove the files automatically after a data flow finishes running.

管理者ガイド

SecurityPUBLIC

公開 29

Persistent cache

When you use metadata from a persistent cache type of datastore, the data isn't encrypted. It is your responsibility to secure the data using operating system file and directory permissions.

long data

When you process long data types, such as BLOB or CLOB, in databases that are large, Data Services stores the data in temporary cache files. When long data is cached, such as for a join, sort, or table comparison process, Data Services deletes the cache when it finishes executing the job.

Data Services also deletes a long data cache file when the data is out of scope. For example, the data is out of scope under the following circumstances:

● The data flow loads the data to a target.● A query transform filters the data out.● Data Services converts a long datatype to a varchar.

Encrypting temporary cache files [page 30]Set SAP Data Services to encrypt specific temporary cache files to protect personal information.


関連情報

Data protection and privacy [page 26]Firewall for secure administrative functions [page 27]External DTD in XML documents [page 28]Message client library [page 28]SSL or TLS for Data Services components [page 31]Configure SSL for the CMS connection [page 41]SSL for Metadata Browsing and View Data Services [page 42]Password encryption [page 45]Repository password required [page 47]

3.5.1 Encrypting temporary cache files

Set SAP Data Services to encrypt specific temporary cache files to protect personal information.

Data Services can encrypt the following temporary cache files:

● Persistent cache datastore files

30PUBLIC公開

管理者ガイド

Security

● Pageable cache data flow files● Cache files from functions such as lookup, search_replace, distinct, and group_by.● Cache files from transforms such as Data Quality transforms and Table Comparison

Data Services deletes the files immediately after the data flow finishes executing.

注記

Encrypting temporary cache files can slow job performance significantly.

Encrypting the cache files is optional.

To encrypt the specific temporary cache files, perform the following steps:

1. Open the DSConfig.txt file, located in <DS_COMMON_DIR>¥conf.

2. Add the following parameter to the String section: pageable_cache_encrypt_data =.

3. Enter the value yes.

pageable_cache_encrypt_data = yes

4. Save and close the dsconfig.txt file.

Task overview: Temporary cache files [page 29]

3.6 SSL or TLS for Data Services components

Secure Sockets Layer (SSL), and its newer version, Transport Layer Security (TLS), are cryptographic protocols that provide security and data integrity for network communications.

Transport Layer Security (TLS) is the standard specification published by the IETF that is based on earlier SSL specifications. Use TLS for Windows version 10 and higher.

注記

When you see the term “SSL” or “SSL/TLS” in this document, understand that you can use TLS when it is supported by your database system, and when you use Widows 10 and higher versions.

The SSL/TLS protocol allows client/server applications to communicate across a network in a way designed to prevent eavesdropping, tampering, and message forgery. SSL/TLS provides endpoint authentication and communications confidentially over the network using cryptography.

Protected communication paths [page 32]Within the SAP Data Services platform, SSL/TLS is supported for all communication paths between components that communicate over a network.

Default certificates [page 34]By default, the SAP Data Services installer creates a set of SSL certificates for secure communication between Data Services components.

Copying certificates in a distributed environment [page 35]Manually copy trusted certificates to all machines in a distributed environment.

管理者ガイド

SecurityPUBLIC

公開 31

Enable or disable SSL on select communication paths [page 36]SAP Data Services uses multiple communication paths, therefore, there are many methods to enable or disable SSL for any given path.

Using custom certificates [page 39]SAP Data Services includes a set of SSL certificates by default, however, you can use your own certificates.

Generating keys and signing certificates [page 40]To use custom certificates for SSL security in SAP Data Services, generate the certificates and have them signed by a trusted certificate authority (CA), such as VeriSign.


関連情報

Data protection and privacy [page 26]Firewall for secure administrative functions [page 27]External DTD in XML documents [page 28]Message client library [page 28]Temporary cache files [page 29]Configure SSL for the CMS connection [page 41]SSL for Metadata Browsing and View Data Services [page 42]Password encryption [page 45]Repository password required [page 47]

3.6.1 Protected communication paths

Within the SAP Data Services platform, SSL/TLS is supported for all communication paths between components that communicate over a network.

The following diagram illustrates the communication channels within the Data Services architecture that support SSL/TLS.

32PUBLIC公開

管理者ガイド

Security

注記

All TCP/IP communication paths support SSL/TLS.

注記

Depending on the communication for your web application server, you can switch your clients that use HTTP to the HTTPS protocol.

For information about configuring HTTPS with Data Services Management Console, see SAP Note 1423991.

When you use a server group with a distribution level of “Sub data flow”, SSL/TLS also protects the TCP/IP communication path between sub data flows that are on different job servers within the server group. The following diagram illustrates the communication path.

管理者ガイド

SecurityPUBLIC

公開 33

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/1423991


Parent topic: SSL or TLS for Data Services components [page 31]

関連情報

Default certificates [page 34]Copying certificates in a distributed environment [page 35]Enable or disable SSL on select communication paths [page 36]Using custom certificates [page 39]Generating keys and signing certificates [page 40]

3.6.2 Default certificates

By default, the SAP Data Services installer creates a set of SSL certificates for secure communication between Data Services components.

The default certificates use 2048-bit RSA keys and are valid for 30 years.

To use your own custom certificates, configure the certificates after installation.


関連情報

Protected communication paths [page 32]Copying certificates in a distributed environment [page 35]Enable or disable SSL on select communication paths [page 36]

34PUBLIC公開

管理者ガイド

Security

Using custom certificates [page 39]Generating keys and signing certificates [page 40]

3.6.3 Copying certificates in a distributed environment

Manually copy trusted certificates to all machines in a distributed environment.

When you install SAP Data Services components on multiple machines, and each installation has its own root and intermediate certificate authority (CA) configuration, you must manually copy the trusted certificate files from one machine to all other machines.

注記

Trusted certificate files are root and intermediate CA certificate files. Trusted certificate files have a .crt extension, and are located in the <LINK_DIR>¥ssl¥trusted_certs folder.

注意

When you copy trusted certificates from one host machine to another, always copy the files to and from the <LINK_DIR>¥ssl¥trusted_certs folder on each respective machine.

Each step represents a different scenario. Find the step that represents your situation and perform the substeps.

1. If the Job Server and Access Server are installed on different machines, configure the hosts with the new certificates by performing the following substeps.a. Copy the trusted certificates from the Access Server to the Job Server host.b. Run the following batch file on the Job Server host machine to refresh the <LINK_DIR>¥ssl

¥trusted_certs¥jssecacerts keystore file:

○ On Windows: <LINK_DIR>¥bin¥SetupJavaKeystore.bat○ On UNIX: $LINK_DIR/bin/SetupJavaKeystore.sh

After you run the batch files, adapters that communicate with the Access Server use the new certificates.

c. Copy the trusted certificates from the Job Server to the Access Server host.d. Restart the job service on both the Job Server and Access Server host machines.

2. If the Access Server and Management Console are installed on different machines, configure the Management Console host with the new certificates by performing the following substeps:a. Copy the trusted certificates from the Access Server to the Management Console host.b. Run the following batch file on the Management Console host machine to refresh the <LINK_DIR>

¥ssl¥trusted_certs¥jssecacerts keystore file:

○ On Windows: <LINK_DIR>¥bin¥SetupJavaKeystore.bat○ On UNIX: $LINK_DIR/bin/SetupJavaKeystore.sh

c. Restart the web application server that hosts the Management Console.3. If the Access Server and message client are installed on different machines, configure the message client

host with the new certificates by performing the following substeps:a. Copy the trusted certificates from the Access Server to the message client host.

管理者ガイド

SecurityPUBLIC

公開 35

b. If the message client host uses Java, import the trusted certificates into the keystore used by the message client application.For information about creating keystores, see the JDK help for the keytool command.

4. If the Job Server and job launcher or external scheduler are installed on different machines, copy the trusted certificates from the Job Server to the job launcher or external scheduler host.

注記

If the scheduled job connects to multiple Job Servers through a server group, copy the trusted certificates from all Job Servers within the group.

Task overview: SSL or TLS for Data Services components [page 31]

関連情報

Protected communication paths [page 32]Default certificates [page 34]Enable or disable SSL on select communication paths [page 36]Using custom certificates [page 39]Generating keys and signing certificates [page 40]

3.6.4 Enable or disable SSL on select communication paths

SAP Data Services uses multiple communication paths, therefore, there are many methods to enable or disable SSL for any given path.

Choose to enable or disable SSL on select communication paths based on your security and performance requirements. The following table describes the types of communication paths.

Communication path Considerations

Adapter management Enable SSL on your Job Servers to protect the communication path between your Job Servers and adapters and message broker clients.

To configure SSL on a Job Server, use the Data Services Server Manager.

36PUBLIC公開

管理者ガイド

Security


Real-time messaging Enable SSL on your Access Servers to protect the communication path between your Access Servers and their real-time clients.

注記

By default, SSL is enabled for real-time messaging. If you disable it on an Access Server, be sure to disable it on any message clients or adapters that communicate with that Access Server.

注記

You can enable or disable SSL on a per-server basis. You don't have to configure SSL the same way for all Access Servers.

To configure SSL on an Access Server, use the Data Services Server Manager.

Peer-to-peer communication Enable SSL by configuring SSL for run-time resources to protect the communication path between sub data flows running on different Job Servers.

注記

If you run multiple Job Servers within a server group, configure SSL the same way on each Job Server.

To configure SSL for run-time resources, use the Data Services Server Manager.

管理者ガイド

SecurityPUBLIC

公開 37


Other communication paths SSL is required for other communication paths in the Data Services architecture, and is already enabled.

For example, SSL is always enabled on the communication paths between a Job Server and the following clients:

● The Administrator application in the Management Console

● SAP Data Services Designer● The job launcher● Access Servers● The job execution engine● Other Job Servers within a server group● The job service used for monitoring

Ensure that each client has the correct certificates for these other communication paths. however, there are no additional configuration steps to perform.

注記

You must copy the certificates from the Job Server to the Access Server, Management Console, and external job launcher hosts. In all other cases, the certificates are exchanged automatically.


関連情報

Protected communication paths [page 32]Default certificates [page 34]Copying certificates in a distributed environment [page 35]Using custom certificates [page 39]Generating keys and signing certificates [page 40]Use the Server Manager on Windows [page 114]Using the Server Manager on UNIX systems [page 123]

38PUBLIC公開

管理者ガイド

Security

3.6.5 Using custom certificates

SAP Data Services includes a set of SSL certificates by default, however, you can use your own certificates.

Before you perform the following task, generate custom certificates and have them signed by a trusted certificate authority (CA). For instructions, see Generating keys and signing certificates [page 40].

To use custom certificates instead of the certificates provided by Data Services, perform the following steps:

注記

The following steps are based on different Data Services deployments. Perform the steps that apply to your specific deployment.

1. Copy all required custom certificates to the Data Services client machine or machines.

注記

When the system validates the certificates for the Data Services server, it requires that each Data Services client has the certificates for all CAs in the certificate chain. The certificates within a certificate chain are called “trusted certificates”. Trusted certificates must be present on the local machine. In most cases, the certificate chain is the same for all clients, and therefore the same certificates must be present on all client machines.

2. If you use Java-based clients, generate a keystore that contains the trusted certificates using the JDK keytool utility.

3. Configure server certificate and keyfile paths with the SAP Data Services Server Manager.4. Configure certificates for SAP Data Services Designer.

a. Choose Tools Options in Designer.b. Expand the Designer node and select the SSL node.c. Specify the locations for the following options:

○ Server certificate file○ Server private key file○ Trusted certificates folder

If you change any SSL options other than Use SSL protocol for profiler, you must restart both the Designer and any Data Services servers.


関連情報

Protected communication paths [page 32]Default certificates [page 34]Copying certificates in a distributed environment [page 35]Enable or disable SSL on select communication paths [page 36]Generating keys and signing certificates [page 40]

管理者ガイド

SecurityPUBLIC

公開 39

SSL パスの設定 [page 122]

3.6.6 Generating keys and signing certificates

To use custom certificates for SSL security in SAP Data Services, generate the certificates and have them signed by a trusted certificate authority (CA), such as VeriSign.

To generate custom SSL certificates and have them signed, perform the following steps:

1. Open a command prompt and use the Open SSL toolkit with a command like the following:

openssl req -config <DS_COMMON_DIR>¥ssl¥conf¥openssl.conf -new -newkey rsa:2048 -nodes -keyout <mykey.pem> -out <myreq.pem>

Where:○ <mykey.pem> is the name of the key file to generate.○ <myreq.pem> is the name of the certificate file to generate.

注記

By default, OpenSSL is installed to <DS_COMMON_DIR>¥bin. For more information about available options and commands, see the OpenSSL documentation at https://www.openssl.org/docs/ .

2. Send the RSA private key and certificate files to your external CA.3. After you receive the signed certificate from your CA, use the SAP Data Services Server Manager to specify

the path to the new certificate and private key file.

注記

Trusted certificates from an external CA must be in PEM format.

4. Copy the signed certificates to the <DS_COMMON_DIR>¥ssl¥trusted_certs directory.


関連情報

Protected communication paths [page 32]Default certificates [page 34]Copying certificates in a distributed environment [page 35]Enable or disable SSL on select communication paths [page 36]Using custom certificates [page 39]SSL パスの設定 [page 131]

40PUBLIC公開

管理者ガイド

Security

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

3.7 Configure SSL for the CMS connection

Use the Secure Sockets Layer (SSL) protocol for all network communications between SAP Data Services clients and the SAP Central Management Server (CMS)

To set up SSL for all CMS communication, you need to perform the following tasks:

● Deploy the SAP BusinessObjects BI platform or Information Platform Services with SSL enabled.● Create key and certificate files for each machine in your deployment.● Configure the location of the key and certificate files in the Central Configuration Manager (CCM) and your

web application server.

For Data Services, use the sslconfig utility to configure all components that log into the CMS for SSL, including the following components:

● SAP Data Services Designer● Job Servers● External schedulers and the job launcher● SAP Data Services Management Console (if deployed to a different web application server than the SAP

BusinessObjects BI platform or Information platform services web tier)

注記

For J2EE web application servers, configure SSL by modifying the startup script.

By default, the sslconfig utility is installed in the following location:

● For Windows:<INSTALL_DIR>¥SAP BusinessObjects Enterprise XI 4.0¥win32_x86¥sslconfig.exe

● For UNIX:$INSTALL_DIR/sap_bobj/enterprise_xi40/<platform>/boe_sslconfigWhere <platform> matches your UNIX platform.

For more information about sslconfig.exe and configuring the SSL protocol for CMS and its clients, see the SAP BusinessObjects BI Platform Administrator Guide or the SAP BusinessObjects Information Platform Services Administrator Guide.


関連情報

Data protection and privacy [page 26]Firewall for secure administrative functions [page 27]External DTD in XML documents [page 28]Message client library [page 28]Temporary cache files [page 29]SSL or TLS for Data Services components [page 31]SSL for Metadata Browsing and View Data Services [page 42]

管理者ガイド

SecurityPUBLIC

公開 41

Password encryption [page 45]Repository password required [page 47]

3.8 SSL for Metadata Browsing and View Data Services

Use Secure Sockets Layer (SSL) protocol for all network communications between SAP Data Services, back-end engines, and EIM Adaptive Processing Server services.

The following EIM Adaptive Processing Server services use SSL:

● Metadata Browsing Service● View Data Service

Data Services provides the EIM Adaptive Processing Server services, but they're used by other SAP software products, such as the Data Insight module of SAP Information Steward.

Data Services provides the keystore file and the trusted certificates file by default. The following table describes each file.

File Description

Java Server keystore Contains a single key and all the certificates that are part of the certificate chain involved in signing the key on the server side. Password files for the Java Server keystore file and the key are also required.

Data Services places the default keystore file and password files in <LINK_DIR>¥ssl¥mds.

Trusted certificate Certificates in a certificate chain, used for signing the key that is stored in the Java keystore on the server side. The client side, the Data Services back-end engine, uses the trusted certificates to communicate with the server.

Data Services places the trusted certificates in <LINK_DIR>¥ssl¥mds¥trusted_certs .

Configuring SSL for Metadata Browsing and View Data Services [page 43]The Metadata Browsing Service and View Data Service are EIM Adaptive Processing Server services that use SSL.

Creating keystore file and certificates for default [page 44]Use custom keystore file and SSL certificate instead of using the default files provided for the Metadata Browsing Service and View Data Service services.


42PUBLIC公開

管理者ガイド

Security

関連情報

Data protection and privacy [page 26]Firewall for secure administrative functions [page 27]External DTD in XML documents [page 28]Message client library [page 28]Temporary cache files [page 29]SSL or TLS for Data Services components [page 31]Configure SSL for the CMS connection [page 41]Password encryption [page 45]Repository password required [page 47]

3.8.1 Configuring SSL for Metadata Browsing and View Data Services

The Metadata Browsing Service and View Data Service are EIM Adaptive Processing Server services that use SSL.

To enable and configure SSL communications for Metadata Browsing and View Data Services, perform the following steps:

1. Log into the Central Management Console (CMC) as a user with administrative rights to SAP Data Services.

2. Open the Applications management page of the CMC.3. Right-click Data Services Application and choose Settings.4. Choose Yes from the Enable SSL communication for Metadata Browsing and View Data Services list.5. To use the default keystore and certificates that Data Services provides, perform the following substeps:

a. Choose Yes from the Use Default SSL Settings list.b. Select Save.

6. To use custom certificates, perform the following substeps:

Your keystore must be a Java keystore file that contains a single key with all the certificates that are part of the certificate chain involved in signing the key. Provide a password for the key and a password for the keystore file.

Your keystore file must be in the <LINK_DIR>¥ssl¥mds directory. The corresponding certificate files must be in the <LINK_DIR>¥ssl¥mds¥trusted_certs directory.

a. For multiple instances of Metadata Browsing Service or View Data Service associated with the same CMS server, copy the keystore and certificate files to all the machines where these instances are installed.

b. Choose No from the Use Default SSL Settings list.c. Enter the name of the KeyStore file in KeyStore File.d. Enter the applicable password in KeyStore Password.e. Enter the applicable password in Key Password.

管理者ガイド

SecurityPUBLIC

公開 43

f. Select Save.7. Restart the EIM Adaptive Processing Server by performing the following substeps:

a. Open the Servers management area.b. Expand the Service Categories node and select the Enterprise Information Management Services node.c. Select the EIMAdaptiveProcessingServer from the Server Name column in the right pane.

d. Select Action Restart Server .

The State column lists “Stopping”, then “Starting”, and finally “Running”.

Selecting the Refresh icon helps to update the status in the State column.

Task overview: SSL for Metadata Browsing and View Data Services [page 42]

関連情報

Creating keystore file and certificates for default [page 44]

3.8.2 Creating keystore file and certificates for default

Use custom keystore file and SSL certificate instead of using the default files provided for the Metadata Browsing Service and View Data Service services.

Before performing the following steps, configure SSL for the Metadata Browsing Service and View Data Service services following the instructions in Configuring SSL for Metadata Browsing and View Data Services [page 43]. Ensure that you select Yes for Use Default SSL Settings when you configure SSL for the services.

To create a keystore file and SSL certificates for the default SSL settings, perform the following steps:

1. Run the MDSSetupJavaKeyStore.bat tool.

The MDSSetupJavaKeyStore.bat file is in <LINK_DIR>¥bin by default.

The MDSSetupJavaKeyStore batch file creates the files described in the following table:

File name Location Description

DSJavaKeyStore.keystore <LINK_DIR>¥ssl¥mds Keystore file that contains a single key and all the certificates that are part of the certificate chain for signing the key.

sslks.key <LINK_DIR>¥ssl¥mds Key password.

sslstore.key <LINK_DIR>¥ssl¥mds Keystore password.

2. Restart the EIMAdaptiveProcessingServer in the Central Management Console.The restart picks up the new keystore and certificate files as the default files.

Task overview: SSL for Metadata Browsing and View Data Services [page 42]

44PUBLIC公開

管理者ガイド

Security

関連情報

Configuring SSL for Metadata Browsing and View Data Services [page 43]

3.9 Password encryption

In the SAP Data Services system, all passwords are encrypted using the AES algorithm with 128-bit keys.

Encryption key storage locations [page 45]The SAP Data Services system stores passwords for files and applications, and it stores individual keys associated with each password in specific locations.

Encrypt passwords manually [page 46]Manually encrypt passwords when encryption isn't handled automatically by the SAP Data Services applications and utilities.


関連情報

Data protection and privacy [page 26]Firewall for secure administrative functions [page 27]External DTD in XML documents [page 28]Message client library [page 28]Temporary cache files [page 29]SSL or TLS for Data Services components [page 31]Configure SSL for the CMS connection [page 41]SSL for Metadata Browsing and View Data Services [page 42]Repository password required [page 47]

3.9.1 Encryption key storage locations

The SAP Data Services system stores passwords for files and applications, and it stores individual keys associated with each password in specific locations.

The following table lists each file or application that has a password, and the associated password key location.

管理者ガイド

SecurityPUBLIC

公開 45

Password for Associated key location

Local repository REPOKEY column in the AL_VERSION table

Central repository REPOKEY column in the AL_VERSION table

Management Console admin.key located in the same directory as admin.xmlAccess Server AS.key located in the same directory as AS.xmlAdapter SDK <DS_COMMON_DIR>/adapters/adapter.key

DSConfig.txt <DS_COMMON_DIR>/conf/DSConfig.keyData Services-managed schedules If the schedule uses a password file, the password is stored

in the password file.

If the schedule doesn't use a password file, the password is located in the job command line.

External scheduler command lines If the schedule uses a password file, the password is stored in the password file.

If the schedule doesn't use a password file, the password is located in the job command line.

警告

For encryption keys that are stored in files, Data Services protects the security of the key file with strong OS permissions. For example, the software sets owner-only read and write access to the file (chmod 600 on UNIX systems). You should also protect the key file by restricting user access to the server host machine when possible.

Parent topic: Password encryption [page 45]

関連情報

Encrypt passwords manually [page 46]

3.9.2 Encrypt passwords manually

Manually encrypt passwords when encryption isn't handled automatically by the SAP Data Services applications and utilities.

When password encryption for some tasks isn't handled automatically by the Data Services application or utility, manually encrypt the password.

46PUBLIC公開

管理者ガイド

Security

例You quickly generate a data flow to use with the object creation XML toolkit. The data flow contains a datastore that requires a password. Therefore, the password must be encrypted before you can import and run the data flow successfully.

To manually encrypt a password, use the al_encrypt command-line utility installed with the software. For more information about using al_encrypt for password encryption, see Command line: Password encryption [page 223]

Parent topic: Password encryption [page 45]

関連情報

Encryption key storage locations [page 45]

3.10 Repository password required

By default, the SAP Data Services system requires that you enter the repository user name and password when you log into applications that use the repository.

For example, your repository user name and password are required when you log into SAP Data Services Designer or when you open a Data Quality report in SAP Data Services Management Console.

You, as an administrator, can disable the requirement of the repository user name and password through permissions in the Central Management Console. After you disable the default behavior, the system sends the repository credentials from the Central Management Server to the client, such as Data Services, without you entering the repository user name and password.

警告

Although this password is encrypted, and you can secure the communication channel through SSL, sending passwords can pose a risk, such as malicious users obtaining access to the password.

You can selectively grant the permissions for repositories. For example, you can grant the right for development repositories but not for production repositories.

Accessing Data Services applications without repository credentials [page 48]Grant permission for certain users, or certain repositories, to open SAP Data Services applications that use the repository without entering user name and password credentials.


管理者ガイド

SecurityPUBLIC

公開 47

関連情報

Data protection and privacy [page 26]Firewall for secure administrative functions [page 27]External DTD in XML documents [page 28]Message client library [page 28]Temporary cache files [page 29]SSL or TLS for Data Services components [page 31]Configure SSL for the CMS connection [page 41]SSL for Metadata Browsing and View Data Services [page 42]Password encryption [page 45]

3.10.1 Accessing Data Services applications without repository credentials

Grant permission for certain users, or certain repositories, to open SAP Data Services applications that use the repository without entering user name and password credentials.

Before peforming the following steps, understand the application rights by viewing the table in Detailed application rights [page 52].

警告

Although the repository password is encrypted, and you can secure the communication channel through SSL, sending passwords can pose a risk, such as malicious users obtaining access to the password.

You can selectively grant the permissions for repositories. For example, you can grant the right for development repositories but not for production repositories.

To set repository permissions in the Central Management Console (CMC), perform the following steps:

1. Open the Data Services page from CMC Home.2. Select the Repositories node at left.

To assign rights to a user group for all repositories, skip the next step where you select a specific repository.

3. Select the applicable repository at right.

Select the repository to restrict access rights to a specific repository. For example, remove the requirement for repository credentials for the test repository only. To assign rights to a user group for all repositories, don't select a specific repository.

4. Choose Manage Security User Security .

The User Security page opens. Check that you selected the correct repository by looking at the repository name in the page banner.

5. Select the applicable user group under Name.Before you select the user group, consider the application from which you want to remove the repository credential requirement.

48PUBLIC公開

管理者ガイド

Security

例

○ To remove the credential requirement from Data Services Designer, select Data Services Designer Users.

○ To remove the credential requirement from Data Quality reports in the Management Console, select Data Services Monitor Users.

6. Select Assign Security.

The Assign Security page opens. Check that you have the correct user group by looking at the Principal value in the upper right corner of the page.

7. Open the Advanced tab.8. Select Add/Remove Rights.

The Add/Remove Rights page opens.9. Expand the Application node at left and select the applicable repository name.10. Under Specific Rights for Data Services Repository, select Granted for either or both of the following

options:

○ Allow user to retrieve repository password○ Allow user to retrieve repository password that user owns

11. Select OK.

All users in the selected user group now have rights for accessing an application that uses the selected repository without entering the repository credentials.

Task overview: Repository password required [page 47]

管理者ガイド

SecurityPUBLIC

公開 49

4 User and rights management

SAP Data Services uses the Central Management Server (CMS) for user accounts and rights management.

To set user accounts and rights management for administrating procedures for applications other than Data Services, see the SAP BusinessObjects BI Platform Administrator Guide or the SAP BusinessObjects Information Platform Services Administrator Guide.

User management [page 50]When you create users and groups in the Central Management Console (CMC), you also grant the user or group access rights to the repository with which they work.

Group management [page 51]Groups are collections of users who share the same account privileges, such as users in the same department, role, or location.

4.1 User management

When you create users and groups in the Central Management Console (CMC), you also grant the user or group access rights to the repository with which they work.

By default, the SAP Data Services installation program doesn't create any user accounts. Use the CMC to create new user accounts, or assign existing user accounts to the default group accounts.

For information about creating user accounts for applications other than Data Services, see the SAP BusinessObjects BI Platform Administrator Guide or the SAP BusinessObjects Information Platform Services Administrator Guide.

Parent topic: User and rights management [page 50]

関連情報

Group management [page 51]Accessing repository user security in the CMC [page 62]

50PUBLIC公開

管理者ガイド

User and rights management

4.2 Group management

Groups are collections of users who share the same account privileges, such as users in the same department, role, or location.

Manage groups in the Users and Groups area of the Central Management Console.

Groups enable administrators to change the rights and permissions for multiple users in one place instead of modifying the rights and permissions for each user account individually. Also, administrators can assign object rights to a group or groups.

In addition to the basic SAP BusinessObjects BI platform or Information Platform Services group accounts, Data Services includes several default group accounts as described in the following table.

Account name Description

Data Services Administrator Members have access to all Data Services administrative functionalities.

Data Services Designer Users Members have access to Designer.

注記

Application rights and repository security rights are two separate sets of rights. For more information about repository rights, see Detailed repository rights [page 64].

Data Services Monitor Users Members have access limited to options available from the Status tabs.

例● A Monitor User can cancel batch jobs but can't run

or schedule them.● A Monitor User can restart, cancel, or shut down an

Access Server, service, adapter instance, or client interface but can't add or remove them.

Data Services MU (Multi-user) Administrator Members are limited to managing secure central repositories. This role is a subset of the Data Services Administrator role. Multi-user administrators have the rights to perform the following tasks:

● Add and remove secure central repositories.● Manage users and groups.● View secure central repository reports.

Data Services Operator Users Members have all Administrator privileges except they can't modify repository, access, or CMS servers nor update datastore settings.

管理者ガイド

User and rights managementPUBLIC

公開 51

Account name Description

Data Services Profiler Administrator Users Members are limited to managing profiler repositories. This role is a subset of the Administrator role. Profiler administrators can do the following:

● Manage profiler tasks in any profiler repository.● Manage the Profiler configuration.

Data Services Profiler Users Members of this group are limited to managing profiler tasks in the profiler repository that is configured for the user.

Detailed application rights [page 52]Each SAP Data Services user group has default rights to the application.

Viewing application rights assigned to a group [page 55]Administrators can view application rights assigned to each SAP Data Services group in the Central Management Console (CMC).

Managing application rights for a group [page 55]Administrators can manage application rights assigned to each SAP Data Services group in the Central Management Console (CMC).

Parent topic: User and rights management [page 50]

関連情報

User management [page 50]

4.2.1 Detailed application rights

Each SAP Data Services user group has default rights to the application.

The following table lists all default application rights granted to each type of user group. In the Central Management Console (CMC), each Data Services group name is prefaced with “Data Services”. For example, Data Services Designer Users. However, because of limited space, we don't include “Data Services” in the table for Data Services user groups.

注記

The Data Services Administrator group has access to all of the available Data Services application rights. Therefore, the Administrator group isn't included in the table.

52PUBLIC公開

管理者ガイド


Application rights

Data Services user groups

Designer Users

Monitor Users

Multi-user (MU) Administrator

Operator Users

Profiler Administrator Users

Profiler Users

Management Console Administrator

X X X X X X

Management Console Auto Documentation

X X X X X X

Management Console Data Quality Reports

X X X X X X

Data Services Designer X

Management Console Impact and Lineage

X X X X X X

Management Console Operational Dashboard

X X X X X X

Management Console Validation Dashboard

X X X X X X

Management Console Administrator overview

X X X X X X

Execute batch job X X

Manage access server configurations

Manage adapter configurations X

Manage batch job history X X

Manage central repository groups X

Manage certification log configurations

Manage datastore and substitution param configurations

Manage Object Promotion Configurations

Manage Object Promotion Import

Manage profiler configurations X

Manage real-time client interface status

X

Manage real-time logs X

Manage real-time service status X

Manage real-time status X

Manage RFC client and server configurations

X

Manage server group configurations

X X

管理者ガイド


公開 53

Application rights

Data Services user groups

Designer Users

Monitor Users

Multi-user (MU) Administrator

Operator Users

Profiler Administrator Users

Profiler Users

Manage status interval configuration

Manage webservices configurations X

View adapter status X X

View batch job history X X X

View Data Quality sample data X X X X X X

View profiler status X X

View internal information in log X X

View real-time client interface status

X X

View real-time logs X X

View real-time service status X X

View real-time status X X

View RFC client status X X

View server group information X X X

View Validation sample data X X X X X X

View webservices status X X

注記

Application rights and repository security rights have separate rights. When a repository is registered, the owner is granted full access to the repository. By default, other Designer users have no access to the repository.

Parent topic: Group management [page 51]

関連情報

Viewing application rights assigned to a group [page 55]Managing application rights for a group [page 55]Detailed repository rights [page 64]

54PUBLIC公開

管理者ガイド


4.2.2 Viewing application rights assigned to a group

Administrators can view application rights assigned to each SAP Data Services group in the Central Management Console (CMC).

To perform the following steps, you must have Administrator rights or be a member of the Data Services Administrator Users group.

To view the assigned application rights for a group, perform the following steps in the CMC:

1. In CMC Home, select Applications in the Manage column.2. Double-click Data Services Application in the Application Name column.3. Select User Security.

The user groups display at right.4. Select the applicable user group to view and select View Security.

The Permissions Explorer opens and displays all of the current application rights that are assigned to your selected user group.

Task overview: Group management [page 51]

関連情報

Detailed application rights [page 52]Managing application rights for a group [page 55]

4.2.3 Managing application rights for a group

Administrators can manage application rights assigned to each SAP Data Services group in the Central Management Console (CMC).

To perform the following steps, you must have Administrator rights or be a member of the Data Services Administrator Users group.

For complete information about the windows and options mentioned in this topic, see the Business Intelligence Platform Administrator Guide.

To manage the assigned application rights for a group, perform the following steps in the CMC:

1. In CMC Home, select Applications in the Manage column.2. Double-click Data Services Application in the Application Name column.3. Select User Security.

The user groups display at right.4. Select the applicable user group and select Assign Security.

The Assign Security window opens.

管理者ガイド


公開 55

https://help.sap.com/viewer/2e167338c1b24da9b2a94e68efd79c42/latest/en-US/468e341a6e041014910aba7db0e91070.html

https://help.sap.com/viewer/2e167338c1b24da9b2a94e68efd79c42/latest/en-US/468e341a6e041014910aba7db0e91070.html

5. Select the Advanced tab.6. Select Add/Remove rights located below the tab labels.

The Add/Remove Rights window opens. Each right is in a row with options to grant or deny the right.7. Find the row for the applicable right under Specific Rights for Data Services Application.8. Select the applicable option:

○ Select the radio dial under the Granted icon in the row for the applicable right to grant the right.○ Select the radio dial under the Deny icon in the row for the applicable right to deny access to the right.

9. Select Apply to save your changes and then select OK.

Task overview: Group management [page 51]

関連情報

Detailed application rights [page 52]Viewing application rights assigned to a group [page 55]

56PUBLIC公開

管理者ガイド


5 Repository management

Before you can access an SAP Data Services repository in other components such as the Designer and Data Services Management Console, configure the repository correctly.

Create and configure a repository by performing the tasks in the following workflow:

1. Create the repository database in an approved database management system.2. Create the repository connection using the Data Services Repository Manager.3. Associate the repository server with the Job Server in the Data Services Server Manager.4. Register the repository in the Central Management Console (CMC).5. Manage user security settings for the repository in the CMC.

For descriptions of the repository types that you can create in Data Services, see Repository [page 15].

Configuring a Data Services local repository [page 57]Enter the repository connection information in the Data Services Repository Manager.

Registering a repository in the CMC [page 60]Register a repository in the Data Services Central Management Console (CMC) by entering connection information including server name, port number, and password.

Accessing repository user security in the CMC [page 62]User security settings include granting access to the repository for users and groups, and other user and group privileges to the repository.

Oracle TCPS protocol for repositories [page 65]Choose TCPS (Transmission Control Protocol Secures) for an Oracle repository so that the client—server communication is authenticated and the data is encrypted and decrypted.

SAP HANA SSL/TLS protocol for repositories [page 71]Choose to use the Secure Socket Layer (SSL) or the newer Transport Layer Security (TLS) protocol when you configure your SAP HANA repository in the Central Management Console (CMC).

Editing the java.security file [page 74]Edit the java.security file based on the TrustStore type you select when you use either SAP HANA or Oracle for your repository.

5.1 Configuring a Data Services local repository

Enter the repository connection information in the Data Services Repository Manager.

Before you configure a new local repository, you must perform the following tasks:

● Create a database for the repository using an approved database management system.For approved databases and versions for the Data Services repository, see the Product Availability Matrix.

● For server-based (DSN-less) connections, gather the following information: Server information, database name, user name, and password.

管理者ガイド

Repository managementPUBLIC

公開 57


● For data source name (DSN) connections, create the DSN following instructions in your database documentation before you configure the repository. Then use one of the following utilities to connect with the applicable driver and create the DSN:○ Windows: ODBC Data Source Administrator○ Linux and Unix: Data Services Connection Manager

注記

If you're creating additional repositories, don't use the tools in your DBMS to replicate the additional repositories. Instead, use the Data Services Repository Manager to create and seed multiple repositories to avoid potential issues related to the configuration of repository objects.

To create a local repository in the Data Services Repository Manager, perform the following steps:

1. Open the Repository Manager:

○ Windows: Select the Start icon and then select SAP Data Services <version> Data Services Repository Manager.

○ Unix or Linux: Open a command prompt and open the Repository Manager in <$LINK_DIR>/bin/repoman.sh.

2. Choose Local from the Repository Type list.3. Select a database from the Database Type list.

The remaining options appear based on the database type that you select.4. Select Use data source name (DSN) or Use TNS name (Oracle).

Don't select this option if your connection is based on the server name.

注記

If your database doesn't support connecting with DSN or TNS, the option isn't available.

5. Select a version from the Database version list when applicable.6. The following table contains an alphabetical listing of all remaining options.

Options appear based on the type of database you selected and whether you selected to create a DSN connection.

Repository Manager Option Descriptions

Option Description

Data Source Name Specifies the DSN connection name that you created for this repository. Not applicable for server-based (DSN-less) connections

Database Name Enter the name of the database that you created for the repository. Applicable for DSN-less connections.

Database Server Name Enter the server name for the repository database. Applicable for DSN-less connections.

58PUBLIC公開

管理者ガイド

Repository management

Option Description

Database Version Select the version for the repository database management system. Not applicable for all database types.

Hostname Enter the hostname of the Oracle database.

Applicable for Oracle TNS-less connections.

Password Enter the password associated with the stated user name. Applicable for DSN-less connections.

Port Enter the server port number. Applicable for DSN-less connections.

SID Enter the Oracle system ID that uniquely identifies the database to access.

Applicable for Oracle TNS-less connections.

TNS name Specifies the connection string created by your database administrator for the TNS. Not applicable for server-based (TNS-less) connections.

Applicable for Oracle databases only.

User Name Enter the user name associated with the specified repository database. Applicable for DSN-less connections.

7. After you complete all applicable options, select Create.8. When the repository is created successfully, select Close.

Before you can use the new local repository, perform the following tasks:

● Associating a Job Server to a repository [page 117]● Registering a repository in the CMC [page 60]

Task overview: Repository management [page 57]

関連情報

Registering a repository in the CMC [page 60]Accessing repository user security in the CMC [page 62]Oracle TCPS protocol for repositories [page 65]SAP HANA SSL/TLS protocol for repositories [page 71]Editing the java.security file [page 74]接続マネージャの使用 [page 89]

管理者ガイド


公開 59

5.2 Registering a repository in the CMC

Register a repository in the Data Services Central Management Console (CMC) by entering connection information including server name, port number, and password.

Before you perform the following steps, make sure that you perform the following tasks:

● Create the repository in the Data Services Repository Manager: Configuring a Data Services local repository [page 57].

● Associate the repository to a Job Server: Associating a Job Server to a repository [page 117].

1. Log into the Central Management Console (CMC) as a user with administrative rights to the SAP Data Services application.

2. Open the Data Services page.

3. Select Manage Configure Repository .The Add Data Services Repository dialog box opens.

4. Specify a name and optionally a description for the repository.After you complete the registration, the repository name and description show in the Designer and Data Services Management Console applications.

5. Select a type from the Database Type list.6. Enter the connection information for the repository database. Options vary based on the database type

you select.The following table contains descriptions for common connection options. For descriptions of options specific to the database type, see that database type topic for registering a repository in the CMC.

Common CMC Repository Registration options

Option Description

Database Server Name The service or server name used to connect to the repository.

注記

For Microsoft SQL Server or Sybase ASE, don't use localhost for the server name. If you use localhost, other machines are unable to connect to the repository.

Port Enter the port number of the database server.

Database Name Enter the name of the database for the repository.

User Name Enter the user name for accessing the repository

Password Enter the password for accessing the repository.

60PUBLIC公開

管理者ガイド


Option Description

Is Profiler Repository Select one of the following values:○ Yes: This repository is for the Data Services Profiler. If

you select Yes, also complete Profiler Server Host Name and Profiler Server Port options.

○ No: This repository is for the local or central repositories.

Profiler Server Host Name Enter the host name of the web application server hosting the profiler.

Applicable when you select Yes for Is Profiler Repository.

Profiler Server Port Enter the port number used by the web application server hosting the profiler.

Applicable when you select Yes for Is Profiler Repository.

Data Source Name (DSN) Enter the data source name that you created for this repository. Leave blank for a server-based (DSN-less) connection.

注記

DSN-less is the default connection type for DB2, MySQL, or SAP HANA databases.

注記

If you use DSN connections in a distributed installation, configure the database connection to the repository the same on each machine as in the CMC. For example, if you configured a repository with the DSN my_dsn in the CMC, you must also configure the DSN of my_dsn for the Designer and Job Server machines.

7. Select Test Connection.Data Services attempts to verify the connection details without adding the repository to the CMC. If the connection isn't successful, review the error message and correct the repository connection information.

8. When the connection test is successful, select Save.

The new repository appears in the list of registered repositories in the Data Services application page.


関連情報

Configuring a Data Services local repository [page 57]Accessing repository user security in the CMC [page 62]Oracle TCPS protocol for repositories [page 65]

管理者ガイド


公開 61

SAP HANA SSL/TLS protocol for repositories [page 71]Editing the java.security file [page 74]

5.3 Accessing repository user security in the CMC

User security settings include granting access to the repository for users and groups, and other user and group privileges to the repository.

Manage security settings for repositories that are registered in the Data Services Central Management Console (CMC) using the security options in the Manage menu.

注記

To perform the following steps, you must have administrative rights to SAP Data Services.

To set user and group privileges to a repository, perform the following steps in the CMC:

1. Open the Data Services page.2. Highlight the Repositories node in the navigation tree at left.

A list of all repositories appears at right.

3. Select Manage Security User Security.

The User Security page for the selected repository opens.

Viewing rights for a user or group on a repository [page 63]View user and group rights to a repository when you open the user security page in the Central Management Console (CMC).

Assigning users and groups to an access control list for a repository [page 63]Assign a user or group to an access control list, which specifies the users or groups that are granted or denied rights to a repository.

Detailed repository rights [page 64]Each access right comes with specific repository rights for the user or group.


関連情報

Configuring a Data Services local repository [page 57]Registering a repository in the CMC [page 60]Oracle TCPS protocol for repositories [page 65]SAP HANA SSL/TLS protocol for repositories [page 71]Editing the java.security file [page 74]

62PUBLIC公開

管理者ガイド


5.3.1 Viewing rights for a user or group on a repository

View user and group rights to a repository when you open the user security page in the Central Management Console (CMC).

To view user and group rights to a repository, perform the following steps:

1. Log into the CMC and open the Data Services page.2. Select the Repositories node at left.3. Select the repository for which you want to view security settings from the list at right.

4. Select Manage Security User Security.The User Security page for the selected repository opens. The page displays a list of users and groups that have access to the repository, and their access type.

5. Highlight a user or group from the list, and select View Security.The Permissions Explorer page opens. The page displays a list of rights for the user or group to the repository.

6. Select OK to close the Permissions Explorer.

Task overview: Accessing repository user security in the CMC [page 62]

関連情報

Assigning users and groups to an access control list for a repository [page 63]Detailed repository rights [page 64]

5.3.2 Assigning users and groups to an access control list for a repository

Assign a user or group to an access control list, which specifies the users or groups that are granted or denied rights to a repository.

To assign the same access right to select users and groups for a specific repository, perform the following steps:

1. Log into the CMC and open the Data Services page.2. Select the Repositories node at left.3. Select the applicable repository from the list at right.

4. Select Manage Security User Security .The User Security page opens. The Access column lists the access type for each listed user or group in the Name column.

5. Select Add Principals.The Add Principals page opens.

管理者ガイド


公開 63

6. Select the User List node or the Group List node from the Available Users or Groups list at left.

The applicable users or groups appear in the center pane.7. Select one or more user or group from the center pane list as applicable.8. Select the right-pointing arrow.

ヒント

To select both users and groups, first select the User List node, select the user or users, and select the right-pointing arrow. Then select the Group List node, select the group or groups, and select the right-pointing arrow.

The system adds the selected users or groups to the Selected Users or Groups list at right.9. Select Add and Assign Security at the bottom of the page.

The Assign Security page opens.10. Select the access level to grant to the user or group and select the right-pointing arrow to add the users or

groups to the Assigned Access Level list.11. Select OK.

The Assign Security page closes and the User Security page reopens. Notice that the access type in the Access list changes to the new access level for the applicable user or group.

Task overview: Accessing repository user security in the CMC [page 62]

関連情報

Viewing rights for a user or group on a repository [page 63]Detailed repository rights [page 64]

5.3.3 Detailed repository rights

Each access right comes with specific repository rights for the user or group.

The following table lists some of the common repository rights that are available to the Full Control and the View access rights.

Repository right Full control View

Add objects to the folder X

Copy objects to another folder X

Delete objects X

Edit objects X

Modify the rights users have to objects X

64PUBLIC公開

管理者ガイド


Repository right Full control View

Replicate content X

Securely modify right inheritance settings X

Securely modify right users have to objects X

Translate objects X

Use access level for security assignment X

View objects X X

To view all repository rights related to Full Control and View access rights, select the user or group that has Full Control in the User Security page and select View Security. The rights are listed in the Permissions Explorer page.

注記

Application rights and repository security rights are two separate sets of rights. When a repository is registered, the owner is granted full access to the repository. By default, other Designer users have no access to the repository.

Parent topic: Accessing repository user security in the CMC [page 62]

関連情報

Viewing rights for a user or group on a repository [page 63]Assigning users and groups to an access control list for a repository [page 63]Detailed application rights [page 52]

5.4 Oracle TCPS protocol for repositories

Choose TCPS (Transmission Control Protocol Secures) for an Oracle repository so that the client—server communication is authenticated and the data is encrypted and decrypted.

TCPS protocol is an optional feature that Data Services supports for an Oracle repository. The TCPS protocol secures an Oracle repository by encrypting SSL/TLS and server authentication. When you choose to use TCPS protocol for your Oracle repository, perform the required prerequisites.

管理者ガイド


公開 65

Required prerequisites

Before you configure TCPS, install the required Oracle Advanced Security files and comply with Oracle SSL/TLS requirements. Consult the Oracle documentation for details. The Advanced Security files contain the necessary files to configure TCPS for an Oracle repository in SAP Data Services.

Obtain the following information after you install the Oracle Advanced Security files:

● Connection string to connect to the Oracle database.● Cipher Suites to use for the TLS-SSL network protocol as applicable.● SSL TrustStore location, type, and password as applicable.

Additionally, ensure that you perform the following tasks in Data Services before configuration:

● Install the required JDBC driver file ojdbc<x>.jar. See the Product Availability Matrix (PAM) on the SAP Support Portal to determine the correct version for <x>.

注記

For instructions to configure JDBC driver files, see the Installation Guide.

● Create a TNS (Transparent Network Substrate) for the Oracle database. See the Oracle documentation for information.

Oracle references

For information about Oracle TCPS protocol, and the prerequisite steps, see the following documentation:

● For additional information about your connection and using wallets for TrustStores, see SSL with Oracle JDBC Thin Driver, an Oracle white paper. To access the whitepaper, copy and paste the following URL in your browser: https:/www.oracle.com/technetwork/topics/wp-oracle-jdbc-thin-ssl-130128.pdf.

● For information about the Oracle Security requirements, go to the Oracle Database Documentationpage and select your version from the list. Then select Security under Topics.

Configurations in the java.security folder [page 67]When you enable the TCPS protocol for your Oracle repository, configure the Cipher Suite information by editing the Java Security file based on the security selections that you make.

Configuring for JCE Cipher Suites [page 68]JCE Cipher Suites provide stronger cryptography encryption than the Cypher Suites provided with the Oracle Advanced Security files.

Configuring Oracle repository for TCPS protocol [page 69]Secure your Oracle repository using TCPS protocol when you register the repository in the Central Management Console (CMC).

Parent topic: Repository management [page 57]

66PUBLIC公開

管理者ガイド



http://help.sap.com/disclaimer?site=https%3A%2F%2Fdocs.oracle.com%2Fen%2Fdatabase%2Foracle%2Foracle-database%2Findex.html

関連情報

Configuring a Data Services local repository [page 57]Registering a repository in the CMC [page 60]Accessing repository user security in the CMC [page 62]SAP HANA SSL/TLS protocol for repositories [page 71]Editing the java.security file [page 74]Configuring JDBC drivers for SAP HANA, Oracle, and MySQL

5.4.1 Configurations in the java.security folder

When you enable the TCPS protocol for your Oracle repository, configure the Cipher Suite information by editing the Java Security file based on the security selections that you make.

When you configure the Oracle repository using TCPS, SAP Data Services repository setup asks for the following information:

● The type of Cipher Suites that ou use, if applicable.

注記

Use the Cipher Suites that don't use the Diffie-Hellman anonymous authentication.

● TCPS information.

The following special requirements apply based on your TCPS selections:

● If you choose to use PKCS12 wallet for the SSL TrustStore Type option, edit the java.security file for the Oracle PKI provider. For instructions, see Editing the java.security file [page 74].

● If you choose to use Cipher Suites, modify the java.security file to comment out a specific row. For instructions, see Editing the java.security file [page 74].

● If you choose to use Cipher Suites that have stronger encryption (key lengths greater than 128 bits), obtain and add additional JAR files to the security folder. For instructions, see Configuring for JCE Cipher Suites [page 68].

Parent topic: Oracle TCPS protocol for repositories [page 65]

関連情報

Configuring for JCE Cipher Suites [page 68]Configuring Oracle repository for TCPS protocol [page 69]

管理者ガイド


公開 67

https://help.sap.com/viewer/aad3428705d9497daed23eca43e0dab9/4.2.14/ja-JP/573eaf9f6d6d1014b3fc9283b0e91070.html

5.4.2 Configuring for JCE Cipher Suites

JCE Cipher Suites provide stronger cryptography encryption than the Cypher Suites provided with the Oracle Advanced Security files.

Cipher Suites with key lengths of 128 bits are included in the Oracle Advanced Security files along with the necessary JAR files. Cipher Suites with key lengths of more than 128 bits, such as 256 bits, provide stronger encryption. To use Cipher Suites with stronger encryption, you must perform extra steps.

Before you perform the following steps, obtain the JAR files for the stronger Cipher Suites from the JCE (Java Cryptography Encryption) Unlimited Strength Jurisdiction Policy Files. For more information about the JCE files, and to access the JCE Cipher Suites download page, see “Enabling Cipher Suites for Stronger Encryption” on the Open Source Elastic Stack Web page at https://www.elastic.co/guide/en/shield/current/ciphers.html

.

To implement the JCE Unlimited Strength Jurisdiction Policy Files Cipher Suites, perform the following steps:

1. Download and unzip the JCE zip file and extract the following 2 files to <BOE_INSTALL_DIR>¥SAP BusinessObjects Enterprise XI 4.0¥<win64_x64 or win32_x32>¥sapjvm¥jre¥lib¥security:

○ local_policy.jar○ US_export_policy.jar

2. Restart the EIM Adaptive Processing Server in the Central Management Console (CMC).a. Log into the CMC.b. Open the Servers pagec. Expand Service Categories and select Enterprise Information Management Services.

d. Highlight the EIM Adaptive Processing server and select Actions Restart Server.

The status in the State column switches to Stopping, Starting, and finally Running.

注記

Select the Refresh icon several times to update the State column.

3. Obtain the official Cipher Suite names. SAP Data Services requires the names when you configure the Oracle repository for TCPS protocol. To obtain the official JCE Cipher Suite names, perform the following steps:a. Go to the Oracle documentation “Java Cryptography Architecture Standard Algorithm Name

Documentation for JDK 16” at https://docs.oracle.com/en/java/javase/16/docs/specs/security/standard-names.html .

The link takes you to Java SE 16 documentation. Make sure to look at the list relative to your version of Java SE.

b. To open the list, scroll down the list of names in the Standard Names list and click the “JSSE Cipher Suite names” link.

c. Find the name of the Cipher Suite you downloaded in the Standard Name column.d. When you configure the repository connection in the CMC in a later process, enter the Cipher Suite

name or names in the SSL Cypher Suite option as they're listed in the JSSE Cipher Suite names list.

Task overview: Oracle TCPS protocol for repositories [page 65]

68PUBLIC公開

管理者ガイド


http://help.sap.com/disclaimer?site=https%3A%2F%2Fwww.elastic.co%2Fguide%2Fen%2Fshield%2Fcurrent%2Fciphers.html

http://help.sap.com/disclaimer?site=https%3A%2F%2Fwww.elastic.co%2Fguide%2Fen%2Fshield%2Fcurrent%2Fciphers.html

http://help.sap.com/disclaimer?site=https%3A%2F%2Fdocs.oracle.com%2Fen%2Fjava%2Fjavase%2F16%2Fdocs%2Fspecs%2Fsecurity%2Fstandard-names.html

http://help.sap.com/disclaimer?site=https%3A%2F%2Fdocs.oracle.com%2Fen%2Fjava%2Fjavase%2F16%2Fdocs%2Fspecs%2Fsecurity%2Fstandard-names.html

関連情報

Configurations in the java.security folder [page 67]Configuring Oracle repository for TCPS protocol [page 69]

5.4.3 Configuring Oracle repository for TCPS protocol

Secure your Oracle repository using TCPS protocol when you register the repository in the Central Management Console (CMC).

Ensure that you complete the prerequisites as listed in Oracle TCPS protocol for repositories [page 65]. Also perform the following tasks:

● Create the Oracle database repository with the Repository Manager and use the TNS name that you created.

● Modify the java.security file using the information in Editing the java.security file [page 74].● If you use Cipher Suites with stronger encryption, update the security folder with additional JAR files

following instructions in Configuring for JCE Cipher Suites [page 68].

To configure your Oracle repository with TCPS protocol, perform the following steps in the Central Management Console:

1. Select Data Services from the Organize column.

2. Select Manage Configure Repository.

The Add Data Services Repository dialog box opens.3. Enter a repository name and optionally enter a description.4. Select Oracle from the Database Type list.5. Select Yes for Use Oracle TCPS.

If applicable, select Yes for Use Oracle RAC.

注記

These instructions don't include steps for Oracle RAC.

6. Enter information for Oracle TCPS based on the option descriptions in the following table.

If an option isn't applicable, leave it blank.

管理者ガイド


公開 69

TCPS option descriptions

Option Description

Connection String Enter the connection string to the Oracle database using the following format:

(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=<servername>)(PORT=<port>))(CONNECT_DATA=(SERVICE_NAME=<servicename>)))

SSL Cipher Suites Enter the official Cipher Suite name. To list multiple names, separate each name by commas. Enter the suite name or names in parentheses.

例(SSL_RSA_WITH_RC4_128_CBC_SHA,SSL_RSA_WITH_3DES_EDE_CBC_SHA,SSL_RSA_WITH_RC4_128_SHA,TLS_RSA_WITH_AES_256_CBC_SHA)

To ensure that you enter the official Cipher Suite names, see Configuring for JCE Cipher Suites [page 68].

SSL TrustStore Enter the path and file name for the SSL TrustStore.

注記

The SSL TrustStore is the repository for trusted certificates. Use the SSL TrustStore for authenticating client certificates for two-way SSL.

SSL TrustStore Type Enter the TrustStore type:○ JKS (Java KeyStore): For Java 8 and earlier. Format-

specific for Java.○ PCKS12: For Java 9 and later. Standardized and

language-neutral.

注記

If you use Oracle PKCS12, remember to update the java.security file with the Oracle pki provider.

SSL TrustStore Password Enter the TrustStore password.

70PUBLIC公開

管理者ガイド


Option Description

SSL KeyStore Not required for SSL encryption and server authentication. Leave blank.

注記

The SSL KeyStore holds the identity key for the server.

SSL KeyStore type Not required for SSL encryption and server authentication. Leave blank.

SSL KeyStore Password Not required for SSL encryption and server authentication. Leave blank.

7. Enter the user name and password for the repository.8. Select No for Is Profiler Repository.

If this repository is a profiler repository, select Yes and complete the options for host name and port number for the host Web application server.

9. Click Test Connection. When the connection test is successful, click Save.

If your connection isn't successful, and you used Oracle PKCS12 or Cipher Suites, ensure that you correctly configured the java.security file. If you use Cipher Suites with stronger encryption, ensure that you added the additional JAR files to the security folder.

Task overview: Oracle TCPS protocol for repositories [page 65]

関連情報

Configurations in the java.security folder [page 67]Configuring for JCE Cipher Suites [page 68]Configuring JDBC drivers for SAP HANA, Oracle, and MySQL

5.5 SAP HANA SSL/TLS protocol for repositories

Choose to use the Secure Socket Layer (SSL) or the newer Transport Layer Security (TLS) protocol when you configure your SAP HANA repository in the Central Management Console (CMC).

SSL/TLS protocol is an optional feature that adds a level of security for repositories that use the SAP HANA database.

管理者ガイド


公開 71

https://help.sap.com/viewer/aad3428705d9497daed23eca43e0dab9/4.2.14/ja-JP/573eaf9f6d6d1014b3fc9283b0e91070.html

注記

Ensure that you have installed SAP Data Services version 4.2.11 (14.02.11.02) or later version before you proceed with the processes for including SSL/TLS for your SAP HANA repository.

Before you configure SSL/TLS, install the Public Key Infrastructure (PKI) from the SAP HANA installer. The PKI provides the CommonCryptoLib Library as the cryptographic library. Then gather the following information:

● SSL TrustStore type, location, password● SSL KeyStore type, location, password

注記

Make sure that the locations of the TrustStore and KeyStore are local so the Central Management Console (CMC) can access them.

Additionally, ensure that you perform the following tasks before you configure the SAP HANA repository in the CMC:

1. Configure the bundled JDBC driver files for SAP HANA

注記

For instructions, see the Installation Guide.

2. If you plan to use a data source name (DSN) connection for the repository, create the DSN using the ODBC Data Source Administrator (Windows) or the SAP Data Services Connection Manager (Unix).

注記

If you plan to use a server-name (DSN-less) connection, skip this step.

3. If you did not create the SAP HANA repository during installation, create the SAP HANA database repository with the Repository Manager.

4. Edit the Java security file following the steps in Editing the java.security file [page 74].

SAP HANA に対する CMC での SSL/TLS の設定 [page 73]SSL/TLS プロトコルに SAP HANA リポジトリを設定するには、リポジトリの設定時にセントラル管理コンソール

(CMC) で適切な設定を行います。

Parent topic: Repository management [page 57]

関連情報

Configuring a Data Services local repository [page 57]Registering a repository in the CMC [page 60]Accessing repository user security in the CMC [page 62]Oracle TCPS protocol for repositories [page 65]Editing the java.security file [page 74]

72PUBLIC公開

管理者ガイド


5.5.1 SAP HANA に対する CMC での SSL/TLS の設定

SSL/TLS プロトコルに SAP HANA リポジトリを設定するには、リポジトリの設定時にセントラル管理コンソール (CMC) で適切な設定を行います。

SAP HANA SSL/TLS protocol for repositories [71 ページ] の手順を実行していることを確認します。Registering a repository in the CMC [60 ページ] の手順に従って、CMC でリポジトリの登録プロセスを実行します。このプロセス中

に、以下のステップのとおりに SSL/TLS オプションを設定します。

注記

SSL/TLS プロトコルを有効化すると、CMC で DSN 接続はサポートされません。

1. CMC の Data Services リポジトリの追加ダイアログボックスで、SSL を有効にするドロップダウンリストからはいを選

択します。

2. サーバ証明書の確認ドロップダウンリストからはいを選択します。

CMC で、SSL 関連オプションが有効になります。

3. 該当する場合は、ホスト名の上書きの値を入力します。

4. 次のテーブルのとおりに SAP HANA の残りの SSL/TLS オプションを入力します。

SSL/TLS オプションの説明

オプション値

SSL キーストア SSL キーストアの場所を入力します。

注記

CMC でキーストアにアクセスすることができることを確認し

ます。

○ Windows: キーストアはローカルドライブに配置され

ます。

○ Unix/Linux: CMC がフォルダにアクセスすることがで

きる限り、場所は問題となりません。

SSL キーストアの種類ドロップダウンリストから適切なキーストアのファイル形式タイプ

を選択します。

○ JKS○ PKCS12

SSL キーストアのパスワード該当する場合、パスワードを入力して、指定したキーストアファ

イルの秘密鍵にアクセスします。

SSL 信頼ストア SSL 信頼ストアの場所を入力します。

管理者ガイド


公開 73

オプション値

SSL 信頼ストアの種類ドロップダウンリストから適切な SSL 信頼ストアのファイル形式

タイプを選択します。

○ JKS○ PKCS12

このオプションの選択に関係なく、Editing the java.security file [74 ページ] の手順に従って java.security ファイルを

編集する必要があります。

SSL 信頼ストアのパスワード該当する場合、パスワードを入力して、指定した SSL 信頼スト

アファイルの秘密鍵にアクセスします。

5. 接続テストを実行します。リポジトリの接続テストが成功したら、保存をクリックします。

CMC で、新しいリポジトリが CMC Data Services ページのリポジトリノードに追加されます。

タスクの概要: SAP HANA SSL/TLS protocol for repositories [71 ページ]

5.6 Editing the java.security file

Edit the java.security file based on the TrustStore type you select when you use either SAP HANA or Oracle for your repository.

Edit the java.security file under the following circumstances:

● Oracle: When you select to use an Oracle PKCS12 as your TrustStore type or you choose to use Cipher Suites with either PKCS12 or JKS.

● SAP HANA: When you select to use PKCS12 or JKS as your TrustStore type.

The following steps apply to either Oracle or SAP HANA databases as your repository.

1. Open the java.security file that is installed with JRE.

The file is located in <BOE_INSTALL_DIR>¥SAP BusinessObjects Enterprise XI 4.0¥win64_x64¥sapjvm¥jre¥lib¥security¥java.security.

2. Copy and paste the provider information as instructed for your database type:a. Oracle: If you select to use Oracle PKCS12 as the SSL TrustStore type, copy the Oracle provider

information from Oracle and paste the information to the specified location in the provider list in the java.security file.

The provider information and instructions for specific placement are located in the Oracle white paper, SSL with Oracle JDBC Thin Driver. To access the whitepaper, copy and paste the following URL in your browser: https:/www.oracle.com/technetwork/topics/wp-oracle-jdbc-thin-ssl-130128.pdf.

b. SAP HANA: If you select to use PKCS12 or JKS as the SSL TrustStore type, copy the SAP HANA provider information from SAP HANA and paste the information to the specified location in the provider list in the java.security file.

Search the Java security file for the following sentence: List of providers and their perference order. Enter the provider information in the format specified in the Java security file.

74PUBLIC公開

管理者ガイド


3. Oracle only: If you use Cipher Suites for TCPS protocol with either PKCS12 or JKS, follow these substeps:a. In the java.security file, search for the line that contains the option

jdk.tls.disabledAlgorithms=.b. Type a “#” to comment out the line.

If you do not comment out this line, the connection that you create using the Cipher Suites fails.4. Save and close the java.security file.

5. Restart the Server Intelligence Agent (SIA).6. If the change doesn't take effect, delete the EIM Adaptive Processing Server cache.

a. Find the EIMAPS cache at <BOE_INSTALL_DIR>¥SAP BusinessObjects Enterprise XI 4.0¥java¥pjs¥container¥work¥<WIN2K8R2X64>.EIMAdaptiveProcessingServer.

b. Delete the entire folder.

注記

The prefix <WIN2K8R2X64> may be different on your system.

c. Restart The SIA again.


関連情報

Configuring a Data Services local repository [page 57]Registering a repository in the CMC [page 60]Accessing repository user security in the CMC [page 62]Oracle TCPS protocol for repositories [page 65]SAP HANA SSL/TLS protocol for repositories [page 71]

管理者ガイド


公開 75

6 サーバの管理

サーバ管理ツールを使用して Job Server およびデータベースサーバを管理し、ODBC ドライバ、データソース名 (DSN)、およびサーバ名 (DSN なし) 接続を設定します。

DSN-less and TNS-less connections [77 ページ]DSN-less and TNS-less (Oracle) connections are also known as server name connections.

Setting UNIX environment variables [79 ページ]Set up UNIX or Linux environment variables by running a script with the applicable syntax for your environment.

Windows および Unix でのサービスの自動起動 [81 ページ]正しく実行するには、SAP Data Services ではジョブサービスおよび関連するサービス、パッケージ化された

Tomcat サービスが必要となります。

History retention and Job Server log retention [82 ページ]The job execution history files and the Job Server logs contain data to produce internal statistics, regulatory reports, or other nonregulatory reports.

UNIX および Linux のデータベース接続の設定 [87 ページ]SAP Data Services の処理目的で ODBC データベースの種類を追加するたび、SAP Data Services (DS) 接続

マネージャでサポートされているドライバを設定し、データベースへの接続を確立します。

Using the ODBC Drivers Selector for Windows [112 ページ]To configure an ODBC driver on the Windows platform, use the SAP Data Services ODBC Drivers Selector utility.

Using the License Manager [113 ページ]The License Manager allows you to add and delete licenses that you receive from SAP, such as when you buy the software or when your current license expires.

Use the Server Manager on Windows [114 ページ]Use the Data Services Server Manager for many tasks, such as to create, edit, or delete Job Servers and Access Servers after installation.

Using the Server Manager on UNIX systems [123 ページ]Use the Server Manager to create, edit, or delete Job Servers and Access Servers after installation on your UNIX platform.

Configuring Metadata Browsing Service and View Data Service [133 ページ]SAP Information Steward uses the Metadata Browsing Service and the View Data Service to connect to and view data in profiling sources.

Data Services CMC アプリケーション設定 [138 ページ]セントラル管理コンソール (CMC) で Data Services アプリケーションに関する以下の設定を変更することができ

ます。

76PUBLIC公開

管理者ガイド

サーバの管理

6.1 DSN-less and TNS-less connections

DSN-less and TNS-less (Oracle) connections are also known as server name connections.

If you configure a repository during installation, SAP Data Services creates a DSN-less or TNS-less (Oracle) connection to the repository database by default.

Server name connections eliminate the need to configure the same DSN (Data Source Name) or TNS ( Oracle Transparent Network Substrate) entries on every machine in a distributed environment.

制限

To configure the repository using a DSN or TNS connection, skip the repository creation during installation and create the repository after installation.

The following table lists all eligible database types for the Data Services repository, and the supported connection types.

Repository database types and supported connection types

Database DSN DSN-less

DB2 Yes Yes

Microsoft SQL Server No Yes

My SQL Yes Yes

Oracle Yes: TNS Yes: TNS-less

SAP HANA Yes Yes

SQL Anywhere Yes Yes

Sybase ASE No Yes

For databases that you use as sources and targets in Data Services, the database type determines the type of connection you can create. Some databases support both types of connections while other support one or the other.

The following table lists all eligible source and target databases and the connection types they support.

Source and target databases and supported connections


Amazon Redshift Yes No

Attunity Connector No Yes

Data Federator No Yes

DB2 (Linux, UNIX, Windows) Yes Yes

管理者ガイド

サーバの管理

PUBLIC公開 77


Hive Yes Yes

HP Vertica Yes No

Informix Yes Yes

Microsoft SQL Server No Yes

My SQL Yes Yes

Netezza Yes Yes

ODBC Yes No

Oracle Yes: TNS Yes: TNS-less

PostgreSQL Yes Yes

SAP HANA Yes Yes

Snowflake Yes Yes

SQL Anywhere Yes Yes

Sybase ASE No Yes

SAP IQ (Sybase IQ) Yes Yes

Teradata Yes Yes

The information in the database tables is subject to change and may not reflect the most up-to-date information. For current lists of supported databases and versions for repository or sources and targets, see the Product Availability Matrix (PAM) on the SAP Support Portal.

Parent topic: サーバの管理 [page 76]

関連情報

Setting UNIX environment variables [page 79]Windows および Unix でのサービスの自動起動 [page 81]History retention and Job Server log retention [page 82]UNIX および Linux のデータベース接続の設定 [page 87]Using the ODBC Drivers Selector for Windows [page 112]Using the License Manager [page 113]Use the Server Manager on Windows [page 114]Using the Server Manager on UNIX systems [page 123]

78PUBLIC公開

管理者ガイド

サーバの管理


Configuring Metadata Browsing Service and View Data Service [page 133]Data Services CMC アプリケーション設定 [page 138]

6.2 Setting UNIX environment variables

Set up UNIX or Linux environment variables by running a script with the applicable syntax for your environment.

When you install SAP Data Services on UNIX or Linux platforms, the SAP Data Services Job Server requires that you set environment variables. To set these variables, run the script file al_env.sh.

To run the file, use the syntax required by your environment.

例

$ cd $LINK_DIR/bin/ $ . ./al_env.sh

You can also add a command to your login script so that the environment variable is always configured. For example, add the following line to .profile:

. $LINK_DIR/bin/al_env.sh

Troubleshooting

If the script fails to run, the system does not issue an error. Therefore, to check that you properly set the variable values, check one or more of the environment variables described in the following table:

Variable Details

$LINK_DIR Points to the default Data Services installation directory, set by the installer.

$DS_COMMON_DIR Includes the $LINK_DIR path for compatibility.

$SHLIB_PATH For 64-bit Oracle clients, make sure that you list $LINK_DIR/bin before any 64-bit Oracle shared library path.

$LD_LIBRARY_PATH For Solaris or Linux, make sure that the variable includes $LINK_DIR/bin and the location of the database libraries.

To use a 64-bit Oracle client, make sure that you list $LINK_DIR/bin before any 64-bit Oracle shared library path.

管理者ガイド

サーバの管理

PUBLIC公開 79

Variable Details

$LIBPATH For AIX, make sure that the variable includes $LINK_DIR/bin and the location of the database libraries.

To use a 64-bit Oracle client, make sure that you list $LINK_DIR/bin before any 64-bit Oracle shared library path.

$ORACLE_SID Required for an Oracle source, target, or repository.

$ORACLE_HOME Required for an Oracle source, target, or repository.

To use a 64-bit Oracle client, make sure this variable points to the 64-bit Oracle installation.

$DB2INSTANCE Required for a DB2 source, target, or repository.

$DB2DIR Required for a DB2 source, target, or repository.

$SYBASE Required for an SAP ASE source, target, or repository.

$SYBASE_OCS Required for an SAP ASE source, target, or repository.

$ODBCINI Required for ODBC sources or targets. Contains the data source name (DSN) information for all existing DSNs. For MySQL, the variable is $ODBCSYSINI.

$ODBCINST Required for ODBC sources or targets. Contains the ODBC driver information for installed drivers.

注記

For the MySQL ODBC driver, set the driver location in the $ODBCSYSINI environment variable instead of the $ODBCINST environment variable. Make sure that the odbcinst.ini file exists. If you do not set the location in $ODBCSYSINI, Data Services uses /etc/odbcinst.ini by default for the instance file.

$PATH Make sure that the variable includes $LINK_DIR/bin and <databasehome>/bin.

ヒント

Use the echo command to verify environment variable settings.

If you don't properly configure the variable settings and you start any Data Services utility, the software issues error messages that indicate there are missing database server files.

If you see errors about missing database server files, verify that al_env.sh contains commands to set the appropriate database home locations. Run al_env.sh for the account used by the Job Server, or start the Job Server using an account that has all necessary environment variables defined in its .profile.

80PUBLIC公開

管理者ガイド

サーバの管理

ヒント

To use the RFC Server Interface in the Management Console on a 64-bit UNIX platform, see the Management Console Guide for additional environment configuration information.


関連情報

DSN-less and TNS-less connections [page 77]Windows および Unix でのサービスの自動起動 [page 81]History retention and Job Server log retention [page 82]UNIX および Linux のデータベース接続の設定 [page 87]Using the ODBC Drivers Selector for Windows [page 112]Using the License Manager [page 113]Use the Server Manager on Windows [page 114]Using the Server Manager on UNIX systems [page 123]Configuring Metadata Browsing Service and View Data Service [page 133]Data Services CMC アプリケーション設定 [page 138]

6.3 Windows および Unix でのサービスの自動起動

正しく実行するには、SAP Data Services ではジョブサービスおよび関連するサービス、パッケージ化された Tomcat サービスが必要となります。

Data Services の一部の設定を行うときは、サービスを停止する必要があります。Data Services を終了するときも、サー

ビスを停止します。サービスを手動で再起動する必要がある場合もあります。それ以外の場合は、サービスは自動的に再

実行されます。

Windows の場合

Data Services のサービスおよびパッケージ化された Tomcat サービスは、コンピュータを起動または再起動すると自動

で起動されます。再起動されたコンピュータで、Data Services サービスが Job Server と Access Server を起動します。

該当する場合は、Windows のサービスウィンドウで、サービスの起動を手動に変更できます。

注記

Web アプリケーションに手動でログインするには、情報プラットフォームサービス管理ガイドの “Web アプリケーション

のトレース設定”の節を参照してください。

管理者ガイド

サーバの管理

PUBLIC公開 81

UNIX の場合

サーバの再起動時に Job Server と Access Server を自動的に起動するには、ルート権限を使って actaservices ス

クリプトをインストールします。Data Services では、$ LINK_DIR/bin にスクリプトファイルが格納されます。

お使いの環境でサポートされている構文を使用してスクリプトを呼び出してください。

例 # cd $LINK_DIR/bin/# autostrt.sh $LINK_DIR

親トピック: サーバの管理 [76 ページ]

関連情報

DSN-less and TNS-less connections [77 ページ]Setting UNIX environment variables [79 ページ]History retention and Job Server log retention [82 ページ]UNIX および Linux のデータベース接続の設定 [87 ページ]Using the ODBC Drivers Selector for Windows [112 ページ]Using the License Manager [113 ページ]Use the Server Manager on Windows [114 ページ]Using the Server Manager on UNIX systems [123 ページ]Configuring Metadata Browsing Service and View Data Service [133 ページ]Data Services CMC アプリケーション設定 [138 ページ]

6.4 History retention and Job Server log retention

The job execution history files and the Job Server logs contain data to produce internal statistics, regulatory reports, or other nonregulatory reports.

Set a time period for data retention in the history files and Job Server logs. After the set time period, SAP Data Services deletes retained data automatically and permanently. Therefore, know what these logs contain before setting the retention period.

ヒント

To create reports based on specific jobs, transforms, time periods, and job statistics, back up the job execution files and the Job Server log files before the retention period expires.

82PUBLIC公開

管理者ガイド

サーバの管理

It's important to delete files periodically to maintain efficient system processing. If you don't delete files periodically, the history files and Job Server logs can get large, which slows job performance. The files get large because Data Services appends information to files for each job that you run. Therefore, we recommend that you establish a maintenance management procedure.

警告

You can select to delete Job Server and history files for a specific batch job in the Data Services Management Console. Data Services deletes the selected job, history, and log files, and ignores the set retention periods in the Central Management Console (CMC).

For more information about deleting jobs, history, and log files for the selected job in the Data Services Management Console, see the Management Console Guide.

USPS-required log files and reports [page 84]Set the log retention period so that you don't lose data before the creation and submission of USPS-required logs and reports.

Setting the History Retention Period [page 85]Change the default setting of 30 days for history log file retention to increase or decrease the number of days that SAP Data Services retains the files before deleting them.

Setting the Job Server Log Retention Period [page 86]The Job Server Log Retention Period provides a set schedule for automatically deleting Job Server log files, such as server_event*.logs.


関連情報

DSN-less and TNS-less connections [page 77]Setting UNIX environment variables [page 79]Windows および Unix でのサービスの自動起動 [page 81]UNIX および Linux のデータベース接続の設定 [page 87]Using the ODBC Drivers Selector for Windows [page 112]Using the License Manager [page 113]Use the Server Manager on Windows [page 114]Using the Server Manager on UNIX systems [page 123]Configuring Metadata Browsing Service and View Data Service [page 133]Data Services CMC アプリケーション設定 [page 138]

Deleting batch job history data [page 145]Monitoring jobs [page 140]

管理者ガイド

サーバの管理

PUBLIC公開 83

6.4.1 USPS-required log files and reports

Set the log retention period so that you don't lose data before the creation and submission of USPS-required logs and reports.

Set the number of days in History Retention Period in the Central Management Console (CMC). If you have postal certification requirements such as CASS certification, the USPS requires that you submit log files to the postal authorities on a periodic basis.

例For CASS certified mailings, the USPS requires that you submit certification log files each month. The default setting for the History Retention Period option is 30 days. Thirty days don't provide enough time for you to export and send the log files to the USPS by the monthly due date. And 30 days don't account for months that include 31 days. Therefore, set the history retention to longer, such as 50 days, to ensure that you submit complete monthly logs to the USPS.

In addition to sending monthly data to the USPS, you must have report data available for the USPS to examine for several years after the job is processed. To ensure that you retain all required reports and logs before the data is deleted from the repository, consider exporting the required reports and logs from the repository to a local folder on a monthly basis. Exporting reports and logs to a local folder also prevents the repository contents from becoming so large that the export process times out because of the volume of statistics retained.

View stored job execution history files in the Administrator application of the SAP Data Services Management Console.

警告

Many history files contain job statistics and other information required for statistics and regulatory reports. Make sure that you understand what your job history files are used for before you set a number of days to delete them. Also be aware of current USPS rules for data retention by viewing your USPS licensing agreement.

For information about regulatory statistics and log files, see the Designer Guide. For information about trace and error logs, data quality reports, and troubleshooting, see the Management Console Guide.

Parent topic: History retention and Job Server log retention [page 82]

関連情報

Setting the History Retention Period [page 85]Setting the Job Server Log Retention Period [page 86]

84PUBLIC公開

管理者ガイド

サーバの管理

6.4.2 Setting the History Retention Period

Change the default setting of 30 days for history log file retention to increase or decrease the number of days that SAP Data Services retains the files before deleting them.

To change the History Retention Period setting, perform the following steps:

1. Log into the Central Management Console and open the Applications page.2. Right-click Data Services Application from the Application Name column and select Settings.

The Data Services Application Settings dialog box opens.3. Type an integer in the History Retention Period text box.

例The following table describes results for specific settings.

Value Results

30 Data Services retains job history files for 30 days before deleting.

0 Data Services doesn't retain any of the job history files.

Negative number Data Services retains job history files indefinitely.

4. Select Save.

If Data Services is performing background processes, it can take up to an hour before the new setting goes into effect.

Task overview: History retention and Job Server log retention [page 82]

関連情報

USPS-required log files and reports [page 84]Setting the Job Server Log Retention Period [page 86]

管理者ガイド

サーバの管理

PUBLIC公開 85

6.4.3 Setting the Job Server Log Retention Period

The Job Server Log Retention Period provides a set schedule for automatically deleting Job Server log files, such as server_event*.logs.

The default setting for the Job Server Log Retention Period is 30 days. To change the setting, perform the following steps:

1. Log into the Central Management Console (CMC) and select Applications.2. Right-click Data Services Application from the Application Name column and select Settings.

The Data Services Application Settings dialog box opens.3. Type an integer in the Job Server Log Retention Period text box.

The value sets the number of days that SAP Data Services retains the Job Server log files.

例The following table describes results for specific settings.

Value Results

30 Default setting. Software retains Job Server logs for 30 days.

0 Software doesn't retain Job Server logs.

Negative number Software retains Job Server logs indefinitely.

4. Select Save.

If Data Services is performing background processes, it can take up to an hour before the new setting goes into effect.

To view stored Job Server log files, open the Administrator application in the Data Services Management Console.

Task overview: History retention and Job Server log retention [page 82]

関連情報

USPS-required log files and reports [page 84]Setting the History Retention Period [page 85]

86PUBLIC公開

管理者ガイド

サーバの管理

6.5 UNIX および Linux のデータベース接続の設定

SAP Data Services の処理目的で ODBC データベースの種類を追加するたび、SAP Data Services (DS) 接続マネージ

ャでサポートされているドライバを設定し、データベースへの接続を確立します。

必要な情報は似ていますが、UNIX および Linux オペレーティングシステムで ODBC ドライバを設定するためのプロセス

は、Windows オペレーティングシステムとは異なります。たとえば、UNIX および Linux でインストール済みの ODBC ドラ

イバを設定するには、SAP Data Services 接続マネージャを使用します。Windows では、データソース名 (DSN) 接続の

場合は Microsoft ODBC データソースアドミニストレータを、サーバ名 (DSN なし) 接続の場合は ODBC ドライバセレクタ

を使用します。

ドライバを設定するのと同時に DSN 接続を設定します。DSN 接続の場合、データソースに関する情報 (サーバ情報、ユ

ーザ名、パスワードなど) が必要です。該当する場合、データを安全に転送できるように、SSL/TLS を設定します。

UNIX および Linux のデータベース接続 [88 ページ]UNIX または Linux プラットフォームでデータベース接続を設定するには、SAP Data Services (DS) 接続マネー

ジャを使用します。

接続マネージャの使用 [89 ページ]SAP Data Services 接続マネージャは、ODBC ドライバ情報を SAP Data Services のドライバライブラリファイル

に追加するコマンドラインユーティリティです。

サーバ名 (DSN なし) 接続を使用したドライバの設定 [90 ページ]UNIX および Linux プラットフォームの場合、DSN なし接続のドライバを設定する際に SAP Data Services では

ODBC ドライバライブラリに ODBC ドライバ情報が含まれていることが必須となります。

データソース名 (DSN) 接続によるドライバの設定 [95 ページ]Linux および Unix プラットフォームの場合、SAP Data Services では、ODBC ドライバ情報のほか、ODBC ドラ

イバマネージャライブラリと ODBC ドライバライブラリに含めるデータソース名 (DSN) 接続が必要になります。

DataDirect ODBC の設定 [103 ページ]DataDirect ドライバは、SAP Data Services のインストールに含まれており、適用可能なデータベース

(Microsoft SQL Server や zSeries または iSeries 上の DB2 など) とともに使用します。


関連情報

DSN-less and TNS-less connections [77 ページ]Setting UNIX environment variables [79 ページ]Windows および Unix でのサービスの自動起動 [81 ページ]History retention and Job Server log retention [82 ページ]Using the ODBC Drivers Selector for Windows [112 ページ]Using the License Manager [113 ページ]Use the Server Manager on Windows [114 ページ]Using the Server Manager on UNIX systems [123 ページ]

管理者ガイド

サーバの管理

PUBLIC公開 87

Configuring Metadata Browsing Service and View Data Service [133 ページ]Data Services CMC アプリケーション設定 [138 ページ]

SSL or TLS for Data Services components [31 ページ]

6.5.1 UNIX および Linux のデータベース接続

UNIX または Linux プラットフォームでデータベース接続を設定するには、SAP Data Services (DS) 接続マネージャを使

用します。

Data Services 接続マネージャを使用して、ODBC ドライバを設定し、DSN 接続を確立します。DS 接続マネージャによ

り、ドライバ情報は odbcinst.ini ファイルに、DSN 情報は ds_odbc.ini ファイルに追加されます。ds_odbc.iniファイルには、DSN および ODBC ドライバの名前が一覧表示されます。

インストーラによる DSN なし接続の設定

UNIX または Linux に Data Services をインストールする場合、SAP Data Services インストールセットアッププログラム

によってリポジトリが設定されるように選択することができます。インストーラによってリポジトリが設定されるようにするに

は、リポジトリのデータベースの種類を入力します。デフォルトでは、インストーラによって、以下のリポジトリデータベース

に関するタスクが自動で実行されます。

● 指定したデータベースの種類のデータベース接続を確立する

● サーバ名 (DSN なし) 接続を作成する

リポジトリで DSN または TNS (Oracle 用) 接続を使用する場合は、インストール中のリポジトリ作成はスキップします。

インストール後のリポジトリデータベース接続の設定

インストール後、DS 接続マネージャを使用してリポジトリデータベースを設定し、DSN または TNS (Oracle) 接続を確立

します。さらに、DS 接続マネージャを使用して、追加データベースおよび DSN 接続を Data Services に追加します。

接続マネージャで以下のタスクを実行します。

● ドライバマネージャの場所やドライバ名など、ODBC ドライバに関する情報を追加します。

● データソースの名前、サーバ情報、適用可能なユーザ名およびパスワードなど、DSN 接続に関する情報を追加しま

す。

Data Services では、インストールに DS 接続マネージャが含まれており、デフォルトでは次の場所に格納されます。

$LINK_DIR//bin/DSConnectionManager.sh。

リポジトリに使用可能なサポートされているデータベースおよびバージョンの一覧については、SAP Support Portal で製

品出荷マトリクス (PAM)を参照してください。PAM には、Data Services でサポートされている非リポジトリデータベースと

バージョン、および適用可能な ODBC ドライバも記載されています。

親トピック: UNIX および Linux のデータベース接続の設定 [87 ページ]

88PUBLIC公開

管理者ガイド

サーバの管理



関連情報

接続マネージャの使用 [89 ページ]サーバ名 (DSN なし) 接続を使用したドライバの設定 [90 ページ]データソース名 (DSN) 接続によるドライバの設定 [95 ページ]DataDirect ODBC の設定 [103 ページ]

6.5.2 接続マネージャの使用

SAP Data Services 接続マネージャは、ODBC ドライバ情報を SAP Data Services のドライバライブラリファイルに追加

するコマンドラインユーティリティです。

接続マネージャを実行してデータベースの ODBC ドライバを設定する前に、以下のタスクを実行します。

● 製品出荷マトリクス (PAM)を確認して、適用可能なデータベースの種類に対応する ODBC ドライバおよびバージョン

を特定します。

● サポートされている ODBC ドライバをダウンロードおよびインストールし、ベンダのマニュアルの記載されたドライバに

関する情報にすべて目を通してドライバを適切に設定します。

● オプション。接続マネージャのグラフィカルユーザインタフェースを使用する場合は、GTK+2 ライブラリをインストール

します。GTK+2 は、ユーザインタフェースを作成する無料のマルチプラットフォームツールキットです。GTK+2 の入手

とインストールの詳細については、https://www.gtk.org/ を参照してください。

接続マネージャでは、SAP Data Services ドライバマネージャファイル内で、ODBC ドライバおよび DSN 情報が以下のよ

うに設定されます。

● 接続マネージャにより、ドライバ情報 (ベンダのクライアントドライバファイルの名前および場所を含む) がodbcinst.ini ファイルに追加されます。このベンダの場所は読み取りおよび書き込みが可能である必要がありま

す。

例DataDirect ドライバのデフォルトの場所は$LINK_DIR/DataDirect/odbc/です。そのため、接続マネージ

ャから情報を求められた場合は、以下の場所を設定します。

Specify the Driver: /$LINK_DIR/DataDirect/odbc/<name_of_driver_file>

● 接続マネージャにより、DSN 情報が ds_odbc.ini ファイルに追加されます。

次の手順は、接続マネージャのインタフェースが使用できる状態で行ってください。

1. 以下のコマンドで接続マネージャを開きます。$LINK_DIR は、Data Services インストールディレクトリへのパスに置

き換えます。

$ cd $LINK_DIR/bin/DSConnectionManager.sh

接続マネージャが開きます。

2. DSN 接続とサーバ名 (DSN なし) 接続のどちらの場合も、ドライバタブを開いてデータベースの ODBC ドライバを設

定します。

管理者ガイド

サーバの管理

PUBLIC公開 89


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

ドライバタブのオプションは、ドライバの種類に応じて異なる場合があります。

3. DSN 接続の場合は、データソースタブを開いてデータソース名接続を設定します。

データソースタブのオプションは、データベースの種類に応じて異なる場合があります。

4. サービスの再起動をクリックして、EIM Adaptive 処理サービスと Data Services ジョブサービスを再開します。

タスクの概要: UNIX および Linux のデータベース接続の設定 [87 ページ]

関連情報

UNIX および Linux のデータベース接続 [88 ページ]サーバ名 (DSN なし) 接続を使用したドライバの設定 [90 ページ]データソース名 (DSN) 接続によるドライバの設定 [95 ページ]DataDirect ODBC の設定 [103 ページ]

6.5.3 サーバ名 (DSN なし) 接続を使用したドライバの設定

UNIX および Linux プラットフォームの場合、DSN なし接続のドライバを設定する際に SAP Data Services では ODBC ドライバライブラリに ODBC ドライバ情報が含まれていることが必須となります。

UNIX の ODBC ドライバ設定ファイルには、ODBC ドライバライブラリを参照するドライバ名が含まれています。UNIX の

ODBC ドライバ設定は、$ODBCINST 変数で参照されるインスタンスファイルです。

SAP Data Services (DS) 接続マネージャでネイティブにサポートされるデータベースの ODBC ドライバを設定すると、DS 接続マネージャによって$ODBCINST 内の ODBC ドライバライブラリファイルが自動的に更新されます。

UNIX および Linux 用のネイティブ ODBC ドライバの設定 [91 ページ]SAP Data Services (DS) 接続マネージャを使用して、サーバ名 (DSN なし) 接続を使用している UNIX および

Linux 用の ODBC ドライバを設定します。

Properties for server name connections [92 ページ]The SAP Data Services (DS) Connection Manager configures the applicable environment variables for native ODBC drivers based on the property values that you enter.


関連情報

UNIX および Linux のデータベース接続 [88 ページ]接続マネージャの使用 [89 ページ]データソース名 (DSN) 接続によるドライバの設定 [95 ページ]

90PUBLIC公開

管理者ガイド

サーバの管理

DataDirect ODBC の設定 [103 ページ]

Setting UNIX environment variables [79 ページ]

6.5.3.1 UNIX および Linux 用のネイティブ ODBC ドライバの設定

SAP Data Services (DS) 接続マネージャを使用して、サーバ名 (DSN なし) 接続を使用している UNIX および Linux 用の ODBC ドライバを設定します。

ODBC ネイティブドライバを設定する前に、以下の前提条件タスクを実行してください。

● データベースクライアントに対応した ODBC ドライバライブラリおよび関連する環境変数を設定します。手順について

は、Setting UNIX environment variables [79 ページ]を参照してください。

● データベースがサーバ名接続に対応していることを確認してください。データベースおよびサポートされている接続の

最新の一覧については、製品出荷マトリクス (PAM)を参照してください。

● オプション。DS 接続マネージャの GUI で作業するには、GTK+2 ライブラリをインストールします。ダウンロードの手

順については、接続マネージャの使用 [89 ページ]を参照してください。

以下の手順は、DS 接続マネージャの GUI バージョンを対象としています。

1. 次のコマンドを実行して、接続マネージャを開きます。

$ cd $LINK_DIR/bin/DSConnectionManager

2. データソースタブを開いて、追加をクリックします。

3. データベースの種類の選択ダイアログボックスから目的のデータベースの種類を選択し、OK をクリックします。

ODBC Inst ファイルオプションに値が入力された状態で、... の設定ダイアログボックスが開きます。

4. ドライバとデータベースサーバに関する情報を入力します。

以下のサーバプロパティの値を指定します。

○ サーバ名

○ ポート (該当する場合)○ データベース (該当する場合)○ ユーザ名

○ パスワード

注記

接続マネージャでは、入力した値が今後の使用ために保存されることはありません。

5. 接続テストをクリックして接続をテストします。

6. 接続テストが成功したら、サービスの再起動をクリックします。

以下の状況では、EIM Adaptive 処理サービスおよび Data Services ジョブサービスは自動で再起動されます。

○ 情報プラットフォームサービス(IPS) または BI プラットフォームと同じマシンの同じフォルダに Data Services を

インストールしている場合は、EIM Adaptive 処理サービスと Data Services ジョブサービスの両方が自動で再

起動されます。

注記

プロンプトが表示されたら、Central Management Server (CMS)のパスワードを入力してください。

管理者ガイド

サーバの管理

PUBLIC公開 91


○ IPS または BI プラットフォーム以外のコンピュータに Data Services をインストールしている場合は、Data Services ジョブサービスが自動で再起動されます。

タスクの概要: サーバ名 (DSN なし) 接続を使用したドライバの設定 [90 ページ]

関連情報

Properties for server name connections [92 ページ]

6.5.3.2 Properties for server name connections

The SAP Data Services (DS) Connection Manager configures the applicable environment variables for native ODBC drivers based on the property values that you enter.

Environment variables for ODBC data sources include $ODBCINST or $ODBCSYSINI.

The following table contains a list of native database types and the information required in the DS Connection Manager to configure the ODBC driver.

注記

We add support for additional database types on a regular basis. Therefore, the following table may not be up-to-date.

Database Type Properties on Drivers tab

DB2 UDB ● DB2 Client Path● Driver Version● Server Name● Port● Database● User Name● Password

92PUBLIC公開

管理者ガイド

サーバの管理


Google BigQuery ODBC ● Driver Name (Must use Simba ODBC driver for Google BigQuery)

● Driver location● UNIX ODBC Lib Path● Google BigQuery Oauth Mechanism and options based

on the type chosen:○ BigQuery Refresh Token○ BigQuery e-mail○ BigQuery Private Key

● Google BigQuery catalog● Optional. Proxy server information:

○ Host○ Port○ Username○ Password

● Google BigQuery Trusted Certificates

Informix ● ODBC Inst File● Driver Version● Driver Name● Informix Home Path● Server Name● Database● User Name● Password

MySQL ● ODBC Inst File● Driver Version● Unix ODBC Lib Path● Driver Name● Driver● Server Name● Port● Database● User Name● Password

Netezza ● ODBC Inst File● Driver Version● Driver Name● Driver● Server Name● Port● Database● User Name● Password

管理者ガイド

サーバの管理

PUBLIC公開 93


Oracle ● Oracle Home Path● Driver Version● Server Name● Port● SID● User Name● Password

SAP HANA ● ODBC Inst File● Driver Version● Driver Name● Driver● Server Name● Port● User Name● Password

SAP Sybase IQ ● ODBC Inst File● Driver Version● Driver Name● Driver● Server Name (This is also known as the host name. For

example, a host name may be vanpgc13b9.)● Port● Engine Name (This is also known as the server name.

For example, a server name may be vanpgc13b9_iqdemo.)

● Database● User Name● Password

SQL Anywhere ● Driver Version● Driver Name● User Name● Password (no echo)● Retype Password (no echo)● Driver (path and file name)● Host● Port● Database

Teradata ● ODBC Inst File● Driver Version● Driver Name● Driver● Server Name● User Name● Password

94PUBLIC公開

管理者ガイド

サーバの管理

Parent topic: サーバ名 (DSN なし) 接続を使用したドライバの設定 [page 90]

関連情報

UNIX および Linux 用のネイティブ ODBC ドライバの設定 [page 91]

6.5.4 データソース名 (DSN) 接続によるドライバの設定

Linux および Unix プラットフォームの場合、SAP Data Services では、ODBC ドライバ情報のほか、ODBC ドライバマネ

ージャライブラリと ODBC ドライバライブラリに含めるデータソース名 (DSN) 接続が必要になります。

ODBC ドライバマネージャと ODBC ドライバの機能を 1 つのライブラリで提供している ODBC ドライバベンダもいれば、2 つのライブラリに分けて提供しているベンダもいます。すべての ODBC ベンダに対応する場合、Data Services では、次

の 2 つの DSN 接続用ライブラリで設定が必要です。

● UNIX ODBC ドライバ設定ファイル ($ODBCINST 環境変数で参照): ODBC ドライバマネージャライブラリを参照する

DSN インスタンスが含まれます。デフォルトの場所は$LINK_DIR/bin/ds_odbc.ini です。

ヒント

Data Services でネイティブにサポートされている ODBC データベースの場合は、ds_odbc.ini ファイルを手

動で設定しないでください。代わりに、SAP Data Services (DS) 接続マネージャを使用してドライバを設定し、情

報を UNIX ODBC ドライバマネージャライブラリに自動的に追加します。

● ベンダの ODBC 設定ファイル ($ODBCINI 環境変数で参照): ODBC ドライバライブラリとデータベースサーバ接続

情報を参照するデータソース名 (DSN) インスタンスが含まれます。

注記

1 つの ODBC 設定ファイルに複数の DSN インスタンスを含めることができます。たとえば、$ODBCINI で参照さ

れるファイルに、MySQL、Netezza、Teradata 用の DSN が含まれることがあります。

ネイティブ ODBC データソース [96 ページ]SAP Data Services は、複数の ODBC データソースを DSN 接続でネイティブにサポートします。

Configuring ODBC data sources [96 ページ]To configure ODBC data sources in Linux or UNIX, use the SAP Data Services Connection Manager.

Properties for ODBC data sources using DSN connections [98 ページ]The Connection Manager configures the $ODBCINI file based on the property values that you enter on the Data Sources tab.

Troubleshooting [102 ページ]Configuring drivers can be troublesome for a variety of reasons.


管理者ガイド

サーバの管理

PUBLIC公開 95

関連情報

UNIX および Linux のデータベース接続 [88 ページ]接続マネージャの使用 [89 ページ]サーバ名 (DSN なし) 接続を使用したドライバの設定 [90 ページ]DataDirect ODBC の設定 [103 ページ]

6.5.4.1 ネイティブ ODBC データソース

SAP Data Services は、複数の ODBC データソースを DSN 接続でネイティブにサポートします。

ネイティブ ODBC データソースのドライバとデータソースは、SAP Data Services 接続マネージャを使用して設定します。

Data Services の ODBC 設定および関連する環境変数を設定します。非ネイティブ ODBC データソースには、追加の手

動設定が必要です。

注記

接続マネージャでサポートされるデータベースの種類の最新の一覧については、SAP Support Portal で製品出荷マ

トリクス (PAM)を参照してください。

接続マネージャで値を入力して、$ODBCINI を DSN 接続が含まれるファイルに設定します。接続マネージャを実行する

前に、次のコマンドを実行して、このファイルが読み取りおよび書き込み可能であることを確認してください。

export ODBCINI=<dir-path>/ds_odbc.ini touch $ODBCINI

親トピック: データソース名 (DSN) 接続によるドライバの設定 [95 ページ]

関連情報

Configuring ODBC data sources [96 ページ]Properties for ODBC data sources using DSN connections [98 ページ]Troubleshooting [102 ページ]

6.5.4.2 Configuring ODBC data sources

To configure ODBC data sources in Linux or UNIX, use the SAP Data Services Connection Manager.

Data Services supports several ODBC data sources natively with DSN connections. Ensure that Data Services supports your ODBC data source.

Ensure that you have the correct privileges to change the configuration files mentioned in these steps.

96PUBLIC公開

管理者ガイド

サーバの管理



Install the GTK+2 library to make a graphical user interface for Connection Manager. The GTK+2 is a free multi-platform toolkit that creates user interfaces. The installation is at https://www.gtk.org/ .

1. To open the DSConnectionManager, enter the following command:

$ cd $LINK_DIR/bin/ $ ./DSConnectionManager.sh

The DSConnectionManager GUI opens.2. Click the Data Sources tab, and click Add to display the list of database types.3. Select the database type in the Select Database Type dialog box, and click OK.

The Configuration for... dialog box opens. The Connection Manager automatically completes the following information:○ The absolute location of the odbc.ini file in which the DSN is defined○ Driver, if relevant for database type○ Driver Version, if relevant for database type

4. Provide values for additional connection properties, such as Server Name, Instance, or Port, for the specific database type.For a list of relevant properties for each database type, see Properties for ODBC data sources using DSN connections [page 98].

5. Provide the following properties:○ User name○ Password

注記

The Connection Manager does not save this information for further use.

6. To test the connection, click Test Connection.7. When the connection test is successful, click Restart Services to restart the following services:

○ EIM Adaptive Process Service and Data Services Job Service: When Data Services is installed at the same location (machine and folder) as Information Platform Services (IPS) or BI platform. A prompt appears for the Central Management Server (CMS) password.

○ Data Services Job Service: When Data Services is installed without IPS or BI platform.

Task overview: データソース名 (DSN) 接続によるドライバの設定 [page 95]

関連情報

ネイティブ ODBC データソース [page 96]Properties for ODBC data sources using DSN connections [page 98]Troubleshooting [page 102]

管理者ガイド

サーバの管理

PUBLIC公開 97


6.5.4.3 Properties for ODBC data sources using DSN connections

The Connection Manager configures the $ODBCINI file based on the property values that you enter on the Data Sources tab.

The following table lists the properties that are relevant for each database type.

注記

We add support for additional database types on a regular basis. Therefore, the following table may not be up-to-date.

Database Type Properties on Data Sources tab

Amazon Redshift ● DSN Name● User Name● Database password● Unix ODBC Lib Path● Driver● Driver Version● Host Name● Port● Database● Redshift SSL Certificate Mode [require|allow|disable|

prefer|verify-ca|verify-full]

Apache Cassandra ● User Name● Database password● Host Name● Port● Database● Unix ODBC Lib Path● Driver● Cassandra SSL Certificate Mode[0:disabled|1:one-way|

2:two-way]

Depending on the value you choose for the Certificate Mode, you may be asked to define some or all of the following

● Cassandra SSL Server Certificate File● Cassandra SSL Client Certificate File● Cassandra SSL Client Key File● Cassandra SSL Client Key Password● Cassandra SSL Validate Server Hostname?[0:disabled|

1:enabled]

98PUBLIC公開

管理者ガイド

サーバの管理


Apache Impala ● ODBC Ini File● DSN Name● User Name● Database password● Host Name● Port● Database● Unix ODBC Lib Path● Driver● Impala Auth Mech[0:noauth|1:kerberos|2:user|3:user-

password]● Kerberos Host FQDN● Kerberos Realm● Impala SSL Mode[0:disabled|1:enabled]● Impala SSL Server Certificate File

Attunity ● Attunity Driver Path

DB2 on iSeries or zSeries ● ODBC ini File● DSN Name● Server Name● Port● Location● Collection● Package Collection● User Name● Password

Google BigQuery ODBC ● ODBC ini file● DSN Name● Unix ODBC Lib Path● Specify the Driver (Must use Simba ODBC driver for

Google BigQuery)● Google BigQuery Oauth Mechanism and options based

on the type chosen:○ BigQuery Refresh Token○ BigQuery e-mail○ BigQuery Private Key

● Google BigQuery catalog● Optional. Proxy server information:

○ Host○ Port○ Username○ Password

● Google BigQuery Trusted Certificates

管理者ガイド

サーバの管理

PUBLIC公開 99


Hive Server ● Driver● Host Name● Port● Schema● Service Discovery Mode● Hive Server Type● Auth Mech● Thrift Target● UID● PWD● Kerberos Host FQDN● Kerberos Realm● SSL

Informix ● ODBC Ini File● DSN Name● Driver● Server Name● Database● User Name● Password

MySQL ● ODBC Ini File● DSN Name● Unix ODBC Lib Path● Driver● Driver Version● Server Name● Port● Database● User Name● Password

Netezza ● ODBC Ini File● DSN Name● Driver● Driver Version● Server Name● Port● Database● User Name● Password

PostgreSQL ● Database name● Server● Port● User name● Password

100PUBLIC公開

管理者ガイド

サーバの管理


SAP HANA ● ODBC Ini File● DSN Name● Driver● Server Name● Instance● User Name● Password

SAP Vora ● ODBC Ini File● DSN Name● User Name● Password● Driver● Host Name● Port

Snowflake ● User● Password● Server● Database● Schema● Warehouse● Role● Tracing(0-6)● Authenticator● Proxy● NoProxy

For information about these connection options, see the Snowflake User Guide.

SQL Server ● ODBC Ini File● DSN Name● Server Name● Port● Database● User Name● Password

Sybase ASE ● Sybase Home Path● OCS● Server Name● Database● User Name● Password

管理者ガイド

サーバの管理

PUBLIC公開 101


Sybase IQ ● ODBC Ini File● DSN Name● Driver● Server Name (This is also known as the host name. For

example, a host name may be vanpgc13b9.)● Port● Engine Name (This is also known as the server name.

For example, a server name may be vanpgc13b9_iqdemo.)

● Database● User Name● Password

Teradata ● ODBC Ini File● DSN Name● Teradata Install Path● Teradata Version● Server Name● User Name● Password

Parent topic: データソース名 (DSN) 接続によるドライバの設定 [page 95]

関連情報

ネイティブ ODBC データソース [page 96]Configuring ODBC data sources [page 96]Troubleshooting [page 102]

6.5.4.4 Troubleshooting

Configuring drivers can be troublesome for a variety of reasons.

The following are some of the more common issues to troubleshoot when you configure drivers with DSN connections:

Trouble with libraries

To determine whether all dependent libraries are set properly in the environment variables, use the ldd command on the ODBC driver manager library and the ODBC driver library.

102PUBLIC公開

管理者ガイド

サーバの管理

例

ldd tdata.so

If you see that any dependent libraries are missing, ensure that you've added the environment settings to the session running the job service, or consult your ODBC driver vendor's documentation.

Trouble with Connection Manager

If an error occurs when using the Connection Manager, invoke it from the command line by using the -c option, and use the -d option to show details in the log.

例

$LINK_DIR/bin/DSConnectionManager.sh -c -d

The log file path is $LINK_DIR/log/DSConnectionManager.log.

Possible errors include the following:

● The Connection Manager can't connect to database.● The Data Services Job Server can't connect to database.

Parent topic: データソース名 (DSN) 接続によるドライバの設定 [page 95]

関連情報

ネイティブ ODBC データソース [page 96]Configuring ODBC data sources [page 96]Properties for ODBC data sources using DSN connections [page 98]

6.5.5 DataDirect ODBC の設定

DataDirect ドライバは、SAP Data Services のインストールに含まれており、適用可能なデータベース (Microsoft SQL Server や zSeries または iSeries 上の DB2 など) とともに使用します。

データベース用の ODBC DataDirect ドライバを手動で設定する前に、以下を確認してください。

● odbc.ini および odbcinst.ini ファイルを編集するための適切な権限が付与されていることを確認します。

● SAP カスタマポータルで最新の製品出荷マトリクス (PAM)を確認して、適用可能な DataDirect バージョンおよびデ

ータベースバージョンを判断してください。

● ドライバとデータソース情報を$ODBCINI および$ODBCINST の.ini ファイルに自動的に追加する場合は、SAP Data Services (DS) 接続マネージャの使用を検討してください。

管理者ガイド

サーバの管理

PUBLIC公開 103


Linux または UNIX プラットフォーム上で適用可能なデータベースの種類に手動で DataDirect ODBC ドライバを設定す

るには、以下の手順を実行します。

1. テキストエディタで ds_odbc.ini ファイルを開きます。

このファイルは$LINK_DIR/bin/ds_odbc.ini にあります。

2. データソース名を角括弧で囲んで追加します。

Microsoft SQL Server の場合:

[test_Microsoft_SQL_SERVER]

zSeries または iSeries 上の DB2 の場合:

[test_DB2] 3. ドライバキーのインストール先を追加します。


[test_Microsoft_SQL_SERVER] Driver = <install_location>/lib/[DA][DD]sqls<xx>.so

<install_location>は DataDirect ODBC ドライバの場所です。


[test_DB2] Driver = <install_location>/lib/[DA][DD]db2<xx>.so


注記

4. RebrandedLib =の値を追加します。

ブランド変更後のライブラリの値は、SAP のブランド変更後の DataDirect ドライバを使用する場合に必要になりま

す。


[test_Microsoft_SQL_SERVER] Driver = <install_location>/lib/[DA][DD]sqls<xx>.so RebrandedLib = TRUE


[test_DB2] Driver = <install_location>/lib/[DA][DD]db2<xx>.so RebrandedLib = TRUE

5. UNIX 変数$ODBCINI によって参照される ODBC ベンダの設定ファイルにデータソースを追加します。

注記

バージョン番号とドライバのファイル名は、リリースごとに変更される場合があります。現在のバージョン情報を確

認するには、$LINK_DIR/DataDirect/odbc/odbc.ini にアクセスします。

104PUBLIC公開

管理者ガイド

サーバの管理

注記

Microsoft SQL Server の場合は、EnableQuotedIdentifiers = 1 が必要です。

Microsoft SQL Server の場合は、プロンプトの説明が太字で表示されます。

[test_Microsoft_SQL_SERVER] Driver=<install_location>/lib/[DA][DD]msss<xx>.so Description=DataDirect <current version number> SQL Server Wire Protocol AlternateServers= AnsiNPW=Yes ConnectionRetryCount=0 ConnectionRetryDelay=3 Database=<database_name> EnableQuotedIdentifiers=1 HostName=<SQL_Server_host> LoadBalancing=0 LogonID= Password= PortNumber=<SQL_Server_server_port> QuotedId=No ReportCodePageConversionErrors=0 DriverExpirationBehavior=1



[test_DB2] Driver=<install_location>/lib/[DD][DA]db2<xx>.so Description=DataDirect <current version number> DB2 Wire Protocol AddStringToCreateTable=AlternateID=AlternateServers= ApplicationUsingThreads=1 AuthenticationMethod=0 CatalogSchema= CharsetFor65535=0 #Collection applies to z/OS and iSeries only Collection=<collection_name> ConnectionRetryCount=0 ConnectionRetryDelay=3 #Database applies to DB2 UDB only Database=<database_name> DefaultIsolationLevel=1 DynamicSections=200 EncryptionMethod=0 GrantAuthid=PUBLIC GrantExecute=1 GSSClient=native HostNameInCertificate= IpAddress=<DB2_server_host> LoadBalancing=0 #Location applies to z/OS and iSeries only Location=<location_name> LogonID=Password= PackageCollection=<package_collection> PackageOwner= ReportCodePageConversionErrors=0 TcpPort=<port number> TrustStore=TrustStorePassword= UseCurrentSchema=1 ValidateServerCertificate=1

管理者ガイド

サーバの管理

PUBLIC公開 105

WithHold=1 XMLDescribeType=-10


6. $LINK_DIR/DataDirect/odbc/odbc.sh スクリプトを実行して、ジョブサービスを実行しているセッションに環

境設定を追加します。

DSN 接続のドライバマネージャ設定ファイルの例 [106 ページ]使用する各 ODBC ドライバには、ドライバライブラリファイルの情報が含まれ、権限のあるユーザのみが編集可

能です。

タスクの概要: UNIX および Linux のデータベース接続の設定 [87 ページ]

関連情報

UNIX および Linux のデータベース接続 [88 ページ]接続マネージャの使用 [89 ページ]サーバ名 (DSN なし) 接続を使用したドライバの設定 [90 ページ]データソース名 (DSN) 接続によるドライバの設定 [95 ページ]

6.5.5.1 DSN 接続のドライバマネージャ設定ファイルの例

使用する各 ODBC ドライバには、ドライバライブラリファイルの情報が含まれ、権限のあるユーザのみが編集可能です。

データソース名を追加する場合は、名前を角括弧 ([]) で囲みます。次の形式を使用して、後続の行にデータソースのプロ

パティを入力します。PropertyName = PropertyValue。

例

[test_source] Driver = /path/to/driverOdbcConformanceLevel = LazyLoading = ODBC64SqlHandleSize = ODBC64SqlLenSize = DriverUnicodeType =

この例のデータソースは、[test_source] です。指定したドライバライブラリファイルを使用してロードすることができま

す。SAP Data Services では、オプションのプロパティを空白のままにした場合、デフォルト値が使用されます。

<LINK_DIR>/bin/ds_odbc.ini ファイルという名前の Data Services ODBC ファイルを編集する場合は、以下のガ

イドラインに従ってください。

● データソース名ごとに少なくとも 1 つのドライバプロパティを定義します。ドライバプロパティによって、ドライバがデータ

ベースに接続されている場合にドライバマネージャがドライバをロードできるようになります。

● いかなるコメント行でも、コメントであることを示すため、先頭文字をポンド記号 (#) にします。

106PUBLIC公開

管理者ガイド

サーバの管理

● Data Services では、データソース名およびプロパティの先頭と末尾の空白文字がすべて無視されます。

以下の表に、ds_odbc.ini 内のデータソース設定パラメータ (キー)、必須であるかどうか、有効な値の説明、および例

を示します。

データソース設定ファイルのキーの説明

キー必須有効な値例

Driver はい ODBC ドライバライブラリの完

全パスおよびライブラリ名。依存

ライブラリを含むディレクトリは、

共有ライブラリパス内にある必

要があります。以下はその例で

す。

● AIX の場合、LIBPATH● Solaris または Linux の場

合、

LD_LIBRARY_PATH

適用可能な共有ライブラリパス

については、該当するベンダの

マニュアルを確認してください。

Driver=/home/mysql/myodbc/lib/libmyodbc3_r.so

管理者ガイド

サーバの管理

PUBLIC公開 107


OdbcConformanceLevel

いいえドライバの ODBC 適合レベルを

指定する小数値。

デフォルト値は 0 です。0 に設

定すると、ドライバが適合レベル

2.x の API 機能、適合レベル

3.x の API 機能の順にロードを

実行して、適合レベルを検出し

ます。

4.0 以上の値が存在する場合、

ドライバマネージャにより実行時

エラーが出力されます。

注記

ODBC ドライバは 2.x と

3.x のいずれか、またはそ

の両方に準拠できます。

UNIX ODBC ドライバマネ

ージャはドライバが 2.x 準拠か 3.x 準拠かを検出し、

それぞれに対応する

ODBC API 機能をロードし

ます。ドライバが 2.x と 3.x 両方に準拠している場合

は、2.x ODBC API のみを

ロードします。この動作は、

たとえば

OdbcConformanceLevel = 3.0 のように

指定することで上書きする

ことができます。この結果、

ODBC ドライバマネージャ

は 3.x ODBC API 機能の

みをロードします。

OdbcConformanceLevel=0

OdbcConformanceLevel=3.0

108PUBLIC公開

管理者ガイド

サーバの管理


LazyLoading いいえ ODBC ドライバマネージャが

ODBC ドライバをロードし、ドラ

イバの依存ライブラリをすべて

ロードするようオペレーティング

システムに指示するかどうかを

指定します。

はいの場合は TRUE を、いいえ

の場合は FALSE を指定しま

す。デフォルト値は FALSE です。

LazyLoading フラグは、ODBC ドライバの一部の特定の依存ラ

イブラリが不要であり、かつ

ODBC ベンダが遅延モードでの

ライブラリのロードを推奨してい

る場合に役立ちます。

LazyLoading=TRUE

管理者ガイド

サーバの管理

PUBLIC公開 109


ODBC64SqlHandleSize はい、64 ビットのプラットフォー

ムの場合に限り必須です。ODBC ハンドルのサイズを指定

します。

32 または 64 を入力します。

このオプションを空白のままに

するか、32 または 64 以外の値

に設定すると、Data Services ではデフォルト値の 64 が使用

されます。

64 ビット ODBC の

SQLHANDLE データ型の標準

定義は、64 ビット Integer です。ただし、一部の ODBC ドラ

イバはこの標準に準拠していま

せん。そのため、

ODBC64S1lHandleSize キーを使用して、SQLHANDLE の実際のサイズを指定してくだ

さい。

DataDirect 64 ビット ODBC ドライバの場合は、Data Direct 64 ビットが標準に準拠している

ため、キーを無視するか、64 に設定します。その他の 64 ビット

ODBC ドライバの場合は、ベン

ダに問い合わせて

SQLHANDLE の実際のサイズ

を決定してください。

注記

このオプションは 64 ビット

プラットフォームの場合の

み必須です。

ODBC64SqlHandleSize=64

110PUBLIC公開

管理者ガイド

サーバの管理


ODBC64SqlLenSize はい、64 ビットのプラットフォー

ムの場合に限り必須ですODBC ドライバの SQL 長のサ

イズを指定します。

32 または 64 を入力します。

このキーを空白のままにする

か、32 または 64 以外の値を入

力すると、Data Services では

デフォルト値の 64 が使用され

ます。

64 ビット ODBC の SQLLEN データ型の標準定義は、64 ビット

Integer です。ただし、一部の

ODBC ドライバはこの標準に準

拠していません。そのため、

ODBC64SqlLenSize キー

を使用して、SQLLEN の実際の

サイズを指定してください。

DataDirect 64 ビット ODBC ドライバは標準に準拠しているた

め、DataDirect の場合は設定

を無視するか、キーを 64 に設

定します。その他の 64 ビット

ODBC ドライバの場合は、ベン

ダに問い合わせて SQLLEN の実際のサイズを決定してくださ

い。

注記

このオプションは 64 ビット

プラットフォームの場合の

み必須です。

ODBC64SqlLenSize=64

管理者ガイド

サーバの管理

PUBLIC公開 111


DriverUnicodeType はい、W 機能のみをサポートす

る ODBC ドライバに限り必須で

す。

ODBC ドライバの Unicode タイ

プを指定します。

以下の整数のいずれかを入力

します。

● 1: UTF16 の場合

● 2: UTF8 の場合

このキーを空白のままにする

か、1 または 2 以外の値を設定

するか、検出不可の場合、Data Services ではデフォルト値の 2 が使用されます。

DataDirect SQL Server ODBC ドライバは W 機能のみをサポ

ートします。そのため、このドラ

イバの場合は 2 を指定します。

注記

このオプションは W 機能の

みをサポートする ODBC ドライバの場合に限り必須で

す。

DriverUnicodeType=2

親トピック: DataDirect ODBC の設定 [103 ページ]

6.6 Using the ODBC Drivers Selector for Windows

To configure an ODBC driver on the Windows platform, use the SAP Data Services ODBC Drivers Selector utility.

Before you perform the following steps, download and install the applicable ODBC driver.

1. Open the ODBC Driver Selector: <LINK_DIR>¥bin¥ODBCDriversSelector.exe.

The Drivers Selector dialog box contains three columns:○ Database versions: Contains a row for each database type and version supported in Data Services. Not

editable.○ ODBC Driver: Contains the ODBC driver name or is blank. Has a dropdown arrow that displays all

available ODBC drivers.○ State: Contains “installed”, “not installed”, or blank.

2. Find your database type and version under the Database version column.

112PUBLIC公開

管理者ガイド

サーバの管理

3. Click the corresponding cell under the ODBC Drivers column and select the correct driver from the dropdown list.

4. If the status doesn't appear in the State column, click in the empty column and the applicable state appears. The state should be “Installed”.

注記

The list of drivers in the ODBC Driver Selector is the same as the list of drivers in the ODBC Data Source Administsrator for data sources using DSN connections.

5. Click OK.

Open the DSConf.txt file and verify that the data source and driver are present in the [DBClientDrivers] section. The format is <DATASOURCE_VERSION>=<ODBC_DRIVER>.

Task overview: サーバの管理 [page 76]

関連情報

DSN-less and TNS-less connections [page 77]Setting UNIX environment variables [page 79]Windows および Unix でのサービスの自動起動 [page 81]History retention and Job Server log retention [page 82]UNIX および Linux のデータベース接続の設定 [page 87]Using the License Manager [page 113]Use the Server Manager on Windows [page 114]Using the Server Manager on UNIX systems [page 123]Configuring Metadata Browsing Service and View Data Service [page 133]Data Services CMC アプリケーション設定 [page 138]

6.7 Using the License Manager

The License Manager allows you to add and delete licenses that you receive from SAP, such as when you buy the software or when your current license expires.

The License Manager is a command-based utility. For a list of commands and location of the License Manager, see ライセンスマネージャ [page 205].


管理者ガイド

サーバの管理

PUBLIC公開 113

関連情報

DSN-less and TNS-less connections [page 77]Setting UNIX environment variables [page 79]Windows および Unix でのサービスの自動起動 [page 81]History retention and Job Server log retention [page 82]UNIX および Linux のデータベース接続の設定 [page 87]Using the ODBC Drivers Selector for Windows [page 112]Use the Server Manager on Windows [page 114]Using the Server Manager on UNIX systems [page 123]Configuring Metadata Browsing Service and View Data Service [page 133]Data Services CMC アプリケーション設定 [page 138]

6.8 Use the Server Manager on Windows

Use the Data Services Server Manager for many tasks, such as to create, edit, or delete Job Servers and Access Servers after installation.

The Server Manager user interface consists of several tabs in which to view, add, and edit your environment related to SAP Data Services. The following table describes the tabs in the Server Manager.

Tab Description

Job Server Associate an existing repository to a Job Server. Also add, edit, or delete Job Servers.

Access Server Add, edit, or delete access servers.

SSL Configure SSL paths.

Run-Time Configure runtime resources.

NCS Enable the NCS (Native Component Supportability) library and set the tracing level threshold, execution interval, and execution time offset.

SLD Enable SLD (System Landscape Directory) support by registering the SAPHOSTAGENT, installing the SMD (Solution Manager Diagnostics) agent, and configuring the CA Introscope Enterprise Manager.

Miscellaneous Specify the SMTP server settings and Windows cluster settings.

Configuring Job Servers [page 115]Use the Data Services Server Manager to create and edit all types of Job Servers.

Configuring runtime resources [page 119]Configure runtime resources to control Job Server operations, such as pageable cache or parallel processes.

Access Server の設定 [page 121]

114PUBLIC公開

管理者ガイド

サーバの管理


Job Server と Access Server の実行の確認 [page 123]


関連情報

DSN-less and TNS-less connections [page 77]Setting UNIX environment variables [page 79]Windows および Unix でのサービスの自動起動 [page 81]History retention and Job Server log retention [page 82]UNIX および Linux のデータベース接続の設定 [page 87]Using the ODBC Drivers Selector for Windows [page 112]Using the License Manager [page 113]Using the Server Manager on UNIX systems [page 123]Configuring Metadata Browsing Service and View Data Service [page 133]Data Services CMC アプリケーション設定 [page 138]

6.8.1 Configuring Job Servers

Use the Data Services Server Manager to create and edit all types of Job Servers.

To use the Server Manager for Job Servers, perform the following steps:

1. Open the Windows Start menu, expand SAP Data Services <version>.

2. Right-click Data Services Server Manager and select More Run as administrator.

The Data Services Server Manager opens.3. In the Job Server tab, select Configuration Editor.

From the Job Server Configuration Editor you can perform the following tasks:○ Add a new job server and associate it with an existing repository.○ Edit an existing Job Server.○ Delete an existing Job Server.○ Resync an existing Job Server with the associated repository.

4. Decide which configuration task to perform:

○ To add a new Job Server, click Add.Continue to the remaining configuration steps.

○ To edit an existing Job Server, select the Job Server and click Edit.Continue to the remaining configuration steps.

○ To remove an existing Job Server, select the Job Server and click Delete.No additional configuration steps are required.

管理者ガイド

サーバの管理

PUBLIC公開 115

注記

If the Job Server has associated repositories, you must first delete those and then click OK before you can delete the Job Server.

5. In the Job Server Properties window, enter configuration information for the Job Server.6. In the Associated Repositories section, configure any local or profiler repositories that you want to

associate with the Job Server. Each Job Server must be associated with at least one local repository.a. If you want to use a server name connection (for DB2, MySQL, SQL Anywhere, or SAP HANA database

types), clear the Use data source name (DSN) checkbox.b. If you want to use a server name connection for an Oracle database type, clear the Use TNS name

checkbox.c. When you have finished configuring associated repositories, including one default, click OK.

7. Click OK to return to the Server Manager window.8. Click Restart to restart the services with any updated configurations.

Job Server properties [page 116]When you open a Job Server, the Server Manager displays information about the Job Server.

Associating a Job Server to a repository [page 117]A repository must have a Job Server for moving data into and out of SAP Data Services.

Resynchronizing associated repositories [page 119]There are times when you must resynchronize a Job Server with the local repository, such as after a reinstallation.

Task overview: Use the Server Manager on Windows [page 114]

関連情報

Configuring runtime resources [page 119]Access Server の設定 [page 121]SSL パスの設定 [page 122]Job Server と Access Server の実行の確認 [page 123]

6.8.1.1 Job Server properties

When you open a Job Server, the Server Manager displays information about the Job Server.

The following table describes the Job Server Properties listed in the Server Manager.

Property Description

Job Server name Specifies a name that uniquely identifies the Job Server.

116PUBLIC公開

管理者ガイド

サーバの管理

Property Description

Job Server port Specifies the TCP/IP port that the Job Server uses to receive commands from the Designer and the Access Server. If a computer hosts multiple Job Servers, each Job Server must have a unique port number. Additionally, the post number must not be used by another process on the computer.

If you are unsure of which port number to use, use the default port number and increment it for each additional Job Server that you configure.

Support adapter and message broker communication Enables communication between the Job Server and adapters. Each computer that hosts adapters must have exactly one Job Server designated to manage them.

Use SSL protocol for adapter, message broke and communication

Enables SSL security on the communication paths between the Job Server and any adapters or message brokers.

Communication port Specifies the TCP/IP port number that the Job Server uses for communicating with adapters. The default port is 4001.

Parent topic: Configuring Job Servers [page 115]

関連情報

Associating a Job Server to a repository [page 117]Resynchronizing associated repositories [page 119]

6.8.1.2 Associating a Job Server to a repository

A repository must have a Job Server for moving data into and out of SAP Data Services.

For more information about Job Servers, and other standard components, see Architecture overview [page 11].

In addition to a repository association, each Job Server can be associated with other local and profiler repositories.

To associate a repository to a Job Server, perform the following steps:

1. Open the Data Services Server Manager from the Windows Start menu selecting to run as an administrator.

2. Select Configuration Editor.

The Job Server Configuration Editor opens.3. Select Add.

The Job Server Properties opens.4. Select Add.

管理者ガイド

サーバの管理

PUBLIC公開 117

The Repository Information pane at right becomes enabled.5. Enter the required connection information for your repository database. The details required vary

depending on the database and connection type.6. Enter the user name and password for the repository database.7. Check Default repository if this repository is the default repository for the Job Server.

You can specify only 1 default repository per Job Server.

注記

Don't check Default repository if you're adding a profiler repository.

8. Select Apply to save your entries and associate the repository with the Job Server.

The associated repository entry updates with the Job Server's computer name and port number.9. To change the default repository setting, perform the following substeps beginning in the Job Server

Configuration Editor dialog box:a. Select the Job Server with which the repository is associated and select Edit.b. Select the repository under Associated Repositories and select Edit.c. Under Repository Information, enter the password.d. Check or uncheck Default repository, indicating whether this repository is the default repository for the

Job Server.e. Select Apply.

制限

You can change only whether an associated repository is the default for the Job Server. To change other configurations, delete the existing associated repository and add a new one with the updated configuration information.

10. To delete an associated repository, perform the following substeps:a. Select the Job Server with which the repository is associated and select Edit.b. Select the repository under Associated Repositories and select Delete.c. Under Repository Information, enter the password.d. Select Apply to remove the associated repository from the Job Server configuration.

Task overview: Configuring Job Servers [page 115]

関連情報

Job Server properties [page 116]Resynchronizing associated repositories [page 119]

118PUBLIC公開

管理者ガイド

サーバの管理

6.8.1.3 Resynchronizing associated repositories

There are times when you must resynchronize a Job Server with the local repository, such as after a reinstallation.

The following lists situations when you must resynchronize the Job Server and the local repository:

● The Job Server information isn't available or not correct in the local repository.● You've uninstalled SAP Data Services and reinstalled the same version, without creating a new local

repository.● You create a new local repository using the Repository Manager after creating a repository and Job Server

when you installed Data Services.

To resynchronize Job Servers, perform the following steps:

1. Open the Data Services Server Manager from the Windows Start menu, and select to run as an administrator.

2. Select Configuration Editor.

The Job Server Configuration Editor opens.3. Select the name of your Job Server.4. Select Resync with Repository.5. In the Job Server Properties window, select an associated local repository.6. Select Resync.7. Select OK when asked whether to update this associated repository with this local machine information.8. Enter the local repository password under Repository Information.9. Select Apply.10. Select OK on the Job Server Properties window.

Task overview: Configuring Job Servers [page 115]

関連情報

Job Server properties [page 116]Associating a Job Server to a repository [page 117]

6.8.2 Configuring runtime resources

Configure runtime resources to control Job Server operations, such as pageable cache or parallel processes.

1. In the Server Manager window, click the Run-time resources tab.2. For the Specify a directory with enough disk space for pageable cache option, accept the default directory

(<DS_COMMON_DIR>¥Log¥PCache) or click the ellipses button to browse to a different directory.

管理者ガイド

サーバの管理

PUBLIC公開 119

注記

For memory-intensive operations such as Group By, Order By, and Detailed profiling, specify a pageable cache directory that fulfills the following criteria:

○ The directory contains enough disk space for your data. To estimate the amount of space required for pageable cache, consider factors such as:○ Number of concurrently running jobs or data flows.○ Amount of pageable cache required for each concurrent data flow.

○ The directory exists on a separate disk or file system from the SAP Data Services system and operating system (such as the C: drive on Windows, or the root file system on UNIX systems).

○ The directory limits the disk space that data flows consume. The pageable cache uses all available disk space on the file system that contains the pageable cache directory. So, to limit the disk space that data flows consume, create a file system (or partition on Windows) with a limited size. Use the new file system (partition on Windows) as the pageable cache directory.The software uses this directory in the following situations:○ For pageable caching, which is the default cache type for data flows.○ When selecting a file transfer type and Automatic is specified in the Data_Transfer transform.

3. In the Peer-to-peer options area, change the values for Start port and End port to restrict the number of ports used by the software. The default values for Start port and End port are 1025 and 32767, respectively.The software uses these ports for peer-to-peer communications when sending data between data flows or sub data flows.

注記

If you want to enable SSL security on the communication paths between data flows and sub data flows, select Use SSL protocol.

4. Click Apply to save any configuration changes.

Task overview: Use the Server Manager on Windows [page 114]

関連情報

Configuring Job Servers [page 115]Access Server の設定 [page 121]SSL パスの設定 [page 122]Job Server と Access Server の実行の確認 [page 123]Performance Optimization Guide: Caching dataReference Guide: Data_TransferPerformance Optimization Guide: Using grid computing to distribute data flows execution

120PUBLIC公開

管理者ガイド

サーバの管理

https://help.sap.com/viewer/e54136ab6a4a43e6a370265bf0a2d744/4.2.14/en-US/575692746d6d1014b3fc9283b0e91070.html

https://help.sap.com/viewer/e54136ab6a4a43e6a370265bf0a2d744/4.2.14/en-US/5756d8ff6d6d1014b3fc9283b0e91070.html

6.8.3 Access Server の設定

Access Server をインストールする場所を設定すると、SAP Data Services によって Access Server ログファイルのため

の領域が作成されます。

1. サーバマネージャを開き、Access Server タブをクリックして編集をクリックします。

2. 実行する設定タスクを以下のように指定します。

○ 新しい Access Server を追加するには、[追加] をクリックします。

残りの設定手順を続けます。

○ 既存の Access Server を編集するには、Access Server を選択して [編集] をクリックします。

残りの設定手順を続けます。

○ 既存の Access Server を削除するには、Access Server を選択して [削除] をクリックします。

この後に必要な設定手順はありません。

3. [Access Server のプロパティ] ウィンドウで、Access Server の設定情報を入力して [OK] をクリックします。

プロパティ説明

ディレクトリこの Access Server インスタンス用のログファイルの場所を指定します。楕円のボタン

をクリックして、ソフトウェアをインストールしたディレクトリの下のログディレクトリを参照

します。

初期設定後にこの値を変更しないでください。

通信ポート Access Server がクライアントからの受信メッセージの受信待機するために使用する、

このコンピュータ上のポートを指定します。

このポート番号が未使用で、それぞれの Access Server に固有になっていることを確

認してください。

パラメータ追加の Access Server パラメータを指定します。

注記

コマンドラインで「AL_AccessServer」と入力すると、追加の Access Server パラメータを確認できます。詳細については、管理コンソールガイドの「“リアルタイ

ムのパフォーマンス”」を参照してください。

SSL プロトコルを使用するこの Access Server のリアルタイムメッセージングで、SSL セキュリティを有効にしま

す。

Access Server を有効にする Data Services サービス起動時に、Access Server を自動的に起動するかどうかを制

御します。

4. [OK] をクリックして、サーバマネージャウィンドウに戻ります。

5. [再起動]をクリックして、更新した設定でサービスを再起動します。

タスクの概要: Use the Server Manager on Windows [114 ページ]

管理者ガイド

サーバの管理

PUBLIC公開 121

関連情報

Configuring Job Servers [115 ページ]Configuring runtime resources [119 ページ]SSL パスの設定 [122 ページ]Job Server と Access Server の実行の確認 [123 ページ]管理コンソールガイド: Access Server の設定

6.8.4 SSL パスの設定

サーバマネージャを使用して、SSL 証明書とキーファイルへのパスを設定します。

注記

デフォルトでは SSL 証明書とキーファイルのパスは、インストール中に自動的に設定されます。独自の証明書を使用

する場合を除き、変更は不要です。

注記

SSL 証明書の設定を変更した場合、ジョブを正常に実行するには、Job Server に関連付けられたすべてのリポジトリ

を再同期する必要があります。

1. サーバマネージャを開き、SSL タブをクリックします。

2. サーバ証明書ファイル、サーバの秘密鍵ファイル、信頼された証明書フォルダの場所を指定します。

注記

サーバ証明書は PEM 形式である必要があります。信頼された証明書フォルダ内で有効な証明書の拡張子

は、.pem、.crt、.cer などです。ファイル拡張子にかかわらず、証明書ファイルの内容はすべて PEM 形式に

します。

3. 秘密鍵パスワードファイルを指定する場合は、[サーバの秘密鍵パスワードファイルを使用する] を選択して、パスワ

ードファイルの場所を指定します。

4. 閉じて再起動をクリックしてサーバマネージャを閉じ、証明書情報が更新されたコンピュータ上の Data Services サー

バをすべて再起動します。

注記

サーバマネージャで指定した証明書情報は、その物理コンピュータ上で実行されているすべての Data Services サー

バに適用されます。たとえば、Job Server、Access Server などです。

タスクの概要: Use the Server Manager on Windows [114 ページ]

122PUBLIC公開

管理者ガイド

サーバの管理

https://help.sap.com/viewer/4d2e69d5c5c2492681f0c64062ba66f1/4.2.14/ja-JP/574f500e6d6d1014b3fc9283b0e91070.html

関連情報

Configuring Job Servers [115 ページ]Configuring runtime resources [119 ページ]Access Server の設定 [121 ページ]Job Server と Access Server の実行の確認 [123 ページ]

6.8.5 Job Server と Access Server の実行の確認

Job Server が実行中であることを確認するには、以下の手順に従います。

1. Windows タスクマネージャのプロセスタブで、以下を確認します。

○ al_jobservice.exe (SAP Data Services サービスを表します)○ al_jobserver.exe (各 Job Server に 1 つです)○ AL_AccessServer.exe (各 Access Server に 1 つです）

2. 予定したすべてのプロセスが表示されない場合は、Job Server イベントログ (<LINK_DIR>/log/<JobServer name>/server_eventlog.txt) でエラーメッセージを確認してください。

注記

Access Server のログは、<AccessServerPathName>/error_mm_dd_yyyy.log にあります。

親トピック: Use the Server Manager on Windows [114 ページ]

関連情報

Configuring Job Servers [115 ページ]Configuring runtime resources [119 ページ]Access Server の設定 [121 ページ]SSL パスの設定 [122 ページ]

6.9 Using the Server Manager on UNIX systems

Use the Server Manager to create, edit, or delete Job Servers and Access Servers after installation on your UNIX platform.

The following tables describe the options that the Server Manager displays.

管理者ガイド

サーバの管理

PUBLIC公開 123

Job Server information

Option Description

Server name This name uniquely identifies the Job Server. The Job Server name cannot be changed.

TCP/IP port number The port number is a TCP/IP port that the Job Server uses to receive commands from the Designer and an Access Server. If a computer hosts multiple Job Servers, each Job Server must have a unique port number. Choose a port number that is not used by another process on the computer. It's recommended that you use 3500. If you are unsure of which port number to use, use the default port number and increment it for each additional Job Server you configure.

Supports adapter communication on port If this computer hosts adapters, you must designate one (and only one) Job Server to support them. Once a Job Server is set to support adapters (a port is entered and saved), it is marked on the Job Server Configuration screen with this label.

Run-time resource information

Option Description

Pageable cache directory This directory contains the pageable cache that the software uses for memory-intensive operations and for file transfer types when Automatic is specified in the Data_Transfer transform.

Start port The software uses this starting port number for peer-to-peer communication between data flows or sub data flows that are running on different Job Servers. The default is 1025.

Access Server information

Option Description

Server number This sequence number uniquely identifies the Access Server on this machine. The Access Server number cannot be changed.

Directory The directory containing Access Server information.

Communication port This port number is used to communicate between the Access Server and the Administrator. The default is 4000.

124PUBLIC公開

管理者ガイド

サーバの管理

Option Description

Parameters Additional parameters used by the Access server.

View Access Server parameters by typing AL_AccessServer at the command line. For more information about parameters, see "Configuring an Access Server" in the Management Console Guide.

Enable Enter Y to activate the Access Server.

Job service information

Option Description

Service executable path The directory containing AL_JobService information.

Status Status of the Data Services service:

● Running● Not running

SMTP Server information

Option Description

Server The name or IP address of the SMTP server (for example, mail.company.com).

Sender The email address that will appear in the From field of the email.

For information about configuring an Access Server, see the Management Console Guide.

Configuring Job Servers on UNIX [page 126]Use the Server Manager to configure the Job Server and to configure a repository Job Server for your Unix or Linux platform.

ランタイムリソースの設定 [page 128]

Access Server の設定 [page 130]


サービスの開始または停止 [page 132]

Configure SMTP email [page 133]Use the Server Manager to specify SMTP server settings for the smtp_to email function.


管理者ガイド

サーバの管理

PUBLIC公開 125

関連情報

DSN-less and TNS-less connections [page 77]Setting UNIX environment variables [page 79]Windows および Unix でのサービスの自動起動 [page 81]History retention and Job Server log retention [page 82]UNIX および Linux のデータベース接続の設定 [page 87]Using the ODBC Drivers Selector for Windows [page 112]Using the License Manager [page 113]Use the Server Manager on Windows [page 114]Configuring Metadata Browsing Service and View Data Service [page 133]Data Services CMC アプリケーション設定 [page 138]

6.9.1 Configuring Job Servers on UNIX

Use the Server Manager to configure the Job Server and to configure a repository Job Server for your Unix or Linux platform.

Before you perform the following steps, ensure that you set all required environment variables.

1. Start the Server Manager by opening a command prompt and typing the following commands:

$ cd $LINK_DIR/bin/ $ . ./al_env.sh $ ./svrcfg

The Server Manager information screen opens.2. Enter 3 to configure a Job Server.

The Job Server information screen appears.

The repository information for each configured Job Server is displayed in one of the following formats:○ The following table contais the formats for a DSN or TNS (Oracle) connection:

Database Type Format of Repository String

Oracle <username>@<TNSname_user>

SAP HANA <username> @<DSNname_user>

DB2

MySQL

SQL Anywhere

○ The following table contains the formats for a server name connection (also known as DSN-less or TNS-less connection):

126PUBLIC公開

管理者ガイド

サーバの管理

Database Type Format of Repository String

Oracle <username>@<server_SID_user>

SAP HANA <username> @<server_port_user>

MySQL <username> @<server_database_user>

DB2

SAP Sybase

3. Enter the command for the applicable configuration task as described in the following table.

Command Configuration task

c Add a new Job Server.

e Edit an existing Job Server.

d Delete an existing Job Server.

a Add a repository connection to a Job Server.

u Update a repository connection on a Job Server.

r Remove a repository connection from a Job Server.

s Set the default repository connection for a Job Server.

y Resynchronize a Job Server configuration with a repository.

You must resynchronize your Job Server and repository when:○ You have uninstalled Data Services and are reinstalling the same version without creating a new

repository.○ You have created a new repository using the Repository Manager after installing the software.

If you resynchronize your Job Server configuration with a repository, you must re-add a connection for this repository to the Administrator. For more information, see the Management Console Guide.

4. To add or edit a Job Server, perform the following substeps as applicable:a. Enter the name for the Job Server.b. Specify the TCP/IP port that the Job Server uses to receive commands from the Designer and the

Access Server.

注記

If a computer hosts multiple Job Servers, each Job Server must have a unique port number. Additionally, the post number must not be used by another process on the computer.

If you are unsure of which port number to use, use the default port number and increment it for each additional Job Server that you configure.

c. Enter Y or N for Do you want to manage adapters for the job server, as applicable.d. Specify the TCP/IP port number to manage adapter communication with the Job Server.e. Enter Y to enable SSL on the adapter management communication paths used by the Job Server.

5. When you add or edit a repository connection, specify the database connection information by performing the following substeps:

管理者ガイド

サーバの管理

PUBLIC公開 127

a. For a DSN-less connection (for a DB2, MySQL, or SAP HANA database), enter N when the Server Manager asks you if you want to use an ODBC data source.

b. For a TNS-less connection for an Oracle database, enter N when the Server Manager asks you if you want to use a TNS name.

c. For a DSN or TNS connection, you must specify the following additional database connection information:

Database Required information

Oracle The TNSNAME specified in tnsnames.ora

MySQL The DSN entry specified in odbc.ini

SAP HANA The DSN entry specified in odbc.iniDB2 The DB2 instance name

SQL Anywhere The DSN entry specified in odbc.ini

d. If your database type is SAP Sybase, specify the Sybase server name specified in the Interfaces file.

注記

The Server Manager for UNIX systems does not prompt for the repository password except when creating a Job Server or adding a repository. To update the repository password in the <DS_COMMON_DIR>/conf/DSConfig.txt file, enter u. All options use the updated password from DSConfig.txt file.

6. When you are satisfied with your configuration changes, enter q and then x to exit the Server Manager.

Task overview: Using the Server Manager on UNIX systems [page 123]

関連情報

ランタイムリソースの設定 [page 128]Access Server の設定 [page 130]SSL パスの設定 [page 131]サービスの開始または停止 [page 132]Configure SMTP email [page 133]DSN-less and TNS-less connections [page 77]

6.9.2 ランタイムリソースの設定

1. 必要な環境変数が設定されていることを確認して、サーバマネージャを実行します。

$ cd $LINK_DIR/bin/ $ . ./al_env.sh

128PUBLIC公開

管理者ガイド

サーバの管理

$ ./svrcfg

サーバマネージャのメイン画面が表示されます。

2. 「4」を入力して、ランタイムリソースを設定します。

ランタイムリソースの情報画面が表示されます。

3. 「e」を入力して、ランタイムリソース設定を編集します。

4. デフォルトの [ページング可能キャッシュディレクトリ] をそのまま使用するか、他の場所を指定します。

制限

ページング可能キャッシュディレクトリのパスは、70 文字以内で指定する必要があります。

注記

Group By、Order By、詳細プロファイルのようにメモリを大量に消費する処理の場合は、以下の条件を満たすペ

ージング可能キャッシュディレクトリを指定します。

○ データに対して十分なディスク領域を持つディレクトリであること。必要なディスク領域を予測するには、同時

に実行するジョブまたはデータフローの数や、同時データフローごとに必要なページング可能キャッシュのサ

イズなどの要素を検討します。

○ Data Services システムやオペレーティングシステムとは別のディスク、またはファイルシステムにあるディレ

クトリであること。

○ データフローが消費するディスク領域が限定されるディレクトリであること。ページング可能キャッシュは、ペ

ージング可能キャッシュディレクトリを含むファイルシステムの使用可能なディスク領域をすべて使用します。

データフローが消費するディスク領域を限定するため、限られたサイズのファイルシステムを作成します。新

しいファイルシステムをページング可能キャッシュディレクトリとして使用します。

このディレクトリは次のような場合に使用されます。

○ ページング可能キャッシュがデータフローのデフォルトキャッシュタイプの場合。詳細については、パフォーマ

ンスの最適化ガイドを参照してください。

○ Data_Transfer トランスフォームで自動が指定されているときに、ソフトウェアによってファイル転送タイプが

選択された場合。

5. [開始ポート] と [終了ポート] の値を変更して、ピアツーピア通信で使用されるポートの数を制限します。デフォルト値

はそれぞれ 1025 および 32767 です。

異なる Job Server で実行されているデータフローまたはサブデータフロー間でデータを送信する際に、ピアツーピア

通信にこれらのポートを使用します。

6. データフローおよびサブデータフロー間の通信パス上で、SSL セキュリティプロトコルを使用するかどうかを指定しま

す。

7. q、x の順に入力して、サーバマネージャを終了します。

タスクの概要: Using the Server Manager on UNIX systems [123 ページ]

関連情報

Configuring Job Servers on UNIX [126 ページ]Access Server の設定 [130 ページ]

管理者ガイド

サーバの管理

PUBLIC公開 129

SSL パスの設定 [131 ページ]サービスの開始または停止 [132 ページ]Configure SMTP email [133 ページ]パフォーマンスの最適化ガイド: グリッドコンピューティングを使用したデータフロー実行の分散

6.9.3 Access Server の設定

Access Server をインストールする場所を設定すると、SAP Data Services によって Access Server ログファイルのため

の領域が作成されます。




2. 「4」を入力して、Access Server を設定します。

Access Server の情報画面が表示されます。

3. 実行する設定タスクに応じて、コマンドを入力します。

コマンド設定タスク

c 新しい Access Server を作成します。

e 既存の Access Server を編集します。

d 既存の Access Server を削除します。

4. Access Server を作成または編集する場合は、追加の設定情報を指定します。

a. 既存の Access Server を編集する場合は、Access Server の設定情報画面に表示されている Access Server の番号を入力します。

b. Access Server のディレクトリを指定します。

c. Access Server が通信に使用する TCP/IP ポートを指定します。

注記

1 台のコンピュータ上に複数の Access Server を設定できますが、ポートは 1 つずつ必要です。すでに使用

されているポート番号を入力した場合は、エラーメッセージが表示されます。

d. Access Server の追加パラメータを指定します。

注記

コマンドラインで「AL_AccessServer」と入力すると、追加の Access Server パラメータを確認できます。

詳細については、管理コンソールガイドの「“リアルタイムのパフォーマンス”」を参照してください。

e. この Access Server のリアルタイムメッセージングで、SSL セキュリティを使用するかどうかを指定します。

f. Access Server を有効にするかどうかを指定します。

5. Access Server を削除する場合は、削除する Access Server の番号を指定します。

130PUBLIC公開

管理者ガイド

サーバの管理

https://help.sap.com/viewer/e54136ab6a4a43e6a370265bf0a2d744/4.2.14/en-US/5756d8ff6d6d1014b3fc9283b0e91070.html

注記

Access Server を 1 つでも削除すると、すべての Access Server が停止します。サーバマネージャを終了する

と、残っている Access Server が再起動されます。

6. 必要な設定変更が終わったら、q、x の順に入力して、サーバマネージャを終了します。


関連情報

Configuring Job Servers on UNIX [126 ページ]ランタイムリソースの設定 [128 ページ]SSL パスの設定 [131 ページ]サービスの開始または停止 [132 ページ]Configure SMTP email [133 ページ]管理コンソールガイド: Access Server の設定

6.9.4 SSL パスの設定

サーバマネージャを使用して、SSL 証明書とキーファイルへのパスを設定します。

注記

デフォルトでは SSL 証明書とキーファイルのパスは、インストール中に自動的に設定されます。独自の証明書を使用

する場合を除き、変更は不要です。




2. 「7」を入力して、SSL パスを設定します。

SSL 設定の情報画面が表示されます。

3. 「e」を入力して、SSL 設定を編集します。

4. プロンプトが表示されたら、以下の SSL 設定情報を指定します。

a. サーバ証明書ファイルへのパス

b. サーバの秘密鍵ファイルへのパス

c. 秘密鍵パスワードファイルを使用するかどうかと、そのファイルへのパス

d. 信頼された証明書が保存されるディレクトリ

管理者ガイド

サーバの管理

PUBLIC公開 131

https://help.sap.com/viewer/4d2e69d5c5c2492681f0c64062ba66f1/4.2.14/ja-JP/574f500e6d6d1014b3fc9283b0e91070.html

注記

サーバ証明書は PEM 形式である必要があります。信頼された証明書フォルダ内で有効な証明書の拡張子

は、.pem、.crt、.cer などです。ファイル拡張子にかかわらず、証明書ファイルの内容はすべて PEM 形式に

します。

5. 必要な設定変更が終わったら、q、x の順に入力して、サーバマネージャを終了します。

サーバマネージャで指定した証明書情報は、その物理コンピュータ上で実行されているすべての Data Services サーバ

(Job Server、Access Server など) に適用されます。


関連情報

Configuring Job Servers on UNIX [126 ページ]ランタイムリソースの設定 [128 ページ]Access Server の設定 [130 ページ]サービスの開始または停止 [132 ページ]Configure SMTP email [133 ページ]

6.9.5 サービスの開始または停止

SAP Data Services サービス (AL_JobService) は $LINK_DIR に割り当てられたデーモンであり、ローカルで設定さ

れている Job Server と Access Server を起動して監視し、実行されていなければ再起動を試行します。

サーバマネージャを終了すると、AL_JobService は Job Server または Access Server に加えられた変更を自動的に

取得します。 AL_JobService を再起動する必要はありません。

1. サーバマネージャを実行します。


注記

2 番目のコマンドは ./svrcfg がサーバマネージャを実行する前に必要な環境変数を設定します。


2. 「1」を入力して、サービス (ジョブサービス) を制御します。

3. ジョブサービスを開始または停止します。

○ 「s」を入力して、ジョブサービスを開始します。

○ 「o」を入力して、ジョブサービスを停止します。

132PUBLIC公開

管理者ガイド

サーバの管理

4. q、x の順に入力して、サーバマネージャを終了します。


関連情報

Configuring Job Servers on UNIX [126 ページ]ランタイムリソースの設定 [128 ページ]Access Server の設定 [130 ページ]SSL パスの設定 [131 ページ]Configure SMTP email [133 ページ]

6.9.6 Configure SMTP email

Use the Server Manager to specify SMTP server settings for the smtp_to email function.

For more information, see “Defining and enabling the smtp_to function” in the Reference Guide.

Parent topic: Using the Server Manager on UNIX systems [page 123]

関連情報

Configuring Job Servers on UNIX [page 126]ランタイムリソースの設定 [page 128]Access Server の設定 [page 130]SSL パスの設定 [page 131]サービスの開始または停止 [page 132]

6.10 Configuring Metadata Browsing Service and View Data Service

SAP Information Steward uses the Metadata Browsing Service and the View Data Service to connect to and view data in profiling sources.

When you install SAP Data Services, the installation configures the two services with default settings, and lists them under the server EIMAdaptiveProcessingServer. You can change the configuration settings to more effectively integrate Information Steward with your hardware, software, and network configurations.

管理者ガイド

サーバの管理

PUBLIC公開 133

To change the configuration settings for Metadata Browsing Service and View Data Service, perform the following steps in the Central Management Console (CMC):

1. Open the Servers management area of the CMC.2. Expand Service Categories node the tree panel and select Enterprise Information Management Services.3. Double-click <computername.> EIMAdaptiveProcessingServer in the list in the right pane.

The Properties page opens.4. Double-click the service to change.5. Change the configuration as applicable and select Save or Save & Close.

注記

Not all changes occur immediately. If a setting can't change immediately, the Properties page displays both the current setting (in red text) and the updated setting. When you return to the Servers management area, the server is labeled as Stale. When you restart the server, it uses the updated settings from the Properties page and removes the Stale flag from the server.

メタデータ参照サービスの設定パラメータ [page 135]メタデータ参照サービスの次のプロパティを変更できます。

Data Services の表示設定パラメータ [page 136]データ表示サービスの次のプロパティを変更できます。

Task overview: サーバの管理 [page 76]

関連情報

DSN-less and TNS-less connections [page 77]Setting UNIX environment variables [page 79]Windows および Unix でのサービスの自動起動 [page 81]History retention and Job Server log retention [page 82]UNIX および Linux のデータベース接続の設定 [page 87]Using the ODBC Drivers Selector for Windows [page 112]Using the License Manager [page 113]Use the Server Manager on Windows [page 114]Using the Server Manager on UNIX systems [page 123]Data Services CMC アプリケーション設定 [page 138]

134PUBLIC公開

管理者ガイド

サーバの管理

6.10.1 メタデータ参照サービスの設定パラメータ

メタデータ参照サービスの次のプロパティを変更できます。

サーバ設定パラメータ説明指定できる値

サービス名サービス設定の名前です。 64 文字以下の英数字の文字列。サービス

名にスペースは使用できません。

デフォルト値: MetadataBrowsingService

データソース接続の最大数サービスインスタンス下で任意の時点に開

くことができる、データソース接続数の上限

です。

整数値。

デフォルト値: 200

サービスプロバイダの起動の再試行回数共有のサービスプロバイダへのアクセスが

競合した際に、新しいサービスプロバイダ

の起動を試行する回数の上限です。


ステートフル接続のタイムアウト (秒) ステートフル接続が開いている最長時間で

す。ステートフル接続には、SAP アプリケー

ションと SAP BW ソースが含まれます。


ステートレス接続のタイムアウト (秒) ステートレス接続が開いている最長時間で

す。ステートレス接続には、すべてのリレー

ショナルデータベースソースが含まれます。


リサイクルしきい値 Data Services バックエンドエンジンが再使

用され、メタデータ参照用に割り当てられた

メモリが解放される前に、サービスによって

処理される要求の最大数です。


ログレベルトレースメッセージのログファイルへの記録

のレベルです。

注記

CMS で設定されているメタデータ参照

サービスのインスタンスが複数ある場

合、すべてのインスタンスから同じレベ

ルの情報が収集されます。最初に実

行されたサービスに対して定義されて

いるログレベルが使用されます。

Information Steward ログ:

● なし: ログは無効です。

● 情報: ログは無効です。([なし] と同

じ)。

● 詳細: すべてのトレース、要求、および

応答です。

Data Services ログ


● 情報: すべてのトレースです。

● 詳細: すべてのトレース、要求、および

応答です。

デフォルトレベルは [情報] です。

接続統計の収集開いている接続に関する統計情報の収集

を有効または無効にします。

デフォルトでは有効です。

管理者ガイド

サーバの管理

PUBLIC公開 135


リスナポート Data Services バックエンドエンジンとの通

信に使用されるポート番号です。

ポート番号を変更する場合、変更を有効に

するには EIM Adaptive Processing Server を再起動する必要があります。

現在使用されていない 4 桁のポート番号。


JMX コネクタポート JMX コネクタで使用するポート番号です。

ポート番号を変更する場合、変更を有効に

するには EIMAdaptiveProcessingServer を再起動する必要があります。

現在使用されていない 4 桁のポート番号。


親トピック: Configuring Metadata Browsing Service and View Data Service [133 ページ]

関連情報

Data Services の表示設定パラメータ [136 ページ]

6.10.2 Data Services の表示設定パラメータ

データ表示サービスの次のプロパティを変更できます。


サービス名サービス設定の名前です。 64 文字以下の英数字の文字列。サ

ービス名にスペースは使用できませ

ん。

デフォルト値: ViewData

リスナポート Data Services バックエンドエンジンとの通信に使用されるポ

ート番号です。

ポート番号を変更する場合、変更を有効にするには

EIMAdaptiveProcessingServer を再起動する必要がありま

す。

4 桁の整数値。


JMX コネクタポート JMX コネクタで使用するポート番号です。

ポート番号を変更する場合、変更を有効にするには

EIMAdaptiveProcessingServer を再起動する必要がありま

す。

4 桁の整数値。


136PUBLIC公開

管理者ガイド

サーバの管理


バッチサイズ (KB) データの表示の応答に格納されるデータのサイズです。最小値: 1000

最大値: 5000


共有サービスプロバイダの最小

数

サービス開始時に起動する必要がある共有 Data Services バックエンドエンジンの最小数です。


共有サービスプロバイダの最大

数

データの表示要求を処理する際に起動できる共有 Data Services バックエンドエンジンの最大数です。


専用サービスプロバイダの最大

数

任意の時点に起動できる専用 Data Services バックエンドエ

ンジンの最大数です。デフォルト値: 10

リサイクルしきい値 Data Services バックエンドエンジンが再使用され、データの

表示用に割り当てられたメモリが解放される前に、サービス

によって処理される要求の最大数です。

任意の整数


サービスプロバイダの起動の試

行回数

Data Services バックエンドエンジンインスタンスの起動が試

行される回数です。デフォルト値: 1

共有サービスプロバイダの最長

アイドル時間 (分)Data Services バックエンドエンジンが要求を処理せずに継

続できる最長時間 (分) です。この時間を超えると、Data Services バックエンドエンジンはシャットダウンされます。


ログレベルトレースメッセージのログファイルへの記録のレベルです。

注記

CMS で設定されているデータ表示サービスのインスタ

ンスが複数ある場合、すべてのインスタンスから同じレ

ベルの情報が収集されます。最初に実行されたサービ

スに対して定義されているログレベルが使用されます。

Information Steward ログ:


● 情報: ログは無効です。 ([なし] と同じ)。

● 詳細: すべてのトレース、要求、

および応答です。

Data Services ログ


● 情報: すべてのトレースです。

● 詳細: すべてのトレース、要求、

および応答です。

デフォルトレベルは [情報] です。

親トピック: Configuring Metadata Browsing Service and View Data Service [133 ページ]

関連情報

メタデータ参照サービスの設定パラメータ [135 ページ]

管理者ガイド

サーバの管理

PUBLIC公開 137

6.11 Data Services CMC アプリケーション設定

セントラル管理コンソール (CMC) で Data Services アプリケーションに関する以下の設定を変更することができます。

設定説明

履歴保持期間ジョブ実行履歴を保持する日数です。


● 0 を入力した場合、ジョブ履歴は保持されません。

● マイナス値を入力した場合、ジョブ履歴は無期限に保持されます。

Job Server のログファイルの保存期間 Job Server のログファイルを保持する日数です。


● 0 を入力した場合、Job Server のログファイルは保持されません。

● マイナス値を入力した場合、Job Server のログファイルは無期限に保持されま

す。

ジョブ履歴クリーンアップ間隔ジョブの開始時間から、Data Services 管理コンソールによって不正なジョブ履歴また

はクラッシュしたジョブ履歴がクリーンアップされるまでの秒数。

この設定を使用すると、通常より実行に時間がかかっているジョブや異常事態の発生

でクラッシュしたジョブを見つけることができます。

ジョブが異常事態によりクラッシュすると、ジョブ履歴メタデータテーブルまたはローカ

ルリポジトリが更新されないため、終了時刻が登録されません。そのため、ジョブがク

ラッシュしても管理コンソールにジョブが依然として実行中であると表示される場合が

あります。

デフォルト設定は 0 です。

● デフォルト値の 0 のままにするか、マイナスの値を設定した場合、不正なジョブ履

歴またはクラッシュしたジョブ履歴はクリーンアップされません。

● 1 以上の値を設定すると、ジョブの開始時間から設定された秒数で不正なジョブ

履歴またはクラッシュしたジョブ履歴がクリーンアップされます。

この設定にプラスの数字を入力する場合、最も実行時間の長いジョブが完了するのに

十分な時間が設けられる秒数を入力してください。この秒数を経過すると、終了タイプ

スタンプのないジョブはエラーとしてマークされます。これらのジョブについては、ログフ

ァイルをチェックして、ジョブが異常終了したのかどうかを判断することができます。

たとえば、実行に最も時間がかかるジョブの所要時間が 30 分の場合、このオプション

を 3600 秒に設定します。そうすると、ジョブの開始時間から 1 時間経過した後、管理

コンソールのバッチジョブのステータスページに表示されるジョブのステータスはもう処

理中ではありません。このようにして、長時間待たなくても、異常事態の発生でクラッシ

ュした可能性があるジョブの一覧を確認することができます。

138PUBLIC公開

管理者ガイド

サーバの管理

設定説明

メタデータ参照サービスおよびデータ表示サ

ービスに対して SSL 通信を有効にする

EIM Adaptive Processing Server のメタデータ参照サービスおよびデータ表示サービ

スで、SSL 通信を使用するかどうかを指定します。

SAP Information Steward など他の SAP ソフトウェア製品では、メタデータ参照サー

ビスおよびデータ表示サービスを使用して、メタデータの参照とインポートや接続内の

データの表示を行います。

デフォルトの SSL 設定を使用デフォルトの SSL キーストアと証明書を使用するかどうかを指定します。

デフォルト値: No

[いいえ] を指定した場合は、[キーストアファイル]、[キーストアパスワード]、[キーパ

スワード] に、値を入力する必要があります。

キーストアファイルキーとキーの署名に使用された証明書チェーンを構成するすべての証明書が格納さ

れている、キーストアのファイル名です。

デフォルト値: DSJavaKeyStore.keystore

キーストアパスワードキーストアファイルのパスワードです。

キーパスワードキーストアファイル内のキーのパスワードです。

暗号化パスフレーズメタデータ参照サービスおよびデータ表示サービスへの要求の一部として送信される、

パスワードの暗号化に使用するパスフレーズです。

SAP HANA など他の SAP ソフトウェア製品は、接続開始要求を送信する際、この [暗号化パスフレーズ] を使ってパスワードを暗号化します。バックエンドエンジンはこのパ

スフレーズを使用してパスワードの復号化を行い、接続開始要求を処理します。


関連情報

DSN-less and TNS-less connections [77 ページ]Setting UNIX environment variables [79 ページ]Windows および Unix でのサービスの自動起動 [81 ページ]History retention and Job Server log retention [82 ページ]UNIX および Linux のデータベース接続の設定 [87 ページ]Using the ODBC Drivers Selector for Windows [112 ページ]Using the License Manager [113 ページ]Use the Server Manager on Windows [114 ページ]Using the Server Manager on UNIX systems [123 ページ]Configuring Metadata Browsing Service and View Data Service [133 ページ]

管理者ガイド

サーバの管理

PUBLIC公開 139

7 Monitoring jobs

To view the overall status of a batch job and job statistics, SAP Data Services provides job monitoring tools in the SAP Data Services Management Console Administrator.

Monitor the job execution information of any batch job in a connected repository. Monitor jobs that you run from the Administrator or from the Designer.

Viewing overall status of executed jobs [page 140]To view the overall status of each batch job execution and to access more detailed statistics and log files, use the list in the Batch Job Status tab of the SAP Data Services Management Console Administrator.

Statistics [page 142]The SAP Data Services Management Console Administrator contains statistics for each job that you run.

Ignoring error status [page 145]When you view the job status logs for jobs with warnings or errors, use the Ignore Error Status button to change the status indicator to green to indicate that you've reviewed the job logs.

Deleting batch job history data [page 145]The Batch Job Status page in the SAP Data Services Management Console includes an option to delete information about how a job ran.

Stopping a running job [page 146]Stop a running batch job in the SAP Data Services Management Console Administrator while you monitor job status.

Deleting trace, monitor, and error logs for a batch job [page 146]View and delete trace, monitor, and error logs for job instances in the SAP Data Services Management Console.

7.1 Viewing overall status of executed jobs

To view the overall status of each batch job execution and to access more detailed statistics and log files, use the list in the Batch Job Status tab of the SAP Data Services Management Console Administrator.

Before you perform the following steps, execute the batch job, log in to the Management Console, and open the Administrator.

To view the overall status of an executed job, perform the following steps:

1. Expand the Batch node on the left of the Administrator window and select the repository name.

The Batch Job Status tab opens at right. The tab shows filter options and a list of each job execution instance for the selected repository.

2. Optional: Filter the list of batch jobs displayed by performing the following substeps:

140PUBLIC公開

管理者ガイド

Monitoring jobs

a. Choose a job name from the Job name list.b. Select Search.

3. Optional: Further filter the list of batch jobs displayed using one of the following Display options:

○ To display the instance of the last execution for the job or jobs: Choose Last execution of job and select Search.

○ To display the instances of the job or jobs executed in the specified number of days: Choose Last, choose the number of days from the Days list, and select Search.

○ To display the instances of the job or jobs executed within the specified date range: Choose All executions, enter a From and To date, and select Search.

4. Optional: Sort a specific column by selecting a column heading and choosing Ascending or Descending in the Batch jobs history section.

5. View the status indicator in the Status column.

Status indicators

Indicator Description

A green icon indicates that the batch job ran without error.

A yellow icon indicates that the batch job has one or more warnings.

A red icon indicates that the batch job experienced an error.

6. Optional: View the End Time column to see when the job completed.

注記

If a job is running longer than usual, and there's no end time listed, there's an issue with the job, or the job completed abnormally. When a job completes abnormally, it doesn't update the job history metadata or the local repository, so there's no end time. You can set a limit for how long jobs display as running in the Central Management Console. For more information, see Data Services CMC アプリケー

ション設定 [page 138].

7. Optional: To view job processing information, select one of the following links under the Job information column:

○ Trace: View information in the Job Trace Log tab.○ Monitor: View information in the Job Monitor Log tab.○ Error: View information in the Job Error Log tab.

8. Optional: View additional information in the Batch Job Status tab, such as server information.

注記

Configure jobs to execute by a specific Job Server, or by a server group. If you choose to execute a job using a server group, use the Batch Job Status tab to see which Job Server actually executed the job.

注記

When the job includes a server group icon in the Job Server column, a server group executed the job. To view the name of the server group, roll your cursor over the Server Group icon. The Job Server listed

管理者ガイド

Monitoring jobsPUBLIC

公開 141

is the Job Server in the server group that executed the job. If you explicitly select a Job Server to execute a job, the Server Group icon doesn't appear for the job, even when the Job Server is a part of a server group.

Task overview: Monitoring jobs [page 140]

関連情報

Statistics [page 142]Ignoring error status [page 145]Deleting batch job history data [page 145]Stopping a running job [page 146]Deleting trace, monitor, and error logs for a batch job [page 146]ステータスの間隔の設定

7.2 Statistics

The SAP Data Services Management Console Administrator contains statistics for each job that you run.

Statistics quantify the activities of the components of the job. View the following types of statistics in the Administrator:

● Job statistics, such as time spent in a given component of a job and the number of data rows that streamed through the component.

● Data flow object statistics, such as the cache size used by a transform within a data flow.

Viewing job statistics [page 143]Use job statistics to help tune job performance.

Data flow statistics [page 144]Use statistics from a data flow to help tune job performance.

Parent topic: Monitoring jobs [page 140]

関連情報

Viewing overall status of executed jobs [page 140]Ignoring error status [page 145]Deleting batch job history data [page 145]Stopping a running job [page 146]Deleting trace, monitor, and error logs for a batch job [page 146]

142PUBLIC公開

管理者ガイド

Monitoring jobs

https://help.sap.com/viewer/4d2e69d5c5c2492681f0c64062ba66f1/4.2.14/ja-JP/574c84336d6d1014b3fc9283b0e91070.html

7.2.1 Viewing job statistics

Use job statistics to help tune job performance.

Before you perform the following steps, run a job for which you want to improve job performance.

To view job statistics in SAP Data Services Management Console, perform the following steps:


The Batch Job Status tab opens at right.2. Find the applicable job instance using the page subtitle.

The page subtitle provides the name of the repository in which SAP Data Services stores the job. Further, use the column headings described in the following table.

Column name Description

Status Contains an icon that indicates the overall job status:○ Green icon indicates that the job ran without error.○ Yellow icon indicates that the job ran, but has one or

more warnings.○ Red icon indicates that the job didn't complete

because of one or more errors.

Job Name Name of the job that you ran in Designer.

System Configuration Name of the set of datastore configurations that the job used to connect to source and target databases when you ran the job.

Each value in this column is a link that opens to the set of datastore configurations in the system configuration.

Job Server Name of the Job Server on which the job ran.

Start Time The date and time that the job started.

End Time The date and time that the job stopped.

Duration The number of seconds that the job took to complete.

Run # The number of times that the job instance ran before it completed.

3. Select Monitor under Job Information for a job instance.The Administrator opens the Job Server Monitor Log Viewer page, which shows statistics about this job instance, starting with the name of the Monitor log file.

After the Monitor log file name, each line in the log provides the information described in the following table.

管理者ガイド


公開 143

Column name Description

Path Name Indicates which object (step in a data flow) is running.

State Indicates the run-time order of the processes in the transform object and the states of each process.

The states in this column aren't error status states. However, an error is indicated when a process state lists Proceed, and it never changes to Stop.

Initializing Indicates that the job is initializing.

Optimizing Indicates that the job is optimizing.

Proceed Indicates that the process is executing.

Stop Indicates that the process ended without error.

Row Count Indicates the number of rows processed through this object. This value updates based on the Monitor sample rate (# of seconds) set as an execution option on the Execute Batch Job page.

Elapsed Time Indicates the number of seconds since the object received its first row of data.

Absolute Time Indicates the number of seconds since the running of this entire data flow, including all of the transforms, began.

Task overview: Statistics [page 142]

関連情報

Data flow statistics [page 144]

7.2.2 Data flow statistics

Use statistics from a data flow to help tune job performance.

Parent topic: Statistics [page 142]

関連情報

Viewing job statistics [page 143]

144PUBLIC公開

管理者ガイド

Monitoring jobs

7.3 Ignoring error status

When you view the job status logs for jobs with warnings or errors, use the Ignore Error Status button to change the status indicator to green to indicate that you've reviewed the job logs.

When you initially look at the Batch Job Status page in SAP Data Services Management Console, the Status column shows icons whose color indicates whether the job ran successfully (green), has warnings (yellow), or has errors (red). After you've reviewed a job that has warnings or errors, use the Ignore Error Status button to change the icon to green, and move on to review the next job with warnings or errors.

To use the Ignore Error Status feature, perform the following steps in the Batch Job Status page:

1. Choose the job and examine the logs to discover why the job has warnings or wasn't successful.2. Select the Ignore Error Status button.

The page refreshes, and the row that you've selected now display a green icon in the Status column.3. Continue in this manner until you've reviewed all jobs that had warnings or errors.


関連情報

Viewing overall status of executed jobs [page 140]Statistics [page 142]Deleting batch job history data [page 145]Stopping a running job [page 146]Deleting trace, monitor, and error logs for a batch job [page 146]

7.4 Deleting batch job history data

The Batch Job Status page in the SAP Data Services Management Console includes an option to delete information about how a job ran.

Delete selected rows from the Batch Job Status page. To delete entire log files on a periodic basis, set the Job Server Log Retention Period or the History Retention Period options in the Central Management Console. For more information about the log retention settings in the Central Management Console, see History retention and Job Server log retention [page 82]. See the Management Console Guide for more information about the Batch Job Status page.


管理者ガイド


公開 145

関連情報

Viewing overall status of executed jobs [page 140]Statistics [page 142]Ignoring error status [page 145]Stopping a running job [page 146]Deleting trace, monitor, and error logs for a batch job [page 146]

7.5 Stopping a running job

Stop a running batch job in the SAP Data Services Management Console Administrator while you monitor job status.

The Batch Job Status page includes an option to stop batch jobs while they are running. If a batch job is running and you need to stop it, select the check box next to the job name and select Abort.


関連情報

Viewing overall status of executed jobs [page 140]Statistics [page 142]Ignoring error status [page 145]Deleting batch job history data [page 145]Deleting trace, monitor, and error logs for a batch job [page 146]

7.6 Deleting trace, monitor, and error logs for a batch job

View and delete trace, monitor, and error logs for job instances in the SAP Data Services Management Console.

Delete a set of batch log history files from a Job Server computer and its corresponding repository. The corresponding Job Server must be up and running to view or delete these logs.

警告

The trace, monitor, and error log files can contain important files that the system needs to create regulatory or certified reports as well as statistical tables. Therefore, make sure that the log files you delete aren't required for reporting purposes. If you're not sure, make backup copies of any files that you need before you delete the batch job history.

146PUBLIC公開

管理者ガイド

Monitoring jobs


The Batch Job Status tab opens at right.2. Select the job or jobs with the logs to delete.

Alternately, you can select Select All.3. Select Delete.

The software deletes the batch log history files from the Job Server computer and the corresponding repository.


関連情報

Viewing overall status of executed jobs [page 140]Statistics [page 142]Ignoring error status [page 145]Deleting batch job history data [page 145]Stopping a running job [page 146]

管理者ガイド


公開 147

8 Lifecycle migration

Lifecycle migration is the process of moving SAP Data Services applications through multiple development phases to production.

Data Services supports simple and complex migration through all phases into production.

Development phases [page 148]SAP Data Services supports multiple phases to conform to your development requirements.

Migration tools [page 152]Migration tools help you create a foundation for your development phases and migration structure.

Migration mechanisms [page 160]Decide which migration mechanism to use to migrate aplications from one development phase to the next.

Migrate with export and import [page 164]Use the flexibility of the export and import features in SAP Data Services to migrate projects with single and multiple developers in different development environments.

Back up repositories [page 172]To avoid data loss by accidentally deleting or overwriting data, adopt the best practice of backing up your repositories on a regular schedule, and especially before migration.

Mismatched locales and job performance [page 173]After you migrate to a new environment, performance is affected by factors such as different locales between source and target data sources.

8.1 Development phases

SAP Data Services supports multiple phases to conform to your development requirements.

The ETL application development process typically involves the following distinct phases:

● Design: Requires only limited sample data and low security.● Test: Requires larger sample data with increased security.● Development: Requires actual data with the highest security.

The following diagram shows the three development phases.

148PUBLIC公開

管理者ガイド

Lifecycle migration

Data Services supports separate repositories for each development phase to control environment differences. Your environment can have as many phases as you require. Further, you can create each phase on a different computer in a different environment with different security settings. Data Services provides migration tools and mechanisms for moving objects from phase to phase in an ordered manner.

The design phase [page 150]In the design phase, define applications that instruct SAP Data Services in your data movement requirements.

The test phase [page 150]In the test phase, test applications for errors and trace the flow of data without exposing actual data to security risks.

The production phase [page 151]In the production phase, use actual data, set a schedule to run applications, monitor application performance, and evaluate results.

Parent topic: Lifecycle migration [page 148]

関連情報

Migration tools [page 152]Migration mechanisms [page 160]Migrate with export and import [page 164]Back up repositories [page 172]Mismatched locales and job performance [page 173]

管理者ガイド

Lifecycle migrationPUBLIC

公開 149

8.1.1 The design phase

In the design phase, define applications that instruct SAP Data Services in your data movement requirements.

The design phase has its own local repository. Data Services stores objects and applications in the local repository for reuse or modification as your system evolves.

Design your project with migration in mind. Consider the following basic guidelines as you design your applications:

● Construct steps as independent, testable modules.● Use meaningful names for each step you construct.● Make independent modules that you can use repeatedly for common operations.● Use test data that reflects all the variations of your production data.

Parent topic: Development phases [page 148]

関連情報

The test phase [page 150]The production phase [page 151]

8.1.2 The test phase

In the test phase, test applications for errors and trace the flow of data without exposing actual data to security risks.

If you discover data movement problems or other errors during this phase, return to the design phase to correct the application. Then move the corrected application to the test phase for further testing.

Testing has two parts:

● The first part includes designing the data movement through the application using your local repository.● The second part includes fully emulating your production environment, including increasing the data

volume.

Use SAP Data Services Management Console Administrator to view feedback through trace, error, and monitor logs during both parts of the test phase. For more information about the Management Console trace and error monitoring, read about batch jobs in the Management Console Guide.

In the second part of the test phase, emulate the production repository environment as closely as possible. For example, schedule jobs through the Central Management Console rather than starting jobs manually.


150PUBLIC公開

管理者ガイド

Lifecycle migration

関連情報

The design phase [page 150]The production phase [page 151]

8.1.3 The production phase

In the production phase, use actual data, set a schedule to run applications, monitor application performance, and evaluate results.

After moving objects from test to production, continue to use the SAP Data Services Management Console Administrator to monitor performance and results. Most issues are caught during testing. However, if the performance or results still aren't what you expect, return to the test phase to optimize performance and refine your target requirements.

Monitor Performance during the production phase:

● View trace and monitoring logs in the Management Console Administrator for information about each job, and the work flows and data flows contained within the job.

注記

Customize log details in jobs to provide the information that is most helpfulWhen you adjust log details to provide more information, the job takes longer to complete. Balance job run time against the information necessary to analyze job performance.

For more information about the Management Console trace and error monitoring, read about batch jobs in the Management Console Guide.

● Check the accuracy of your data by reviewing output and reports.

If you determine that adjustments are necessary, enhance, or correct your applications.

例You notice that an application produces unexpected results. You perform the following tasks:

1. Export the application to the design environment, find issues, and update the application.2. Export the adjusted application to the test environment.3. Test the application.4. When you are satisfied with the results, export changed application to the production environment.


関連情報

The design phase [page 150]

管理者ガイド


公開 151

The test phase [page 150]

8.2 Migration tools

Migration tools help you create a foundation for your development phases and migration structure.

Prepare for migration using one or both tools based on your development environment. The following table describes the migration tools.

Tool Description

Naming conventions Use when migrating applications in a multi-user environment.

Implement standardized naming conventions in datastores for connectivity between computer systems.

Multiple configuration datastore and system configurations Use if your source data comes from multiple, homogeneous systems.

Create datastores with multiple configurations. Each configuration reflects the environment of each development phase.

Group datastores into system configurations to use when running jobs.

移行の命名規則 [page 153]

データストアとシステム設定 [page 156]


関連情報

Development phases [page 148]Migration mechanisms [page 160]Migrate with export and import [page 164]Back up repositories [page 172]Mismatched locales and job performance [page 173]

152PUBLIC公開

管理者ガイド

Lifecycle migration

8.2.1 移行の命名規則

迅速で円滑な移行を実現する最良の方法は、すべての開発環境のすべてのシステムおよび段階において、共通の命名

規則を使用することです。

このようにオブジェクトの先頭文字、接尾語やパス名の識別子を標準化して、プロジェクトを内部的に簡素化するだけでは

なく、外部的にも移行に備えた命名規則を使用することをお勧めします。

移行を容易にするため、以下に対して共通の命名規則を使用します。

● 外部データストアへの接続

● ディレクトリの場所

● スキーマ構造および所有者

ユーザ間や段階間でのアプリケーションの移行は、できる限りすばやく簡単に実行できるようにする必要があります。これ

は、特定の環境での作業に向けた、ジョブの再設定に要する時間を大幅に減らすことにつながります。

抽出、変換、ロードする実際のデータは、通常、データベースによって異なりますが、同じアプリケーションを使って処理す

るデータベースであれば、データの基本的な構造は変わりません。このため、開発プロセスを開始する前にデータベース

の命名と構造を標準化することが最も有用になります。

外部データストアへの接続 [153 ページ]

ディレクトリの場所 [155 ページ]

スキーマ構造および所有者 [155 ページ]

親トピック: Migration tools [152 ページ]

関連情報

データストアとシステム設定 [156 ページ]Designer ガイド: ジョブ内のオブジェクトの命名規約

外部データストアへの接続 [153 ページ]ディレクトリの場所 [155 ページ]スキーマ構造および所有者 [155 ページ]

8.2.1.1 外部データストアへの接続

移行は、エクスポート/インポートによる直接的な方法か、マルチユーザ開発による間接的な方法を使って、ローカルリポ

ジトリ間でオブジェクトを移動するプロセスです。どちらの方法の場合も、ジョブに関連付けられている接続設定に対する

移行の影響を考慮する必要があります。

類似する外部データストア接続に対して汎用的な命名を使用すると、同じデータベースタイプへの接続の再構成に要する

時間を短縮できます。たとえば、同じ種類のデータベース構造への Oracle データストア接続には、移行段階の環境にか

かわらず、すべて同じ論理名を選択します。

管理者ガイド


公開 153

https://help.sap.com/viewer/ec06fadc50b64b6184f835e4f0e1f52f/4.2.14/ja-JP/57388ab36d6d1014b3fc9283b0e91070.html

特定の段階やコンピュータシステム名に対して意味を持つ接続名 (Test_DW、Dev_DW、Prod_DW) にすることができま

すが、この命名構造を用いる場合は、移行に備えたデータストア構造を使用することをお勧めします。

開発サイクルテスト段階

ユーザ名:Dev_DW ユーザ名:Test_DW

パスワード:Dev_DW パスワード:Test_DW

ホスト文字列: Dev_DW ホスト文字列:Test_DW

テスト段階および開発段階でジョブを実行するには、Test_DW と Dev_DW を使用する必要があり、Test インスタンスや

Dev インスタンスに対するジョブを実行するため、データストア設定をそれぞれ別に作成する必要があります。

その代わりに、ジョブを実行するインスタンスにかかわらず、接続文字列 DW を呼び出すことで、複数のデータストア設定

を作成せずにジョブを実行することができます。

開発段階テスト段階

データベース A データストア接続データベース B データストア接続

ユーザ名:DW ユーザ名:DW ユーザ名:DW ユーザ名:DW

パスワード:DW パスワード:DW パスワード:DW パスワード:DW

ホスト文字列:DW 所有者名:DW ホスト文字列:DW 所有者名:DW

例

● 注文データを処理する Oracle ソースシステムが 1 つ社内にあります。このシステムには、開発用、テスト用、本稼動用として、複数のインスタンスが存在します。そのた

め、Oracle ソースシステムへの接続文字列を "ORDER_SYSTEM" と命名します。その後すべての段階で、この名前

が正しい (段階固有の) システムインスタンスを参照するように設定します。

● ターゲットデータウェアハウスへの接続文字列を "DW" と命名した後、現在の環境が開発、テスト、本稼動のいずれ

であるかに応じて、この名前が異なるデータベースを参照するようにします。

この汎用的な段階をまたぐ命名方法を使用すると、(接続文字列のマップ先が 1 つのインスタンスのみであるため) 開発

環境とテスト環境に同じコンピュータからアクセスすることはできません。両方の環境へのアクセスが必要な場合は、複数

のデータストアの設定を使用してください。

親トピック: 移行の命名規則 [153 ページ]

関連情報

ディレクトリの場所 [155 ページ]スキーマ構造および所有者 [155 ページ]Designer ガイド:マルチユーザ対応の開発

154PUBLIC公開

管理者ガイド

Lifecycle migration

https://help.sap.com/viewer/ec06fadc50b64b6184f835e4f0e1f52f/4.2.14/ja-JP/571e54ec6d6d1014b3fc9283b0e91070.html

8.2.1.2 ディレクトリの場所

論理ディレクトリ名 (X:¥ など) を使用するか、共通のローカルドライブを参照して、ディレクトリの場所を標準化することを

お勧めします。たとえば、C:¥ ドライブはすべてのコンピュータにあるため、このディレクトリの場所を参照する C:¥TEMP は安全で、再現性のある基準になります。


関連情報

外部データストアへの接続 [153 ページ]スキーマ構造および所有者 [155 ページ]

8.2.1.3 スキーマ構造および所有者

開発段階間の構造をさらに円滑にするには、すべてのデータベースインスタンスに対して、読み取りと読み込みを行う同じ

スキーマ構造の同じ所有者名を付けます。名前にかかわらず、各スキーマ構造の所有者は異なっていても構いません。

ソフトウェアによって調整されます。

管理者ガイド


公開 155


関連情報

外部データストアへの接続 [153 ページ]ディレクトリの場所 [155 ページ]

8.2.2 データストアとシステム設定

データストアとシステム設定は、さまざまなデータストア環境に対して同じ論理を実行する際に必要な設定を減らすことが

できる、強力なツールです。設定を利用して、開発段階間の移行時間を短縮し、簡素化することができます。

Multiple configurations in multi-user environments [156 ページ]

データストア設定と移行 [157 ページ]

親トピック: Migration tools [152 ページ]

関連情報

移行の命名規則 [153 ページ]

データストア設定と移行 [157 ページ]Multiple configurations in multi-user environments [156 ページ]

8.2.2.1 Multiple configurations in multi-user environments

SAP Data Services also supports a multi-user development environment. A team can work together on an application during development, testing, and production phases. Further, different teams can work on the different phases simultaneously.

Individual users work on an application in their unique local repositories. The team uses a central repository to store, check in, and check out objects that belong to the application primary copy. The central repository preserves all versions of an application's objects, allowing you to revert to a previous version if needed.

The easiest way to set up your environment to work with multi-user functionality is by establishing the exact same environment naming standards among your developers. In each developer's environment, the configuration would be different. For example a database connection string would point to their local database. However, if implementing these naming standards is not possible, you can still save time and streamline your multi-user environment by using multiple-configuration datastores.

156PUBLIC公開

管理者ガイド

Lifecycle migration

For example, if your developers use databases with the same metadata structure but different database instances and owners, you can define a datastore configuration for each developer on your design team, mapping different owners to a common set of aliases used by all. This way, they can share and contribute to the same projects without having to set up their datastore connection information each time they check out a project from the central repository.

Parent topic: データストアとシステム設定 [page 156]

関連情報

データストア設定と移行 [page 157]Designer Guide: Multi-user developmentDesigner Guide: Multi-user environment setupDesigner Guide: Working in a multi-user environmentDesigner Guide: Migrating multi-user jobs

8.2.2.2 データストア設定と移行

データストアを複数設定する場合を除き、リポジトリ間でのエクスポート/インポートでは、新しいリポジトリで作業するため

にデータストア接続を再構成する手間が毎回かかります。

複数設定の場合を除き、リポジトリ内のジョブを実行できるのは、1 つのデータストア設定に対してのみです。

管理者ガイド


公開 157

https://help.sap.com/viewer/ec06fadc50b64b6184f835e4f0e1f52f/4.2.14/ja-JP/571e54ec6d6d1014b3fc9283b0e91070.html

https://help.sap.com/viewer/ec06fadc50b64b6184f835e4f0e1f52f/4.2.14/ja-JP/573a26966d6d1014b3fc9283b0e91070.html

https://help.sap.com/viewer/ec06fadc50b64b6184f835e4f0e1f52f/4.2.14/ja-JP/573662a26d6d1014b3fc9283b0e91070.html

https://help.sap.com/viewer/ec06fadc50b64b6184f835e4f0e1f52f/4.2.14/ja-JP/573698bd6d6d1014b3fc9283b0e91070.html

複数設定の場合、データベースインスタンスごとに別々のデータストア (およびデータストア設定) を使用するのではなく、

複数のデータストア設定を 1 つのデータストア定義に関連付けることができます。

各システムの設定では、ジョブを実行するときに組み合わせて使用する一連のデータストア設定を定義します。システム

設定を作成する前に、リポジトリ内のデータストアの設定を作成する必要があります。

158PUBLIC公開

管理者ガイド

Lifecycle migration

複数設定のデータストアにインポートするすべてのオブジェクトでは、同じ所有者を共有する必要があります。

管理者ガイド


公開 159

親トピック: データストアとシステム設定 [156 ページ]

関連情報

Multiple configurations in multi-user environments [156 ページ]Designer ガイド:データストア、複数のデータストア設定の作成と管理

8.3 Migration mechanisms

Decide which migration mechanism to use to migrate aplications from one development phase to the next.

Choose a migration mechanism based on several criteria, such as project size, team size, and types of objects to migrate. SAP Data Services provides two migration mechanisms:

● Export and import

160PUBLIC公開

管理者ガイド

Lifecycle migration

https://help.sap.com/viewer/ec06fadc50b64b6184f835e4f0e1f52f/4.2.14/ja-JP/572395826d6d1014b3fc9283b0e91070.html

● Multi-user

Export and import migration [page 161]Export and import migration in SAP Data Services involves exporting applications from the local repository in one phase, to the local repository in another phase.

Multi-user development migration [page 162]Multi-user development migration in SAP Data Services includes advanced features, like labeling and filtering, to provide flexibility and control in managing application objects.

The best mechanism [page 163]To determine the best mechanism to use, examine factors, such as the size of your development team, the size of your projects, and the complexity of your projects.


関連情報

Development phases [page 148]Migration tools [page 152]Migrate with export and import [page 164]Back up repositories [page 172]Mismatched locales and job performance [page 173]

8.3.1 Export and import migration

Export and import migration in SAP Data Services involves exporting applications from the local repository in one phase, to the local repository in another phase.

Alternately, instead of importing to another local repository, use an intermediate file and then import the jobs into another local repository.

Consider using the export and import mechanism for the following environment:

● Projects are small to medium size.● Team includes a small number of developers.● Team members use independent Data Services applications through all phases of development.

The following diagram shows the movements between three repositories: Design, Test, and Production. The red lines show an indirect route using a temporary file between the export and import. The blue lines show a direct route from one repository to the next repository.

管理者ガイド


公開 161

例If your test system issues application errors during testing:

1. Open the application in the Design Repository.2. Correct the application errors.3. Export from the Design Repository directly or indirectly to the Test Repository.4. Retest the application.

Parent topic: Migration mechanisms [page 160]

関連情報

Multi-user development migration [page 162]The best mechanism [page 163]

8.3.2 Multi-user development migration

Multi-user development migration in SAP Data Services includes advanced features, like labeling and filtering, to provide flexibility and control in managing application objects.

Instead of exporting and importing applications like you would for simpler environments, multi-user development provides a more secure check-in, check-out, and get mechanism. Multi-user migration uses a central repository to store the primary copies of your application elements.

Consider the multi-user migration mechanism for the following environment:

● Projects are large.● Team includes multiple developers or multiple teams of developers.● Teams work use interdependent parts of Data Services applications through all phases of development.

For more information about migrating multi-user jobs, see the Designer Guide.


162PUBLIC公開

管理者ガイド

Lifecycle migration

関連情報

Export and import migration [page 161]The best mechanism [page 163]

8.3.3 The best mechanism

To determine the best mechanism to use, examine factors, such as the size of your development team, the size of your projects, and the complexity of your projects.

Not all situations comply exactly with our guidelines for determining the mechanisms and tools to use for migration.

SAP Data Services supports a multi-user environment, however, a multi-user environment isn't required on all projects. If your project is small to medium and consists only of one or two developers, then a Central Repository isn't a solution for integrating the work of the developers.

例

Two consultants worked on an HR data mart application. Instead of using a central repository, the consultants worked in the following manner:

● Consultant 1 managed the local repository.● Consultant 2 worked on a new section of development in a copy of the local repository.

Consultant 2 used the export utility to export the completed new section from the copy of the local repository into the original local repository. Then consultant 2 created a copy of the local repository. The copy wrote over the previous copy.

Use the following matrix to help determine which mechanism and tools work best in your environment.

Legend:

● X = Optimal solution● O = Compatible solution● blank = Not applicable

Environments

Migration Mechanism Migration Tool

Export/Import Multiuser Naming ConventionsDatastore & System Configurations

Project: Small to medium

X O O

Team: Multiple X X O

Data: Multiple, homogeneous systems

X X

管理者ガイド


公開 163

Environments

Migration Mechanism Migration Tool

Export/Import Multiuser Naming ConventionsDatastore & System Configurations

Databases: Different source and target databases between the environments

X X

Requirement: A “fast and easy” migration solution

O X


関連情報

Export and import migration [page 161]Multi-user development migration [page 162]

8.4 Migrate with export and import

Use the flexibility of the export and import features in SAP Data Services to migrate projects with single and multiple developers in different development environments.

When you export a job from a test repository to a production repository, change the properties of objects being exported to match your production environment, for example:

● Datastore definitions● Application locations● Database locations● Login information

Choose to export objects directly to another repository or indirectly to a flat file (ATL or XML) and then to another repository. You must be able to connect to and have write permission for target repositories, and the current and new repository versions must match.

制限

You can't export read-only transform configurations.

The export editor [page 165]The SAP Data Services Designer Export editor enables you to select individual objects, object trees, and all objects within the tree for exporting.

Exporting objects to another repository [page 166]

164PUBLIC公開

管理者ガイド

Lifecycle migration

When you export objects directly to another repository, you change environment-specific information defined in datastores and file formats to match the new environment.

Exporting objects to a file [page 167]When you export objects to an ATL or XML file, the process doesn't provide options to change environment-specific information.

Exporting a repository to a file [page 169]When you export an entire repository to a file, SAP Data Services also exports all jobs and their job execution schedules.

Importing objects or a repository from a file [page 169]After you export objects to an ATL or XML file, import the objects to a repository in the target environment.


関連情報

Development phases [page 148]Migration tools [page 152]Migration mechanisms [page 160]Back up repositories [page 172]Mismatched locales and job performance [page 173]

8.4.1 The export editor

The SAP Data Services Designer Export editor enables you to select individual objects, object trees, and all objects within the tree for exporting.

Add the objects to export using drag and drop from the object library into the Export editor. When you select objects, such as work flows, Data Services adds all associated objects to the Export editor. Select objects in the Export editor to exclude from the export, if applicable.

例Export a work flow and all tables contained in the work flow, but exclude the associated data flow.

After you've specified all objects to export, select the file or repository as the target object for the export. When you export objects to a file, enter a passphrase so that Data Services encrypts all passwords associated with the exported objects. Later, you must enter the passphrase when you import the objects to the target environment.

Parent topic: Migrate with export and import [page 164]

管理者ガイド


公開 165

関連情報

Exporting objects to another repository [page 166]Exporting objects to a file [page 167]Exporting a repository to a file [page 169]Importing objects or a repository from a file [page 169]

8.4.2 Exporting objects to another repository

When you export objects directly to another repository, you change environment-specific information defined in datastores and file formats to match the new environment.

Before you export objects from one repository to another repository, ensure that the repositories are created and that they're the same versions.

To export objects from one repository to another repository, perform the following steps, starting in SAP Data Services Designer:

1. Right-click an object to export from the object library and select Export.The Export editor opens in the workspace.

2. Drag and drop additional objects to export from the object library to the Objects to export list.3. Optional: To exclude objects from export:

a. Right-click the applicable object or tree in the Export editor.b. Select Exclude.

A red “X” appears on the icon that represents the excluded objects. If you change your mind, you can add back any object with a red “X”.

4. Right-click an empty area of the Export editor and choose Export to repository.

The login dialog box opens for the Central Management Console (CMC)5. Enter your user credentials for the CMC and select Log on.

After a successful login, the CMC displays a list of repositories available to your user name.6. Select the applicable repository for the export target and select Next.

The Export Confirmation dialog box opens.7. Verify the listed export components.

The following table shows the applicable values in the Destination status column. The values reflect the status of the component in the target database and the proposed action.

Destination Status Action

Does not exist Create or Exclude

Exists Replace or Exclude

8. To edit an action, perform the following substeps:a. Select one or more objects.b. Select either Create, Exclude, or Replace from the Target Status list.

166PUBLIC公開

管理者ガイド

Lifecycle migration

9. Select Next.

The Datastore Export Options dialog box opens.10. Select the applicable datastore, change the owner of a table, or change the connection properties of the

datastore as necessary and select Advanced.11. Change the database connection information as required by the target repository database and select

Next.

The File Format Mapping dialog box opens.12. Select a file and change the Destination Root Path, if necessary.

Change the Destination Root Path for any file format to match the new destination.13. Select Finish.

Data Services copies objects in the Export editor to the target destination. When copying is complete, the objects display in the Output window. The Output window shows the number of objects exported as well as a list of any errors.

Task overview: Migrate with export and import [page 164]

関連情報

The export editor [page 165]Exporting objects to a file [page 167]Exporting a repository to a file [page 169]Importing objects or a repository from a file [page 169]

8.4.3 Exporting objects to a file

When you export objects to an ATL or XML file, the process doesn't provide options to change environment-specific information.

To export objects to a file, perform the following steps in SAP Data Services Designer:

1. Right-click an object in the object library, and select Export.The Export editor opens in the workspace.

2. Drag and drop additional objects to export from the object library to the Objects to export list.3. Optional: To exclude objects from export:

a. Right-click the applicable object from the specific area of the Export editor.b. Select Exclude.

A red “X” appears on the icon that represents the excluded object. If you change your mind, you can add back any object with a red “X”.

4. Right-click an empty area of the Export editor and choose Export to ATL file or Export to XML file, based on the type of file format for the export.

管理者ガイド


公開 167

ヒント

Even though ATL is the Data Services' proprietary format, XML is easier to read the repository content. You can also use XML with the object creation XML toolkit.

By default, Data Services doesn't include non-executable elements in an export to an XML file for improved readability.

例The order of transforms in a data flow isn't included in the export, but Data Services automatically arranges the transforms when you import the data flow into the next phase of Data Services.

5. To include the non-executable elements, perform the following substeps:

a. Select Tools Options.b. Expand Designer and select General.c. Uncheck Exclude non-executable elements from exported XML document.

6. Specify the location for the file.7. Enter the case-sensitive passphrase to encrypt any passwords that are stored in the objects to be exported

and select OK.

注記

The passphrase is required when you import the file so that the passwords are also imported. If you use an incorrect passphrase, or don't enter a passphrase on import, Data Services imports the objects but removes the stored passwords.

If you select the option Export to XML file, your SAP Data Quality Management SDK developer can configure Data Quality transforms within Data Services Designer, and export the settings to an XML file to use with the Data Quality Management SDK.

However, if you employ Data Services as a configuration tool for the Data Quality Management SDK, Data Services doesn't create a change log for changes to the configuration.

You can use the Data Services central repository concept to manage changes to the Data Quality transforms, but no change log is created.


関連情報

The export editor [page 165]Exporting objects to another repository [page 166]Exporting a repository to a file [page 169]Importing objects or a repository from a file [page 169]

168PUBLIC公開

管理者ガイド

Lifecycle migration

8.4.4 Exporting a repository to a file

When you export an entire repository to a file, SAP Data Services also exports all jobs and their job execution schedules.

Keep the following information in mind about exporting a repository to a file:

● You can't export and import schedules without including the associated job and the job's repository.● Data Services doesn't provide options to change environment-specific information.

1. In Data Services Designer, right-click in the Local Object Library and choose Repository Export To File.

2. Browse the directory to change the location, set the file type (XML or ATL), and enter a name for the file.3. Select Save.4. Enter a case-sensitive passphrase to encrypt all passwords that are stored in the repository and select

Export.

注記

The passphrase is required when you import the file so that the passwords are also imported. If you use an incorrect passphrase, or don't enter a passphrase on import, Data Services imports the objects but removes the stored passwords.


関連情報

The export editor [page 165]Exporting objects to another repository [page 166]Exporting objects to a file [page 167]Importing objects or a repository from a file [page 169]

8.4.5 Importing objects or a repository from a file

After you export objects to an ATL or XML file, import the objects to a repository in the target environment.

Before you perform the following steps, export objects from an instance of Data Services to an ATL or XML file. Ensure that the target repository has the same version as the source repository.

注記

Importing objects or an entire repository from a file overwrites existing objects with the same names in the destination repository.

管理者ガイド


公開 169

To import objects or a repository from an ATL or XML file, perform the following steps in Data Services Designer:

1. Right-click in the object library and choose Repository Import from File .

The Open Import File dialog box opens.2. Select the file type of the import file from the list.

Import an individual file or an entire repository by selecting ATL, XML, DMT, or FMT from the list.3. Select a file to import and select Open.

A Data Services warning appears, if applicable, telling you that the imported file overwrites existing objects. Select Yes to continue.

For ATL and XML file types, the Import Plan dialog box opens.4. Select objects to import in one of the following ways:

○ Select Import to import all objects listed in the Import Plan dialog box.○ Highlight objects and use the buttons at the bottom of the window to include or exclude the objects

during import and select Import.○ The following table describes the buttons at the bottom of the Import Plan dialog box.

Option Description

Exclude Select to exclude the selected objects from the list of objects to be imported. A red “X” appears on the object to be excluded.

All occurrences of the object are excluded.

When you import, objects called by the excluded object aren't removed from the list of objects to be imported, unless you've marked them for exclusion.

Exclude Tree Select to exclude the selected object tree from the list of objects to be imported.

例Select a project parent object and select Exclude Tree. The project object and all jobs in the project appear with a red “X” for exclusion from the import.

When you import the list, the excluded objects aren't imported.

170PUBLIC公開

管理者ガイド

Lifecycle migration

Option Description

Include Select to include an object marked for exclusion with a red “X”.

例If you select a project tree and select Exclude Tree, but you decide to import one or two of the jobs in the project, select the job or jobs within the project and select Include.

Data Services removes the red “X” on the icon to indicate that all occurrences of the object are now included in the import.

Include Tree Select to include the selected parent object and all child objects in the import. If you've previously excluded the tree, the red X on all icons disappears. When you import the tree, the parent and all children objects are copied to the destination.

Select All Select to include all objects. The red “X” disappears from any objects that had a red “X”, and all other listed objects are included in the import.

After you select Import, the Passphrase dialog box opens.

5. Enter the passphrase to decrypt the passwords and include them in the import.6. Select Import.

注記

If the passphrase is incorrect, or if you select Import without entering a passphrase, Data Services continues with the import, but doesn't import the passwords. When Data Services doesn't import the passwords, you must set the passwords manually.

7. Perform any additional steps based on the file type you import. The following table describes additional steps based on file type.

管理者ガイド


公開 171

File type Information

ATL file from an earlier version of Data Services Displays a warning that the version of the ATL file is older than the repository version, and that the ATL file you're about to import can contain objects that don't make optimal use of your upgraded repository.

例New features and options in the current version of Data Services may not be available in the imported ATL file.

Workaround: Before you import the ATL file into the newer version of Data Services, import it into a repository with the same version as the ATL, then upgrade the repository.

Options:○ Cancel the import by selecting No to the warning.○ Continue the import by selecting Yes to the warning.

ATL file saved from a repository that is newer than your current version

Displays an error that the version of the ATL file is newer than the repository version, and that the file can't be imported.

Cancel the import by selecting OK.


関連情報

The export editor [page 165]Exporting objects to another repository [page 166]Exporting objects to a file [page 167]Exporting a repository to a file [page 169]

8.5 Back up repositories

To avoid data loss by accidentally deleting or overwriting data, adopt the best practice of backing up your repositories on a regular schedule, and especially before migration.

During the migration process, accidents can happen. Therefore, before you migrate from one development phase to the next, back up your repositories. If the import process overwrites any data, use the backup copy to restore your lost objects.

172PUBLIC公開

管理者ガイド

Lifecycle migration

To back up repositories, follow instructions from the database management system that supports the repository.


関連情報

Development phases [page 148]Migration tools [page 152]Migration mechanisms [page 160]Migrate with export and import [page 164]Mismatched locales and job performance [page 173]

8.6 Mismatched locales and job performance

After you migrate to a new environment, performance is affected by factors such as different locales between source and target data sources.

The cause

Data Services allows you to use different codepages for your source and target databases without causing errors. Data Services attempts to treat equivalent settings without any transcoding. However, mismatched locales can result in performance degradation from the transcoding process during job execution.

例

Your design environment is on Windows, and has the following configurations:

● Data Services, the local repository, and the Job Server are on the same computer.● There's one datastore with two configurations: The source database and the target database.

The test environment has the following configurations:

● The local repository is on the same computer as the design environment.● Data Services and the Job Server are on a different computer.● Data Services has a database client installed for each database required to run jobs in the test

environment.

管理者ガイド


公開 173

Solution

If you notice a significant difference between the speed of design and test environments after migration, check the locale settings of the data sources in the test environment.

● Ensure that your default locales are the same.● Check that codepages for the datastores and the targets datastores match client codepages on the Job

Server computer.

For more information about locales, see ロケールとマルチバイト機能 in the Reference Guide.


関連情報

Development phases [page 148]Migration tools [page 152]Migration mechanisms [page 160]Migrate with export and import [page 164]Back up repositories [page 172]

174PUBLIC公開

管理者ガイド

Lifecycle migration

https://help.sap.com/viewer/8092b085a68941f6aaa6708685a62b0d/4.2.14/ja-JP/5766e2856d6d1014b3fc9283b0e91070.html

9 The Enhanced Change and Transport System (CTS+)

CTS+ transports ABAP and non-ABAP objects between systems for lifecycle management.

Use CTS+ to transport ABAP and non-ABAP objects to a new system, such as upgrading to a new service pack.

注記

To migrate from one environment to another environment, such as design to test, use one of the migration mechanisms described in Migration mechanisms [page 160].

CTS or CTS+

CTS and CTS+ are part of SAP Solution Manager and SAP NetWeaver. CTS+ is a newer version of CTS, which supported transporting only ABAP objects.

For simplicity, we use the term CTS to mean one of two things:

● The system where the transport landscapes are configured.● The system that transports ABAP and non-ABAP objects.

If you don't need a transport management system like CTS, use Object Promotion in the SAP Data Services Management Console Administrator to transport objects over secure FTP. For more information about Object Promotion, see Object promotion management [page 177].

Required versions and CTS+ plug-in

To use CTS in your environment, ensure that you use the following:

● SAP Data Services 4.2 Support Pack 6 patch 1 and later versions● SAP Solution Manager or SAP NetWeaver that supports a separate CTS+ plug-in, or a version that has the

CTS+ plug-in included in the installation.

Transport objects with CTS

Transport the following Data Services objects, and their dependents, using CTS:

● Projects● Jobs● Workflows

管理者ガイド

The Enhanced Change and Transport System (CTS+)PUBLIC

公開 175

● Dataflows● File formats● Functions● Datastores (as top-level object only)

For complete information about CTS+, see the Configuration Guide for CTS+ for version requirements.

176PUBLIC公開

管理者ガイド

The Enhanced Change and Transport System (CTS+)

10 Object promotion management

The object promotion tool in SAP Data Services Management Console Administrator enables you to move one or more objects from one environment to another environment using FTP or shared directories.

To maintain security in both source and target environments, configure the environments so that there is no direct access between them. Also, actions such as exporting and importing objects, and creating export and import configurations, require specific user types and application or repository rights.

Requirements for object promotion [page 177]Understand the special requirements for object promotion, such as user types, application rights, and shared directory requirements.

User rights for promotion management [page 180]The tasks for configuring and performing object promotion in SAP Data Services Management Console require the correct user type, user group, application rights, or repository rights.

Export and import configuration requirements [page 181]Before you create export and import configurations for object promotion, familiarize yourself with some rules and tips for a successful configuration.

Before you export and import objects [page 185]Ensure that you and your systems are ready for export and import.

Object promotion options [page 186]The Object Promotion page in SAP Data Services Management Console offers export and import options.

Exporting objects [page 187]Use object promotion in SAP Data Services Management Console to export objects from a Data Services environment.

Importing objects [page 189]Import objects into a new environment that is different than the export environment.

Export and import trace and error log [page 191]The SAP Data Services Management Console generates trace and error information, which you can access from the Confirmation page after an export or import completes.

10.1 Requirements for object promotion

Understand the special requirements for object promotion, such as user types, application rights, and shared directory requirements.

The following table is an overview of the special requirements for configuring and using the promotion management feature.

管理者ガイド

Object promotion managementPUBLIC

公開 177

Considerations Description

User rights and permissions To configure promotion management, and to export and import objects, the Management Console requires that users have specific rights and permissions.

Repositories The repository in the source and target environments must be running the same Data Services version.

例If you have a design, test, and production environment, repositories in each environment must have the same Data Services version.

Datastore promotion Promote datastores separately from other promoted objects.

Datastore reconfiguration You must reconfigure datastores after import for the following reasons:

● Your design, test, and production data sources are different, therefore, the data source connection information in each environment is different.

● For security, Management Console doesn't promote passwords when it promotes datastores. Therefore, enter the data source password when you reconfigure promoted datastores.

Sequential import Management Console imports each top-level object sequentially. With sequential import, if one object fails to import, Management Console reverts the object back to its previous state, then continues importing with the next top-level object.

Shared directory user rights [page 179]The user who starts the Server Intelligence Agent (SIA) server for the shared directories must at least be a SAP Data Services user with full read and write access to the shared directories.

Sequential import of multiple objects [page 179]If you export the same objects multiple times, and them import the objects, SAP Data Services Management Console imports the objects sequentially by export date.

Parent topic: Object promotion management [page 177]

関連情報

User rights for promotion management [page 180]Export and import configuration requirements [page 181]Before you export and import objects [page 185]

178PUBLIC公開

管理者ガイド

Object promotion management

Object promotion options [page 186]Exporting objects [page 187]Importing objects [page 189]Export and import trace and error log [page 191]

User and rights management [page 50]Detailed application rights [page 52]Detailed repository rights [page 64]

10.1.1 Shared directory user rights

The user who starts the Server Intelligence Agent (SIA) server for the shared directories must at least be a SAP Data Services user with full read and write access to the shared directories.

If you use shared directories for object promotion, and the Data Services user who starts the SIA server for the shared directory doesn't have full read and write access to the directory, the export and import configurations fail validation.

Reset the configurations

Before you can complete an export or import using the shared directories, you must reset the failed configuration.

● Data Services user must have the application right: Manage Object Promotion Configurations.● Open the export and/or import configuration that failed.● Select Test, or select Save.

After resetting the failed configuration, ensure that a user with full read and write access to the shared directories restarts the SIA server.

Parent topic: Requirements for object promotion [page 177]

関連情報

Sequential import of multiple objects [page 179]

10.1.2 Sequential import of multiple objects

If you export the same objects multiple times, and them import the objects, SAP Data Services Management Console imports the objects sequentially by export date.

If you import objects that you've already imported, the Management Console doesn't overwrite the objects in the target system. It displays all imported objects in the Import Configuration page. Objects that you've imported multiple times appear in a group, with the objects in the group listed sequentially based on export date.

管理者ガイド


公開 179

Parent topic: Requirements for object promotion [page 177]

関連情報

Shared directory user rights [page 179]

10.2 User rights for promotion management

The tasks for configuring and performing object promotion in SAP Data Services Management Console require the correct user type, user group, application rights, or repository rights.

The following list contains the various user permissions and rights required for tasks in object promotion:

● User types:○ Data Services Administrator○ Data Services user

● User group: Data Services Administrator group● Application rights:

○ Manage Object Promotion Configurations○ Manage Object Promotion Import

● Repository rights:○ View access○ Full control

The following table summarizes the minimum user requirements for the processes in object promotion.

User requirementsCreate export and import configurations

Export objects from source repository

Import objects to target repository

User type: Data Services Administrator

X X X

User group type: Data Services Administrator Users

X X X

● User type: Regular Data Services user

● Application right: Manage Object Promotion Configurations

X

● User type: Data Services user

● Repository right: View Objects

X

180PUBLIC公開

管理者ガイド


User requirementsCreate export and import configurations

Export objects from source repository

Import objects to target repository

● User type: Regular Data Services user

● Application right: Manage Object Promotion Import

X


関連情報

Requirements for object promotion [page 177]Export and import configuration requirements [page 181]Before you export and import objects [page 185]Object promotion options [page 186]Exporting objects [page 187]Importing objects [page 189]Export and import trace and error log [page 191]User and rights management [page 50]Detailed application rights [page 52]Detailed repository rights [page 64]

10.3 Export and import configuration requirements

Before you create export and import configurations for object promotion, familiarize yourself with some rules and tips for a successful configuration.

Requirements for both export and import configurations

● Ensure that you obtain the required user rights to create and edit export and import configurations. For more information, see User rights for promotion management [page 180].

● For security reasons, only a system administrator can create a shared directory for export and import.● To clear space on a shared directory, delete the exported ATL and Manifest files after you've imported

them.

管理者ガイド


公開 181

ヒント

If you create a separate export configuration for each release, it's easier to identify the groups of files you can safely archive or delete.

Requirements for export configurations

● You can associate the same repository with multiple export configurations.● If a shared directory hasn't yet been created but you've been granted permission to configure exports and

imports, the only available transport option for your configuration is FTP.● If you set an export configuration to use FTP to promote objects to a UNIX system, configure the FTP

server to have full read and write access to the shared directory for exported objects.

Requirements for import configurations

● You can associate only one repository with an import configuration.● An object and all of its dependent objects must have already been exported before you run the import

configuration.● A target repository must be configured to a shared directory to which you've already exported ATL files.

Creating an export configuration [page 183]Create an export configuration to export objects and dependencies over secure FTP or to a shared directory.

Creating an import configuration [page 184]Create an import configuration to import objects and dependencies from an export shared directory.

Edit or delete configurations [page 185]Users with the correct permission and access can edit or delete export and import configurations.


関連情報

Requirements for object promotion [page 177]User rights for promotion management [page 180]Before you export and import objects [page 185]Object promotion options [page 186]Exporting objects [page 187]Importing objects [page 189]Export and import trace and error log [page 191]

182PUBLIC公開

管理者ガイド


10.3.1 Creating an export configuration

Create an export configuration to export objects and dependencies over secure FTP or to a shared directory.

Before you perform the following steps, ensure that you comply with the requirements listed in Export and import configuration requirements [page 181] and Requirements for object promotion [page 177].

To create an export configuration, perform the following steps:

1. Log into SAP Data Services Management Console and open the Administrator.

Start Management Console from your Windows Start menu or by selecting the link in the Start Page of Data Services Designer.

2. Expand the Object Promotion node from the Administrator tree.3. Select the Export Configuration node.

The Export Configuration page opens to the right of the Administrator tree.4. Open either the FTP tab or the Shared Directory tab.

○ FTP: Select to create an export configuration to transport objects using FTP.○ Shared Directory: Select to create an export configuration to transport objects to an existing shared

directory.5. To transport objects over FTP, open the FTP tab and perform the following substeps:

a. Select Add.

The FTP Configuration tab opens.b. Enter applicable information in each of the required fields, which are designated with an asterisk.c. Optional: Choose Secure FTP.

If you don't select Secure FTP, the system exports information in clear text format instead of encrypted format.

d. Select one or more repositories listed in the Available Repositories list and select the right-pointing arrow to add the repositories to the Associated Repositories list.

You can export objects only from the repositories that you include in the Associated Repositories list.e. Select Test.

Testing ensures that the configuration can access the associated repositories and the directory that you indicated in the Target Directory option.

f. Select Save.6. To transport objects directly to an existing shared directory, open the Shared Directory tab and perform the

following steps:a. Select Add.

The Share Directory Configuration tab opens.b. Enter a name for the configurationc. Enter the path of the shared directory in Target Directory.

The target directory is the shared directory for exported objects.d. Select one or more repositories listed in the Available Repositories list and select the right-pointing

arrow to add the repositories to the Associated Repositories list.

You can export objects only from the repositories that you added to the Associated Repositories list.

管理者ガイド


公開 183

e. Select Save.

When you test the FTP configuration, or save the shared directory configuration, the Object Promotion Management tool validates whether the Server Intelligence Agent (SIA) can read and write content to the shared directory. If the configuration can access the repositories with which it has been associated and the SIA validates access to the shared directory, the Management Console saves the configuration with the name that you specified.

The Management Console displays the export configuration name in the following locations:

● As a choice in the Export Configuration page.● As a choice in the Object Name list when you choose the following options from the Select an object list in

the Object Promotion page:○ Export Objects○ Export System Configuration○ Export Substitution Parameters

Task overview: Export and import configuration requirements [page 181]

関連情報

Creating an import configuration [page 184]Edit or delete configurations [page 185]

10.3.2 Creating an import configuration

Create an import configuration to import objects and dependencies from an export shared directory.

Before you perform the following steps, ensure that you comply with the requirements listed in Export and import configuration requirements [page 181] and Requirements for object promotion [page 177].

To create an import configuration, perform the following steps:



2. Expand the Object Promotion node from the Administrator tree at left.3. Select Import Configuration.

The Import Configuration page opens.4. Select Add.5. Select a repository from the Repository list.

The repository is where the imported objects are placed.6. Enter the path to the shared directory that contains the exported ATL files in Source Directory.

After you save the configuration, you can't configure the repository with a different path because the repository won't appear in the list.

184PUBLIC公開

管理者ガイド


7. Select Save.

The Management Console checks that it can access the specified shared directory.

If the import configuration can access the shared directory to where the objects are exported, Management Console saves the configuration. The configuration now appears in the following locations:

● As a choice on the Import Configuration page.● As a choice in the Object Name list when you choose the Import option from the Select an object list.

Task overview: Export and import configuration requirements [page 181]

関連情報

Creating an export configuration [page 183]Edit or delete configurations [page 185]

10.3.3 Edit or delete configurations

Users with the correct permission and access can edit or delete export and import configurations.

A regular SAP Data Services user who is granted the Manage Object Promotion Configurations rights can edit or remove configurations.

Parent topic: Export and import configuration requirements [page 181]

関連情報

Creating an export configuration [page 183]Creating an import configuration [page 184]

10.4 Before you export and import objects

Ensure that you and your systems are ready for export and import.

Check that you comply with the following items before you export and import objects using the object promotion feature:

● You've read and complied with the information in Requirements for object promotion [page 177].● You've met the user rights requirements stated in User rights for promotion management [page 180].

管理者ガイド


公開 185

● The repository from which you're exporting objects is associated with an export configuration.● The repository to which you're importing objects is associated with an import configuration.● The source and target repositories are running the same version of SAP Data Services.● You import to a local repository.

注記

The export repository can be a local or a central repository.

● Export datastores separately from their parent objects.● Import datastores separately from their parent objects.


関連情報

Requirements for object promotion [page 177]User rights for promotion management [page 180]Export and import configuration requirements [page 181]Object promotion options [page 186]Exporting objects [page 187]Importing objects [page 189]Export and import trace and error log [page 191]

10.5 Object promotion options

The Object Promotion page in SAP Data Services Management Console offers export and import options.

Access the Object Promotion page by selecting the Object Promotion node in Management Console. Select an action from the Select an object list in the Object Promotion page. The following table describes each action.

Action Description

Export Objects Select to export objects from the specified repository.

Export Substitution Parameters Select to export existing substitution parameters in the selected repository.

Export System Configurations Select to export existing system configuration in a selected repository.

Import Select to import objects into a selected target repository. Enables you to filter and search for specific objects or object types.

186PUBLIC公開

管理者ガイド



関連情報

Requirements for object promotion [page 177]User rights for promotion management [page 180]Export and import configuration requirements [page 181]Before you export and import objects [page 185]Exporting objects [page 187]Importing objects [page 189]Export and import trace and error log [page 191]

10.6 Exporting objects

Use object promotion in SAP Data Services Management Console to export objects from a Data Services environment.

Before you perform the following steps, ensure that you comply with the requirements listed Before you export and import objects [page 185].

Also create an export configuration.

To export objects using object promotion, perform the following steps:



2. Select the Object Promotion node from the Administrator tree at left.

The Object Promotion page opens at right.3. To export objects:

a. Select Export objects from the Objects list and select Next.b. Select the repository from the Select Repository list.

The repository can be local or central.c. Choose an object type from the Type list and select Next.

Remember that you must export all datastores separately from any parent object.

The Export page opens with a list of the latest versions for all of the objects that match the selected object type. Only the objects that are available in your chosen repository appear in the list.

Management Console lists up to 23 entries on each page. Use the page navigation icons to move to additional pages, if applicable.

d. Optional: Set search criteria to narrow the list of objects and select Search.

Search suggestions:

管理者ガイド


公開 187

○ Enter specific text in the Object Name search field.○ Combine search terms with an asterisk as a wildcard to find objects that partially match or are a

part of a common naming schema.○ If you select a central repository for exporting, use the additional filter options.

例If the selected Object Type is Project, select a different version in the Get list (the default is Latest Version).

When you submit the query, it matches the parent object's label with the associated version. If the label for a child of an object does not match with the specified label, when a parent object is exported, the latest version of the child object will be exported.

4. To export system configurations or substitution parameters:a. Select Export system configurations or Export substitution parameters and select Next.b. Select a repository and select Next.

The Export page opens, with a list of the latest versions for all of the objects that match the selected object type. Only the objects that are available in your chosen repository appear in the list.

Management Console lists up to 23 entries on each page. Use the page navigation icons to move to additional pages, if applicable.

c. Choose up to 23 Object Name entries displayed on the current page, or choose Select All on Current Page to import all 23 objects on the currently displayed page.

d. Optional: Use the Search field to narrow the list to only objects that you want to export.

The Search field supports wildcards.5. Choose the export method from the Export over list.

The method is either shared directory or FTP.6. Select Export.

Results:

For each object, Management Console writes export data to an ATL file and a manifest file, and sends the files to the target directory that is specified in the export configuration.

The Confirmation page displays progress for the export. The Management Console refreshes the Status automatically every five seconds. When the export is completed, the automatic refresh ends, and the final status is Completed. The Confirmation page lists each item exported with an export completed date and time, and a status of success or failure.

For more information about the trace and error logs, and the confirmation ID, see Export and import trace and error log [page 191].

Task overview: Object promotion management [page 177]

関連情報

Requirements for object promotion [page 177]User rights for promotion management [page 180]

188PUBLIC公開

管理者ガイド


Export and import configuration requirements [page 181]Before you export and import objects [page 185]Object promotion options [page 186]Importing objects [page 189]Export and import trace and error log [page 191]

10.7 Importing objects

Import objects into a new environment that is different than the export environment.

Before you import objects, ensure that you've created an import configuration. Also, you must first export the objects so that they are available to import. Ensure that you comply with the requirements in Before you export and import objects [page 185].

To import objects, perform the following steps:



2. Select the Object Promotion node from the Administrator tree at left.

The Object Promotion page opens at right.3. Select Import from the Select an object list and select Next.

The Target Repository page opens.4. Choose a repository from the Select Repository list and select Next.

The Import page opens with a list of exported objects that are available in the source repository. The list contains the following information about each exported object:○ Object name○ Type○ Label (version)○ Source Repository○ Source Repository version○ Date exported (includes the time)○ Whether the object has been imported○ Exported by

There are 23 entries listed on each page.5. Optional: To narrow the list of objects to import, perform the following substeps:

a. Select a Filter option:

○ All○ Objects exported the last <number> Days○ From <date range>

b. Use the Search by options to build an expression:

○ Select All object types, or an object type from the first list.

管理者ガイド


公開 189

○ Select not imported, imported, older export, or All from the next list.○ Enter a word or words in the object name in the last text box. Combine with an asterisk wild card, if

applicable.c. Select Search.

6. Select objects to import per page, or check Select All to select all objects on the page.

Use the page navigation icons to move to the next page and repeat selecting objects on the page.7. Select Import.

Result:

The Confirmation page opens. The Status column reflects the import progress. Management Console updates the status automatically every five seconds.

When the import is completed, the automatic refresh ends, the ending status information is success or failure.

For more information about the logs and the unique conformation ID, see Export and import trace and error log [page 191].

Post-requisites:

● Reconfigure all datastores that you imported:○ Update the connection information.○ Enter the applicable password.

To reconfigure datastores in the SAP Data Servics Management Console, expand the following nodes: Administration Management Datastore.

● Update the paths for any imported substitution parameters.

Required permissions and rights for updating datastores and substitution parameters include one of the following:

● Data Services Administrator user● Data Services Administrator Users group● Regular Data Services user with the application right, Manage datastore and substitution param

configurations.

Task overview: Object promotion management [page 177]

関連情報

Requirements for object promotion [page 177]User rights for promotion management [page 180]Export and import configuration requirements [page 181]Before you export and import objects [page 185]Object promotion options [page 186]Exporting objects [page 187]Export and import trace and error log [page 191]

190PUBLIC公開

管理者ガイド


10.8 Export and import trace and error log

The SAP Data Services Management Console generates trace and error information, which you can access from the Confirmation page after an export or import completes.

Export or import log

View the log information after export or import completes, but while you still have the Confirmation page open. Select view log under the Status column for a specific object.

A dialog box opens showing the unique export or import Confirmation ID in the banner. There's a Trace and an Error tab:

● Trace: Contains details about the export or import.● Error: If there were export or import errors, lists error messages. Otherwise blank.

Further, the Management Console stores log information under the repository table AL_EXPORT_HISTORY.

Export Confirmation ID

The Management Console assigns a unique Confirmation ID to each export or import attempt and displays it in the Confirmation page and the Trace and Error dialog box. The Confirmation ID is a unique ID stored under the AL_EXPORT_HISTORY table. The Management Console uses the Confirmation ID to pass information to the target environment when you import the objects. The Confirmation ID consists of the following information:

<Timestamp-in-milliseconds>-<six-digit random number>-<number of export attempts>

例The breakdown of the Confirmation ID 162447709772-518654-2 is:

● 162447709772 = Timestamp in milliseconds● 518654 = Six-digit random number● 2 = Number of export attempts

You can't return to the Confirmation page after you dismiss it. If you want to refer to the trace and error information later, copy the unique confirmation ID, and any information from the Trace and/or Error tab, and save it to a text file.

Alternately, the Management Console saves a copy of the log to the repository under the AL_EXPORT_HISTORY table. Therefore, to find log information after you close the Confirmation page, query the AL_EXPORT_HISTORY table.


管理者ガイド


公開 191

関連情報

Requirements for object promotion [page 177]User rights for promotion management [page 180]Export and import configuration requirements [page 181]Before you export and import objects [page 185]Object promotion options [page 186]Exporting objects [page 187]Importing objects [page 189]

192PUBLIC公開

管理者ガイド


11 Integration with SAP and SAP Solution Manager

Integrate SAP Data Services with the SAP System Landscape Directory and the SAP Solution Manager diagnostics features to manage, monitor, and maintain your SAP Data Services deployment.

SAP System Landscape Directory (SLD) [page 193]The System Landscape Directory (SLD) is a central repository for your system landscape information, which helps SAP Solution Manager manage SAP software lifecycles.

Solution Manager Diagnostics (SMD) Agent [page 194]The SMD component of SAP Solution Manager provides all functionality to centrally analyze and monitor a complete system landscape.

SLD integration requirements [page 194]SAP Data Services and SAP Solution Manager require specific components to enable System Landscape Directory (SLD) support.

11.1 SAP System Landscape Directory (SLD)

The System Landscape Directory (SLD) is a central repository for your system landscape information, which helps SAP Solution Manager manage SAP software lifecycles.

The SLD contains a description of the systems and software components that are currently installed. The SLD uses all gathered system information to provide a foundation for tool support so that you can better plan software lifecycle tasks in your system landscape. The SLD also provides a directory that contains information about all installable software available from SAP. Additionally, SLD automatically updates existing data about systems that are already installed in your landscape.

The SAP Data Services installation program registers all associated vendors, product names, and versions with the SLD. The installation program also registers server and front-end component names, versions, and location.

Parent topic: Integration with SAP and SAP Solution Manager [page 193]

関連情報

Solution Manager Diagnostics (SMD) Agent [page 194]SLD integration requirements [page 194]

管理者ガイド

Integration with SAP and SAP Solution ManagerPUBLIC

公開 193

11.2 Solution Manager Diagnostics (SMD) Agent

The SMD component of SAP Solution Manager provides all functionality to centrally analyze and monitor a complete system landscape.

If an SMD Agent is installed, the SMD server monitors SAP Data Services and Data Services systems. The SMD Agent reports information to Solution Manager for analysis, which uses the information for root cause analysis.

SAP Data Services supports performance monitoring through CA (Wily) Introscope, which works with Solution Manager Diagnostics through an integration with the NCS (Native Component Supportability) library. The Data Services installer installs the NCS library automatically.


関連情報

SAP System Landscape Directory (SLD) [page 193]SLD integration requirements [page 194]

11.3 SLD integration requirements

SAP Data Services and SAP Solution Manager require specific components to enable System Landscape Directory (SLD) support.

The following table summarizes the components that are required to enable SLD support.

Support for... Required for Data Services

SLD registration Requires the following application and files:

● SAPHOSTAGENT: Enables registration of Data Services servers.

注記

If you install SAPHOSTAGENT before Data Services, the Data Services installer registers servers automatically.

● Create the slddest.cfg.key and slddest.cfg files for the SLDReg data supplier that reports on the back-end servers.

Solution Manager Diagnostics (SMD) Agent integration Download and install SMD Agent (DIAGNOSTICS.AGENT) on all Data Services server hosts.

194PUBLIC公開

管理者ガイド

Integration with SAP and SAP Solution Manager

Support for... Required for Data Services

Performance instrumentation Configure the Introscope Agent to connect to the CA Introscope Enterprise Manager with Data Services Server Manager. For Unix, use the ServerConfig utility.


関連情報

SAP System Landscape Directory (SLD) [page 193]Solution Manager Diagnostics (SMD) Agent [page 194]

管理者ガイド

Integration with SAP and SAP Solution ManagerPUBLIC

公開 195

12 Data Services registration in the SLD

The SLDReg (System Landscape Directory data suppliers) registers the landscape systems, including SAP Data Services, on the SLD server and keeps the information updated.

Management and business applications access the information stored in the SLD to perform tasks in a collaborative computing environment.

SLDReg is installed when you install the SAPHOSTAGENT. After SLDReg is installed, you must create the slddest.cfg and slddest.cfg.key files to enable SLDReg to connect to the SLD server.

The Data Services installer supplies the SLDReg for every installation of Data Services. SLDReg reports on the following components:

● Server components, such as Job Server and Access Server.● Services deployed on the SAP Business Intelligence Platform, such as the RFC (Remote Function Call)

Server, View Data Service, Metadata Browsing Service, and the Administrator Service.● Web applications deployed on an application server, such as the Data Services Management Console

注記

SAP NetWeaver has a built-in SLD-DS supplier that registers the NetWeaver application server as well as hosted web applications and services. This SLD-DS is relevant for Data Services deployments that are integrated in an SAP NetWeaver environment.

The Data Services installer stores the information required for registering Data Services in a configuration file. This file contains information used by the SLDReg to connect to the Data Services database.

For information about how to configure the specific data supplier for WebSphere, see the SAP Web Application Deployment Guide for Unix or SAP Web Application Deployment Guide for Windows.

196PUBLIC公開

管理者ガイド

Data Services registration in the SLD

https://help.sap.com/viewer/b5c0acee766744a9bbc897356f33b962/latest/en-US/46ff02b36e041014910aba7db0e91070.html

https://help.sap.com/viewer/b5c0acee766744a9bbc897356f33b962/latest/en-US/46ff02b36e041014910aba7db0e91070.html

https://help.sap.com/viewer/b56e05d44d7c4648875049bfc96f2a60/latest/en-US/46f8cefb6e041014910aba7db0e91070.html

13 Performance and availability monitoring

Monitor your job performance and system availability using tools in the SAP Solution Manager such as Solution Manager Diagnostics Agent and alert monitoring.

Solution Manager Diagnostics (SMD) overview [page 197]SMD analyzes and monitors problematic components from incidents in your system landscape to help you keep your systems running.

SMD Agent guidelines [page 199]The Solution Manager Diagnostics Agent (DIAGNOSTICS.AGENT) on your local system collects and sends information to the SMD server.

Configure your system for SMD [page 199]For the Solution Manager Diagnostics (SMD) to work properly, enable SMD by configuring the applicable files and setting the correct options.

The Native Component Supportability (NCS) library [page 200]SAP Data Services supports performance monitoring through CA Introscope, which needs the NCS library integration with Solution Manager Diagnostics.

Heartbeat monitoring [page 203]Heartbeat monitoring, also known as availability monitoring, uses the SAP Solution Manager to monitor whether a component, such as a Job Server or Access Server, is running.

Alert monitoring [page 203]SAP Solution Manager provides alerts that enable you to view critical errors.

13.1 Solution Manager Diagnostics (SMD) overview

SMD analyzes and monitors problematic components from incidents in your system landscape to help you keep your systems running.

The SMD Agent sends local information to the SMD, including back-end server configurations and the location of server log files. The SMD uses this information in its analysis of the complete system.

注記

SMD requires SAP Solution Manager version 7.01 SP 26 or later.

The following table describes the components of SMD.

管理者ガイド

Performance and availability monitoringPUBLIC

公開 197

Component Information

SMD Agent Named DIAGNOSTICS.AGENT, collects and sends local diagnositcs information to the SMD through the SMD server.

Download and install the SMD Agent on each Job Server machine.

注記

You must install the SMD Agent on each Job Server machine manually.

For information about the diagnostics Agent installation, see SAP Note 1833501

CA Introscope An application performance management framework. Introscope Enterprise Server is part of SAP Solution Manager. CA Introscope doesn't require a separate installation.

For complete information about the application operations of CA Introscope and the integration with SAP Solution Manager, see the following SAP Community WIKI page: https://wiki.scn.sap.com/wiki/display/TechOps/RCA_Introscope_Home .

NCS (Native Component Supportability) library Integrated in SMD to enable CA Introscope. The Data Services installer automatically installs the NCS library on your system.

SAP Operating System Collector (SAPOSCOL) The SAPOSCOL provides operating system data to SMD and CA Introscope.

For more information about any of the SMD components, see the SAP Solution Manager documentation page at https://help.sap.com/viewer/product/SAP_Solution_Manager/latest/en-US?task=discover_task.

Download any of the components from the SAP Service Marketplace at http://support.sap.com/swdc .

Parent topic: Performance and availability monitoring [page 197]

関連情報

SMD Agent guidelines [page 199]Configure your system for SMD [page 199]The Native Component Supportability (NCS) library [page 200]Heartbeat monitoring [page 203]Alert monitoring [page 203]

198PUBLIC公開

管理者ガイド

Performance and availability monitoring


http://help.sap.com/disclaimer?site=https%3A%2F%2Fwiki.scn.sap.com%2Fwiki%2Fdisplay%2FTechOps%2FRCA_Introscope_Home

http://help.sap.com/disclaimer?site=https%3A%2F%2Fwiki.scn.sap.com%2Fwiki%2Fdisplay%2FTechOps%2FRCA_Introscope_Home

https://help.sap.com/viewer/product/SAP_Solution_Manager/latest/en-US?task=discover_task

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

13.2 SMD Agent guidelines

The Solution Manager Diagnostics Agent (DIAGNOSTICS.AGENT) on your local system collects and sends information to the SMD server.

The following are a few guidelines for using the SMD Agent:

● Install the SMD Agent before or after installing and deploying SAP Data Services. The installation order of the monitored system and agent isn't critical.

● If the servers are deployed on a distributed system, install an SMD Agent on every machine hosting a server.


関連情報

Solution Manager Diagnostics (SMD) overview [page 197]Configure your system for SMD [page 199]The Native Component Supportability (NCS) library [page 200]Heartbeat monitoring [page 203]Alert monitoring [page 203]

13.3 Configure your system for SMD

For the Solution Manager Diagnostics (SMD) to work properly, enable SMD by configuring the applicable files and setting the correct options.

The following list contains the basic steps to enable SMD:

1. Enable the feature in the Data Services Server Manager for each Job Server from which you want performance metrics.

2. If you see unexpected information in the metrics, edit the Native Component Supportability (NCS) Library (ncs.conf) file, which controls the information sent to the SMD Agent.

注記

The ncs.conf library file is located in <LINK_DIR>¥bin. The ncs.conf library file contains descriptions of the options.

3. Configure the following SMD Agent files to provide information to the SAP Solution Manager server.○ SapAgentConfig.xml○ IntroscopeSapAgent.profile

The SMD Agent files are located in your SMD Agent installation location.

管理者ガイド


公開 199


関連情報

Solution Manager Diagnostics (SMD) overview [page 197]SMD Agent guidelines [page 199]The Native Component Supportability (NCS) library [page 200]Heartbeat monitoring [page 203]Alert monitoring [page 203]

13.4 The Native Component Supportability (NCS) library

SAP Data Services supports performance monitoring through CA Introscope, which needs the NCS library integration with Solution Manager Diagnostics.

The Data Services installer automatically installs the NCS library. However, before Data Services can monitor Job Server performance, you need to enable NCS in the Job Server.

Enabling NCS library on Windows [page 201]Enable the NCS (Native Component Supportability) library on the Windows platform.

Enabling NCS library on Unix or Linux [page 202]Enable the NCS (Native Component Supportability) library on the Unix or Linux platforms.


関連情報

Solution Manager Diagnostics (SMD) overview [page 197]SMD Agent guidelines [page 199]Configure your system for SMD [page 199]Heartbeat monitoring [page 203]Alert monitoring [page 203]

200PUBLIC公開

管理者ガイド


13.4.1 Enabling NCS library on Windows

Enable the NCS (Native Component Supportability) library on the Windows platform.

To enable NCS on the Job Server for Windows, perform the following steps:

1. Open the Data Services Server Manager from the Windows Start menu as an Administrator.2. Open the NCS tab.3. Select Enable instrumentation in NCS (Native Component Supportability) library.4. Complete the remaining options.

For most situations, leave the options set to the default settings. The following table describes all of the options in the NCS tab.

Option Description

Tracing level threshold Indicates the tracing level:

○ 0: Uses the value from the ncs.conf configuration file. 0 is the default setting.

○ 1–5: No tracing (NONE).○ 6–10: Tracing major points (MAJOR).○ 11–15: Tracing minor points (MINOR).○ 16–20: Tracing fine details (FINE).○ >20: Max details (FINEST).

Execution interval The time in seconds, between which the system sends the CPU usage/process memory metrics to the CA Interscope Enterprise Manager.

The default setting of 0 causes the system to use the NCS library scheduler.

Execution time offset The execution time offset in seconds related to the set Execution interval.

例If you set the execution settings as follows, the system sends the CPU usage/process memory metrics to the SMD agent at 3:30, 4:30, 5:30, and so on:○ Execution interval = 3600 (every 1 hour)○ Execution time offset = 1800 (every half hour)

If you set the Execution interval to less time than the default NCS library scheduler interval, the system bypasses your setting in Execution time offset. The default NCS library scheduler interval is set in the datasending_interval parameter.

管理者ガイド


公開 201

Option Description

Tracing level Currently not used.

Application passport Currently not used.

5. Select Apply and then select Close.

The system enables the performance monitoring for the jobs run on this computer by the Data Services Job Server.

Task overview: The Native Component Supportability (NCS) library [page 200]

関連情報

Enabling NCS library on Unix or Linux [page 202]

13.4.2 Enabling NCS library on Unix or Linux

Enable the NCS (Native Component Supportability) library on the Unix or Linux platforms.

To enable NCS on the Job Server for Unix or Linux, perform the following steps:

1. Open the DSConfig.txt file.

DSConfig.txt is located in <DS_COMMON_DIR>/conf.

2. Set the Wily_instrumentation parameter to True.

Leave all of the other parameters in the Engine section set to the default values as follows:

● Wily_instrumentation=TRUE● Wily_instrumentation_Level_Threshold=0● Wily_instrumentation_Interval=0● Wily_instrumentation_Offset=● Wily_instrumentation_TraceLevel=3487● Wily_instrumentation_App_Passport=

Task overview: The Native Component Supportability (NCS) library [page 200]

関連情報

Enabling NCS library on Windows [page 201]

202PUBLIC公開

管理者ガイド


13.5 Heartbeat monitoring

Heartbeat monitoring, also known as availability monitoring, uses the SAP Solution Manager to monitor whether a component, such as a Job Server or Access Server, is running.

With hearbeat monitoring, you can also view information about real-time services for Access Servers.

View each monitored Job Server or Access Server status from CA Introscope under the Status node. The following are example values for heartbeat monitoring:

● 1 = The server is running.● 0 = The server isn't running

In addition, view the real-time service status for Access Servers. The following table describes each status indicator.

0 not running

1 starting

2 started

3 shutting down

4 warning

5 error

9 disabled


関連情報

Solution Manager Diagnostics (SMD) overview [page 197]SMD Agent guidelines [page 199]Configure your system for SMD [page 199]The Native Component Supportability (NCS) library [page 200]Alert monitoring [page 203]

13.6 Alert monitoring

SAP Solution Manager provides alerts that enable you to view critical errors.

The SAP Data Services Job Servers send alerts when a job fails.

In CA Introscope Enterprise Manager, view the status for each monitored Job Server under the Status node. A value of 1 indicates a job that ran in a specific Job Server repository has failed.

管理者ガイド


公開 203


関連情報

Solution Manager Diagnostics (SMD) overview [page 197]SMD Agent guidelines [page 199]Configure your system for SMD [page 199]The Native Component Supportability (NCS) library [page 200]Heartbeat monitoring [page 203]

204PUBLIC公開

管理者ガイド


14 Command line administration

SAP Data Services provides utilities that run from a command line on both Windows and Unix platforms.

Each utility has a special set of command-line options that control the behavior of the specific Data Services component.

注記

Data Services components also use internal options, however the internal options aren't published because they can't be modified.

In all command line topics, values shown in square brackets [ ] are optional.

ライセンスマネージャ [page 205]

Command line: Data Services Connection Manager (Unix) [page 208]Use the Connection Manager after you install SAP Data Services on Unix, to configure ODBC databases and ODBC drivers for repositories, sources, and targets.

Command line: Repository Manager (Windows) [page 209]Use the command-line version of the Data Services Repository Manager to create or update repositories on Windows platforms.

Command line: Repository Manager (Unix) [page 211]Use the Repository Manager executable file, repoman, to create or update repositories from the command line on Unix platforms.

Command line: Server Manager (Unix or Linux) [page 213]Use the console-based SAP Data Services Server Manager, svrcfg, on Unix or Linux to create, edit, or delete Job Servers and Access Servers after installation.

Command line: Server Manager (Windows) [page 219]Use the SAP Data Services Server Manager executable, AWServerConfig.exe, on Windows to create, edit, or delete Job Servers and Access Servers after installation

Command line: Password encryption [page 223]Use al_encrypt to encrypt a password with an encryption key or a passphrase, and also to return the base64 encoding of any text.

al_engine options [page 225]al_engine is a core Data Services process that is responsible for executing jobs, importing repository objects, exporting repository objects, and so on.

14.1 ライセンスマネージャ

ライセンスマネージャはコマンドラインモードでのみ使用できます。ユーザは、ライセンスマネージャを使用して製品アクテ

ィベーションキーコードを管理できます。このキーコードは、特定のソフトウェアを実行するたびに参照される英数字のコー

管理者ガイド

Command line administrationPUBLIC

公開 205

ドです。ライセンスマネージャを使用すると、SAP ソリューションポートフォリオソフトウェア (SAP Data Services など) に必要な製品アクティベーションキーコードを表示、追加、および削除できます。

注記

ライセンスマネージャはローカルシステムのキーコードにのみアクセスします。リモートシステムからのキーコードには

アクセスできません。キーコードを更新する場合は、Designer コンピュータや Job Server コンピュータなどの各コン

ピュータでライセンスマネージャを起動して、すべての SAP Data Services コンピュータ上で変更を行います。

注記

Windows オペレーティングシステムを実行している場合、管理者権限がなければ、ライセンスキーコードの追加や削

除を行うことはできません。管理者権限がないユーザの場合、-v パラメータおよび --view パラメータのみが使用

可能です。

構文

LicenseManager [-v | -a <keycode> | -r <keycode> [-l <location>]]

パラメータ説明

-v または --view 格納された製品アクティベーションキーコードを表示します。以下はその例です。

Keycode: 00000-0000000-0000000-0000 Trial Option: Yes Expired: No Days Remaining: 54

-a または --add <keycode>

指定したライセンスキーコードを追加し、格納されたキーコードを表示します。次の状態に対する

ステータスメッセージを戻します。

● 内部エラーが発生しました。

● キーコードが正常に追加されました。

● キーコードが正常に追加され、試用版が置換されました。

● キーコードが無効のため、追加されませんでした。

● キーコードが重複しているため、追加されませんでした。

-r または --remove <keycode> [-l <location>]

指定した製品アクティベーションキーコードを削除し、格納されたキーコードを表示します。

<location> が指定された場合は、そのノードのみについて削除されます。次の状態に対する

ステータスメッセージを戻します。

● 内部エラーが発生しました。

● 1 個のキーコードを削除しました。

● 複数のキーコードを削除しました。

● キーコードが無効のため、削除されませんでした。

● キーコードが見つからないため、削除されませんでした。

Starting License Manager in Unix [207 ページ]Start License Manager from a terminal, and use commands to set your license keys.

206PUBLIC公開

管理者ガイド

Command line administration

親トピック: Command line administration [205 ページ]

関連情報

Command line: Data Services Connection Manager (Unix) [208 ページ]Command line: Repository Manager (Windows) [209 ページ]Command line: Repository Manager (Unix) [211 ページ]Command line: Server Manager (Unix or Linux) [213 ページ]Command line: Server Manager (Windows) [219 ページ]Command line: Password encryption [223 ページ]al_engine options [225 ページ]

14.1.1 Starting License Manager in Unix

Start License Manager from a terminal, and use commands to set your license keys.

Before you use License Manager on UNIX platforms, set the environment variable BOE_REGISTRYHOME.

If you've already configured the SAP Data Services environment by running the al_env.sh script, the BOE_REGISTRYHOME variable is already set. However, if it isn't set, manually add BOE_REGISTRYHOME to your .profile, .login, or .cshrc file:

● If you use Bourne shell, add product entries to your .profile or .login file:

BOE_REGISTRYHOME=$LINK_DIR/registry ; export BOE_REGISTRYHOME ● If you use C shell (Berkeley), add product entries to your .cshrc file:

setenv BOE_REGISTRYHOME $LINK_DIR/registry

To start License Manager in Unix, perform the following steps:

1. Open a terminal.2. Open License Manager by entering a command such as the following:

$ cd $LINK_DIR/bin $ ./LicenseManager

3. Use the commands and syntax in ライセンスマネージャ [page 205] to set your license key.

Task overview: ライセンスマネージャ [page 205]

管理者ガイド


公開 207

14.2 Command line: Data Services Connection Manager (Unix)

Use the Connection Manager after you install SAP Data Services on Unix, to configure ODBC databases and ODBC drivers for repositories, sources, and targets.

The Connection Manager is a command-line utility. However, a graphical user interface (GUI) is available.

注記

To use the graphical user interface for Connection Manager, you must install the GTK+2 library. The GTK+2 is a free multi-platform toolkit that creates user interfaces. For more information about obtaining and installing GTK+2, see https://www.gtk.org/ .

To use DSConnectionManager.sh from the command line, use the -c parameter which must be the first parameter.

If an error occurs when using the Connection Manager, use the -d option to show details in the log

For example:

$LINK_DIR/bin/DSConnectionManager.sh -c -d

注記

For Windows installations, use the ODBC Administrator (Driver Selector) to configure ODBC databases and drivers for repositories, sources, and targets.

Parent topic: Command line administration [page 205]

関連情報

ライセンスマネージャ [page 205]Command line: Repository Manager (Windows) [page 209]Command line: Repository Manager (Unix) [page 211]Command line: Server Manager (Unix or Linux) [page 213]Command line: Server Manager (Windows) [page 219]Command line: Password encryption [page 223]al_engine options [page 225]Using the ODBC Drivers Selector for Windows [page 112]

208PUBLIC公開

管理者ガイド



14.3 Command line: Repository Manager (Windows)

Use the command-line version of the Data Services Repository Manager to create or update repositories on Windows platforms.

The Repository Manager default location is <LINK_DIR>¥bin¥RepoManBatch.exe.

The following table contains descriptions for all of the commands in the Repository Manager.

Option Description

-U<User> Repository login user.

Required for all database types.

-P<Password> Repository login password.


-s Use Server-based connection.

Include the -s parameter when your connection uses a server name (also know as DSN-less or TNS-less) connection to the repository.

If you specify this parameter, you must specify the -p and -V parameters.

Required when you don't use -S.

-S<Server> Use for DSN or TNS connections to the repository:

Values for <Server>:

● For DB2: The DSN (data source name)● For MySQL: The ODBC DSN● For Oracle: TNSNAME defined in tnsnames.ora● For SAP HANA: ODBC DSN● For SAP Sybase SQL Anywhere: ODBC DSN● For SAP ASE: Server

This parameter is required when you don't include -s.

-p<PortNo> Repository server port number.

This parameter is required if you specified -s for a server name connection.

管理者ガイド


公開 209

Option Description

-N<DatabaseType> Repository database type:

● DB2● HANA● MySQL● Oracle● SQL_Anywhere● Sybase (SAP ASE)

This parameter is required.

-Q<Database> Repository database.

This parameter is required only for SAP ASE (Sybase).

-V<Database_version> Repository database server version.

This parameter is required if you specified -s for a server name connection.

-g Repository uses Windows Authentication (Microsoft SQL Server only).

-t<Type> Repository type:

● local● central● profiler

-c Operation mode: Creates repository.

-u Operation mode: Upgrades repository.

-v Operation mode: Gets repository version.

-d Operation mode: Shows details.

-a Central Repository security.

-o Overwrites existing repository.

Example

RepoManBatch -Usa -Psa -NMicroSoft_SQL_Server -SServer -QJake -c -tcentral -d

Or

RepoManBatch -UJake -PJake -NOracle -Sdbsvr -v


210PUBLIC公開

管理者ガイド


関連情報

ライセンスマネージャ [page 205]Command line: Data Services Connection Manager (Unix) [page 208]Command line: Repository Manager (Unix) [page 211]Command line: Server Manager (Unix or Linux) [page 213]Command line: Server Manager (Windows) [page 219]Command line: Password encryption [page 223]al_engine options [page 225]

14.4 Command line: Repository Manager (Unix)

Use the Repository Manager executable file, repoman, to create or update repositories from the command line on Unix platforms.

By default, repoman is installed to the <LINK_DIR>/bin directory.

Specify parameters using a command prompt. ./repoman must be the first command.

The following table contains descriptions for each code in the Repository Manager.

Code Description

-U Repository login user.


-P Repository login password.


-s Specify to use a server name (also known as DSN-less or TNS-less) connection to the repository. You must specify the -p and -V parameters.

Required when you don't use -S.

-S Use for DSN or TNS connections to the repository:

Values for <Server>:

● For DB2: The DSN (data source name)● For MySQL: The ODBC DSN● For Oracle: TNSNAME defined in tnsnames.ora● For SAP HANA: ODBC DSN● For SAP Sybase SQL Anywhere: ODBC DSN● For SAP ASE: Server

Required when you don't include -s.

管理者ガイド


公開 211

Code Description

-p Repository database port number.

Required if you specified -s for a server name connection.

-N Repository database type:

● DB2● HANA● MySQL● Oracle● SQL_Anywhere● Sybase (SAP ASE)


-Q Repository database name.

Required for SAP ASE (Sybase). Optional for Oracle.

-V Repository database version.

Required if you specified -s for a server name connection.

-t Repository type:

● local● central● profiler

-c Operation mode: Creates repository.

-u Operation mode: Upgrades repository.

-v Operation mode: Gets repository version.

-d Operation mode: Shows details.

-a Central repository security.

-o Overwrite existing repository.

例./repoman -Usa -Psa -NDB2 -Srepo_server -Qrepo_central -c -tcentral -d

Where:

Command Description Value

-U User name sa

-P Password sa

-N Repository database type DB2

-S Repository server name repo_server

-Q Repository database name repo_central

-c Create repository

212PUBLIC公開

管理者ガイド


Command Description Value

-t Repository type Central repository

-d Show details


関連情報

ライセンスマネージャ [page 205]Command line: Data Services Connection Manager (Unix) [page 208]Command line: Repository Manager (Windows) [page 209]Command line: Server Manager (Unix or Linux) [page 213]Command line: Server Manager (Windows) [page 219]Command line: Password encryption [page 223]al_engine options [page 225]

14.5 Command line: Server Manager (Unix or Linux)

Use the console-based SAP Data Services Server Manager, svrcfg, on Unix or Linux to create, edit, or delete Job Servers and Access Servers after installation.

svrcfg supports command-line parameters for the following tasks:

● Adding a Job Server● Adding an Access Server● Adding run-time resources● Starting Data Services services● Stopping Data Services services

Find the svrcfg file in $LINK_DIR/bin.

Common parameters

svrcfg supports one common parameter, -T, in combination with task characters for all operations. The following table lists the characters to use in combination with -T for each task.

管理者ガイド


公開 213

Parameter Task

-TJS Add a Job Server.

-TAS Add an Access Server.

-TR Add a runtime resource.

-TSTART Start SAP Data Services services.

-TSTOP Stop SAP Data Services services.

注記

-TSTART and -TSTOP don't require additional parameters.

例To start Data Services services: svrcfg -TSTART

To stop Data Services services: svrcfg -TSTOP

Output

When you use svrcfg to perform tasks from the command line, the Server Manager directs output to the stdout console. The last line of the output indicates whether the task execution succeeded or failed. Possible statuses include the following:

● Success● Failure

Command line: Adding an Access Server (Unix or Linux) [page 215]Add an Access Server in Unix or Linux using the -TAS parameter, along with other special parameters, in svrcfg.

Command line: Adding a Job Server (Unix or Linux) [page 216]Add a Job Server in Unix or Linux using the -TJS parameter, along with other special parameters, in svrcfg.

Command line: Adding runtime resources (Unix or Linux) [page 218]Add runtime resources in Unix or Linux using the -TR parameter along with other special parameters, in svrcfg.


関連情報

ライセンスマネージャ [page 205]Command line: Data Services Connection Manager (Unix) [page 208]

214PUBLIC公開

管理者ガイド


Command line: Repository Manager (Windows) [page 209]Command line: Repository Manager (Unix) [page 211]Command line: Server Manager (Windows) [page 219]Command line: Password encryption [page 223]al_engine options [page 225]

14.5.1 Command line: Adding an Access Server (Unix or Linux)

Add an Access Server in Unix or Linux using the -TAS parameter, along with other special parameters, in svrcfg.

The following table describes the additional Access Server-specific parameters to use with -TAS.

注記

Ensure that -TAS is the first argument in the string.

Parameter Description

-A<path> Specifies the path for the access server.

Replace <path> with the desired path.

-O<port> Specifies the port assigned to the Access Server.

Replace <port> with the desired port number. Use a value from 1024 through 49151 for the port number. The number must be unique and not already in use.

-R<param> Specifies a parameter for the Access Server.

Replace <param> with the desired parameter.

-E Indicates that the Access Server is created and enabled. If -E isn't specified, the Access Server is created but not enabled.

例The following string creates and enables an Access Server on port 4000: svrcfg -TAS -A/home/bods/AStest -O4000 -E

Parent topic: Command line: Server Manager (Unix or Linux) [page 213]

関連情報

Command line: Adding a Job Server (Unix or Linux) [page 216]

管理者ガイド


公開 215

Command line: Adding runtime resources (Unix or Linux) [page 218]

14.5.2 Command line: Adding a Job Server (Unix or Linux)

Add a Job Server in Unix or Linux using the -TJS parameter, along with other special parameters, in svrcfg.

The following table describes the additional Job Server-specific parameters to use with -TJS.

注記

Ensure that -TJS is the first argument in the string.


-a Indicates that the Job Server manages an adapter. If not specified, the new Job Server won't manage adapters.

-b<broker_port> Specifies the adapter manager port.

Replace <broker_port> with the desired port number. The port number can have a value between 1024 and 49151, and must be unique and not in use.

-C<connect_string> Specifies the connection string to use to connect to the repository.

Replace <connect_string> with appropriate information for the database type:

● For DB2, the database instance name.● For MySQL, the data source name as specified in

vendor configuration file referenced by $ODBCINI.● For Oracle, the service name as specified in

tnsnames.ora.● For SAP HANA, the data source name as specified in

vendor configuration file referenced by $ODBCINI● For SAP SQL Anywhere, the database server name.● For SAP IQ, the database server name.

-d<database> Specifies the database name for the repository.

Replace <database> with the name of the repository database.

注記

This parameter is required only for repositories on Sybase.

216PUBLIC公開

管理者ガイド



-D<db_type> Specifies the type of database used for the repository.

Replace <db_type> with a valid value:

● DB2● HANA● MySQL● Oracle● SQL_Anywhere● SYBASE

-e Indicates that SNMP is enabled for the Job Server. If not specified, SNMP is disabled.

-J<server_name> Specifies the name of the Job Server.

Replace <server_name> with the desired name for the Job Server. The specified name must not contain @@ and must be unique.

-P<password> Specifies the password used to connect to the repository.

Replace <password> with the repository password.

-p<port_number> Specifies the listening port for the Job Server.

Replace <port_number> with the desired port number. The port number can have a value between 1024 and 49151, and must be unique and not in use.

-U<username> Specifies the username used to connect to the repository.

Replace <username> with the repository username.

例The following string adds a Job Server with an Oracle repository: svrcfg -TJS -JJobServer_1 -p3500 -DOracle -CORCL -Uuser -Ppassword


関連情報

Command line: Adding an Access Server (Unix or Linux) [page 215]Command line: Adding runtime resources (Unix or Linux) [page 218]

管理者ガイド


公開 217

14.5.3 Command line: Adding runtime resources (Unix or Linux)

Add runtime resources in Unix or Linux using the -TR parameter along with other special parameters, in svrcfg.

The following table describes the additional runtime resource-specific parameters to use with the -TR parameter.

注記

Ensure that -TR is the first argument in the string.


-i<cache_dir> Specifies the directory for the pageable cache.

Replace <cache_dir> with the desired directory.

-n<port> Specifies the ending port number.

Replace <port> with the desired port number. The port number may have a value between 1026 and 32767, and must be unique and not in use. The ending port value must be greater than the starting port value.

-t<port> Specifies the starting port number.

Replace <port> with the desired port number. The port number may have a value between 1025 and 32766, and must be unique and not in use.

例The following string adds a pageable cache resource on ports 2000-3000

svrcfg -TR -i$LINK_DIR¥Log¥Cache2 -t2000 -n3000


関連情報

Command line: Adding an Access Server (Unix or Linux) [page 215]Command line: Adding a Job Server (Unix or Linux) [page 216]

218PUBLIC公開

管理者ガイド


14.6 Command line: Server Manager (Windows)

Use the SAP Data Services Server Manager executable, AWServerConfig.exe, on Windows to create, edit, or delete Job Servers and Access Servers after installation

In addition, AWServerConfig.exe also supports command-line parameters for the following tasks:

● Adding a Job Server● Adding an Access Server● Adding run-time resources● Configuring SSL● Enabling and setting NCS (Native Component Supportability) library● Adding and editing SLD registration information for Data Services

Find the AWServerConfig.exe file in <LINK_DIR>¥bin.

注記

Data Services installs AWServerConfig.exe as a Windows service. Therefore, you can't start or stop the Data Services services using AWServerConfig.exe. Instead, use the standard net command to start and stop the Data Services services.

例To start the Data Services services: net start "SAP Data Services"

To stop the Data Services services: net stop "SAP Data Services"

Command line: Adding an Access Server (Windows) [page 220]Add an Access Server in Windows using the -n parameter and other special parameters.

Command line: Adding a Job Server (Windows) [page 221]Add a Job Server in Windows using the -n parameter along with other special parameters.

Command line: Adding runtime resources (Windows) [page 223]Add runtime resources in Windows using the -n parameter along with other special parameters.


関連情報

ライセンスマネージャ [page 205]Command line: Data Services Connection Manager (Unix) [page 208]Command line: Repository Manager (Windows) [page 209]Command line: Repository Manager (Unix) [page 211]Command line: Server Manager (Unix or Linux) [page 213]Command line: Password encryption [page 223]

管理者ガイド


公開 219

al_engine options [page 225]

The Native Component Supportability (NCS) library [page 200]

14.6.1 Command line: Adding an Access Server (Windows)

Add an Access Server in Windows using the -n parameter and other special parameters.

The following table describes the special Access Server-specific parameters to use with -n.

注記

Ensure that -n is the first argument in the string.


-R<access_server_dir> Specifies the directory path for the Access Server.

Replace <access_server_dir> with the Access Server directory path.

-A<port> Specifies the port assigned to the Access Server.

Replace <port> with the desired port number. The port number may have a value between 1024 and 49151, and must be unique and not in use.

-E Indicates that the Access Server should be enabled. If not specified, the Access Server is created but not enabled.

-T<param> Specifies a parameter for the Access Server.

Replace <param> with the desired parameter.

例The following string creates and enables an Access Server on port : AWServerConfig.exe -n -RC:¥DataServices¥AccessServer -A4000 -E

Parent topic: Command line: Server Manager (Windows) [page 219]

関連情報

Command line: Adding a Job Server (Windows) [page 221]Command line: Adding runtime resources (Windows) [page 223]

220PUBLIC公開

管理者ガイド


14.6.2 Command line: Adding a Job Server (Windows)

Add a Job Server in Windows using the -n parameter along with other special parameters.

The following table describes the other Job Server-specific parameters to use with -n.

注記



-a Indicates that the Job Server will manage an adapter. If not specified, the new Job Server won't manage adapters.

-B<broker_port> Specifies the adapter manager port.

Replace <broker_port> with the desired port number. The port number can have a value between 1024 and 49151, and must be unique and not in use.

-d Indicates that this repository is the default for the Job Server.

-g Indicates that Windows authentication will be used for the connection to the repository.

注記

This parameter is applicable only for repositories on Microsoft SQL Server.

-J<server_name> Specifies the name of the Job Server.

Replace <server_name> with the desired name for the Job Server. The specified name may not contain @@ and must be unique.

-N<db_type> Specifies the type of database used for the repository.

Replace <db_type> with a valid value:

● DB2● Microsoft_SQL_Server● MySQL● Oracle● SQL_Anywhere● Sybase

-P<port_number> Specifies the listening port for the Job Server.

Replace <port_number> with the desired port number. The port number can have a value between 1024 and 49151, and must be unique and not in use.

管理者ガイド


公開 221


-Q<database_name> Specifies the database name for the repository.

Replace <database_name> with the name of the repository database.

注記

This parameter is required only for repositories on Sybase and Microsoft SQL Server.

-s Indicates that SNMP is enabled for the Job Server. If not specified, SNMP is disabled.

-S<server_name> Specifies the database service name or server name used to connect to the repository.

Replace <server_name> with the appropriate information for the database type:

● For Oracle, the database service name as specified in tnsnames.ora.

● For DB2, the database instance name.● For Microsoft SQL Server, the database server name.● For Sybase (SAP ASE), the database server name.● For MySQL, the database source name as specified in

the system DSN.● For SAP Sybase SQL Anywhere, the database server

name.

-U<username> Specifies the username used to connect to the repository.

Replace <username> with the repository username.

-W<password> Specifies the password used to connect to the repository.

Replace <> with the repository password.

例The following string adds a Job Server with an Oracle repository: AWServerConfig.exe -n -JNewJobServer -P3500 -Uuser -Wpass -NOracle -SORCLPROD


関連情報

Command line: Adding an Access Server (Windows) [page 220]Command line: Adding runtime resources (Windows) [page 223]

222PUBLIC公開

管理者ガイド


14.6.3 Command line: Adding runtime resources (Windows)

Add runtime resources in Windows using the -n parameter along with other special parameters.

The following table describes the other runtime resource-specific parameters to use with -n.

注記



-C<cache_dir> Specifies the directory for the pageable cache.

Replace <cache_dir> with the desired directory.

-PF<from_port> Specifies the starting port number.

Replace <from_port> with the desired port number. The port number may have a value between 1025 and 32766, and must be unique and not in use.

-PT<to_port> Specifies the ending port number.

Replace <to_port> with the desired port number. The port number may have a value between 1026 and 32767, and must be unique and not in use. The ending port value must be greater than the starting port value.

例The following string adds a pageable cache resource on ports 2000-2550: AWServerConfig.exe -n -C"%LINK_DIR%¥log¥Pcache" -PF2000 -PT2550


関連情報

Command line: Adding an Access Server (Windows) [page 220]Command line: Adding a Job Server (Windows) [page 221]

14.7 Command line: Password encryption

Use al_encrypt to encrypt a password with an encryption key or a passphrase, and also to return the base64 encoding of any text.

Returning the base64 encoding can be useful to modify a command line that contains global variable or substitution variable data, which must be encoded in base64 form.

管理者ガイド


公開 223

By default, the installer locates al_encrypt in the <LINK_DIR>/bin directory.

Syntax

al_encrypt -e <plain_password> [-k <key string> | -p <passphrase>]

al_encrypt "<text to encode>"

注記

Values shown in square brackets [ ] are optional.

Where


-e <password> Specifies the plain-text password to encrypt.

-k <key string> Specifies the encryption key for encrypting the password.

-p <passphrase> Specifies the passphrase for encrypting the password.

<text to encode> Returns the base64 encoding of any following text when you run al_encrypt with no parameters. The text can be in quotation marks or not.

Example: Encrypt a password using a passphrase

al_encrypt -e mypassword -p thepassphrase > +0100000000120303000803E83F55088B0C987CD715006C02938825530E8691DFD9DDB4198AFFC5C194CD8CE6D338FDE470E2

Example: Encode text using base64 encoding

al_encrypt "encode this as base64" > ZW5jb2RlIHRoaXMgYXMgYmFzZTY0


224PUBLIC公開

管理者ガイド


関連情報

ライセンスマネージャ [page 205]Command line: Data Services Connection Manager (Unix) [page 208]Command line: Repository Manager (Windows) [page 209]Command line: Repository Manager (Unix) [page 211]Command line: Server Manager (Unix or Linux) [page 213]Command line: Server Manager (Windows) [page 219]al_engine options [page 225]

14.8 al_engine options

al_engine is a core Data Services process that is responsible for executing jobs, importing repository objects, exporting repository objects, and so on.

Common options

al_engine supports options that are common to many different operations.

The following table contains descriptions for all applicable codes for the al_engine.


-g Specifies Windows Authentication as the repository connection type. This parameter is valid only for repositories on Microsoft SQL Server.

-Kport<PortNumber> Repository port number for server name connection. This parameter is required if you specified -Kserver for a server name connection.

-Kserver Specify this parameter to use a server name (also known as DSN-less or TNS-less) connection to the repository. If you specify this parameter, you must specify the -Kport and -Kversion parameters.

-Kversion<VersionNumber> Server version for the repository database. Applicable for server-based connections. This parameter is required if you specified -Kserver for a server name connection.

For example, -Kversion"MySQL 5.1"

管理者ガイド


公開 225


-N<DatabaseType> Specifies the repository database type

Acceptable values include:

● Oracle● Microsoft_SQL_Server● DB2● MySQL● Sybase● HANA● SQL_Anywhere

-P<Password> Specifies the password used to log into the repository.

-Q<DatabaseName_or_SID> Specifies the repository database name or SID (for Oracle). For a DSN-less connection to a DB2, SAP Sybase, or SAP Sybase SQL Anywhere repository, use database name.

-S<ServerName> Specifies the repository server name. For a DSN connection to a DB2, SAP HANA, SAP Sybase, or SAP Sybase SQL Anywhere repository, use ODBC connection name.

-U<Username> Specifies the username used to log into the repository.

-v Returns the version number of the Data Services engine.

al_engine Export and Import options [page 227]al_engine imports and exports repository information in the internal scripting languages of SAP Data Services: XML and ATL.


関連情報

ライセンスマネージャ [page 205]Command line: Data Services Connection Manager (Unix) [page 208]Command line: Repository Manager (Windows) [page 209]Command line: Repository Manager (Unix) [page 211]Command line: Server Manager (Unix or Linux) [page 213]Command line: Server Manager (Windows) [page 219]Command line: Password encryption [page 223]

226PUBLIC公開

管理者ガイド


14.8.1 al_engine Export and Import options

al_engine imports and exports repository information in the internal scripting languages of SAP Data Services: XML and ATL.

The following table describes the export and import options that al_engine supports.

注意

The options are only for export and import operations.

注記

Values shown in square brackets [ ] are optional.


-epassphrase<passphrase> Specifies a base64-encoded passphrase to use for the following purposes:

● Encrypt any passwords when exporting objects.● Decrypt any passwords when importing objects.

You can use -epassphrase<passphrase> for a passphrase that contains special characters.

制限

You must transcode the passphrase to the UTF8 character set before encoding it into base64.

-f<filename.atl> Imports information from the ATL file specified in <filename.atl> to the repository.

-passphrase<passphrase> Specifies a plain-text passphrase to use for the following purposes:

● Encrypt any passwords when exporting objects.● Decrypt any passwords when importing objects.

-X Exports the entire repository in ATL format to repo_export.atl.

-XI<filename.xml> Imports information from the XML file specified in <filename.xml> to the repository.

-XKport<PortNumber> Exports repository port number for server name connection. You must use this parameter with the -XKserver parameter.

-XKserver Exports repository server name connection. Applicable for MySQL, SAP HANA, ORACLE, and DB2 database types.

管理者ガイド


公開 227


-XKversion<VersionNumber> Exports repository database server version for server name connection. You must use this parameter with the -XKserver parameter.

例-XKversion“MySQL 5.1”

-Xp@<ObjectType>@<FileName> Exports all repository objects of the specified type to the specified file in ATL format.

-Xp@<ObjectType>@<FileName>@<ObjectName>@D

Exports the specified repository object and its dependents to the specified file in ATL format, excluding datastore information.

-Xp@<ObjectType>@<FileName>@<ObjectName>@DE

Exports the specified repository object and its dependents to the specified file in ATL format, including datastore information.

-Xp@<ObjectType>@<FileName>@<ObjectName> Exports the specified repository object to the specified file in ATL format.

-XX[L] Exports the entire repository in XML format to export.xml.

-XX[L]@<ObjectType>@<FileName> Exports all repository objects of the specified type to the specified file in XML format.

-XX[L]@<ObjectType>@<FileName>@<ObjectName>@D

Exports the specified repository object and its dependents to the specified file in XML format, excluding datastore information.

-XX[L]@<ObjectType>@<FileName>@<ObjectName>@DE

Exports the specified repository object and its dependents to the specified file in XML format, including datastore information.

-XX[L]@<ObjectType>@<FileName>@<ObjectName>

Exports the specified repository object to the specified file in XML format.

注記

When you export objects, you must specify a passphrase with either the -passphrase parameter or the -epassphrase parameter. When you import objects, the passphrase is optional. However, if you don’t specify a passphrase, or the specified passphrase is incorrect, the software removes any encrypted passwords in the imported objects.

Lean XML format [L]

Specify the lean XML format using [L] when you use any of the -XX parameters.

The lean XML format excludes all non-executable elements from the exported XML to improve readability.

228PUBLIC公開

管理者ガイド


例The exact arrangement of transforms in a data flow in the Designer workspace area isn't maintained on export when you use [L] with an -XX parameter. However, when imported back into the software, Data Services arranges the data flows automatically.

例To export all data flows in lean XML format, use the following string:

al_engine -Uuser -Ppassword -Slocalhost -NMySQL -QTheRepository -XXL@D@exported_dataflows.xml -passphraseMypassphrase

Available object type codes

The following table lists the possible values for the object type (<ObjectType>) codes and the related object types.

Code Object type

B COBOL Copybooks

C Custom functions

D data flows

E Excel workbooks

F User-defined file formats

J Jobs

K SDK-type transform configurations

P Projects

p System profiles

S Datastores

T Idocs

v Substitution parameter configurations

W work flows

X XML and DTD message formats

Parent topic: al_engine options [page 225]

管理者ガイド


公開 229

重要免責事項および法的情報

ハイパーリンク

リンクの一部は、アイコンやマウスオーバーテキストで分類されています。これらのリンクから、追加の情報を得ることができます。

アイコンについて。

● このアイコンが付いたリンク: SAP がホストしているものではない Web サイトに移動します。これらのリンクを使用することで、お客様は (お客様と SAP との契約書に別段

の明示的な記載がない限り) 以下のことに同意することになります。

● リンク先のサイトのコンテンツが SAP のドキュメンテーションではないこと。お客様は、この情報に基づいて SAP に対する製品クレームを推断することはできません。

● SAP が、リンク先のサイトのコンテンツについて同意することも反対することもなく、また SAP がその利用可能性や正確性について保証しないこと。SAP は、かかるコン

テンツの使用により発生した損害が、SAP の重大な過失又は意図的な違法行為が原因で発生したものでない限り、その損害に対して一切責任を負いません。

● このアイコンが付いたリンク: 当該の特定の SAP 製品又はサービスのドキュメンテーションから離れ、SAP がホストしている Web サイトに移動します。これらのリンクを使

用することで、お客様は (お客様と SAP との契約書に別段の明示的な記載がない限り)、この情報に基づいて SAP に対する製品クレームを推断することはできないことに同意

します。

外部プラットフォームでホストされているビデオ

一部のビデオは、サードパーティのビデオホスティングプラットフォームに置かれている場合があります。SAP では、これらのプラットフォームに保存されているビデオが将来にわたっ

て利用できると保証することはできません。また、これらのプラットフォームにホストされている、いかなる広告またはその他のコンテンツ (関連ビデオまたは同じサイトでホストされてい

る別のビデオに移動する場合など) については、SAP の管理外であり責任を負いません。

ベータおよびその他の試験的機能

試験的機能は、SAP が将来のリリースを保証する正式に提供される機能の範囲外です。これは、試験的機能は、SAP により通知なく理由の如何を問わず随時変更される場合がある

ことを意味します。試験的機能は、本稼働使用のためのものではありません。お客様は、試験的機能を実際の運用環境で、又は十分なバックアップがとられていないデータとともに、

デモンストレーション、テスト、試験、評価その他の方法で使用してはなりません。

試験的機能の目的は、早期にフィードバックを得ることで、それに応じて顧客の皆様やパートナーが将来の製品に影響を与えることを可能にすることです。SAP コミュニティなどにおい

てフィードバックを提供することで、お客様は、投稿物や二次的著作物の知的財産権が SAP の独占的所有物であり続けることを承認することになります。

コード例

ソフトウェアのコーディングやコードスニペットはすべて、例です。それらは、本稼働使用のためのものではありません。コード例は、構文や表現規則を分かりやすく説明し視覚化するこ

とのみを目的としています。SAP は、コード例の正確性や完全性について保証しません。SAP は、コード例の使用により発生した過誤や損害が、SAP の重大な過失又は意図的な違

法行為が原因で発生したものでない限り、損害に対して一切責任を負いません。

偏見のない表現

SAP は、ダイバーシティ & インクルージョンの文化を支持しています。SAP の文書では、可能な限り、文化、民族性、ジェンダー、および障がいの有無を問わず、すべての人々に対す

る偏見を伴わない表現を採用します。

230PUBLIC公開

管理者ガイド


管理者ガイド


PUBLIC公開 231

www.sap.com/contactsap

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

本書のいかなる部分も、SAP SE 又は SAP の関連会社の明示的な許可なくし

て、いかなる形式でも、いかなる目的にも複製又は伝送することはできません。

本書に記載された情報は、予告なしに変更されることがあります。

SAP SE 及びその頒布業者によって販売される一部のソフトウェア製品には、他

のソフトウェアベンダーの専有ソフトウェアコンポーネントが含まれています。製品

仕様は、国ごとに変わる場合があります。

これらの文書は、いかなる種類の表明又は保証もなしで、情報提供のみを目的と

して、SAP SE 又はその関連会社によって提供され、SAP 又はその関連会社は、

これら文書に関する誤記脱落等の過失に対する責任を負うものではありません。

SAP 又はその関連会社の製品及びサービスに対する唯一の保証は、当該製品

及びサービスに伴う明示的保証がある場合に、これに規定されたものに限られま

す。本書のいかなる記述も、追加の保証となるものではありません。

本書に記載される SAP 及びその他の SAP の製品やサービス、並びにそれらの

個々のロゴは、ドイツ及びその他の国における SAP SE （又は SAP の関連会

社）の商標若しくは登録商標です。本書に記載されたその他すべての製品および

サービス名は、それぞれの企業の商標です。

商標に関する詳細の情報や通知については、https://www.sap.com/japan/about/legal/trademark.html をご覧ください。

THE BEST RUN

https://www.sap.com/japan/about/legal/trademark.html

https://www.sap.com/japan/about/legal/trademark.html