guide d'administration

PUBLIC (PUBLIQUE)SAP Data ServicesVersion du document : 4.2 Support Package 14 (14.2.14.0) – 2022-01-28

Guide d'administration

© 2

021 S

AP S

E ou

soc

iété

affiliée

SAP.

Tous

dro

its ré

serv

és.

THE BEST RUN

Contenu

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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.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

2PUBLICPUBLIQUE

Guide d'administrationContenu

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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Configuring Oracle repository for TCPS protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

5.5 SAP HANA SSL/TLS protocol for repositories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Configuration de SSL/TLS dans la CMC pour SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

5.6 Editing the java.security file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

6 Gestion des serveurs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766.1 DSN-less and TNS-less connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776.2 Setting UNIX environment variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796.3 Lancer les services automatiquement pour Windows and Unix. . . . . . . . . . . . . . . . . . . . . . . . . . . . 816.4 History retention and Job Server log retention. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

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

6.5 Configuration de la connectivité de la base de données pour UNIX et Linux. . . . . . . . . . . . . . . . . . . 87Connexion à la base de données pour UNIX et Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Utilisation du Gestionnaire de connexions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Configuration de pilotes à l'aide de connexions avec nom de serveur (sans DNS). . . . . . . . . . . . .90Configuration des pilotes avec des connexions avec nom de source de données (DSN).. . . . . . . . 95


PUBLICPUBLIQUE 3

Configuration d'ODBC DataDirect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046.6 Using the ODBC Drivers Selector for Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1136.7 Using the License Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1146.8 Use the Server Manager on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Configuring Job Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Configuring runtime resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Configuration des serveurs d'accès. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Configuration des chemins SSL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Vérification de l'exécution des Job Servers et des serveurs d'accès. . . . . . . . . . . . . . . . . . . . . . 124

6.9 Using the Server Manager on UNIX systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Configuring Job Servers on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Configuration des ressources d'exécution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129Configuration des serveurs d'accès. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Configuration des chemins SSL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Démarrage ou arrêt du service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133Configure SMTP email. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

6.10 Configuring Metadata Browsing Service and View Data Service . . . . . . . . . . . . . . . . . . . . . . . . . . .135Paramètres de configuration du service de navigation dans les métadonnées. . . . . . . . . . . . . . 136Paramètres de configuration des services de visualisation des données. . . . . . . . . . . . . . . . . . .138

6.11 Paramètres de l'application CMC de Data Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

7 Monitoring jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1427.1 Viewing overall status of executed jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1427.2 Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Viewing job statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Data flow statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

7.3 Ignoring error status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1477.4 Deleting batch job history data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1477.5 Stopping a running job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1487.6 Deleting trace, monitor, and error logs for a batch job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

8 Lifecycle migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1508.1 Development phases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

The design phase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152The test phase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152The production phase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

8.2 Migration tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Conventions d'affectation des noms pour la migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Configurations système et de banque de données. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

8.3 Migration mechanisms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Export and import migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Multi-user development migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

4PUBLICPUBLIQUE


The best mechanism. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1658.4 Migrate with export and import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166

The export editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Exporting objects to another repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Exporting objects to a file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Exporting a repository to a file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Importing objects or a repository from a file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171

8.5 Back up repositories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1748.6 Mismatched locales and job performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

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

10 Object promotion management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17910.1 Requirements for object promotion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179

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

10.2 User rights for promotion management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18210.3 Export and import configuration requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Creating an export configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Creating an import configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186Edit or delete configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

10.4 Before you export and import objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18710.5 Object promotion options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18810.6 Exporting objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18910.7 Importing objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19110.8 Export and import trace and error log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

11 Integration with SAP and SAP Solution Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19511.1 SAP System Landscape Directory (SLD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19511.2 Solution Manager Diagnostics (SMD) Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19611.3 SLD integration requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196

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

13 Performance and availability monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19913.1 Solution Manager Diagnostics (SMD) overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19913.2 SMD Agent guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20113.3 Configure your system for SMD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20113.4 The Native Component Supportability (NCS) library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Enabling NCS library on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Enabling NCS library on Unix or Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

13.5 Heartbeat monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20513.6 Alert monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205


PUBLICPUBLIQUE 5

14 Command line administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20714.1 Gestionnaire de licences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Starting License Manager in Unix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20914.2 Command line: Data Services Connection Manager (Unix). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21014.3 Command line: Repository Manager (Windows). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21114.4 Command line: Repository Manager (Unix). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21314.5 Command line: Server Manager (Unix or Linux). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

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

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

14.7 Command line: Password encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22514.8 al_engine options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

al_engine Export and Import options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

6PUBLICPUBLIQUE


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.

RemarqueData 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

RemarqueINSTALL_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.

Guide d'administrationNaming conventions and variables

PUBLICPUBLIQUE 7


BIP_INSTALL_DIR The directory for the BI or IPS platform.

Default location:

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

ExempleC:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0

● For UNIX: <INSTALL_DIR>/enterprise_xi40

RemarqueThese paths are the same for both BI and IPS.

RemarqueBIP_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

ExempleC:\Program Files (x86)\SAP BusinessObjects\Data Services

8PUBLICPUBLIQUE



<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

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

ExempleC:\ProgramData\SAP BusinessObjects\Data Services

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

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

ExempleC:\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.

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


PUBLICPUBLIQUE 9


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

RemarqueThe 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

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

RemarqueThe 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.

10PUBLICPUBLIQUE


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.

ExempleIntegrate 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]

Guide d'administrationArchitecture overview

PUBLICPUBLIQUE 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]

Informations associées

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

12PUBLICPUBLIQUE


2.2 Standard components

SAP 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.

RemarqueThe 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]


PUBLICPUBLIQUE 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 19]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.

RemarqueIn 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]

14PUBLICPUBLIQUE



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

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 19]


PUBLICPUBLIQUE 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]

16PUBLICPUBLIQUE


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

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 19]

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.


PUBLICPUBLIQUE 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 19]

18PUBLICPUBLIQUE


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.

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]


PUBLICPUBLIQUE 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.


Gestionnaire de licences [page 207]

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.

20PUBLICPUBLIQUE


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 115]Using the Server Manager on UNIX systems [page 124]

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.


PUBLICPUBLIQUE 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 23]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]

22PUBLICPUBLIQUE


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.

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


PUBLICPUBLIQUE 23

SAP tool Description

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

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 177]SAP System Landscape Directory (SLD) [page 195]Solution Manager Diagnostics (SMD) Agent [page 196]

24PUBLICPUBLIQUE


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.

Guide d'administrationSecurity

PUBLICPUBLIQUE 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.

RemarqueIn 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]

26PUBLICPUBLIQUE


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 23]


PUBLICPUBLIQUE 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.

ExempleThe 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.

28PUBLICPUBLIQUE




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.


PUBLICPUBLIQUE 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

30PUBLICPUBLIQUE


● 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.

RemarqueEncrypting 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.

RemarqueWhen 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.


PUBLICPUBLIQUE 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.

32PUBLICPUBLIQUE


RemarqueAll TCP/IP communication paths support SSL/TLS.

RemarqueDepending 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.


PUBLICPUBLIQUE 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]Using custom certificates [page 39]

34PUBLICPUBLIQUE


Generating keys and signing certificates [page 40]

3.6.3 Copying certificates in a distributed environmentManually 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.

RemarqueTrusted 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.

N'oubliez pasWhen 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.b. If the message client host uses Java, import the trusted certificates into the keystore used by the

message client application.


PUBLICPUBLIQUE 35

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.

RemarqueIf 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.

36PUBLICPUBLIQUE



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

RemarqueBy 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.

RemarqueYou 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.

RemarqueIf 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.


PUBLICPUBLIQUE 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.

RemarqueYou 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 115]Using the Server Manager on UNIX systems [page 124]

38PUBLICPUBLIQUE


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:

RemarqueThe 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.

RemarqueWhen 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]


PUBLICPUBLIQUE 39

Configuration des chemins SSL [page 123]

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.

RemarqueBy 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.

RemarqueTrusted 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]Configuration des chemins SSL [page 132]

40PUBLICPUBLIQUE


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)

RemarqueFor 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]


PUBLICPUBLIQUE 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.


42PUBLICPUBLIQUE



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.


PUBLICPUBLIQUE 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]

44PUBLICPUBLIQUE



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.


PUBLICPUBLIQUE 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.xml

Access Server AS.key located in the same directory as AS.xml

Adapter SDK <DS_COMMON_DIR>/adapters/adapter.key

DSConfig.txt <DS_COMMON_DIR>/conf/DSConfig.key

Data 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.

AttentionFor 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.

46PUBLICPUBLIQUE


ExempleYou 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 225]

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.

AttentionAlthough 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.



PUBLICPUBLIQUE 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].

AttentionAlthough 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.

48PUBLICPUBLIQUE


Exemple○ 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]


PUBLICPUBLIQUE 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]

50PUBLICPUBLIQUE

Guide d'administrationUser 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.

RemarqueApplication 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.

Exemple● 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.


PUBLICPUBLIQUE 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.

RemarqueThe 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.

52PUBLICPUBLIQUE


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 configura-tions

Manage adapter configurations X

Manage batch job history X X

Manage central repository groups X

Manage certification log configura-tions

Manage datastore and substitution param configurations

Manage Object Promotion Configu-rations

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 configura-tions

X X


PUBLICPUBLIQUE 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 configura-tion

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

RemarqueApplication 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]

54PUBLICPUBLIQUE


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.


PUBLICPUBLIQUE 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]

56PUBLICPUBLIQUE


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.

Guide d'administrationRepository management

PUBLICPUBLIQUE 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

RemarqueIf 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.

RemarqueIf 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.

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

58PUBLICPUBLIQUE


Option Description

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 118]● 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]Utilisation du Gestionnaire de connexions [page 89]


PUBLICPUBLIQUE 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 118].

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.

RemarqueFor 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.

60PUBLICPUBLIQUE


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.

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

RemarqueIf 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]


PUBLICPUBLIQUE 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.

RemarqueTo 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]

62PUBLICPUBLIQUE


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.

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


PUBLICPUBLIQUE 63

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.

ConseilTo 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

Replicate content X

64PUBLICPUBLIQUE


Repository right Full control View

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.

RemarqueApplication 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.

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.


PUBLICPUBLIQUE 65

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>.

RemarqueFor 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 67]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]


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]

66PUBLICPUBLIQUE



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

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.

RemarqueUse 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 67].

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


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

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


PUBLICPUBLIQUE 67

https://help.sap.com/viewer/aad3428705d9497daed23eca43e0dab9/4.2.14/fr-FR/573eaf9f6d6d1014b3fc9283b0e91070.html

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.

RemarqueSelect 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]


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

68PUBLICPUBLIQUE


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

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 67].

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.

RemarqueThese 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.

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>)))


PUBLICPUBLIQUE 69

Option Description

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.

Exemple(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 67].

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

RemarqueThe 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 lan

guage-neutral.

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

SSL TrustStore Password Enter the TrustStore password.

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

RemarqueThe SSL KeyStore holds the identity key for the server.

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

70PUBLICPUBLIQUE


Option Description

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 67]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.

RemarqueEnsure 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


PUBLICPUBLIQUE 71

https://help.sap.com/viewer/aad3428705d9497daed23eca43e0dab9/4.2.14/fr-FR/573eaf9f6d6d1014b3fc9283b0e91070.html

RemarqueMake 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

RemarqueFor 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).

RemarqueIf 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].

Configuration de SSL/TLS dans la CMC pour SAP HANA [page 72]Pour configurer votre référentiel SAP HANA pour protocole SSL/TLS, définissez les options requises dans la Central Management Console (CMC) lorsque vous enregistrez le référentiel.

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]

5.5.1 Configuration de SSL/TLS dans la CMC pour SAP HANA

Pour configurer votre référentiel SAP HANA pour protocole SSL/TLS, définissez les options requises dans la Central Management Console (CMC) lorsque vous enregistrez le référentiel.

Assurez-vous d’exécuter les étapes décrites dans SAP HANA SSL/TLS protocol for repositories [page 71]. Puis suivez le processus d'enregistrement du référentiel dans la CMC en suivant les étapes décrites dans

72PUBLICPUBLIQUE


Registering a repository in the CMC [page 60]. Au cours de ce processus, définissez les options SSL/TLS comme décrit dans les étapes suivantes.

RemarqueLa CMC ne prend pas en charge une connexion avec DSN lors de l'activation du protocole SSL/TLS.

1. Dans laboîte de dialogue CMC Ajouter référentiel Data Services, sélectionnez Oui dans la liste déroulante Activer SSL.

2. Sélectionnez Oui dans la liste déroulante Vérifier le certificat de serveur.

La CMC active les options liées à SSL.3. Saisissez une valeur pour Remplacer le nom d'hôte, le cas échéant.4. Complétez les autres options SSL/TLS de SAP HANA comme indiqué dans le tableau suivant :

Descriptions d’option SSL/TLS

Option Valeur

Keystore SSL Entrez l'emplacement du Keystore SSL.

RemarqueVeillez à ce que la CMC puisse accéder au keystore :○ Windows : Localisez le keystore dans un pilote lo

cal○ Unix/Linux : Le site n'est pas important tant que

la CMC peut accéder au dossier.

Type de keystore SSL Sélectionnez le type de format de fichier du keystore dans la liste déroulante :○ JKS○ PKCS12

Mot de passe du keystore SSL Saisissez le mot de passe pour accéder à la clé privée dans le fichier keystore indiqué, le cas échéant.

Fchier de stockage sécurisé SSL Entrez l'emplacement du fichier de stockage sécurisé SSL.

Type de fichier de stockage sécurisé SSL Sélectionnez le type de format de fichier de stockage sécurisé TrustStore SSL applicable dans la liste déroulante :○ JKS○ PKCS12

Sans tenir compte de votre sélection pour cette option, vous devez traiter le fichier java.security fichier comme décrit dans Editing the java.security file [page 74].

Mot de passe du fichier de stockage sécurisé SSL Saisissez le mot de passe pour accéder à la clé privée du fichier de stockage sécurisé SSL, le cas échéant.

5. Testez la connexion. Lorsque le test de connexion du référentiel est réussi, cliquez sur Sauvegarder.

La CMC ajoute le nouveau référentiel au nœud Référentiel sur la page CMC Data Services.


PUBLICPUBLIQUE 73

Présentation des tâches : SAP HANA SSL/TLS protocol for repositories [page 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.

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.

74PUBLICPUBLIQUE


RemarqueThe 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]


PUBLICPUBLIQUE 75

6 Gestion des serveurs

Gérez le Job Server et les serveurs de base de données à l'aide d'outils de gestion de serveur, puis configurez les pilotes ODBC, les connexions avec nom de sources de données (DSN) et les connexions avec nom de serveur (sans DSN).

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

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

Lancer les services automatiquement pour Windows and Unix [page 81]Pour être exécuté correctement, SAP Data Services requiert le service de jobs et les services associés, ainsi que le service Tomcat fourni.

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

Configuration de la connectivité de la base de données pour UNIX et Linux [page 87]Chaque fois que vous ajoutez un type de base de données ODBC pour le traitement SAP Data Services, configurez un pilote pris en charge dans le Gestionnaire de connexions SAP Data Services (DS) pour établir une connexion à la base de données.

Using the ODBC Drivers Selector for Windows [page 113]To configure an ODBC driver on the Windows platform, use the SAP Data Services ODBC Drivers Selector utility.

Using the License Manager [page 114]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 [page 115]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 [page 124]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 [page 135]SAP Information Steward uses the Metadata Browsing Service and the View Data Service to connect to and view data in profiling sources.

Paramètres de l'application CMC de Data Services [page 139]Vous pouvez modifier les paramètres suivants de l'application Data Services dans la Central Management Console (CMC).

76PUBLICPUBLIQUE

Guide d'administrationGestion des serveurs

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.

RestrictionTo 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


PUBLICPUBLIQUE 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: Gestion des serveurs [page 76]


Setting UNIX environment variables [page 79]Lancer les services automatiquement pour Windows and Unix [page 81]History retention and Job Server log retention [page 83]Configuration de la connectivité de la base de données pour UNIX et Linux [page 87]Using the ODBC Drivers Selector for Windows [page 113]Using the License Manager [page 114]Use the Server Manager on Windows [page 115]Using the Server Manager on UNIX systems [page 124]

78PUBLICPUBLIQUE



Configuring Metadata Browsing Service and View Data Service [page 135]Paramètres de l'application CMC de Data Services [page 139]

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.

Exemple

$ 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.


PUBLICPUBLIQUE 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.

RemarqueFor 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.

ConseilUse 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.

80PUBLICPUBLIQUE


ConseilTo 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]Lancer les services automatiquement pour Windows and Unix [page 81]History retention and Job Server log retention [page 83]Configuration de la connectivité de la base de données pour UNIX et Linux [page 87]Using the ODBC Drivers Selector for Windows [page 113]Using the License Manager [page 114]Use the Server Manager on Windows [page 115]Using the Server Manager on UNIX systems [page 124]Configuring Metadata Browsing Service and View Data Service [page 135]Paramètres de l'application CMC de Data Services [page 139]

6.3 Lancer les services automatiquement pour Windows and Unix

Pour être exécuté correctement, SAP Data Services requiert le service de jobs et les services associés, ainsi que le service Tomcat fourni.

Certaines configurations de Data Services requièrent l'arrêt des services. Les services s'arrêtent également lorsque vous fermez Data Services. Dans certains cas, vous devez relancer les services manuellement. Sinon, Data Services relance automatiquement les services.

Sous Windows

Le service Data Services et le service Tomcat fourni démarrent automatiquement lorsque vous démarrez ou redémarrez votre ordinateur. Le service Data Services démarre les Job Servers et les serveurs d'accès sur l'ordinateur qui a redémarré.

Le cas échéant, vous pouvez modifier le démarrage du service et le définir sur Manuel dans la fenêtre des services Windows.


PUBLICPUBLIQUE 81

RemarquePour vous connecter manuellement aux applications Web, reportez-vous à la section « Configuration du suivi pour applications Web » du Guide d'administration de services de plateforme d'informations..

Sous UNIX

Pour démarrer automatiquement les Job Servers et les serveurs d'accès lors du redémarrage du serveur, installez le script actaservices avec des droits racine. Data Services stocke le fichier de script dans $LINK_DIR/bin.

Appelez le script en utilisant la syntaxe prise en charge par votre environnement.

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

Rubrique parent : Gestion des serveurs [page 76]


DSN-less and TNS-less connections [page 77]Setting UNIX environment variables [page 79]History retention and Job Server log retention [page 83]Configuration de la connectivité de la base de données pour UNIX et Linux [page 87]Using the ODBC Drivers Selector for Windows [page 113]Using the License Manager [page 114]Use the Server Manager on Windows [page 115]Using the Server Manager on UNIX systems [page 124]Configuring Metadata Browsing Service and View Data Service [page 135]Paramètres de l'application CMC de Data Services [page 139]

82PUBLICPUBLIQUE


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.

ConseilTo 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.

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.

AttentionYou 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]Lancer les services automatiquement pour Windows and Unix [page 81]Configuration de la connectivité de la base de données pour UNIX et Linux [page 87]


PUBLICPUBLIQUE 83

Using the ODBC Drivers Selector for Windows [page 113]Using the License Manager [page 114]Use the Server Manager on Windows [page 115]Using the Server Manager on UNIX systems [page 124]Configuring Metadata Browsing Service and View Data Service [page 135]Paramètres de l'application CMC de Data Services [page 139]

Deleting batch job history data [page 147]Monitoring jobs [page 142]

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.

ExempleFor 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.

AttentionMany 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 83]

84PUBLICPUBLIQUE



Setting the History Retention Period [page 85]Setting the Job Server Log Retention Period [page 86]

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.

ExempleThe 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 83]


USPS-required log files and reports [page 84]Setting the Job Server Log Retention Period [page 86]


PUBLICPUBLIQUE 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.

ExempleThe 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 83]


USPS-required log files and reports [page 84]Setting the History Retention Period [page 85]

86PUBLICPUBLIQUE


6.5 Configuration de la connectivité de la base de données pour UNIX et Linux

Chaque fois que vous ajoutez un type de base de données ODBC pour le traitement SAP Data Services, configurez un pilote pris en charge dans le Gestionnaire de connexions SAP Data Services (DS) pour établir une connexion à la base de données.

Bien que les informations requises soient similaires, les processus de configuration d'un pilote ODBC sur les systèmes d'exploitation UNIX et Linux sont différents de ceux des systèmes d'exploitation Windows. Par exemple, pour configurer des pilotes ODBC installés dans UNIX et Linux, vous utilisez le Gestionnaire de connexions SAP Data Services. Sous Windows, utilisez l'Administrateur de source de données ODBC Microsoft pour les connexions avec nom de source de données (DSN) ou le sélecteur de pilotes ODBC pour les connexions avec nom de serveur (sans DNS).

Configurez une connexion DSN en même temps que vous configurez le pilote. Pour une connexion DSN, vous avez besoin d'informations sur la source de données, notamment les informations sur le serveur, le nom d'utilisateur et le mot de passe. Le cas échéant, configurez SSL/TLS pour le transfert sécurisé des données.

Connexion à la base de données pour UNIX et Linux [page 88]Pour configurer la connectivité de la base de données sur les plateformes UNIX ou Linux, utilisez le Gestionnaire de connexions SAP Data Services (DS).

Utilisation du Gestionnaire de connexions [page 89]Le Gestionnaire de connexions SAP Data Services est un utilitaire de ligne de commande qui ajoute les informations du pilote ODBC aux fichiers de la bibliothèque du pilote SAP Data Services.

Configuration de pilotes à l'aide de connexions avec nom de serveur (sans DNS) [page 90]Sur les plateformes UNIX et Linux, SAP Data Services requiert que les informations du pilote ODBC soient incluses dans la bibliothèque de pilotes ODBC lorsque vous configurez le pilote pour une connexion sans DSN.

Configuration des pilotes avec des connexions avec nom de source de données (DSN). [page 95]Sur les plateformes Linux et Unix, SAP Data Services exige que les informations du pilote ODBC avec une connexion avec nom de source de données (DSN) soient incluses dans la bibliothèque du gestionnaire de pilotes ODBC et dans la bibliothèque de pilotes ODBC.

Configuration d'ODBC DataDirect [page 104]Le pilote DataDirect est inclus avec votre installation SAP Data Services pour être utilisé avec les bases de données applicables telles que Microsoft SQL Server ou DB2 sur zSeries ou iSeries.



DSN-less and TNS-less connections [page 77]Setting UNIX environment variables [page 79]Lancer les services automatiquement pour Windows and Unix [page 81]History retention and Job Server log retention [page 83]Using the ODBC Drivers Selector for Windows [page 113]


PUBLICPUBLIQUE 87

Using the License Manager [page 114]Use the Server Manager on Windows [page 115]Using the Server Manager on UNIX systems [page 124]Configuring Metadata Browsing Service and View Data Service [page 135]Paramètres de l'application CMC de Data Services [page 139]

SSL or TLS for Data Services components [page 31]

6.5.1 Connexion à la base de données pour UNIX et Linux

Pour configurer la connectivité de la base de données sur les plateformes UNIX ou Linux, utilisez le Gestionnaire de connexions SAP Data Services (DS).

Utilisez le Gestionnaire de connexions DS pour configurer les pilotes ODBC et créer des connexions DSN. Le gestionnaire de connexions DS ajoute les informations du pilote au fichier odbcinst.ini et les informations DSN au fichier ds_odbc.ini. Le fichier ds_odbc.ini répertorie le DSN avec le nom du pilote ODBC.

Le programme d'installation définit les connexions sans DSN

Lorsque vous installez Data Services sous UNIX ou Linux, vous pouvez choisir d'utiliser le programme d'installation de SAP Data Services pour configurer le référentiel. Pour que le programme d'installation configure le référentiel, saisissez le type de base de données pour le référentiel. Par défaut, le programme d'installation effectue automatiquement les tâches suivantes de base de données du référentiel :

● Établit la connectivité de la base de données pour le type de base de données indiqué.● Crée un nom de serveur connexion (sans DSN).

Si vous voulez utiliser une connexion avec DSN ou TNS (pour Oracle) pour votre référentiel, ignorez la création de référentiel lors de l'installation.

Configuration de la connexion à la base de données du référentiel après l'installation

Utilisez le Gestionnaire de connexions DS après l'installation pour configurer la base de données du référentiel et établir une connexion DSN ou TNS (Oracle). De plus, utilisez le Gestionnaire de connexions DS pour ajouter des bases de données supplémentaires et des connexions DSN à Data Services.

Exécutez les tâches suivantes dans le Gestionnaire de connexions :

● Ajoutez des informations sur le pilote ODBC, notamment l'emplacement du gestionnaire de pilotes et le nom du pilote.

● Ajoutez des informations sur une connexion DSN, notamment un nom pour la source de données, les informations sur le serveur et les noms et mots de passe des utilisateurs concernés.

Data Services inclut le gestionnaire de connexions DS dans l'installation et le place par défaut à l'emplacement suivant : $LINK_DIR//bin/DSConnectionManager.sh.

88PUBLICPUBLIQUE


Voir la Product Availability Matrix (PAM) disponible sur le SAP Support Portal pour obtenir une liste des bases de données et versions prises en charge que vous pouvez utiliser pour votre référentiel. La PAM inclut également des bases de données et versions sans référentiel prises en charge dans Data Services, en plus des pilotes ODBC applicables.

Rubrique parent : Configuration de la connectivité de la base de données pour UNIX et Linux [page 87]


Utilisation du Gestionnaire de connexions [page 89]Configuration de pilotes à l'aide de connexions avec nom de serveur (sans DNS) [page 90]Configuration des pilotes avec des connexions avec nom de source de données (DSN). [page 95]Configuration d'ODBC DataDirect [page 104]

6.5.2 Utilisation du Gestionnaire de connexions

Le Gestionnaire de connexions SAP Data Services est un utilitaire de ligne de commande qui ajoute les informations du pilote ODBC aux fichiers de la bibliothèque du pilote SAP Data Services.

Avant d'exécuter le Gestionnaire de connexions pour configurer le pilote ODBC pour une base de données, réalisez les tâches suivantes :

● Vérifiez la Product Availability Matrix (PAM) pour déterminer le pilote ODBC et la version pour le type de base de données applicable.

● Téléchargez et installez le pilote ODBC pris en charge et lisez toutes les informations relatives au pilote dans la documentation du fournisseur pour vous assurer de configurer le pilote correctement.

● Facultatif. Pour utiliser l'interface utilisateur graphique du Gestionnaire de connexions, installez la bibliothèque GTK+2. Le GTK+2 est une boîte à outils multi-plateformes libre qui crée des interfaces utilisateur. Pour d'autres informations sur l'obtention et l'installation de GTK+2, voir https://www.gtk.org/

.

Le Gestionnaire de connexions définit le pilote ODBC et les informations DSN dans les fichiers du gestionnaire de pilotes SAP Data Services comme suit :

● Le Gestionnaire de connexions ajoute les informations du pilote au fichier odbcinst.ini, y compris le nom et l'emplacement du fichier pilote du client du fournisseur. L'emplacement fournisseur doit être accessible en lecture et écriture.

ExempleL'emplacement par défaut pour les pilotes DataDirect est $ LINK_DIR/DataDirect/odbc/. Par conséquent, définissez l'emplacement suivant lorsque le Gestionnaire de connexions demande les informations :

Specify the Driver: /$LINK_DIR/DataDirect/odbc/<name_of_driver_file>


PUBLICPUBLIQUE 89



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


● Le Gestionnaire de connexions ajoute les informations DSN au fichier ds_odbc.ini.

Les instructions suivantes partent du principe que vous disposez d'une interface utilisateur pour le Gestionnaire de connexions.

1. Ouvrez le Gestionnaire de connexions à l'aide de la commande suivante, en remplaçant $LINK_DIR par le chemin d'accès réel au répertoire d'installation de Data Services :

$ cd $LINK_DIR/bin/DSConnectionManager.sh

Le Gestionnaire de connexions s'ouvre.2. Pour les connexions avec DSN et connexions avec nom de serveur (sans DNS), ouvrez l'onglet Pilotes pour

configurer le pilote ODBC pour la base de données.

Les options de l'onglet Pilotes peuvent différer en fonction du type de pilote.3. Pour les connexions DSN, ouvrez l'onglet Sources de données, puis configurez la connexion au nom de

source de données.

Les options de l'onglet Sources de données diffèrent en fonction du type de base de données.4. Cliquez sur Redémarrer les services pour redémarrer le Service de traitement adaptatif EIM et le Service de

jobs Data Services.

Présentation des tâches : Configuration de la connectivité de la base de données pour UNIX et Linux [page 87]


Connexion à la base de données pour UNIX et Linux [page 88]Configuration de pilotes à l'aide de connexions avec nom de serveur (sans DNS) [page 90]Configuration des pilotes avec des connexions avec nom de source de données (DSN). [page 95]Configuration d'ODBC DataDirect [page 104]

6.5.3 Configuration de pilotes à l'aide de connexions avec nom de serveur (sans DNS)

Sur les plateformes UNIX et Linux, SAP Data Services requiert que les informations du pilote ODBC soient incluses dans la bibliothèque de pilotes ODBC lorsque vous configurez le pilote pour une connexion sans DSN.

Le fichier de configuration du pilote ODBC UNIX contient des noms de pilotes se référant à des bibliothèques de pilotes ODBC. La configuration du pilote ODBC UNIX est un fichier d’instance référencé par la variable $ODBCINST.

Lorsque vous configurez le pilote ODBC pour les bases de données prises en charge de manière native dans le Gestionnaire de connexions SAP Data Services (DS), le gestionnaire de connexions DS met automatiquement à jour les fichiers de la bibliothèque de pilote ODBC dans $ODBCINST.

Configuration de pilotes ODBC natifs pour UNIX et Linux [page 91]

90PUBLICPUBLIQUE


Configurez les pilotes ODBC pour UNIX et Linux ayant une connexion avec nom de serveur (sans DNS) en utilisant le Gestionnaire de connexions SAP Data Services (DS).

Properties for server name connections [page 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.



Connexion à la base de données pour UNIX et Linux [page 88]Utilisation du Gestionnaire de connexions [page 89]Configuration des pilotes avec des connexions avec nom de source de données (DSN). [page 95]Configuration d'ODBC DataDirect [page 104]

Setting UNIX environment variables [page 79]

6.5.3.1 Configuration de pilotes ODBC natifs pour UNIX et Linux

Configurez les pilotes ODBC pour UNIX et Linux ayant une connexion avec nom de serveur (sans DNS) en utilisant le Gestionnaire de connexions SAP Data Services (DS).

N'oubliez pas d'effectuer les tâches préalables suivantes avant de configurer le pilote natif ODBC :

● Configurez la bibliothèque de pilotes ODBC et les variables d'environnement associées pour le client de base de données. Pour de plus amples instructions, voir Setting UNIX environment variables [page 79].

● Assurez-vous que la base de données est admissible pour une connexion avec nom de serveur. Pour une liste complète des bases de données et connexions prises en charge, voir la Product Availability Matrix (PAM).

● Facultatif. Installez la bibliothèque GTK+2 pour travailler dans l'interface utilisateur graphique (GUI) pour le gestionnaire de connexions DS. Pour obtenir des instructions de téléchargement, voir Utilisation du Gestionnaire de connexions [page 89].

Les étapes suivantes concernent la version GUI du gestionnaire de connexions DS.

1. Ouvrez le Gestionnaire de connexions à l’aide de la commande suivante :

$ cd $LINK_DIR/bin/DSConnectionManager

2. Ouvrez l'onglet Sources de données et cliquez sur Ajouter.3. Sélectionnez le type de base de données dans la boîte de dialogue Sélectionner le type de base de données,

puis cliquez sur OK.

La boîte de dialogue Configuration pour... apparaît avec la valeur renseignée pour l’option Fichier Inst ODBC.


PUBLICPUBLIQUE 91



4. Saisissez les informations relatives au pilote et au serveur de base de données.

Indiquez les valeurs pour les propriétés de serveur suivantes :○ Nom du serveur○ Port (le cas échéant)○ Base de données (le cas échéant)○ Nom d'utilisateur○ Mot de passe

RemarqueLe Gestionnaire de connexions n’enregistre pas les valeurs que vous saisissez pour une utilisation ultérieure.

5. Testez la connexion en cliquant sur Tester la connexion.6. Lorsque le test de connexion est réussi, cliquez sur Enregistrer.

Le Gestionnaire de connexions redémarre le Service de traitement adaptatif EIM et/ou le Service de jobs Data Services dans les circonstances suivantes :○ Si vous avez installé Data Services sur le même ordinateur et dans le même dossier que les services de

plateforme d'informations (IPS) ou la plateforme de BI, le Gestionnaire de connexions DS redémarre le Service de traitement adaptatif EIM et le Service de jobs Data Services.

RemarqueEntrez le mot de passe du Central Management Server (CMS) lorsque vous y êtes invité.

○ Si vous avez installé Data Services sur un autre ordinateur que IPS ou la plateforme de BI, le Gestionnaire de connexions redémarre le Service de jobs Data Services.

Présentation des tâches : Configuration de pilotes à l'aide de connexions avec nom de serveur (sans DNS) [page 90]


Properties for server name connections [page 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.

92PUBLICPUBLIQUE


RemarqueWe 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

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


PUBLICPUBLIQUE 93


Netezza ● ODBC Inst File● Driver Version● Driver Name● Driver● Server Name● Port● Database● User Name● Password

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

94PUBLICPUBLIQUE



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

Parent topic: Configuration de pilotes à l'aide de connexions avec nom de serveur (sans DNS) [page 90]


Configuration de pilotes ODBC natifs pour UNIX et Linux [page 91]

6.5.4 Configuration des pilotes avec des connexions avec nom de source de données (DSN).

Sur les plateformes Linux et Unix, SAP Data Services exige que les informations du pilote ODBC avec une connexion avec nom de source de données (DSN) soient incluses dans la bibliothèque du gestionnaire de pilotes ODBC et dans la bibliothèque de pilotes ODBC.

Certains fournisseurs de pilotes ODBC incluent des fonctionnalités de gestionnaire de pilotes ODBC et de pilote ODCB dans une seule bibliothèque, alors que d'autres les séparent en deux bibliothèques. Pour s'adapter à tous les fournisseurs ODBC, Data Services requiert des configurations dans deux bibliothèques différentes pour les connexions DSN :

● Fichier de configuration du pilote ODBC pour Unix, référencé par la variable d'environnement $ODBCINST : Contient des instances DSN qui référencent les bibliothèques de gestionnaire de pilotes ODBC. L'emplacement par défaut est $LINK_DIR/bin/ds_odbc.ini.

ConseilPour les bases de données ODBC que Data Services prend en charge nativement, ne configurez pas le fichier ds_odbc.ini manuellement. À la place, configurez le pilote à l'aide du gestionnaire de


PUBLICPUBLIQUE 95

connexions SAP Data Services (DS) pour ajouter automatiquement les informations à la bibliothèque de gestionnaires de pilotes ODBC Unix.

● Fichiers de configuration du fournisseur ODBC référencés par la variable d'environnement $ODBCINI : Contient des instances de nom de source de données (DSN) référençant les bibliothèques de pilotes ODBC et les informations de connexion au serveur de base de données.

RemarqueUn fichier de configuration ODBC peut contenir plusieurs instances DSN. Un fichier référencé par $ODBCINI peut contenir des DSN pour MySQL, Netezza et Teradata, par exemple.

Sources de données ODBC natives [page 96]SAP Data Services prend en charge plusieurs sources de données ODBC de manière native avec des connexions DSN.

Configuring ODBC data sources [page 97]To configure ODBC data sources in Linux or UNIX, use the SAP Data Services Connection Manager.

Properties for ODBC data sources using DSN connections [page 98]The Connection Manager configures the $ODBCINI file based on the property values that you enter on the Data Sources tab.

Troubleshooting [page 103]Configuring drivers can be troublesome for a variety of reasons.



Connexion à la base de données pour UNIX et Linux [page 88]Utilisation du Gestionnaire de connexions [page 89]Configuration de pilotes à l'aide de connexions avec nom de serveur (sans DNS) [page 90]Configuration d'ODBC DataDirect [page 104]

6.5.4.1 Sources de données ODBC natives

SAP Data Services prend en charge plusieurs sources de données ODBC de manière native avec des connexions DSN.

Pour des sources de données ODBC natives, configurez le pilote et la source de données à l'aide du Gestionnaire de connexions SAP Data Services. Définissez la configuration ODBC Data Services et les variables d'environnement associées. Des sources de données ODBC autres que des sources de données natives requièrent une configuration manuelle supplémentaire.

96PUBLICPUBLIQUE


RemarquePour obtenir la toute dernière liste des types de bases de données que prend en charge le Gestionnaire de connexions, voir la Product Availability Matrix (PAM) sur le SAP Support Portal.

Entrez des valeurs dans le Gestionnaire de connexions pour définir le $ODBCINI sur un fichier qui contient la connexion DSN. Avant d'exécuter le Gestionnaire de connexions, assurez-vous que le fichier est accessible en lecture et écriture à l'aide de la commande suivante :

export ODBCINI=<dir-path>/ds_odbc.ini touch $ODBCINI

Rubrique parent : Configuration des pilotes avec des connexions avec nom de source de données (DSN). [page 95]


Configuring ODBC data sources [page 97]Properties for ODBC data sources using DSN connections [page 98]Troubleshooting [page 103]

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.

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


PUBLICPUBLIQUE 97



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

RemarqueThe 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: Configuration des pilotes avec des connexions avec nom de source de données (DSN). [page 95]


Sources de données ODBC natives [page 96]Properties for ODBC data sources using DSN connections [page 98]Troubleshooting [page 103]

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.

RemarqueWe add support for additional database types on a regular basis. Therefore, the following table may not be up-to-date.

98PUBLICPUBLIQUE


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]

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


PUBLICPUBLIQUE 99


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

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

100PUBLICPUBLIQUE



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

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


PUBLICPUBLIQUE 101


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

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

102PUBLICPUBLIQUE


Parent topic: Configuration des pilotes avec des connexions avec nom de source de données (DSN). [page 95]


Sources de données ODBC natives [page 96]Configuring ODBC data sources [page 97]Troubleshooting [page 103]

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.

Exemple

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.

Exemple

$LINK_DIR/bin/DSConnectionManager.sh -c -d

The log file path is $LINK_DIR/log/DSConnectionManager.log.

Possible errors include the following:


PUBLICPUBLIQUE 103

● The Connection Manager can't connect to database.● The Data Services Job Server can't connect to database.

Parent topic: Configuration des pilotes avec des connexions avec nom de source de données (DSN). [page 95]


Sources de données ODBC natives [page 96]Configuring ODBC data sources [page 97]Properties for ODBC data sources using DSN connections [page 98]

6.5.5 Configuration d'ODBC DataDirect

Le pilote DataDirect est inclus avec votre installation SAP Data Services pour être utilisé avec les bases de données applicables telles que Microsoft SQL Server ou DB2 sur zSeries ou iSeries.

Avant de configurer manuellement le pilote ODBC DataDirect pour votre base de données, vérifiez que les points suivants sont bien respectés :

● Assurez-vous de disposer de l'autorisation permettant de modifier les fichiers odbc.ini et odbcinst.ini.

● Déterminez la version applicable de DataDirect et celle de la base de données en consultant la dernière Product Availability Matrix (PAM) sur le portail SAP Customer.

● Envisagez d'utiliser le Gestionnaire de connexions SAP Data Services (DS) pour ajouter automatiquement les informations du pilote et de la source de données aux fichiers .ini dans $ODBCINI et $ODBCINST.

Pour configurer manuellement le pilote DataDirect ODBC pour le type de base de données applicable sur une plateforme Linux ou Unix, réalisez les étapes suivantes :

1. Ouvrez le fichier ds_odbc.ini dans un éditeur de texte.

Le fichier est situé dans $LINK_DIR/bin/ds_odbc.ini.

2. Ajoutez le nom de la source de données entre crochets.Pour Microsoft SQL Server :

[test_Microsoft_SQL_SERVER]

Pour DB2 sur zSeries ou iSeries :

[test_DB2] 3. Ajoutez l'emplacement d'installation de la clé pilote.

Pour Microsoft SQL Server :

[test_Microsoft_SQL_SERVER] Driver = <install_location>/lib/[DA][DD]sqls<xx>.so où <install_location> est l'emplacement du pilote ODBC DataDirect.

104PUBLICPUBLIQUE




[test_DB2] Driver = <install_location>/lib/[DA][DD]db2<xx>.so où <install_location> est l'emplacement du pilote ODBC DataDirect.

Remarque

4. Ajoutez une valeur pour RebrandedLib =.

Une valeur Rebranded Library est requise lorsque vous utilisez le pilote DataDirect renommé SAP.

Pour Microsoft SQL Server :

[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. Ajoutez la source de données au fichier de configuration du fournisseur ODBC référencé par la variable Unix $ODBCINI.

RemarqueLe numéro de version et les noms de fichier du pilote sont susceptibles d'être modifiés avec chaque version. Accédez à $REP_LIENS/DataDirect/odbc/odbc.ini pour afficher les informations de la version en cours.

RemarqueEnableQuotedIdentifiers = 1 est requis pour Microsoft SQL Server.

Pour Microsoft SQL Server, les invites sont en gras à titre d'illustration :

[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 <install_location> est l'emplacement du pilote ODBC DataDirect.


PUBLICPUBLIQUE 105


[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 WithHold=1 XMLDescribeType=-10

<install_location> est l'emplacement du pilote ODBC DataDirect.

6. Exécutez le script $REP_LIENS/DataDirect/odbc/odbc.sh pour ajouter les paramètres d'environnement à la session exécutant le service de jobs.

Exemple de fichier de configuration du gestionnaire de pilotes pour la connexion DSN [page 107]Chaque pilote ODBC utilisé contient des informations dans les fichiers de la bibliothèque du pilote, qui sont modifiables uniquement par les utilisateurs autorisés.

Présentation des tâches : Configuration de la connectivité de la base de données pour UNIX et Linux [page 87]


Connexion à la base de données pour UNIX et Linux [page 88]Utilisation du Gestionnaire de connexions [page 89]Configuration de pilotes à l'aide de connexions avec nom de serveur (sans DNS) [page 90]

106PUBLICPUBLIQUE


Configuration des pilotes avec des connexions avec nom de source de données (DSN). [page 95]

6.5.5.1 Exemple de fichier de configuration du gestionnaire de pilotes pour la connexion DSN

Chaque pilote ODBC utilisé contient des informations dans les fichiers de la bibliothèque du pilote, qui sont modifiables uniquement par les utilisateurs autorisés.

Lorsque vous ajoutez un nom de source de données, mettez les noms entre crochets ([]). Saisissez les propriétés de source de données dans les lignes suivantes au format suivant : PropertyName = PropertyValue.

Exemple

[test_source] Driver = /path/to/driverOdbcConformanceLevel = LazyLoading = ODBC64SqlHandleSize = ODBC64SqlLenSize = DriverUnicodeType =

La source de données dans cet exemple est [test_source], qui peut être chargé à l'aide du fichier de bibliothèque du pilote spécifié. SAP Data Services utilise des valeurs par défaut lorsque vous laissez des propriétés facultatives vides.

Suivez ces directives lorsque vous modifiez le fichier ODBC Data Services nommé <LINK_DIR>/bin/ds_odbc.ini :

● Définissez au moins une propriété de pilote pour chaque nom de source de données. Une propriété de pilote permet au gestionnaire de pilotes de charger le pilote lorsqu'il se connecte à la base de données.

● Commencez toute ligne de commentaire par un signe dièse (#) comme premier caractère pour désigner un commentaire.

● Data Services ignore tous les blancs en début ou en fin de noms de sources de données et de propriétés.

Le tableau suivant contient des paramètres de configuration de la source de données (clés) dans ds_odbc.ini, si la clé est nécessaire, la description de valeur valide et un exemple.


PUBLICPUBLIQUE 107

Descriptions des clés du fichier de configuration de source de données

Clé Requise Valeur valide Exemple

Driver Oui Le chemin d'accès complet et le nom de la bibliothèque pour la bibliothèque de pilotes ODBC. Le répertoire contenant les bibliothèques dépendantes doit se trouver dans le chemin de la bibliothèque partagée. Exemple :

● Pour AIX, LIBPATH● Pour Solaris ou Linux,

LD_LIBRARY_PATH

Vérifiez la documentation du fournisseur applicable pour le chemin d'accès à la bibliothèque partagée applicable.

Driver=/home/mysql/myodbc/lib/libmyodbc3_r.so

108PUBLICPUBLIQUE



OdbcConformanceLevel

Non Une valeur décimale indiquant le niveau de compatibilité ODBC du pilote.

La valeur par défaut est 0. Avec une option dont la valeur est 0, le pilote détecte le niveau de conformité en chargeant les fonctions API pour le niveau de conformité 2.x, puis en chargeant les fonctions API pour le niveau de conformité 3.x.

S'il existe une valeur égale ou supérieure à 4.0, le gestionnaire de pilotes imprime une erreur d'exécution.

RemarqueUn pilote ODBC peut être compatible avec 2.x, 3.x ou bien les deux. Le gestionnaire de pilotes ODBC UNIX détecte si le pilote est compatible avec 2.x ou 3.x et charge les fonctions API ODBC compatibles respectives. Si le pilote est compatible à la fois avec 2.x et 3.x, le pilote charge uniquement l'API ODBC 2.x. Vous pouvez déroger à ce comportement en indiquant, par exemple, OdbcConformanceLevel = 3.0. Ainsi, le gestionnaire de pilotes ODBC charge uniquement les fonctions d'API ODBC 3.x.

OdbcConformanceLevel=0

OdbcConformanceLevel=3.0


PUBLICPUBLIQUE 109


LazyLoading Non Spécifie si le gestionnaire de pilotes ODBC UNIX charge le pilote ODBC et indique au système d'exploitation de charger toutes les bibliothèques dépendantes du pilote.

Indiquez TRUE pour Oui, ou FALSE pour Non. La valeur par défaut est FALSE.

L'indicateur LazyLoading est utile lorsque certaines bibliothèques dépendantes du pilote ODBC ne sont pas requises et que le fournisseur ODBC recommande de charger la bibliothèque en mode différé.

LazyLoading=TRUE

110PUBLICPUBLIQUE



ODBC64SqlHandleSize Oui, pour les plateformes 64 bit uniquement.

Spécifie la taille du descripteur ODBC.

Saisissez 32 ou 64.

Si vous laissez cette option vide, ou si vous définissez une valeur autre que 32 ou 64, Data Services utilise la valeur par défaut de 64.

La définition standard du type de données SQLHANDLE en ODBC 64 bits est un nombre entier de 64 bits. Toutefois, certains pilotes ODBC ne sont pas conformes à ce standard. Par conséquent, utilisez la clé ODBC64S1lHandleSize pour spécifier la taille réelle de SQLHANDLE.

Pour les pilotes ODBC DataDirect 64 bits, ignorez la clé ou définissez la valeur 64 car Data Direct 64 bits est conforme au standard. Pour d'autres pilotes ODBC de 64 bits, contactez votre fournisseur pour déterminer la taille réelle de SQLHANDLE.

RemarqueCette option est uniquement requise pour les plateformes de 64 bits.

ODBC64SqlHandleSize=64


PUBLICPUBLIQUE 111


ODBC64SqlLenSize Oui, pour les plateformes 64 bit uniquement.

Spécifie la taille de la longueur SQL du pilote ODBC.

Saisissez 32 ou 64.

Si vous laissez cette clé vide, ou si vous saisissez une valeur autre que 32 ou 64, Data Services utilise la valeur par défaut de 64.

La définition standard du type de données SQLLEN en ODBC 64 bits est un nombre entier de 64 bits. Toutefois, certains pilotes ODBC ne sont pas conformes à ce standard. Par conséquent, utilisez la clé ODBC64SqlLenSize pour spécifier la taille réelle de SQLLEN.

Comme les pilotes ODBC de 64 bits DataDirect se conforment à ce standard, ignorez ce paramètre ou définissez la clé sur 64 pour DataDirect. Pour d'autres pilotes ODBC de 64 bits, contactez votre fournisseur pour déterminer la taille réelle de SQLLEN.

RemarqueCette option est uniquement requise pour les plateformes 64 bits.

ODBC64SqlLenSize=64

112PUBLICPUBLIQUE



DriverUnicodeType Oui, pour les pilotes ODBC qui prennent uniquement en charge les fonctions W.

Spécifie le type Unicode du pilote ODBC.

Saisissez l'un des nombres entiers suivants :

● 1 : pour UTF16● 2 : Pour UTF8

Si vous laissez cette clé vide, ou si vous définissez une valeur autre que 1 ou 2, ou une valeur non détectable, Data Services utilise la valeur par défaut de 2.

Le pilote ODBC SQL Server DataDirect prend uniquement en charge les fonctions W ; spécifiez 2 pour ce pilote.

RemarqueCette option est uniquement requise pour les pilotes ODBC qui ne supportent que les fonctions W.

DriverUnicodeType=2

Rubrique parent : Configuration d'ODBC DataDirect [page 104]

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.


PUBLICPUBLIQUE 113

2. Find your database type and version under the Database version column.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”.

RemarqueThe 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: Gestion des serveurs [page 76]


DSN-less and TNS-less connections [page 77]Setting UNIX environment variables [page 79]Lancer les services automatiquement pour Windows and Unix [page 81]History retention and Job Server log retention [page 83]Configuration de la connectivité de la base de données pour UNIX et Linux [page 87]Using the License Manager [page 114]Use the Server Manager on Windows [page 115]Using the Server Manager on UNIX systems [page 124]Configuring Metadata Browsing Service and View Data Service [page 135]Paramètres de l'application CMC de Data Services [page 139]

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 Gestionnaire de licences [page 207].


114PUBLICPUBLIQUE



DSN-less and TNS-less connections [page 77]Setting UNIX environment variables [page 79]Lancer les services automatiquement pour Windows and Unix [page 81]History retention and Job Server log retention [page 83]Configuration de la connectivité de la base de données pour UNIX et Linux [page 87]Using the ODBC Drivers Selector for Windows [page 113]Use the Server Manager on Windows [page 115]Using the Server Manager on UNIX systems [page 124]Configuring Metadata Browsing Service and View Data Service [page 135]Paramètres de l'application CMC de Data Services [page 139]

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 116]Use the Data Services Server Manager to create and edit all types of Job Servers.

Configuring runtime resources [page 120]Configure runtime resources to control Job Server operations, such as pageable cache or parallel processes.

Configuration des serveurs d'accès [page 122]


PUBLICPUBLIQUE 115


Vérification de l'exécution des Job Servers et des serveurs d'accès [page 124]



DSN-less and TNS-less connections [page 77]Setting UNIX environment variables [page 79]Lancer les services automatiquement pour Windows and Unix [page 81]History retention and Job Server log retention [page 83]Configuration de la connectivité de la base de données pour UNIX et Linux [page 87]Using the ODBC Drivers Selector for Windows [page 113]Using the License Manager [page 114]Using the Server Manager on UNIX systems [page 124]Configuring Metadata Browsing Service and View Data Service [page 135]Paramètres de l'application CMC de Data Services [page 139]

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.

116PUBLICPUBLIQUE


RemarqueIf 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 117]When you open a Job Server, the Server Manager displays information about the Job Server.

Associating a Job Server to a repository [page 118]A repository must have a Job Server for moving data into and out of SAP Data Services.

Resynchronizing associated repositories [page 120]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 115]


Configuring runtime resources [page 120]Configuration des serveurs d'accès [page 122]Configuration des chemins SSL [page 123]Vérification de l'exécution des Job Servers et des serveurs d'accès [page 124]

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.


PUBLICPUBLIQUE 117

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 116]


Associating a Job Server to a repository [page 118]Resynchronizing associated repositories [page 120]

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.

118PUBLICPUBLIQUE


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.

RemarqueDon'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.

RestrictionYou 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 116]


Job Server properties [page 117]Resynchronizing associated repositories [page 120]


PUBLICPUBLIQUE 119

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 116]


Job Server properties [page 117]Associating a Job Server to a repository [page 118]

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.

120PUBLICPUBLIQUE


RemarqueFor 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.

RemarqueIf 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 115]


Configuring Job Servers [page 116]Configuration des serveurs d'accès [page 122]Configuration des chemins SSL [page 123]Vérification de l'exécution des Job Servers et des serveurs d'accès [page 124]Performance Optimization Guide: Caching dataReference Guide: Data_TransferPerformance Optimization Guide: Using grid computing to distribute data flows execution


PUBLICPUBLIQUE 121

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 Configuration des serveurs d'accès

Lors de la configuration de l'emplacement d'installation d'un serveur d'accès, SAP Data Services crée de l'espace pour les fichiers journaux du serveur d'accès.

1. Ouvrez le Gestionnaire de serveurs, cliquez sur l'onglet Serveur d'accès, puis sur Modifier.2. Sélectionnez une tâche de configuration à effectuer :

○ Pour ajouter un serveur d'accès, cliquez sur Ajouter.Poursuivez et effectuez les étapes de configuration restantes.

○ Pour modifier un serveur d'accès existant, sélectionnez le serveur d'accès et cliquez sur Modifier.Poursuivez et effectuez les étapes de configuration restantes.

○ Pour supprimer un serveur d'accès existant, sélectionnez le serveur d'accès et cliquez sur Supprimer.Aucune étape de configuration supplémentaire n'est requise.

3. Dans la fenêtre Propriétés du serveur d'accès, saisissez les informations de configuration du serveur d'accès et cliquez sur OK.

Propriété Description

Répertoire Spécifie l'emplacement des fichiers journaux pour cette instance du serveur d'accès. Cliquez sur le bouton points de suspension pour naviguer jusqu'au répertoire du journal sous le répertoire où le logiciel est installé.

Ne modifiez pas cette valeur après la configuration initiale.

Port de communication Spécifie le port de cet ordinateur que le serveur d'accès utilise pour écouter les messages entrants des clients.

Assurez-vous que ce numéro de port est inutilisé et unique pour chaque serveur d'accès.

Paramètres Spécifiez tout paramètre supplémentaire du serveur d'accès.

RemarqueIl est possible d'afficher les paramètres supplémentaires du serveur d'accès en entrant AL_AccessServer au niveau de la ligne de commande. Pour plus d'informations, consultez « Performance en temps réel » dans le guide Management Console Guide.

Utiliser le protocole SSL Active la sécurité SSL pour la messagerie instantanée sur ce serveur d'accès.

Activer le serveur d'accès Contrôle si le serveur d'accès démarre automatiquement au démarrage du service Data Services.

4. Cliquez sur OK pour retourner à la fenêtre Gestionnaire de serveurs.5. Cliquez sur Redémarrer pour redémarrer les services avec la configuration mise à jour.

Présentation des tâches : Use the Server Manager on Windows [page 115]

122PUBLICPUBLIQUE



Configuring Job Servers [page 116]Configuring runtime resources [page 120]Configuration des chemins SSL [page 123]Vérification de l'exécution des Job Servers et des serveurs d'accès [page 124]Guide de la console de gestion : Configuration d'un serveur d'accès

6.8.4 Configuration des chemins SSL

Utilisez le Gestionnaire de serveurs pour configurer les chemins d'accès aux certificats SSL et aux fichiers de clé.

RemarquePar défaut, les chemins d'accès aux certificats SSL et aux fichiers de clé sont automatiquement configurés pendant l'installation. Il n'est pas nécessaire de les modifier à moins que vous ne souhaitiez utiliser vos propres certificats.

RemarqueSi vous modifiez la configuration du certificat SSL, il est nécessaire de resynchroniser tous les référentiels associés au Job Server pour pouvoir exécuter des jobs.

1. Ouvrez le Gestionnaire de serveurs et cliquez sur l'onglet SSL.2. Spécifiez les emplacements du fichier du certificat du serveur, le fichier de clé privée du serveur et le

dossier de certificats de confiance.

RemarqueLe certificat du serveur doit être au format PEM. Parmi les extensions valides pour les certificats dans le dossier des certificats de confiance figurent .pem, .crt et .cer. Quelle que soit l'extension du fichier, tous les contenus de fichiers de certificats doivent être au format PEM.

3. Pour spécifier un fichier de mots de passe de clé privée, sélectionnez Utiliser le fichier de mots de passe de la clé privée du serveur et spécifiez l'emplacement du fichier de mots de passe.

4. Cliquez sur Fermer et redémarrer pour fermer le Gestionnaire de serveurs et redémarrer tout serveur Data Services sur l'ordinateur avec les informations de certificat mises à jour.

RemarqueLes informations de certificat spécifiées dans le Gestionnaire de serveurs s'appliquent à tous les serveurs Data Services s'exécutant sur cet ordinateur physique. comme les Job Servers, les serveurs d'accès, etc.

Présentation des tâches : Use the Server Manager on Windows [page 115]


PUBLICPUBLIQUE 123

https://help.sap.com/viewer/4d2e69d5c5c2492681f0c64062ba66f1/4.2.14/fr-FR/574f500e6d6d1014b3fc9283b0e91070.html


Configuring Job Servers [page 116]Configuring runtime resources [page 120]Configuration des serveurs d'accès [page 122]Vérification de l'exécution des Job Servers et des serveurs d'accès [page 124]

6.8.5 Vérification de l'exécution des Job Servers et des serveurs d'accès

Pour vérifier l'exécution des Job Servers :

1. Dans l'onglet Processus de Windows Task Manager, vérifiez si les processus suivants sont définis :○ al_jobservice.exe (représente le service SAP Data Services)○ al_jobserver.exe (un par Job Server)○ AL_AccessServer.exe (un par serveur d'accès)

2. Si l'un de ces processus n'y figure pas, consultez les messages d'erreur dans le journal d'événements du Job Server dans <REP_LIENS>/log/<Nom du Job Server>/server_eventlog.txt.

RemarqueLes journaux de serveur d'accès se trouvent dans le journal <Nom du chemin d'accès au serveur d'accès>/error_mm_jj_aaaa.log

Rubrique parent : Use the Server Manager on Windows [page 115]


Configuring Job Servers [page 116]Configuring runtime resources [page 120]Configuration des serveurs d'accès [page 122]Configuration des chemins SSL [page 123]

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.

124PUBLICPUBLIQUE


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.


PUBLICPUBLIQUE 125

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 127]Use the Server Manager to configure the Job Server and to configure a repository Job Server for your Unix or Linux platform.

Configuration des ressources d'exécution [page 129]

Configuration des serveurs d'accès [page 131]


Démarrage ou arrêt du service [page 133]

Configure SMTP email [page 134]Use the Server Manager to specify SMTP server settings for the smtp_to email function.


126PUBLICPUBLIQUE



DSN-less and TNS-less connections [page 77]Setting UNIX environment variables [page 79]Lancer les services automatiquement pour Windows and Unix [page 81]History retention and Job Server log retention [page 83]Configuration de la connectivité de la base de données pour UNIX et Linux [page 87]Using the ODBC Drivers Selector for Windows [page 113]Using the License Manager [page 114]Use the Server Manager on Windows [page 115]Configuring Metadata Browsing Service and View Data Service [page 135]Paramètres de l'application CMC de Data Services [page 139]

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):


PUBLICPUBLIQUE 127

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 repo

sitory.○ 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.

RemarqueIf 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:

128PUBLICPUBLIQUE


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.ini

DB2 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.

RemarqueThe 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 124]


Configuration des ressources d'exécution [page 129]Configuration des serveurs d'accès [page 131]Configuration des chemins SSL [page 132]Démarrage ou arrêt du service [page 133]Configure SMTP email [page 134]DSN-less and TNS-less connections [page 77]

6.9.2 Configuration des ressources d'exécution

1. Assurez-vous que les variables d'environnement requises sont définies et exécutez le Gestionnaire de serveurs.

$ cd $LINK_DIR/bin/


PUBLICPUBLIQUE 129

$ . ./al_env.sh $ ./svrcfg

L'écran principal du Gestionnaire de serveurs apparaît.2. Saisissez le chiffre 4 pour configurer des ressources d'exécution.

L'écran Informations des ressources d'exécution s'affiche.3. Saisissez e pour modifier la configuration des ressources d'exécution.

4. Acceptez le Répertoire du cache paginable proposé par défaut ou spécifiez un emplacement différent.

RestrictionLe chemin d'accès au Répertoire du cache paginable ne peut pas dépasser 70 caractères.

RemarquePour les opérations sollicitant activement la mémoire comme Regrouper par, Trier par et Profilage détaillé, spécifiez un répertoire du cache paginable qui remplit les conditions suivantes :○ Le répertoire contient assez d'espace disque pour les données. Pour estimer l'espace requis,

prenez en compte des facteurs comme le nombre de jobs ou flux de données s'exécutant simultanément et la quantité de cache paginable requise par chacun de ces flux de données.

○ Le référentiel existe sur un disque ou un fichier système distinct du système Data Services et du système d'exploitation.

○ Le référentiel limite l'espace disque que consomment les flux de données. Le cache paginable utilise tout l'espace disque disponible sur le système de fichiers qui contient le répertoire du cache paginable. Pour limiter l'espace disque consommé par les flux de données, créez un système de fichiers au volume limité. Utilisez le nouveau système de fichiers en tant que répertoire du cache paginable.

Le logiciel utilise ce répertoire dans les situations suivantes :○ Pour une mise en cache paginable, le type de cache par défaut pour les flux de données. Pour plus

d'informations, consultez le Guide d'optimisation de la performance.○ Lorsque le logiciel sélectionne un type de transfert de fichiers et qu'Automatique est spécifié dans

la transformation Data_Transfer.

5. Modifiez les valeurs pour Port de début et Port de fin afin de restreindre le nombre de ports utilisés par le logiciel pour les communications Peer-to-Peer. Les valeurs par défaut sont respectivement 1025 et 32767.Le logiciel utilise ces ports pour des communications Peer-to-Peer lors de l'envoi de données entre flux de données ou flux de données secondaires s'exécutant sur des Job Servers différents.

6. Spécifiez si vous souhaitez utiliser le protocole de sécurité SSL sur les chemins de communication entre flux de données et flux de données secondaires.

7. Saisissez q, puis x pour quitter le Gestionnaire de serveurs.

Présentation des tâches : Using the Server Manager on UNIX systems [page 124]


Configuring Job Servers on UNIX [page 127]

130PUBLICPUBLIQUE


Configuration des serveurs d'accès [page 131]Configuration des chemins SSL [page 132]Démarrage ou arrêt du service [page 133]Configure SMTP email [page 134]Guide d'optimisation de la performance : utilisation du calcul distribué pour distribuer l'exécution des flux de données

6.9.3 Configuration des serveurs d'accèsLors de la configuration de l'emplacement d'installation d'un serveur d'accès, SAP Data Services crée de l'espace pour les fichiers journaux du serveur d'accès.



L'écran principal du Gestionnaire de serveurs apparaît.2. Saisissez le chiffre 4 pour configurer un serveur d'accès.

L'écran Informations du serveur d'accès apparaît.3. Saisissez la commande pour la tâche de configuration que vous souhaitez effectuer :

Commande Tâche de configuration

c Créer un serveur d'accès.

e Modifier un serveur d'accès existant.

d Supprimer un serveur d'accès existant.

4. Lors de la création ou de la suppression d'un serveur d'accès, spécifiez les détails des configurations supplémentaires :a. Si vous modifiez un serveur d'accès existant, entrez le numéro du serveur d'accès indiqué à l'écran des

informations de configuration du serveur d'accès.b. Spécifie le répertoire du serveur d'accès.c. Spécifie le port TCP/IP que le serveur d'accès doit utiliser pour la communication.

RemarqueIl est possible de configurer plus d'un serveur d'accès sur le même ordinateur, mais chacun d'entre eux doit avoir des ports distincts. Si vous saisissez un numéro de port déjà en cours d'utilisation, un message d'erreur s'affiche.

d. Spécifiez tout paramètre supplémentaire du serveur d'accès.

RemarqueIl est possible d'afficher les paramètres supplémentaires du serveur d'accès en entrant AL_AccessServer au niveau de la ligne de commande. Pour plus d'informations, consultez « Performance en temps réel » dans le guide Management Console Guide.


PUBLICPUBLIQUE 131



e. Spécifiez si vous souhaitez utiliser la sécurité SSL pour la messagerie instantanée sur ce serveur d'accès.

f. Spécifiez si vous souhaitez activer le serveur d'accès.5. Lors de la suppression d'un serveur d'accès, spécifiez le numéro du serveur d'accès à supprimer.

RemarqueLors de la suppression d'un serveur d'accès, tous les serveurs d'accès sont arrêtés. Lorsque vous quittez le Gestionnaire de serveurs, tout serveur d'accès restant redémarre.

6. Lorsque les modifications apportées à la configuration vous conviennent, saisissez q, puis x pour quitter le Gestionnaire de serveurs.



Configuring Job Servers on UNIX [page 127]Configuration des ressources d'exécution [page 129]Configuration des chemins SSL [page 132]Démarrage ou arrêt du service [page 133]Configure SMTP email [page 134]Guide de la console de gestion : Configuration d'un serveur d'accès

6.9.4 Configuration des chemins SSL

Utilisez le Gestionnaire de serveurs pour configurer les chemins d'accès aux certificats SSL et aux fichiers de clé.

RemarquePar défaut, les chemins d'accès aux certificats SSL et aux fichiers de clé sont automatiquement configurés pendant l'installation. Il n'est pas nécessaire de les modifier à moins que vous ne souhaitiez utiliser vos propres certificats.



L'écran principal du Gestionnaire de serveurs apparaît.2. Saisissez le chiffre 7 pour configurer des chemins SSL.

L'écran Informations de la configuration SSL s'affiche.

132PUBLICPUBLIQUE


https://help.sap.com/viewer/4d2e69d5c5c2492681f0c64062ba66f1/4.2.14/fr-FR/574f500e6d6d1014b3fc9283b0e91070.html

3. Saisissez e pour modifier la configuration SSL.

4. Spécifiez les informations de la configuration SSL lorsque vous y êtes invité :a. Chemin d'accès au fichier du certificat du serveurb. Chemin d'accès au fichier de clé privée du serveurc. Si vous souhaitez utiliser un fichier de mots de passe de clé privée et le chemin d'accès à ce fichierd. Répertoire où sont stockés vos certificats de confiance

RemarqueLe certificat du serveur doit être au format PEM. Parmi les extensions valides pour les certificats dans le dossier des certificats de confiance figurent .pem, .crt et .cer. Quelle que soit l'extension du fichier, tous les contenus de fichiers de certificats doivent être au format PEM.

5. Lorsque les modifications apportées à la configuration vous conviennent, saisissez q, puisx pour quitter le Gestionnaire de serveurs.

Les informations de certificat spécifiées dans le Gestionnaire de serveurs s'appliquent à tous les serveurs Data Services s'exécutant sur cet ordinateur physique (par exemple, tout Job Server, serveur d'accès, etc.)



Configuring Job Servers on UNIX [page 127]Configuration des ressources d'exécution [page 129]Configuration des serveurs d'accès [page 131]Démarrage ou arrêt du service [page 133]Configure SMTP email [page 134]

6.9.5 Démarrage ou arrêt du serviceLe service SAP Data Services (AL_JobService) est un démon associé à $LINK_DIR qui démarre les Job Servers et les serveurs d'accès configurés localement, les surveille et tente de les redémarrer s'ils ne sont pas en cours d'exécution.

Après avoir quitté le Gestionnaire de serveurs, AL_JobService extrait automatiquement toute modification apportée aux Job Servers ou aux serveurs d'accès. Il n'est pas nécessaire de redémarrer AL_JobService.

1. Exécutez le Gestionnaire de serveurs


RemarqueLa deuxième commande définit les variables d'environnement requises avant l'exécution du Gestionnaire de serveurs par ./svrcfg.


PUBLICPUBLIQUE 133

L'écran principal du Gestionnaire de serveurs apparaît.2. Saisissez le chiffre 1 pour contrôler le service (service de Jobs).

3. Démarrez ou arrêtez le service de Jobs.

○ Saisissez s pour démarrer le service de Jobs.○ Saisissez o pour arrêter le service de Jobs.

4. Saisissez q, puis x pour quitter le Gestionnaire de serveurs.



Configuring Job Servers on UNIX [page 127]Configuration des ressources d'exécution [page 129]Configuration des serveurs d'accès [page 131]Configuration des chemins SSL [page 132]Configure SMTP email [page 134]

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 124]


Configuring Job Servers on UNIX [page 127]Configuration des ressources d'exécution [page 129]Configuration des serveurs d'accès [page 131]Configuration des chemins SSL [page 132]Démarrage ou arrêt du service [page 133]

134PUBLICPUBLIQUE


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.

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.

RemarqueNot 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.

Paramètres de configuration du service de navigation dans les métadonnées [page 136]Il est possible de modifier les propriétés suivantes du Service d'exploration des métadonnées.

Paramètres de configuration des services de visualisation des données [page 138]Il est possible de modifier les propriétés suivantes du Service de visualisation des données.

Task overview: Gestion des serveurs [page 76]


DSN-less and TNS-less connections [page 77]Setting UNIX environment variables [page 79]Lancer les services automatiquement pour Windows and Unix [page 81]History retention and Job Server log retention [page 83]Configuration de la connectivité de la base de données pour UNIX et Linux [page 87]Using the ODBC Drivers Selector for Windows [page 113]Using the License Manager [page 114]Use the Server Manager on Windows [page 115]


PUBLICPUBLIQUE 135

Using the Server Manager on UNIX systems [page 124]Paramètres de l'application CMC de Data Services [page 139]

6.10.1 Paramètres de configuration du service de navigation dans les métadonnées

Il est possible de modifier les propriétés suivantes du Service d'exploration des métadonnées.

Paramètre de configuration du serveur Description Valeurs possibles

Nom du service Nom de la configuration du service. Chaîne alphanumérique de 64 caractères au maximum. Le nom du service ne peut comporter aucun espace.

Valeur par défaut : MetadataBrowsingService

Nombre maximal de connexions de source de données

Nombre maximal de connexions de source de données pouvant être ouvertes à un moment donné sous une instance du service.

entier.

Valeur par défaut : 200

Tentatives d'essai de lancement du fournisseur de services

Nombre maximal de tentatives pour lancer un nouveau fournisseur de services en cas de refus d'accès à un fournisseur de service partagé.


Délai d'attente de connexion avec état (en secondes)

Durée maximale d'ouverture d'une connexion avec état. Les connexions avec état comprennent les applications SAP et la source SAP BW.


Délai d'attente de connexion sans état (en secondes)

Durée maximale d'ouverture d'une connexion sans état. Les connexions sans état comprennent toutes les sources de bases de données relationnelles.


Seuil de recyclage Nombre maximal de demandes traitées par le service avant que le moteur backend de Data Services ne soit recyclé pour libérer la mémoire qui a été allouée à la navigation par métadonnées.


136PUBLICPUBLIQUE



Niveau de journalisation Niveau de journalisation des messages de suivi dans le fichier journal.

RemarqueSi plusieurs instances du service de navigation par métadonnées sont configurées dans le CMS, le même niveau d'informations est collecté dans toutes les instances. Le niveau de journalisation défini pour le premier service en cours d'exécution est le niveau utilisé.

Journaux d'Information Steward :

● Aucun : journalisation désactivée.● Infos : journalisation désactivée.

(comme Aucun)● Plus détaillé : l'ensemble des sui

vis, demandes et réponses.

Journaux de Data Services :

● Aucun : journalisation désactivée.● Infos : tous les suivis.● Plus détaillé : l'ensemble des sui

vis, demandes et réponses.

Le niveau par défaut est Infos.

Collecte des statistiques de connexion Activer ou désactiver la collecte des informations statistiques pour chaque connexion ouverte.

La valeur par défaut est Activée.

Port d'écoute Numéro de port utilisé pour communiquer avec le moteur backend de Data Services

Si vous modifiez le numéro de port, vous devez redémarrer le serveur EIMAdaptiveProcessingServer pour que les modifications s'appliquent.

Numéro de port à quatre chiffres non utilisé actuellement.


Port du connecteur JMX Numéro de port utilisé pour le connecteur JMX.


Numéro de port à quatre chiffres non utilisé actuellement.


Rubrique parent : Configuring Metadata Browsing Service and View Data Service [page 135]


Paramètres de configuration des services de visualisation des données [page 138]


PUBLICPUBLIQUE 137

6.10.2 Paramètres de configuration des services de visualisation des données

Il est possible de modifier les propriétés suivantes du Service de visualisation des données.


Nom du service Nom de la configuration du service. Chaîne alphanumérique de 64 caractères au maximum. Le nom du service ne peut comporter aucun espace.

Valeur par défaut : ViewData

Port d'écoute Numéro de port utilisé pour communiquer avec le moteur backend de Data Services


Entier à quatre chiffres.


Port du connecteur JMX Numéro de port utilisé pour le connecteur JMX.


Entier à quatre chiffres.


Taille de lot (en kilooctets) Taille des données à stocker dans une réponse d'affi-chage des données.

Valeur minimale : 1000

Valeur maximale : 5000


Nombre minimal de fournisseurs de services partagés

Nombre minimal de moteurs backend de Data Services devant être lancés au moment du démarrage du service.


Nombre maximal de fournisseurs de services partagés

Nombre maximal de moteurs backend de Data Services pouvant être lancés pendant la réponse aux demandes de visualisation des données.


Nombre maximal de fournisseurs de services dédiés

Nombre maximal de moteurs backend de Data Services pouvant être lancés à tout moment.


Seuil de recyclage Nombre maximal de demandes traitées par un service avant que le moteur backend de Data Services ne soit recyclé pour libérer la mémoire qui a été allouée à l'affi-chage des données.

Un entier quelconque.


Nombre de tentatives de lancement du prestataire de services

Nombre de tentatives effectuées pour essayer de lancer l'instance du moteur backend de Data Services.


Délai maximal d'inactivité du fournisseur de services partagé (minutes)

Nombre maximal de minutes pendant lesquelles le moteur backend de Data Services sans traiter de demandes. A l'expiration de ce délai, le moteur backend de Data Services est arrêté.


138PUBLICPUBLIQUE



Niveau de journalisation Niveau de journalisation des messages de suivi dans le fichier journal.

RemarqueSi plusieurs instances du service d'affichage des données sont configurées dans le CMS, le même niveau d'information est collecté dans toutes les instances. Le niveau de journalisation défini pour le premier service en cours d'exécution est le niveau utilisé.

Journaux d'Information Steward :

● Aucun : journalisation désactivée.

● Infos : journalisation désactivée. (comme Aucun)

● Plus détaillé : l'ensemble des suivis, demandes et réponses.

Journaux de Data Services :

● Aucun : journalisation désactivée.

● Infos : tous les suivis.● Plus détaillé : l'ensemble des

suivis, demandes et réponses.

Le niveau par défaut est Infos.

Rubrique parent : Configuring Metadata Browsing Service and View Data Service [page 135]


Paramètres de configuration du service de navigation dans les métadonnées [page 136]

6.11 Paramètres de l'application CMC de Data Services

Vous pouvez modifier les paramètres suivants de l'application Data Services dans la Central Management Console (CMC).

Option Description

Période de rétention de l'historique Nombre de jours durant lequel l'historique d'exécution du job est conservé.


● Si vous saisissez 0, le logiciel ne conserve pas d'historique de jobs.● Si vous saisissez une valeur négative, le logiciel conserve alors l'historique

de jobs indéfiniment.


PUBLICPUBLIQUE 139

Option Description

Période de rétention du journal de Job Server

Nombre de jours durant lequel les journaux de Job Server sont conservés.


● Si vous saisissez 0, le logiciel ne conserve pas les journaux de Job Server.● Si vous saisissez une valeur négative, le logiciel conserve alors les jour

naux de Job Server indéfiniment.

Période de nettoyage de l'historique de jobs

Nombre de secondes à partir de l'heure de début du job à laquelle la Console de gestion Data Services nettoie l'historique des job mauvais ou qui ont planté.

Avec ces paramètres, vous pouvez trouver les jobs qui sont exécutés plus longtemps que d'habitude, ou bien les jobs qui ont planté de manière anormale.

Un job qui plante d'une manière anormale ne met pas à jour les tables de métadonnées de l'historique de jobs ou le référentiel local, et le logiciel n'enregistre pas une heure de fin. Par conséquent, même si le job plante, la Console de gestion peut l'afficher comme étant en cours d'exécution.

Le paramètre par défaut est 0.

● Si vous conservez la valeur par défaut de 0, ou si vous définissez un nombre négatif, alors le logiciel ne nettoie pas l'historique de jobs mauvais ou qui ont planté.

● Si vous définissez sur 1 ou plus, alors le logiciel nettoie l'historique de jobs mauvais ou qui ont planté dans le nombre de secondes défini à partir de l'heure de début du job.

Lorsque vous saisissez un nombre positif dans ce paramètre, saisissez un nombre qui vous donne suffisamment de temps pour que jobs en cours d'exécution soient terminés. Après l'écoulement de cette durée, tous les jobs n'ayant pas d'horodatage de début seront marqués comme échoués. Pour ces jobs, vous pouvez vérifier les fichiers journaux pour déterminer si le job s'est terminé normalement.

Par exemple, si votre job le plus long dure 30 minutes, définissez cette option sur 3 600 secondes afin que, une heure après le début du job, le statut dans la page de statut de batch dans la Console de gestion montre que le job n'est plus en traitement. De cette manière, vous pouvez voir une liste de jobs qui ont potentiellement planté de manière anormale, sans devoir attendre une longue période de temps.

Activer la communication SSL pour le Service d'exploration des métadonnées et le Service de visualisation des données

Indique s'il convient ou non d'utiliser les communications SSL pour le Service d'exploration des métadonnées et le Service de visualisation des données du serveur de traitement adaptatif EIM.

D'autres produits logiciels SAP tels que SAP Information Steward ont recours au Service d'exploration des métadonnées et au Service de visualisation des données pour explorer et importer des métadonnées et visualiser les données dans les connexions.

140PUBLICPUBLIQUE


Option Description

Utiliser les paramètres SSL par défaut Indique s'il convient ou non d'utiliser le keystore et les certificats SSL par défaut.

Valeur par défaut : Non

Si vous spécifiez Non, vous devez alors saisir des valeurs dans Fichier keystore, Mot de passe du keystore et Mot de passe clé.

Fichier keystore Nom de fichier du keystore qui contient la clé unique et tous les certificats faisant partie de la chaîne de certificats associée à la signature de la clé.

Valeur par défaut : DSJavaKeyStore.keystore

Mot de passe du keystore Mot de passe du fichier keystore.

Mot de passe clé Mot de passe pour accéder à la clé figurant dans le fichier keystore.

Phrase secrète de cryptage Phrase secrète à utiliser pour crypter les mots de passe envoyés dans le cadre des requêtes du Service d'exploration des métadonnées et du Service de visualisation des données.

D'autres produits progiciels SAP tels que SAP HANA ont recours à cette Phrase secrète de cryptage pour crypter les mots de passe lors de l'envoi d'une requête de connexion ouverte. Le moteur backend utilisera cette phrase secrète pour décrypter le mot de passe et traiter la requête de connexion ouverte.



DSN-less and TNS-less connections [page 77]Setting UNIX environment variables [page 79]Lancer les services automatiquement pour Windows and Unix [page 81]History retention and Job Server log retention [page 83]Configuration de la connectivité de la base de données pour UNIX et Linux [page 87]Using the ODBC Drivers Selector for Windows [page 113]Using the License Manager [page 114]Use the Server Manager on Windows [page 115]Using the Server Manager on UNIX systems [page 124]Configuring Metadata Browsing Service and View Data Service [page 135]


PUBLICPUBLIQUE 141

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 142]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 144]The SAP Data Services Management Console Administrator contains statistics for each job that you run.

Ignoring error status [page 147]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 147]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 148]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 148]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:

142PUBLICPUBLIQUE

Guide d'administrationMonitoring 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.

RemarqueIf 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 Paramètres de l'application CMC de Data Services [page 139].

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.

RemarqueConfigure 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.

RemarqueWhen 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 is the Job Server in the server group that executed the job. If you explicitly select a Job Server to


PUBLICPUBLIQUE 143

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 142]


Statistics [page 144]Ignoring error status [page 147]Deleting batch job history data [page 147]Stopping a running job [page 148]Deleting trace, monitor, and error logs for a batch job [page 148]Configuration de l'intervalle de statut

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 145]Use job statistics to help tune job performance.

Data flow statistics [page 146]Use statistics from a data flow to help tune job performance.

Parent topic: Monitoring jobs [page 142]


Viewing overall status of executed jobs [page 142]Ignoring error status [page 147]Deleting batch job history data [page 147]Stopping a running job [page 148]Deleting trace, monitor, and error logs for a batch job [page 148]

144PUBLICPUBLIQUE


https://help.sap.com/viewer/4d2e69d5c5c2492681f0c64062ba66f1/4.2.14/fr-FR/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 be

cause 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.


Path Name Indicates which object (step in a data flow) is running.


PUBLICPUBLIQUE 145


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 144]


Data flow statistics [page 146]

7.2.2 Data flow statistics

Use statistics from a data flow to help tune job performance.

Parent topic: Statistics [page 144]


Viewing job statistics [page 145]

146PUBLICPUBLIQUE


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 142]Statistics [page 144]Deleting batch job history data [page 147]Stopping a running job [page 148]Deleting trace, monitor, and error logs for a batch job [page 148]

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 83]. See the Management Console Guide for more information about the Batch Job Status page.



PUBLICPUBLIQUE 147


Viewing overall status of executed jobs [page 142]Statistics [page 144]Ignoring error status [page 147]Stopping a running job [page 148]Deleting trace, monitor, and error logs for a batch job [page 148]

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 142]Statistics [page 144]Ignoring error status [page 147]Deleting batch job history data [page 147]Deleting trace, monitor, and error logs for a batch job [page 148]

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.

AttentionThe 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.

148PUBLICPUBLIQUE



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 142]Statistics [page 144]Ignoring error status [page 147]Deleting batch job history data [page 147]Stopping a running job [page 148]


PUBLICPUBLIQUE 149

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 150]SAP Data Services supports multiple phases to conform to your development requirements.

Migration tools [page 154]Migration tools help you create a foundation for your development phases and migration structure.

Migration mechanisms [page 162]Decide which migration mechanism to use to migrate aplications from one development phase to the next.

Migrate with export and import [page 166]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 174]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 175]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.

150PUBLICPUBLIQUE

Guide d'administrationLifecycle 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 152]In the design phase, define applications that instruct SAP Data Services in your data movement requirements.

The test phase [page 152]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 153]In the production phase, use actual data, set a schedule to run applications, monitor application performance, and evaluate results.

Parent topic: Lifecycle migration [page 150]


Migration tools [page 154]Migration mechanisms [page 162]Migrate with export and import [page 166]Back up repositories [page 174]Mismatched locales and job performance [page 175]


PUBLICPUBLIQUE 151

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 150]


The test phase [page 152]The production phase [page 153]

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.


152PUBLICPUBLIQUE



The design phase [page 152]The production phase [page 153]

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.

RemarqueCustomize 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.

ExempleYou 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 152]The test phase [page 152]


PUBLICPUBLIQUE 153

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 confi-guration reflects the environment of each development phase.

Group datastores into system configurations to use when running jobs.

Conventions d'affectation des noms pour la migration [page 154]

Configurations système et de banque de données [page 158]



Development phases [page 150]Migration mechanisms [page 162]Migrate with export and import [page 166]Back up repositories [page 174]Mismatched locales and job performance [page 175]

8.2.1 Conventions d'affectation des noms pour la migration

Pour garantir une migration rapide et transparente, il est préférable d'utiliser des conventions d'affectation de noms communes à tous les systèmes et à toutes les phases des environnements de développement.

154PUBLICPUBLIQUE


Tout comme il est recommandé de standardiser les préfixes et les suffixes des objets ainsi que les identificateurs des chemins d'accès pour simplifier vos projets en interne, il est également préférable d'utiliser des conventions d'affectation de noms en externe à des fins de migration.

Pour faciliter la migration, utilisez des conventions d'affectation de noms communs aux éléments suivants :

● Connexions aux banques de données externes● Emplacements de répertoires● Structures et propriétaires des schémas

Il est préférable de rendre la migration d'applications entre utilisateurs et entre phases aussi rapide et facile que possible. Cela se traduit par une diminution significative – ou la suppression – du temps passé à la reconfiguration des jobs pour qu'ils fonctionnent dans chaque environnement spécifique.

Même si les données que vous extrayez, transformez et chargez sont généralement différentes d'une base de données à une autre, la structure de base de ces données doit être identique dans chacune des bases de données avec lesquelles vous souhaitez faire fonctionner les mêmes applications. C'est pourquoi il est judicieux de standardiser l'affectation de noms et la structure des bases de données avant de démarrer le processus de développement.

Connexions aux banques de données externes [page 155]

Emplacements de répertoires [page 157]

Structures et propriétaires des schémas [page 157]

Rubrique parent : Migration tools [page 154]


Configurations système et de banque de données [page 158]Guide de Designer : conventions d'appellation pour objets dans jobsConnexions aux banques de données externes [page 155]Emplacements de répertoires [page 157]Structures et propriétaires des schémas [page 157]

8.2.1.1 Connexions aux banques de données externes

La migration est le processus impliquant le déplacement d'objets entre référentiels locaux, de manière directe, à l'aide de la méthode d'exportation et d'importation, ou de manière indirecte, à l'aide de la méthode de développement multi-utilisateur. Indépendamment de la méthode, il est nécessaire de prendre en compte l'impact que la migration aura sur les configurations de connexion associées aux jobs.

L'utilisation d'une affectation de noms générique pour des connexions de banque de données en externe similaires diminue le temps passé à la reconfiguration des connexions à un même type de base de données. Il est préférable, par exemple, de choisir le même nom logique pour toutes vos connexions de banque de données Oracle au même type de structure de base de données, indépendamment de l'environnement de la phase de migration.


PUBLICPUBLIQUE 155

https://help.sap.com/viewer/ec06fadc50b64b6184f835e4f0e1f52f/4.2.14/fr-FR/57388ab36d6d1014b3fc9283b0e91070.html

Il est possible de donner des noms de connexion porteurs de sens pour une certaine phase et des noms de systèmes informatiques spécifiques (Test_DW, Dev_DW, Prod_DW). Cependant, si vous choisissez cette structure d'appellation, il est recommandé d'utiliser les configurations de banque de données à des fins de migration.

Phase de développement Phase de test

Nom d'utilisateur : Dev_DW Nom d'utilisateur : Test_DW

Mot de passe : Dev_DW Mot de passe : Test_DW

Chaîne hôte : Dev_DW Chaîne hôte : Test_DW

Pour qu'un job s'exécute en fonction de Test et de Développement, il doit utiliser Test_DW et Dev_DW. Cela implique de créer différentes configurations de banque de données pour les cas où le job s'exécute respectivement en fonction de l'instance Test ou de l'instance Dev.

Sinon, il est possible d'appeler la chaîne de connexion DW ; le job s'exécutera sans que les utilisateurs aient besoin de créer plusieurs configurations de banque de données, indépendamment de l'instance en fonction de laquelle vous l'exécutez.

Phase de développement Phase de test

Base de données AConnexion de banque de données Base de données B

Connexion de banque de données

Nom d'utilisateur : DW Nom d'utilisateur : DW Nom d'utilisateur : DW Nom d'utilisateur : DW

Mot de passe : DW Mot de passe : DW Mot de passe : DW Mot de passe : DW

Chaîne hôte : DW Nom du propriétaire : DW Chaîne hôte : DW Nom du propriétaire : DW

Exemples :

● Un système source Oracle traite dans votre société lesdonnées de saisie de commande. Plusieurs instances de ce système existent à des fins de développement, de test et de production. Vous nommez donc la chaîne de connexion à votre système source Oracle "ORDER_SYSTEM". Puis, dans toutes les phases, vous configurez ce nom de manière à ce qu'il pointe vers l'instance correcte (spécifique à la phase) du système.

● Nommez la chaîne de connexion à votre entrepôt de données cibles "DW", puis pointez-la vers des bases de données différentes selon l'environnement où vous vous trouvez : développement, test ou production.

Lors de l'utilisation de cette méthode d'affectation de noms interphase et générique, il est impossible d'accéder à la fois à dev et à test à partir du même ordinateur (puisque la chaîne de connexion ne mappe qu'une seule instance). Si vous avez besoin d'accéder aux deux, utilisez des configurations de banque de données différentes.

Rubrique parent : Conventions d'affectation des noms pour la migration [page 154]

156PUBLICPUBLIQUE



Emplacements de répertoires [page 157]Structures et propriétaires des schémas [page 157]Guide de Designer : développement multi-utilisateurs

8.2.1.2 Emplacements de répertoires

Il est recommandé d'utiliser des noms de répertoire logique (par exemple, X:\) ou de pointer vers des lecteurs locaux communs pour standardiser l'emplacement des répertoires. Par exemple, comme tout ordinateur possède un lecteur C:\ pointant vers l'emplacement du répertoire, C:\TEMP serait un standard sûr et reproductible.



Connexions aux banques de données externes [page 155]Structures et propriétaires des schémas [page 157]

8.2.1.3 Structures et propriétaires des schémas

Pour faciliter la transparence d'une structure entre les phases de développement, donnez à toutes vos instances de base de données le même nom de propriétaire pour les structures de schéma identiques à partir desquelles vous effectuez la lecture et vers lesquelles vous effectuez le chargement. Indépendamment du nom, le propriétaire de chaque structure de schéma peut varier et le logiciel les rapprochera.


PUBLICPUBLIQUE 157

https://help.sap.com/viewer/ec06fadc50b64b6184f835e4f0e1f52f/4.2.14/fr-FR/571e54ec6d6d1014b3fc9283b0e91070.html



Connexions aux banques de données externes [page 155]Emplacements de répertoires [page 157]

8.2.2 Configurations système et de banque de données

Les configurations système et de banque de données sont des outils performants destinés à réduire les configurations requises pour exécuter les mêmes calculs en fonction de différents environnements de banque de données. Avec l'aide de configurations, la migration entre les phases de développement est plus rapide et davantage simplifiée.

Multiple configurations in multi-user environments [page 159]

Configurations et migration de banque de données [page 160]

158PUBLICPUBLIQUE


Rubrique parent : Migration tools [page 154]


Conventions d'affectation des noms pour la migration [page 154]

Configurations et migration de banque de données [page 160]Multiple configurations in multi-user environments [page 159]

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.

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: Configurations système et de banque de données [page 158]


Configurations et migration de banque de données [page 160]Designer Guide: Multi-user developmentDesigner Guide: Multi-user environment setupDesigner Guide: Working in a multi-user environmentDesigner Guide: Migrating multi-user jobs


PUBLICPUBLIQUE 159

https://help.sap.com/viewer/ec06fadc50b64b6184f835e4f0e1f52f/4.2.14/fr-FR/571e54ec6d6d1014b3fc9283b0e91070.html

https://help.sap.com/viewer/ec06fadc50b64b6184f835e4f0e1f52f/4.2.14/fr-FR/573a26966d6d1014b3fc9283b0e91070.html

https://help.sap.com/viewer/ec06fadc50b64b6184f835e4f0e1f52f/4.2.14/fr-FR/573662a26d6d1014b3fc9283b0e91070.html

https://help.sap.com/viewer/ec06fadc50b64b6184f835e4f0e1f52f/4.2.14/fr-FR/573698bd6d6d1014b3fc9283b0e91070.html

8.2.2.2 Configurations et migration de banque de données

Lorsque vous effectuez des exportations et des importations d'un référentiel à l'autre sans avoir plusieurs configurations de banque de données, il est possible que vous perdiez du temps à chaque fois à reconfigurer les connexions de banque de données afin qu'elles utilisent le nouveau référentiel (et parfois l'ordinateur hôte).

Sans ces configurations multiples, chaque job d'un référentiel peut s'exécuter uniquement en fonction d'une configuration de banque de données.

Avec plusieurs configurations, vous pouvez associer plusieurs configurations de banque de données avec une seule définition de banque de données, au lieu d'avoir une banque de données distincte (et une configuration de banque de données) pour chaque instance de base de données.

Chaque configuration système définit un ensemble de configurations de banque de données qu'il est préférable d'utiliser ensemble lors de l'exécution d'un job. Il est nécessaire de créer des configurations de banque de données pour les banques de données du référentiel avant de créer des configurations de système.

160PUBLICPUBLIQUE


Tous les objets que vous souhaitez importer vers une banque de données aux configurations multiples doivent avoir le même propriétaire.


PUBLICPUBLIQUE 161

Rubrique parent : Configurations système et de banque de données [page 158]


Multiple configurations in multi-user environments [page 159]Guide de Designer : Banques de données, Création et gestion de plusieurs configurations de banque de données

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:

162PUBLICPUBLIQUE


https://help.sap.com/viewer/ec06fadc50b64b6184f835e4f0e1f52f/4.2.14/fr-FR/572395826d6d1014b3fc9283b0e91070.html

https://help.sap.com/viewer/ec06fadc50b64b6184f835e4f0e1f52f/4.2.14/fr-FR/572395826d6d1014b3fc9283b0e91070.html

● Export and import● Multi-user

Export and import migration [page 163]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 164]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 165]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 150]Migration tools [page 154]Migrate with export and import [page 166]Back up repositories [page 174]Mismatched locales and job performance [page 175]

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.


PUBLICPUBLIQUE 163

ExempleIf 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 162]


Multi-user development migration [page 164]The best mechanism [page 165]

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.


164PUBLICPUBLIQUE



Export and import migration [page 163]The best mechanism [page 165]

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.

ExempleTwo 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


PUBLICPUBLIQUE 165

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 163]Multi-user development migration [page 164]

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.

RestrictionYou can't export read-only transform configurations.

The export editor [page 167]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 168]

166PUBLICPUBLIQUE


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 169]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 171]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 171]After you export objects to an ATL or XML file, import the objects to a repository in the target environment.



Development phases [page 150]Migration tools [page 154]Migration mechanisms [page 162]Back up repositories [page 174]Mismatched locales and job performance [page 175]

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.

ExempleExport 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 166]


PUBLICPUBLIQUE 167


Exporting objects to another repository [page 168]Exporting objects to a file [page 169]Exporting a repository to a file [page 171]Importing objects or a repository from a file [page 171]

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.

168PUBLICPUBLIQUE


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 166]


The export editor [page 167]Exporting objects to a file [page 169]Exporting a repository to a file [page 171]Importing objects or a repository from a file [page 171]

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.


PUBLICPUBLIQUE 169

ConseilEven 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.

ExempleThe 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.

RemarqueThe 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 167]Exporting objects to another repository [page 168]Exporting a repository to a file [page 171]Importing objects or a repository from a file [page 171]

170PUBLICPUBLIQUE


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.

RemarqueThe 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 167]Exporting objects to another repository [page 168]Exporting objects to a file [page 169]Importing objects or a repository from a file [page 171]

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.

RemarqueImporting objects or an entire repository from a file overwrites existing objects with the same names in the destination repository.


PUBLICPUBLIQUE 171

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.

ExempleSelect 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.

172PUBLICPUBLIQUE


Option Description

Include Select to include an object marked for exclusion with a red “X”.

ExempleIf 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.

RemarqueIf 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.


PUBLICPUBLIQUE 173

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.

ExempleNew 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 167]Exporting objects to another repository [page 168]Exporting objects to a file [page 169]Exporting a repository to a file [page 171]

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.

174PUBLICPUBLIQUE


To back up repositories, follow instructions from the database management system that supports the repository.



Development phases [page 150]Migration tools [page 154]Migration mechanisms [page 162]Migrate with export and import [page 166]Mismatched locales and job performance [page 175]

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.

ExempleYour 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.


PUBLICPUBLIQUE 175

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 Paramètres régionaux et fonctionnalité multi-octets in the Reference Guide.



Development phases [page 150]Migration tools [page 154]Migration mechanisms [page 162]Migrate with export and import [page 166]Back up repositories [page 174]

176PUBLICPUBLIQUE


https://help.sap.com/viewer/8092b085a68941f6aaa6708685a62b0d/4.2.14/fr-FR/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.

RemarqueTo migrate from one environment to another environment, such as design to test, use one of the migration mechanisms described in Migration mechanisms [page 162].

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 179].

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

Guide d'administrationThe Enhanced Change and Transport System (CTS+)

PUBLICPUBLIQUE 177

● Dataflows● File formats● Functions● Datastores (as top-level object only)

For complete information about CTS+, see the Configuration Guide for CTS+ for version requirements.

178PUBLICPUBLIQUE

Guide d'administrationThe 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 179]Understand the special requirements for object promotion, such as user types, application rights, and shared directory requirements.

User rights for promotion management [page 182]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 183]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 187]Ensure that you and your systems are ready for export and import.

Object promotion options [page 188]The Object Promotion page in SAP Data Services Management Console offers export and import options.

Exporting objects [page 189]Use object promotion in SAP Data Services Management Console to export objects from a Data Services environment.

Importing objects [page 191]Import objects into a new environment that is different than the export environment.

Export and import trace and error log [page 193]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.

Guide d'administrationObject promotion management

PUBLICPUBLIQUE 179

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.

ExempleIf 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 diffe-rent, 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 181]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 181]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 179]


User rights for promotion management [page 182]Export and import configuration requirements [page 183]Before you export and import objects [page 187]

180PUBLICPUBLIQUE


Object promotion options [page 188]Exporting objects [page 189]Importing objects [page 191]Export and import trace and error log [page 193]

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 179]


Sequential import of multiple objects [page 181]

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.


PUBLICPUBLIQUE 181

Parent topic: Requirements for object promotion [page 179]


Shared directory user rights [page 181]

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

182PUBLICPUBLIQUE


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 179]Export and import configuration requirements [page 183]Before you export and import objects [page 187]Object promotion options [page 188]Exporting objects [page 189]Importing objects [page 191]Export and import trace and error log [page 193]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 182].

● 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.


PUBLICPUBLIQUE 183

ConseilIf 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 185]Create an export configuration to export objects and dependencies over secure FTP or to a shared directory.

Creating an import configuration [page 186]Create an import configuration to import objects and dependencies from an export shared directory.

Edit or delete configurations [page 187]Users with the correct permission and access can edit or delete export and import configurations.



Requirements for object promotion [page 179]User rights for promotion management [page 182]Before you export and import objects [page 187]Object promotion options [page 188]Exporting objects [page 189]Importing objects [page 191]Export and import trace and error log [page 193]

184PUBLICPUBLIQUE


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 183] and Requirements for object promotion [page 179].

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.


PUBLICPUBLIQUE 185

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 183]


Creating an import configuration [page 186]Edit or delete configurations [page 187]

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 183] and Requirements for object promotion [page 179].

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.

186PUBLICPUBLIQUE


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 183]


Creating an export configuration [page 185]Edit or delete configurations [page 187]

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 183]


Creating an export configuration [page 185]Creating an import configuration [page 186]

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 179].● You've met the user rights requirements stated in User rights for promotion management [page 182].


PUBLICPUBLIQUE 187

● 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.

RemarqueThe 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 179]User rights for promotion management [page 182]Export and import configuration requirements [page 183]Object promotion options [page 188]Exporting objects [page 189]Importing objects [page 191]Export and import trace and error log [page 193]

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.

188PUBLICPUBLIQUE




Requirements for object promotion [page 179]User rights for promotion management [page 182]Export and import configuration requirements [page 183]Before you export and import objects [page 187]Exporting objects [page 189]Importing objects [page 191]Export and import trace and error log [page 193]

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 187].

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:


PUBLICPUBLIQUE 189

○ 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.

ExempleIf 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 193].

Task overview: Object promotion management [page 179]


Requirements for object promotion [page 179]User rights for promotion management [page 182]

190PUBLICPUBLIQUE


Export and import configuration requirements [page 183]Before you export and import objects [page 187]Object promotion options [page 188]Importing objects [page 191]Export and import trace and error log [page 193]

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 187].

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.


PUBLICPUBLIQUE 191

○ 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 193].

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 179]


Requirements for object promotion [page 179]User rights for promotion management [page 182]Export and import configuration requirements [page 183]Before you export and import objects [page 187]Object promotion options [page 188]Exporting objects [page 189]Export and import trace and error log [page 193]

192PUBLICPUBLIQUE


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>

ExempleThe 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.



PUBLICPUBLIQUE 193


Requirements for object promotion [page 179]User rights for promotion management [page 182]Export and import configuration requirements [page 183]Before you export and import objects [page 187]Object promotion options [page 188]Exporting objects [page 189]Importing objects [page 191]

194PUBLICPUBLIQUE


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 195]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 196]The SMD component of SAP Solution Manager provides all functionality to centrally analyze and monitor a complete system landscape.

SLD integration requirements [page 196]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 195]


Solution Manager Diagnostics (SMD) Agent [page 196]SLD integration requirements [page 196]

Guide d'administrationIntegration with SAP and SAP Solution Manager

PUBLICPUBLIQUE 195

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 195]SLD integration requirements [page 196]

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.

RemarqueIf 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.

196PUBLICPUBLIQUE


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 195]Solution Manager Diagnostics (SMD) Agent [page 196]


PUBLICPUBLIQUE 197

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

RemarqueSAP 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.

198PUBLICPUBLIQUE

Guide d'administrationData 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 199]SMD analyzes and monitors problematic components from incidents in your system landscape to help you keep your systems running.

SMD Agent guidelines [page 201]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 201]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 202]SAP Data Services supports performance monitoring through CA Introscope, which needs the NCS library integration with Solution Manager Diagnostics.

Heartbeat monitoring [page 205]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 205]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.

RemarqueSMD requires SAP Solution Manager version 7.01 SP 26 or later.

The following table describes the components of SMD.

Guide d'administrationPerformance and availability monitoring

PUBLICPUBLIQUE 199

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.

RemarqueYou 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 199]


SMD Agent guidelines [page 201]Configure your system for SMD [page 201]The Native Component Supportability (NCS) library [page 202]Heartbeat monitoring [page 205]Alert monitoring [page 205]

200PUBLICPUBLIQUE



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 199]Configure your system for SMD [page 201]The Native Component Supportability (NCS) library [page 202]Heartbeat monitoring [page 205]Alert monitoring [page 205]

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.

RemarqueThe 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.


PUBLICPUBLIQUE 201



Solution Manager Diagnostics (SMD) overview [page 199]SMD Agent guidelines [page 201]The Native Component Supportability (NCS) library [page 202]Heartbeat monitoring [page 205]Alert monitoring [page 205]

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 203]Enable the NCS (Native Component Supportability) library on the Windows platform.

Enabling NCS library on Unix or Linux [page 204]Enable the NCS (Native Component Supportability) library on the Unix or Linux platforms.



Solution Manager Diagnostics (SMD) overview [page 199]SMD Agent guidelines [page 201]Configure your system for SMD [page 201]Heartbeat monitoring [page 205]Alert monitoring [page 205]

202PUBLICPUBLIQUE


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.

ExempleIf 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.


PUBLICPUBLIQUE 203

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 202]


Enabling NCS library on Unix or Linux [page 204]

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 202]


Enabling NCS library on Windows [page 203]

204PUBLICPUBLIQUE


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 199]SMD Agent guidelines [page 201]Configure your system for SMD [page 201]The Native Component Supportability (NCS) library [page 202]Alert monitoring [page 205]

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.


PUBLICPUBLIQUE 205



Solution Manager Diagnostics (SMD) overview [page 199]SMD Agent guidelines [page 201]Configure your system for SMD [page 201]The Native Component Supportability (NCS) library [page 202]Heartbeat monitoring [page 205]

206PUBLICPUBLIQUE


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.

RemarqueData 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.

Gestionnaire de licences [page 207]

Command line: Data Services Connection Manager (Unix) [page 210]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 211]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 213]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 215]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 221]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 225]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 227]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 Gestionnaire de licences

Le Gestionnaire de licences peut être utilisé uniquement dans le mode ligne de commande. Vous pouvez l'utiliser pour gérer les codes clés d'activation de votre produit (les codes alphanumériques auxquels il est fait référence chaque fois que vous exécutez certains logiciels). En utilisant le Gestionnaire de licences, vous

Guide d'administrationCommand line administration

PUBLICPUBLIQUE 207

pouvez afficher, ajouter et supprimer les codes clés d'activation du produit pour un logiciel du portefeuille de solutions SAP (comme SAP Data Services), si nécessaire.

RemarqueLe Gestionnaire de licences accède aux codes clés sur le système local uniquement ; il est impossible d'accéder aux codes clés à partir d'un système distant. Lors de la mise à jour de codes clés, appliquez les modifications sur tous les ordinateurs SAP Data Services en lançant le Gestionnaire de licences sur chaque ordinateur, y compris sur les ordinateurs de Designer et du Job Server.

RemarqueSi vous exécutez un système d'exploitation Windows, vous ne pourrez ni ajouter, ni supprimer les codes clés de licence, à moins d'avoir les droits d'administrateur. Pour ceux qui ne possèdent pas les droits d'administrateur, seuls les paramètres -v et --view sont disponibles.

Syntaxe

LicenseManager [-v | -a <code clé> | -r <code clé> [-l <code clé>]]

Paramètre Description

-v or --view Affiche les codes clés d'activation du produit stockés. Exemple :

Keycode: 00000-0000000-0000000-0000 Trial Option: Yes Expired: No Days Remaining: 54

-a or --add <code clé> Ajoute le code clé de licence spécifié et affiche les codes clés stockés. Renvoie des messages de statut lorsque les conditions suivantes se présentent :

● Une erreur interne s'est produite.● Code clé ajouté.● Code clé ajouté et version d'essai remplacée.● Code clé non ajouté car non valide.● Code clé non ajouté car c'est un enregistrement doublon.

-r or --remove <code clé> [-l <emplacement>]

Supprime le code clé d'activation du produit spécifié et affiche les codes clés stockés. Si <l'emplacement> est spécifié, la suppression est limitée à ce noeud. Renvoie des messages de statut lorsque les conditions suivantes se présentent :

● Une erreur interne s'est produite.● Suppression d'un code clé.● Suppression de plusieurs codes clés.● Code clé non supprimé car non valide.● Code clé non supprimé car non trouvé.

Starting License Manager in Unix [page 209]Start License Manager from a terminal, and use commands to set your license keys.

Rubrique parent : Command line administration [page 207]

208PUBLICPUBLIQUE



Command line: Data Services Connection Manager (Unix) [page 210]Command line: Repository Manager (Windows) [page 211]Command line: Repository Manager (Unix) [page 213]Command line: Server Manager (Unix or Linux) [page 215]Command line: Server Manager (Windows) [page 221]Command line: Password encryption [page 225]al_engine options [page 227]

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 Gestionnaire de licences [page 207] to set your license key.

Task overview: Gestionnaire de licences [page 207]


PUBLICPUBLIQUE 209

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.

RemarqueTo 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

RemarqueFor 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 207]


Gestionnaire de licences [page 207]Command line: Repository Manager (Windows) [page 211]Command line: Repository Manager (Unix) [page 213]Command line: Server Manager (Unix or Linux) [page 215]Command line: Server Manager (Windows) [page 221]Command line: Password encryption [page 225]al_engine options [page 227]Using the ODBC Drivers Selector for Windows [page 113]

210PUBLICPUBLIQUE



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.


PUBLICPUBLIQUE 211

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


212PUBLICPUBLIQUE



Gestionnaire de licences [page 207]Command line: Data Services Connection Manager (Unix) [page 210]Command line: Repository Manager (Unix) [page 213]Command line: Server Manager (Unix or Linux) [page 215]Command line: Server Manager (Windows) [page 221]Command line: Password encryption [page 225]al_engine options [page 227]

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.


PUBLICPUBLIQUE 213

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.

Exemple./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

214PUBLICPUBLIQUE


Command Description Value

-t Repository type Central repository

-d Show details



Gestionnaire de licences [page 207]Command line: Data Services Connection Manager (Unix) [page 210]Command line: Repository Manager (Windows) [page 211]Command line: Server Manager (Unix or Linux) [page 215]Command line: Server Manager (Windows) [page 221]Command line: Password encryption [page 225]al_engine options [page 227]

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.


PUBLICPUBLIQUE 215

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.

Remarque-TSTART and -TSTOP don't require additional parameters.

ExempleTo 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 217]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 218]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 220]Add runtime resources in Unix or Linux using the -TR parameter along with other special parameters, in svrcfg.



Gestionnaire de licences [page 207]Command line: Data Services Connection Manager (Unix) [page 210]

216PUBLICPUBLIQUE


Command line: Repository Manager (Windows) [page 211]Command line: Repository Manager (Unix) [page 213]Command line: Server Manager (Windows) [page 221]Command line: Password encryption [page 225]al_engine options [page 227]

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.

RemarqueEnsure 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.

ExempleThe 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 215]


Command line: Adding a Job Server (Unix or Linux) [page 218]


PUBLICPUBLIQUE 217

Command line: Adding runtime resources (Unix or Linux) [page 220]

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.

RemarqueEnsure 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 ven

dor 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.

RemarqueThis parameter is required only for repositories on Sybase.

218PUBLICPUBLIQUE



-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.

ExempleThe 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 217]Command line: Adding runtime resources (Unix or Linux) [page 220]


PUBLICPUBLIQUE 219

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.

RemarqueEnsure 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.

ExempleThe 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 217]Command line: Adding a Job Server (Unix or Linux) [page 218]

220PUBLICPUBLIQUE


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.

RemarqueData 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.

ExempleTo 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 222]Add an Access Server in Windows using the -n parameter and other special parameters.

Command line: Adding a Job Server (Windows) [page 223]Add a Job Server in Windows using the -n parameter along with other special parameters.

Command line: Adding runtime resources (Windows) [page 225]Add runtime resources in Windows using the -n parameter along with other special parameters.



Gestionnaire de licences [page 207]Command line: Data Services Connection Manager (Unix) [page 210]Command line: Repository Manager (Windows) [page 211]Command line: Repository Manager (Unix) [page 213]Command line: Server Manager (Unix or Linux) [page 215]Command line: Password encryption [page 225]


PUBLICPUBLIQUE 221

al_engine options [page 227]

The Native Component Supportability (NCS) library [page 202]

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.

RemarqueEnsure 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.

ExempleThe 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 221]


Command line: Adding a Job Server (Windows) [page 223]Command line: Adding runtime resources (Windows) [page 225]

222PUBLICPUBLIQUE


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.

RemarqueThis 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.


PUBLICPUBLIQUE 223


-Q<database_name> Specifies the database name for the repository.

Replace <database_name> with the name of the repository database.

RemarqueThis 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.

ExempleThe 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 222]Command line: Adding runtime resources (Windows) [page 225]

224PUBLICPUBLIQUE


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.

ExempleThe 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 222]Command line: Adding a Job Server (Windows) [page 223]

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.


PUBLICPUBLIQUE 225

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>"

RemarqueValues 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


226PUBLICPUBLIQUE



Gestionnaire de licences [page 207]Command line: Data Services Connection Manager (Unix) [page 210]Command line: Repository Manager (Windows) [page 211]Command line: Repository Manager (Unix) [page 213]Command line: Server Manager (Unix or Linux) [page 215]Command line: Server Manager (Windows) [page 221]al_engine options [page 227]

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"


PUBLICPUBLIQUE 227


-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 229]al_engine imports and exports repository information in the internal scripting languages of SAP Data Services: XML and ATL.



Gestionnaire de licences [page 207]Command line: Data Services Connection Manager (Unix) [page 210]Command line: Repository Manager (Windows) [page 211]Command line: Repository Manager (Unix) [page 213]Command line: Server Manager (Unix or Linux) [page 215]Command line: Server Manager (Windows) [page 221]Command line: Password encryption [page 225]

228PUBLICPUBLIQUE


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.

N'oubliez pasThe options are only for export and import operations.

RemarqueValues 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.

RestrictionYou 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.


PUBLICPUBLIQUE 229


-XKversion<VersionNumber> Exports repository database server version for server name connection. You must use this parameter with the -XKserver parameter.

Exemple-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.

RemarqueWhen 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.

230PUBLICPUBLIQUE


ExempleThe 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.

ExempleTo 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 227]


PUBLICPUBLIQUE 231

Clauses de non-responsabilité importantes et informations juridiques

Liens hypertexteCertains liens affichent une icône et/ou du texte contextuel. Ils fournissent des informations complémentaires.Explication des icônes :

● Liens accompagnés de l'icône : vous accédez à un site Web non hébergé par SAP. En utilisant de tels liens, vous acceptez (sauf indication contraire expresse dans vos contrats avec SAP) ce qui suit :

● Le contenu du site vers lequel redirige le lien n'est pas de la documentation SAP. Vous ne pouvez émettre aucune réclamation produit auprès de SAP sur la base de ces informations.

● SAP n'accepte pas ou désapprouve le contenu affiché sur le site vers lequel vous êtes redirigé, ni ne garantit la disponibilité et l'exactitude dudit contenu. SAP ne saurait être tenue responsable des dommages causés par l'utilisation dudit contenu sauf si de tels dommages étaient causés par une négligence grave ou une faute intentionnelle de SAP.

● Liens accompagnés de l'icône : vous quittez la documentation associée à un produit ou service SAP en particulier et accédez à un site Web hébergé par SAP. En utilisant lesdits liens, vous convenez (sauf indication contraire expresse dans vos contrats avec SAP) que vous ne pourrez pas émettre de réclamation produit auprès de SAP sur la base de ces informations.

Vidéos hébergées sur des plateformes externesCertaines vidéos peuvent pointer vers des plateformes d'hébergement de vidéos tierces. SAP ne garantit pas la disponibilité future des vidéos stockées sur ces plateformes. Par ailleurs, toute annonce ou tout autre contenu hébergé(e) sur ces plateformes (par exemple, suggestions de vidéos ou navigation vers d'autres vidéos hébergées sur le même site) ne relève ni du contrôle ni de la responsabilité de SAP.

Fonctionnalités Beta et expérimentalesLes fonctionnalités expérimentales ne font pas partie des éléments officiellement fournis par SAP et garantis pour les versions à venir. Cela signifie que les fonctionnalités expérimentales peuvent être modifiées par SAP à tout moment pour quelle que raison que ce soit, sans préavis. Les fonctionnalités expérimentales ne sont pas conçues pour être utilisées en production. Vous ne pouvez pas faire la démonstration, tester, examiner, évaluer ou utiliser d'une quelconque autre manière les fonctionnalités expérimentales dans un environnement productif ou avec des données n'ayant pas été suffisamment sauvegardées.Le but des fonctionnalités expérimentales est d'obtenir rapidement des avis afin que les clients et partenaires puissent influencer le produit futur. En partageant votre avis (par exemple sur SAP Community), vous acceptez que les droits de propriété intellectuelle des contributions ou œuvres dérivées constituent la propriété exclusive de SAP.

Exemple de codeLes codes et/ou fragments de code ne sont que des exemples. Ils ne sont pas destinés à une utilisation en production. L'exemple de code est utilisé uniquement pour mieux expliquer et visualiser les règles de syntaxe. SAP ne garantit pas l'exactitude ni l'exhaustivité de l'exemple de code. SAP ne saurait être tenue responsable des erreurs ou dommages causés par l'utilisation dudit exemple de code sauf si de tels dommages étaient causés par une négligence grave ou une faute intentionnelle de SAP.

Langage sans préjugésSAP soutient une culture de diversité et d'inclusion. Chaque fois que cela est possible, nous utilisons un langage impartial dans notre documentation pour faire référence aux personnes de toutes cultures, ethnies, genres et capacités.

232PUBLICPUBLIQUE

Guide d'administrationClauses de non-responsabilité importantes et informations juridiques

Guide d'administrationClauses de non-responsabilité importantes et informations juridiques

PUBLICPUBLIQUE 233

www.sap.com/contactsap

© 2021 SAP SE ou société affiliée SAP. Tous droits réservés.

Toute reproduction ou communication de la présente publication, même partielle, par quelque procédé et à quelque fin que ce soit, est interdite sans l'autorisation expresse et préalable de SAP SE ou d'une société affiliée SAP. Les informations du présent document sont susceptibles d’être modifiées sans préavis.

Certains logiciels commercialisés par SAP SE et ses distributeurs contiennent des composants logiciels qui sont la propriété d'éditeurs tiers. Les spécifications des produits peuvent varier d’un pays à l’autre.

Les informations du présent document sont fournies par SAP SE ou par une société affiliée SAP uniquement à titre informatif, sans engagement ni garantie d'aucune sorte. SAP SE ou ses sociétés affiliées ne pourront en aucun cas être tenues responsables des erreurs ou omissions relatives à ces informations. Les seules garanties fournies pour les produits et les services de SAP SE ou d'une société affiliée SAP sont celles énoncées expressément à titre de garantie accompagnant, le cas échéant, lesdits produits et services. Aucune des informations contenues dans le présent document ne saurait constituer une garantie supplémentaire.

SAP et tous les autres produits et services SAP mentionnés dans ce document, ainsi que leurs logos respectifs, sont des marques commerciales ou des marques déposées de SAP SE (ou d'une société affiliée SAP) en Allemagne ainsi que dans d'autres pays. Tous les autres noms de produit et service mentionnés sont des marques commerciales de leurs sociétés respectives.

Veuillez consulter https://www.sap.com/france/about/legal/trademark.html pour plus d'informations sur les marques déposées.

THE BEST RUN

https://www.sap.com/france/about/legal/trademark.html

https://www.sap.com/france/about/legal/trademark.html