SAP Basis Configuration - Server

System description

1.3.9

2021-11-25

SEAL Systems
Copyright

This document and all its parts are protected by copyright. Their use without prior
written consent by SEAL Systems is prohibited and subject to prosecution. In particular,
this applies to reproduction, translation, microfilming and the storing and processing
in electronic systems.
Customers that currently own a valid SEAL Systems software license for the product(s)
described within the contents of this document, may freely distribute this documenta-
tion in electronic form (i. e. CD/File Server or Intranet) for internal usage only.
All product names mentioned are the registered trademarks of the associated compa-
nies.
Copyright 2001-2021 SEAL Systems AG
Lohmühlweg 4
D-91341 Röttenbach
Germany
Contents 3

Contents
1 Introduction...............................................................................................................7
Conventions in this Documentation .....................................................8
Activate the Retrace of your Viewing Path in PDF ...............................9
Variables in this Documentation ........................................................10
Overview of Contents.........................................................................11

Description.......................................................................................................13
2 Overview ................................................................................................................. 15
3 Configuration on the OM server...............................................................................17
3.1 Unicode SAP System - Transfer With sapftp/saphttp.......................................18
3.2 Troubleshooting.............................................................................................. 20
Additional Messages and Debugging..................................................21
Activate DLL Version of sapftp/saphttp in Case of Bottlenecks .........22
4 Configuration on the SAP System.............................................................................23
4.1 Establish the RFC Destination on the SAP System ............................................24
RFC Destination - Basis Data...............................................................25
RFC Destination - Technical Settings ..................................................27
RFC Destination - Unicode Settings ....................................................28
4.2 Security Configuration for RFC and SAP Destinations ...................................... 29
Configure Security for Incoming Connections - reginfo .....................31
Configure Security for Outgoing Connections - secinfo .....................33
Security Configuration - Important Hints ...........................................35
Activate Simulation Mode for Security Configuration........................36
Specify Prefix for Generic RFC Destinations .......................................37
Security Configuration - Background Knowledge ...............................38
4.3 Troubleshooting.............................................................................................. 39
Hints for the Load Balancing...............................................................40
Define the USE_GWHOST Parameter .................................................42
Activate the SAP Gateway Logging.....................................................43
Activate RFC Trace..............................................................................44
5 RFC Destination - Start and Test ...............................................................................45
5.1 Determine the RFC Destinations to be Started ................................................ 46
[ACTIVE] Section .................................................................................47
Parameters .........................................................................................48
5.2 Start the RFC Destinations on the OM Server ..................................................49
5.3 Test the RFC Destination on the SAP System ................................................... 50
6 Integration via Web Service - SAP as Provider ..........................................................51
6.1 Required Authorizations ................................................................................. 52
6.2 Configuration on the Provider System (SAP).................................................... 53
Select the Service ...............................................................................54
Create the Binding on the Provider System .......................................55
Determine URL for WSDL Access........................................................57
6.3 Troubleshooting - Analysis of Web Service Requests .......................................58
Record and Display Web Service Requests ........................................59
Debug Web Service Requests.............................................................60
7 Integration via Web Service - SAP as Consumer........................................................ 61
7.1 Required Authorizations ................................................................................. 62
7.2 Configuration on the Consumer System (SAP) ................................................. 63
Select the ABAP Proxy ........................................................................64

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
4 Contents

Create a Logical Port .......................................................................... 65

Suppress the Message ID Transfer..................................................... 67
Transfer of Large Amounts of Data.................................................... 68
7.3 Advisable Behavior in the Case of Error........................................................... 69
7.4 Troubleshooting.............................................................................................. 71

Reference ........................................................................................................ 73
8 Configuration Files - Reference ................................................................................ 75
8.1 cadrfc.ini - Logon Information ......................................................................... 76
System-/Client-Specific Logon Data................................................... 79
CadRfcUser Parameter....................................................................... 81
CadRfcPassword Parameter............................................................... 82
CadRfcPasswordCoded Parameter .................................................... 83
CadRfcClient Parameter..................................................................... 84
CadRfcLanguage Parameter............................................................... 85
CadRfcDestination Parameter ........................................................... 86
CadDialogNetAddress Parameter ...................................................... 87
8.2 saprfc.ini - Connection Data ............................................................................ 88
Types of RFC Destinations and Module Classification ....................... 90
Parameter Overview .......................................................................... 91
DEST Parameter ................................................................................. 94
TYPE Parameter ................................................................................. 95
ASHOST Parameter ............................................................................ 96
SYSNR Parameter ............................................................................... 97
MSHOST Parameter ........................................................................... 98
GROUP Parameter ............................................................................. 99
GWHOST Parameter ........................................................................ 100
GWSERV Parameter ......................................................................... 101
RFC_TRACE Parameter..................................................................... 102
SEAL_TRACE Parameter ................................................................... 103
ABAP_DEBUG Parameter................................................................. 104
USE_SAPGUI Parameter................................................................... 105
UNICODE Parameter ........................................................................ 106
CODEPAGE Parameter ..................................................................... 107
SNC_MODE Parameter .................................................................... 108
SNC_MYNAME Parameter ............................................................... 109
SNC_PARTNERNAME Parameter ..................................................... 110
SNC_QOP Parameter ....................................................................... 111
SNC_SSO Parameter......................................................................... 112
X509CERT Parameter ....................................................................... 113
8.3 jrfcserver.cfg - RFC Destinations.................................................................... 114
[ACTIVE] Section .............................................................................. 116
[SECTIONNAME] Section.................................................................. 117
9 Configuration Tables - Reference ........................................................................... 120
/seal/bas_cr142 - Define Parameters .............................................. 121
10 Changes ................................................................................................................. 123
Changes with Release 1.3.5 ............................................................. 124
Changes with Release 1.3.3 ............................................................. 125
Changes with Release 1.3.2 ............................................................. 126
Changes with Release 1.3.1 ............................................................. 127
Changes with Release 1.3.0 ............................................................. 128

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Contents 5

Changes with Release 1.2.8 ..............................................................129

Changes with Release 1.2.6 ..............................................................130
Changes with Release 1.2.5 ..............................................................131
Changes with Release 1.2.4 ..............................................................132
Bibliography............................................................................................................... 133
Terminology ............................................................................................................... 134
Abbreviations............................................................................................................. 135
Keywords ................................................................................................................... 136
Index .......................................................................................................................... 138

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
6 Contents

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
1 Introduction 7

1 Introduction

SEAL Systems offers a range of integration modules for the output management subject - connec-
systems from SEAL Systems and SAP including add-ons for SAP PDM, creation tion PLOSSYS/
of digital paper or plot reproduction services for SAP. In order for the output SAP
management system and the SAP system to exchange data, the two systems
must recognize each other.
The following documentation describes the necessary steps to establish
connections between the output management system and the SAP system to
exchange data.

The integration modules from SEAL Systems are defined in the/SEAL/, /SEALC/ subject - repairs
and /DVSREPRO/ namespace. If objects within the namespace must be repaired,
these namespaces must be established explicitly.
The following documentation describes the necessary steps to do this.

You may find information about a secure RFC communication via SNC and SSO reference
and about the HTTPS support in [SAP_BASECONF_SNC_TEC].

This chapter deals with the following topics: in this chapter

→ Conventions in this Documentation, Page 8
→ Activate the Retrace of your Viewing Path in PDF, Page 9
→ Variables in this Documentation, Page 10
→ Overview of Contents, Page 11

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
8 1 Introduction

Conventions in this Documentation

path specifica- The path information given in this documentation is relative to the installation
tion directory of PLOSSYS netdome. This is usually the home directory of the plossys
user. The path information is indicated in Windows notation only in most cases.
This corresponds to the UNIX directory structures unless noted otherwise.

typography The following table lists the typographical conventions employed in this docu-
mentation.

Typographical Meaning
Convention
Consolas File names, paths, commands, menu items, keywords,
special values, short scripts and examples
Consolas italic Parameters; variables that must be replaced by
current values

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
1 Introduction 9

Activate the Retrace of your Viewing Path in PDF

Adobe Reader provides buttons to retrace your viewing path of PDF pages that description
you viewed earlier. This makes reading easier and helps to keep the central
theme.

This is how you activate the buttons for retracing your viewing path in the PDF instructions
documentation as of Adobe Reader 10:

Step Action
1 Activate the following options via the menu:
• View - Show/Hide - Toolbar Items - Page Navigation Show
Tools
• Previous View: Activate
• Next View: Activate

Adobe Reader offers the following buttons to allow you jumping forward and result
backward in the document while showing pages you viewed in the reverse
order that you viewed them:

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
10 1 Introduction

Variables in this Documentation

meaning of Mod‐ The variable ModuleGlobal represents the general module short cuts:
uleGlobal • pls
• dvs

meaning of Mod‐ The variable ModuleSelect represents the individual modules:

uleSelect • convserv
• convservdpf
• dvsviewserv
• filecheck
• jrfcserver
• rfcserver

meaning of Ac‐ The variable Action represents the actions:

tion • start
• status
• stop

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
1 Introduction 11

Overview of Contents

This documentation has two parts: a description and a reference. The first part structure
describes the functionality and the installation process using figures, step-by-
step-procedures and explanatory texts. The second part serves as a detailed
reference guide, containing configuration settings, keywords etcetera.

The description deals with the following topics: description

→ Overview, Page 15
This chapter offers an overview of the relevant configuration files and their
correlation.
→ Configuration on the OM server, Page 17
This chapter describes required configuration settings on the OM server.
→ Configuration on the SAP System, Page 23
This chapter explains the necessary steps in the SAP system to establish an RFC
destination.
→ RFC Destination - Start and Test, Page 45
This chapter explains how the connection for the data exchange between OM
servers and SAP systems is established and tested.
→ Integration via Web Service - SAP as Provider, Page 51
This chapter describes the establishing of an integration via Web service, if SAP
serves as provider.
→ Integration via Web Service - SAP as Consumer, Page 61
This chapter describes the establishing of an integration via Web service, if SAP
serves as consumer.

The reference contains the following chapters: reference

→ Configuration Files - Reference, Page 75
This chapter explains the configuration files which are evaluated to establish a
connection between OM servers and SAP systems.
→ Configuration Tables - Reference, Page 120
This chapter contains an alphabetically sorted list of all configuration tables
relevant for the basis configuration in SAP.

→ Changes, Page 123 changes

This chapter describes the most important changes for each released module
version.

For an easier overview, a bibliography, terminology list, abbreviation list, and lists
index are included at the end of the documentation.

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
12 1 Introduction

Overview of Contents, Continuation

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Description
2 Overview 15

2 Overview

This chapter offers an overview of the relevant configuration files and their introduction
correlation.

The data necessary for the connection between OM servers and SAP systems is data for the
saved in the following files/transactions: con-nection

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
16 2 Overview

Overview, Continuation

coherence The following important correlations exist between these settings:

be-tween the
data

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
3 Configuration on the OM server 17

3 Configuration on the OM server

This chapter describes required configuration settings on the OM server. introduction

The SEAL Setup Suite module queries the required data and inserts the data into SEAL Setup Suite
the configuration files. Alternatively, you can customize the configuration files.
The following chapters describe the customizing.

The configuration on the OM server includes the following steps: general pro-
ceed-ing
Step Description
1 Define the system data of the SAP systems to which the RFC
desti-nations are to be established in
saprfc.ini

→ saprfc.ini - Connection Data, Page 88

2 Define the RFC destinations to be started in
jrfcserver.cfg

→ jrfcserver.cfg - RFC Destinations, Page 114

3 Specify the information for the first-time logon in:
cadrfc.ini

→ cadrfc.ini - Logon Information, Page 76

Hint:
You can modify the cadrfc.ini file on the installation directory.
Afterwards you can distribute this file to the required directories.

This chapter deals with the following topics: in this chapter

→ Unicode SAP System - Transfer With sapftp/saphttp, Page 18
→ Troubleshooting, Page 20

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Unicode SAP System - Transfer With sapftp/saphttp
18 3 Configuration on the OM server

3.1 Unicode SAP System - Transfer With sapftp/

saphttp

description SAP provides different versions of the programs sapftp and saphttp for the
data exchange with Unicode SAP systems and non-Unicode SAP systems. The
correct variant is started via the sapftp/saphttp wrapper program from SEAL
Systems.

requirement - Specify with the parameter UNICODE at the confirmation of the SAP systems in
saprfc.ini saprfc.ini whether the SAP system is a Unicode or a non-Unicode system.

requirement - For each application server, which is used by the message server, a section has
message server to be exist in saprfc.ini with TYPE R, where beside the net address of the appli-
cation server as GWHOST also UNICODE have to be specified correctly.

Unicode SAP sys- If Unicode SAP systems are used only (no mixed operation with non-Unicode
tems only SAP systems, determined via UNICODE in saprfc.ini), sysinit automatically
copies the Unicode version of sapftp and saphttp from SAP to sapftp and
saphttp and replaces the wrapper program. In this case, you may skip this
chapter.

requirement - The sapftp/saphttp wrapper program from SEAL Systems must be located in
wrapper pro- the tools\bin_xxx directory for mixed operation with Unicode SAP systems and
gram non-Unicode SAP systems. Do not replace this program by the sapftp/saphttp
program from SAP!
Execute the following steps to ensure that the program is the wrapper program:

Step Action
1 Determine the program version with:
sapftp -V and saphttp -V

2 The wrapper program from SEAL Systems displays this result:

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Unicode SAP System - Transfer With sapftp/saphttp
3 Configuration on the OM server 19

Unicode SAP System - Transfer With sapftp/

saphttp, Continuation

Step Action
3 Replace the program if the display looks different, for example:

All required DLLs must exist, for instance under Windows in the directory requirement -
tools\bin_xxx icuuc.dll, librfc32u.dll, libsapu16vc.dll, libsapucum.dll, DLLs
sapnwrfc.dll.

The value of UNICODE defined in saprfc.ini is read when starting the RFC desti- effect and pro-
nation. The correct variant of sapftp and saphttp is started. cess

Level Processing
1 The wrapper program sapftp/saphttp from SEAL Systems reads
UNICODE in saprfc.ini.

2 If UNICODE=1:
The wrapper program starts the sapftp_uc/saphttp_uc program
from SAP.
3 If UNICODE=0:
The wrapper program starts the sapftp_nuc/saphttp_nuc program
from SAP.

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Troubleshooting
20 3 Configuration on the OM server

3.2 Troubleshooting

in this chapter This chapter deals with the following topics:

→ Additional Messages and Debugging, Page 21
→ Activate DLL Version of sapftp/saphttp in Case of Bottlenecks, Page 22

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Troubleshooting
3 Configuration on the OM server 21

Additional Messages and Debugging

You can activate additional files with trace messages, if the RFC destinations description
cause difficulties. The debugging of system functions can be activated for RFC
client destinations alternatively.

You activate the trace messages with RFC_TRACE in saprfc.ini. activate trace
messages
Alternatively, you can also activate the RFC trace or SAP Gateway logging within
the SAP system:
→ Activate the SAP Gateway Logging, Page 43
→ Activate RFC Trace, Page 44

You activate the debugging of system functions with ABAP_DEBUG in saprfc.ini. debugging of sys-
tem functions

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Troubleshooting
22 3 Configuration on the OM server

Activate DLL Version of sapftp/saphttp in Case of

Bottlenecks

required if These steps are only required if you want to use the DLL variant of the sapftp
and saphttp programs due to performance reasons.

requirements The following requirement must be fulfilled:

• The sapftp.dll and saphttp.dll files must be located in the
tools\bin_winxx directory.
• In the SAP system, the /seal/bas_dm_be_checkoutviewx function must
exist.

instructions This is how you activate the DLL variant of the sapftp and saphttp programs:

Step Action
1 Edit the following file:
plossys.ini

2 Enter:
[rlistsap]

CAD_CHECKOUT_DLL = Y

3 Enter:
[rlistsap]
BAPI_DOCUMENT_CHECKOUTVIEWX = /SEAL/BAS_DM_BE_CHECKOUTVIEWX
ARC_CHECKOUT_RETRY_ERROR=Y

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
4 Configuration on the SAP System 23

4 Configuration on the SAP System

This chapter explains the necessary steps in the SAP system to establish an RFC introduction
destination.

This chapter deals with the following topics: in this chapter

→ Establish the RFC Destination on the SAP System, Page 24
→ Security Configuration for RFC and SAP Destinations, Page 29
→ Troubleshooting, Page 39

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Establish the RFC Destination on the SAP System
24 4 Configuration on the SAP System

4.1 Establish the RFC Destination on the SAP System

introduction RFC destinations must be established on the SAP system with the sm59 transac-
tion to create the connection to an output management system.

procedure - This is how you create an RFC destination:

over-view
Step Action
1 Start the sm59 transaction.
2 Click Create:

3 → RFC Destination - Basis Data, Page 25

4 → RFC Destination - Technical Settings, Page 27
5 → RFC Destination - Unicode Settings, Page 28
6 Save the settings.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Establish the RFC Destination on the SAP System
4 Configuration on the SAP System 25

RFC Destination - Basis Data

Enter the following basis data: necessary set-

tings
Parameter Value
RFC Destination unique identifier on the SAP system
Example:
SEAL-CONNC-001
Hint - name identical to the program ID:
For reasons of simplicity, the values of RFC Destina-
tion and Program ID at the technical settings should
be identical.
Hint - exception:
When using Conversion Server, a different name must
be specified in order to implement load balancing/
reliability, see scenario 1 in:
→ Hints for the Load Balancing, Page 40
Hint - ambiguous identifier:
If the identifier is ambiguous the SAP system establish
the connections to the OM server where the RFC
server with this identifier is started first.
Connection Type T

Description describing text

Gateway Options - GWHOST as in saprfc.ini

Gateway Host Hint - exception:
When using Conversion Server, this value may be
empty in order to implement load balancing/reli-
ability, see scenario 1 in:
→ Hints for the Load Balancing, Page 40
Gateway Options - GWSERVas in saprfc.ini
Gateway Service Hint - exception:
When using Conversion Server, this value may be
empty in order to implement load balancing/reli-
ability, see scenario 1 in:
→ Hints for the Load Balancing, Page 40

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Establish the RFC Destination on the SAP System
26 4 Configuration on the SAP System

RFC Destination - Basis Data, Continuation

example

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Establish the RFC Destination on the SAP System
4 Configuration on the SAP System 27

RFC Destination - Technical Settings

Switch to the Technical settings tab. requirement

Enter the following technical settings: necessary set-

tings
Parameter Value
Activation Type Registered server program

Registered Server PROGID identifier in the configuration file like jrfc-

Program - Program server.cfg on the OM server
ID Example:
SEAL-CONNC-001
Caution - upper/lower cases:
The designation is case-sensitive!
Caution - allow RFC destinations:
As of EhP7 or kernel 721, destinations are no longer
accepted automatically but have to be allowed manu-
ally in reginfo/secinfo:
→ Security Configuration for RFC and SAP Destina-
tions, Page 29
Hint - naming convention:
The identifier can include letters, numbers, '+', '.', '-',
and '_' characters!

example

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Establish the RFC Destination on the SAP System
28 4 Configuration on the SAP System

RFC Destination - Unicode Settings

requirement Switch to the tab:

• Unicode(as of ECC 6.0)
• MDMP & Unicode (up to release 6.40)
• Special Options (up to release 4.7)

necessary set- Enter the following options:

tings
Parameter Value
as of release • For JRFC Server:
6.40: Unicode

Communication
Type with Target
System

up to release
4.7:

Character Width
in Target System
• For RFC Server and Conversion Server:
Non-Unicode
Explicit Code Page (as of ECC 6.0)

Caution - Conversion Server:

The ConvUtil and ConvServSamp programs on the OM
server are not Unicode-enabled! Therefore, Non-
Unicode has to be activated!

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Security Configuration for RFC and SAP Destinations
4 Configuration on the SAP System 29

4.2 Security Configuration for RFC and SAP Destina-

tions

Versions before EhP7 or kernel 721 automatically accept all destinations by reason
default. As of EhP7 or kernel 721, destinations are no longer accepted automat-
ically but have to be allowed manually.

The security configuration in SAP can be used in order to avoid that unautho- connection types
rized programs or users log on to SAP or connect to outside. The security config-
uration distinguishes the following connection types:
• reginfo - incoming connections
(registrations and communication with registered programs)
• secinfo - outgoing connections
(start attempts)
• proxyinfo - connections from SAP to SAP
(not relevant in the context of SEAL Systems)

The following alternatives are provided at the security configuration: alternatives

• Explicit maintenance of secinfo/reginfo
See description below
• Profile parameter gw/acl_mode (transaction: rz11)
Evaluated if secinfo/reginfo are not maintained
If gw/acl_mode=0, all connections are allowed.
If gw/acl_mode=1, all internal connections are allowed.

This chapter deals with the following topics: in this chapter

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Security Configuration for RFC and SAP Destinations
30 4 Configuration on the SAP System

Security Configuration for RFC and SAP Destina-

tions, Continuation
→ Configure Security for Incoming Connections - reginfo, Page 31
→ Configure Security for Outgoing Connections - secinfo, Page 33
→ Security Configuration - Important Hints, Page 35
→ Activate Simulation Mode for Security Configuration, Page 36
→ Specify Prefix for Generic RFC Destinations, Page 37
→ Security Configuration - Background Knowledge, Page 38

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Security Configuration for RFC and SAP Destinations
4 Configuration on the SAP System 31

Configure Security for Incoming Connections -

reginfo

This is how you specify the accepted registered programs on the SAP gateway instructions - >=
in reginfo for SAP NetWeaver Application Server 7.45 or newer: NW 7.45

Step Action
1 Start the smgw transaction.
2 Select
Goto

→Expert Functions
→External Security
→Maintain ACL Files
→Reginfo File
3 Enter the following line:
P TP=* HOST=<IP address of the SEAL server> CANCEL=*
ACCESS=*
Caution - important hints:
Note the following hints when you enter the security configura-
tion:
→ Security Configuration - Important Hints, Page 35

This is how you specify the accepted registered programs on the SAP gateway instructions - <
in reginfo for SAP NetWeaver Application Server older than 7.45: NW 7.45

Step Action
1 Start the smgw transaction.
2 Select
Goto

→Expert Functions
→External Security
→Display (reginfo)

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Security Configuration for RFC and SAP Destinations
32 4 Configuration on the SAP System

Configure Security for Incoming Connections -

reginfo, Continuation

Step Action
3 If the file does not exist, you can create is via:
Goto

→Expert Functions
→External Security
→Create (reginfo)
Select the destinations, which are to be accepted, and save them
via Save Selected Entries in File.
Example:

4 Enter the following

lines in the usr\sap\system\dveb-
mgs00\data\reginfo.dat file:

P TP=* HOST=<IP address of the SEAL server> CANCEL=*

ACCESS=*
Caution - important hints:
Note the following hints when you enter the security configura-
tion:
→ Security Configuration - Important Hints, Page 35

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Security Configuration for RFC and SAP Destinations
4 Configuration on the SAP System 33

Configure Security for Outgoing Connections -

secinfo

This is how you specify the accepted programs to be started on the SAP gateway instructions - >=
in secinfo for SAP NetWeaver Application Server 7.45 or newer: NW 7.45

Step Action
1 Start the smgw transaction.
2 Select
Goto

→Expert Functions
→External Security
→Maintain ACL Files
→Sec info
3 Enter the following line:
P TP=* USER=* USER-HOST=<IP address of the SEAL server>
HOST=<IP address of the SEAL server>
Caution - important hints:
Note the following hints when you enter the security configura-
tion:
→ Security Configuration - Important Hints, Page 35

This is how you specify the accepted programs to be started on the SAP gateway instructions - <
in secinfo for SAP NetWeaver Application Server older than 7.45: NW 7.45

Step Action
1 Start the smgw transaction.
2 Select
Goto

→Expert Functions
→External Security
→Display (secinfo)

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Security Configuration for RFC and SAP Destinations
34 4 Configuration on the SAP System

Configure Security for Outgoing Connections -

secinfo, Continuation

Step Action
3 If the file does not exist, you can create is via:
Goto

→Expert Functions
→External Security
→Create (secinfo)
Select the destinations, which are to be accepted, and save them
via Save Selected Entries in File.
Example:

4 Enter the following

lines in the usr\sap\system\dveb-
mgs00\data\secinfo.dat file:

P TP=* USER=* USER-HOST=<IP address of the SEAL server>

HOST=<IP address of the SEAL server>
Caution - important hints:
Note the following hints when you enter the security configura-
tion:
→ Security Configuration - Important Hints, Page 35

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Security Configuration for RFC and SAP Destinations
4 Configuration on the SAP System 35

Security Configuration - Important Hints

Note the following issues at the security configuration: note

• The first line has to start with: #VERSION=2
• Each line has to describe a complete rule, which starts with:
• P: Permit
• D: Deny
• If not all destinations/programs are accepted via TP=*, all destinations,
which are used by SEAL Systems products, have explicitly to be specified,
for instance ConvUtil.exe and ConvServSamp.exe.
You also may specify a prefix for generic RFC destinations and only allow
RFC destinations with this prefix:
→ Specify Prefix for Generic RFC Destinations, Page 37
• The items depend on the order. The first matching rule is used and the
reading of the rules is canceled.
For instance, if a rule is found, which denies SEAL Systems connections, the
search is canceled. A rule below, which permits SEAL Systems connections,
is not read and is therefore without effect.
• A rule at the end, which denies all connections, is not required, because it
is set automatically by the system.
Exception: If the simulation mode is activated all connections are allowed.
• The rules have to be reread after changed in order to become effective.
• Activate the simulation mode before major changes in order to check the
effects of the changes.
→ Activate Simulation Mode for Security Configuration, Page 36
Deactivate the simulation mode as soon as you are sure that the security
settings are correct.

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Security Configuration for RFC and SAP Destinations
36 4 Configuration on the SAP System

Activate Simulation Mode for Security Configura-

tion

purpose The simulation mode makes the creating of the security configuration easier. It
specifies a rule at the end, which allows all connections. These are logged with
a specific identifier. The security settings can be modified by means of these
items.
The simulation mode is intended for analysis purposes only and does not
increase in safety because the registration of non-specified connections is
allowed, while a communication via these connections is denied.

instructions This is how you activate the simulation mode:

Step Action
1 Start the transaction: smgw
2 Select:
Goto

→Expert Functions
→Logging
3 Configure the Log Events area according to your wishes and acti-
vate in the Simulation Mode area:
• On: Activate
Hint - effects:
The connection is allowed or denied if a matching rule is found.
If there is no explicit rule for the connection the connection is
allowed and logged in the gateway log file with Z as identifier.
4 Activate the change with Edit→Activate.
5 Deactivate the simulation mode as soon as you are sure that the
security configuration is correct.

alternative Alternatively, you can set the gw/sim_mode profile parameter (transaction:
rz11):
• If gw/sim_mode=0 (default) all connections without any explicit rule are
denied. The simulation mode is deactivated.
• If gw/sim_mode=1 all connections without any explicit rule are allowed. The
simulation mode is activated.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Security Configuration for RFC and SAP Destinations
4 Configuration on the SAP System 37

Specify Prefix for Generic RFC Destinations

The OM server processes start generic RFC destinations (sapftp and saphttp via description
the RFC destination BACK) at the check-out of files from the SAP system. For
these, you can specify a prefix, for instance SEAL, in order to explicitly allow all
destinations with this prefix.

These steps are only required as of EhP7 or kernel 721, if you do not want to required if
allow generally all destinations with * in secinfo/reginfo but you want to
restrict this setting as much as possible.

This is how you specify the prefix for generic RFC destinations on the SAP instructions
system:

Step Action
1 Start the se16n transaction with the sdokprof table.
2 Enter:
• Key: RFC_PREFIX
• Secondary Key: Empty or SAPFTP,SAPHTTP
• Contents:SEAL_ (example)
Example:

Hint - SAP note:

For further information see SAP note 750877.

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Security Configuration for RFC and SAP Destinations
38 4 Configuration on the SAP System

Security Configuration - Background Knowledge

tips & tricks The smgw transaction provides following useful functions additionally:
• Gateway monitor: Goto→Trace→Gateway→Display File
Hints regarding all connections
• Clients logged on on SAP: Goto→Logged on Clients
Overview which clients/systems are logged on with which identification

background Important SAP notes regarding the security configuration on https://

knowledge - SAP support.sap.com/notes:
notes • General:
• 1408081 - Basic settings for reg_info and sec_info
• 1525125 - Update #1 to security note
• 1105897 - GW: reginfo and secinfo with permit and deny ACL
• 1425765 - Generating of sec_info reg_info
• 2061464 - GW: Several smaller corrections in gateway
• 2090489 - GW: Problems with registrations
• secinfo
• 614971 - GW: Changes to the ACL list of the gateway (secinfo)
• recinfo
• 1069911 - GW: Changes to the ACL list of the gateway (reginfo)
• 1592493 - GW: Problems during the reginfo configuration
• proxyinfo
• 910918 - GW: Parameter gw/prxy_info
• Gateway simulation mode
• 1689663 - GW: Simulation mode for reg,sec and prxy_info

background SAP WIKI items regarding the security configuration on https://

knowledge - SAP wiki.scn.sap.com/wiki:
WIKI • Gateway Access Control List:
• https://wiki.scn.sap.com/wiki/display/SI/
Gateway+Access+Control+Lists
• SAP Network Interface and ACL Control
• https://wiki.scn.sap.com/wiki/display/SI/SAP+Network+Inter-
face+and+ACL+control

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Troubleshooting
4 Configuration on the SAP System 39

4.3 Troubleshooting

The following table illustrates typical problems (P) and their approaches (A): typical problems
and their solu-
P: Establishing several application server - what do you need to know tions

A: → Hints for the Load Balancing, Page 40

P: The check-out of files returns an error.
Possibly, the following error is logged on Unicode systems:
[E] E171 Only available with the RFC library from 4.0C
onwards

A: → Define the USE_GWHOST Parameter, Page 42

P: RFC destinations cannot be restored.
Possible cause is the update to EhP7 or kernel 721, where the desti-
nations are no longer accepted automatically.
A: → Security Configuration for RFC and SAP Destinations, Page 29
The simulation mode may simplify the troubleshooting:
→ Activate Simulation Mode for Security Configuration, Page 36
P: RFC destinations - sporadic connection errors or program ProgamId
not registered error

A network component, for example a firewall, closes the TCP/IP

connection without informing the external registered RFC server
program. The external RFC server program waits endlessly for
incoming RFC requests.
A: Activate logging for the SAP gateway to find the cause of the error
(JCO_ERROR_CANCELLED):
→ Activate the SAP Gateway Logging, Page 43
Activate the RFC trace to find the cause of the error (JCO_ERR_COM-
MUNICATION):

→ Activate RFC Trace, Page 44

Avoid idle time in the network, for example by pings at regular
intervals to prevent the TCP-IP connection from being closed, see
SAP note 1332022 or 1494757.

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Troubleshooting
40 4 Configuration on the SAP System

Hints for the Load Balancing

description If an SAP system consists of several application servers, for instance in order to
distribute the workload (load balancing), one of these servers must be specified
as the gateway so that only a single RFC server is started for this connection.

specification The host name of the application server is specified as Gateway Host and the
gateway service as Gateway Service for the load balancing when creating the
RFC destination on the SAP system.

select the ap- It is advisable to select the application server with the least downtime as
pli-cation server Gateway host. This should also be the system's database server.

Caution - If the SAP system is copied, for instance for validation purposes, these gateway
copy of the SAP options must be customized for the new (copied) system to use the RFC desti-
system nation of the second system!

overview SEAL Systems products support load balancing/reliability in different ways:

Product Load Balancing/Reliability

Conversion Server Scenario 1:
Several application servers with one message server
which convert independently - even in case of failure
of another application server.
Solution:
• Establish the RFC destination (sm59 transaction)
without any gateway option.
• Establish one RFC server connection of type R
with different names and application server but
identical program ID for each application server.
Scenario 2:
Load Balancing/Reliability
Solution:
This functionality is provided by the SAP standard
conversion. Several RFC destinations (converter
numbers) can be specified for each conversion.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Troubleshooting
4 Configuration on the SAP System 41

Hints for the Load Balancing, Continuation

Product Load Balancing/Reliability

RFC Server: The functionality described as scenario 2 is
• DMS View Server supported by Conversion Server.
• Core Convert Alternative when using JRFC Server:
You may assign several JRFC Servers via the same
RFC destination.
Hint - restriction:
The JRFC Server which will execute the function is
selected by random. The execution of the individual
functions must therefore be independently. This is
only valid for parts of the BC XDC Interface Imple-
mentation (assignment and status query can be
executed on different servers).
RFC Client RFC clients support the SAP load balancing via
message servers (type B).
CD Installations CD installations from SEAL Systems (type A) do not
support the automatic load balancing.
The conversion files, for instance saprfc.ini and
jrfcserver.cfg, must be modified and saved manu-
ally.

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Troubleshooting
42 4 Configuration on the SAP System

Define the USE_GWHOST Parameter

description The check-out of files from the SAP systems returns an error. One of the reasons
could be that a wrong host name is used at the start of sapftp and saphttp -
required for the check-out - when using several application servers. The deter-
mination of the host name can be influenced by the USE_GWHOST parameter.

instructions This is how you specify the value for the USE_GWHOST parameter:

Step Action
1 Start the /seal/img transaction.
2
Click at
Basis Configuration

→Define Parameters
(table: /seal/bas_cr142)
3 Specify the value of the USE_GWHOST parameter with:
• RFC server destinations: PARA_GWHST: Y or N
• RFC client destinations: PARA_GWHSB: Y or N
Example:

Default is for both parameters: N

background When using sapftp/saphttp, the host name is passed via the GWHOST parameter
knowledge and transferred to librfc23, for instance:
sapftp -xHostName

The HostName is previously determined via the Z_SYS_INFO function for RFC
server destinations and via the SYSTEM_GET_CURRENT_GATEWAY function for RFC
client destinations.
librfc32 uses the transferred value or determine the host name again for itself.
This depends on the value of the USE_GWHOST parameter. With USE_GWHOST Y the
transferred value is used, with USE_GWHOST N the host name is determined
again.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Troubleshooting
4 Configuration on the SAP System 43

Activate the SAP Gateway Logging

If there are problems with RFC destinations, you can activate the RFC trace to description
search for the cause of the error in the generated trace files.

This is how you activate the SAP gateway logging: instructions

Step Action
1 Start the transaction: smgw
2 Select:
Goto

→Expert Functions
→Logging
3 Activate the following options in the Log Events area:
• Network: Activate
• Security - (denied accesses without rules):
Activate
• Registered Programs: Activate
Example:

4 Display the log to search for the cause of the error:

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Troubleshooting
44 4 Configuration on the SAP System

Activate RFC Trace

description If there are problems with RFC destinations, you can activate the RFC trace to
search for the cause of the error in the generated trace files.

alternative Alternatively, you can also activate the RFC trace on the server side:
→ RFC_TRACE Parameter, Page 102
→ SEAL_TRACE Parameter, Page 103

instructions This is how you activate the RFC trace:

Step Action
1 Start the transaction: sm59
2 Switch to the tab: Special Options

3 Activate the following option in the Trace area:

• Set RFC Trace: Activate
Hint - effects:
This automatically activates the Export Trace option in the Trace
Export Methods section and overrides the gw/export_trace_level
profile parameter. See also SAP note 558254.
Example:

result The following trace files are created:

• dev_jco_rfc.log
• jco_rfcPID_UUID.trc

deactivate trace After successful cause analysis, deactivate the option Set RFC Trace again.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
5 RFC Destination - Start and Test 45

5 RFC Destination - Start and Test

This chapter explains how the connection for the data exchange between OM introduction
servers and SAP systems is established and tested.

You can use the following alternatives as start script: start script
• ModuleGlobalstart, for instance dvsstart
• sysstart System, for instance sysstart SAP
• ModuleSelectstart, for instance jrfcserverstart

The connections between the OM servers and the SAP systems are established process at the
as follows: connection start

Level Processing
1 The start script determines the RFC destinations which are to be
started.
2 The start script determines the SAP system data for the RFC desti-
nations which are to be started in saprfc.ini (DESTINATIONS in
ModuleSelect.cfg like jrfcserver.cfg and DEST in saprfc.ini).

3 The start script starts the RFC destinations to the SAP systems.
4 The SAP systems establish the connection to the OM servers via
PROGID as specified in the sm59 transaction.

This chapter deals with the following topics: in this chapter

→ Determine the RFC Destinations to be Started, Page 46
→ Start the RFC Destinations on the OM Server, Page 49
→ Test the RFC Destination on the SAP System, Page 50

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Determine the RFC Destinations to be Started
46 5 RFC Destination - Start and Test

5.1 Determine the RFC Destinations to be Started

alternatives - The RFC destination which are to be started can be specified in the following
overview way:
→ [ACTIVE] Section, Page 47
→ Parameters, Page 48

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Determine the RFC Destinations to be Started
5 RFC Destination - Start and Test 47

[ACTIVE] Section

The [ACTIVE] section in ModuleSelect.cfg like jrfcserver.cfg contains the format

section names with the RFC destinations which are to be started. Each section
which is to be considered is assigned to a server name or the general keyword
SECTION:
• SECTION=SectionName
If a section is assigned to the SECTION keyword it is considered for all
servers.
• HostName=SectionName
If a section is assigned to a server it is considered only for this server.

The [ACTIVE] section is evaluated by all start scripts. evaluated by

The [ACTIVE] section is ignored on these conditions: exception

• The SAP_START_SYSTEM environment variable is specified.
• Section names are specified as parameters at the program start.

The RFC destinations of the DEV, TEST and PROD sections are always to be started example 1
independently of the current server:
jrfcserver.cfg:
[ACTIVE]
SECTION=DEV
SECTION=TEST
SECTION=PROD

The following scenario is to be emulated: example 2

• The RFC destinations of the DEV section are always to be started inde-
pendently of the current server.
• The RFC destinations of the DEV-EXTand PRODsections are to be started only
if SEALSAP1 is the current server.
• The RFC destinations of the DEV-EXTand TEST sections are to be started
only if SEALSAP2 is the current server.
jrfcserver.cfg:
[ACTIVE]
SECTION=DEV
SEALSAP1=DEV-EXT
SEALSAP2=DEV-EXT
SEALSAP2=TEST
SEALSAP1=PROD

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Determine the RFC Destinations to be Started
48 5 RFC Destination - Start and Test

Parameters

format The sections with the RFC destinations which are to be started are specified
directly as parameters at the start. Multiple section names can be specified
separated by blanks.

evaluated by The parameters specified at the start are evaluated only by the scripts Module‐
SelectActionlike jrfcserverstart. The parameters specified at the start have
the highest priority. The SAP_START_SYSTEM environment variable and the
[ACTIVE] section are ignored.

exception The parameters specified at the start are not evaluated by the ModuleGlobalAc‐
tion scripts, like dvsstart, or sysstart System, like sysstart SAP.

example jrfcserverstart PROD

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Start the RFC Destinations on the OM Server
5 RFC Destination - Start and Test 49

5.2 Start the RFC Destinations on the OM Server

You can start the RFC destinations on the OM server as follows: start on the OM
• plsstart or sysstart PLOSSYS netdome server
Starts PLOSSYS netdome and all required RFC destinations
• dvsstart or sysstart SAP
Starts all required RFC destinations
• rfcserverstart, jrfcserverstart, convservstart, convservdpfstart,
filecheckstart, dvsviewserverstart
Starts only the required RFC destinations from the corresponding configu-
ration file like jrfcserver.cfg

You can check the status of the RFC destinations on the OM server as follows: status check on
• plsstatus or sysstatus PLOSSYS netdome the OM server
Displays the status of PLOSSYS netdome and of all required RFC destina-
tions
• dvsstatus or sysstatus SAP
Displays the status of all required RFC destinations
• rfcserverstatus, jrfcserverstatus, convserverstatus, convservdpf-
status, filecheckstatus, dvsviewserverstatus
Displays only the status of the required RFC destinations from the corre-
sponding configuration file like jrfcserver.cfg

Sometimes the RFC server can not be started, if a registration already exists on problems at start
the SAP system. Stop the RFC server and test the connection on the SAP system
to delete the registration; after that it should be possible to start the RFC server
on the OM server again.

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Test the RFC Destination on the SAP System
50 5 RFC Destination - Start and Test

5.3 Test the RFC Destination on the SAP System

instructions This is how you test the RFC destination on the SAP system:

Step Action
1 Start the sm59 transaction.
2 Double-click the RFC destination which you want to test in the list
TCP/IP connections.

3 Click Connection Test.

4 In the case of success, you will get this result:

5 In the case of error, you will get this result:

6 In the case of error, check if the RFC server on the OM server is

actually started and PROGID in jrfcserver.cfg matches the Program
ID in sm59.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
6 Integration via Web Service - SAP as Provider 51

6 Integration via Web Service - SAP as Provider

This chapter describes the establishing of an integration via Web service, if SAP introduction
serves as provider.

Functions that are implemented in different SAP software components may be description
combined via Web service to one process. This chapter describes the steps
required to use the integration via Web service for SEAL Systems products.

→ Integration via Web Service - SAP as Consumer, Page 61 related top-

ics

SAP as provider: overview

This chapter deals with the following topics: in this chapter

→ Required Authorizations, Page 52
→ Configuration on the Provider System (SAP), Page 53
→ Troubleshooting - Analysis of Web Service Requests, Page 58

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Required Authorizations
52 6 Integration via Web Service - SAP as Provider

6.1 Required Authorizations

requirement - The required authorizations have to be assigned to the users via the following
roles roles (transaction: su01; maintenance of the authorizations via the profile
generator with the pfcg transaction):
• User, who administrates the Web service via the SOA manager:
SAP_BC_WEBSERVICE_ADMIN_TEC
• SAP as provider - user, who is used as ABAP service user for the endpoint
on the provider system:
SAP_BC_WEBSERVICE_SERVICE_USER
• SAP as provider - user, who want to debug the Web service requests:
SAP_BC_WEBSERVICE_DEBUGGER
• SAP as consumer - user, who starts the Web service:
SAP_BC_WEBSERVICE_CONSUMER

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Configuration on the Provider System (SAP)
6 Integration via Web Service - SAP as Provider 53

6.2 Configuration on the Provider System (SAP)

This chapter deals with the following topics: in this chapter

→ Select the Service, Page 54
→ Create the Binding on the Provider System, Page 55
→ Determine URL for WSDL Access, Page 57

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Configuration on the Provider System (SAP)
54 6 Integration via Web Service - SAP as Provider

Select the Service

instructions This is how you select the service which is provided by SEAL Systems and for
which you want to establish the integration:

Step Action
1 Start the SOA manager via the soamanager transaction.
2 Switch to the Service Administration tab.
3 Click:
Web Service Configuration

4 Search for the desired service:

Click Search.

5 Select the required service of type Service Definition:

Click the internal name of the service.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Configuration on the Provider System (SAP)
6 Integration via Web Service - SAP as Provider 55

Create the Binding on the Provider System

A binding has to be created on the provider system in order to provide the description
service.

This is how you create a binding on the provider system: instructions

Step Action
1 → Select the Service, Page 54
2 Switch to the Configurations tab.
3 Click Create Binding.

4 Enter the name of the binding and click Next:

• Service Name: SEAL_ZLAD_XML (example)
• Description: Binding for SEAL_ZLAD_XML (example)
• New Binding Name: SEAL_ZLADXML (example)

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Configuration on the Provider System (SAP)
56 6 Integration via Web Service - SAP as Provider

Create the Binding on the Provider System, Continuation

Step Action
5 Specify the required settings and click Finish:
• Communication Security: None (HTTP) activate
• Authentication Method:
No Authentication activate
• ABAP Service User:
Enter user name and password

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Configuration on the Provider System (SAP)
6 Integration via Web Service - SAP as Provider 57

Determine URL for WSDL Access

This is how you determine the URL for the WSDL access on the provider system, instructions
which you need for the creation of the logical port on the consumer system:

Step Action
1 → Select the Service, Page 54
2 Switch to the Configurations tab.
3 Click Open WSDL Generation for Binding.

4 Copy the URL.

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Troubleshooting - Analysis of Web Service Requests
58 6 Integration via Web Service - SAP as Provider

6.3 Troubleshooting - Analysis of Web Service

Requests

in this chapter This chapter deals with the following topics:

→ Record and Display Web Service Requests, Page 59
→ Debug Web Service Requests, Page 60

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Troubleshooting - Analysis of Web Service Requests
6 Integration via Web Service - SAP as Provider 59

Record and Display Web Service Requests

This is how you use the recorder in order to record and display incoming and instructions
outgoing Web service requests on the provider system:

Step Action
1 Start the sicf transaction.
2 Open the service tree for the SERVICE hierarchy type:
sap/bc/srt/rfc/sap/Web service Function/Client/Web service
Name/Binding
Example:
/sap/bc/srt/rfc/seal/zlad_xml/020/zseal_ladxml/
zseal_ladxml

3 Select the menu:

• Edit→Recorder→Activate Recording
for incoming requests on the provider system
• Client→Recorder→Activate Recording
for outgoing requests on the consumer system
4 Enter the desired settings and click Activate.
5 Start the Web service.
6 Display the recording with:
• Edit→Recorder→Display Recording
for incoming requests on the provider system
• Client→Recorder→Display Recording
for outgoing requests on the consumer system

Activate additional trace messages for the troubleshooting on the provider trace messages
system via Edit→Trace→Activate Trace.

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Troubleshooting - Analysis of Web Service Requests
60 6 Integration via Web Service - SAP as Provider

Debug Web Service Requests

requirement → Required Authorizations, Page 52

instructions This is how you debug Web service requests on the provider system:

Step Action
1 Start the sicf transaction.
2 Open the service tree for the SERVICE hierarchy type:
sap/bc/srt/rfc/sap/Web service Function/Client/Web service
Name/Binding
Example:
/sap/bc/srt/rfc/seal/zlad_xml/020/zseal_ladxml/
zseal_ladxml

3 Select the menu:

Edit→Debugging→Activate Debugging

4 Start the Web service.

5 Debug the Web service in the debugger.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
7 Integration via Web Service - SAP as Consumer 61

7 Integration via Web Service - SAP as

Consumer

This chapter describes the establishing of an integration via Web service, if SAP introduction
serves as consumer.

External functionality can be provided via Web service in order to be used by description
SAP as consumer.

→ Integration via Web Service - SAP as Provider, Page 51 related top-

ics

SAP as consumer: overview

This chapter deals with the following topics: in this chapter

→ Required Authorizations, Page 62
→ Configuration on the Consumer System (SAP), Page 63
→ Advisable Behavior in the Case of Error, Page 69
→ Troubleshooting, Page 71

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Required Authorizations
62 7 Integration via Web Service - SAP as Consumer

7.1 Required Authorizations

requirement - The required authorizations have to be assigned to the users via the following
roles roles (transaction: su01; maintenance of the authorizations via the profile
generator with the pfcg transaction):
• User, who administrates the Web service via the SOA manager:
SAP_BC_WEBSERVICE_ADMIN_TEC
• SAP as provider - user, who is used as ABAP service user for the endpoint
on the provider system:
SAP_BC_WEBSERVICE_SERVICE_USER
• SAP as provider - user, who want to debug the Web service requests:
SAP_BC_WEBSERVICE_DEBUGGER
• SAP as consumer - user, who starts the Web service:
SAP_BC_WEBSERVICE_CONSUMER

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Configuration on the Consumer System (SAP)
7 Integration via Web Service - SAP as Consumer 63

7.2 Configuration on the Consumer System (SAP)

The Web service, which you want to use from SAP, is started externally. requirement

This chapter deals with the following topics: in this chapter

→ Select the ABAP Proxy, Page 64
→ Create a Logical Port, Page 65
→ Suppress the Message ID Transfer, Page 67
→ Transfer of Large Amounts of Data, Page 68

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Configuration on the Consumer System (SAP)
64 7 Integration via Web Service - SAP as Consumer

Select the ABAP Proxy

instructions This is how you select the ABAP proxy for which you want to establish the inte-
gration:

Step Action
1 Start the SOA manager via the soamanager transaction.
2 Switch to the Service Administration tab.
3 Click:
Web Service Configuration

4 Search for the desired service:

Click Search.

5 Select the desired consumer proxy from the Consumer Proxy type:
Click the internal name of the consumer proxy.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Configuration on the Consumer System (SAP)
7 Integration via Web Service - SAP as Consumer 65

Create a Logical Port

A logical port has to be created for the communication between the service description
consumer and the external Web service.

This is how you create a logical port: instructions

Step Action
1 → Select the ABAP Proxy, Page 64
2 Switch to the Configurations tab.
3 Click Create - WSDL based Configuration.

4 Enter the data for the logical pro and click Next:
• Logical Port Name: WS_DPF4C_OK (example)
• Logical Port is Default: activate
• Description: Logical port for WS_DPF4C_OK (example)

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Configuration on the Consumer System (SAP)
66 7 Integration via Web Service - SAP as Consumer

Create a Logical Port, Continuation

Step Action
5 Enter the WSDL access settings for the logical pro and click Finish:
• WSDL Base: Via HTTP Access activate
• URL for WSDL Access:
http://server:9125/dpf4c-service-v1.3/
convert?wsdl(example)

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Configuration on the Consumer System (SAP)
7 Integration via Web Service - SAP as Consumer 67

Suppress the Message ID Transfer

The ID transfer of the message ID protocol has to be suppressed. description

This is how you suppress the message ID transfer on the consumer system: instructions

Step Action
1 → Select the ABAP Proxy, Page 64
2 Switch to the Configurations tab.
3 Select the desired logical port and click Edit.
4 Switch to the Messaging tab:
5 Enter:
• Message ID Protocol: Suppress ID Transfer

Caution - default
Up to SAP NetWeaver Application Server 7.3, Suppress ID
Transfer is the default. As of SAP NetWeaver Application Server
7.4, this value has to be specified explicitly:

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Configuration on the Consumer System (SAP)
68 7 Integration via Web Service - SAP as Consumer

Transfer of Large Amounts of Data

description If you transfer large amounts of date in the Web service environment, you can
use the SOAP Message Transmission Optimization Mechanism (MTOM).

requirement MTOM is supported as of SAP release 7.20 or newer without restrictions, see
SAP note 1582187.

instructions This is how you activate the optimized XML transfer for large amounts of date
on the consumer system:

Step Action
1 → Select the ABAP Proxy, Page 64
2 Switch to the Configurations tab.
3 Select the desired logical port and click Edit.
4 Switch to the Transport Settings tab.
5 Enter:
• Optimized XML Transfer: MTOM

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Advisable Behavior in the Case of Error
7 Integration via Web Service - SAP as Consumer 69

7.3 Advisable Behavior in the Case of Error

This is how you check the possible reasons in the case of error step by step: instructions

Step Action
1 Check if the URL is accessible:
• Start the rswf_test_http program (transaction: sa38).

• Enter the URL to be tested and click .

Example:

Result:
A green status display in the first line indicates a successful connec-
tion, a red status display indicates an error.
Example - HTTP connection successful:

Example - HTTP connection is faulty:

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Advisable Behavior in the Case of Error
70 7 Integration via Web Service - SAP as Consumer

Advisable Behavior in the Case of Error, Continuation

Step Action
2 If an error occurs, start the ICM monitor to determine the exact
cause of the error and forward this data to your Technical Project
Manager at SEAL Systems if necessary:
Transaction: smicm
• Display trace file:
Goto→Trace File→Display All
• Save trace file:
Goto→Trace File→Save Locally

Hint - reset trace file:

For a better overview, you can delete the trace file with
Goto→Trace File→Reset and execute the erroneous call again.
Hint - set trace level:
In general, the default trace level is sufficient. You can change it
with Goto→Trace Level→Set and execute the erroneous call
again.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Troubleshooting
7 Integration via Web Service - SAP as Consumer 71

7.4 Troubleshooting

The following table illustrates typical problems (P) and their approaches (A): typical problems
and their solu-
P: The Web service returns an error message of the following type: tions
SOAP:1.023 SRT: Processing error in Internet Communication
Framework: ("ICF Error when receiving the response:
IC-M_HTTP_CONNECTION_FAILED"

Possible cause is that the Web service is not started.

A: Start the Web service.
P: The Web service returns an error message of the following type:
Error while calling DPF Webservice

SoapFaultCode:3 MustUnderstand headers:[{http://

schemas.xmlsoap.org/ws/2004/08/addressing}Action, {http://
schemas.xmlsoap.org/ws/2004/08/addressing}To] are not
understood

Possible cause is that the ID transfer of the message ID protocol is

not suppressed.
A: Suppress the message ID transfer:
→ Suppress the Message ID Transfer, Page 67
P: The Web service returns an error message of the following type:
SOAP:1.001 CX_SXML_PARSE_ERROR: An exception was raised.
Error when parsing an XML stream: '<EOF> reached

Possible cause is that the optimization of the transfer of large

amounts of data is not activated.
A: Optimize the transfer of large amounts of data:
→ Transfer of Large Amounts of Data, Page 68
P: The Web service returns an error message of the following type:
SOAP:1.007 SRT: Unsupported xstream found: ("HTTPCode 502:
Bad Gateway")

Possible cause is that the timeout is too small.

A: Increase the timeout in server\web\apache\conf\workers.proper-
ties:

worker.seal-worker.socket_timeout

P: The Web service returns an error message of the following type:

"HTTPCode 502: Bad Gateway"

Possible cause is that the timeout is too small.

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 Troubleshooting
72 7 Integration via Web Service - SAP as Consumer

Troubleshooting, Continuation

A: Increase the timeout for the HTTP protocol via the smicm transac-
tion with Goto→Services and Service→Change:
Keep Alive (in Sec.)

In addition to that, check the following DPF timeouts:

• apache\conf\httpd.conf: TimeOut 1200 (20 min)
• apache\conf\workers.properties:
worker.seal-workers.socket_timeout 1200 (20 min)
• tomcat\conf\server.xml: connectionTimeout 600000(10 min,
is generally not activated)
P: The Web service returns an error message of the following type:
"ICM_HTTP_TIMEOUT"

Possible cause is that the timeout is too small.

A: Check the following values for the HTTP log via the smicm transac-
tion with Goto→Services and Service→Change:
Keep Alive (in Sec.)

Maximum Processing Time (ProcTimeout)

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Reference
8 Configuration Files - Reference 75

8 Configuration Files - Reference

This chapter explains the configuration files which are evaluated to establish a introduction
connection between OM servers and SAP systems.

This chapter deals with the following topics: in this chapter

→ cadrfc.ini - Logon Information, Page 76
→ saprfc.ini - Connection Data, Page 88
→ jrfcserver.cfg - RFC Destinations, Page 114
jrfcserver.cfg serves as an example for the following configuration files:
• alfilechecker.cfg
• alviewserver.cfg
• convserv.cfg
• convservdpf.cfg
• dvsviewserver.cfg
• filecheck.cfg
• jrfcserver.cfg
• rfcserver.cfg

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 cadrfc.ini - Logon Information
76 8 Configuration Files - Reference

8.1 cadrfc.ini - Logon Information

introduction This chapter contains the reference information about the cadrfc.ini configu-
ration file.

requirement The cadrfc.ini file is evaluated for RFC client connections. Other RFC server
connections ignore this file.

ASCII/Unicode Within cadrfc.ini only ASCII characters are supported. Unicode characters are
not supported.

location The cadrfc.ini file is located in the following directory:

client\dvs...\bin_...

hint - gXnet- For gXnetplot, the file is located in:

plot $GRALPLOTLIB/PDM (servermenu - c - cdl - cd PDM)

purpose The configuration file contains the necessary logon data which is evaluated by
the BAPI and CAD interface.
The interactive RFC clients use the logon data as default values for the initial
logon dialog.
The remaining RFC clients and RFC servers use the logon information for the
initial logon when they start up. Later logons use the information saved in the
job files (repro lists).

structure You can specify general as well as system- and client-specific logon data:
• General logon data is specified in the configuration file without section
name.
• System- and client-specific logon data is specified in separate sections
subsequent to the general logon data:
[SAP\SystemName\Client] or [SAP\SystemName]
Example:
[SAP\W74\020]or[SAP\W74]

example Extract of an example for cadrfc.ini:

*----------------------------------------------------

* SAP logon parameters

*----------------------------------------------------

CadRfcUser SEALCPIC

CadRfcPassword <SAPPWD>

#CadRfcPasswordCoded 0xe3f0e9c6604b14b3

#CadRfcClient 010

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
cadrfc.ini - Logon Information
8 Configuration Files - Reference 77

cadrfc.ini - Logon Information, Continuation

CadRfcLanguage EN

*----------------------------------------------------

* Connection parameters

*----------------------------------------------------

* Logical destination

CadRfcDestination W46

...

*----------------------------------------------------

* Parameters specific for Dialog interface (SapConnc)

*----------------------------------------------------

...

* important for check-in/check-out

CadDialogNetAddress DEFAULT

*----------------------------------------------------

* TRACE parameters 0 - set trace off | 1 - on

*----------------------------------------------------

CadRfcTrace 0

CadTraceDir

*----------------------------------------------------

* ABAP debug parameter 0 - set debug off | 1 - on

*----------------------------------------------------

CadRfcAbapDebug 0

...

*----------------------------------------------------

* system/client-specific logon data

*----------------------------------------------------

[SAP\W74]

CadRfcUser SEALPE

CadRfcPasswordCoded 0xe3f0e9c6604b14b3

CadRfcClient 010

...

Only a couple of parameters of the configuration file must be adjusted to the customize
current system environment. Only these parameters are described below. The

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 cadrfc.ini - Logon Information
78 8 Configuration Files - Reference

cadrfc.ini - Logon Information, Continuation

remaining parameters have reasonable defaults and do not need to be

adjusted.

restart You must restart the DMS Rlist RFC client after you have changed parameters in
cadrfc.ini.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
cadrfc.ini - Logon Information
8 Configuration Files - Reference 79

System-/Client-Specific Logon Data

The rlistsap, sapcli, omscli and oms_server programs must be linked with requirement
sapini.c version 1.14 or newer.

To check the correct version, for example of rlistsap, execute the following
steps:

Step Action
1 Enter:
what rlistsap | grep sapini.c

2 As result must be displayed:

SAP-CAD $Id: sapini.c,v 1.14 2005/10/12 ...

The requirement is fulfilled if the version is 1.14 or newer. Other-

wise contact your Technical Project Manager at SEAL Systems.

With regard to DMS Rlist for the initial login to the SAP system during the start restriction
of DMS Rlist, only the login data in the general (system and client independent)
section of the file cadrfc.ini is used. The system- and client-specific login infor-
mation is only evaluated during the processing of repro list jobs at runtime.

System- and client-specific logon data is specified in separate sections: structure

[SAP\SystemName\Client] or [SAP\SystemName]

Example:
[SAP\W74\020]or[SAP\W74]

The sections containing the system- and client-specific logon data must be Caution - at
located at the end of the file after the general logon information. the end

The current system and the current client specified in the order file (repro list) system/client
are compared with the configuration entries in cadrfc.ini to determine the comparison
user to be used for logon.

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 cadrfc.ini - Logon Information
80 8 Configuration Files - Reference

System-/Client-Specific Logon Data, Continuation

section determi- The section of cadrfc.ini which is to be used for the current system/client
nation specified in the order file is determined as follows:

example The subsequent example demonstrates which user is used for logon dependent
on the system/client in the job data.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
cadrfc.ini - Logon Information
8 Configuration Files - Reference 81

CadRfcUser Parameter

The CadRfcUser parameter determines the user used by the RFC client or RFC meaning
server to logon on the SAP system.

The following requirements must be fulfilled for a successful logon: requirement

• The specified user must be identically configured on all SAP systems.
• The user name must be entered in capitals.
• The interactive RFC clients require a dialog user.
• For security reasons, a system user is generally used for logon by the
remaining RFC clients, for instance DMS loader and DMS Rlist, and the RFC
servers.
Exception:
If USE_SAPGUI in saprfc.ini is specified as 1 or 2 a dialog user must be
used!

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 cadrfc.ini - Logon Information
82 8 Configuration Files - Reference

CadRfcPassword Parameter

meaning The CadRfcPassword parameter specifies the uncoded password used by the
RFC client and RFC server to logon on the SAP system.

alternative The password can be specified in a coded form with the CadRfcPasswordCoded
parameter. For security reasons, the coded passwords are to be preferred.

requirement The CadRfcPassword parameter is ignored as soon as a coded password is spec-

ified with the parameter CadRfcPasswordCoded.

example The item looks as follows:

CadRfcPassword xyz

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
cadrfc.ini - Logon Information
8 Configuration Files - Reference 83

CadRfcPasswordCoded Parameter

The CadRfcPasswordCoded parameter specifies the coded password used by the meaning
RFC client and RFC server to logon on the SAP system. This is the more secure
variant compared to the previous CadRfcPasswordparameter.

This is how you create and save a coded password: code the
pass-word
Step Action
1 Execute the program to encode the password:
sealencrypt.exe configpassword

2 Enter the created coded password in the cadrfc.ini file.

Example:
CadRfcPasswordCoded e3f0e9c6604b14b3

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 cadrfc.ini - Logon Information
84 8 Configuration Files - Reference

CadRfcClient Parameter

meaning The CadRfcClient parameter determines the client used by the RFC client and
RFC server to logon on the SAP system.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
cadrfc.ini - Logon Information
8 Configuration Files - Reference 85

CadRfcLanguage Parameter

The CadRfcLanguage parameter specifies the language used by the RFC client meaning
and RFC server to logon on the SAP system.
All two-character ISO-639-1 language codes installed on the SAP system can be
specified as logon language. ISO-639-2B/T and ISO-639-3 are not supported.

The item looks as follows: example

CadRfcLanguage EN

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 cadrfc.ini - Logon Information
86 8 Configuration Files - Reference

CadRfcDestination Parameter

meaning The CadRfcDestination parameter specifies the SAP system on which the RFC
client and RFC server log on.

example The item looks as follows:

CadRfcDestination W74

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
cadrfc.ini - Logon Information
8 Configuration Files - Reference 87

CadDialogNetAddress Parameter

The CadDialogNetAddress parameter specifies the host name of the local meaning
machine. This is used for check-in and check-out files.

If the CadDialogNetAddress parameter is not specified the value of the HOSTNAME environment
(Windows) or DISPLAY (Unix) environment variable is used instead. variable

The following value is used as default: default

CadDialogNetAddress DEFAULT

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 saprfc.ini - Connection Data
88 8 Configuration Files - Reference

8.2 saprfc.ini - Connection Data

introduction This chapter contains the reference information about the saprfc.ini configu-
ration file.

requirement: AS- Within saprfc.ini only ASCII characters are supported. Unicode characters are
CII/Unicode not supported.

location The saprfc.ini file is located in the following directory:

client\dvs...\bin_... (RFC client connection)

server\sapserv\conf (RFC server connection)

hint - gXnet- For gXnetplot, the file is located in:

plot $GRALPLOTLIB/PDM (servermenu - c - cdl - cd PDM)

contents The configuration file contains parameter items with the system data for the
individual SAP systems. This data is used to establish the RFC destinations from
OM-Servers to the SAP systems.

determine sys- The current SAP system data like instance number, route string and so on can
tem data be determined by the saplogon.ini file.
If SAP GUI is installed, the file is located under Windows in the c:\winnt direc-
tory. If the SAPLOGON_INI_FILE environment variable is set, the file it specifies
(e.g., a centrally stored file) will be used.
If SAP GUI is installed, you can display the SAP system data also on SAP logon
via Properties (right mouse button) or Change entry (button).
Further system data, like the information whether it is a Unicode SAP system,
can be determined for each system via the following program execution:
tools\bin_winnxx\sap_conn_checkerParameter

structure Dependent on the type of RFC destination - client or server - different param-
eter entries in saprfc.ini are required. All parameter entries concerning one
type are grouped as one block without section name in the configuration file.

in this chapter This chapter deals with the following topics:

→ Types of RFC Destinations and Module Classification, Page 90
→ Parameter Overview, Page 91
→ DEST Parameter, Page 94
→ TYPE Parameter, Page 95
→ ASHOST Parameter, Page 96
→ SYSNR Parameter, Page 97
→ MSHOST Parameter, Page 98

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
saprfc.ini - Connection Data
8 Configuration Files - Reference 89

saprfc.ini - Connection Data, Continuation

→ GROUP Parameter, Page 99

→ GWHOST Parameter, Page 100
→ GWSERV Parameter, Page 101
→ RFC_TRACE Parameter, Page 102
→ SEAL_TRACE Parameter, Page 103
→ ABAP_DEBUG Parameter, Page 104
→ USE_SAPGUI Parameter, Page 105
→ UNICODE Parameter, Page 106
→ CODEPAGE Parameter, Page 107
→ SNC_MODE Parameter, Page 108
→ SNC_MYNAME Parameter, Page 109
→ SNC_PARTNERNAME Parameter, Page 110
→ SNC_QOP Parameter, Page 111
→ SNC_SSO Parameter, Page 112
→ X509CERT Parameter, Page 113

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 saprfc.ini - Connection Data
90 8 Configuration Files - Reference

Types of RFC Destinations and Module Classifica-

tion

type of RFC desti- The following types of RFC destinations can be distinguished:
nations • RFC client via application server (type A)
• RFC client via message server (type B)
• RFC server via SAP gateway (type R)

modules and The modules from SEAL Systems can be classified in RFC client and RFC server
types modules as follows:

RFC Client RFC Server

DMS Rlist DMS Loader
DMS Scan Conversion Server
JSAPcli, SAPcli RFC Server, JRFC Server, for instance for
• DMS Loader/ABAP
• DMS View Server
• PDF Longlife Suite - SAP Integration

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
saprfc.ini - Connection Data
8 Configuration Files - Reference 91

Parameter Overview

Some parameters are evaluated for all connection types. In addition to these validity
general parameters there are parameters which are only important for special
connection types.

The following table presents an overview of which parameters are evaluated overview
for which connection type:

Parameters RFC Client RFC Client RFC Server

Application Server Message Server Gateway
DEST X X X

TYPE A B R

ASHOST X - -

SYSNR X - -

MSHOST - X -

GROUP - X -

GWHOST - - X

GWSERV - - X

RFC_TRACE X X X

SEAL_TRACE - - X

ABAP_DEBUG X X -

USE_SAPGUI X X -

UNICODE - - X

CODEPAGE - - X

SNC_MODE X X X

SNC_MYNAME X X X

SNC_PARTNER- X X -
NAME

SNC_QOP X X X

SNC_SSO X X X

X509CERT X X X

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 saprfc.ini - Connection Data
92 8 Configuration Files - Reference

Parameter Overview, Continuation

example The following table contains example parameter entries for the different
connection types:

Type Items
RFC client DEST=W74

(application server) TYPE=A

ASHOST=/H/SEALDOS3/H/sapt60-1

SYSNR=00

RFC_TRACE=0

ABAP_DEBUG=0

USE_SAPGUI=0

SNC_MODE=1

SNC_MYNAME=p:CN=SEALRFC, OU=SEALSAP, O=SEAL, C=DE

SNC_PARTNERNAME=p:CN=T6B, OU=SEALSAP, O=SEAL, C=DE

SNC_QOP=3

SNC_SSO=1

X509CERT=c:\seal\customer\server\sapserv\conf\sec\SEAL-RFC.crt

RFC client DEST=W74

(message server) TYPE=B

MSHOST=/H/SEALDOS3/H/sapt60-2

GROUP=Standard

RFC_TRACE=0

ABAP_DEBUG=0

USE_SAPGUI=0

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
saprfc.ini - Connection Data
8 Configuration Files - Reference 93

Parameter Overview, Continuation

Type Items
RFC server gateway DEST=W74RFC

TYPE=R

GWHOST=/H/SEALDOS3/H/sapt60-3

GWSERV=sapgw00

RFC_TRACE=0

SEAL_TRACE=1

UNICODE=1

CODEPAGE=UTF-8

SNC_MODE=1

SNC_MYNAME=p:CN=SEALRFC, OU=SEALSAP, O=SEAL, C=DE

SNC_QOP=8

SNC_SSO=1

For each RFC client, only one item is allowed, either one with TYPE=A for appli- Caution - RFC
cation server or one with TYPE=B for message server. client

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 saprfc.ini - Connection Data
94 8 Configuration Files - Reference

DEST Parameter

meaning The DEST parameter contains the unique identifier for the SAP system.
It refers to the DESTINATIONS item in the configuration file like jrfcserver.cfg.
It is used to determine the SAP system data for the RFC destination which
should be established.

naming con- The identifier should indicate the SAP system and the type of the RFC destina-
ven-tion tion. The following naming convention is advisable where W74 is used as
example of an SAP system name:

DEST Value Using for

W74 RFC client connections via application server

W74 RFC client connections via message server

W74RFC RFC server connections via SAP gateway

length RFC server as of 1.3.3 or newer allows identifiers with a maximum of 32

char-acters. Lower versions only support a maximum of 8 characters.

validity The parameter DEST is evaluated for all destination types.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
saprfc.ini - Connection Data
8 Configuration Files - Reference 95

TYPE Parameter

The TYPE parameter identifies the connection type. meaning

The following connection types are available: values

• A
RFC client connections via application server
The connection via an application server is the standard connection type
for RFC clients. This type is used by all interactive modules and by the
modules DMS Rlist and DMS Loader.
• B
RFC client connections via message server
The connection via a message server is available for RFC clients as an alter-
native to the connection via an application server. It is rarely used. It can be
used for load distribution purposes (load balancing) to distribute the regis-
tration via the message server to several application servers.
• R
RFC server connections via SAP gateway
RFC server or conversion server register with an intermediate SAP gateway
where they then wait for queries from the SAP system or other RFC clients.
Usually, an SAP gateway is running on each application server.

Depending on the connection type, a port must be assigned to the instance Caution - in-
number of the SAP system (xx) in the winnt\system32\drivers\etc\services stance number/
system file: port
• Type A, RFC client connections via application server
sapdpxx32xx/tcp
sapgwxx 33xx/tcp
• Type B, RFC client connections via message server
sapmsgxx 36xx/tcp
• Type R, RFC server connections via SAP gateway
sapgwxx 33xx/tcp

Items in the saprfc.ini file starting with sapgw are automatically mapped to the hint - auto-
correct port, for instance sapgw00 to 3300 or sapgw01 to 3301. It is not required matic mapping
to map them explicitly in the system file.

The TYPE parameter is evaluated for all destination types. validity

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 saprfc.ini - Connection Data
96 8 Configuration Files - Reference

ASHOST Parameter

meaning The ASHOST parameter contains the net address of the application server.

system data The net address is composed of SAP Router String (SAP logon) or the [Router]
section(saplogon.ini) and Application Server (SAP logon) or the [Server]
section (saplogon.ini).

hint - sym- If the router string contains a symbolic port, for instance /S/sapgw01, this port
bolic port has to be assigned in the system file:
→ TYPE Parameter, Page 95

validity The ASHOST parameter is evaluated only for the following destination types:
• Type A, RFC client connections via application server

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
saprfc.ini - Connection Data
8 Configuration Files - Reference 97

SYSNR Parameter

The SYSNR parameter contains the instance number (up to release 4.7: system meaning
number) of the application server.

The parameter is displayed as Instance Number (SAP logon) or in the [Database] system data
section (saplogon.ini).

The SYSNR parameter is evaluated only for the following destination types: validity
• Type A, RFC client connections via application server

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 saprfc.ini - Connection Data
98 8 Configuration Files - Reference

MSHOST Parameter

meaning The MSHOST parameter contains the net address of the message server.

system data The net address is composed of SAP Router String (SAP logon) or the [Router]
section (saplogon.ini) and the [MSSrvName] section (saplogon.ini).

hint - sym- If the router string contains a symbolic port, for instance /S/sapmsg01, this port
bolic port has to be assigned in the system file:
→ TYPE Parameter, Page 95

validity The MSHOST parameter is evaluated only for the following destination types:
• Type B, RFC client connections via message server

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
saprfc.ini - Connection Data
8 Configuration Files - Reference 99

GROUP Parameter

The GROUP parameter contains the group identifier of the message server. meaning

The parameter is displayed in the [Server] section (saplogon.ini). system data

The GROUP parameter is evaluated only for the following destination types: validity
• Type B, RFC client connections via message server

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 saprfc.ini - Connection Data
100 8 Configuration Files - Reference

GWHOST Parameter

meaning The GWHOST parameter contains the net address of the SAP gateway. This is
generally identical with the application server.

system data The net address is composed of SAP Router String (SAP logon) or the [Router]
section (saplogon.ini) and Application Server (SAP logon) or the [Server]
section (saplogon.ini).

hint - sym- If the router string contains a symbolic port, for instance /S/sapgw01, this port
bolic port has to be assigned in the system file:
→ TYPE Parameter, Page 95

validity The GWHOST parameter is evaluated only for the following destination types:
• Type R, RFC server connections via SAP gateway

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
saprfc.ini - Connection Data
8 Configuration Files - Reference 101

GWSERV Parameter

The GWSERV parameter contains the group identifier of the SAP gateway. meaning

The parameter is composed of sapgw and Instance Number (SAP logon) or the system data
item in the [Database] section (saplogon.ini).

The GWSERV parameter is evaluated only for the following destination types: validity
• Type R, RFC server connections via SAP gateway

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 saprfc.ini - Connection Data
102 8 Configuration Files - Reference

RFC_TRACE Parameter

meaning The RFC_TRACE parameter activates or deactivates the trace messages.

location and Trace messages are saved on the application server in the log directory in files
name with the following names:
jco_rfc_*.trc

dev_rfc*

If the CPIC_TRACE environment variable is set to a value >0, the following file is
created additionally:
CPIC*

Caution - size Files with the trace messages can quickly become extremely large; therefore
the trace messages should only be activated for test purposes. By default, it is
advisable to deactivate the trace messages.

values The following values are available:

• 0 The trace messages are deactivated.
• 1 Error messages
• 2 Additional warnings
• 3 Additional information
• 4 Additional process trace
• 5 Additional extended process trace
• 6 Additional restricted data trace
• 7 Additional data trace with metadata
• 8 Additional complete data trace with metadata

validity The RFC_TRACE parameter is evaluated for all destination types.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
saprfc.ini - Connection Data
8 Configuration Files - Reference 103

SEAL_TRACE Parameter

The SEAL_TRACE parameter activates or deactivates additional information in meaning

the log file and the creation of HTML files containing the transferred data from
and to SAP.

The following values are available: values

• 0 No additional information in the log file
• 1 The connection status and memory status is logged additionally
• 2 HTML files are created additionally

HTML files with the transferred data can quickly become extremely large; Caution -
therefore the creation of HTML files should only be activated for trouble- number
shooting. By default, it is advisable to set SEAL_TRACE to 0 or 1.

Default is 0. default

The SEAL_TRACE parameter is evaluated only for the following destination types: validity
• Type R, RFC server connections via SAP gateway

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 saprfc.ini - Connection Data
104 8 Configuration Files - Reference

ABAP_DEBUG Parameter

meaning The ABAP_DEBUG parameter activates or deactivates the debugging of system

functions.

requirement The USE_SAPGUI parameter must be set to 1 or 2 to enable the debugging.

values The following values are available:

• 0
The debugging of the system functions is deactivated. This is the standard
case.
• 1
The debugging of the system functions is activated for test purposes.

validity The ABAP_DEBUG parameter is evaluated only for the following destination types:
• Type A, RFC client connections via application server
• Type B, RFC client connections via message server

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
saprfc.ini - Connection Data
8 Configuration Files - Reference 105

USE_SAPGUI Parameter

The USE_SAPGUI parameter determines if SAP GUI is used for communication. In meaning
addition to that it specifies if the dialogs are minimized after the end of the
function.

The following requirements have to be fulfilled: requirement

• USE_SAPGUI must be set to 2 for the modules DMS Repro and DMS Scan.
• If USE_SAPGUI is set to 1 or 2 a dialog user must be specified in cadrfc.ini!
A system user causes error.

The following values are available: values

• 0
SAP GUI is not used for communication.
• 1
SAP GUI is used for communication. The dialogs remain open after the end
of the function.
• 2
SAP GUI is used for communication. The dialogs are minimized after the
end of the function.

The USE_SAPGUI parameter is evaluated only for the following destination types: validity
• Type A, RFC client connections via application server
• Type B, RFC client connections via message server

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 saprfc.ini - Connection Data
106 8 Configuration Files - Reference

UNICODE Parameter

meaning The UNICODE parameter specifies if the SAP system is a Unicode or non-Unicode
system.
By means of this parameter the correct version of the programs sapftp and
saphttp is determined.

values The following values are available:

• 0 The SAP system is a non-Unicode system.
• 1 The SAP system is a Unicode system.

code page For Unicode systems, the coding can be specified with CODEPAGE:
→ CODEPAGE Parameter, Page 107

validity The UNICODE parameter is evaluated only for the following destination types:
• Type R, RFC server connections via SAP gateway

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
saprfc.ini - Connection Data
8 Configuration Files - Reference 107

CODEPAGE Parameter

The CODEPAGE parameter specifies the coding for Unicode systems. meaning

The code page is only evaluated in the case UNICODE=1. interrelation

The default code page is UTF-8. These is used in the following cases: default
• Neither a general code page is specified in saprfc.ini nor a specific code
page at the function start.
• The specified code page is not supported by Java.
• The specified code page is UTF-* (* = 7, 16, 16BE, 16LE, 32, ...), because
only UTF-8 is supported.

The CODEPAGE parameter is only evaluated for the following destination types: validity
• Type R, RFC server connections via SAP gateway

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 saprfc.ini - Connection Data
108 8 Configuration Files - Reference

SNC_MODE Parameter

meaning The SNC_MODE parameter activates and deactivates SNC (activation sign).

values The following values are available:

• 0 SNC is deactivated.
• 1 SNC is activated.

default Default is 0.

validity The SNC_MODE parameter is evaluated for all destination types.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
saprfc.ini - Connection Data
8 Configuration Files - Reference 109

SNC_MYNAME Parameter

The SNC_MYNAME parameter contains the name of the user who executes remote meaning
function calls.

The default name is the name which is determined by the security product for default
the current user.

The name must use the following format: format

p:SEAL Server ‐ DistinguishedName from SEALRFC.pse

p:CN=UniqueName, OU=Department, O=Company, C=CountryKey example

p:CN=SEALRFC, OU=SEALSAP, O=SEAL, C=DE

The SNC_MYNAME parameter is evaluated for all destination types. validity

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 saprfc.ini - Connection Data
110 8 Configuration Files - Reference

SNC_PARTNERNAME Parameter

meaning The SNC_PARTNERNAME parameter contains the name of the communication

partner (application server).

format The name must use the following format:

p:SAP System ‐ DistinguishedName

example p:CN=UniqueName, OU=Department, O=Company, C=CountryKey

p:CN=SEALRFC, OU=SEALSAP, O=SEAL, C=DE

validity The SNC_PARTNERNAME parameter is evaluated only for the following destination
types:
• Type A, RFC client connections via application server
• Type B, RFC client connections via message server

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
saprfc.ini - Connection Data
8 Configuration Files - Reference 111

SNC_QOP Parameter

The SNC_QOP parameter specifies the protection level (quality of protection). meaning

The following values are available: values

• 1: Use authentication only
• 2: Use integrity protection (authentication)
• 3: Use confidentiality protection (integrity and authentication)
• 8: Use default values
• 9: Use maximum protection

The default security level is 3 for RFC client connections via application server default
(TYPE=A) or message server (TYPE=B) and 8 for RFC server connections via SAP
gateway (TYPE=R).

The SNC_QOP parameter is evaluated for all destination types. validity

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 saprfc.ini - Connection Data
112 8 Configuration Files - Reference

SNC_SSO Parameter

meaning The SNC_SSO parameter activates or deactivates the single sign-on mechanism
of SNC. This allows to log on on the SAP ABAP backend with a user different
form the SNC identity, while SNC is used for the encryption of the network
communication.

requirement A minimum kernel patch of the SAP system is required, see SAP note 1701870.

values The following values are available:

• 0 SSO is deactivated.
• 1 SSO is activated.

default The default value is 1.

validity The SNC_SSO parameter is evaluated for all destination types.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
saprfc.ini - Connection Data
8 Configuration Files - Reference 113

X509CERT Parameter

The X509CERT parameter contains the certificate name if the logon with certifi- meaning
cate (SSO, single sign-on) is activated.

The certificate must be in the Based64 file format, in one line without BEGIN and format
END sequence.

The default name is: default

%PLSROOT%\server\sapserv\conf\sec\SEALRFC.crt

The X509CERT parameter is evaluated only for the following destination types: validity
• Type A, RFC client connections via application server

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 jrfcserver.cfg - RFC Destinations
114 8 Configuration Files - Reference

8.3 jrfcserver.cfg - RFC Destinations

introduction This chapter contains the reference information about the jrfcserver.cfg
configuration file.

location The jrfcserver.cfg file is located in the following directory:

server\sapserv\conf

The directory and the file can be specified differently from the standard by the
RUNTIME_CONFIG environment variable and the -cfgfile parameter.

hint - gXnet- For gXnetplot, the file is located in:

plot servermenu - c - cdl - cd PDM

structure The configuration file is divided into separate sections.

→ [ACTIVE] Section, Page 116
[ACTIVE] is the first section. Only section names which are specified in the
section [ACTIVE] are regarded at the start of the RFC destinations.
→ [SECTIONNAME] Section, Page 117
The remaining sections with exception of [ACTIVE] can be named user-defined.

example Example for jrfcserver.cfg:

[ACTIVE]

SEALSAP1 = DEV

SEALSAP1 = T6A

SEALSAP2 = PROD

[DEV]

DESTINATIONS = “X74RFC“

PROGID = SEAL-BCXDC-001

PROGID = SEAL-BCXDC-002

[T6A]

DESTINATIONS = “T6ARFC“

PROGID = SEAL-BCXDC-001 3

RLIGATE = %PLSDATA%\io\rligate

[PROD]

DESTINATIONS = “W74RFC“

PROGID = SEAL-BCXDC-001 5

PROGID = SEAL-BCXDC-002 3

PROGID = SEAL-BCXDC-003

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
jrfcserver.cfg - RFC Destinations
8 Configuration Files - Reference 115

jrfcserver.cfg - RFC Destinations, Continuation

RLIGATE = %PLSDATA%\io\stargate

XMS = 128

XMX = 512

'#' and '!' are supported as comment characters. Within one file, only one of comment char-
these comment characters has to be used. A combination of '#' and '!' causes acter
an error at the start.
SEAL Systems provides the update_rfc_cfg.pl script (install\rfc directory) in
order to replace ’!’ by ’#’.

A restart of JRFC Server is required after modifications in jrfcserver.cfg. restart

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 jrfcserver.cfg - RFC Destinations
116 8 Configuration Files - Reference

[ACTIVE] Section

contents This section lists the names of the sections containing the RFC destinations
which are to be started.

exceptions The [ACTIVE] section is ignored on these conditions:

1. The SAP_START_SYSTEM environment variable is specified. In this case the
sections names specified in the environment variable are evaluated for the
start of the RFC destinations.
2. Section names are specified as parameters when directly executing jrfc-
serverstart. In this case, also the SAP_START_SYSTEM environment variable
is ignored.

parameters The following section describes the available parameters in the [ACTIVE]
section.

ServerName or This name refers to the a section in jrfcserver.cfg which contains further
SECTION data.
The section may contain ServerName items or SECTION items. A mix of both is not
allowed.
The section may contain multiple ServerName or SECTION items. If ServerName
items exist, only those are considered whose name matches the current server
name. If SECTION items exist, all items are considered. For each considered item,
a JRFC Server main process is started. Threads related to this main process are
started for all RFC destinations which are listed as PROGID in the associated
section.
The value is a string.
• PROD
Name of the section in jrfcserver.cfg containing further data
Default: None

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
jrfcserver.cfg - RFC Destinations
8 Configuration Files - Reference 117

[SECTIONNAME] Section

This section contains the relation to the system data in saprfc.ini and a list of contents
the RFC destinations which are to be started with relation to their definitions in
the SAP system via the sm59 transaction.

The SAP system data must only be defined once in saprfc.ini even if several advantage - SAP
RFC destinations (PROGID) to one SAP system are started. system data only
once

For all RFC destinations of one section, a JRFC Server main process is started and advantage - sep-
stopped. The subdivision into individual sections allows the start of some arate start/stop
groups of RFC destinations while other remain stopped.

The name of the log files are composed of: advantage - sep-
arate log files
ModuleName.SECTIONNAME_Number.log, for instance: jrfcserver.PROD_0.log

Thus the log files contain only messages of a group of RFC destinations. It is
easier to keep track of the status of one RFC destination.

If you want to establish RFC destinations to Unicode and non-Unicode systems, Unicode and
you must specify these destination in separate sections. Collect all RFC destina- non-Unicode
tions to non-Unicode systems in a separate section and all RFC destinations to
Unicode systems in another section. In this case, one main process is executed
for the non-Unicode systems and another main process is executed for the
Unicode systems.

The [SECTIONNAME] section is only evaluated on the following conditions: requirement

1. It exits as ServerName item with the current server name or as SECTION item
in the [ACTIVE] section.
2. The section name is specified via the SAP_START_SYSTEM environment vari-
able. In this case the [ACTIVE] section is ignored.
3. It is specified as parameters when directly executing jrfcserver_start. In
this case theSAP_START_SYSTEM environment variable and the [ACTIVE]
section are ignored.

The following section describes the available parameters in the [SECTIONNAME] parameters
section.

This name refers to saprfc.ini to determine the SAP system data. DESTINATIONS

The value is a string:

• W74RFC
Name of the system as specified in saprfc.ini at DEST
Default: None

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
 jrfcserver.cfg - RFC Destinations
118 8 Configuration Files - Reference

[SECTIONNAME] Section, Continuation

PROGID PROGID is the unique identifier of the RFC destination as specified at Program ID
in the SAP system in the sm59 transaction.
This name refers to the data in sm59 in the SAP system. The SAP system data is
determined via DESTINATIONS.
The section may contain multiple PROGID items. After each PROGID item the
thread number, which are started from the JRFC Server main process as a
maximum, can be optionally specified to allow a parallel processing.
If no PROGID item exists, the PROGID setting in saprfc.ini is used. If there also
no item exists, no RFC destination is started.
It is advisable to use the server name as name component to get a unique iden-
tifier if multiple OM servers are to establish RFC destinations to the same SAP
system.

naming con- The identifier can include letters, numbers, '+', '.', '-', and '_' characters!
vention The value is a string:
• SEAL-ALFILECHECK-ShortCutNumber
ArchiveLink FileChecker, alfileche-cker.cfg
• SEAL-ALVIEWS-ShortCutNumber
ArchiveLink View Server, alviewserver.cfg
• SEAL-BCXDC-ShortCutNumber
BC-XDC Interface, jrfcserver.cfg
• SEAL-CONNC-ShortCutNumber
Output via JRFC Server, jrfcserver.cfg, or RFC Server, rfcserver.cfg
• SEAL-DPF4C-ShortCutNumber
Conversion Server and PDF Longlife Suite SAP Integration - conversion/vali-
dation of files already checked-in,convservdpf.cfg
• SEAL-PDFLLS-ShortCutNumber
PDF Longlife Suite SAP-Integration - check-in,filecheck.cfg
• SEAL-VIEWS-ShortCutNumber
DMS View Server,dvsviewserver.cfg
Default: None

RLIGATE RLIGATE specifies the directory for the repro list processing.

The value is a string:

• %PLSDATA%\io\stargate
Default: %PLSDATA%\io\stargate

XMS XMS specifies the minimum memory at start.

The value is an integer with possible values: 0, 64, 128, 256, 512, 1024
• 0

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
jrfcserver.cfg - RFC Destinations
8 Configuration Files - Reference 119

[SECTIONNAME] Section, Continuation

No memory parameter is passed.

• 512
Minimum memory at start in MB
Default: 64

XMX specifies the maximum memory. XMX

Specify a three times larger size than the maximum file size, which is to be hint - recom-
processed, as value. mendation:
The value is an integer with possible values: 0, 64, 128, 256, 512, 1024
• 0
No memory parameter is passed.
• 1024
Maximum memory in MB
Default: 256

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
120 9 Configuration Tables - Reference

9 Configuration Tables - Reference

introduction This chapter contains an alphabetically sorted list of all configuration tables
relevant for the basis configuration in SAP.

description Each configuration table and its fields is described in a separate section.

internal key When displaying the value help for certain fields, it is possible to display the
internal key of the value in addition to the description text.

display key This is how you display the internal keys:

Step Action
1
Click in the icon bar of SAP GUIor press Alt+F12 alternatively
and select the Options item.
2 Select on the left:
Interaction Design→Visualization 1

3 Activate in the Controls section:

Show keys within dropdown lists

Caution - re- After modifications of the configuration tables, the end application must be
start required restarted.

in this chapter This chapter deals with the following topics:

→ /seal/bas_cr142 - Define Parameters, Page 121

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
9 Configuration Tables - Reference 121

/seal/bas_cr142 - Define Parameters

General parameters are specified. description

This is how you open the table: open the table

Step Action
1 Start the transaction: /n/seal/img
2
Click at
Basis Configuration

→Define Parameters
(table: /seal/bas_cr142)

The table has the following parameters: overview

Parameter ID defines the parameter for which a value is to be specified. The Parameter ID
possible values at Parameter Value depend on the value of Parameter ID.
Values of the following enumeration are supported:
• PARA_DDEST Unconditional Use of Destination NONE with Classifica-
tion
The DESTINATION parameter value is specified for the characteristic evalua-
tion.
• PARA_GWHSB Parameter Value of USE_GWHOST at BACK
The parameter value of USE_GWHOST is specified for RFC client connections
(destination BACK).
• PARA_GWHST Parameter Value of USE_GWHOST
The parameter value of USE_GWHOST is specified for RFC server connections.
• PARA_NSWAP No byte swapping in OTF data with endianness mismatch
Swapping bytes in bitmap data on bigendian Unicode systems is
suppressed.
• PARA_UCORR Correction in OTF Data Streams
The execution of the length correction in ST commands of OTF data
streams is specified.
Default: None

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
122 9 Configuration Tables - Reference

/seal/bas_cr142 - Define Parameters, Continuation

Parameter Value Parameter Value specifies the value of the parameter. The possible values
depend on the value of Parameter ID.
Values of the following enumeration and any strings are supported depending
on the value of Parameter ID:
PARA_DDEST as Parameter ID:
• empty (default)
Destination NONE is only used for selected transactions (mm02, cv0*, Conver-
sion Server) at the characteristic evaluation in order to accelerate the data
evaluation.
• X or Y
Destination NONEis used at all transactions at the characteristic evaluation.
PARA_GWHSB as Parameter ID:
• Y
Set USE_GWHOST for RFC client connections to Y.
• N (default)
Set USE_GWHOST for RFC client connections to N.
PARA_GWHST as Parameter ID:
• Y
Set USE_GWHOST to Y.
• N (default)
Set USE_GWHOST to N.
PARA_UCORR as Parameter ID:
• empty (default)
Consider configuration referred to SAP note 944778 at the length correc-
tion of OTF data streams.
• X
Always execute the length correction in ST commands of OTF data streams.
Default: See above

Short Descrip- Short Description contains an explanation of the parameter.

tion
The value is a string:
• Purpose
Default: None

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
10 Changes 123

10 Changes
This chapter describes the most important changes for each released module
version.

This chapter deals with the following topics: in this chapter

→ Changes with Release 1.3.5, Page 124
→ Changes with Release 1.3.3, Page 125
→ Changes with Release 1.3.2, Page 126
→ Changes with Release 1.3.1, Page 127
→ Changes with Release 1.3.0, Page 128
→ Changes with Release 1.2.8, Page 129
→ Changes with Release 1.2.6, Page 130
→ Changes with Release 1.2.5, Page 131
→ Changes with Release 1.2.4, Page 132

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
124 10 Changes

Changes with Release 1.3.5

DLL The current version of sapftp/saphttp requires the following DLLs in the
tools\bin_xxx directory: sapnwrfccm.dll (non-Unicode) and sapnwrfc.dll
(Unicode).

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
10 Changes 125

Changes with Release 1.3.3

In the delivered configuration files of the RFC destinations, for instance jrfc- RFC destination
server.cfg, all RFC destinations are inactive. The start of the desired RFC desti-
nations has to be activated explicitly.

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
126 10 Changes

Changes with Release 1.3.2

wrapper pro- If Unicode SAP systems are used only (no mixed operation with non-Unicode
gram SAP systems, determined via UNICODE in saprfc.ini), sysinit automatically
copies the Unicode version of sapftp and saphttp from SAP to sapftp and
saphttp and replaces the wrapper program from SEAL Systems.

The sapftp/saphttp wrapper programs are delivered with digital signature.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
10 Changes 127

Changes with Release 1.3.1

As of JRFC Server version 2.0.2 or newer, the logon information for the initial cadrfc.ini
logon is no longer required for RFC server connections in cadrfc.ini (this infor-
mation was required for JRFC Server as of version 2.0.1).

The logging of additional information, for instance connection status and logging
memory usage, and the creation of HTML files containing the transferred data
from and to SAP can be activated via the SEAL_TRACE parameter in the
saprfc.ini file.

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
128 10 Changes

Changes with Release 1.3.0

Web service The description of the integration via Web service has been inserted to the
common basis documentation.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
10 Changes 129

Changes with Release 1.2.8

As of JRFC Server 2.0.1 or newer, cadrfc.ini has to contain logon information cadrfc.ini
for the initial logon also for RFC server connections. The data has to be located
in a system-dependent section [SAP\SystemName] which specifies the client as
CadRfcClient item. A client-dependent section will not be considered!

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
130 10 Changes

Changes with Release 1.2.6

sap_conn_check- The sap_conn_checker program is provided to evaluate SAP system data.

er

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
10 Changes 131

Changes with Release 1.2.5

The RFC destinations which are to be started can be specified within the config- start depending
uration file like jrfcserver.cfg depending on the current server. on the current
server

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
132 10 Changes

Changes with Release 1.2.4

Unicode The UNICODE parameter in the saprfc.ini file is evaluated at the start of RFC
connections. Dependent in this value the Unicode or non-Unicode variant of the
sapftp and saphttp program is started. The wrapper programs sapftp and
saphttp from SEAL Systems are used to determine the correct variant. It is not
necessary to copy files.

SAP system data The SAP system data is specified only once in saprfc.ini for each SAP system.
Multiple RFC destinations are specified via PROGID entries in the configuration
file like jrfcserver.cfg.

start in groups RFC destinations can be grouped within the configuration file like jrfc-
server.cfg. Each of these groups can be started and stopped individually.

start with en- The required RFC connections for start, status request or stop can be specified
vi-ronment vari- via the environment variable SAP_START_SYSTEM.
able

start with call The required RFC connections for start, status request or stop can be specified
pa-rameter via call parameters. This is not supported by plsstart and dvsstart.

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Bibliography 133

Bibliography
[SAP_BASECONF_SAP_TEC]
SAP Basis Configuration - SAP, System Description, SEAL Systems
[SAP_BASECONF_SNC_TEC]
SAP Basis Configuration - SNC and RFC, System Description, SEAL Systems

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
134 Terminology

Terminology
The following section explains the most important terms that are used in this documentation. Terms
identified by → refer to other terms in this section.
Customizing
Configuring the SAP system
cv04, cv04n
→Transaction to start the search function in SAP DMS
cv<xx>, cv<xx>n
Transaction used for document search and management within the context of document
management in SAP DMS (refer to the SAP online documentation)
Document
→Document information record
Document management system
In the document management system (short: DMS), the →document information records
and their assigned files are managed.
Document information record
A master record in the →DMS containing management data for a document and original
files. To each document information record, a identification key is assigned, consisting of
four partial keys: type, number, part and version.
Developer license
Key giving an SAP user development authorizations
Client
A unit within an SAP system that is independent with regard to action, organization, and
data functions. It also has separate master records in a table within the SAP system
Naming convention
Agreement regarding name assignment for development purposes, for example all devel-
opments in a system should be given a prefix of X, Y, or Z as these prefixes have been
reserved for customers by SAP.
Namespace
Protected namespaces can be reserved upon request by SAP. The namespace for SEAL
Systems is /seal/, /sealc/ (for customer development) or /dvsrepro/ (old).
Transaction
Means of executing programs
Transaction code
Identifier naming a →transaction in the SAP system
Transport
Exporting/importing data between SAP systems

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Abbreviations 135

Abbreviations
ABAP
Advanced Business Application Programming (SAP system programming language)
DPF®
Digital Process Factory® from SEAL Systems
DMS
Document management system
FTP
File Transfer Protocol
OSS
Online Support Service
PDF
Adobe Portable Document Format
PDF/A
Adobe Portable Document Format (PDF/A norm)
PLM
Product Lifecycle Management
PLOSSYS®
Product family from SEAL Systems
RFC
Remote Function Call

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
136 Keywords

Keywords
Symbols H
/seal/bas_cr142 121 HOSTNAME 87

A J
ABAP 135 jco_rfc*.trc 102
ABAP_DEBUG 21, 104 jco_rfcPID_UUID.trc 44
Action 10 jrfcserver.cfg 114
ACTIVE 116 jrfcserverstart 49
Aktivierungsart 27
ASHOST 96 K
Kommunikationsart mit dem Zielsystem 28
B Kurzbeschreibung 122
Beschreibung 25
L
C Logon
CAD_CHECKOUT_DLL 22 Benutzer 81
CadDialogNetAddress 87 Passwort
cadrfc.ini 76 unverschlüsselt 82
CadRfcClient 84
CadRfcDestination 86 M
CadRfcLanguage 85 ModuleGlobal 10
CadRfcPassword 82 ModuleSelect 10
CadRfcPasswordCoded 83 MSHOST 98
CadRfcUser 81
CODEPAGE 107 O
convservdpfstart 49 oms_server 79
convservstart 49 omscli 79
CPIC* 102 OSS 135

D P
DEST 94 PARA_DDEST 122
DESTINATIONS 117 PARA_GWHSB 122
dev_jco_rfc.log 44 PARA_GWHST 122
dev_rfc* 102 PARA_UCORR 122
DISPLAY 87 Parameter-Id 121
DMS 135 Parameterwert 122
DPF® 135 PDF 135
dvsstart 49 PDF/A 135
dvsviewserverstart 49 PLM 135
PLOSSYS® 135
F plsstart 49
filecheckstart 49 PROGID 118
FTP 135 Programm ID 27
proxyinfo 29
G
Gateway-Host 25, 40 R
Gateway-Service 25, 40 reginfo 29
GROUP 99 RFC 135
GWHOST 100 RFC_TRACE 21, 102
GWSERV 101 RFC-Destination 25
SAP Basis Configuration - Server 2021-11-25 SEAL Systems
System description 1.3.9 www.sealsystems.com
Keywords 137

rfcserverstart 49
RLIGATE 118
rlistsap 79
rswf_test_http 69

S
sap_conn_checker 88
sapcli 79
sapftp 18
sapftp.dll 22
saphttp 18
saphttp.dll 22
SAPLOGON_INI_FILE 88
saplogon.ini 88
saprfc.ini 88
SEAL_TRACE 103
sealencrypt 83
secinfo 29
smicm 70
SNC_MODE 108
SNC_MYNAME 109
SNC_PARTNERNAME 110
SNC_QOP 111
SNC_SSO 112
SYSNR 97
sysstart 49

T
TYPE 95

U
UNICODE 18, 106
USE_GWHOST 121
USE_SAPGUI 81, 105

V
Verbindungstyp 25

X
X509CERT 113
XMS 118
XMX 119

Z
Zeichenbreite im Zielsystem 28

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
138 Index

Index
A requirement USE_SAPGUI 105
ACTIVE, at start 47 DMS Rlist 90
application server restriction - system/client-spec. logon 79
determine host name, USE_GWHOST 42 DMS Scan 90
load distribution 40 requirement USE_SAPGUI 105
DMS View Server 90
C Document information record 134
call parameter, at start 48 document management system 134
check-out document, see document information record
error, determine host name 42
client 134 E
code page 107 environment variable
Conversion Server, explicit 28 SAPLOGON_INI_FILE 88
RFC Server, explicit 28 error
configuration debugging, activate 104
OM server, OM server proceeding, advisable 69
configuration 17 RFC destination
SAP as consumer SAP gateway logging, activate 43
Web service 61 trace message, activate 21, 44, 102
SAP as provider starting the RFC server 49
Web service 51 system function, debugging 21
configuration file typical 71
overview 15 typical problem 39
Conversion Server 90 Web service
sm59 SAP as consumer
code page, explicit 28 check 69
non-Unicode 28 trace message
customizing 134 display 70
cv<xx>, cv<xx>n 134 SAP as provider
cv04, cv04n 134 debug request 60
record requests 59
D trace message, activate 59
debug
Web service request G
SAP as provider 60 gateway
requirement 52, 62 settings for load distribution 40
debugging
system functions 21 H
developer license 134 HTTPS
dialog user 81 see SAP_BASECONF_SNC_TEC 7
directory
convention at the specification 8
J
repro list processing 118 JRFC Server 90
DLL variant configuration file 114
requirement 22 sm59
DMS 134 Unicode 28
DMS Loader 90 JSAPcli 90
DMS Loader/ABAP 90
L
DMS Repro
language

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com
Index 139

at logon 85 PDF Longlife Suite - SAP Integration 90

on connection establishment, supported
85 R
load distribution registration 49
between application server 40 registration, see logon
gateway options 40 repro list processing
log file directory 118
connection status, requirement 103 requirement
memory status, requirement 103 cadrfc.ini 76
logon connection status, log 103
client 84 debug
configuration 76 Web service request
language 85 SAP as provider 52, 62
password DLL variant 22
coded 83 DMS Repro 105
requirement 81 DMS Scan 105
requirement - system/client-spec. user 79 logon 81
restriction - system/client-spec. logon 79 memory status, log 103
system/client-spec. user 79 message server 18
MTOM 68
M saprfc.ini 88
memory SSO, deactivate 112
maximum 119 system/client-spec. logon 79
minimum at start 119 Unicode - separate section in jrfcserver.cfg
status log, requirement 103 117
message server Web service
requirement 18 roles with authorizations 52, 62
MTOM restriction
requirement 68 system/client-spec. logon 79
RFC client 90
N RFC destination
namespace 134 allow
naming convention 134 alternatives 29
prefix for secinfo/reginfo, specify 37
O reginfo
OM server 31
publish 24 >= NW 7.45 31
OTF secinfo
length correction in ST commands 122 33
overview >= NW 7.45 33
configuration files 15 simulation mode 36
RFC client/RFC server 90 configuration on SAP systems as of 4.7 24
RFC destination on SAP systems as of 4.7 24 data, overview 15
logon data 76
P SAP gateway logging, activate 43
parallel processing 118 SAP system data 88
password security configuration 29
coded 83 start 45
path specification, convention 8 order 46
PDF status log, requirement 103
Icon zur einfachen Navigation aktivieren, test 50
ab Adobe Reader 10 9 trace message

SEAL Systems 2021-11-25 SAP Basis Configuration - Server

www.sealsystems.com 1.3.9 System description
140 Index

activate 21, 44, 102 USE_GWHOST

type 90 parameter value, specify 121
RFC Server 90
sm59 V
code page, explicit 28 variable
non-Unicode 28 Action 10
RFC server 90 ModuleGlobal 10
error during start 49 ModuleSelect 10

S W
SAP system Web service
data configuration 88 requirement
SAP system data roles with authorizations 52, 62
identify 88 SAP as consumer
SAPcli 90 ABAP proxy, select 64
SNC check 69
activation sign 108 configuration 61
certificate large amounts of data, optimize trans-
for logon 113 fer with MTOM 68
name of the communication partner 110 logical port, create 65
name of the user 109 suppress message ID transfer 67
quality of protection 111 trace, display 70
see SAP_BASECONF_SNC_TEC 7 SAP as provider
SSO binding, create 55
deactivate configuration 51
requirement 112 debug request 60
SNC_SSO 112 requests, record 59
see SAP_BASECONF_SNC_TEC 7 service, select 54
system user 81 trace, activate 59
URL, determine 57
T timeout 71
thread wrapper program sapftp/saphttp for Unicode
maximum number 118 18
timeout digital signature 126
Web service 71
trace message
display
Web service
SAP as consumer
display 70
transaction 134
transaction code 134
transport 134

U
Unicode
code page 107
configuration 18, 106
requirement - message server 18
requirement - separate section in jrfcserv-
er.cfg 117
requirement - wrapper program 18

SAP Basis Configuration - Server 2021-11-25 SEAL Systems

System description 1.3.9 www.sealsystems.com