Contents

Purpose

This section provides information about all steps necessary to preserve the connection to NLS on Hadoop during the SAP system refresh.
It does NOT cover the information related to actual application data.

The chapters below list the areas of SAP system that need to be saved during the system refresh.
The usual approach is to export the content of appropriate tables and import it afterward.
Actual table names are not listed, as these may vary depending on the SAP Netweaver version.

RFC destinations

It is a common practice to re-import all RFC destinations during the system refresh. Datavard Storage Management is dependent on two RFC destinations (link) that need to be preserved.

Certificates

Similarly to the usual Secure Storage content re-import, the system's certificates contained in STRUST need to be re-imported as well.

User Master Data

User Master Data re-import usually is, but sometimes may not be a part of the system refresh. Important for Datavard Java Connector functionality is the HADOOP user (link).

HADOOP technical user and the role are client dependent.

Logical paths

If the Storage Management setup was done properly, the logical paths defined in transaction FILE (link) are identical in development, quality, and production systems.
Usage of <SYSID> in the path definition ensures that no post-processing in this area is necessary.

OS directories

The "dvd_conn" directories described in the setup guide (link) contain configuration files necessary for the proper functionality of Datavard Java Connector and as such need to be preserved.

Java Connector export

Prior to refresh of the quality system, we recommend to preserve Java connector settings by exporting them into a transport. This transport can be later imported to the refreshed quality system.

To export the Java connector:

Go to transaction /DVD/JCO_MNG
Click the Transport JCO button in the toolbar
Fill the required information. In most cases, you want to preserve all settings and libraries.
Proceed. In the next screen use either an existing transport or create a new transport of copies.
Go to SE01 and release the transport.

Storage definition export

TO BE ADDED - a full definition of selected Storage ID will be exportable into standard transport request using a report.
Jira ticket: RL-644 - Getting issue details... STATUS

Datavard Java Connector setup export into transport is already available.

Things to consider

The following topics do not relate directly to the Storage Management setup but are worth keeping in mind while refreshing the SAP system connected to Hadoop.

License - functionality of Datavard software (e.g. Datavard Outboard, Datavard Glue) is dependent on a valid license. The license is issued for a specific system and needs to be re-applied after the system refresh.
Storage ID & Profile ID - whole Datavard Outboard archiving solution refers to the Profile ID and Storage ID. These must be identical in the source and target system, otherwise, a manual change in the configuration is necessary - please contact the Datavard representative in such a case.
Hive database - if Datavard Outboard is used and the archives are stored in a Hive database, the source Hive database contents need to be copied into the target Hive database.
LOGSYS ID - Logical system conversion usually runs as a post-processing step during the SAP system refresh. It converts only entries in the standard SAP tables. If the LOGSYS ID does somehow appear in the archives stored in the Hive database, the manual conversion is probably necessary on the Hadoop side.

Browser not supported