Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

For that reason you may want to define the connection parameters for the archiving system in another section.

The definition file has to be placed in config folder. (defined in instance common tab)

The reference to this file is currently in common tab called SIDMappingDefFile.

The sections regarding the archiving system also follow a certain structure.

...

Sample of multiple archiving connection definitions

[_ARC_FI]
HttpProtocol = http
HttpHost = test.contentservers.kgs-software.com
HttpPort = 1234
HttpPath = /KGSAdmin-CS/contentserver
HttpParameters =
Security = 0
LateLocking = 1

[_ARC_TE]
HttpProtocol = http
HttpHost = 17.59.128.128
HttpPort = 2345
HttpPath = /KGSAdmin-CSV/contentserver
HttpParameters =
Security = 0
LateLocking = 1

SIDMapping definition

In case you require a linking to multiple SAP systems within one DocumentRouter instance you may need to define an SID-mapping file which contains the connection information required for RFC communication. Like the DataInterface-definitions the SID mapping definition follows a certain structure which allows you to define the mapping to your needs or requirements.

...

Structure of an SID mapping definition

...

[_SID_<SID configuration name>]
SAPHost = H | 0 | 0 | <IP address or hostname of the SAP system>
SAPClient = M | 0 | 0 | <Client related to the SAP system>
SAPSystemNo = Y | 0 | 0 | <System number of the SAP system>
SAPUser = U | 0 | 0 | <User used for RFC communication with the SAP system>
SAPPassword = P | 0 | 0 | <Password related to the user used for RFC communication with the SAP system>
SAPLanguage = L | 0 | 0 | <Language used for the RFC communication with the SAP system>

You may define as many SID configurations in the SID as are required by your needs.

...

Sample of multiple SID mapping definitions

[_SID_T32]
SAPHost = H | 0 | 0 | 127.127.127.32
SAPClient = M | 0 | 0 | 800
SAPSystemNo = Y | 0 | 0 | 00
SAPUser = U | 0 | 0 | saproot
SAPPassword = P | 0 | 0 | S3curePassw0rd!

...

document router 4 the SID mapping for linking does not exist anymore via SID mapping file.

Instead you can use in schema definition the S like in this example

Code Block
[foobarInstance]
SYSID                                                   =       X       |;        |1          |
MANDANT                                                 =       X       |;        |2          |
CONTREP                                                 =       C       |;        |3          |
LoginCL                                                 =       S       |;        |0          |@SYSID@MANDANT

As you see, LoginCLis connected to the Variable S. We see it is concatenated from 2 others. So in index file, the concatenation from place 1 and 2 gives the variable value og LoginCL. This value is pointing to an existing SAP-Connctor instance with this name.