SAP Data Services for Syniti Migrate

This topic contains the following sections:

• Preparation of XML in Migrate

• Importing XML Code Into Data Services

• Post Import Maintenance of Project

• Mapping Standards

• Export Building and Execution

• Report Building and Execution

• Cross Reference Building and Execution

About This Guide

This guide will provide details for the import of XML scripting build to SAP DataServices and instruct the user with tips for best practice and management of the Object conversion and loading to the target system. This guide is not intended to instruct on the installation, setup, security, or user access for SAP DataServices except where there is interaction with Syniti Migrate.

Prerequisites for Using Data Services

As part of the setup and connection from Syniti Migrate module to the ETL (in this case SAP systems), there are a few steps that must be performed to ensure that the systems can communicate efficiently and successfully.  The IT Lead or Project Manager will organize this setup and will be responsible for successful connection of the systems.

The following sections will provide details of steps that have become part of the routine for setup and use of SAP Data Services as the ETL for Syniti Migrate.

Building Datastores in Data Services

Although the XML Scripting that generates for the Import of data to Datasources or the Migration Project is very robust and provides much of the hierarchy in terms of Workflows, Dataflows, and Queries, it cannot build the Datastores.  This is a manual task that is performed by either an IT Lead or the Developers depending upon the security setup and roles on the project.

Datastores must be created manually within SAP Data Services Datastore section before the XML files are imported to Data Services system. They must be setup to connect to the system from which they will tie for table data, and they must be tested.

In addition to building the Datastores for System Datasources, Target Datasources, and Source Datasources, Datastores are required for xAppMigrate, xAppReport, and xAppMigrate_Webservice.  These Datastores assist in connection to Syniti Migrate for updating tables, storing the report output, and for WebServices functions for use in building the WADL reports.

xAppMigrate Datastore

The xAppMigrate Datastore will connect to the Migration Working Server for the purpose of updating values in tables XTVALUEMAP and LIST_TARGET_VALUE for the Xref data conversion. This Datastore will point to the MIGRATE database within the Migration Working Server. Every dataset will reference the tables contained in this datastore and so it too must be present prior to importing XML for Datasets or Sources. The actual tables will be created as part of the Import of XML for Dataset

xAppMigrate_WebService Datastore

The xAppMigrate_WebService datastore will store the functions used within WADL reporting.  This datastore is created as Datastore Type = Web Service REST as shown below.  As the XML scripting imports for the migration project, these functions will also import to load to this Datastore.

Note

The URL is stored within the notes of the Transform job in the XML script.

The import for this Web Service REST is slightly different than for the others.  The user will open the pathway for this datastore to view the Functions that are attached.  For each of these functions, highlight and then right click to open the options and click on Import.  This will import the data.

Only after these functions are imported will they be present in the Datastore as shown below.

Within the query for CallWebService, there will be functions for the xAppMigrate_WebService function category.

DS Repository Setting for Case Sensitive ODBC Datastore Owners and Table Names

As part of the overall setup of Data Services for use with Syniti Migrate, the IT Lead will need to add a row of code to the file as a DS Repository setting.

This is linked to DS Repository setting. Attached SAP note with details.

Cause

Data Services automatically converts the ODBC Datastore owner and table names to all uppercase

characters when importing table metadata.

Resolution

To override this behavior, follow these steps before you create the ODBC Datastore:

1. On the Designer workstation open DSConfig.txt located:  %DS_COMMON_DIR%\conf (%LINK_DIR\bin in older versions)

2. Go to the [AL_Engine] section of the file and the manually add the following parameter:  ODBCAlwaysCaseSensitive=TRUE

3. Stop and restart the SAP Data Services service via Windows Services in order to implement the change.

4. Create (or recreate) the ODBC datastore and import the table(s)

WADL SSL Certificate Setup in Data Services

WADL report refresh error is providing an SSL certificate error

Background Information

User was having trouble with installation of WADL-based report refreshes - User could not import functions to the Datastore due to a certificate failure, however when trying to hit the link both locally and on the server, they did not get certificate warnings.

In a normal situation without issues, the User could open the datastore for xAppMigrate_WebService as shown below to import the Metadata for all 6 functions.  This Datastore is setup as Type = Web Service REST and it stores functions that are used to run the reporting for remediation, validation, and refresh.

When they would try to import the XML Scripting for these functions, it would produce errors as shown below:

Per the Note within the imported XML scripting, the web address is listed as:

SAP Solution

SAP Support provided this solution and when applied it resolved the issue.  The error message below is generated due to this issue.

The 2 specific SAP Notes reference a tie back:

https://launchpad.support.sap.com/#/notes/2338044 - BODI-1111469

https://launchpad.support.sap.com/#/notes/2841300 - BODI-1112446

Also, the SAP Portal provides this Note as a resolve, but the system is running a newer version of Data Services than within this note:

Steps for Resolve of this Issue

STEP 1 - The Browser response to the error while using Chrome shows the following:

STEP 2 - From Chrome, click F12 key to go to the Security Tab and then click View Certificate button.

STEP 3 - The certificate is displayed.  Click tab for Certification Path.

STEP 4 - Click the View Certificate button.

STEP 5 - Click Details tab.

STEP 6 - Click Copy to File... button to start the Export Wizard for the certificate.

STEP 7 - Follow the wizard steps - Click Next

STEP 8 - Select Base-64 encoded x.509 (.CER) as the format to use and then click Next.

STEP 9 - Save Top Layer as *filename*_1.CER

(please note all saved files are in this image including the next few steps)  Click Save button.

STEP 10 - The Wizard will return on page.  Click Next button to proceed.

STEP 11 - The Certificate should have exported successfully - Click Finish button and then click OK to complete this process.

STEP 12 - Select the next tree Layer, click View Certificate button and then REPEAT STEPS 5 through 11 for the second level.  Make sure to name the File as *FileName*_2.CER for the second Layer

Once the export is successful, move to the next level and repeat until all levels have the Certificates exported.

STEP 13 - Combine all of the Certificate export files into a single file and name it *Filename*.CER

Do this by using Notepad - Copy all contents into a single file, appending ALL CONTENTS as shown below.  Each certificate will have ----- BEGIN CERTIFICATE -----  and ------ END CERTIFICATE ----- to identify and separate.

STEP 14 - Data Services References

Now that the combined Certificate file is available, save this file in a location that the Job Server can reach.  A shared drive is preferred as each person at their local run level will also need to be able to reach this same path.

With the file saved on a shared drive, the user can now edit the Datastore for xAppMigrate_WebService - Add SSL Pem File, fully qualified path, and file name:

When the user clicks Apply button the Error message will no longer be present.  Next, click OK and continue the process for Import of Metadata for Functions.

For each of the 4 Functions, click to highlight and then right click and Import.  Refer to section Building Datastores in Data Services for details of this process.